[Touch Pro2, Tilt 2 Android Development] Caldair:
Build.Prop Tweaking

I have been messing around with some lines in /system/build.prop and there seem to be some gains to be made here. In fact I find these tweaks to be more of an improvement than overclocking! and OCing is generally not necessary.

For your peace of mind you may want to backup data.img first.(if you use an SD build like me)

I personally use these tweaks in conjunction with the app System Tuner which I use to set androids Low Memory Killer (I use aggressive setting, set at boot) and I use the SYSCTRL.Conf tweaks (I just use Recommended button, set at boot). I think the LMK setting is important to have enough free ram, the other sysctl stuff is probably not so important. I also have my read_ahead_kb set to 0 as in an earlier post in this thread.

Just let me say here that you will not be doing ANY multitasking with these settings. Strictly using one app at a time, nothing cached in ram.

Firstly enable Dalvik:JIT (Just In Time mode) seems to yeild an overall performance gain, with the very rare hang I presume caused by overwhelming the dalvik. Overall a much smoother experience and very fast response within apps.

Edit the existing line in build.prop

dalvik.vm.execution-mode = int:fast

to

dalvik.vm.execution-mode = int:jit

Second VM Heap: I increased my dalvik vm heapsize to 72m. This gives large, modern apps the room they need to breath. Any higher would be too much for our RAM to handle.

Again edit the existing line in build.prop

dalvik.vm.heapsize=32m

to

dalvik.vm.heapsize=72m

Now the rest of these entries I have added manually to the end of build.prop immediately after the line dalvik.vm.stack-trace-file=/data/anr/traces.txt. Some of these may do nothing on our devices but some are very useful! I find that with all of these lines in build.prop everything is buttery smooth! Try them all or try whichever you like. I will break them up by type of tweak.

The important ones are the Dalvik and Graphics/Touchsreen lines.

Dalvik cache tweaks:

dalvik.vm.verify-bytecode=false
dalvik.gc.type=precise
dalvik.vm.dexopt-data-only=1
persist.android.strictmode=0
debug.gr.swapinterval=0
dalvik.vm.jmiopts=forcecopy
persist.sys.purgeable_assets=1

Graphics/Touchscreen performance:

debug.composition.type=mdp
debug.enabletr=true
debug.sf.hw=1
video.accelerate.hw=1
debug.egl.profiler=1
debug.egl.hw=1
persist.sys.use_16bpp_alpha=1
windowsmgr.max_events_per_sec=50
debug.performance.tuning=1
persist.sys.use_dithering=0
persist.sys.ui.hw=1
persist.sampling_profiler=0
ro.sf.compbypass.enable=1

Power Saving (Don't know if these make much difference yet)

ro.ril.disable.power.collapse=0
ro.ril.power_collapse=1
ro.config.hw_fast_dormancy=1
ro.config.hw_power_saving=true

Qualcomm Specific (No idea if these do anything)

debug.qctwa.statusbar=1
debug.qctwa.preservebuf=1
debug.qc.hardware=true
com.qc.hardware=true

**After editing build.prop the system creates a file in the same location called build.prop.bak. I delete that file before I reboot.

**Before rebooting I also use System Tuner to wipe the Dalvik Cache.

For your comparison try installing angry birds, but leave the sound and backgrounds turned on... For me the performance matches that of disabling sound/backdrops.