[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Whoa! i'm stoked somebody tried my setup! It's been awhile since i posted that and my setup has probably changed very drastically from that file.

I don't have wifi like i did at school so i'm not as active on XDA anymore. but you guys may have just inspired me to write a thorough post about cool stuff to tweak and play with. I haven't posted in this thread in awhile so i haven't been keeping up with what's going on that much but i wanted to share the fun things i've been playing with.

Mr. jacqstrap this will be a long post but i hope you can try this out and see if it works for you. There's a TL;DR at the end so you can use that if you don't want to read the step by step stuff. Oh and for a day on wifi and data you had pretty decent battery life. i've found variables like location tremendously affect cell reception and battery life. like when i was in kansas on their 4g as opposed to the California Bay Area 4g(which is incredibly bogged down by everyone in the silicon valley) I got fantastic battery life in kansas under same, if not more usage. point is battery life is pretty hard to compare and quantify across devices and locations and usage patterns.

ok here goes.

first things first.

cpu0 = first cpu, the one ktweaker governor tweaks affect.

cpu1 = second cpu, the one you don't get to adjust with ktweaker.

OK so you may or may not have known but when you change a governor or any cpu tweaks you are only affecting one core. Strange right? Not necessarily, the second core uses interactive as it's stock governor. this allows the cpu to scale up to 15xxmhz, or whatever the max is, really rapidly. this helps defeat lots and lots of lag. if you write to the settings file to use ktoonservative as the cpu1 governor instead of interactive you will see the lag i am talking about almost right away.

So what are we to do? if we de-tune cpu0 with very high thresholds and a high sampling rate we can almost effectively make a single core phone. since cpu1 will most likely be running at 1512 most of the time to take the load that could be distributed to cpu0. When i had done all my tuning in the past i was under the impression that both cores ran at the same frequecny, this is not the case. cup0 can be at 81mhz and cpu1 can be at 1512mhz.

You're probably asking which is better? to detune cpu0 with ktweaker which forces almost all the load onto cpu1? or is it better to underclock both and try and distribute the load between the two?

If you want a quick rundown of my setup i have basically a lower frequency dual core that runs pretty close to the same frequency to each other.

Well this is where i need help from you guys, since you are so good at testing. I've been running a very unique setup, which i'll write about in a moment.

I used Script Manager - SManager from the play store and wrote my own script file to write my settings to the files to change cpu1's values.

I also used PerfMon - Performance Monitor from the play store to monitor what both cpu's were doing during my testing and stuff.

my current setup includes

cpu0 = 1296mhz - ktoonservative governor (plus all the threshold and voltage tweaks which will be posted)

cpu1 = 1080mhz - asswax governor

OK now for the instructions for how to fool around with cpu1

Ok so if you use a hotplugging governor you actually can't access the cpu1 folder if the governor has turned the core off and hot plugged it out. for me when I wanted to adjust cpu1's settings i would start a bench marking app to force a load onto both cpu's. This prevents the folder from disappearing.

to fool with cpu1 for testing you can go here, assuming it's not turned off by hotplugging.

/sys/devices/system/cpu/cpu1/cpufreq/

using an appropriate root explorer or terminal or ADB you can write to these files and change them to the values you want to test.

for example, here's what my script runs

echo 1080000 > /sys/devices/system/cpu/cpu1/cpufreq/scaling_max_freq

and

echo asswax > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

​

this only changes the governor and max frequency for cpu1.

You can play around with things and get a feel for how much lag you desire.

ok anyways, so lets say you've played with your settings for awhile but then you realize at some point you will reboot and loose all your settings when KTweaker starts up. ok. so to get around this I wrote my script file and used SManager to run it at boot so it preserves settings across boots.

You can write your own script, or use mine and change the values(assuming you can change them to the correct values). scripts are really pretty simple.

Here's my script https://www.dropbox.com/s/fpzrxfzry5s6cl3/1080mhz-asswax

NOW! before you assume everything is correct and set your phone to boot a script hoping everything is right, you need to test it first!

go download Terminal Emulator for the play store and run the sh command on the script. This will run the script once, and if you somehow make your phone unstable and it reboots all will be well.

so give the terminal emulator superuser permission,

su

ok after that run

sh /sdcard/path/to/your/script/whatever-you-named-the-script

when i run my script i use

sh /sdcard/1080mhz-asswax

it's helpful to have PerfMon running so you can see the change happen.

Ok so now assuming your script works and does what it should(you can always check it with a root explorere) put your script on your SD card and point SManager to it and tell it to run on boot.

SManager can be kind of tricky at first but it is definitely usable, let me know if you have any trouble with this.

NOW

Here's where things get tricky! ktweaker will overwrite your script settings if there is any delay set up on ktweaker. you have to go to ktweaker and tell it to set options on boot. This will prevent ktweaker from overwriting whatever your script does since SManager runs a slight bit later than ktweaker.

Ok guys, i've spent a lot of time writing this, and even longer testing this out, please guys give this a try. it took me quite awhile to figure out a surefire method to make my settings stick. Please let me know how it works out for you guys!

TL;DR

1. cpu1 has some values that aren't affected by ktweaker

2. you can change the values using root explorer, terminal emulator, or scripts

3. here's my script, feel free to make your own or to edit mine https://www.dropbox.com/s/fpzrxfzry5s6cl3/1080mhz-asswax

3a. Here's my ktweaker file (the voltages will likely crash you phone as i have spent like hours tuning them to fit my phone) https://www.dropbox.com/s/sk78has35kf787a/BaconatorXVI's 1296 ktoonservative

4. run the script using sh in terminal emulator

5. once it all works use SManager to run script at boot, also run ktweaker at boot

6. ????

7. Profit

8. Tell BaconatorXVI about your battery life, if it improves or not!

please try this out :laugh: