Related
which of the recent governors gives best performance?
lazy, interactive, smartassv2?
Thanks guys
I just use Ondemand. I've tried others but I always end going back to it.
I've heard interactive is good for performance. I was under the impression that lazy and smartass were more geared towards battery saving.
Sent from my Nexus S using xda premium
I use lazy or ondemand typically.
Follow the leader @corythug
for performance, ondemand with a sampling rate of 15000 and up threshold of 98.
simms22 said:
for performance, ondemand with a sampling rate of 15000 and up threshold of 98.
Click to expand...
Click to collapse
simms, I am assuming this will drain battery faster as the default sampling rate is 40000. Am I correct?
Sampling Rate – An interval (in microseconds) at which the governor will poll for updates. When this happens, the governor will decide whether to scale the CPU up or down.
Up Threshold – Defines a percentage from 1% to 100%. When the CPU load reaches this point, the governor will scale the CPU up.
i like smartassV2 1200 / 100
Naa Laa said:
simms, I am assuming this will drain battery faster as the default sampling rate is 40000. Am I correct?
Sampling Rate – An interval (in microseconds) at which the governor will poll for updates. When this happens, the governor will decide whether to scale the CPU up or down.
Up Threshold – Defines a percentage from 1% to 100%. When the CPU load reaches this point, the governor will scale the CPU up.
Click to expand...
Click to collapse
no. itll actually be a little better on battery, a little more efficient than the default. and itll give the ui a little speed boost.
Isn't interactive supposed to be a 'better OnDemand'
I'm thinking it's the opposite, that on demand was an improved interactive, but I could be wrong. I really don't notice much difference between any of them. On lazy and smartassv2 I seem to get more random problems. Really though, what's best questions are left for you to explore and find out. Some people on these threads use their phone for most their computing needs and some barely even use their phone.
Sent from my Nexus S 4G
i use smartass 1200/200 on matrix 10.0 kernal n havent had any issues..i get awesome battery life 18+ hours with light to moderate use
Sent from my Nexus S 4G using XDA Premium App
I'm voting for interactive, I've had great battery life and performance from it fwiw
Sent from my Nexus S 4G using Tapatalk
What's actually the difference? Is there any guide to read?
gellow said:
What's actually the difference? Is there any guide to read?
Click to expand...
Click to collapse
ondemand – Available in most kernels, and the default governor in most kernels. 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 – Available in newer kernels, and becoming the default scaling option in some official Android kernels. The interactive governor is functionally similar to the ondemand governor with an even greater focus on responsiveness.
conservative – Available in some kernels. 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 – Available in most kernels. 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 – Available in some kernels. It will keep 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 – Included in some custom kernels. The smartass governor effectively gives the phone an automatic Screen Off profile, keeping speeds at a minimum when the phone is idle.
SOURCE: http://setcpu.com/#7
I've tried different configurations but always end up going for ondemand.
There is no "best governor", just like there's no best brand of beer. My favorite, however, is smartassv2. Great performance and battery life - probably one of the better compromises.
But I don't drink beer!
Sent from my Nexus S using XDA App
okay im sorry if this is one of the most noobish questions, but what exactly are governors , and how do they help ?
Sent from my Mytouch 4G Running Capychimps Sense 3.5 rom (v.4.0)
Cpu governors "govern" how the cpu works. There is a list somewhere that explains what a few of them do. Basically they dictate how your cpu behaves and therefore the performance you see and power consumption you experience. I'll see if I can find that list.
Edit:
- The ondemand governor is the default option used by Android. It scales the CPU speed between the minimum and maximum speeds depending on CPU load. If the system needs more speed, the kernel will rapidly scale up the CPU speed. - The conservative sets the CPU speed in a similar way to the ondemand governor, but scales the CPU up much less rapidly. This would theoretically save battery power, but may lead to less responsiveness. - The userspace governor is currently useless. It's another way for applications to set the CPU speed that SetCPU does not use. - The powersave governor always keeps the CPU at the minimum set frequency. - The performance governor always keeps the CPU at the maximum set frequency.
Except for "userspace," no matter which governor you set, the CPU will always stay within the bounds of the maximum and minimum speeds you set in SetCPU.
smartass governor -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 352Mhz (or if your min frequency is higher than 352 -why?! -it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!
Sent from my HTC Glacier using XDA App
estallings15 said:
Cpu governors "govern" how the cpu works. There is a list somewhere that explains what a few of them do. Basically they dictate how your cpu behaves and therefore the performance you see and power consumption you experience. I'll see if I can find that list.
Edit:
- The ondemand governor is the default option used by Android. It scales the CPU speed between the minimum and maximum speeds depending on CPU load. If the system needs more speed, the kernel will rapidly scale up the CPU speed. - The conservative sets the CPU speed in a similar way to the ondemand governor, but scales the CPU up much less rapidly. This would theoretically save battery power, but may lead to less responsiveness. - The userspace governor is currently useless. It's another way for applications to set the CPU speed that SetCPU does not use. - The powersave governor always keeps the CPU at the minimum set frequency. - The performance governor always keeps the CPU at the maximum set frequency.
Except for "userspace," no matter which governor you set, the CPU will always stay within the bounds of the maximum and minimum speeds you set in SetCPU.
smartass governor -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 352Mhz (or if your min frequency is higher than 352 -why?! -it will cap it to your min frequency). Lets take for example the 528/176 kernel, it will sleep at 352/176. No need for sleep profiles any more!
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
wow ! , thanks i guess im gonna get rid of my sleeping profile and start using smartass, thanks for the help
Sent from my Mytouch 4G Running Capychimps Sense 3.5 rom (v.4.0)
do you happen to know any info about smartassv2 ? , i just checked my list and i have both smartass and smartassv2
Sent from my Mytouch 4G Running Capychimps Sense 3.5 rom (v.4.0)
You're welcome! By the way, I'd appreciate it if you'd hit the Thanks button. I help people all the time and am rarely thanked. I'm starting to get a complex. Ha.
Sent from my HTC Glacier using XDA App
jjbat87 said:
do you happen to know any info about smartassv2 ? , i just checked my list and i have both smartass and smartassv2
Sent from my Mytouch 4G Running Capychimps Sense 3.5 rom (v.4.0)
Click to expand...
Click to collapse
Smart ass v2 is just an update of smart ass v1
Sent from my HTC Glacier using XDA App
The stock android 4.2.2 freqs are 102 min 1512 max...
I works liquid smooth and gives love battery life.
My question: does cpu freqs not have any impact the n battery and heat..?
Sent from my Nexus 4 using xda
faddyie said:
The stock android 4.2.2 freqs are 102 min 1512 max...
I works liquid smooth and gives love battery life.
My question: does cpu freqs not have any impact the n battery and heat..?
Sent from my Nexus 4 using xda
Click to expand...
Click to collapse
Hi,
Higher the CPU freq is, higher the electrical consumption will be, higher the temperature too
So higher freq finally mean lower battery.
faddyie said:
The stock android 4.2.2 freqs are 102 min 1512 max...
I works liquid smooth and gives love battery life.
My question: does cpu freqs not have any impact the n battery and heat..?
Sent from my Nexus 4 using xda
Click to expand...
Click to collapse
Technically, high frequency will use more current as well as often requiring a higher voltage to the cpu to maintain stability. Both of those would increase battery consumption and heat. However....
When the cpu is working at a higher frequency, it finishes whatever its doing sooner and therefore has more time to idle, thereby countering some of the higher consumption/heat. Another thing to keep in mind is that on a smartphone, the LCD screen takes up alot more power than the cpu, so that an increase of a few 100 MHz and mV will have a negligible effect on the battery. However, because the heat increases with the square of the voltage, a higher frequency with higher voltage will result in a possibly noticeable increase in temperature.
Hope thats thorough enough for you.
Sent from my Nexus 4 using xda app-developers app
faddyie said:
The stock android 4.2.2 freqs are 102 min 1512 max...
I works liquid smooth and gives love battery life.
My question: does cpu freqs not have any impact the n battery and heat..?
Sent from my Nexus 4 using xda
Click to expand...
Click to collapse
Get Franco kernel, and undervolt some to get rid of heat, and the battery is super++++.
Sent from my Nexus 4 using xda premium
Hello!
I heard about the term "UnderVolting" and I heard it would give me better battery life.
I want to do it but I have few questions before.
1. Is undervolting affects the CPU , GPU or Battery?
2. Can It damage the device?
3. Can it decrease the device performance?
Thanks!
Wassupdog said:
Hello!
I heard about the term "UnderVolting" and I heard it would give me better battery life.
I want to do it but I have few questions before.
1. Is undervolting affects the CPU , GPU or Battery?
2. Can It damage the device?
3. Can it decrease the device performance?
Thanks!
Click to expand...
Click to collapse
1. It effects the cpu. When you undervolt you are reducing the amount of power that is supplied to the cpu depending on what speed the cpu is running at.
2. It is unlikely to damage the device physically but if you undervolt too far the cpu can start failing actions resulting in corruption, but the most common symptom is that it will reboot itself if you go too low.
3. Undervolting can reduce performance but going down -100 mv across the board is usually stable for most.
Sent from my Nexus 4 using xda app-developers app
Alex240188 said:
1. It effects the cpu. When you undervolt you are reducing the amount of power that is supplied to the cpu depending on what speed the cpu is running at.
2. It is unlikely to damage the device physically but if you undervolt too far the cpu can start failing actions resulting in corruption, but the most common symptom is that it will reboot itself if you go too low.
3. Undervolting can reduce performance but going down -100 mv across the board is usually stable for most.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Thanks!
Is it recommended to undervolt?
I just want a better battery and around the same performance as it now.
You are confusing undervolt with underclock. UC is a proven way to increase battery, but it directly makes the CPU run slower. UV will make the CPU/GPU/RAM receive less milivolts, and it will only increase battery, and not decrease performance. The thing with UV is that if the CPU at any given time does not get enough power, it can't perform a given task, and your phone will reboot.
Sent from my LG-P760 using xda app-developers app
In a nutshell UV will not destroy your phone and is it recommended? If you are in xda then you know the risks or at least should read up on the risks. I would say 90% of the custom kernels are undervolted out the box and yes its a great help. I have been UV, UC and sometimes even OC for years now with no negative effects. Give it a shot and if you are worried start slow like -25.
Try mathkids kernel(JSS roms only) which is undervolted -100 and if you read the thread its never been an issue for anyone. I have heard that UV may cause some issues with Maps locking fast
Dr.Molestratus said:
You are confusing undervolt with underclock. UC is a proven way to increase battery, but it directly makes the CPU run slower. UV will make the CPU/GPU/RAM receive less milivolts, and it will only increase battery, and not decrease performance. The thing with UV is that if the CPU at any given time does not get enough power, it can't perform a given task, and your phone will reboot.
Sent from my LG-P760 using xda app-developers app
Click to expand...
Click to collapse
I'm not Confusing undervolt with underclock.
Undervolting can and does reduce performance if you go too far. (Not far enough to cause reboots)
Underclocking is not a proven way to increase battery, in fact it's quite controversial.
It's called race to idle.
Pretty much all processors have great power savings at idle speeds.
By lowering the clock speed common tasks and background processes take longer to perform. Thus keeping the cpu at a higher clock rate (using more mv) for longer and overall using more battery than what it would have done at a higher speed.
From my own tests -150 mv undervolt resulted in slower and sometimes even laggy performance. -100 is great
Underclocking to 1ghz shortened my average daily battery life by nearly 2 hrs compared to running at stock 1.5
Say what you like about stats but these are the results I found from actual usage
Sent from my Nexus 4 using xda app-developers app
UV will reduce how hot your phone gets.. and if your phone gets too hot thermal throttling will reduce the cpu speed.. and thus if u UV it will reduce thermal throttling and will increase performance..
Thanks to everyone !
Stock min CPU freq is 384 MHz.
Is there a benefit of changing this to a lower frequency?
Better battery?
nadastry said:
Stock min CPU freq is 384 MHz.
Is there a benefit of changing this to a lower frequency?
Better battery?
Click to expand...
Click to collapse
I believe after a certain frequency the voltages become the same. Meaning it takes as much power to run a processor at 384MhZ than it does at per say 126MhZ
Sent from my SM-G900T using XDA Free mobile app
Yeah, I believe the above poster is correct, but even if there is a slight variation in voltages, the battery savings are negligent and not worth the possible instabilities or slow downs that result from running the device at a frequency that low. However, if you wish to give it a shot, flashing the hellscore kernel will allow you to drop the minimum frequency to 81 MHz. Please use with caution and make a backup if you choose to proceed.