So ive been told that underclocking or undervolting might actually harm battery life instead of helping it by making the process slower before it completes.
What are the best set cpu settings for battery life?
If i decide I dont want to use setcpu how can i restore the default values?
Search for the setcpu thread by lennyuk.
All your answers are in there. Sorry don't have the link but you will find it. Think it might be in android development and hacking section??
Edit:
http://forum.xda-developers.com/showthread.php?t=1158102
Sent from my GT-I9100 using XDA App
digitallysick said:
So ive been told that underclocking or undervolting might actually harm battery life instead of helping it by making the process slower before it completes.
What are the best set cpu settings for battery life?
If i decide I dont want to use setcpu how can i restore the default values?
Click to expand...
Click to collapse
UC/UV/OC can harm your phone if not properly taken care of.
Each cpu is different so there is no 'best settings'. If i share my settings, it might not be stable in your phone, or may be you can undervolt more than me which means your cpu can handle lower voltages better than mine.
You can use an init.d script (if your kernel supports) or SetCpu or Voltage Control to overclock/underclock/undervolt.
First thing, search through kernel threads and find a kernel you think suits your taste best.
Next, using setcpu or voltage control, set a min and max global frequency.
Now for each frequency lower the voltage by 25 mv (from stock). Keep doing this until your phone becomes unstable or hangs. Use the last settings that didn't cause any problems.
I have a profile which works only at night
from 11pm to 6 am 500mhz with power save.
Once i tried 1000mhz conservative, for the whole day, does seem to give me more battery life at the end of the day.
ProNewb said:
I have a profile which works only at night
from 11pm to 6 am 500mhz with power save.
Once i tried 1000mhz conservative, for the whole day, does seem to give me more battery life at the end of the day.
Click to expand...
Click to collapse
Shouldn't the phone be in deep sleep (200mhz) at night? If you're not using it ofcourse.
TheSaw said:
Shouldn't the phone be in deep sleep (200mhz) at night? If you're not using it ofcourse.
Click to expand...
Click to collapse
Deep Sleep doesn't mean locking on to lowest frequency supported by kernel. (200 mhz on stock).
Deep sleep is the state where both cores shut off, and system (O.S) goes to sleep, governor stays idle, etc etc. There will be some background processes running too, but cpu is not using 200 mhz throughout deep sleep.
EDIT: Or you meant a screen off profile.
TheSaw said:
Shouldn't the phone be in deep sleep (200mhz) at night? If you're not using it ofcourse.
Click to expand...
Click to collapse
The phone should be in deep sleep, but some apps don't let the phone sleep at night thanks to there inefficient coding.
Anyway it does seem to use less battery, without this profile, I loose around 9% in 6 hours, but now I loose only 4-5%.
Sent from my GT-I9100 using XDA App
digitallysick said:
So ive been told that underclocking or undervolting might actually harm battery life instead of helping it by making the process slower before it completes.
What are the best set cpu settings for battery life?
If i decide I dont want to use setcpu how can i restore the default values?
Click to expand...
Click to collapse
just unistall setcpu and then reboot your phone and then you go back to default values
Related
I'm running Bullet 1.420 Kernal, what's a good setting for setcpu for profiles and such? I've been a vibrant rooter for a long time and never looked into it, thanks!
Sent from my SGH-T959 using XDA App
Are you aiming for battery life or performance? If battery life is your goal, try what's in my signature. If you're going for performance, the simplest approach is to set your screen-on profile to 1420 (or performance governor) and nothing else, and your screen off profile to 800.
kaintfm said:
Are you aiming for battery life or performance? If battery life is your goal, try what's in my signature. If you're going for performance, the simplest approach is to set your screen-on profile to 1420 (or performance governor) and nothing else, and your screen off profile to 800.
Click to expand...
Click to collapse
Oh okay, thanks, but what will happen if I put 1420 high and 100 min? Cause I want my Kernal to be free and not suppressed at the standard the phone puts, will that "free" it and will it kill battery faster? I hope you get what I mean, lol
Sent from my SGH-T959 using XDA App
Shouldn't be a problem setting 1420/100. The biggest problem I've found with overclocking is the "Sleep of Death", which occurs when you don't have the proper settings for screen-off mode. At 1200 OC, it's recommended to set your minimum frequency to 400 to avoid Sleep of Death. I believe at 1420, 800 is a safe bet to avoid Sleep of Death.
kaintfm said:
Shouldn't be a problem setting 1420/100. The biggest problem I've found with overclocking is the "Sleep of Death", which occurs when you don't have the proper settings for screen-off mode. At 1200 OC, it's recommended to set your minimum frequency to 400 to avoid Sleep of Death. I believe at 1420, 800 is a safe bet to avoid Sleep of Death.
Click to expand...
Click to collapse
Oh okay, and Overclocking OBVIOUSLY kills battery right? Ans would 1420 high, 800 min kill much battery?
Sent from my SGH-T959 using XDA App
All depends on how you use your phone. When your phone is on and you're gaming which will ramp your speed up to the maximum, then yeah. You're gonna burn more battery. I'm more battery conscious myself, and find my UI and experience smooth as silk at 1.2 with Bali-X while still getting massive battery savings with the phone spending most of it's time under 800mhz when I'm doing less intensive tasks like SMS.
At this point, your best bet is to simply test it out. Your mileage will vary depending on the ROM and kernel version you use.
kaintfm said:
All depends on how you use your phone. When your phone is on and you're gaming which will ramp your speed up to the maximum, then yeah. You're gonna burn more battery. I'm more battery conscious myself, and find my UI and experience smooth as silk at 1.2 with Bali-X while still getting massive battery savings with the phone spending most of it's time under 800mhz when I'm doing less intensive tasks like SMS.
At this point, your best bet is to simply test it out. Your mileage will vary depending on the ROM and kernel version you use.
Click to expand...
Click to collapse
Oh okay, that'll be it then I guess, I appreciate you answering all my questions when we both probably know I could've looked them up, ill be sure to thank you when I'm on a computer!
Sent from my SGH-T959 using XDA App
I was curious... does SetCpu work for this phone like Milestone Overclock? What's the difference, aside from SetCPU having more options?
They are both free (well SetCPU only free for XDA), but everyone uses milestone OC here and I'm wondering if there's a reason for that.
syrenz said:
I was curious... does SetCpu work for this phone like Milestone Overclock? What's the difference, aside from SetCPU having more options?
They are both free (well SetCPU only free for XDA), but everyone uses milestone OC here and I'm wondering if there's a reason for that.
Click to expand...
Click to collapse
There is difference between two applications. Milestone overclock actually overclocks the processor while setcpu doesn't. Setcpu just changes clock frequency of CPU ranging from minimum to maximum. It allows you to make user profiles depending on which frequency of processor will be controlled. It actually helps battery last battery longer. BTW setcpu is paid application
SetCPU is used for setting CPU parameters. Like the range of mhz your CPU works at. Also setting profiles (CPU mhz when the phone is charging, reach temperature, battery lower than... etc.). But it cannot be used for overcharging, that's why we use Milestone overclock...
Sent from my XT720 using XDA App
jackfrost3821 said:
There is difference between two applications. Milestone overclock actually overclocks the processor while setcpu doesn't. Setcpu just changes clock frequency of CPU ranging from minimum to maximum. It allows you to make user profiles depending on which frequency of processor will be controlled. It actually helps battery last battery longer. BTW setcpu is paid application
Click to expand...
Click to collapse
Setcpu is free for XDA members bud, find it here
how should i adjust my advanced settings? im overclocked at 850mhz
LibertyMonger said:
Setcpu is free for XDA members bud, find it here
Click to expand...
Click to collapse
Thank you I wasn't knowing it is free for xda members!
I personally think Setcpu creates glitches in phone routine. Say when I play music and turn off the display, after I turn it on it pauses music a bit. I uninstalled it, problem seems to be no more. Still I can't confirm if the bug was created because of setcpu plus the battery life is not increased exponentially with setcpu.
Thanks for the answers
jackfrost3821 said:
I personally think Setcpu creates glitches in phone routine. Say when I play music and turn off the display, after I turn it on it pauses music a bit. I uninstalled it, problem seems to be no more. Still I can't confirm if the bug was created because of setcpu plus the battery life is not increased exponentially with setcpu.
Click to expand...
Click to collapse
I think I agree, lol. Android has it's own built in "Setcpu" it's supposed to do a good job on it's own. I have been using it lately and not really sure it is much of an advantage. I'm gonna go a few days without I think and see. Same with battery calibration, I use 3 backup batteries so if it works it really can't work properly when switching batteries but they all always seem calibrated the same whether I use it or not.
SetCPU works with msoc but it is more of a parameter setting app. Imagine if you were oc to 1200 all the time. That would be foolish bc your processor would burn up that is to say if you battery stayed charged long enough to do it. Im set at 1100/74 but I don't need it like that all the time. When my screen is off, why do I need it that high. I do bc I listen to alot of online media, MLB, Jango, Pandora, and if the screen is on it makes temp go up. I do, you may not need it that high. SetCPU allows me to set that parameter to adjust the CPU down and underclock it if I need to. Also if my battery is too hot, I don't need it to be fast as lightning compounding heat, so I set it for a specific temp and it underclocks when I hit it. Here is a screen shots to show my settings.
LibertyMonger said:
I think I agree, lol. Android has it's own built in "Setcpu" it's supposed to do a good job on it's own. I have been using it lately and not really sure it is much of an advantage. I'm gonna go a few days without I think and see. Same with battery calibration, I use 3 backup batteries so if it works it really can't work properly when switching batteries but they all always seem calibrated the same whether I use it or not.
Click to expand...
Click to collapse
Exactly that is what I've tried, uninstalled SetCPU to see the battery performance. It was really unnoticeable the battery drain with and without Setcpu. I use Autokill Memory Optimizer which seems to be providing good results as well as performance enhancement.
Nah that pause has nothing to do with setcpu. I get that all the time.
Sent from my Milestone XT720 using XDA App
exist2resist said:
Nah that pause has nothing to do with setcpu. I get that all the time.
Sent from my Milestone XT720 using XDA App
Click to expand...
Click to collapse
Yes it has to do with SetCPU if your minimum frequency is less. In screen lock profile select min frequency to 550Mhz instead of 250Mhz. Music won't pause while waking up your device. It works!
jackfrost3821 said:
Yes it has to do with SetCPU if your minimum frequency is less. In screen lock profile select min frequency to 550Mhz instead of 250Mhz. Music won't pause while waking up your device. It works!
Click to expand...
Click to collapse
I guess you are correct.
But currently I removed the SetCPU. And I see much better performance now. I was min at 250MHz. Even the quadrant score is much better now.
Thanks for your insight
I remove setcpu and do a comparison too. I'm using CM 7.1.0 of fjfalcon and it lasts 1.5-2 days with minimal usage on setcpu. Now let's see if it's barely unnoticable.
but I think set cpu to 250mhz during the night when you don't use your phone may prolong battery life.
Woodrube said:
SetCPU works with msoc but it is more of a parameter setting app. Imagine if you were oc to 1200 all the time. That would be foolish bc your processor would burn up that is to say if you battery stayed charged long enough to do it. Im set at 1100/74 but I don't need it like that all the time. When my screen is off, why do I need it that high. I do bc I listen to alot of online media, MLB, Jango, Pandora, and if the screen is on it makes temp go up. I do, you may not need it that high. SetCPU allows me to set that parameter to adjust the CPU down and underclock it if I need to. Also if my battery is too hot, I don't need it to be fast as lightning compounding heat, so I set it for a specific temp and it underclocks when I hit it. Here is a screen shots to show my settings.
Click to expand...
Click to collapse
Dude! with those settings what is your battery life like?
my minimum is at 125mhz and max at 250mhz (when screen off) and I lose 30% over night! and it barely lasts 8hours D:
what ROM are you on?
Do you guys know how the smartass governor works?
As I understand solution for "998 MHz with screen on" bug is found: http://forum.xda-developers.com/showthread.php?t=1225411&page=17#post16944722
We need to replace only one governor.
I don't want to play with different ROMs and kernels and I'm looking for simplest solution.
Is it possible to compile it as a module ("ondemand_mod" for ex.) and add it to stock ROM?
Or any other (simple) way?
Wrong section ...
Sent from my X10i using Tapatalk
Why wrong Section, this is Development to get the CPU Governor working correctly
Wolfbreak said:
Why wrong Section, this is Development to get the CPU Governor working correctly
Click to expand...
Click to collapse
Exactly, this is the right section for such request.
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
My_Immortal said:
However, I can't help but wonder: is this really a "problem"?
No offence to anyone, but I find that the phone is very snappy
when on max frequency... The big problem for me, would be if it
didn't go into Deep Sleep immediately after turning the screen off
and stayed at min frequency for an extended period.
When the screen is on (aka using the phone) I'd like it to be as FAST
as possible. That's the reason I use the minmax governor.
Anyway, again, I don't mean to argue with anyone, I am just
presenting my point of view.
Click to expand...
Click to collapse
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
As I see it's possible to compile and use governor as module.
Could someone compile it? And assemble as xRecovery package?
Or point me where to read about compiling for arm, where to get tools and so on...
Karlson2k said:
Yes, it's really problem.
Higher frequency - higher power consumption. Moreover - with higher frequency CPU used with higher voltage so consumption is even more higher. So at 998 MHz CPU eats about 5 times more battery than on 246MHz.
With properly tuned governor I don't feel any real lags or slowdowns.
And, when screen is on CPU load is usually is lower than 20% at full frequency. So I don't want to waste my battery.
Click to expand...
Click to collapse
The thing is, on 245 MHz, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Xperia X10i via Tapatalk
My_Immortal said:
The thing is, on 245 MHz with high load, you can't get any kind of decent performance.
Try this: set the minimum and maximum CPU frequency with SetCPU to 245 and attempt to use the phone normally.
Also, you might be right about voltage, but if the CPU is forced to work on lower freqs when it actually needs higher, there's definitely stress and increased battery consumption.
My phone lasts for more than 24 hours and it's always at max frequency when the screen is on. No lag, no freezes, no drain.
I do agree that the ondemand governor might not function as expected but I fail to experience the actual problem. That might be just me though.
Click to expand...
Click to collapse
There is no need to work on 245MHz as proper governor rise frequency automatically when it's necessary.
And really no stress for CPU to work an low frequency at full load. Moreover - CPU will consume more power at 500Mhz with 45% load than at 250Mhz with 95% load.
Sometime I use phone for navigation - long time with screen on and very low load. In this scenario battery drains very fast.
And last one - I like to have everything working properly. In case that I'll really need high frequency all the time I'll use other governor. I just want to have a choice.
I need a simple solotion for this too..I use z kernel and I found that Thego2s kernel fixed this problem..I was going to flash that kernel but think that has a bug and stoucks on logo ..can some one sayas a simple way?
Yes, I think a lot of people would prefer to use just small and simple fixes rather than replacing the whole kernel with a lot of nice but (personally) unnecessary features.
I am waiting for developers to release a fix for this problam
Does anyone underclock? I only do it in certain situations. Do you see it as beneficial? Why or why not?
Sent from my Galaxy S2
EDIT: My settings are attached as a screenshot. My device is underclocked 50% of the time.
In my opinion and from personal use, I don't find underclocking to really be beneficial. I never really saw any better battery life. On the same note, I never really found overclocking and undervolting to be extremely beneficial either. It's like the gains aren't worth the time to tweak everything.
Undervolting, yes. Limiting clock speeds, and setting governer to conservative, yes. I say 1ghz is the best spot without losing much performance, and I get 2 days of battery life (sometimes) compared to the one day before... Stock kernel, you aren't going to see much of a difference because you can't undervolt...
I keep my phone at 800max 200min on conservative with a 85% up and 20% down threshold. I don't even see the phone slow down at 800 plus it saves some battery!
I force underclock when I'm in a situation where I KNOW the clock should never ramp up (Screen-off I set to 500) as a "safety measure" to prevent surprises.
I also may force underclock to 800 when running Navigation once my vehicle dock comes in - since we can't crank our charge current up.
Entropy512 said:
I force underclock when I'm in a situation where I KNOW the clock should never ramp up (Screen-off I set to 500) as a "safety measure" to prevent surprises.
I also may force underclock to 800 when running Navigation once my vehicle dock comes in - since we can't crank our charge current up.
Click to expand...
Click to collapse
My screen off is set to this also (200-500, conservative). You can use Tasker to change frequencies for specific apps automatically.
hi guys..i've a problema that i can't resolve...
during the night my phone stay awake for many many minutes..
i don't know why...
i don't have app in backgrund...
i use the low freq at 100 mhz...
maybe is it the problem?
at 100 mhz for the phone is more difficult goes to sleep?
coloxim said:
hi guys..i've a problema that i can't resolve...
during the night my phone stay awake for many many minutes..
i don't know why...
i don't have app in backgrund...
i use the low freq at 100 mhz...
maybe is it the problem?
at 100 mhz for the phone is more difficult goes to sleep?
Click to expand...
Click to collapse
To low
jje
do you think if i set 200mhx the phone goes in sleep mode more easily?
Depends on the kernel. Different kernels sometimes have different frequencies they will set the CPU at just before the phone goes into deep sleep. There was some posts in the Siyah dev thread about two weeks ago where this was discussed. Some kernels can have the deep sleep frequency set via script. Deep sleep frequency can also vary depending on the CPU governor used for some kernels.
coloxim said:
do you think if i set 200mhx the phone goes in sleep mode more easily?
Click to expand...
Click to collapse
i have the same problem. i've try many roms and kernels, but still can't solve this problem. My gs2 is still being awake when even I am not using it.
I hope stock 4.0 rom would be solved this problem...
Cpu frequency should have nothing to do with wakelocks. Do u leave sync on overnight? I would recommend installing betterbatterystats to find the culprit of the wakelocks, then install titanium backup or bloat freezer (free) to freeze the process that is keeping the phone awake
i've tried battery stat....but i didn't see nothing...
I'll test it this night again...
MistahBungle said:
Depends on the kernel. Different kernels sometimes have different frequencies they will set the CPU at just before the phone goes into deep sleep. There was some posts in the Siyah dev thread about two weeks ago where this was discussed. Some kernels can have the deep sleep frequency set via script. Deep sleep frequency can also vary depending on the CPU governor used for some kernels.
Click to expand...
Click to collapse
so the cpu goes to sleep only when reachs some freq?
I don't use SepCPU anymore it's a useful app but i can get superb battery life without it, Speedmod K2-21 is probably the best kernel for battery life this is what i use and i can get 95% deep sleep at night.
On stock samsung kernel the cpu scales up to 800 mhz before entering deep sleep. On a custom kernel, like siyah kernel, the cpu scales to 500 mhz just before sleep so it can initiate the suspend process, which is basically what puts the phone to sleep. Btw when looking at battery stats you should look at partial wakelocks, those are the ones that keep your phone awake
Sent from my GT-I9100 using XDA App
Sent from my GT-I9100 using XDA App
Btw which kernel and governor are you using? Do you use set cpu or voltage control?
Sent from my GT-I9100 using XDA App
I had this problem too and accidentally fixed it by flashing a modem (XXLPB). Now all is well so give it a try.