Has anyone done any actual benchmarking to decide what the best value to set scaling_governor to is?
I just rooted today and I'm using Fresh 1.1, which has /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor set to ondemand.
Just wondering of the available options, msm7k userspace ondemand performance, which is the best? I'm more concerned with battery life, because I'm assuming that when the screen is on the scaling_governor setting won't matter all that much, so which is better for battery life, msm7k or ondemand?
ASULutzy said:
Has anyone done any actual benchmarking to decide what the best value to set scaling_governor to is?
I just rooted today and I'm using Fresh 1.1, which has /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor set to ondemand.
Just wondering of the available options, msm7k userspace ondemand performance, which is the best? I'm more concerned with battery life, because I'm assuming that when the screen is on the scaling_governor setting won't matter all that much, so which is better for battery life, msm7k or ondemand?
Click to expand...
Click to collapse
ondemand is just the default setting, so you won't get any different battery life. if you use powersaver, you'll obviously get the most battery life but your performance will probably suck. i think msm7k is the best if you want more battery life than performance, but still not have it go super slow. msm7k stays at the lower clocks more, at least i've noticed. i think gbhil mentions in his kernel post that msm7k gives good battery life.
i've also tried it too; i think my battery life went up quite a bit actually.
From what I've heard, msm7k gives the best battery life+performance combination, and it's the governor that came shipping on the phone. It's based on the "conservative" governor, which means it'll stay low until it absolutely needs more processing power, and then it'll ramp up gradually. ondemand will ramp up a lot faster.
I'm not a big OC guy, so I'm perfectly content with what the engineers decided was best, on that front. So that's my recommendation (msm7k).
How do I alter the scaling governer file. I tried doing it with file explorer, and it failed, then I tried coping it to the sd card altered it succesfully, but then I could not copy it back anyone have some instructions, thanks
I just simply did
echo "msm7k" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Related
Hi there,
I'd like to overclock my IncS to 1,3 Ghz...
But I don't know the right settings.
Can you please tell me the right setting for best performance (e.g. oc to 1,3ghz) and best battery life?
thanks
does anybody know?
Set max to your desired, min to the lowest it will go and scaling to smartass.
I'm OCd to over 1.4 and no issues... UCd to 192 with smartassv2 governor
Sent from my Incredible S using XDA App
the best performance I have experienced in my INC is when I put oc / uv beater to the following:
wake gov: ondemand
wake mins: 245000
wake max: 1228800
Sleep gov: Conservative
my sleep: 245000
Sleep max: 691200
when I take a test in antutu nenchmark for I the following result.
score: 2729
If I clocked lower or higher, the result is lower
Overclocking depends entirely on your chip.
You should use whatever governor suits your needs.
I personally use ondemandx which speeds up on demand (as the name implies), conservative tries to keep the frequency as low as possible, interactive uses max frequency if min isn't enough, smartass is an improvement of interactive that keeps performance high while improving battery life (meaning there's little reason to use interactive).
You can find it in more detail here.
So basically, smartass if you want performance, conservative if you want battery life, ondemand if you want something in between. In reality though, I don't think you'll see much difference between them and I've seen no difference in idle power draws, so if you don't use your phone all that much, they won't be that different.
Once you've picked a governor, you should set min speed to 122000 (no reason to use any higher) and max to whatever you want. Your phone will probably crash or suffer from bad performance if you go over 1.5 GHz, but it varies a lot. Might happen even earlier.
Once you've found your desired performance level, you should start tweaking your voltages. You can do that under the UV profile. In there, you can adjust voltages at different speeds and the phone will automatically use them at whatever speed it's at. You should undervolt to increase battery life, so start by reducing all by 25 or 50 and then temp apply. Use it like that for a couple of hours and if it doesn't freeze, you're probably stable. You can either stop here or spend many hours tweaking it further, but that'll take many hours to get right.
This is my setting
Sent from my HTC Incredible S using xda premium
Which would be the best O/C program out there ?! I have SetCPU, Daemon but I'm sure there is better in the market...... just need to know the name so I can get it Thanks!
I'm currently 230MIN/1150MAX
Me4oKyX said:
Which would be the best O/C program out there ?! I have SetCPU, Daemon but I'm sure there is better in the market...... just need to know the name so I can get it Thanks!
I'm currently 230MIN/1150MAX
Click to expand...
Click to collapse
In my opinion, and I'm sure many others', Virtuous daemon is the best by far.
It comes standard in a lot of roms, and using the OC/UV beater
http://forum.xda-developers.com/showthread.php?t=1207546
it would have the best performance. I've set mine similar to yours and with this method, you can set the phone to underclock when battery reaches a low level
Ever since I flashed the 213 leak, battery life has been a bit disappointing. To help things along, I downloaded SetCPU (haven't used it since my good ole OG Droid) and let it autodetect settings. To my surprise the governor was set to 'interactive' instead of hotplug like it was on stock GB.
My understanding is that hotplug allows the phone to disable unneeded cores during periods of low utilization, while interactive does not (although both cores can be disabled when the phone is sleeping). Do you think switching to hotplug from interactive will improve battery life?
My battery life is much better since switching, but I also disabled 4G (on WiFi most of the time) and added screen off and low battery profiles (600mhz and 800mhz max respectively) which muddy the waters a bit. I thought I would mention it on here for those of you who feel the same, it might be an easy way to improve battery life on the leak.
That's interesting. I've been using the .213 leak and my battery life has been quite good. I haven't noticed any particular drop in battery life, and I keep 4G on all the time. If I don't use my phone much, it's not uncommon for me to have 60% left at the end of the day.
Do you use anything like SetCPU? I am wondering whether I can confirm that the default governor of the leak does not shut off one of the CPUs when it is idle. If nobody can confirm I'll get around to checking it myself this weekend :laugh:
Sorry, I haven't messed with my cpu settings.
I'm sorry, but i have already searched the foruns and i did not found any explicit answer, so here it goes.
I recently moved to Zeus v6.39 ROM and i would like to understand how the zeustweak works. I mean, in order to get battery life, should i raise up the CPU frequency (and how much is it safe to raise) and lower the voltage (and, again untill what value may i do it), isn't it so? Assuming i do it, which would be the consequences for my phone?
Thanks
P.S. - is there any way of changing the receiving/making call screen layout?
Don't change, just leave default 0
99% people of Zeus 6.39 getting best battery life. I am also using with same tweak.
Press THANKS button if helped..
The cpu frequency is the amount of calculations per second that the cpu can process so theoretically, the higher the frequency, the faster the ROM will respond. In actual fact the cpu frequency also determines how stable the ROM is and the higher you clock your processor, the more unstable it may be and the more battery it will use.
I would recommend for ultimate stability to leave it at 1000MHz but for negligible performance improvements max could be up to 1350MHz but the difference is minute.
Correct me if I'm wrong but the voltage tweak is the aggressiveness of the governor when ramping the cpu up or down (changing the frequency). The values below 0 indicate that the governor will ramp down the frequency which in turn saves battery life. Values above 0 will make the governor ramp down less aggressively and thereby increase ROM responsiveness and noticeable lag spikes but reduce battery life.
I hope that helps but don't quote me on it.
Sent from my LG-P970 using Tapatalk 2
In my test voltage tweaks works. If I set -7 i could watch the youtube for 4 hours, but when I set 0 I watched only 3 hours continuously. Someone do a test and measure power consumption on charger. With -7 drains about 30% less battery.
Sorry for bad english.
im just wondering how much does the governerr effect battary life? i changed from ondemand to smartass2 and im not sure i see any diffrent...
and im scheduales which one is best for multitasking and which is for when playing games?
and should i change the governerr setting?
i also read that sleep_ideal_frequency should be 200 and not 100 beacuse 100 wastes more or something like that, is that true?
using galaxy i9000 semaphore kernal jb
bump
I use Performance governor all the time for 3 months now, battery life is same as on demand, smartass v2 or any other governor, except my phone lags much rarely than on any other govenor. For those that dont know, CPU of PC, your phone, calculator or anything else always works at 100% of its frequency even it has no work to do (Let's take for example your PC, even cpu usage is 5%, CPU still works at full frequency, the same works for your phone), so to me there is no point of any other governor except for Performance. If you have problem with battery life, it's mostly your screen. When I drain out my battery, my battery mostly get drained by screen (70-90%), I use about 0-30% of brightness always. Screen of 60-100% brightness will probably drain your phone's battery in 2-3 hours.
Lavoslav said:
I use Performance governor all the time for 3 months now, battery life is same as on demand, smartass v2 or any other governor, except my phone lags much rarely than on any other govenor. For those that dont know, CPU of PC, your phone, calculator or anything else always works at 100% of its frequency even it has no work to do (Let's take for example your PC, even cpu usage is 5%, CPU still works at full frequency, the same works for your phone), so to me there is no point of any other governor except for Performance. If you have problem with battery life, it's mostly your screen. When I drain out my battery, my battery mostly get drained by screen (70-90%), I use about 0-30% of brightness always. Screen of 60-100% brightness will probably drain your phone's battery in 2-3 hours.
Click to expand...
Click to collapse
This is so wrong its a pain to read.:banghead: Why do we have the max and min frequency options in the semaphore app? Why do we have "Max Performance" and "Max Battery" power settings on laptops?
Sent from my GT-I9000
There was a thread some while ago that concluded in OnDemand and Performance being to two to give longest battery life and best performance.
I don't have specifics or even a link, but the thread was about schedulers and governors and which went together for best performance and battery life. I'm sure it's google'able
Sent from my GT-I9000 using xda premium
i found that thread but im just wondering how much battary life is wasted if i prefer preformence?
lets say i use smarassv2 since its faster will my phone drain lets say insted 20%\hour - 22%\hour? or is it more then that?
itzikd1 said:
i found that thread but im just wondering how much battary life is wasted if i prefer preformence?
lets say i use smarassv2 since its faster will my phone drain lets say insted 20%\hour - 22%\hour? or is it more then that?
Click to expand...
Click to collapse
maybe you can try and tell us
There should be a significant impact regarding battery life when using Performance for example. But it also depends on what you are used to. If you play games all the time or do heavy tasks, the governor will kick the CPU to 100% all the time anyway. But if you mostly surf on the Internet or read texts there's no need to let the CPU go rampage.
Oh and Btw: Modern CPUs in notebooks or computers in general clock themselves down as well when they're idle.
Sent from my Gameboy Color
BlueFlame4 said:
There should be a significant impact regarding battery life when using Performance for example. But it also depends on what you are used to. If you play games all the time or do heavy tasks, the governor will kick the CPU to 100% all the time anyway. But if you mostly surf on the Internet or read texts there's no need to let the CPU go rampage.
Oh and Btw: Modern CPUs in notebooks or computers in general clock themselves down as well when they're idle.
Sent from my Gameboy Color
Click to expand...
Click to collapse
I do use internet mostly so what will be the most effective governerr any idea?
itzikd1 said:
I do use internet mostly so what will be the most effective governerr any idea?
Click to expand...
Click to collapse
Try OnDemand or SmartAssV2.
Hi,
So, I was wondering if anyone had any experiences with this governor on FroyoPro v2.5. Having experimented with basically everything there is on the phone, this is one of the last things I would like to try.
Currently I'm using 245MHz-600MHz ondemand governor, and was experimenting a bit with the performance one. I loved how performance worked, but I did notice some adverse effect on battery life (somewhat 30% lower), so I switched back.
What I would like to have is a somewhat snappier phone without sacrificing the battery too much. Performance governor, after all, took a too big of a chunk of the battery for me to handle.
What are your opinions/experiences with this governor? Also, is it v1 or v2 that is included in FroyoPro?
Well, I tried it today.
At times it worked okay, but most of the time there was lag.
AnTuTu score dropped a spectacular 1000 points.
Quadrant score dropped 100 points.
Naturally there is possibility that I perhaps did something wrong. However I followed the instructions correctly. Perhaps it would work better on some other device, but mine apparently doesn't like it.
Back to ondemand then
U should use smastass its good both with battery life and performance...
sent from my phone using hands and brain...
dagger said:
U should use smastass its good both with battery life and performance...
sent from my phone using hands and brain...
Click to expand...
Click to collapse
But the performance was horrible! Is there something else I should do besides insmod and echoing to activate it? Perhaps tweaking with its parameters a bit? Because ondemand currently appears to be a much better choice for my device.
xWhiskey said:
But the performance was horrible! Is there something else I should do besides insmod and echoing to activate it? Perhaps tweaking with its parameters a bit? Because ondemand currently appears to be a much better choice for my device.
Click to expand...
Click to collapse
Try adding these settings in hw_config.sh:
Code:
echo 12000 > /sys/devices/system/cpu/cpu0/cpufreq/smartass/up_rate_us
echo 60000 > /sys/devices/system/cpu/cpu0/cpufreq/smartass/down_rate_us
echo 999999 > /sys/devices/system/cpu/cpu0/cpufreq/smartass/ramp_up_step
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/smartass/ramp_down_step
And just to be completely sure that everything is in place, the other required lines should look like these:
Code:
insmod /system/lib/modules/ax8_smartass.ko
echo "smartass" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Fortun said:
Try adding these settings in hw_config.sh:
Code:
echo 12000 > /sys/devices/system/cpu/cpu0/cpufreq/smartass/up_rate_us
echo 60000 > /sys/devices/system/cpu/cpu0/cpufreq/smartass/down_rate_us
echo 999999 > /sys/devices/system/cpu/cpu0/cpufreq/smartass/ramp_up_step
echo 0 > /sys/devices/system/cpu/cpu0/cpufreq/smartass/ramp_down_step
And just to be completely sure that everything is in place, the other required lines should look like these:
Code:
insmod /system/lib/modules/ax8_smartass.ko
echo "smartass" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
Click to expand...
Click to collapse
Ok. I edited all of this in so we'll see how it goes through the day. Will report back in a day or two.
If the performance is horrible with smartass v2 then ate the min frequency to a little higher value...
I suggest 245 or 320...
Then report here..
sent from my phone using hands and brain...
Tried both of your methods. It seems that with Fortun's parameter changes and by ramping up the minimum frequency a notch the governor was a bit more stable. However, there was still lag. Not constant, but in spikes. The battery might have been a bit more durable in this run, but not that much more durable taking into account the performance issues I've been having. You could see frequent spikes in games, while surfing the internet, sometimes even on the UI. IMHO the ondemand governor seems what works best for this device. I might give this governor a shot in the near future again, but for now he'll be asleep.
I'm not into kernels that much, since I cannot unlock the bootloader for free without risking a hardbrick, but might it be possible that stock kernels react badly to things like this? I mean, this governor doesn't work that well, the overclock module slows down the phone, minfree setting changes don't stick. Do you guys run stock or custom kernels?
I use custom kernel...
Btw what's your phone's manufacturing date...
sent from my phone using hands and brain...
dagger said:
I use custom kernel...
Btw what's your phone's manufacturing date...
sent from my phone using hands and brain...
Click to expand...
Click to collapse
11w39, and if I remember correctly, you can unlock safely only until 11w28. I would most certainly attempt to unlock the bootloader and flash a custom kernel if that wouldn't have been an issue. But it's no big deal. I'm liking the device so far. Much better than stock now.
Also, I have a question related to governors. When I reboot, and for example echo the ondemand governor to the scaling governor, do its parameters reset to default? Or do I have to echo the custom parameters for the governor at every boot?
Are you completely sure that the lags dissapear when using ondemand as opposed to smartass? The X8 over here is running with the settings I suggested on stock kernel, it's heavily used for gaming and no problems with the performance.
By the way, the smartass governor from the module is different from the version found in the custom kernels. Then it should be treated differently.
As for your last question, I'm not sure I get it. Anyway, the values set in hw_config.sh are loaded each time the phone boots.
Fortun said:
Are you completely sure that the lags dissapear when using ondemand as opposed to smartass? The X8 over here is running with the settings I suggested on stock kernel, it's heavily used for gaming and no problems with the performance.
By the way, the smartass governor from the module is different from the version found in the custom kernels. Then it should be treated differently.
As for your last question, I'm not sure I get it. Anyway, the values set in hw_config.sh are loaded each time the phone boots.
Click to expand...
Click to collapse
Absolutely. The problems disappeared just after I applied ondemand as the governor. I'm not sure which ROM are you running, but it seems to me most of these things don't quite work that well on mine. None of the modules I applied so far didn't work well.
I was referring to governor parameters. Sampling rate, down differential and the like. Do they return to their default states when the phone is rebooted (assuming I didn't echo anything to their parameters in hw_config)? If I was, for example, change their parameters while the phone is running, does that change stick permanently or does it reset at reboot? I'm asking this because I would try to experiment with SetCPU and parameter tweaks while the phone is running.
Running a slightly modified version of the latest GingerDX right now. Could you post the name of the game that can replicate the lags?
And, yes. The parameters reset at each boot if not put directly in hw_config.sh (not the only where you can put them). And for good reason. If you configure it badly you could be put in a situation where you enter a bootloop (specially true when overclocking). Don't ever commit to some changes before testing stability.
By the way, SetCPU has an option to load settings at boot if those settings are set using the program. In other words, if you choose to set the settings using the echo parameter with the terminal, for instance; these settings will be reset next time you reboot the phone.
Fortun said:
Running a slightly modified version of the latest GingerDX right now. Could you post the name of the game that can replicate the lags?
And, yes. The parameters reset at each boot if not put directly in hw_config.sh (not the only where you can put them). And for good reason. If you configure it badly you could be put in a situation where you enter a bootloop (specially true when overclocking). Don't ever commit to some changes before testing stability.
By the way, SetCPU has an option to load settings at boot if those settings are set using the program. In other words, if you choose to set the settings using the echo parameter with the terminal, for instance; these settings will be reset next time you reboot the phone.
Click to expand...
Click to collapse
The launcher is ADW. I playtested the governor on Tilt Arena, Missile Defense, Racing Moto, Radio Ball 3D. At normal circumstances, RMoto lags here and there, but with smartass it was unplayable. Tilt Arena usually has a spike here and there, but also unplayable with smartass. RBall worked ok, but usually worked flawlessly. Missile Defense tends to slow down when the cpu stress is high, but smartass didn't do much to help.
OK. Tried with Racing Moto and no problems with it. For the sake of completion I tried playing it with the CPU clock capped at 320 MHz and still no problems.
Something looks definitely wrong. Maybe you should try getting the smartass module from the original thread: http://forum.xda-developers.com/showthread.php?t=1159899 .
Maybe you could post the whole contents of you hw_config.sh to take a look at it.
Fortun said:
OK. Tried with Racing Moto and no problems with it. For the sake of completion I tried playing it with the CPU clock capped at 320 MHz and still no problems.
Something looks definitely wrong. Maybe you should try getting the smartass module from the original thread: http://forum.xda-developers.com/showthread.php?t=1159899 .
Maybe you could post the whole contents of you hw_config.sh to take a look at it.
Click to expand...
Click to collapse
I'll try that. But I won't bother you further with the hw_config.sh What you've done so far was enough, and I'm thankful. Over the course of the next few days I'll try the smartass module from the original thread. For some reason, there's a 50KB size difference between the two.
Thanks for your help.
Tried the smartass governor again today, and played with its parameters a bit. It seems it works ok for a while (about 3-4) hours, but then it screws everything up. UI starts lagging, games become unplayable, some apps start force closing, etc. It's a shame because I really wanted it to work, especially after investing so much time into it.
However, taking this post into account:
http://forum.xda-developers.com/showthread.php?t=1369817
... and the tweaks posted there, I made some tweaks to the ondemand governor. Here they are:
echo "60" > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo "100000" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_rate
echo "4" > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor
echo "15" > /sys/devices/system/cpu/cpufreq/ondemand/down_differential
echo "50" > /sys/devices/system/cpu/cpufreq/ondemand/freq_step
CPU is clocked at 245/600, stock kernel. I've noticed that with these parameters AnTuTu scores drop about 100 points, but the results are VERY consistent. They don't oscilate in a ~400 point interval anymore. Also, games are very stable, only with very minor lags here and there on some harder games. Battery seems more or less the same. I might theoretically get 2-3 hours less, but that's hard to quantify at this point. Wake-up speed is also very good.
Could anyone try these out and see how it goes? Perhaps we could conjure up even better settings?
EDIT: Also, interesting thing to note is that setCPU shows about 40% time on 245MHz, 54% on 600MHz, and the rest on in-between freqs. However, I don't think the app recognizes deep sleep states, which means these frequency percentages are used only when the phone is active, which is great! If you look at it, it also makes perfect sense. When CPU reaches 60% of load, frequency is ramped up. However, one freq step is 50% of the max = 300MHz, and because the system uses round-up states, frequency jumps from 245MHz to 600MHz instantly, spending time on in-between frequencies only when ramping down.
Also, I've read somewhere that having a CPU set on e.g. 245MHz on full load is much worse for battery saving than having it set on e.g. 600MHz until it is done working, and then ramp down to min. These settings might actually be a bit beneficial for the battery.
EDIT2: CPU Spy recognizes sleep states, which are at 86% of the time.
Stock Kernel:
Smartassv2 Min CPU freq 245 Max 729
Custom:
Smartassv2 min cpu freq 480 max 768.
Sent from my iPhone using Tapatalk