Anybody notice one performing better than the other with regard to battery life? I have the paid version of SetCPU which I bought for my G1 a while back but I'm not sure I really need it for the CPU throttling on the Vibrant but it does seem to improve battery life and I was wondering if Juice Defender might be better.
JuiceDefender was fabulous for battery life but it did slow down my phone a lot. I ended up uninstalling it. If you want to try toggling your data to save battery, I recommend DCSwitch widget. Works like a charm for data control.
I just started using SetCPU on this phone so I can't say how it affects battery.
Tasker is better then Juice Defender. It does everything JD does and MUCH more stuff.....unlimited possibilities
You should probably understand that lowering the frequency of your processor doesn't save a bit of battery. The only way you can save battery is to lower the voltage which neither of those apps can do so whatever you're seeing as "saving battery" is a placebo effect. When the phone is in sleep mode the CPU is defaulted at 245mhz. Lowering the "Max" frequency does just that; it lowers the maximum frequency the processor is able to use.
bmj1086 said:
You should probably understand that lowering the frequency of your processor doesn't save a bit of battery. The only way you can save battery is to lower the voltage which neither of those apps can do so whatever you're seeing as "saving battery" is a placebo effect. When the phone is in sleep mode the CPU is defaulted at 245mhz. Lowering the "Max" frequency does just that; it lowers the maximum frequency the processor is able to use.
Click to expand...
Click to collapse
It's true that reducing voltage (which we can't do) would be more effective as power consumption at a given clock frequency is proportional to the square of the voltage, but you're wrong to dismiss frequency control as a power saving strategy because at any given voltage, power consumption is proportional to frequency. Hence Intel's "speed step" technology used in notebook CPU's.
Juice Defender and SetCPU are doing more or less the same thing as Intel speed step.
We CAN reduce voltages with the right kernel... Dragon TEST 5 kernel.
^ correct with the voltage control app from the market i believe.
Between setCPU and juice defender..
i say juice defender.
Set CPU is a hassle.
It shuts your phone off sometimes with profiles on, and freezes it etc.
If your phone experiences any of those problems, uninstall setcpu and bam, your phone is normal again.
SetCPU is only good for overclocking, and sometimes sucks at that too.
xriderx66 said:
^ correct with the voltage control app from the market i believe.
Between setCPU and juice defender..
i say juice defender.
Set CPU is a hassle.
It shuts your phone off sometimes with profiles on, and freezes it etc.
If your phone experiences any of those problems, uninstall setcpu and bam, your phone is normal again.
SetCPU is only good for overclocking, and sometimes sucks at that too.
Click to expand...
Click to collapse
Yeah, that's what happened to me with setcpu. Every time the screen turned off, the phone turned off as well.
With juice defender, I lost a lot more battery. About 15% in 3 hrs of standby vs. 3-4% in 3 hrs of standby without any power saving apps.
If people are having good results with both apps, could you please show how you set it up? I may have not set it up right.
burntrat said:
With juice defender, I lost a lot more battery. About 15% in 3 hrs of standby vs. 3-4% in 3 hrs of standby without any power saving apps.
If people are having good results with both apps, could you please show how you set it up? I may have not set it up right.
Click to expand...
Click to collapse
Same here.
I figured that people who got positive results from all the battery-saving apps are the ones that use their phones aggressively and switching between all types of connections (wifi/bluetooth/gps). I use my phone normal, so I'm better off without apps like that.
Yeah, that's what happened to me with setcpu. Every time the screen turned off, the phone turned off as well.
Click to expand...
Click to collapse
If I remembered correctly, it's because you've set the frequencies way too low for your phone to function properly.
Related
I got 12% battery drain in 17 hours, standby. I'm not a pro at android but I might give a little tut. on how to save battery life to the max. Atleast, it works for my P500 so it should work for you & for any other android device as well.
Uninstall every unnecessary app, including system apps (those apps, that does not mess up with the system stability - If you uninstall Email app, you will not solve your problems with Gmail app).. same with Messaging. That said, leave as minimum apps in the background as you can. App killer does not solve this problem, it just closes bg apps - they restart after some time. I'm using ATK (Advanced Task Killer), It usually kills 1 - 3 apps, so.. I have a minimum of apps running in the bg.
Basic stuff.. turn off your 3G, wifi, bg sync, gps when not in use. If you need to check your email, use 2G network only option, not 3G. Use 2G always when you don't need 3G speed. Screen brightness is not that important if you set it to anywhere below 70%. It should not drain the battery that fast.
Setcpu - profiles - governors--
My profiles are as follows
Charging - 480min - 748max
Battery <90% - 245min - 600max
Battery <70% - 245min - 600max (U can live with one profile for the battery, I have 2 in case I want to change the 2nd profile)
Screen off - 122min - 245max -- This is what saves my battery in standby.
The governors are ondemand for usage & conservative for screen off.
I'm using Void.echo rom with tapps & gapps modules, uninstalled everything I don't need.
I hope this helps If anyone has a better idea on how to save battery life, please share yours as well.
Thanks for your post, but actually most background apps don't drain battery. I have made lots of experiments (removing system aps, preventing autorun etc., and I don't see any major difference in battery life. So now, I'm on stock 2.2 and I'm now at 80% after almost 30h use: about 20 min talk, 10-15 min wi-fi (mail), 10-15 min EDGE. The latter by the way drains battery more than wi-fi. So instead of messing with system apps I recommend putting the phone in airplane mode during the night and as mentioned in the above post - not using 3G when not needed (EDGE has decent speed).
thats the why linux works !!! use all the memory u possibly can...These Microsoft *****es have changed the way computers were supposed to be used not reinstalling windows and other crapware all the time..Switch to Debian while its still time
And i use these settings
screen off 245-245 powersave (otherwise phone gets hot Its summer in india)
600-245 ondemand otherwise
kopchev said:
Thanks for your post, but actually most background apps don't drain battery. I have made lots of experiments (removing system aps, preventing autorun etc., and I don't see any major difference in battery life. So now, I'm on stock 2.2 and I'm now at 80% after almost 30h use: about 20 min talk, 10-15 min wi-fi (mail), 10-15 min EDGE. The latter by the way drains battery more than wi-fi. So instead of messing with system apps I recommend putting the phone in airplane mode during the night and as mentioned in the above post - not using 3G when not needed (EDGE has decent speed).
Click to expand...
Click to collapse
If there are many apps running in the bg, phone runs out of ram, so it tries to free up some space constantly. I think that drains battery, not the apps themselves. As well as the more cpu power is used, the faster it drains battery. Airplane mode shuts off any connection, so either that or you could just shut down the phone during night. Hmm you could tell me how to prevent app autorun, i have not looked into that.
btw juicedefender does wonders with the phones battery i had a 2% percent over night normal mode (not airplane) no 3g/Edge/Wifi/Bluetooth active and just sleeping
sarfaraz1989 said:
thats the why linux works !!! use all the memory u possibly can...These Microsoft *****es have changed the way computers were supposed to be used not reinstalling windows and other crapware all the time..Switch to Debian while its still time
And i use these settings
screen off 245-245 powersave (otherwise phone gets hot Its summer in india)
600-245 ondemand otherwise
Click to expand...
Click to collapse
True about windows & linux hehe. You havent tried 122-245mhz on screen off? Ofcouse, it lags even when i receive an sms, it's something like this - the screen turns on, then after 2 sec. i hear a notification, then after 1 sec. i see the sms but that does not make any problems for me, it's extreme powersaving
I don't get the point of airplane mode while you're sleeping.
If you don't want to get calls while sleeping, shouldn't it be better if you turn off the phone?
I had a good experience with JuiceDefender until now too. Last night my phone was 100% and no airplane mode while sleeping. It drained only 3%.
SoundTone said:
If there are many apps running in the bg, phone runs out of ram, so it tries to free up some space constantly.
Click to expand...
Click to collapse
From what I've read, Android doesn't swap. It'll just kill the background apps on it's own. I don't think there even is a swap unless you root, rom and create one on your uSD.
rapharias said:
I don't get the point of airplane mode while you're sleeping.
If you don't want to get calls while sleeping, shouldn't it be better if you turn off the phone?
I had a good experience with JuiceDefender until now too. Last night my phone was 100% and no airplane mode while sleeping. It drained only 3%.
Click to expand...
Click to collapse
It's more convenient, because the on/off process is quite slow...in contrast - airplane mode on/off is 3-4 secs. In airplane mode you can still use wi-fi. Last night the battery drained only 1%
i read somewhere that changing the CPU speed doesnt change the voltage, thus it does not affect battery life... anyone can confirm this???
As far as I can remember from school, a logic gate uses more power when switching, thus a higher frequency would also mean higher power drain (higher frequency = more switching of the logic gates), without voltage modification.
Voltage is changed in order to keep stability - higher voltage means a more stable logic signal, and a faster switching gate, and thus people reccomend using a higher voltage for higher frequencies/lower voltage for lower frequencies.
Thus, a CPU with so many logic gates does not operate just like a simple resistor. In fact it is worse, because when you use higher voltage AND higher frequency power drain is increased much more.
On the other hand, most modern CPU's simply deactivate CPU regions when idling, so, in case of our hardware (constant voltage) there should not be such a great difference when idling (most of the CPU is powered down). The only thing is for the phone to be REALLY idling (no background tasks eating too much of the CPU when screen off).
Basically, what this means is that if you want extreme power saving use a governor with 128MHz minimum and have as few background services as possible (or at least the ones that are there should be optimized for the least CPU usage).
Now I use the standard governor (248 - 600) and I thing my idle power drain is OK.
I guess I will test a governor that is plain 600MHz and one wit 320 or 480 as a minimum, in order to see if power drain is higher when using a lower lag configuration.
And, just as a guess, if background tasks are triggered by timers, a governor with just 600MHz (or 320 - 600 or 380 - 600?) could (just a wild guess) mean that background tasks take less time to execute, and leave the CPU to si more in IDLE mode, causing a very similar power drain as an extreme power saving governor. But this is just a guess, i have not tested it yet. And it also depends on what apps you have (what the apps do when phone is sleeping).
Basically, my best advice would be to watch the apps (after you install a new app, wait for a night to see if the new app causes a higher drain; if it does, search for another app that does the same thing)
spaic said:
As far as I can remember from school, a logic gate uses more power when switching, thus a higher frequency would also mean higher power drain (higher frequency = more switching of the logic gates), without voltage modification.
Voltage is changed in order to keep stability - higher voltage means a more stable logic signal, and a faster switching gate, and thus people reccomend using a higher voltage for higher frequencies/lower voltage for lower frequencies.
Thus, a CPU with so many logic gates does not operate just like a simple resistor. In fact it is worse, because when you use higher voltage AND higher frequency power drain is increased much more.
On the other hand, most modern CPU's simply deactivate CPU regions when idling, so, in case of our hardware (constant voltage) there should not be such a great difference when idling (most of the CPU is powered down). The only thing is for the phone to be REALLY idling (no background tasks eating too much of the CPU when screen off).
Basically, what this means is that if you want extreme power saving use a governor with 128MHz minimum and have as few background services as possible (or at least the ones that are there should be optimized for the least CPU usage).
Now I use the standard governor (248 - 600) and I thing my idle power drain is OK.
I guess I will test a governor that is plain 600MHz and one wit 320 or 480 as a minimum, in order to see if power drain is higher when using a lower lag configuration.
And, just as a guess, if background tasks are triggered by timers, a governor with just 600MHz (or 320 - 600 or 380 - 600?) could (just a wild guess) mean that background tasks take less time to execute, and leave the CPU to si more in IDLE mode, causing a very similar power drain as an extreme power saving governor. But this is just a guess, i have not tested it yet. And it also depends on what apps you have (what the apps do when phone is sleeping).
Basically, my best advice would be to watch the apps (after you install a new app, wait for a night to see if the new app causes a higher drain; if it does, search for another app that does the same thing)
Click to expand...
Click to collapse
I don't know about CPU's as much as u, but simple logical thinking helps here.. Low frequency + minimum of bg tasks = great power saving, I have now used the phone for 36hours without charge, 61% battery left. That is not only idling, i write about 50 to 150 sms a day & use the phone for other stuff too. So, those governors & frequencies i mentioned earlier in this post, helps a lot.
fransisco.franco thinks otherwise read the his post that contains the link to his rom devoid.francov6(ROM is cool btw and unfortunately i have a slow sdcard )
I think the first post is by far the best I have seen so far.
Sent from my LG-P500 using Tapatalk
Wow, only 1% all night?
I'll take a deeper look at your tips!
I use devoid.franco with franco.kernel v12. From all ROMs I've isntalled, it's the best: great performance and long battery life.
I get 5% battery drain in 7:30 hours (at night), without doing anything special, without running a custom ROM and without uninstalling apps. I just make sure GPS, Bluetooth, WiFi and data are off before going to bed.
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
leedavis said:
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
Click to expand...
Click to collapse
Interesting point you raise actually.
I've just installed Setcpu and used the on demand governor. I left the values as default (200mhz for minimum and 1.2 ghz for maximum) - with no overclock.
I've immediately noticed swiping through the screens is a bit smoother and the biggest improvement is the gallery. All my photos appear much smoother. Before the gallery app was a bit lagy.
I haven't set any profiles yet such as screen off.
Every Android phone I've owned scaled the cpu, I think they all do. I've found that with setCPU my battery gets drained much faster en no real benefit in smoothness.
jzuijlek said:
Every Android phone I've owned scaled the cpu, I think they all do. I've found that with setCPU my battery gets drained much faster en no real benefit in smoothness.
Click to expand...
Click to collapse
Have you tried this yet though on the Galaxy S2?
There is definitely less lag than before - as stated, specifically in the gallery app. Just generally swiping feels more responsive as well. Battery is still pretty awesome, especially when using Lightening Rom 1.1 and the Android battery calibration app.
Hmm. I'll try SetCPU on the SGS2 and post back the findings (Performance+Battery).
I don't know how can it get any more smoother, I mean its already SO smooth!
there are many points to use setcpu on gs2:
-for some reason I dunno, gs2 can't manage it's 1.2ghz without gettin too warm. downclock and get rid of the burn effect.
-gs2 sports a good management of gpu (it does most of the work and setcpu doesnt down\overclock that). downclockin doesnt affect UI or video o browsing experience at all. can even downclock at 500 max speed without any sides.
-the only side u ll see it's benchmark (quadrant downgrading to 2000) but I hope u won't pay attention to such an unseful thing. benchmark doenst mean nothing, daily usage it's the only point to look at.
my settings: conservative, 200min 800max.
battery draining doesnt belong to setcpu this time, look to other settings.
alexleon said:
there are many points to use setcpu on gs2:
-for some reason I dunno, gs2 can't manage it's 1.2ghz without gettin too warm. downclock and get rid of the burn effect.
-gs2 sports a good management of gpu (it does most of the work and setcpu doesnt down\overclock that). downclockin doesnt affect UI or video o browsing experience at all. can even downclock at 500 max speed without any sides.
-the only side u ll see it's benchmark (quadrant downgrading to 2000) but I hope u won't pay attention to such an unseful thing. benchmark doenst mean nothing, daily usage it's the only point to look at.
my settings: conservative, 200min 800max.
battery draining doesnt belong to setcpu this time, look to other settings.
Click to expand...
Click to collapse
IT IS TRUE. I agree with every single line you wrote, it is just my expericence.
I have too setcpu conservative and undercloked 800 Mhz.
There no slow down or lag at all... But I am wondering if it gives a real boost to battery life. I am not sure of this.
I'll keep you guys posted... But I think that an undevolted Kernel it is really a need as for the solution of the damn dual core ginger bug that is sucking 20% of my battery every day
Well,from my experience with my Desire and Desire HD(won't even bother with the Hero,I had no real knowledge then),governors can make a huge difference.I for one like smartass or interactive governors(mostly the same).I wouldn't suggest conservative,interactive does the job much better.Tasks get done in less time and the CPU throttles down more quickly.Other than that,you can underclock or overclock all you like,it never made any big difference in battery life for me(Unless Sammy's CPUs are different in that aspect-Snapdragons are really "overclock-friendly").That's personal preference after all!
Anyway,the best solution IMO would be a vdd_levels interface.For those who don't know what it is,it is a mod made by -snq(Meet him at the Desire forums-That guy's a true LEGEND!He can patch/modify anything!),which practically allows you to change the voltage levels of the CPU on the fly rather than having to stick with the values hardcoded into the kernel.Using this and a simple script in GScript to change values that won't survive reboot or in init.d to be applied on boot,you can find the optimal voltages for your CPU(Don't forget,every CPU is unique and different),thus reducing heat and maximizing battery life.
If a dev brings that to the SGS2 it will be a big step in the right direction as far as I'm concerned.
I use SetCPU without issue, but only to run profiles (i limit the device to 500mhz when the screen is off). The rest of the time it scales itself up to 1.4GHz without fuss and using stock voltage. Battery life is fine, best ive had for an android device.
Wow, I've taken SetCPU off but left JuiceDefender on and my battery life is fantastic. At 70% after slightly heavier than normal use (used for listening to music for a couple of hours this morning) and been off charge for 8.5 hours.
SetCPU seems counterproductive on SGS2
leedavis said:
I use SetCPU to help battery life but someone told me it's not needed on the SGS2 as it already scales CPU for demand. True?
Click to expand...
Click to collapse
I did set ondemand which is a little more reactive and slightly smoother.
Though System Tuner is less cpu-consuming and much more useful on the SGS2. No need for all those complicated settings from setCPU. Only changing governor and changing frequencies on standby are useful.
leedavis said:
Wow, I've taken SetCPU off but left JuiceDefender on and my battery life is fantastic. At 70% after slightly heavier than normal use (used for listening to music for a couple of hours this morning) and been off charge for 8.5 hours.
SetCPU seems counterproductive on SGS2
Click to expand...
Click to collapse
Juice Defender uses as much battery as it saves this is fact, i have SepCPU set to 200 Min - 800 Max - On demand and have Juice Defender Ultimate and i thought it was great but it was recommended to me that i could save more battery by not using this, initially i was skeptical but tried it and i was astonished at the results, my battery life improved by 9 hours (i carried out a test with JD and without)
Anyone who says SetCPU uses up loads of battery is talking nonsense,it actually saves battery if configured correctly.
I am using Check Rom with set CPU I have it 1.2ghz max and 200. Using conservative governer. I been off charge for 15hrs, however I am using light usage I am on 72% screen on has been 5h 25m at time of writing. Not yet calibrated the battery.
jonny68 said:
Juice Defender uses as much battery as it saves this is fact, i have SepCPU set to 200 Min - 800 Max - On demand and have Juice Defender Ultimate and i thought it was great but it was recommended to me that i could save more battery by not using this, initially i was skeptical but tried it and i was astonished at the results, my battery life improved by 9 hours (i carried out a test with JD and without)
Anyone who says SetCPU uses up loads of battery is talking nonsense,it actually saves battery if configured correctly.
Click to expand...
Click to collapse
What are the settings are you using for the setcpu program in your S2?? Did you remove the Juice defender application?
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?
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.
Just want to know everyones opinion on if it can really save life for the S4. Cause the way I see it is if the cpu is constantly being clocked down/up for instance, when my screen is off I have it so that cpu is at about 400mhz and when the screen comes on it boosts back up to anywhere between 1200 and max
If you're driving, and you slow when down to say 30mph and slam on the gas to get up to 100mph instead of steadily getting there, you're going to use a lot more gas. So if it is the same with the phone, aren't I using more battery life than saving?
Markymarc206 said:
Just want to know everyones opinion on if it can really save life for the S4. Cause the way I see it is if the cpu is constantly being clocked down/up for instance, when my screen is off I have it so that cpu is at about 400mhz and when the screen comes on it boosts back up to anywhere between 1200 and max
If you're driving, and you slow when down to say 30mph and slam on the gas to get up to 100mph instead of steadily getting there, you're going to use a lot more gas. So if it is the same with the phone, aren't I using more battery life than saving?
Click to expand...
Click to collapse
I'm not entirely sure, but with your example, doesn't that depend how long you're going 30 or how long your screen is off at a crack? If you turn on your screen for 10 minutes for every 20 it's off, I think it would save your battery more in the long run.
You use more gas in the car analogy as you have to overcome a ton or so of mass driving at 30 mph. Changing clock speeds faces no such resistance, so it won't be the same with the phone.
yes, the acceleration doesn't really affect the drain. the fact you're running at a higher clock speed is the drain. you can adjust your steps and max speed, thus saving a little bit of battery. undervolting can help to, but the cpu usually draws so little power that the savings may go unnoticed.