[Desire Android Development] ltGuillaume:
Zipalign apps is ok, might take some time at boot, but it'll save you some memory.

Fix permissions is only necessary if you have some related problems.

It seems to me that if you set Mount2SD to 8192kb (which probably won't help, use 1024kb or 2048kb), AND enable the init.d script "SD boost", you eventually end up having a read ahead buffer set in "Read ahead value" of Beanstalk Init.d scripts, right? The 10mount2sd script is run first, then the 10sdboost overwrites it again.

Similarly, swappiness from 02sysctl ("Enable sysctl", which looks pretty good) will probably be overwritten again by the 10mount2sd script and again by 13minfree ("minfree values"). Can anyone confirm? What's more, "Enable minfree values" again overwrites some values introduced resp. by Sysctl and later by 10mount2sd. It's rather annoying that Mount2SD doesn't give you a "leave be" option. I'm considering to comment it (=running the function "ProcessMemory") out in the 10mount2sd script altogether.

Clear cache: useful if you use internal memory for /data/data, like me (space is scarce, but this will help. It will take some extra time for some apps to load, since their cache has to be rebuilt.

Enable Scheduled tasks (cron) doesn't do much (if anyone can give me a reason why this is here, I'd love to know

File system speedup Some of it probably doesn't do anything, since it changes some EXT4-specific parameters while mounting /system and /data, but our Desire doesn't even use EXT4 on those partitions. But if it doesn't just cancel the operation because of the incompatible switches, at least it does disable access time writing, which could maybe increase performance on /data a bit. However, I'd go for the Speedy tweak instead then, which also includes disabling directory access time.

Enable battery tweaks: you can read here what it does https://www.kernel.org/doc/Documentation/sysctl/vm.txt (dirty_expire_centisecs and dirty_writeback_centisecs), I don't want to fiddle with it as I don't know the implications. So I left the tweak disabled.

Enable touch tweaks would only make sense if the settings really are customized for the HTC Desire and not blindly taken over while porting. Can someone shed a light on that?

Enable gpu renderer cannot be undone: it removes /system/lib/egl/libGLES_android.so, permanently, and edits /system/lib/egl/egl.cfg. You tell me if it does anything.

Enable sleeping is a bit confusing as a title, since it actually disables sleepers from the CFS Scheduler, which might improve UI responsiveness a bit (http://xdaforums.com/galaxy-s2/general/ref-kernel-stuffs-how-ics-kernel-t1572937)

Enable journalism slows down write performance. If you have random reboots, it can save you the pain of lost data, otherwise you should disable it on a slower device like the Desire.

Enable sqlite3 just vacuums and reindexes all SQLite databases on e-ve-ry reboot, which take a lot of time. I doubt it gives an enormous boost in the apps using the db's, but it might, I just don't have the patience for it :P (I use SD Maid to do this "manually" once in a while).

Enable WiFi sleep just sets the WiFi to turn off 10 seconds after the screen turned off. Default is 15 minutes. I don't think it does anything if you have "Keep Wi Fi on during sleep" set to "Always".

Enable iostats actually disables IO stats, which reduces overhead and might give you a bit of a performance increase. I enabled it.

Enable setrenice alters the priority of some default processes over others, like the phone and keyboard, camera etc. As I didn't agree with the priorities as stated in the script, I disabled it.

Enable Super tweaks: again, redundancy redundancy redundancy: it overwrites previous tweaks like swappiness, minfree, and battery tweaks.

Enable Speedy modified: remounts without file/directory access time writes, should improve speed, does some scheduling optimizations, ALSO sets the Set sd card read ahead cache size (2048KB), includes IPv4 networking optimizations, and prevents some useless procedures that cause some overhead. I'd recommend enabling this one.

Enable Loopy Smoothness: again a lot of overlap: process prioritizing (=setrenice), but supposedly it keeps looping a number of times to make sure the priorities are kept. It looks messy.

All in all, there's a lot of overlap and I think it just depends on what script runs last, which relates to the alphabetical order inside the init.d folder.

I would really appreciate any feedback on my findings AND

assumptions

Unfortunately, for me a combination of the tweaks I think really are worth trying (the ones in green) actually slowed down the Desire a whole lot. Anyone having the same results there?