[Galaxy S II Android Development] Orginator:
I've been doing some testing related to boostpulse and smooth scaling, trying to get a smooth experience with a reasonable battery drain. So far my findings are that Boostpulse has to be set to 400 Mhz (Anything under that decreases the overall smoothness), and to achieve a somehow good scaling I have set smooth scaling to 800 Mhz.

Now I believe that more reasonable would be setting smooth scaling at 600-700 Mhz, as that would still leave enough gap between boostpulse and smooth scaling as well as give enough raw power to not push the CPU towards its full-speed without a significant reason. Sadly that option is currently not available, so I'll have to stick to 800 Mhz until that changes. (MCM, please?)

I also noticed that my CPU undervolt settings were not working properly duo to the fact that nowadays there are 16 CPU Steps available, and my init.d script was configured to only 5 Steps. I kinda missed that one and accordingly my start-up script wasn't applying the voltage settings like it should.

For anyone who wants to undervolt his CPU:

1. Install Voltage Control and StabilityTest from Play Store

2.

-> A) Use Voltage Control to lower the voltage settings for each frequency, one at a time (best start with the highest frequency (1200 Mhz) and the reference voltage settings, go down in 25 mV steps)

-> B) Set the MIN and MAX frequency settings to the one that you are testing (for example 1200 Mhz)

-> C) Use StabilityTest to check whenever your smartphone is stable, let the "Classic Stability Test" run in background for at least 10 minutes and while it runs keep using your smartphone (whatever, browse, open gallery, app drawer etc.)

-> D) Do at least 3 minutes of the "CPU+GPU Stability Test", here you don't need to do anything, just let it run and see whenever everything is ok..

-> If everything is ok, lower the voltage and repeat all the steps, do that until you found the lowest possible voltage (PS: if you are too lazy, you can try using my settings)

My current CPU UnderVolt:

After you have the optimal settings you'll see a much better battery run time, it really makes a huge difference! (btw. best possible is doing the undervolt test in summer, or well when its the hottest in your area, as only then you can ensure 100% stability, and remember each chip is different!)

I haven't finished testing everything but so far those are the smoothest settings for me: (with a reasonable battery drain)

CM10 + Siyah v5 (Both latest, also using v5 because it seems that mali touch boost isn't working properly in v4, tho not tested it too deeply so don't shot me :P)

ROM:

-> Boostpulse: 400 Mhz

-> I/O: ROW

-> GRALLOC: Samsung Gralloc

-> SKIA: Fimg2d3x Skia

-> Scrolling cache: ON

-> Entropy Generator: Default

-> Media Scanner: Default

-> CFS tweaks: Samsung defaults (balanced) PS: you can use "Linux kernel defaults" if you need a better battery run time

CPU:

-> Governor: Pegasusq (bootpulse)

-> MAX Freq: 1000

-> MIN Freq: 200

-> CPU Undervolting: No Undervolting (I use a init.d script to set my stuff, you can also use Voltage control to set your settings on boot)

-> Gentle Fair Sleepers: ON

-> Idle: ATR + LPA

-> Smooth Scaling: 800 Mhz (Wish I could use 600 or 700 Mhz, btw. you can also check 500 Mhz but then you'll also see the CPU reach the highest freq more often)

-> Max CPU Lock: Dual Core

-> Hotplug mode: CPU HOTPLUG (Default)

GPU:

-> Mali Touch Boost: Step4 (MCM, no Step5 option?????)

-> Step1: 62 Mhz @ 850 mV

-> Step2: 100 Mhz @ 900 mV

-> Step3: 160 Mhz @ 950 mV

-> Step4: 267 Mhz @ 1050 mV

(I wasn't really doing much here, I'm sure that some of you can get the voltage lower)

Also while testing CPU undervolt, don't play with GPU settings, do one at a time to avoid a misleading situation and false results.