[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] castle_bravo:
CPU1 write up

Following my previous quick test I decided to write up a little more detail. The following governors have been tested for use on CPU1 with the following results. Using a TW rom with the latest kt747 kernel. My balanced ktoonservative setup is the active governor profile set in ktweaker. In order to apply a specific governor for CPU1 you need to have a script set up. I use Smanager although whatever program you prefer is fine. Open Smanager and hit the options softkey next to your home button. Select scripts and then create a new one. Name it whatever you like.

Script

The script should be written as follows: echo userspace > sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

After echo, you will put whichever governor of your choice. For those that don’t know, echo is the value that is to be entered and after the > is the destination that value will go

If you are interested in tweaking the CPU1 governor then the script will be as follows

Echo 5 > sys/devices/system/cpu/cpufreq/ondemand/down_differential

5 is the value I want to insert. Cpufreq is where the OS stores the data for the governor to use, and down_differential is where I want that value to go. Insert whichever governor you are using after cpufreq and insert whichever setting you want to change after the governor. Some people go in to ktweaker and turn off hotplugging but that’s too annoying for me. I just run the script and check to see if the settings stuck using a root explorer. An important note is that if CPU1 is inactive at the time the script is run then the values will not be applied. Secondly, if CPU1 is not active you will not see it’s folder in the root explorer until it is active. I spam the refresh button on ESexplorer until it shows up. That’s it! If you want to know the values to change I am not putting them in here, you can look them up either in the file explorer after you set the governor up or set the governor in ktweaker and write them down. That brings up another important note. You cannot set the same governor for both cpu’s, their settings will conflict with each other so make sure you are using different governors.

Governors not compatible as CPU1 governor on a touchwiz rom

SmartassV2

Slp for scaling governor in script. Pegasusq called for in cpufreq

Superbad

Lagfree (gave delayed reboot)

Lulzactive

Pegasus

Adaptive

Asswax

These are the governors that worked. All these governors were checked with just a base install. No adjustments were made.

Intellidemand – Had smooth operation but relatively poor battery life. There are better options.

Abyssplug - A bit choppy and not consistent, not recommended.

Msm-dcvs - Good performance and good battery life, this is a good alternate to the stock ondemand CPU1 governor. I like that it’s simple and does not have any adjustments..

Badass – Crisp operation but a little high idle drain, no stutter or lag noted. The phone stayed cool on heavy load, a touch high battery drain on load. This is a good option for a performance based setup.

Scary – Runs slow with noticeable lag. Runs warmer than the rest with keyboard stutter when using swype, not recommended.

Wheatley – Nice second governor, smooth with no lag. Performed similar to MSM but this has adjustments to further optimize its performance.

Lazy – I thought lazy was OK, barely noticeable lag during games, not even lag really but the games would actually run slower. Battery drain during load was pretty good. Not a bad choice for a more battery conservative setup.

Conservative – Stock settings leave the phone frustratingly unusable. While swiping along the screen it skips making scrolling or typing on the keyboard impossible. Not recommended.

Ondemand – stock cpu1 governor.

Userspace – This governor had pretty good idle drain similar to powersave. While scrolling or swiping for keyboard the phone would skip and lag sometimes. It happened enough to be frustrating, it seems that it is just barely not enough and if it had adjustments I would recommend this with some tweaking. Since it does not offer tweaking I just didn’t find it to be that effective.

Powersave - Great battery life while web surfing and “typical” phone use, heavy battery drain while running games and benchmarking. This would be an excellent screen off CPU1 governor or for somebody who uses their phone more like a personal assistant than a multimedia device. (My favorite and will be my go to once testing is done)

P.S. For those interested in using powersave there is an important note. Powersave will stick your governor at min mhz. which is the reason for heavy battery drain on load, one core is doing the work of two. To counter act this a bit you should enable touch boosters. I noticed that with my touch boosters set to around 500 mhz CPU1 will use this as its min value and actually scale to the value set in ktweaker as touch booster.

Performance – This idle drain was actually pretty minimal, higher than msm and powersave but not too bad. Response was excellent and phone stayed relatively cool under load. Battery drain during load was not as much as I would expect. Performance and powersave kind of confuse me. You would expect the powersave to save more battery than performance but under load I saved more battery using performance.

This took a while but I hope this helps those who are interested. To summarize, I tested all governors with no adjustments to their settings. This was a baseline/stress/usability test. For those who want to tune and optimize be my guest.

:highfive: