Database Users

Interactive Vs Conservative Governor? CDMA Battery Life Tips

What is this nonsense people are saying about 4 or 5 hours with screen on and their phone is still at 20%? GTFO.... Usually I would say about 3 hours of screen on and i'm dead. I can get like 18 hrs or so lightly, and by lightly, I mean only using it for a few text and check email, maybe some fb just to check inbox and such, lightly, using the phone (with my reception).
I know the Fascinate is better hardware, and I switched for the GPU among other reasons (2 of em for free...=P) but, on my nexus, I still find that the interactive governor ramped up to the max freq. (1113Mhz) less. Of course, I am using the 1150 nonvoodoo from geeknik, but I doubt I will make it 4 or 5 hours of screen on time.w
How can you use the phone, with the screen on, and not do anything that uses the battery. I mean, without cyanogen, it was cool that I can make it through my day, easy, close to out of box (getting to superclean dj05 is about 100 less flashes that I made it through with the n1/sense/cyan nightlys/test roms/etc.).
But now I want more, the price I have to pay I guess for the .3 inches of gained screen is not using the phone heavily in order to save battery!? That sucks. I used to hammer my iPhone and I rarely made it through the day, but I hammered it with atleast 4 or 5 hrs of screen on time sometimes, and it would make it atleast 8 hours... that thing would idle wayyyy better on GSM Edge than CDMA I guess, as with my T-Mobile N1, it idled wayy better, than this CDMA phone. Is there a way to put it on 1x instead of having it always on 3g? There isnt a setting to uncheck, and you cant get in *#*#4636#*#* on CDMA. I tried that immediately after unboxing to get off 3g when I wasnt using net apps, and usually that gave better signal on GSM, saving battery.
Check out my interactive battery test on my N1 that I did, the interactive setting eventually fell out of favor because it ramps up to the max... instead of ramping up accordingly like OnDemand, and not too slowly like Conservative. Again, why does Fascinate use conservative?
http://forum.xda-developers.com/showthread.php?p=7370179 thats my Interactive Governor Battery Test on my N1 I did in the summer time...
I just wanted to start this thread so we can get a consensus on what works best, and for charging this battery. I used to charge my N1 an extra 1.5 hrs with it off after android says it was at 100. That way it idled on 100 instead of immediate drain. An extra 3 or so hours of battery life if you use it right.
CPU governors control exactly how the CPU scales between your "max" and "min" set frequencies. Most kernels have "ondemand" and "performance." The availability
********I want to be able to choose between ondemand and powersave when my battery gets low. On this phone, as I did with the N1.
ondemand - Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
conservative - Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance - Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking.
powersave - Available in some kernels. It will keep the CPU running at the "min" set value at all times.
userspace- A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.

akaine2001 said:
What is this nonsense people are saying about 4 or 5 hours with screen on and their phone is still at 20%? GTFO.... Usually I would say about 3 hours of screen on and i'm dead. I can get like 18 hrs or so lightly, and by lightly, I mean only using it for a few text and check email, maybe some fb just to check inbox and such, lightly, using the phone (with my reception).
I know the Fascinate is better hardware, and I switched for the GPU among other reasons (2 of em for free...=P) but, on my nexus, I still find that the interactive governor ramped up to the max freq. (1113Mhz) less. Of course, I am using the 1150 nonvoodoo from geeknik, but I doubt I will make it 4 or 5 hours of screen on time.w
How can you use the phone, with the screen on, and not do anything that uses the battery. I mean, without cyanogen, it was cool that I can make it through my day, easy, close to out of box (getting to superclean dj05 is about 100 less flashes that I made it through with the n1/sense/cyan nightlys/test roms/etc.).
But now I want more, the price I have to pay I guess for the .3 inches of gained screen is not using the phone heavily in order to save battery!? That sucks. I used to hammer my iPhone and I rarely made it through the day, but I hammered it with atleast 4 or 5 hrs of screen on time sometimes, and it would make it atleast 8 hours... that thing would idle wayyyy better on GSM Edge than CDMA I guess, as with my T-Mobile N1, it idled wayy better, than this CDMA phone. Is there a way to put it on 1x instead of having it always on 3g? There isnt a setting to uncheck, and you cant get in *#*#4636#*#* on CDMA. I tried that immediately after unboxing to get off 3g when I wasnt using net apps, and usually that gave better signal on GSM, saving battery.
Check out my interactive battery test on my N1 that I did, the interactive setting eventually fell out of favor because it ramps up to the max... instead of ramping up accordingly like OnDemand, and not too slowly like Conservative. Again, why does Fascinate use conservative?
http://forum.xda-developers.com/showthread.php?p=7370179 thats my Interactive Governor Battery Test on my N1 I did in the summer time...
I just wanted to start this thread so we can get a consensus on what works best, and for charging this battery. I used to charge my N1 an extra 1.5 hrs with it off after android says it was at 100. That way it idled on 100 instead of immediate drain. An extra 3 or so hours of battery life if you use it right.
CPU governors control exactly how the CPU scales between your "max" and "min" set frequencies. Most kernels have "ondemand" and "performance." The availability
********I want to be able to choose between ondemand and powersave when my battery gets low. On this phone, as I did with the N1.
ondemand - Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed.
conservative - Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery.
performance - Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking.
powersave - Available in some kernels. It will keep the CPU running at the "min" set value at all times.
userspace- A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor.
Click to expand...
Click to collapse
Thank Samsung for breaking ondemand on every sgs phone.
Sent from my SCH-I500 using XDA App

