If I can undervolt my CPU to run 600MHz at a lower voltage than stock runs 300, any reason I wouldn't set my min to 600?
In trying to avoid some of the "wake-up" issues people have experienced, I've been running 400/800/1200 today, and it seems stable...
No reason why you couldn't, but because you could set it to lower than stock voltage, by that reasoning you could set it even lower by undervolting at 300mhz, therefore you're still losing out on a potential power saving
Related
hi there.
I've been tinkering with voltages and cpu frequencies lately.
I noticed that, with stock voltage values, i have "900" for 122, 245 and 368 mhz.
Now the question is, leaving governors aside for a moment: if i set cpu minimum to 122 or 368, there shouldn't be any battery drain differencies, since they both have the same voltage value.
But technically if i have some background stuff going on, with screen off or when the phone is idle, they will be processed faster with 368 mhz, while with 122 they will take longer to carry on or even force the phone to work to get to a higher frequency to finish the task.
Now i maybe saying a lot of bullcrap since i'm not a developer nor a hardware guy,
but if what i said is true, then in theory it would not be the same if i put minimum to 368, it would actually be better for performance AND the battery??
No, as I have learned from another user here; even if the voltage is the same, the power draw is still different. 122mhz will still use the least amount of power
Hello,
Just wondering if anyone has experimented with Tegrak Overclock Ultimate's GPU optimization settings. It allows you to undervolt the GPU. Has anyone tried this and is there any benefit to battery life savings with this? I am playing around with the settings right now, so I'll post my results later. So far been able to undervolt the 267 mhz step by -75mv from 1000mv down to 925mv (900mv is unstable for me). And I undervolted the 160 mhz step by -150mv from 900mv down to 750mv. There is also a 200 mhz step I haven't played with. Perhaps keeping the GPU at 200/160 can yield potential battery savings when playing games because games drain the battery so fast.
Hm. I seem to be able to undervolt the 200 mhz step to 750mv as well. I'm going to run a 200/160 gpu setup at 750mv and see if I can save any battery playing Gun Bros and will let you guys know.
caaznkid said:
There is also a 200 mhz step I haven't played with. \
Click to expand...
Click to collapse
Really? I only have the 267 and 160 MHz clock settings available. Any thoughts anyone?
Oh, I have underclocked my GPU settings but only by a modest 25mV each.
There's only 2 steps, but u can change the clock between 160, 200, and 267
yep ... good results
Yep I've been experimenting with GPU undervolting and had some sucess. So I was methodically working downwards and testing stability... then i saw this thread and thought what the hell, right? I shot for lowest mv of 750 and it's rock solid at 200mhz.
Can confirm 750mv stable at 100, 134, 160 and 200mhz. 267mhz can't be undervolted that much.
I've locked 200mhz 750mz for both speed steps and left it at that. Phone has yet to display any instability in a couple of days of mixed use including gaming. Battery life better? Subjectively yes, mostly I notice phone doesn't get so hot playing Dead Space.
Power consumption scales down almost linearly with clock cycles, and exponentially with voltage (right?). So by my math GPU is using about 40% of the power it does at full 267mhz. I wonder what the TDP of the exynos 4210 is and how much the Mali 400 contributes to that, would give some idea of what battery life to expect. Since GPU sits idle a lot, I doubt it's a magic fix.
Such is the power of our phones I have to underclock the CPU and GPU quite far before any 3D game gets too choppy to play. 160mhz is more than fine for most.
Usually undervolting makes the most sense for power saving because a given computing workload takes a certain number of cpu cycles. But 3D usually tries to render as many frames as it can, with the exception of S2's 60fps frame cap. So slowing down the GPU to no more than you need might improve gaming battery life?
My SGS2 is a bit sensitive to undervolting although underclocking of CPU, so I'm happy be able to so agressively undervolt the GPU.
I'd be interested to know who else can just set 200mhz & 750mv and have it rock solid? If not, 200/800 or 160/750?
I've rarely had problems when I use Tegrak. Then again, I undervolt 100mv on my cpu between 200-1000mhz, and about 50mv on my GPU at 267mhz with the noop scheduler and tweaks enabled. If I can get Tegrak to work with the Gunslinger kernel (currently causes reboot loops when I load the overclock module), I'll report back on battery life with Tegrak and experiment a little more.
jyaworski said:
I've rarely had problems when I use Tegrak. Then again, I undervolt 100mv on my cpu between 200-1000mhz, and about 50mv on my GPU at 267mhz with the noop scheduler and tweaks enabled. If I can get Tegrak to work with the Gunslinger kernel (currently causes reboot loops when I load the overclock module), I'll report back on battery life with Tegrak and experiment a little more.
Click to expand...
Click to collapse
I had the same problem with Gunslinger, I decided to keep my phone on Rogue Stock EL29.
I've been able to drop my GPU Level 0 Clock to 160mhz and voltage to 850mv with out any issues.
I also keep my GPU 1 Clock at 100mhz and my voltage at 750mv without a problem.
Using noop of course.
Changing GPU clocks and volts doesn't help much.
Keeping your CPU Internal Voltage and Core Voltage -50mV and keeping it scaled 200-800 MHz will give you much better battery.
I think the effect would be more significant in ICS since ICS use GPU to render UI
Hello!
I recently noticed how frequencies 122MHz through 460MHz all employ the same voltage (900mV). I've come to understand that the higher the CPU frequency the faster your battery will drain. What I don't understand is why a higher frequency will drain your battery faster.
Is the only cause for higher battery drain when running a higher frequency, the higher voltage which comes with a higher frequency, or are there other factors?
If, then, a higher voltage is the only cause, then my battery would not drain faster if I clocked my minimum frequency at 460MHz instead of 122Mhz?
Thanks in advance to anyone who can shed some light on this!
Hi
cpu power consumption at a specific frequency is bound to its voltage.
you should test a voltage for a frequency while your device has 100% workload, because you could find a voltage so that your device is stable while being idle, but freezes when it needs to work. (for more information search for linux phc)
my conclusion:
the voltage for a specific frequency has minimum!
you can set your minimum frequency to 460 if you want to, since the screen consumes most power, it should not matter that much. i have set my minimum freq that high, too. I believe that way, my phone needn't raise the frequency when dooing simple stuff, like playing music.... but i am just guessing.
i theory it must get hotter than at lower frequencys, but i did not notice that.
i have had a palm pre and a custom kernel introduced a voltage on demand governor, which kept the device at 1ghz all the time, but changes the voltage with the workload. i think the developer of the awesome idea is "unixpsycho" ... i would like to see something similar on android.
greetings
matto
EDIT:
http://en.wikipedia.org/wiki/Dynamic_frequency_scaling
it looks like it is bound to the frequency, too!
~const*f*V^2
the Voltage is quadratic, that means it tkes a higher priorety.
e.g. lowering the voltage from 900mv to 800mv => (0.8^2)/(0.9^2) ~ 0.79
460mhz*0.79~363mhz
=> [email protected] consumes as much power as [email protected] (Stock)
So I tried to underclock my One X to around 640 MHz and it was running VERY smoothly and stable with only 2 cores active. I was using the ViperX 2.2.1 ROM and the Kernel was the no OC NCX 0.99a. The battery life wasn't bad, but has anyone tried underclocking to 1 GHz or lower? If so, how is the battery life and what kernel and ROM did you use?
With SetCPU you can change the max. CPU, but why should you? When the phone doesn't need much processor power, it just scales down by itself.
So, it already has the best underclocker there is.
Mayby you could try undervolting to save even more battery, but that means the CPU can be somewhat less steady.
im trying to get my head around UVing / UCing my HOX. is there any guide around? im trying to search through the forum but still no luck.
ricopoetra said:
im trying to get my head around UVing / UCing my HOX. is there any guide around? im trying to search through the forum but still no luck.
Click to expand...
Click to collapse
underclocking means the CPU runs slower so should use less battery but slower CPU speeds also means to takes longer to preform tasks which could use more battery, check on google most places say its not worth it as that battery saved is tiny and not worth the drop in CPU performance.
undervolting however lowers the voltage that CPU uses while working this does save power and also lowers heat (less voltage less heat) but if you lower it to much then the CPU becomes unstable due to lack of power and well crashes and restarts the phone in most cases.
to get the best out of undervolting you need to lock the max CPU speed to each step (CPU speed, 300mhz, 600mhz and so on) and slower the voltage and then run a bench mark (like antutu) and see if its stable, if it is you lower the voltage again and repeat until it crashes at which point you have found the lowest voltage that the clock speed can handle so you jump up a voltage then more on to the next speed.
it takes along time but that would get you the best undervolt your phone and hardware could handle.
or you can just use the global to lower the voltage for every speed, this is much faster and much less time consuming but you don't get the most out of it.
for this you basically drop the voltage then use your phone for different things; browsing, games, benchmark and see if it crashes if not lower again till it does then go back up a step.
thanks for explaining. I'm getting some of the points that I missed Awhile ago. I guess I'm going to try the longer way of doing it.
Sent from my White HOX JB PA 2.10
I've been playing around with undervolting my Epic 4G with SetCPU and Voltage Control and have noticed that it does not crash if I force it to operate at one frequency -- apparently it is the switching from frequency to frequency at too low a voltage that crashes it. But what I'm seeing seems absurd -- I can overclock to 1200 MHz and set voltage to the 600 mV minimum and run just fine, so long as set the minimum to 1200 MHz as well.
I've run benchmarks with SetCPU and it definitely is running faster at the 1200 MHz setting. I am wondering if the 600 mV is "real" or if perhaps SetCPU and Voltage Control are misreporting what the CPU is actually running at.
I would think that half voltage would result in one quarter the power consumption, but I have not had a good opportunity to observe its battery life yet.