Just curious out there on what everybody is running their CPU frequency, governor, and such, Just looking to see all my options and how I can save battery and increase performance
You won't decide anything until you try. The freq and other settings are highly subjective. As per my usage, i can even survive on 1497Mhz and the phone would still feel buttery smooth, but i use 19xx Mhz step. GPU at 389Mhz. Using default SAOSP kernel with alucard governor + hotplug and the system is performing like a nexus device.
Related
Well, a few friends of mine with Sensations asked me "What are all these SetCPU options for?" So, here's some explanations.
CPU Scaling Governors
CPU governors control exactly how the CPU scales between your “max” and “min” set frequencies.
Ondemand- When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
Interactive- The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
Conservative- It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
Performance- It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
Powersave- Keeps the CPU running at the “min” set value at all times. userspace –A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
Smartass- is based on the concept of the interactive governor. I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies. Smartass will also cap the max frequency when sleeping to 192Mhz (or if your min frequency is higher than 192 - why?! - it will cap it to your min frequency). No need for sleep profiles any more!
CREDIT: http://setcpu.com/#7 & http://forum.xda-developers.com/showpost.php?p=9277771&postcount=2
NikolaiT said:
Well, a few friends of mine with Sensations asked me "What are all these SetCPU options for?" So, here's some explanations.
CPU Scaling Governors
CPU governors control exactly how the CPU scales between your “max” and “min” set frequencies.
Ondemand- When the CPU load reaches a certain point (see “up threshold” in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
Interactive- The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
Conservative- It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
Performance- It will keep the CPU running at the “max” set value at all times. This is a bit more efficient than simply setting “max” and “min” to the same value and using ondemand because the system will not waste resources scanning for CPU load.
Powersave- Keeps the CPU running at the “min” set value at all times. userspace –A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
Smartass- is based on the concept of the interactive governor. I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies. Smartass will also cap the max frequency when sleeping to 192Mhz (or if your min frequency is higher than 192 - why?! - it will cap it to your min frequency). No need for sleep profiles any more!
CREDIT: http://setcpu.com/#7 & http://forum.xda-developers.com/showpost.php?p=9277771&postcount=2
Click to expand...
Click to collapse
The s
Sent from my HTC Glacier using XDA Premium App
So which one would you recommend?
thebigham said:
So which one would you recommend?
Click to expand...
Click to collapse
Smartass, its the best governor, but it hasn't been implemented in any Sensation kernels yet, hopefully Lee or maybe Mike1986 can implement it into their kernels in the future.
Interactive for a good balance of responsiveness and battery life.
Conservative if you're looking for better battery at the expense of responsiveness.
Sent from my HTC Sensation 4G using XDA App
question... I see all the govener setting in ns tools, setcpu, ect.... just wondering something.... What setting is.used in factory otu roms? lets say a.unrooted nexus s, what is.it natively set at? 100/1000 ? and ondamand? or is.it 1000/1000?
Sent from my Nexus S 4G using XDA App
100/1000 ondemand is the default.... but I always change it to 200/1000 smartassv2 it works best for my phone
Sent from my Nexus S 4G using xda premium
I usually use "ondemand", it seems to work best. Once I decided to try "powersave" and my phone slowed down to a crawl, pretty much unusable. I don't know what that was about, but I definitely don't recommend it...
Jabaculemos said:
I usually use "ondemand", it seems to work best. Once I decided to try "powersave" and my phone slowed down to a crawl, pretty much unusable. I don't know what that was about, but I definitely don't recommend it...
Click to expand...
Click to collapse
Powersave limits the cpu to the absolute lowest frequency at all times. It is not usable for normal operations, except for Setcpu screen-off profiles.
Performance governor is the opposite ; it keeps the cpu running at max frequency (1ghz with stock kernel) and is useful only for speed benchmarks.
The other linux kernel governors are described in detail in numerous threads... All you have to do is search "kernel governor ".
My personal choice is smartassv2 since it's responsive, efficient with battery consumption, and features a screen-off sleep profile.
Ezekeel recommended me lazy with proof screenshots
Governors control how the CPU frequency adjusts. They work like this:
Ondemand: Starts at a low frequency and when there is any CPU activity it uses max frequency. It goes back to low over time.
Conservative: Like ondemand, but instead of using max frequency on CPU activity it uses the next step. It's less responsive than ondemand since it goes like: "100% CPU > Higher Freq. > 100% CPU > Higher Freq..." instead of "100% CPU > Max Freq."
Lazy: Like ondemand but there is a small delay between frequency changes. I use this one.
Performance: Max frequency all time.
Powersave: Min frequency all time.
Interactive: This is a bit complex, actually it's sampling the CPU usage and trying to predict what will come up (I think).
Smartass: It's like interactive, but rewritten. It should give better results.
Default is ondemand 100/1000 and it works pretty good.
Hope I helped.
i use setcpu (and i believe i actually bought the donate version)...but lately, i've been seeing people recommended against using setcpu.
any reasoning for this? and what is the preferred alternative?
Sent from my Transformer TF101 using Tapatalk
I've used SetCPU since my phone. Work fine for me, no problems.
If it's working good for you don't worry too much
^what he said.
setCPU works fine for me too. I use it to change cpu speed when I am doing benchmarks and I haven't seen anything that indicates setCPU isn't working correctly.
I will say though, that I can OC my TF and I can't really notice a difference from just running at 1 GHZ...But I do see a difference in battery life.
So bottom line, I just leave it at stock speed and enjoy.
I use Systune app (also, lets you modify "nice" settings, io, etc), advanced test's over SetCpu demonstrated it's not optimized for sleep/awake schedules, so do not use it for sleep/awake frequencies
Setcpu works fine for me! I have used it on a Herotab C8 and some other phones.
nothrills is what I have switched to from setcpu as I didn't like when setcpu changed their interface.
I use No-frills CPU control and it works quite nice. It allows you to set min/max frequency, I/O scheduler as well as your governor. I use min 312, max 1600, I/O noop, and Ondemand for my governor and it runs quite fast! Ondemand, however, does increase your battery consumption but it is geared more for performance than battery life. Interactive also seems to be a good mix of performance and battery usage but I tend to go for pure, unadulterated power! ;-P...well...that would be the "performance" governor but...Ondemand is more practical :-D
Using no frills here. Simple and effective.
Which CPU Governor is the best for battery/performance combo. Coz when I use hotplug with an overclocked kernel asphalt 7 lags, but if I use peformance as the governor everything is fine.
And also how do I add extra governors to my phone.
The best one is Hotplug.
Performance sets your CPU at the top frequency ALL THE TIME, maybe good for games, but a total waste of battery otherwise.
Extra governors: there are other in some custom kernels.
I'm using kernel adiutor.
There isn't any option to change the GPU governor. If I change the CPU governor, will that in effect change how the GPU is governed?
There is the option of changing the voltage of the GPU, however. Can I safely underclock the GPU? Will it result in longer battery life?
Thanks
You can underclock CPU easily is the settings on stock rom. And yeah battery life is better but the device performance are affected.