Well what else can you contribute to this thread? Thanks for letting me know that the ondemand is just broken on galaxy s phones. So basically its interactive ... or laggy UI experience. And if you've never used a ondemand kernel, you wouldn't notice the difference but i certainly do. It just takes too long sometimes for it to wake and other things. I have my screen off at 400 mhz but still that is higher than the 256 i was using on the nexus one and it used to wake immediately.
I was reading today and I found that ondemand is pretty much the way to go so i wonder if we could bounty up enough would somebody unbreak it...

akaine2001 said:
Well what else can you contribute to this thread? Thanks for letting me know that the ondemand is just broken on galaxy s phones. So basically its interactive ... or laggy UI experience. And if you've never used a ondemand kernel, you wouldn't notice the difference but i certainly do. It just takes too long sometimes for it to wake and other things. I have my screen off at 400 mhz but still that is higher than the 256 i was using on the nexus one and it used to wake immediately.
I was reading today and I found that ondemand is pretty much the way to go so i wonder if we could bounty up enough would somebody unbreak it...
Click to expand...
Click to collapse
You are doing something wrong. Conservative is not choppy on my device and the CPU will always ramp up faster than a human being can judge the response time.
Sent from my SCH-I500 using XDA App

My phone makes it the entire day with heavy use, this means about 20 - 10 min phone calls one or two lasting 30 min, texting my wife all day at work, checking emails, and angry birds for at least 1 hour a day i love that game but I suck at it lol. Something that I found is that the phone will last almost an hour of being on the phone after it hits 0%. In my pocket it lasted 4 hours at 0% the day before yesterday. I thought maybe this is on purpose so you have more then enough time to make it to a charger. When I first downloaded angry birds I played it for three hours straight with the screen at full brightness (i always keep it at full brightness, looks prettier that way) I know it was three hourse because it was while i was waiting at the hospital I got there a little before 7 and wasnt called until 10. Overall I am very pleased with the battery life of this phone not so much with other aspects but battery life and lag never came into my mind as a complaint for this phone, except with all the stock touchwiz stuff.

As adrynalyne said, CPU's scaling changes faster than human's perception. It's your phone or setting that's having an issue.

4 hours at 0%?
The little graphic samsung gives you in the stock battery is misleading.
In my brief experience with it, I got the following impression.
full battery graphic: you have between 100% and 75% left.
<full battery: 75%-50%
Half battery: 50%-25%
low battery: 25%-15%
empty: 15%-0%
This may not be quite right, but you get the idea. It has been a while, but stock battery is pretty misleading. Samsung reports [more than] half empty [always] as being half full!
Want a more trailer indicator? You can get an accurate battery mod (via a theme for instance) or you can download an app to check current battery % left (i use osmanager - do not leave this app running in the background! )
Assuming your phone lasts 27 hours or so unplugged with no use at all, I would say 4 hours at "zero" battery makes sense.
For my phone, the display uses an average of 3.5x as much power as the rest of its functionality (total of 1/4.5x lifespan in active use vs. pocket)
Swyped w/ XDA App. When in doubt, mumble.

I meant "reliable" not trailer.

I get about 5 hours of screen time with little voice calls on wifi.

I don't know if I am just one of the lucky ones but my phone gets between 30 and 36 hours on a single charge, having even made it to 44 hours on a very rare occasion and that's without setcpu profiles even set.

Wtf... my phone is brand spanking new and I get about 4ish hours of screen time on a full charge, with the lowest brightness + screen filter app set at 50.6% reduced light. I get like 3 hours without screen filter on.... wtf. This is running on conservative or interactive the whole time..... wtf!!! With wifi on and 0 extra screens or Widgets using launcher pro without animations... wtf!!!
Sent from my SCH-I500 using XDA App

+1... stock battery indicator is not accurate. Get the accurate battery mod.
soba49 said:
4 hours at 0%?
The little graphic samsung gives you in the stock battery is misleading.
In my brief experience with it, I got the following impression.
full battery graphic: you have between 100% and 75% left.
<full battery: 75%-50%
Half battery: 50%-25%
low battery: 25%-15%
empty: 15%-0%
This may not be quite right, but you get the idea. It has been a while, but stock battery is pretty misleading. Samsung reports [more than] half empty [always] as being half full!
Want a more trailer indicator? You can get an accurate battery mod (via a theme for instance) or you can download an app to check current battery % left (i use osmanager - do not leave this app running in the background! )
Assuming your phone lasts 27 hours or so unplugged with no use at all, I would say 4 hours at "zero" battery makes sense.
For my phone, the display uses an average of 3.5x as much power as the rest of its functionality (total of 1/4.5x lifespan in active use vs. pocket)
Swyped w/ XDA App. When in doubt, mumble.
Click to expand...
Click to collapse

Terror_1 said:
I don't know if I am just one of the lucky ones but my phone gets between 30 and 36 hours on a single charge...
Click to expand...
Click to collapse
That's because you don't use your phone.
Go play NFS for 3 hours and get back to us.
MoShiBa said:
...screen filter app set at 50.6% reduced light. I get like 3 hours without screen filter on...conservative or interactive the whole time...
Click to expand...
Click to collapse
What's the screen filter app? Conservative and interactive? That's SetCPU?
I wouldn't worry about these guys coming in here saying they're getting 2 days of use either. They're not using the phone anywhere near as much as you. I've had 3 of these things and know 2 guys with them. They all got the same battery life. You don't see anyone posting any screenshots, do you?

