yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikoal:
I'm still going through the thread, and about 51 pages in.

I have some simple questions....In your opinion which is your top 3 gov/I/O combo for perf and bat life?

Going through the thread people started recommending pegasus with SIO, ktoon w/noop, lulz and bfq, adaptive and deadline, abyss and bfq.

Then later on it went back to ktoonz and noop (near the dec time).

Ktoonsez himself has ktoons and ROW.

Without testing every single settings. I was wondering which are your top 3 that u've had success with.

Also I noticed that once i have another governor / I/O selected for screen off, my phone would boot. I recall reading not to have 2 types of governer selected is that correct? If this is not correct, wouldn't powersave and noop be the best for screen off profile?

i'll continue reading the rest of the pages.... thanlks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
Ok so after some time testing both stock ktoonservative and your settings manually input my finding are:

​

using stock ktoonservative - sampling rate was not automatically adjusted.

​

using manually input values - sampling rate was automagically set to 10000 after minimal use (only playing podcasts with pocket casts and screen off)

I should also mention I'm running the 3/17 nightly PA release from ayysir.

Side Note

Now I'm not sure if this is at all related but I also had issues when attempting to manually set the hispeed_freq on the interactive governor. Is it at all possible that there is an issue with the ktweaker app setting the settings?

Any help is greatly appreciated.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Some parameters like timer rate on interactive are automatically adjusted by the system as part of project butter. I don't believe hispeed_freq was one of them. On sampling rate on ktoonservative I could never figure out why it was always set to 10k, not sure if it has been addressed his thread or not..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
I searched his thread and couldn't find anything. I have seen a few other folks mention this issue in this thread but not sure if anyone ever found a fix or a work around.

The hispeed_freq issue was a little different problem. Once changed the governor would never scale past that frequency and it would continue that behavior until you cleared app data and rebooted.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Here are my personal Ktweaker settings that some users have had success with in terms of performance and battery so try it out if you like and report back with your results. Should you face random reboots try upping the voltages by 25mV across the board.

Locked Frequencies

CPU (MIN): 189mhz

CPU (MAX): 1458mhz

Scheduler: ROW

Scheduler Adjustments:

> hp_swrite_quatum = 5

> rp_swrite_quantum = 4

> rp_write_quantum = 4

Governor: Ktoonservative

Governor Adjustments:

> boost_cpu = 1080

> freq_step = 2

> sampling_rate = 50000

> sampling_rate_min = 10000

> sampling_rate_screen_off = 1000000

Auto Hotplug: Checked

Voltage Table: -50mV across the board

Screen Off Mhz: 189

Screen Off Gov: Same governor

Screen Off Sched: Same scheduler

Battery Level Low: 15

CPU Mhz for low level battery: 1080 mhz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrgnlit:
Just out of curiosity, what is everyone's opinion on undervolting? Some people swear by it and some people say it has so effect of battery life. Is it worth it?

Also I have been trying out the asswax script and I was wondering how much the two scripts are different. I mean besides the fact one seems aggressive and the other is more balanced, do you think there is more benefit to one over the other? I ask this because liltitiz seems to be working more on asswax and not conservative.

One last thing, what is the problem with the sampling rate being automatically set? I have the same setup as bweezy and its the same thing for me. What should the value be if it wasn't auto adjusted?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Read this to gain a better perspective on undervolting

http://xdaforums.com/showthread.php?p=42258652
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Some will say it saves battery, some will say its overrated. IMO if you have a rev0 processor that can take a good amount of undervolting like under 800mv then you can seriously reduce how hot your device gets during normal use, which can save battery life and even extend the life of your hardware.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Yeah I know about this. That is why I keep touch booster enabled, it helps the load to stay on cpu0 instead of making both cpus ramp up quickly and cpu0 is less likely to ramp to its max Freq if you Boost it to like 378-594mhz.i find it is a good balance between disable and 1134. But even if I disable it, my cpu1 rarely ramps up to its max freq.

Imo ktoonservative would need ramp_up_step and ramp_down_step tunables like asswax. So we could make it ramp up slowly but ramp down faster. I think that would help a lot.

On another note, can someone test this for me: try nightmare governor in ktweaker and tell me if it keeps your cpu to its max freq. Nightmare seems to be messed up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrgnlit:
Trying this out now. I have perfmon running and it seems to be working fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Call me crazy but aren't those options already available? Sampling_down_factor reevaluates the load thus taking longer to ramp down so leaving it at 1 should make it ramp down fast enough and increasing freq_step will essentially provide the same function in ramping up slowly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
When I use nightmare my clu0 will never go u der 1674. Well thanks for trying out I'll try to find out why it is acting like this on my device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Ramping down factor is to control the rate at which the kernel will evaluate the load on the cpu to decide if it will ramp down when the cpu is busy. What I'm talking about is a tunable to adjust by how many freq the kernel will make the cpu ramp down after it has made the decision to make the cpu ramp down.

