Guys! What is the best setting for Set Cpu? I need to conserve battery. My battery lasts about 12 hours. Im using a Reflex S 2.04 rom but i shifted to Leedroid 2.4.1. My settings are 768 On demand and 245 max 245 min on demand for powersave.
What is smart ass? How does it affect the system?
On SetCpu, I run overclocked 1200 till under 80%
Then about 80
700 at 70% battery
600 at 50%
I don't wish to run lower, as the desire gets a little wonky below 500mhz
3 profiles. I can get 3 days battery
I use no frills CPU - oc 1114, ondemand governor 245-1114.
Get about 12 he's heavy use, up to 2 days light. Today I have done 3+ hrs train journey with music, browsing and SMS, checked mail, now hanging about on this forum! 41% left.
All other governors are ****. Just use ondemand.
Im set at 128-1190 ondemand.
Sent from CM7
Meaple said:
All other governors are ****. Just use ondemand.
Click to expand...
Click to collapse
Why?
I use smartass @128-768 Mhz.
remember to use screen off feature (saves a lot of battery)
I've been meaning to ask for a while but what's the difference between the governors, such as ondemand smartass etc...? Thanks. Dan.
Sent from my HTC Desire using XDA App
MatDrOiD said:
Why?
I use smartass @128-768 Mhz.
Click to expand...
Click to collapse
Because they don't work well. When you need CPU power they tend to lag and it takes that little extra longer which does my head in. Whether it's just me I don't know but it is so annoying. I have noticed it when playing games like RoboDefence. That's why I stick to ondemand because it actually works.
for the sleep off what is the best setting? screen off 245 max 245 min on demand? or 245 max 128min smart ass?
With smartass you do not have to set a profile for screen off. Smartass uses automatically the min cpu-frequency you set. So if you set smartass for screen off, you have two "screen off"-profiles. I think that could cause problems. You should set the screen-off-profile on [email protected] to avoid waking up problems, which can occur with this min 128 and max 245 for screen off-profile.
Meaple said:
Because they don't work well. When you need CPU power they tend to lag and it takes that little extra longer which does my head in. Whether it's just me I don't know but it is so annoying. I have noticed it when playing games like RoboDefence. That's why I stick to ondemand because it actually works.
Click to expand...
Click to collapse
+1 Agree totally
Ondemand is the only governor which doesnt make my phone lag.
westleydan said:
I've been meaning to ask for a while but what's the difference between the governors, such as ondemand smartass etc...? Thanks. Dan.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
You can find this in the wiki...
westleydan said:
I've been meaning to ask for a while but what's the difference between the governors, such as ondemand smartass etc...? Thanks. Dan.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
From SetCPU-Website:
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.
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.
Click to expand...
Click to collapse
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!
Click to expand...
Click to collapse
Source: http://www.ziggy471.com/2010/11/07/smartass-governor-info/
Related
I used to use setcpu on my first rom (LeeDroid) but it lagged my phone bad, so uninstalled it. Now have came back to it on droidzone RoM and its running fine, I only want screen off profile, but whats the best setting? am using smartass 245 max-128min is smartass best scaling?
EDIT
Topic started of has a question thread, so I thought on changing this to setCPU General CHAT
I recommend for screen off, 245-128 powersave governor.
Setcpu is a great tool ,but you need to play with it a bit with the settings...
Sent from my HTC Desire
dexter93 said:
I recommend for screen off, 245-128 powersave governor.
Setcpu is a great tool ,but you need to play with it a bit with the settings...
Sent from my HTC Desire
Click to expand...
Click to collapse
Thanks for reply, what you recommend for the main scaling? Also powersaver give's me lag, when switching screen back on.
Same here. I'm using smartass at screen-off for same reason.
shankly1985 said:
Thanks for reply, what you recommend for the main scaling? Also powersaver give's me lag, when switching screen back on.
Click to expand...
Click to collapse
Min 128 max 245 for screen off is too low to wake phone up, does not matter which governor you use. Min 128 max 245 with screen off may only work with ondemand governor, but i would not recommend it.
If you want to use min 128 mhz with screen off, you should set max to 422 mhz. As governor i recommend ondemand or interactive. On this way you can avoid issues in waking up the phone and you will still have a great battery life. For screen on you can use min 128 and max 768 with ondemand/interactive. But keep in mind, some phones have problems with 128. If your phone crashes sometimes randomly, set min cpu frequencies in both profiles up to 245.
A little different opinion:
rootSU said:
I use on demand with eviollet kernel min 128 max 245. Only thing that happens screen off is Poweramp, so can't comment for other back ground apps. But wake up is fine and power amp runs fine.
Of course with teh eviolet kernel you can set your own voltage levels so the next frequency up from 245 (384) can be set with the same voltages as 245, so having max of 384 would be no different power drain wise than 245.
Smartass is very bad for waking the phone so I steer clear of that all together.
Once thing that is important to note, using a different governor for screen off than screen on will also slow down your wake time. Changing governors can take time so will produce a lag when turning on the screen so find your governor and stick with it through out.
The most efficient governor for screen off if min and max are the same is either powersave or performance. The reason for this is they as default run at min or max (respectively) so they do not poll the CPU to check for load as they do not care. That said of course, these governors are no good fro screen on use IMHO so it would need a different one which then gives you the governor change issue.
Click to expand...
Click to collapse
That's interesting. Thanks! Didn't know the governor change issue.
MatDrOiD said:
Min 128 max 245 for screen off is too low to wake phone up, does not matter which governor you use. Min 128 max 245 with screen off may only work with ondemand governor, but i would not recommend it.
If you want to use min 128 mhz with screen off, you should set max to 422 mhz. As governor i recommend ondemand or interactive. On this way you can avoid issues in waking up the phone and you will still have a great battery life. For screen on you can use min 128 and max 768 with ondemand/interactive. But keep in mind, some phones have problems with 128. If your phone crashes sometimes randomly, set min cpu frequencies in both profiles up to 245.
A little different opinion:
Click to expand...
Click to collapse
Very good read thanks, am using ondemand for both default and screen off and its perfect screen off set to min128 max384 priority 100
works smooth not so sure about battery saving tho? but I have noticed display in battery settings is now down to 40% used to be always 55-65%
You might want to check this, as I'm pretty certain your 128MHz state almost never kicks in with that profile.
Also, check vdd levels as I think 128 and 245 share the same, so all you get is a placebo, and battery wise you get nothing.
erklat said:
You might want to check this, as I'm pretty certain your 128MHz state almost never kicks in with that profile.
Also, check vdd levels as I think 128 and 245 share the same, so all you get is a placebo, and battery wise you get nothing.
Click to expand...
Click to collapse
I am pretty sure 128 mhz cosumes less battery than 245 mhz, because clock is lower, even if the vdd level (the tension) is the same.
erklat said:
You might want to check this, as I'm pretty certain your 128MHz state almost never kicks in with that profile.
Also, check vdd levels as I think 128 and 245 share the same, so all you get is a placebo, and battery wise you get nothing.
Click to expand...
Click to collapse
Looking at the info and the time of each % 128 has 45% 245 13% 998 23%
I was shocked lad night, after 16 hours and at 12pm my phone had 51% battery
shankly1985 said:
Looking at the info and the time of each % 128 has 45% 245 13% 998 23%
I was shocked lad night, after 16 hours and at 12pm my phone had 51% battery
Click to expand...
Click to collapse
I hope shocked in a good way?
MatDrOiD said:
I hope shocked in a good way?
Click to expand...
Click to collapse
Very good way ha ha
I'd like to try SetCPU, but running across this thread has made me nervous... is there a guide somewhere please?
tobydjones said:
I'd like to try SetCPU, but running across this thread has made me nervous... is there a guide somewhere please?
Click to expand...
Click to collapse
There is no real risk mate, just don't go over clocking it all the way, right away. Start of small steps. Under clocking is very safe
Sent from my HTC Desire using XDA App
tobydjones said:
I'd like to try SetCPU, but running across this thread has made me nervous... is there a guide somewhere please?
Click to expand...
Click to collapse
http://www.setcpu.com/
You might want to check this, as I'm pretty certain your 128MHz state almost never kicks in with that profile.
Also, check vdd levels as I think 128 and 245 share the same, so all you get is a placebo, and battery wise you get nothing.
Click to expand...
Click to collapse
Looking at the info and the time of each % 128 has 45% 245 13% 998 23%
I was shocked lad night, after 16 hours and at 12pm my phone had 51% battery
Click to expand...
Click to collapse
What settings is that with mate?
tbaxter08700 said:
What settings is that with mate?
Click to expand...
Click to collapse
998max 128 min ondemand
Screen off 384 max 128 min ondemand 100% priority.
And that's it mate my battery life is superb
Sent from my HTC Desire using XDA App
Uploaded pic to show.
shankly1985 said:
998max 128 min ondemand
Screen off 384 max 128 min ondemand 100% priority.
And that's it mate my battery life is superb
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
And what other stuff do you have on/off? Mobile internet, WiFi?
tbaxter08700 said:
And what other stuff do you have on/off? Mobile internet, WiFi?
Click to expand...
Click to collapse
Mobile data always on, wifi only when download Apps, sync only when I want it to.
Screen brightness just under halfway, dont use bluetooth that much, never use GPS.
Anything else that I missed?
What's the difference between / features of:
Interactive
Conservative
Ondemand
Smartass
Smartassv2
Performance (is it run at the maximum?)
Powersave (is it run at the minimum?)
And does performance for each vary per kernel? What I mean is will, say, Interactive be better than Conservative on Incredikernel AOSP but worse on Tiny GB Sense?
pianoplayer said:
What's the difference between / features of:
Interactive
Conservative
Ondemand
Smartass
Smartassv2
Performance (is it run at the maximum?)
Powersave (is it run at the minimum?)
And does performance for each vary per kernel? What I mean is will, say, Interactive be better than Conservative on Incredikernel AOSP but worse on Tiny GB Sense?
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. - SetCPU website
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. - SetCPU website
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 the CPU load. This governor is recommended for stable benchmarking. - SetCPU website
powersave
Available in some kernels. It will keep the CPU running at the "min" set value at all times. - SetCPU website
userspace
A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor. - SetCPU website
Interactive
The 'interactive' governor has a different approach. Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down to.
SMARTASS GOVERNOR
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 245Mhz (or if your min frequency is higher than 245 - why?! - it will cap it to your min frequency). Lets take for example the 998/245 kernel, it will sleep at 245. No need for sleep profiles any more!
The performance for each can varry by kernel due to the fact that some devs slightly tweak the governors to their liking. Without any tweaking they should be the same accross all kernels.
Also note that tinys kernel has an interactive X governor and also a smartass 2 governor. These are basicky just tweaked versions of the original governor.
pianoplayer said:
What's the difference between / features of:
Interactive
Conservative
Ondemand
Smartass
Smartassv2
Performance (is it run at the maximum?)
Powersave (is it run at the minimum?)
And does performance for each vary per kernel? What I mean is will, say, Interactive be better than Conservative on Incredikernel AOSP but worse on Tiny GB Sense?
Click to expand...
Click to collapse
This is a good resource for governors. It is quite technical though. It doesn't include smartass though smartass is similar to smartassv2.
CPU Governors
Let me know if you still have questions after reading it.
The answer to your second question is no. The build of the governors are about 95% the same between kernels and with the exception of the smartass governors all those listed are stock android kernels.
Interactive should be smoother than conservative or ondemand but similar in performance to the smartass governors.
SmartassV2 is found to give the best performance/battery life combo across the board.
Edit: Good writeup cmlusco. In practice yes, smartassv2 is better all around I think. Interactive from Nexus S/Galaxy Nexus kernel source should be good but I've yet to be able to backport it to work on this phone property. It turns into a performance governor really.
And a side note. If the phone is actually in deep sleep state (reported by CPU Spy) the governor will not really matter then. Only time screen off matters is when it's awake but screen is off. Governor is most critical when screen is on really, so if you go for performance, screen on performance is what matters.
Edit 2: And I read some interesting viewpoints recently on maximizing battery that are different than the minimize CPU speed.
Right now I'm at 1.35GHz with Francos stock settings, so 700 for the minimum. Should I expect to see much of a loss in battery life? And what is the difference between the different governors? I could never find much info about them.
The OC itself dosent affect battery, it's how much time your phone is in whatever state(350, 700, 1350, etc..) also setting the minimum to 700 is either really good or really bad for battery, if you turn on your screen ever 5 minutes then it will be better to have it at 700 but if you only turn on your screen once every couple hours you will get much better battery with the absolute minimum. As for governors
Code:
interactive - Instead of sampling the cpu at a specified rate, the governor will scale the cpu frequency up when coming out of idle. When the cpu comes out of idle, a timer is configured to fire within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer fires then we assume the cpu is underpowered and ramp to MAX speed.
smartass - Is an improved version of interactive governor
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.
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.
brazilianwax - Very agresive version of smartass
interactiveX - Tweaked Interactive governor by Imoseyon by adding more features like suspend/wake profile
ondemandX - Tweaked and ported from 2.6.38 base Ondemand governor by Imoseyon by adding more features like suspend/wake profile
This is taken from the lord module kernel from the desire HD forum as it has a list of many governors, you may have to try a couple governors until you find one that balances speed and battery life for your personal needs, on more governor on our devices is hotplug which will turn off one of the CPU cores when the screen is off.
Seen a lot of conflicting comments stating using smartass governor means there is no need for profiles to be setup and can actually be detriment to the battery life and speed of phone.
Is this true or could I benefit from setting up profiles to get my usage optimised.
Below is a quote which will explain you everything about smartass governor
From it's developer:
"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!"
Click to expand...
Click to collapse
A couple weeks ago, I installed SetCPU to help with battery life. It did great! But, I didn't see the amazing improvement that I thought I would.
So, I did some research and found out about Profiles. Profiles are settings that you can make that will be applied when certain conditions are met.
Below are the profiles that I have created on my Nitro. I have seen 11 to 12 hours of medium use from my phone with these settings. If you have any suggestions on changes, please let me know. I'd like to find the absolute best settings and share them for everybody.
Profile Name: Screen Off
Conditions: Screen Off
CPU Max: 384Mhz
CPU Min: 192Mhz
Governor: powersave
Priority: 90, Exclusive
Profile Name: Charging Any
Conditions: Charging Any
CPU Max: 1512Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 85, Exclusive
Profile Name: In Call
Conditions: In Call
CPU Max: 810Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 80, Exclusive
Profile Name: Battery <= 10%
Conditions: Battery <= 10%
CPU Max: 594Mhz
CPU Min: 192Mhz
Governor: conservative
Priority: 75, Exclusive
Profile Name: Battery <= 25%
Conditions: Battery <= 25%
CPU Max: 972Mhz
CPU Min: 192Mhz
Governor: conservative
Priority: 70, Exclusive
Profile Name: Battery <= 50%
Conditions: Battery <= 50%
CPU Max: 1242Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 65, Exclusive
Profile Name: Battery <= 75%
Conditions: Battery <= 75%
CPU Max: 1350Mhz
CPU Min: 192Mhz
Governor: ondemand
Priority: 60, Exclusive
By setting the profiles base on battery percentage like that, you are sacrificing the speed to improve battery life. It works in some cases but has side-effect in many other cases:
- Firstly, for some tasks that requires high CPU, apparently you need more time at lower speed, so power consumption for CPU is the same but more power needed for longer screen on -> worse battery life
- Secondly, the more profiles you use, the longer it takes for SetCPU to decide and change CPU speed, so the responsiveness is lower
For you screen off profile, if you use powersave governor, your CPU always runs at min speed, so setting the max speed at 384 MHz is meaningless.
For me, the only profile I use is the screen off profile with min = 192MHz, max = 432MHz, governor = ondemand, so that my phone will wake up faster when there's a call (otherwise you will have to wait a little bit before you can sliding Answer/Reject)
noemtfj said:
By setting the profiles base on battery percentage like that, you are sacrificing the speed to improve battery life. It works in some cases but has side-effect in many other cases:
- Firstly, for some tasks that requires high CPU, apparently you need more time at lower speed, so power consumption for CPU is the same but more power needed for longer screen on -> worse battery life
- Secondly, the more profiles you use, the longer it takes for SetCPU to decide and change CPU speed, so the responsiveness is lower
For you screen off profile, if you use powersave governor, your CPU always runs at min speed, so setting the max speed at 384 MHz is meaningless.
For me, the only profile I use is the screen off profile with min = 192MHz, max = 432MHz, governor = ondemand, so that my phone will wake up faster when there's a call (otherwise you will have to wait a little bit before you can sliding Answer/Reject)
Click to expand...
Click to collapse
I haven't seen any responsiveness problems... And I'd actually like having a phone that I don't have to charge ever 3 hours over one that is unnecessarily fast.
mattman86 said:
I haven't seen any responsiveness problems... And I'd actually like having a phone that I don't have to charge ever 3 hours over one that is unnecessarily fast.
Click to expand...
Click to collapse
His point was that scaling your CPU back so significantly isn't necessarily going to give you better battery life, and may even make it worse. When the phone is running at a slower speed, it takes longer to do certain things, which means your CPU/screen will be turned on for longer. Of course it entirely depends on what you're doing on the phone.
I think you might get just as good battery life by using interactive 1.2GHz all the time. People assume governors like interactive will destroy their battery but you'd be surprised.
mattman86 said:
I haven't seen any responsiveness problems... And I'd actually like having a phone that I don't have to charge ever 3 hours over one that is unnecessarily fast.
Click to expand...
Click to collapse
If you have to charge your phone every 3 hours without SetCPU then I suggest you buy a new phone or new battery rather than playing with SetCPU
drumist said:
His point was that scaling your CPU back so significantly isn't necessarily going to give you better battery life, and may even make it worse. When the phone is running at a slower speed, it takes longer to do certain things, which means your CPU/screen will be turned on for longer. Of course it entirely depends on what you're doing on the phone.
I think you might get just as good battery life by using interactive 1.2GHz all the time. People assume governors like interactive will destroy their battery but you'd be surprised.
Click to expand...
Click to collapse
I don't do much with my phone in the way of heavy gaming or video watching. I am going off of the last couple days of having SetCPU enabled and getting almost 15 hours of medium use out of my phone.
noemtfj said:
If you have to charge your phone every 3 hours without SetCPU then I suggest you buy a new phone or new battery rather than playing with SetCPU
Click to expand...
Click to collapse
It was an arbitrary number.
Does anybody find this kind of post meant to make peoples phones better helpful? It seems like every time I post something that I personally have found to make the Nitro even more awesome gets a tone of comments basically telling me that none of it will ever work. I'm sure that if people would just try the things I post, they would be happy.
my setcpu setting-> uninstall
i found it did more harm than good. jd ultimate handling screen dimming&wifi with simple ondemand gov works much better for me.
scott0 said:
my setcpu setting-> uninstall
i found it did more harm than good. jd ultimate handling screen dimming&wifi with simple ondemand gov works much better for me.
Click to expand...
Click to collapse
That what I've heard also... But I found that JD ran my battery down in about 6 hours without me even touching it one day.
If you have any suggestions on settings for it, I'd love to give them a try.
mattman86 said:
That what I've heard also... But I found that JD ran my battery down in about 6 hours without me even touching it one day.
If you have any suggestions on settings for it, I'd love to give them a try.
Click to expand...
Click to collapse
yeah, i guess it's diff for everybody, just like the roms eh, some get great batt perf on 1 and sucky on another and someone has exactly opposite.
anyhoo, my jd ultimate settings are
Status
advanced profile
graphical notification->quickbox
Controls
wifi enabled->wifi preferred
brightness min 20% mid 45% max 150% (gotta get the most of this screen in the sunlight!)
light sensor fast
cpu min 192 mid 918 max 1512
governor ondemand
schedules
none, i also turned off night schedule as i have the phone plugged in during those hours.
triggers
Apps enabled
Configure->configure apps allow on during screen off->pandora
Location enabled
****************i find it makes a world of difference to give jd =>3 days to get it all right.
make sure setcpu is out of the way as well.