Me and my gfs fascinate gets about same battery life in our apt and hers is still DI01 and i'm on DJ05... she has jts 11/16 kernel and i have the 12/21 voodoo5 and we get about the same battery life... dependent on how much we use the phone. .... so just use your phone, and charge it as necessary... its better for the type of battery we use anyways in our phones... **************************************************************************************closed.**************************************************************************************

[Q] [Opinions] Undervolt Settings.

First off, I would like to apologize in advance in case a thread like this exist and I can't find it.. :/ (Search is down, tried Googling) also, if anyone believes this to be in the wrong forum.
ANYWAYS! This is intended to be a preference/opinions thread centering around your OC/UC and Undervolt settings. Feel free to post your current set-up in Voltage Control (or any app of the like) and what Kernel you are running! I wanted to start this to get an idea of what everyone else is setting their UV and CPU clocks to, and possibly give a few of them a try on my own device. :]
Personally all of my clock speeds are at their defaults except for 1000Mhz @ 1200mV. (-75mV). I am also rocking Genocide v1.0 and getting a decent 30hrs of battery life with pretty moderate use.
Post away!

It is kind of pointless since every phone is different so cannot do exactly the same as others. Most can't do 1.4Ghz and most don't wake from sleep at 100 Mhz. All depends what you use your phone for. Mine runs fine at 1.3Ghz except for some TV apps will freeze.
Do you BONSAI?

kennyglass123 said:
It is kind of pointless since every phone is different so cannot do exactly the same as others. Most can't do 1.4Ghz and most don't wake from sleep at 100 Mhz. All depends what you use your phone for. Mine runs fine at 1.3Ghz except for some TV apps will freeze.
Do you BONSAI?
Click to expand...
Click to collapse
I believe that would be my point however.. curious as to what other people are running as far as cpu and voltage is concerned. Their success and failures. What people can get away with and remain stable. I, and others, could then try their setup (taking precautions of course; ie Nandroid backup.) And see what we get. Who knows, maybe I might adapt a set up that runs better on my device than my current one.
Sent from my SPH-D700 using XDA Premium App

Yes, every phone is different, but that is just more of a reason to collect data - perhaps a baseline can be established, which would be helpful in determining if a particular phone is messed up or just at the low end of the scale. Right now it is hard to determine if a particular phone's troubles are caused by low quality or by damaged hardware.
I keep all voltages at stock, and don't use any OC - my phone runs fine as is, and the battery life actually seemed worse with UV (and my screen felt hot with the screen UV).
Sent from my SPH-D700 using XDA App

My phone wakes from 100 but won't do 1.4ghz for even a couple seconds before reboot but 1.3ghz lasts about 20 minutes before reboot and 1.2ghz is stable. As for undervolts it can handle -25 on 1.2ghz and -50 on 1 and 1.1ghz -50 on 800mhz and that's it otherwise becomes unstable and reboots. Battery life and performance seem to meet at 800mhz with a -50 undervolt games run smooth too and 12 hours of battery. Oddly enough benchmarks are consistantly higher on 1.12ghz than on 1.2ghz I wonder if I'm the only one?
Sent from my midnight rom 5.2 genocide 1.0 epic [email protected] using xda premium app

xopher.hunter said:
My phone wakes from 100 but won't do 1.4ghz for even a couple seconds before reboot but 1.3ghz lasts about 20 minutes before reboot and 1.2ghz is stable. As for undervolts it can handle -25 on 1.2ghz and -50 on 1 and 1.1ghz -50 on 800mhz and that's it otherwise becomes unstable and reboots. Battery life and performance seem to meet at 800mhz with a -50 undervolt games run smooth too and 12 hours of battery. Oddly enough benchmarks are consistantly higher on 1.12ghz than on 1.2ghz I wonder if I'm the only one?
Sent from my midnight rom 5.2 genocide 1.0 epic [email protected] using xda premium app
Click to expand...
Click to collapse
Just to throw it out there. Aggressive undervolts will do more harm than good to your battery life. By that, I mean you'll drain your battery even more.
Sent from my SPH-D700 using XDA Premium App

I can only use Genocide kernel to get 1.3ghz at stock voltage with since all the other choices are uv'd. My last two Epics were able to handle uv'd 1.4ghz by 50mV but I'm not really complaining as I think this is a new phone they gave me and not a refurb. I currently have 100-400 uv'd by 100mV, 600-1000 uv'd by 75mV and 1300 at stock.

My phone can handle 1.4 Ghz but only with the stock voltages. If I try to touch it even by 25mV it locks up.
Who all has enabled the 100Mhz step? I noticed when I did my phone went into Deep Sleep a lot less by a noticeable amount. Staying at 100Mhz a lot.

Always interesting to hear about all this theory behind the reasons for undervolting OC and UC, then to hear about the issues (at times extreme) some have. I would also like to know who uses the 100 step and if it is noticeably better on battery life than the 200? Unfortunately I am missing out on it if I am. Still running Genocide here, but with 1.0 at -50mv 800 @ -50 and 600 @ -25. Very stable and still at 30+ battery life. Having 1.0 down 75 made me nervous. although I hear people dropping it down -100mv successfully.
Sent from my SPH-D700 using XDA Premium App

