From what I understand when you double the frequency, you quadruple the power consumption. Thats when the colts stay the same.
But what about:
800Mhz @ 1000mv
vs
1600 Mhz @ 1350mv
Can someone tell me the formula? Is that more like 7.29 times power consumption instead of 4? Are my sums below on the right track?
((1600÷800)×1.35)^2=7.29 times power consumption
But when you remember it takes half the time to do a calculation then I guess you have it again to be only 3.65 times. And CPU will always consume some power anyway...
Theoretically this sounds like turning on second core preferred to clocking up frequency would save a lot of power. But maybe CPU power consumption always irrelevant compared to screen consumption
Why square the frequency?
The power draw is proportional to the frequency, and to the square of the voltage.
If you double the voltage, the power consumed is:
P = U^2 / R
Disregarding side-effects , the resistance stays the same .
Sent from my GT-N7000 using XDA App
Related
I'm looking at the sys info on quadrant and it shows my current freq: 800mhz.
any one know why it would be showing 800mhz and not 1ghz?
Yep, because it fluctuates.
ahhh... saver modes then... thanks for the info..
now if there's a way to make it static at 1ghz
Why do you want it to run at full power constantly? Why do you want it to suck more power then it needs to?
Believe it or not, your computer CPU does the same thing. It's frequency fluctuates depending on the task at hand. Take this for example: my Core 2 Duo isn't going to always run at it's 2.5Ghz. Intel has something called CPU stepping in it's instruction set and it's meant to decrease power usage, wear and tear, and energy drain when at idle or near idle. Same thing with your phone.
I'm sorry, but i have already searched the foruns and i did not found any explicit answer, so here it goes.
I recently moved to Zeus v6.39 ROM and i would like to understand how the zeustweak works. I mean, in order to get battery life, should i raise up the CPU frequency (and how much is it safe to raise) and lower the voltage (and, again untill what value may i do it), isn't it so? Assuming i do it, which would be the consequences for my phone?
Thanks
P.S. - is there any way of changing the receiving/making call screen layout?
Don't change, just leave default 0
99% people of Zeus 6.39 getting best battery life. I am also using with same tweak.
Press THANKS button if helped..
The cpu frequency is the amount of calculations per second that the cpu can process so theoretically, the higher the frequency, the faster the ROM will respond. In actual fact the cpu frequency also determines how stable the ROM is and the higher you clock your processor, the more unstable it may be and the more battery it will use.
I would recommend for ultimate stability to leave it at 1000MHz but for negligible performance improvements max could be up to 1350MHz but the difference is minute.
Correct me if I'm wrong but the voltage tweak is the aggressiveness of the governor when ramping the cpu up or down (changing the frequency). The values below 0 indicate that the governor will ramp down the frequency which in turn saves battery life. Values above 0 will make the governor ramp down less aggressively and thereby increase ROM responsiveness and noticeable lag spikes but reduce battery life.
I hope that helps but don't quote me on it.
Sent from my LG-P970 using Tapatalk 2
In my test voltage tweaks works. If I set -7 i could watch the youtube for 4 hours, but when I set 0 I watched only 3 hours continuously. Someone do a test and measure power consumption on charger. With -7 drains about 30% less battery.
Sorry for bad english.
Hello all !
I was bored in school today so I've written a governor concept idea for quad cores. I'm not a dev AT ALL (for now at least, i'm studying many different stuff, hardware / code related too).
I have no idea if this is possible or if this is clever but I wanted to share it anway. If it gives idea to a developer, that's totally worth it, otherwise, well... I had fun doing it
It's called Progressive.
Progressive
The name of the governor says all. The idea behind it is to be «*progressive*». It means it doesn't unleash the full power when it's not needed. It goes progressively higher in freq with more cores. This should make the phone cooler and the battery better. The delay (3 sec ) is just a number, not sure this is really nice. Also, I'm not sure how the S4 handles temperature.
Max freq 1.5 Ghz
Min freq 384 Mhz
Screen off
=> 384-918 Mhz // not too low frequency to avoid reboot
Screen on without touching since 3 sec // always check after 3 seconds for changing the state
=> 384-1134 Mhz only one core online
Screen on touched
=> 594-1134 Mhz two cores online // bump the min_freq to avoid keyboard lag and to add a bit of butter
Screen on touched with a medium load of task // not sure how quantify this
=> 594 Mhz – 1.5Ghz two cores online
Screen on touched with a high load of task // i.e. Games
=> 702 Mhz – 1.5 Mhz four cores online // max power
We also need a thermal protection to avoid any damage, this should do the trick
If the temp is >= 80°C
=> Two cores online max_freq 1134 Mhz until it reaches 70 °C // not sure about the temp, this can be adjusted
If the temps is >=70°C
=> Let 4 cores being possibly online but lower the max_freq to 1134 Mhz
Click to expand...
Click to collapse
What do you guys think ? Is this even possible ? Good, bad idea ?
I hope you enjoy reading it as much as I enjoyed to writte it
doesn't it do this already?
Fissurez said:
doesn't it do this already?
Click to expand...
Click to collapse
I'm not sure how the ondemand governor on nexus 4 works. So I can't really answer, it's really a noob idea that poped into my head today
you pretty much described interactive with mpdecision enabled.
not exactly, but quite.
3 seconds is way too long for the CPU to ramp up (just a matter of tweaking, though). you'd get more lag than you save battery.
mpdecision ramps the cpu to its maximum frequency as soon as a touch input is detected (normally only 2 cores until a certain threshold is reached), so yours should save a bit of power during smaller workloads.
also, if the touch input is released, it clocks the active cores down to 1.02 GHz for a bit before disabling them when not needed.
after all, it seems like a more conservative interactive governor with active mpdecision. could be nice for saving battery while retaining good performance.
it could be a viable choice for those who go for battery life over performance. :good:
Nuu~ said:
you pretty much described interactive with mpdecision enabled.
not exactly, but quite.
3 seconds is way too long for the CPU to ramp up (just a matter of tweaking, though). you'd get more lag than you save battery.
mpdecision ramps the cpu to its maximum frequency as soon as a touch input is detected (normally only 2 cores until a certain threshold is reached), so yours should save a bit of power during smaller workloads.
also, if the touch input is released, it clocks the active cores down to 1.02 GHz for a bit before disabling them when not needed.
after all, it seems like a more conservative interactive governor with active mpdecision. could be nice for saving battery while retaining good performance
Click to expand...
Click to collapse
Thank you Sir, I understand better how mpdecision works now
Glad to see i'm not completely stupid lol
Hi,
Brand new One and HTC user and loving it! I've been trying out the power saver function to help a charge last longer (which I would say so far definitely helps). When it says "conserve CPU usage" has anyone been able to monitor the clock or core activity with this turned on? I'd be interested to see what the trade off actually is...
Sorry I don't know how to access this info yet.
When "Power Saver" is enabled, benchmark apps (like Quadrant Standard) would report the CPU as running at 1134 MHz with 4 cores. Disable power saver & CPU returns to 1728 MHz.
omar302 said:
When "Power Saver" is enabled, benchmark apps (like Quadrant Standard) would report the CPU as running at 1134 MHz with 4 cores. Disable power saver & CPU returns to 1728 MHz.
Click to expand...
Click to collapse
Ah ok, that makes sense then given that I don't notice a huge drop in performance unless I ask it to do something serious. But the battery savings are awesome.
Thanks very much!
Does any have experience with editing the available CPU frequencies? I want to go to a lower frequency than 1113 GHz. So, the opposite of overclocking. From what I understand, it requires either editing the kernel or getting an entirely different one - which I am not capable of doing myself.
As it bugs me (and probably you) how fast the battery drains on Mi 6x, I looked in the CPU settings.
As it looks:
CPU 0 to 3 run on a minimum frequency of 633 GHz each.
CPU 4 to 7 run on a minimum frequency of a whopping 1113 GHz each.
When I put the phone into standby, it continues to run on 1113 GHz on 4 cores. So, is it surprising that Mi 6x drains battery? No. (In addition to a massive screen that requires extra battery, in addition to a smaller battery... very smart engineering here) Imagine you'd put your laptop into standby and it would continue to work with half its processor speed. Not acceptable.
daokris said:
Does any have experience with editing the available CPU frequencies? I want to go to a lower frequency than 1113 GHz. So, the opposite of overclocking. From what I understand, it requires either editing the kernel or getting an entirely different one - which I am not capable of doing myself.
As it bugs me (and probably you) how fast the battery drains on Mi 6x, I looked in the CPU settings.
As it looks:
CPU 0 to 3 run on a minimum frequency of 633 GHz each.
CPU 4 to 7 run on a minimum frequency of a whopping 1113 GHz each.
When I put the phone into standby, it continues to run on 1113 GHz on 4 cores. So, is it surprising that Mi 6x drains battery? No. (In addition to a massive screen that requires extra battery, in addition to a smaller battery... very smart engineering here) Imagine you'd put your laptop into standby and it would continue to work with half its processor speed. Not acceptable.
Click to expand...
Click to collapse
Hello. It is normal for the processor to operate at its normal frequency while the phone is idle. There are plenty of processes in the background. If you have root rights, then you can download an application like (l speed) through this application, I put my battery my processor and the data in the background that allows me a loss of only 1% over a period from 10 am
If I'm not mistaken, your processor cores should go into deep sleep state when you turn your screen off. If they stay on 633/1113 then something is probably keeping the phone awake and battery is going to suck.
Download Dev Check to see how long the cores stay on certain frequencies. If you leave your screen off for most of the time, then most of the graph should show "Deep Sleep" instead of any other frequency.