As the title says, is it really worth? I mean, should i decrease my phone maximum clock speed of the cpu by, like, 100-200 mhz in order to notice less battery consumption?
thanks
You can decrease the cpu clock speed for better battery life. But don't decrease to 100-200 mhz. It can cause constant random reboots and make your device very unstable.
Really? I'm using my s3 neo with a clockspeed of 1.3 ghz instead of 1.4, and i'm rarely noticing strange things
Related
What are the best settings to have you phone's CPU speed set at? I'm looking for both good performance and good battery. Also I am using the default overclocker, what is the best one? Thank you guys for your time.
Sent from my LG-VM670 using XDA Premium App
I use SMARTASS as my CPU speed governor and I set my CPU to 480-748 MHz, seems pretty stable for me.
Sent from my LG-VM670 using xda premium
thaunknownartist said:
What are the best settings to have you phone's CPU speed set at? I'm looking for both good performance and good battery. Also I am using the default overclocker, what is the best one? Thank you guys for your time.
Sent from my LG-VM670 using XDA Premium App
Click to expand...
Click to collapse
Overclocking values differ from phone to phone. Test it out with different values and use the one which is stable for you.
This was just discussed in the IHO technical-discussion thread, as a matter of fact.
My phone is stable for most stuff at 806 MHz, but sometimes the camera will cause a freeze/reboot. So I run at a 786 MHz max. Your phone will be different; this has to do with minute physical differences between individual chips.
The thing to keep in mind when overclocking is that the processor in our phone (unlike those of many other phones) does not make use of dynamic voltage scaling. There are only two voltage levels: a lower one if the phone is running at or below (or is it just below? correct me if I'm wrong, guys) 480 MHz, and a higher one if the phone is running above. So below 480 MHz, the system will give the processor a certain amount of voltage (period), and above, the processor will get a certain higher amount of voltage (period).
Because of that, the tests that have been done indicate that 806 MHz is the sweet spot for battery efficiency when the phone is in use--and the closer you get to 806, the better. Thus, I've had the following settings for quite some time:
786 MHz min
786 MHz max
Performance governor
which has treated me pretty well. On a day of light to moderate use, I'd end up with 65-75% battery left (occasionally more like 80%), depending on cell signal where I am et al. And it gives me probably the best performance I'm gonna get out of this phone.
However, I very recently decided to change the minimum to below that 480 MHz threshold and see what a lower voltage when idling would do for my battery life. My current settings are:
320 MHz min (may change to 480)
786 MHz max
Smart*** governor
There is actually a noticeable performance decrease when I first wake the phone up, so I may switch governors as well. In any case, I've had those settings for only one full day now, but for that one day the battery life was noticeably better. I'll post an update when I've had a few more days to test.
As always, it's difficult to quantify battery life in a reliable/rigorous manner (much less a universally applicable one), so YMMV.
I've install Rom Toolbox,
and i saw there is a "CPU slider" where i control the clock speed.
i've put it to 1000MHz instead of 1200MHz and tested it for several days
i really dont feel any difference in performance.
browsing seems same, games like asphalt is equally smooth.
heating is similar, equally warm.
the only difference is quadrant benchmark.
1200MHz scores 3200-3400
1000MHz scores 2600-2900
frankly speaking, i'm not sure if there's any difference in battery life.
is there any way to accurately test whether the clock speed affects the battery life?
i've seen other threads, where there are very different opinions.
some say it will improve battery life, and some say its worst.
http://forum.xda-developers.com/showthread.php?t=726019
Quote: (SetCPU doesn't make a difference in battery life, it can only shorten it. The kernal already has the best settings for CPU speed built in.)
http://forum.xda-developers.com/showthread.php?t=1305465
Quote: (if you are able to stand the side effects of underclocking, it will surely boost your batery life.)
On my SGS2 program called CpuSpy shows that 1200MHz is about 1% of total cpu time (remember that governor is ondemand and CPU is at 1200 only when need it). If power consumption is directly proportional to clock speed by limiting it to 1000MHz you will get about 20% less power usage by 1% of time... looks like 0.2% power saved ? Soo if Your phone works for about 48h on one charging this way You can get about 6 extra minutes. It's just my guess...
Also have to consider if slower cpu causes screen to eat power for longer time... (because You have to wait longer for operation to complete)
slig said:
On my SGS2 program called CpuSpy shows that 1200MHz is about 1% of total cpu time (remember that governor is ondemand and CPU is at 1200 only when need it).
If power consumption is directly proportional to clock speed by limiting it to 1000MHz you will get about 20% less power usage by 1% of time... looks like 0.2% power saved ? Soo if Your phone works for about 48h on one charging this way You can get about 6 extra minutes. It's just my guess...
Also have to consider if slower cpu causes screen to eat power for longer time... (because You have to wait longer for operation to complete)
Click to expand...
Click to collapse
HI, thanks for replying. I understand what you mean. the phone dont operate at 1200MHz all the time. but when using browser, and playing games, such as asphalt, it runs at max CPU usage almost the entire gaming duration.
Anyway.....
the real question is whether the clock speed is directly proportional to the battery consumption.
while reading your post, i thought of a brilliant ideal how to verify this.
the CPU slider not only allows you to set the max CPU speed,
you can set the min CPU speed as well.
So, i thought of an experiment, lets set the min & max CPU to 1200MHz,
this way, the phone will be running constantly at max CPU even when its idle.
let the phone be turn on till it run out of battery, record the time, T1.
then repeat again with max and min CPU set to 1000MHz.
record the time it is turn on till it run out of battery, record time as T2,
then compare T1 & T2, this could certainly work.
it would be nice if any member here happens to have 2 sgs2, and tried them ;-)
There are two more things to consider
1. CPU is not the only element that consumes power.
2. SGS2's Exynos is always clocked at 200MHz when the screen is off - check if this minimum slider affects that too.
Please let know how your experiment goes.
Regards
when the screen is off, the phone will be in "deep sleep" state. i think thats less than 200MHz.
anyway, i wont be doin this experiment any time soon.
you see, this is my only phone, i need to use it.
i dont have much oportunity to leave it and wait for it to run out of juice.
still, i'll try it when i have the chance.
Just to let you know ahead of time, I know how to overclock & undervolt
My question:
Should I notice better battery life with 1400MHz @ 1275mV or 1200MHz @ 1275mV?
Even more basic - "With my voltages the same, but clocks higher, will I notice less battery life?"
My thoughts:
Not using more mV than a stock 1200MHz, so I shouldn't notice anymore drain
Should be finishing tasks faster - Saving Battery Life
So I shouldn't be noticing any more drain then stock, but it is faster.I do notice a difference in speed between 1200 & 1400MHz, otherwise I would just use 1200MHz @ my current stable of 1200mV.
Overclocking/Undervolting
You might want to grab SetCPU or Pimp My CPU from the market and memorize some different CPU profiles that would allow you to test and see the results of what you want to do.
I flashed the cm7 1.4 240-325-300 Kernel.
In my settings what should I keep my min and max at for all time usage?
I max them and my quad score is like 5501
don't know if your supposed to keep those certain.
Also does decrease or increase battery life.
I left mine at the default values. Was wondering this myself though. How do you test quad scores?
Download quadrant standard from market
Sent from my MB855 using XDA App
You want the lowest value to be at the lowest(216 i think) because this allows the processor to idle at that low speed, if you keep the minimum speed at 1ghz your processor will ALWAYS be running 1ghz at the lowest, and that will be an obvious way to kill your battery in no time. So set that to the lowest, and for the maximum i personally run mine at 750 for CM9, think i had it at 800 for CM7 but cannot remember for sure. This is limiting how fast the processor can run so the lower the better as far as battery goes. It comes down to you personally, if you game and do processor heavy tasks often then having the processor underclocked like i run mine will affect your gaming/app/overall experience. Its always like 2 clicks away to bump it up to a higher speed and i have a link on my home screen so if i do decide to do anything processor heavy i can bump it up quickly. But in general it takes more power for your processor to run higher so if your really concerned about battery life try bringing it down. I can still score a solid 1,500+(with a bunch of crap installed on my Photon mind you) on CM9 with my max at 750 and min and 216. Benchmarks are honestly just a number, it comes down to how if performs for you and what you are doing with your phone.
Awesome, I'm lowering it now and battery is dropping slow so its good, thanks for the detailed reply.
Sent from my MB855 using XDA App
Hi.
I noticed the S5 is much snappier when the minimum clock frequency of 128 MHz is not used (245 instead).
Did you notice the same pattern?
Is there a drawback in battery consumtion?
lordofazeroth said:
I noticed the S5 is much snappier when the minimum clock frequency of 128 MHz is not used (245 instead).
Click to expand...
Click to collapse
what is the point using such low frequencies? Most of the power usage is from the screen. I'm not quite sure, but I think remembering some study that shows, the power consumption on HD2 is optimal around 450Mhz. So why bother with 128 vs. 245?
now that you mention it... 245mhz is much responsive when the wake up from deep sleep... so, yeah.. 128mhz is not good for stability... even the battery saving is not much different when using 245..
actually i have abandon default 128mhz quite some time now...