Good tip about "aggressive UnderVolting"...didn't know that actually drains your battery more. Might explain why 6 hours into my day, my battery is down to 30% already!!! I had it set at 1120Mhz UV to 1175mV (Stock = 1300)...
So now I'm going to try 1200Mhz only UV by 50...see what my battery life is after this!

Custodian said:
Just to throw it out there. Aggressive undervolts will do more harm than good to your battery life. By that, I mean you'll drain your battery even more.
Sent from my SPH-D700 using XDA Premium App
Click to expand...
Click to collapse
Can you explain how this is so? Is this based on any actual research, experimentation, or online documentation, or is this just your own opinion?
Unless your undervolt causes the CPU to hang (I've seen mine start to warm up when it's hung, until a battery pull), I don't understand how providing less voltage to the cpu will cause it to drain the battery faster.

If you change the voltage settings please don't blame the rom developers when you phone bricks...
Sent from Bonsai 7.1.3.1

I'm running Twilight Zone v 1.1.1 RC1-Hajime Taisho, Vision kernel v 1.2
SetCpu-1.450 max
-1.450 min
Quadrant-2377
Linpack-20.577
Voltage Control-1.450
Uv -100
Quadrant-2346
Linpack-21.495
I ran SetCpu, benchmarks, ran VC, benchmarks..... This Epic runs super fast, with no FC's or any other problems at all. I'm currently using VC with the uv-100. As far as excessive battery use, I have Mugen 3200 mah battery. This battery lasts all day in heavy use with no problem.
Sent from my SPH-D700 using XDA Premium App

Possible fix for random reboots on Gingerbread

Here are my current stable settings:
SetCPU
Min: 100mhz
Max: 1000mhz
Governor: Ondemand
Profile: Screen Off
--Min: 100mhz
--Max: 200mhz
--Priority: 100
--Governor: Ondemand
Tegrak:
Governor: Ondemand
Scaling: 100-1000mhz
Optimization:
--200mhz Core Voltage: 1025mv
--100mhz Core Voltage: 925mv
Both SetCPU and Tegrak are running side by side.
No random reboots for over a week.
Battery should last between 20-25 hours with normal usage.
Certain phones might need a higher voltage, you may need to do some experimenting to get things stable.
Old text
Anyone experiencing random reboots should try using SetCPU or Tegrak to set the CPU to 1000mhz-1000mhz instead of 100mhz-1000mhz.
I was previously getting 3-4 reboots per day. I set my CPU to 1000mhz-1000mhz using Tegrak four days ago and have not had a single reboot since.
Sure, my battery only lasts about 10 hours vs 20 or so, but at least I can rely on my phone.
Of course I could just be lucky, and who knows it might just randomly reboot any time now.. So, obviously there is no guarantee it will work for anyone else.
Just as a note I also tried 200-1000 and 400-1000, but still had random reboots every few hours.
I am currently testing 200mhz-200mhz with the screen off and 1000mhz-1000mhz with the screen on using SetCPU. I will update this thread in a few days or if it randomly reboots.
Update: 200mhz during screen off causes the phone to not wake up (happened three times). I'm currently testing 400mhz.
Update 2: I got a random reboot last night while asleep using 400mhz. I will see if it continues.
Update 3: Got another reboot at 400mhz. I am now testing 100mhz-1000mhz at 1.275v Core and 1.100v Internal for all frequencies, this should rule out any voltage issues.
Update 4: Made a spreadsheet with my findings, it does not seem to be a voltage issue.
Update 5: Scratch that, I have been using a [email protected] screen off profile for the last 20h... No black screen of death or random reboots. Next up is [email protected]
Update 6: [email protected] is unstable, rebooted after 3 hours. Testing [email protected], 6 hours in and no reboots yet.
Update 7: [email protected] seems to be stable, 24 hours and no reboots yet.
Old text
Click to expand...
Click to collapse
Here is a spreadsheet of my current findings.

My random reboots always came while in deep sleep so this will not work for me. I switched back to a EG22 ROM and get no reboots.
Sent from my SPH-D700 using XDA App

kennyglass123 said:
My random reboots always came while in deep sleep so this will not work for me. I switched back to a EG22 ROM and get no reboots.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Same here, but for some odd reason this (seems to have) fixed it for me. Although, on EG22 I also got a lot of random reboots, so maybe I have a different issue.
I did not get reboots on ED12, EE03, or EF02..
EG22, EH06, and EH17 randomly reboot for me.

I thought it might be similiar to the sleep of death phones would get going from 100 Mhz to deep sleep and also tried boosting to 200 Mhz on EH17 but it didn't help. It may be related and your discovery may aid Devs in fixing the problem If it is still there when source is released.
Sent from my SPH-D700 using XDA App

I think the problem lies in the voltage settings that deep sleep runs on, like in tegrak overclock if the internal voltage is too low the phone will reboot.
Maybe some samsung devs tried lowering the voltages in deep sleep to optimize battery life but only tested it for like a couple hours and didn't notice it.
Are there any ways to edit these values somewhere in the kernel because I know tegrak nor setcpu can do anything to deep sleep.
Sent from my SPH-D700 using xda premium

