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.
Related
Yesterday I thought I would test my battery life if I left my clock speed at 806 MHz, It lasted over 24 hours with no real speed decrease... I am requesting that a developer makes a kernel that is underclocked to 806 MHz and undervolted as much as possible so we can see how much battery life we can pull out of this thing.
take intersectRavens 800mv (or 925) kernel and underclock via setcpu?
lower than 800mv won't be possible, even 800mv is too low for me, it uses more battery cause data connections is very unstable. 925 gives better battery life for me.
IR kernel supports conservative governor too.. works great for me.
yeah just use set cpu to underclock the device. all these kernels already have the lowest voltages for each cpu frequency. but once again, the lower the voltage, the lower your signal strength, and if you signal strength gets too low, your phone will boost voltage to the radio to try to increase it and it will end up using more power. this is why many prefer the 925mv kernels as opposed to the 800mv ones.
this is my understanding, please correct me if i am wrong.
nellyspageli said:
yeah just use set cpu to underclock the device. all these kernels already have the lowest voltages for each cpu frequency. but once again, the lower the voltage, the lower your signal strength, and if you signal strength gets too low, your phone will boost voltage to the radio to try to increase it and it will end up using more power. this is why many prefer the 925mv kernels as opposed to the 800mv ones.
this is my understanding, please correct me if i am wrong.
Click to expand...
Click to collapse
I wasn't sure, that's why I said lowest possible. So I think I'll just do that, but from what you said I'm now wondering if we can OV the radio's voltage from the kernel to fix the 3g/speed problems...
will it work on froyo? i have CM6alpha1
link to the kernal to use and setCPU settings please (including profiles) much appreciated!
I was just wondering what people get for battery life with miui 1.7.8 and OTB .13 kernel.
Also, what does overclock actually mean? Does it mean that setting the min and max to 1400Mhz in Voltage Control or remain the min to 100 and max to 1400Mhz?
I'm currently on noop, ondemand and min=100Mhz, max=1400Mhz with nothing UV'ed.
Please help me to get better battery life!!!!!!!!
Your CPU by default can do, unmodified, a certain number of commands per second. These commands are measured in Hertz, thus a 1GHz processor does about 1 billionish commands per second. Overclocking means you allow your processor to do more commands in the same time frame. The downside to this, however, is that more electricity is flowing through the CPU, thus draining the battery more. Having a lower clock speed will save some battery life.
That being said, I have kept my CPU clocked at maximum of 1GHz, with the I/O Scheduler set to deadline and the CPU Governor set to smartass, and I'm getting about a day out of my battery, maybe a little less. I have no idea if that's the "optimal" battery saver setting, but it works for me.
I do have a question, though... What do those two settings mean, anyway?
1n73rn37_j3d1 said:
Your CPU by default can do, unmodified, a certain number of commands per second. These commands are measured in Hertz, thus a 1GHz processor does about 1 billionish commands per second. Overclocking means you allow your processor to do more commands in the same time frame. The downside to this, however, is that more electricity is flowing through the CPU, thus draining the battery more. Having a lower clock speed will save some battery life.
That being said, I have kept my CPU clocked at maximum of 1GHz, with the I/O Scheduler set to deadline and the CPU Governor set to smartass, and I'm getting about a day out of my battery, maybe a little less. I have no idea if that's the "optimal" battery saver setting, but it works for me.
I do have a question, though... What do those two settings mean, anyway?
Click to expand...
Click to collapse
What do you mean by two settings?
Like, what are I/O Schedulers and CPU Governors? That last question was me hijacking the thread.
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.
I don't know if this is tandard on all kernels but on my kernel for example the steps are like that:
1000mhz=1175mv
1100mhz=1225mv
1200mhz=1275mv
Now at THIS point it starts getting weird. Suddenly the voltage increases by 25mv each
1300mhz=1300mv
1400mhz=1325mv
then it's 50 again
1500mhz=1375mv
then 25 again
1600mhz=1400mv
I know a bit about overclocking and overvolting CPUs. And I know that the higher you go the bigger the steps to increase voltage have to be (assuming you always choose the lowest voltage possible on which everything is stable). That's just due to physics. And now the opposite is the case... Why is the step from 1,5ghz to 1,6ghz only 25mv but from 1000 to 1100mhz it's 50mv? This doesn't make much sense.
Seriously no wonder that my phone is instable on 1600mhz. I guess the voltage just isn't high enought so the transistors aren't able to do their job properly within that short amount of time they're given at 1,6ghz.
Are the voltage steps like that on every kernel?
Frozenthunder said:
I don't know if this is tandard on all kernels but on my kernel for example the steps are like that:
1000mhz=1175mv
1100mhz=1225mv
1200mhz=1275mv
Now at THIS point it starts getting weird. Suddenly the voltage increases by 25mv each
1300mhz=1300mv
1400mhz=1325mv
then it's 50 again
1500mhz=1375mv
then 25 again
1600mhz=1400mv
I know a bit about overclocking and overvolting CPUs. And I know that the higher you go the bigger the steps to increase voltage have to be (assuming you always choose the lowest voltage possible on which everything is stable). That's just due to physics. And now the opposite is the case... Why is the step from 1,5ghz to 1,6ghz only 25mv but from 1000 to 1100mhz it's 50mv? This doesn't make much sense.
Seriously no wonder that my phone is instable on 1600mhz. I guess the voltage just isn't high enought so the transistors aren't able to do their job properly within that short amount of time they're given at 1,6ghz.
Are the voltage steps like that on every kernel?
Click to expand...
Click to collapse
I'm on Siyah 2.6.14 Voltage Control setting as follow:
I/O = bfq & Governor = ondemand
1600Mhz - 1500mv
1400Mhz - 1300mv
1200Mhz - 1200mv
1000Mhz - 1100mv
800Mhz - 1000mv
500Mhz - 950mv
200Mhz - 900mv
100Mhz - 900mv
I've applied these setting as default at bootup with no problem.
OC to 1600Mhz + set to Performance gives me 6800-6990 benchmark score in Antutu.
Which kernel are you on?
Siyah 3.2
I see you are using 1,5V on 1,6ghz. Maybe that's why you running stable?
When I set max clock to 1,6ghz and 1,4V at that clock then I get random app crashes/freezes... Once I tried shutting down my phone and it made some very loud and creepy noise... Some very loud beeping. It was definitely not the shutdown sound of the rom.
On my stock rom I just get random reboot.
Can you also permanently work on 1,[email protected],5V (setting min clock to 1,6ghz) without freezes/crashes?
Also funny that at 1400mhz you are on 1,3v while standard on siyah 3.2 is [email protected],4ghz
While 1600mhz is lower voltage again.. This is messed up
Frozenthunder said:
Siyah 3.2
I see you are using 1,5V on 1,6ghz. Maybe that's why you running stable?
When I set max clock to 1,6ghz and 1,4V at that clock then I get random app crashes/freezes... Once I tried shutting down my phone and it made some very loud and creepy noise... Some very loud beeping. It was definitely not the shutdown sound of the rom.
On my stock rom I just get random reboot.
Can you also permanently work on 1,[email protected],5V (setting min clock to 1,6ghz) without freezes/crashes?
Also funny that at 1400mhz you are on 1,3v while standard on siyah 3.2 is [email protected],4ghz
While 1600mhz is lower voltage again.. This is messed up
Click to expand...
Click to collapse
I face lots of apps crashed/Forced closed before someone refer me to here:
http://forum.xda-developers.com/showthread.php?t=1466017
Take a look....
i neva do oc , but had tried ov an phone simply was not stable as out of the box.as my sig says iam good wiv 520 apps right now wiv decent batt life and good speed,only thing u got to kno wat ur phone can handle..
First of all, I am totally new to this forum.(I mean as an registered user)
Before that I always had the thing from the forum what I needed.
Now here is my question,
If i overclock the processor speed of my android device to a higher position, isn't it gonna take more battery power than usual?
Phone model: Xperia Live With Walkman
Boot loader: unlocked
Root Access: Rooted
Kernel: Rage 3.2
ROM: Real ICS r6
overclocking is going to drain your battery obviously.
overclocking drains more battery but gives better performance,too much over clocking makes phone heat & even hardware issues
saqib nazm said:
overclocking drains more battery but gives better performance,too much over clocking makes phone heat & even hardware issues
Click to expand...
Click to collapse
My phn's original capacity is 1 Ghz
How much overclocking can keep my battery level fair and also give smoother performance without causing me any hardware issue?
Btw, Thx for the ans.:good:
Saimoon said:
My phn's original capacity is 1 Ghz
How much overclocking can keep my battery level fair and also give smoother performance without causing me any hardware issue?
Btw, Thx for the ans.:good:
Click to expand...
Click to collapse
Power consumption = Voltage x Voltage x cpufreq x some constant for your device. If you OC (raise the cpufreq) you will have more power consumption and more heat generation because most of the power is dissipated as heat and the heat is what damages your cpu. It is probably impossible to kill your cpu in one go, because your device should shut off when it begins to over heat (this will look like a random reboot). But you will slowly degrade the over all performance of your cpu and eventually you get to a point where you see a lot of random reboots. So if you decide to OC you probably want to also undervolt as well. This is because power consumption (and heat) scale with the square of the applied voltage. One rule of thumb is that your maximum cpufreq is actually determined by the voltage. For example, my cpu is rated to be stable at 1 GHZ and 1200 mV, so when I OC and UV, I scale the cpufreq as high as I can go, as long as the voltage is not greater than 1200 mV, for me this is 1.5 GHz.
Also remember that your cpu governor will have a big effect on your power consumption and it is probably doing a good job keeping the cpu running in the low range of the cpufreq table, so you are unlikely to see big effects of OC or UV on real life battery consumption.
every chipset is different, even though the brand and model is the same. noone can guarantee you any safe value to overclock.
Thanks Giving!
Thanks Everybody for helping me out!
I am applying 1.402 GHz :laugh:
Overclocking is not the only thing you have to think of in order to improve your phone's overall performance. The most important issue for me is choosing the right kernel and applying the right governor + I/O scheduler. From my experience with Mini (i have tried ALL available kernels and most of ROMs) I can surely say that now with my phone (ICS .587, custom ROM + kernel) overclocked to 1.5 GHz battery with minimal use (20 mins calls, 40 mins WiFi per day) lasts at least 60 hours. When I bought my phone (GB, no OC, all stock) battery was struggling to stay alive for 24 hours with the same minimal use. Conclusion: first pick the right kernel and ROM, then OC.