And no. Increasing freq step will make the cpu ramp up faster. Let say you put freq step to 5 and your max freq is 1512, everytime the kernel makes the decision to ramp up, the cpu will ramp up by 5/100*1512. So the higher the freq step, the more it will ramp up/down quickly. So no ktoonservative doesn't offer the option to control separately the ramping up/down logic like asswax does. Don't get me wrong, I'm not saying ktoonservative isn't good enough, it is one of my favorite governor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuigiBull23:
Ah.. gotcha definitely would be interesting to see that tunable implemented.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I am using these values and your undervoltage values, I will report back with battery life within the next 24hours thanks for your work! :good::laugh:

**Going to the performance settings under the settings menu causes a system reboot.**
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cloudyphiz:
Same issue here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cloudyphiz:
Two hours off the charger and >70m screen time with these settings and I was at 85%. Wow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
If you use kt747, it is a known issues that going into performance will crSh the phone( with aokp i dont know about cm10) anyway just use ktweaker you dont need performance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
On my way to 6.66 hrs of screen time :p

Liquidsmooth & kt747 10/9b

Ktoonservative/sio and undervolted -100 all steps. 384 min 1512 max
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
You should try abyssplug, it should give best battery life because it's a hot plug governor that will put one core to sleep most of the times. Others keep both cores on.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
I'll give it a shot

I believe ktoonservative is also a hot plug governor (conservative + hot plugging)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
You're right, I guess they'll be similar.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Tweaked my under volt some more this weekend. Been testing / running smooth all day,

so far

. Gave it a 2 hr. scaling test and some "real world" tests; no reboots so far (*knock on wood*). Battery has been the best I've experienced so far too.

If you try this, remember to make sure you disable "set on boot" so you wont get caught in a loop, if your phone doesn't like the settings. ;)

ROM: AOKP 10-13

Kernel: KT747 AOSP JB 10-9b

Kernel Settings:

Min = 96 Mhz

Max = 1728 Mhz

Governor = ktoonservative (stock adjustments)

I/O Scheduler = deadline (stock adjustments)

Touch Boosters = Stock

Screen Off Profile = 486000

Vibration Strength = 100

Voltages:

1728Mhz = 1080mv

1674Mhz = 1070mv

1512Mhz = 1060mv

1458Mhz = 1040mv

1404Mhz = 1030mv

1350Mhz = 1020mv

1296Mhz = 1010mv

1242Mhz = 1000mv

1188Mhz = 980mv

1134Mhz = 960mv

1080Mhz = 940mv

1026Mhz = 920mv

972Mhz = 900mv

918Mhz = 885mv

864Mhz = 870mv

810Mhz = 855mv

756Mhz = 840mv

702Mhz = 825mv

648Mhz = 810mv

594Mhz = 800mv

540Mhz = 790mv

486Mhz = 780mv

384Mhz = 770mv

192Mhz = 760mv

144Mhz = 750mv

96Mhz = 740mv

Hope this helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Thanks for this; helped my phone alot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Oh man I just setup liltitiz's configuration; would you say this configuration works better? Also why are you not scaling up to 2Ghz? Thanks :fingers-crossed:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
Probably to save battery

With all (most) of the aosp ROMs being updated to 4.1.2, everything's so buttery smooth I can't see a reason to over clock anymore
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
I have no idea which would work better, each device is specific. Try each one for a day and see.

As far as why i don't OC to 2 GHz... b/c i don't want to.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I would overclock my toaster if i could! Every reason ils good to overclock :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
The way I see it, his settings are more for overall battery life so if you want you battery charge to last longer take this. Mine are a good in between, consume near to none power on idle. But still very smooth because it unlock the second core when needed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wired_In:
Does anyone have weird crackling audio if you go below 900 at 96?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Many reports of it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mobilehavoc:
Abyssplug for first half of battery and then ktoonservative for the second. I might go back to abyssplug but this is good for me.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Heisenberg420:
I tried liltitz's abyssplug/bfq settings this morning and I got 45 min of screen time and a few voice calls out of just 10% battery. Pretty impressive! I did notice some lag during the CRT animation and some other window transition (visual effects) but nothing major.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enomi:
this **** is so complicated..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
To all of you who tried my asswax settings on cpu1 if you wanna adjust asswax for your needs, check this http://pastebin.com/UwA8swVv
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikoal:
liltitiz i was wondering what kind of results were you getting wiht the new CPU1 settings compared to your latest settings here http://xdaforums.com/showpost.php?p=39691543&postcount=972

I tried applying your settings wihtout any OC or UV, and i dont really notice that much of energy savings.

