Related
Im new to android, what is the best setting for setcpu for balancing performance and battery life. Thanks in advance
Sent from my SPH-D700 using XDA App
What Rom/kernel are you on? Voltage Control might be the better option.
The Root said:
What Rom/kernel are you on? Voltage Control might be the better option.
Click to expand...
Click to collapse
On leaky gingerbread eeo3, don't know what kernel but kernel version is 2.6.35.7, firmware is 2.3.3...
The lower the maximum speed you can tolerate will give you the max battery life. A lot of people keep 800 Mhz as max for that reason.
If you want a good mix between battery and performance, I recommend keeping your maximum clock at 1000Mhz (default) and lowering your minimum clock to 100Mhz (default should be 200Mhz) if your phone will allow it.
Blankrubber said:
If you want a good mix between battery and performance, I recommend keeping your maximum clock at 1000Mhz (default) and lowering your minimum clock to 100Mhz (default should be 200Mhz) if your phone will allow it.
Click to expand...
Click to collapse
Yeah, just make sure you have journaling on if you are going to try 100 Mhz. A lot of phones get the sleep of death from that. Mine is one of those. Then you will have to pull the battery and adjust your settings to 200 Mhz minimum on SetCPU.
Or....You could not use 100mhz at all!
It uses the same voltage as 200mhz. And by increasing the amount frequencies scaled makes the phone slower.
800mhz max, 200mhz min. 800mhz is volted -75 over 1ghz. Which should increase battery life.
Awsome stuff guys. Thanks for all the great info and to all that reply... Thanks again
Sent From My Epic 4G
darkierawr said:
Or....You could not use 100mhz at all!
It uses the same voltage as 200mhz. And by increasing the amount frequencies scaled makes the phone slower.
800mhz max, 200mhz min. 800mhz is volted -75 over 1ghz. Which should increase battery life.
Click to expand...
Click to collapse
I'd quote him but I'm on my phone. Rodderik has stated that all the frequencies use the same internal voltage except for 100mhz, which uses a slightly less internal voltage. What we're adjusting and seeing read in voltage control is the arm voltage, or the processor voltage at each frequencies. I'm not sure the exact difference, but there is a slight drop in voltage at 100mhz compared to the other frequencies? A battery saving difference? Who knows
Sent from my SPH-D700 using XDA App
Just insalled new syndicate frozen rom. Set cpu not compatible? Installed set cpu and every time screen goes to sleep, I can't get it to wake up unless I pull out battery. Anybody else having this problem on this rom?
Sent from my SPH-D700 using XDA Premium App
otee670 said:
Just insalled new syndicate frozen rom. Set cpu not compatible? Installed set cpu and every time screen goes to sleep, I can't get it to wake up unless I pull out battery. Anybody else having this problem on this rom?
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Everyone try conservative now, not on demand...
Edit::: The problem is with Voltage control 4b4, I'm going to test more before I report and start a thread, but feel free to...
Help support autism awareness,it only takes 2 seconds to help make a difference...
http://picketfenceblogs.com/vote/3616
Just changed setting to coservative and so far it seems to be working. settings is max-1300000 min-200 conservative (charging) max-1300000 min-1300000 conservative (screen off) max-400 min-400 consevative... on screen off, I tried max-200 min-200 phone stays in sleep. This what worked for me...
Sent from my SPH-D700 using XDA Premium App
Thanks to ecooce
Sent from my SPH-D700 using XDA Premium App
I know unrooted desire z devices always work at 800mhz. My device is set to 245mhz min and 1400mhz max (interactive or smartass governor). It sometimes causes my device to wake up a bit late. I wonder how long time my battery goes if I set my device at min 800 mhz and max 1200 or 1400 mhz... Did anyone try this clock speeds?
Deadly Sto(R)m said:
I know unrooted desire z devices always work at 800mhz. My device is set to 245mhz min and 1400mhz max (interactive or smartass governor). It sometimes causes my device to wake up a bit late. I wonder how long time my battery goes if I set my device at min 800 mhz and max 1200 or 1400 mhz... Did anyone try this clock speeds?
Click to expand...
Click to collapse
That's way too low of a min speed, just bump it up to the next (I think it's 386) and you should see noticable improvement.
I'd also suggest the ondemand gov; since it only ramps up to the top speed when needed, then drops it back down again, you should get a bit better battery life.
Sent from my HTC Vision using XDA App
OriginalGabriel said:
That's way too low of a min speed, just bump it up to the next (I think it's 386) and you should see noticable improvement.
I'd also suggest the ondemand gov; since it only ramps up to the top speed when needed, then drops it back down again, you should get a bit better battery life.
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
i read ondemand and conservative governors are od, so using interactive or smartass are better then using others. I will try min 368 mhz but am not sure if it works...
What are you trying to accomplish by messing with the clock speed? Leave it alone at default. Performance difference is NEGLIGIBLE (bottleneck is elsewhere), and all you'll accomplish is eating the battery and burning it up with excessive heat caused by excessive clock.
dhkr234 said:
What are you trying to accomplish by messing with the clock speed? Leave it alone at default. Performance difference is NEGLIGIBLE (bottleneck is elsewhere), and all you'll accomplish is eating the battery and burning it up with excessive heat caused by excessive clock.
Click to expand...
Click to collapse
First of all, I would like to thank you for your comments.
People don't do anything to access root if they don't want to mess device. I am one of them and want to have a device which both has performance and visuality. You offered me to not to change clock speeds. But we know HTC Desire Z is scheduled to work at 800mhz everytime (default). My opinion is just to set minimum clock speed to 800 mhz or something like this. If my device was burn by this clock speed, it was already dead.
Today i tried this clock speed (min 614, max 1382) and during the day it didn't heat up. Moreover, 8 hours passed, i played NFS for about 1,5 hour, made some call and 30 percent of battery left. It seems this clockspeeds doesn't cause battery drain or i couldn't feel it...
EDIT: 13 hours passes, 16 percent battery left (I made minimum 30 minutes of call)
According to Franco 700 MHz is the most efficient. I think all other kernels (+ for sure the phone's default from Samsung & Google) have the minimum set on 350 MHz.
Personally I see it being dependent on usage style; if the phone lays idle a lot the 350 MHz should be better. If you keep waking up the phone every other moment then the 700 MHz makes sense.
350mhz.
700mhz minimum is not more efficient.
Vangelis13 said:
According to Franco 700 MHz is the most efficient. I think all other kernels (+ for sure the phone's default from Samsung & Google) have the minimum set on 350 MHz.
Personally I see it being dependent on usage style; if the phone lays idle a lot the 350 MHz should be better. If you keep waking up the phone every other moment then the 700 MHz makes sense.
Click to expand...
Click to collapse
for francos kernel it might be the case...not others
I think it depends on the governe you're using. when the phone is idle it absolutely doensn't matter (on any kernel) because the cpu shuts down.
when you're using the phone then it depends how the governer manager the cpu to get the task done and race back to minimum freq.
I'm just guessing here but based on this assumption I think 700mhz is better for ondemand/conservative but not so much for interactive.
ArmanUV said:
I think it depends on the governe you're using. when the phone is idle it absolutely doensn't matter (on any kernel) because the cpu shuts down.
when you're using the phone then it depends how the governer manager the cpu to get the task done and race back to minimum freq.
I'm just guessing here but based on this assumption I think 700mhz is better for ondemand/conservative but not so much for interactive.
Click to expand...
Click to collapse
I've read that ondemand is more power-hungry than interactive...
anton2009 said:
I've read that ondemand is more power-hungry than interactive...
Click to expand...
Click to collapse
Interactive has less in between steps and is quicker to jump to max
Sent from my francoPhone
Franco uses 700 because of the wake lag caused by 350 when using hot plug mod (shutting off cpu1)
Sent from my Galaxy Nexus using xda premium
With 350 or 700 I still get wake lag.
i'm on franco's latest and hotplug is on and my cpu gov is set to conservative and min freq is 350mhz. no lag on waking at all..
180
Vangelis13 said:
According to Franco 700 MHz is the most efficient. I think all other kernels (+ for sure the phone's default from Samsung & Google) have the minimum set on 350 MHz.
Personally I see it being dependent on usage style; if the phone lays idle a lot the 350 MHz should be better. If you keep waking up the phone every other moment then the 700 MHz makes sense.
Click to expand...
Click to collapse
I'm using 180 in imoseyon's Leankernel experimental builds.. works amazing, telephone spends 70% in this state on average, at 180 undervolting at 875mV.
ArmanUV said:
I think it depends on the governe you're using. when the phone is idle it absolutely doensn't matter (on any kernel) because the cpu shuts down.
when you're using the phone then it depends how the governer manager the cpu to get the task done and race back to minimum freq.
I'm just guessing here but based on this assumption I think 700mhz is better for ondemand/conservative but not so much for interactive.
Click to expand...
Click to collapse
The cpu may idle in a low power state, but it does not shut down. How can the phone run if the CPU stops running? There is no secondary system that intervenes to start the CPU back up.
adrynalyne said:
The cpu may idle in a low power state, but it does not shut down. How can the phone run if the CPU stops running? There is no secondary system that intervenes to start the CPU back up.
Click to expand...
Click to collapse
that's what I meant. my point is that power consumption in idle state doesn't depend on the min frequency.
But it matters every time your phone wakes up, even if its momentarily.
Only get lag and signal loss when on 350. 700 seems to give me the best sleep and wake time with no lag. I had to learn the hard way. But figured out from reading around that 350 causes some problems on any kernel/governor.
Sent from my Galaxy Nexus using XDA Premium App
The only time 350mhz gives troubles is if you set the min/max to it for sleep.
ChongoDroid said:
Interactive has less in between steps and is quicker to jump to max
Sent from my francoPhone
Click to expand...
Click to collapse
I think you have that backwards? OnDemand basically just jumps between minimum and max. Only recently has a 2stage part been added in that you can set to around the halfway point for light load tasks.
Interactive used to be more efficient because it didnt jump straight to max speed like OnDemand does. However with the addition of the 2nd stage in OnDemand, that tends to be more efficient now. Besides, Interactive governors are always buggy on any phone I have used them with.
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
ArmanUV said:
that's what I meant. my point is that power consumption in idle state doesn't depend on the min frequency.
Click to expand...
Click to collapse
It does in some ways. It will idle at the lowest speed it can. If you go too low the CPU will drop out and the phone will never wake up or will crash and restart. If you set your minimum to 700MHz then it wont go below that so that becomes the idle speed. And since p=v2*f, the lower your frequency the lower your battery drain.
Actually, stock kernel, onDemand is garbage, and Interactive is best.
EniGmA1987 said:
I think you have that backwards? OnDemand basically just jumps between minimum and max. Only recently has a 2stage part been added in that you can set to around the halfway point for light load tasks.
Interactive used to be more efficient because it didnt jump straight to max speed like OnDemand does. However with the addition of the 2nd stage in OnDemand, that tends to be more efficient now. Besides, Interactive governors are always buggy on any phone I have used them with.
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
It does in some ways. It will idle at the lowest speed it can. If you go too low the CPU will drop out and the phone will never wake up or will crash and restart. If you set your minimum to 700MHz then it wont go below that so that becomes the idle speed. And since p=v2*f, the lower your frequency the lower your battery drain.
Click to expand...
Click to collapse
You're absolutely right, I had em backwards lol
Sent from my Galaxy Nexus using xda premium
Same here.
EniGmA1987 said:
I think you have that backwards? OnDemand basically just jumps between minimum and max. Only recently has a 2stage part been added in that you can set to around the halfway point for light load tasks.
Interactive used to be more efficient because it didnt jump straight to max speed like OnDemand does. However with the addition of the 2nd stage in OnDemand, that tends to be more efficient now. Besides, Interactive governors are always buggy on any phone I have used them with.
---------- Post added at 03:12 PM ---------- Previous post was at 03:10 PM ----------
It does in some ways. It will idle at the lowest speed it can. If you go too low the CPU will drop out and the phone will never wake up or will crash and restart. If you set your minimum to 700MHz then it wont go below that so that becomes the idle speed. And since p=v2*f, the lower your frequency the lower your battery drain.
Click to expand...
Click to collapse
it's not as simple as that. when the screen is off the phone enters deep sleep as much as possible which uses (almost) the same power regardsless of min frequency. The phone obviousely will wake up from deep sleep from time to time and that's when the minimum frequency comes into play. For example, for someone who has a lot of applications syncing every few minutes or someone who listens to music a lot with the screen off (which prevents deep sleep), setting the minimum to 350 will be better. Otherwise, the savings are negligible.
This was put to test by someone here on xda (the gnexus general section) by measuring voltage and current through the battery in different conditions.
Wich undervolting values do you prefer with the latest nightly from Franco?
The efficient and stablest
Sent from my Galaxy Nexus using xda premium
I am on franco kernel r180. I actually am using default mV. And have seen great results this far.
Just as well, using 25% brightness and only used Wi-Fi (4G buries my battery. Using a stock GN (Verizon) battery). Here's some photos.
Edit: I accidentally reversed the order of the screen shots from the way I wanted. Anyway, its been a great kernel. Kudos to franco. He's very smart. I wish I could do something this awesome.
One last thing, I've kept Max CPU at 1036MHz. It keeps the phone cool as the other side of the pillow. When I'm only using xda premium app, some light web browsing and Pandora running, 1036MHz is perfectly fine. I hope you find this useful.
Sent from my Galaxy Nexus using xda premium
Running AOKP B38 + Franco M3, and seeing great results with these voltages. If I lower it -25 mv across the board, the phone gets hot easily. And -50 mv across the board, and it'll randomly reboot when turning on Wi-Fi or while playing music, multitasking, etc.
Also, usually have it running at 728 MHz, unless I actually need to get stuff done and I up it to 1036 MHz. I've never had to set it at 1228 MHz.
Sent from my Galaxy Nexus using Tapatalk 2
The upper value doesn't really matter at all since the CPU is hardly ever sitting there.
Sent from my Galaxy Nexus using xda premium
I just wanted to post an update on how I am doing with Franco kernel r180. Just to be clear, this is not a continuation of my results from yesterday. Today's results are after a full charge.
CPU settings remain the same in terms of min and max, 384/1036 respectively, mainly on Wi-Fi (was on 3G for a good 20 minutes when I walked to the local CVS) and 25% brightness (again, shifted that to 100% when I went to CVS, but brought that back down to 25% when I got home).
I am close to 2.5 hours of screen time with 50% battery used. I have kept the screen on for a long time for testing reasons. Also, a 23 minute phone call was done on speaker phone with screen on as well. Phone stays very cool with these CPU settings.
If you have any questions, please feel free to ask.
Edit: as for under volting, I'm at (all in mV units of course) 1400, 1300, 1250, 1225, 1125, 950 ,900 for (all in MHz units of course) 1536, 1344, 1228, 1036, 729, 384,192 respectively. Again, my CPU boundaries are stated above so I'm never at settings such as 1534, 1334, etc.
Sent from my Galaxy Nexus using xda premium
I got these results using AOKP build 36 and Franco Kernel 166. 3G on when screen is on with occaisonal LTE (no WiFi usage). CPU clocked between 196MHz and 1036MHz with 384MHz for when the screen is off. Auto screen brightness. The last 3 images are my voltage settings. The saved voltages are the ones that were used.
I had a slightly longer screen on time and battery life. In my experience the voltage didn't affect heat output, but clocking the CPU at 1036MHz instead of 1228MHz did.
I am familiar with undervolting, went -75 across the board with no problems, obviously the lowest frequencies are all at 800. Would it be beneficial to set the minimum CPU frequency to the highest frequency at 800mv? Seeing as there is no voltage difference between 192mhz and 594mhz wouldn't it make sense and even save battery to set minimum to 594 so it can idle faster basically and use less time to do calcs at minimum frequency?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
zander21510 said:
I am familiar with undervolting, went -75 across the board with no problems, obviously the lowest frequencies are all at 800. Would it be beneficial to set the minimum CPU frequency to the highest frequency at 800mv? Seeing as there is no voltage difference between 192mhz and 594mhz wouldn't it make sense and even save battery to set minimum to 594 so it can idle faster basically and use less time to do calcs at minimum frequency?
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Theoretically yes, but undervolting that low at high clock speeds will greatly increase your chances of freezing.