I tried running the command from prompt. Same result, just hangs on the command.
I have an idea why some users reported slower speeds after running LagFix previous versions - it did not finish running. The problem with older version is that I used another lib for su and shell stuff and this way LagFix did not properly synchronize with fstrim. So a lot of weird things were happening, like /data trimming output was shown after success message. Some people didn't see it at all.
Right now EVERYTHING WORKS! And all the errors are properly handled. Everyone with lagfix hanging also reports that running fstrim manually also "hangs".
So, just open terminal, run fstrim and let it run - you may go back to home screen. Check like every five minutes. Looks like Samsung failed with memory in Nexus too.
So, check how long it runs, I might move the execution into background service.
root@android:/ # /data/data/com.grilledmonkey.lagfix/files/fstrim -v /data 4244234240 Bytes was trimmed
Looks like 4 gigs were processed (: It can't be done in one second. Ook, so the problem is diagnosed, I'll move processing to a service with status notification.
By the way, scheduler auto-trim in Premium version already runs in background service and no one complained yet.
Many thanks for your report! I wish Google had promo codes like in AppStore so that I could give away Premium version for free to everyone who helped me improve LagFix. Eh...
|fstrim, htc one x, lag fix, nexus 7, trim|
|Thread Tools||Search this Thread|