Is there anything else I can do to further conserve energy? so far i feel no lag or reduction in performance.

thanks!

EDIT:

Also i was wondering how the min freq interacts with the screen off frequency.

I had the min freq at 189mhz and its stable, but my tethering wouldn't work at times. so i changed my off screen to 384mhz so the tether still works....but does that cancel out the 189mhz from ever activating?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Yeah I undervolt so the BaconatorXVI's fingers don't get cooked! My chip gets so hot!

Sent from a Galaxy far far away...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikoal:
Hi Bacon,

I came across this little piece here http://xdaforums.com/showpost.php?p=34153152&postcount=15576, what do you think?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
With my new settings I can get up to 5-6 hour of screen on with a discharging time of around 24 hours. Before I start playing with cpu1, I couldn't get more than 4hours of screen on with a discharging time around 15hours since the Linux 3.4 kernel

Note that I also use greening to hibernate apps and Tasker to turn on things like gps, data, wifi, auto rotate only when I need them.

I readjusted my settings yesterday to test something out if you got no loss in performance yet you can try them out:

Ktoonservative setup to input in ktweaker:

Boost 2nd core on button:0

Boost cpu:540

Boost gpu: doesn't matter

Boost hold cycle :0

Boost turn on 2nd core:0

Cpu down block cycle:0

Down threshold:75

Down threshold hotplug:60

Freq step:3

Ignore nice load:0

No 2nd cpu screen off:1

Sampling down factor:3

Sampling rate: 25000

Sampling rate screen off: 45000

Up threshold:94

Up threshold hotplug:96

---------------------------------------------------

Command lines to apply my asswax settings on cpu1 :

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

echo 135000 > /sys/devices/system/cpu/cpufreq/asswax/awake_ideal_freq

echo 200 > /sys/devices/system/cpu/cpufreq/asswax/down_rate_us

echo 189000 > /sys/devices/system/cpu/cpufreq/asswax/interactive_ideal_freq

echo 95 > /sys/devices/system/cpu/cpufreq/asswax/max_cpu_load

echo 65 > /sys/devices/system/cpu/cpufreq/asswax/min_cpu_load

echo 250000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_down_step

echo 50000 > /sys/devices/system/cpu/cpufreq/asswax/ramp_up_step

echo 81000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_ideal_freq

echo 135000 > /sys/devices/system/cpu/cpufreq/asswax/sleep_wakeup_freq

echo 5000 > /sys/devices/system/cpu/cpufreq/asswax/up_rate_us

---------------------------------------------------

If you set your ktoonservative to turn off 2nd core(cpu1) when screen is off, then it doesn't matter because your cpu1.will be off so only your ktoonservative(cpu0) settings matter. Personally I use 486 as my max freq when screen is off.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
Every time I run the script, my phone reboots within 10 seconds of running it. Is there a log I could get to help you see what the problem is?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Are you also running my ktoonservative settings? Maybe your cpu just don't handle such load on his lower freqs(81-189) just try to raise your min freq and don't forget to adjust awake ideal freq, sleep ideal freq and sleep wakeup freq in the script to match your new min freq. You could also try raising your voltage
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikoal:
With your settings before messing with CPU1, I had 1.5 hours of on screen time with a total of 5 hours of battery life and it hit 1%.

i was also tethering for an hour or so with the screen off.

Do you have any suggestiosn? or is this "good time"

i dont want to do CPU1 mods just yet......

oh also to add, i didnt OC or UV either......
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Only you can judge if this is good time for your device. Are you are you running 378-1512 or 81-1512?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikoal:
Well from my experiences its about typical to have constant usage of the phone to be around this time.

However I want to say maybe its a bit worse than my ondemand cfq. But I could be wrong.

What is 378-1512? or 81-1512

I'm on 4.1.1 stock TW with V6 supercharged script on 5/31 kt747 with your ktoonservative settings. I even changed it to noop hoping for better battery life. but no go.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
81mhz-1512mhz or 378mhz-1512mhz you min/max frquencies
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikoal:
was at 378 then lowered to 189
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] frazbox:
These settings are the bomb! I'm using them but overclocking to 1890!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Is it working now?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jbreeze905:
sampling_rate 10000?

My sampling_rate in ktoonservative governor adjustments keeps setting itself to 10000... it seems to be the only setting that changes on it's own.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bweezy21:
I'm still trying to figure this out. For now it's keeping me from running any of these test settings that have been posted. The 10K sample rate causes my phone to run at max frequency for way too long and I get lots of heat related reboots...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikoal:
I'm still draining like normal....is there any advice on improving bat life with settings?

I am still sticking with the CPU0 ktweaks.

I also noticed that my ktoonserative likes noop and lags on sio, row etc.

