• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root TRIM, wiping, performance degrading?

Hi all, figured someone here would know. Since it was announced that TRIM was enabled in android 4.3 I was wondering if all the rom wipes and installs where causing degrading speed to the eMMC of our phones? Or does wiping act like formatting and therefore the eMMC hardware level controls know that those sectors are totally clear and don't need to to that "read copy modify write" function when all it needed to do was a "write" if the sector was previously empty or TRIMed. Thanks for any insight.
 
Im not sure what you mean since technically nothings ever Wiped its only overwritten as explained here


That video is for a hard drive, not a solidstate/flash drive. How they work is totally different.

Assuming phones work like SSD's, yes, not having TRIM support is indeed slowing down your phone.


OP: Try this out. I just discovered it. I've never even thought about garbage collect on my phone.

https://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix&hl=en

App doesn't work on PACMAN JB4.2.
 
Try this out. I just discovered it. I've never even thought about garbage collect on my phone.

https://play.google.com/store/apps/details?id=com.grilledmonkey.lagfix&hl=en

App doesn't work on PACMAN JB4.2.

Thanks for the link. I too never thought about TRIM on my phone, but saw my already speedy EVO 3D running AngryBean get a 30% boost in Sequential Write speed & 31% in Sequential Read just by running LagFix. I ran the AndroBench Micro scan just before and just after applying the fix without rebooting or changing what was in memory.
 
So this TRIM command is compatible with 4.2? Then why is 4.3 supposedly "TRIM compatible" when we could just run something like LagFix on 4.2?

According to the post here, "all pre-ICS devices used different memory and they do NOT need it nor support [TRIM]." Does this include our devices, since, when the Evo 3D came out, it was on Gingerbread?
 
So this TRIM command is compatible with 4.2? Then why is 4.3 supposedly "TRIM compatible" when we could just run something like LagFix on 4.2?

According to the post here, "all pre-ICS devices used different memory and they do NOT need it nor support [TRIM]." Does this include our devices, since, when the Evo 3D came out, it was on Gingerbread?

I saw that too, but figured I'd try it anyway. Maybe what I experienced was coincidental, fluctuation. It seemed to finish immediately. I'll let someone smarter than me answer this...

Edit: I just ran the benchmark again and it's back down to the pre-LagFix number on SEQ WR. SEQ RD is still looking faster, but now I think it's just normal variance.
 
Back
Top Bottom