xopher.hunter said:
I think the problem lies in the voltage settings that deep sleep runs on, like in tegrak overclock if the internal voltage is too low the phone will reboot.
Maybe some samsung devs tried lowering the voltages in deep sleep to optimize battery life but only tested it for like a couple hours and didn't notice it.
Are there any ways to edit these values somewhere in the kernel because I know tegrak nor setcpu can do anything to deep sleep.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
+1 That's what I think.

That would explain why my phone never reboots with the screen on.

I think we may be onto something in this thread.
Sent from my SPH-D700 using XDA App

Agreed. My phone has always randomly rebooted when the screen is off. I set the minimum to 400 Mhz as well. Will let you know what goes down.

Someone should point the SamSprint devs to this thread lol. That would be amusing if it was in fact the problem/solution to random reboots.
Sent from my SPH-D700 using xda premium

Ok, so far 400mhz screen off has been stable, 12:56 on battery, and 1:01 screen on time.
I noticed something.. Here is what CPU Spy says:
1000mhz: 00:55:03
400mhz: 1:35:09
Deep Sleep: 9:22:42
I reset the stats once, which is why 1000mhz is 6 min different from the screen on time.
The phone was asleep for 11:55, but it was only in deep sleep for 9:22, what this tells me is when the screen is off and the phone needs to "do something" (I have Skype open 24/7, and 3 accounts in k9)it will jump up to 400mhz (or normally, anywhere between 100-1000mhz) for a time until it is finished, and then drop back into deep sleep.
It might be worth a try to bump up the voltage for 100mhz and 200mhz and see if that helps anything.

So I played around with the clock settings a bit in the last 24 hours. Here's what I've found:
If I set the minimum to 200Mhz or lower, and leave the phone alone, it continues to have random reboots. With the minimum set to 400Mhz, it sleeps fine all day long. I also tried adding in the profile to enable a minimum and maximum of 200Mhz when the screen is off. In the 4 hours that was set I didn't get any random reboots, but when I went to wake the phone up, it rebooted. And with the min/max set to 200 on the screen sleep profile on, if the screen turns off and I try to turn it back on, it would reboot. What I found to work best is if the screen off profile min and max is set to 400, and then the mains are at 200 min and 1000 max, it runs (so far for me) with out any reboots and the phone will wake up like normal again. This has been good for the last 10 hours, so I will continue to let it simmer and will see how it goes.
So I know that the 100Mhz and 200Mhz states were active and working in Froyo. If they aren't working correctly here, could it possibly be because Samsung set the voltages of those two freq's too low in GB?

when looking at the voltage settings for 400, they are lower in GB versus Froyo by -50. maybe thats causing the issue?

If its really this simple as far as clock and voltage how the hell does Samsung not find that.
Sent from my SPH-D700 using xda premium

What software are you guys using to adjust these settings, SetCPU? Is there a free alternative that does the same thing? Since I've been reading this thread, my phone has slept to death several times (EH06) - I'm hoping this solves it.

ss4rob said:
What software are you guys using to adjust these settings, SetCPU? Is there a free alternative that does the same thing? Since I've been reading this thread, my phone has slept to death several times (EH06) - I'm hoping this solves it.
Click to expand...
Click to collapse
SetCPU is free for xda members
Sent from my SPH-D700 using Tapatalk

I recently downgraded to EC05 due to the reboots, but left the EH17 Modem.
I still get reboots, and now believe the reboots are related to the modem, GPS issues, and general updating, as new e-mail notifications would sometimes be followed with an immediate reboot.
I'm gonna flash the EF02 Modem onto EH17 to see if it works, I have nothing to lose at this point as i'm returning my epic today. Stupid B and V dont work on my keyboard

radugb said:
So I played around with the clock settings a bit in the last 24 hours. Here's what I've found:
If I set the minimum to 200Mhz or lower, and leave the phone alone, it continues to have random reboots. With the minimum set to 400Mhz, it sleeps fine all day long. I also tried adding in the profile to enable a minimum and maximum of 200Mhz when the screen is off. In the 4 hours that was set I didn't get any random reboots, but when I went to wake the phone up, it rebooted. And with the min/max set to 200 on the screen sleep profile on, if the screen turns off and I try to turn it back on, it would reboot. What I found to work best is if the screen off profile min and max is set to 400, and then the mains are at 200 min and 1000 max, it runs (so far for me) with out any reboots and the phone will wake up like normal again. This has been good for the last 10 hours, so I will continue to let it simmer and will see how it goes.
So I know that the 100Mhz and 200Mhz states were active and working in Froyo. If they aren't working correctly here, could it possibly be because Samsung set the voltages of those two freq's too low in GB?
Click to expand...
Click to collapse
What scaling are you using?

This sounds more like a band-aid than a fix. Perhaps the system doesn't scale the clock speed properly when waking, and keeping the clock speed artificially high in sleep mode masks the problem.Not an ideal solution because it kills battery.

