Thanks a ton Kusro for the information. I may not agree with all the changes, but overall, its a good start.
Some of the tweaks are not really required. You might want to take a look at:
http://www.jeffmixon.com/series/exam...hensive-guide/
http://android.stackexchange.com/que...uild-prop-mean
Seeder naysayers/non-believers:
http://www.xda-developers.com/androi...cked-up-to-be/
http://www.geek.com/android/lag-defe...eless-1534691/
I commented out these two entries, since I don't have these apps installed:
#sys.keep_app_1=com.desaxedstudios.bassboosterpro
#sys.keep_app_2=com.smartprojects.RAMOptimization
As per Jeff Mixon's article & further Android code comments say the windows managers mx events shoul at most be 90:
windowsmgr.max_events_per_sec=90
Since our M96 only has a density of 150, so M96 users should comment out this line:
#ro.sf.lcd_density=265
Furthermore, the M96 users should edit their build.prop file instead of replacing, since this build.prop is from T68, so would turn the bigger sibling down to T68 size. Just kidding!
The other parameters, even if they don't help much, don't have much downsides, so its not 'dangerous' to apply.
Most of the gain in speed I feel I'm having is from the usage of Lightning Launcher (maybe Nova/ADW could have had almost the same effect with judicious tinkering) & some throttling/disabling of unneeded apps & services. I'm not sure how much further build.prop will take my M96, but I've applied it all the same.
I tried out No-Frills CPU control to see how the kernel is being used. To my surprise, our kernel only has three clock speeds - 396, 792 & 996 MHz. The default CPU governor was Performance! The default I/O scheduler was deadline. I changed it to OnDemand & NOOP respectively. I wonder why we have a slow CPU (Freescale i.MX 6 Cortex A9 1.0GHz) & then have it running at top speed continuously to make up for it.
EDIT: Attaching the original as well as the modified build.prop files. Added extension in order to upload.
Jp