Finally......wouldnt screen off profile of power save and noop be the best?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] danesusername:
I've been having rom troubles, so I haven't had a chance to try and figure it out. After I switch to a solid rom I'll give it a try again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
If you get massive battery drain there is no settings that are gonna stop the draining. You will have to figure out what is draining your battery and fix the problem yourself. You can use better battery stats or wake lock detectors to help you with that. Applying my script on cpu1 could also improve your battery life. Greenify and Tasker can also help you get the best out of your phone

If your device works best with noop then stick with it.

All power save does is setting your min frequency as your max frequency. So i wouldn't use it at all. Just stick with ktoonservative and set your max screen off frequency to 486mhz or something around that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikoal:
It's not massive.........well.........at least i dont think it is.......

It lasts about 5 hours with screen brightness to the max and about 1.5 hours of on screen time. Sometimes with tether and constant net surfing.

Checking BBS, theres nothing special or out of the orfinary. I already renamed all the files that needs to be renamed that causes battery drain.

I dont have really that many wakelocks......but im not complaining about my sleep battery consumption, but more of the on screen time.

My next step would be off screen time......

I already got greenify on........ i was wondering if theres a setting that most would agree is good for batteries (with, and without uv) that is a step above powersave's slow performance.

What happens when screen off freq is 486mhz and powersave is on? which frequency takes precedence?

But if powersave throttles the frequency, why not use it for off screen? What can ktoon + off screen freq of 486 do thats better than that for saving battery life?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
Using ktoonservative while screen off will keep the same scaling logic intended for good battery/performance balance but will max my cpu to486mhz so my cpu can scale from 81mhz to 486mhz. If I used power save, my cpu would only use 81mhz.

There is not much left to try beside under volt, other governors\schedulers or governor settings. Using my asswax settings for cpu1 could also help you out with that. But I do not have your device so it is hard for me to tell you exactly what will work best for you.

Even with max brightness 1.5hr screen on and 5hrs charge is not that good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikoal:
liltitiz, regarding OC and UV, have you seen this http://xdaforums.com/showpost.php?p=34153152&postcount=15576

So in my case with screen off, would it only be limited to my lowest frequency? the max screen off frequency is ignored?

hmmm.... with max screen brightness.......what would considered a above avg batter life (in your experience) for screen time with toital time?

thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] liltitiz:
I think this is just the technical way of explaining the fact that no chips are the same so some will under volt more than others and so will not over\under clock as much as others.

For the don't overclock/under volt part, it is his opinion on the subject, I wouldn't agree with him on this since I've notice less heat and no loss in stability with my under volt table and 81-1890mhz. In my opinion you need to know the limitation of your chip to find how to get the best out of it.

With 1.5 hour screen on I would expect minimum 10hrs of discharge
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikoal:
just as an example

i ran my phone for about 16 mins, 70% was from screen, screen on time was about 12 min and it dropped 8%.....

could there be something wrong here?

BBS shows powermanager service on for 2 mins

cpu states were on 189mhz(7min), 972mhz (2min), 1.51 (2min), 1.67mhz(2min)....i did overclock it slightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Mikoal, my biggest suggestion to you for better battery life would be to get off the stock Rom.

If you got the time, it's definitely worth making a nandroid backup in recovery and flashing the slimbean weekly build 6.5, or whatever is most recen. In my opinion this is the most stable fast and smooth Rom. Trust me, this Rom is better than all the touch wiz gimmicky features.

Seriously, this will be one if the better decisions you make. If you're worried about messing something up you have more chance of screwing up with the script files for cpu1 than you do flashing a fantastic Rom .zip

I've gotten the best battery life I've ever had on this Rom

Oh and in regards to the guy taking about undervolting yes he knows his stuff about how a cpu works but his explanation still doesn't account for the major heat reduction I experienced. I had a difference of like ten degrees C during a benchmark which is huge between stock and way undervolted. If you are willing to test each of the many frequencies for stability(which I do) and tweak each step's corresponding voltage to reach a point where you have a stable, cool, and possibly more energy efficient phone then I see no reason to not undervolt.

---------- Post added at 02:05 PM ---------- Previous post was at 01:20 PM ----------

Also I was going to add, my biggest battery saver has been hitting the mobile data toggle whenever I don't need data. It makes for massive savings for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] baconatorXVI:
Ok also I've got about 13+ hours of uptime, 1 hour 40 minutes of screen time and about 34% battery left. Hitting that data toggle and my cpu1 settings make a massive difference for me personally
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TimeAndroid:
Hi, I have a Bell Samsung Galaxy S3 SGH-I747M and would like a suggestion for settings that balance battery with performance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
I think I may have shared these with you before. But these always worked well for me.

https://www.box.com/s/6jsfkpiywux9bgvuapac