omair2005 said:
when looking at the voltage settings for 400, they are lower in GB versus Froyo by -50. maybe thats causing the issue?
Click to expand...
Click to collapse
Good catch. Here are the voltages on EH06 (as reported by Tegrak):
1000mhz
Core Voltage: 1275mv
Internal Voltage: 1100mv
800mhz
Core Voltage: 1200mv
Internal Voltage: 1100mv
400mhz
Core Voltage: 1050mv
Internal Voltage: 1100mv
200mhz
Core Voltage: 950mv
Internal Voltage: 1100mv
100mhz
Core Voltage: 950mv
Internal Voltage: 1000mv
Could someone list out the stock voltages on EC05?
Lord-Anubis said:
I recently downgraded to EC05 due to the reboots, but left the EH17 Modem.
I still get reboots, and now believe the reboots are related to the modem, GPS issues, and general updating, as new e-mail notifications would sometimes be followed with an immediate reboot.
I'm gonna flash the EF02 Modem onto EH17 to see if it works, I have nothing to lose at this point as i'm returning my epic today. Stupid B and V dont work on my keyboard
Click to expand...
Click to collapse
That is what I thought at first... But then I tried the EF02, and EE03 modems and still experienced reboots (I am currently on the EE03 modem).
poit said:
This sounds more like a band-aid than a fix. Perhaps the system doesn't scale the clock speed properly when waking, and keeping the clock speed artificially high in sleep mode masks the problem.Not an ideal solution because it kills battery.
Click to expand...
Click to collapse
While this is true (for now) it could lead to a more viable fix. If the voltage actually is lower in GB, that could be at least part of the problem.

Undervolting a Xoom - battery results included

