Yea, that's a great tool. But it kills EVERYTHING and some of the processes restart. And if you have many apps installed, it just ruins the performance.
Instead soft reboot the phone
Data stored on NAND flash (yes like the SSD & ours phone's internal storage) is saved differently than on traditional hard drives. Similar to HDD storage, NAND also keeps a map of where data is stored. When you delete a file, rather than freeing up that spot for re-use, most of the time it’s simply marked as “not in use”. The data is still there, and, more importantly, the entry in the file system is still there. (We just can’t access because it’s “not in use”.) That means as you write and delete files, the file map has to get bigger, and it takes more time to find the files that you’re looking for. While technically not “fragmentation”, this “I/O lag” becomes more pronounced with use– causing your device to operate more slowly the more you use it. This problem has been present in virtually every Android-powered device (and almost every other device that uses NAND flash for storage)
TRIM essentially goes through the file records and frees up blocks that you’ve deleted by telling the controller to stop keeping track of them. Now the controller only has to keep track of the files that haven’t been deleted, which speeds things up significantly!
Short info
TRIM support was included in the desktop Linux kernel in 2008. Microsoft’s desktop operating systems didn’t get support until 2009 with Windows 7. Apple didn’t pick up TRIM support on OS X until 10.6.8 in 2011. Android, however, didn’t pick it up until version 4.3
Unfortunately, if a device isn’t running Android 4.3, it’s unlikely that OEM has built in TRIM support. For those of you who have another new devices running Android 4.3, you’re all set, TRIM is set up and running automatically.
Data stored on NAND flash (yes like the SSD & ours phone's internal storage) is saved differently than on traditional hard drives. Similar to HDD storage, NAND also keeps a map of where data is stored. When you delete a file, rather than freeing up that spot for re-use, most of the time it’s simply marked as “not in use”. The data is still there, and, more importantly, the entry in the file system is still there. (We just can’t access because it’s “not in use”.) That means as you write and delete files, the file map has to get bigger, and it takes more time to find the files that you’re looking for. While technically not “fragmentation”, this “I/O lag” becomes more pronounced with use– causing your device to operate more slowly the more you use it. This problem has been present in virtually every Android-powered device (and almost every other device that uses NAND flash for storage)
TRIM essentially goes through the file records and frees up blocks that you’ve deleted by telling the controller to stop keeping track of them. Now the controller only has to keep track of the files that haven’t been deleted, which speeds things up significantly!
Short info
TRIM support was included in the desktop Linux kernel in 2008. Microsoft’s desktop operating systems didn’t get support until 2009 with Windows 7. Apple didn’t pick up TRIM support on OS X until 10.6.8 in 2011. Android, however, didn’t pick it up until version 4.3
Unfortunately, if a device isn’t running Android 4.3, it’s unlikely that OEM has built in TRIM support. For those of you who have another new devices running Android 4.3, you’re all set, TRIM is set up and running automatically.
Update 3
(Some users have reported a bootloop after installing this update. Be sure to make a nandroid backup before installing this update.)
EDIT: Refer this.
Changelog:
Update 1
Added gradient statusbar
Added gradient Navigation Bar
Partially ported KitKat Platform Logo
Update 2
Fixed Platform Logo issue (Used to Force Close)
Update 3
Added KitKat clock
Changed some visuals
Added many tweaks and scripts for smoother and lag-free experiance
build.prop tweaks for performance and quality
(NOTE: Density and android version will revert back to orignal.)