I haven't been able to find any info on undervolting the Xoom, so have started this thread in the hope that some may find it beneficial.
What is undervolting?
It basically involves reducing the amount of electrical voltage running through the CPU. It does not affect the speed of the CPU at all, just the amount of power that it uses. The stock configuration of CPUs usually has a fairly high voltage, to cater for the fact that CPUs are not exactly identical.
Why undervolt?
Reduce power consumption, and therefore increase battery life.
Why not undervolt?
Can affect stability, and there is a small risk of damage to your device.
Disclaimer: Undervolting, like overclocking, does have the potential to damage your device. It's very rare, but not unheard of. I've never had a problem, but you may. Good luck, and don't blame me.
My config:
Model: MZ601 Xoom
Kernel: Tiamat Xoom v2.1.0
Undervolting software: SetCPU 2.2.4
My voltages before UV:
MHz mV
216 770
312 770
456 825
608 900
760 975
816 1000
912 1050
1000 1100
1200 1150
1408 1250
1504 1325
1600 1400
1704 1400​
So after doing a bit of testing, I've found that I can lower my voltages noticeably throughout the range, reducing the amount of power my Xoom uses, and prolonging my battery.
My UV voltages:
MHz mV
216 770
312 770
456 775
608 825
760 875
816 925
912 975
1000 1000
1200 1075
1408 1125
1504 1175
1600 1250
1704 1325​​
Notes:
It is not possible to UV any less than 770 mV (with the kernel I'm using anyway).
Given that the mV for the 456 CPU frequency is so similar to 216, I set my minimum clock frequency to 456, which makes the device more responsive.
So, you may want to try these voltages, and see how they work for you.
To test: (Instructions for SetCPU)
Set your min & max speeds to the same frequency, for example 456.
Set the voltage of the 456 frequency to an amount lower that the current amount, for example 775. (It's generally best to adjust your voltage down only 25mv at a time.)
Perform a "Stress Test", for at least about 5 seconds.
If the device locks up or reboots, the mV is too low - try a higher mV.
Once you've found the optimal voltage for that frequency, move onto the next one, for example 608, then 760, etc.
If your device locks up or freezes during testing, you can force a reboot by holding down the Volume Up button, and the Power button.
The voltages I've used above may work for you, or you may have to increase them a little on your device. You may also get better voltages than me - if so, please post your results.

Battery test results
Performed some battery performance testing by doing the following steps:
1. Set the screen to not turn off, and brightness to 10% (screen needs to be on to keep the stress test running, and brightness low to minimise the battery drain of the screen, as that's not what we're testing).
2. Disabled all network connections (WiFi, Bluetooth, Data, GPS) to minimise battery drain by other factors.
3. Closed all other apps, and did not use the Xoom at all during the tests.
4. Charged Xoom to 100%.
5. Set CPU speed to 1504mhz using SetCPU (both min & max frequencies the same for accurate testing).
6. Unplugged the Xoom.
7. Ran "Stress Test" for 2 hours (give or take 20 seconds).
I performed the above steps for both stock voltage, and undervolted voltage. Results as follows:
1. For stock voltage (1325mV on Tiamit Tachi kernel), battery life went down to 62%.
2. For undervolted voltage (1175mV, which is nice & stable for me), battery life went down to 72%.
Findings:
I was expecting battery savings, but not quite this much.
Standard voltage (at 1504mhz) at this CPU load, drains at about 19% per hour.
UV voltage at this CPU load, drains at about 14% per hour.
Standard voltage at this CPU load, the Xoom would drain battery entirely after about 5.26 hours.
UV voltage at this CPU load, the Xoom would drain battery entirely after about 7.14 hours.
In addition to the battery savings, the Xoom was only slightly warm after the UV tests, but very warm after the standard voltage tests. (Standard voltage test was performed first.)
Note: For general usage (email, browsing, basic apps & widgets), the CPU is not as heavily used. But in situations where the CPU is heavily used (such as intensive games), these results show there is significant potential for battery savings.

super nice tips. Tq very much

126-608 -175
Others -150
This is my settings... no prob at all.

Would I use setcpu app or just use the Moray(in settings) or does it matter

rayhodge02 said:
Would I use setcpu app or just use the Moray(in settings) or does it matter
Click to expand...
Click to collapse
Not sure what the "Moray" is, but any tool capable of undervolting should be ok. I like and use SetCPU, but I've tried other tools on other devices in the past, and they did similar things.

nobody wants to share their result after trying?

Very good job, I try
Sent from my Xoom using xda premium

pls share ur best result

I try your results and they're unstable in function off the useful task, exemple impossible to play simple games.
That's all right just for basic tasks like navigation, music ...
Sent from my Xoom using xda premium

Hmm, your stress testing seems inaccurate.
I used your values and did a stress test at each frequency for around 10 seconds. No problem. But my xoom restarted just 5 mins later while I was surfing the net.
So I increased each frequency by 25-50 and it stayed stable since then.

for me i just underclock my xoom to 912mhz. it is almost as fast as 1ghz. and i save battery alot.

Gregus59 said:
I try your results and they're unstable in function off the useful task, exemple impossible to play simple games.
That's all right just for basic tasks like navigation, music ...
Sent from my Xoom using xda premium
Click to expand...
Click to collapse
Try bumping up the voltages a little bit at a time, until you find a stable setting. The settings I listed are what are stable for my Xoom (even intensive 3D games), but CPUs vary. What I get, others may not, and others may get better than me.

musashiken said:
Hmm, your stress testing seems inaccurate.
I used your values and did a stress test at each frequency for around 10 seconds. No problem. But my xoom restarted just 5 mins later while I was surfing the net.
So I increased each frequency by 25-50 and it stayed stable since then.
Click to expand...
Click to collapse
They're not 100%. The longer you stress test, the more likely the CPU is stable, but 10 seconds gives a general idea. If unstable, just do as you did, and increase by 25mv or so.

omnia1994 said:
126-608 -175
Others -150
This is my settings... no prob at all.
Click to expand...
Click to collapse
Can you confirm your mV values? -175 sounds like a big saving. Surely your mV is not less than the minimum 770?
What kernel are you using?

do some proper tests to establish how much extra time you will get from a fully charged batt.
i would think its perhaps a tiny bit at most...
the screen would take a huge amount of the batt, the processor would use only a small percentage, so surely cutting a small fraction off a couple of steppings is fairly pointless?

baron von bubba said:
do some proper tests to establish how much extra time you will get from a fully charged batt.
i would think its perhaps a tiny bit at most...
the screen would take a huge amount of the batt, the processor would use only a small percentage, so surely cutting a small fraction off a couple of steppings is fairly pointless?
Click to expand...
Click to collapse
1. It depends what you're using the device for. Games, for example, can use a lot of CPU, so undervolting in this instance, will definitely use noticeably less battery.
2. If CPU voltage throughput didn't make any difference, we'd all just run our devices at 1700mhz all the time.
3. With undervolting, I can run my Xoom at the same voltage at 456mhz, as it run at 216mhz. This means I set my minimum frequency to 456 instead, and for the same minimum battery consumption, my device is noticeably smoother.
If you want to know how much extra time you will get from a fully charged battery, YOU do some tests.

lindsaytheflint said:
Can you confirm your mV values? -175 sounds like a big saving. Surely your mV is not less than the minimum 770?
What kernel are you using?
Click to expand...
Click to collapse
Yes i m sure. Has been using these settings till now.. no prob at all. Using tiamat stock gpu kernal with moray rom

i agree that during low intensity operation the power savings are probably nearly negligible, but during CPU-intense usage it could save a bit.
I myself am not willing to leave my Xoom on full bore for a series of tests lasting 7-10 hours each just to quantify how much power undervolting can save under super extraordinary circumstances.
But even if the energy savings is an arguable benefit, the reduction in CPU temperature is not. That alone makes this worth doing, IMO.

Agree.. after setting it my xoom now has lower temp when playing it

standby time for miui

How do i increase my standby time with miui on?
Some say to undervolt, but idk how to do that.

Use voltage Control an test the waters an see how phone reacts -25 across board first an sleep profile also build prop tweaks
Sent from my GT-I9000 using XDA App

Jasonhunterx said:
Use voltage Control an test the waters an see how phone reacts -25 across board first an sleep profile also build prop tweaks
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I just got Voltage Control (the free one)
but I don't get how to use it. Can you please guide me? Which Mhz is sleep profile? and what do you mean build prop tweaks?

Well its pretty simple open app click second tab the you will see sliders you slide them down slide it down 1 notch
Sent from my GT-I9000 using XDA App

But like which ones? I set the 100 to -25 and went to sleep and most 13% overnight.
Which other ones should I set there.sorry for the questions I just don't want to mess up my phone

Start with these
100 = -100
200 = -75
400 = -50
800 = -25
1000 = - 0 (Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.

}{Alienz}{ said:
Start with these
100 = -100
200 = -75
400 = -50
800 = -25
1000 = - 0 (Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.
Click to expand...
Click to collapse
So basically, I have to go through the voltages (-#'s) and see how low i can go without crashing?

}{Alienz}{ said:
Start with these
100 = -100
200 = -75
400 = -50
800 = -25
1000 = - 0 (Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.
Click to expand...
Click to collapse
What would happen if you set it to 1000= -0 ??? Couldn't you just odin back to stock if the phone crashed?

}{Alienz}{ said:
Start with these
(Don't touch it).
If that works, undervolt more till it starts crashing. If it doesn't work, lighten the undervolts. What I'm giving you is a starting point.
Click to expand...
Click to collapse
I UV crazily but It doesn't seem to help much with Battery Life
My Settings
100 = -500
200 = -150
400 = -125
800 = -100
Max Freq. is 800
Conservative CPU Governor

check this out
http://forum.xda-developers.com/showthread.php?t=829731

nbhnohome said:
I UV crazily but It doesn't seem to help much with Battery Life
My Settings
100 = -500
200 = -150
400 = -125
800 = -100
Max Freq. is 800
Conservative CPU Governor
Click to expand...
Click to collapse
I don't think I want to go THAT low, maybe it'll crash my phone or someting?
caldran said:
http://forum.xda-developers.com/showthread.php?t=829731
Click to expand...
Click to collapse
that thread doesn't help. I've seen it before, its just info.

I think people are answering the wrong question. Or I should say, giving answers to a different question.
To the OP: You're talking about Deep Sleep battery usage, right? There's no way to undervolt Deep Sleep. It's already using very minimal voltage. I believe what causes excessive Deep Sleep battery drain is the number of apps still running and using the CPU during Deep Sleep.
Undervolting will help a bit with battery drain during normal usage. For Deep Sleep, turn off your various apps' syncing ability, as well as freezing programs you don't use but that run in the background. For instance, if you don't use navigation very often, consider freezing the Maps app, as it runs all the time in the background. A number of popular games like to run in the background like GunBros and Aqua Pets. Also switch from 2g/3g or 3g to 2g only at night to save battery there.
To recap, the less you have running in the background, the less battery you'll lose when you phone is in Deep Sleep.

I was also going to say switch to 2g if you don't need the speed. It helps a lot for me. I also usually put my phone in flight mode before I sleep. I lose like 0.5% of battery an hr on flight mode. I'm not on MIUI yet, still on froyo, but should still help.

I am using these and getting good battery life
1000 MHz -50mV
800 MHz -75mV
400 MHz -100mV
200 MHz -150mV
100 MHz -200mV

mohitmoudgil said:
I am using these and getting good battery life
1000 MHz -50mV
800 MHz -75mV
400 MHz -100mV
200 MHz -150mV
100 MHz -200mV
Click to expand...
Click to collapse
that crashes my phone as soon as i put "apply" lol i tried it twice, so probably not a good sign for my phone.

Can I do voltage Control on stock MIUI Kernal or do I need Neo?
Sent from my Vibrant.

In my experience (admittedly only been on MIUI for a few weeks), Pimp my CPU, Voltage Control, and SetCPU all work fine on MIUI, so yes. You should be able to use Voltage Control. Not entirely sure about Stock MIUI, but if you use the (superior) Revamped version (either SS or Lithium editions) the kernel that comes stock with it allows you to change voltages, though I would still recommend moving to Glitch and using either the ML or LL versions if you want to maximize battery savings.
that crashes my phone as soon as i put "apply" lol i tried it twice, so probably not a good sign for my phone.
Click to expand...
Click to collapse
OV/UV settings can vary widely between phones. Some offer little to no leeway at all, and can't even be overclocked to the rather tame 1200mhz. Others can sit at 1700mhz at 100uv. It's luck of the draw really. Also, Conservative Governor will be kinder to more exotic UV settings, while others like Smartass or OnDemand may only allow for a slight 25 or 50uv for most voltage levels.
Trial and error, my friend. Find what works best for your phone.

Thanks guys.
One more question
If when I test if my phone can handle a certain UV is it good to have it at the lowest I can?
Like example
My 400mhz can go down to -200UV is that good or bad? Should I keep it that low if its not crashing or anything

You need to do some stress testing to be sure it's stable at those frequencies. Depending on the governor you use, your phone may not hit 400mhz often enough for you to really tell if it's stable or not. You could set 800mhz to -800uv, but if your phone tends to skip over 800mhz most of the time...
Undervolting can cause other problems if it's not completely stable. For instance, on Froyo I would get annoying static during music playback. Took me nearly a month to figure out that it was because I was undervolting the 400 to 100mhz range too much.
Undervolting doesn't make THAT big a difference. If you don't want to tweak and stress test and tweak and tweak again and stress test again, etc etc etc, then just reasonable settings that most phones can handle. For instance, 1200 0uv, 1000 25uv, 800 50uv, 400 75uv, 200 100uv, 100 125uv.

xriderx66 said:
How do i increase my standby time with miui on?
Some say to undervolt, but idk how to do that.
Click to expand...
Click to collapse
In my experience when I switch to only use only 2G networks I get damn near twice the standy time. Also, changing wifi to never sleep and staying connected to wifi has about the same effect. This also holds true for CM7.
3G is a battery killer for MIUI and CM7
The only resolution I see to this is a GB source drop but I'm not holding my breath.
Off topic but does anyone know a good, fast device that runs CM7/MIUI without bugs or this horrible battery drain? I've been running some form of CM7 since Eugene's build this spring and it has gotten MUCH better but I'm kind of disappointed at the lack of vibrant-specific progress lately. There's only so much the devs can do without source (or a working vibrant and a T-Mobile data plan for that matter....). Don't get me wrong, I'm thankful for what we have and what the devs have given us but I'd love GPS that isn't f'd and 3G that doesn't suck my battery dry in a little over 10 hours (working 911 wouldn't hurt either.
Sent from my T959 using xda premium