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.**************************************************************************************

oc'd phone heating up during normal use and poor battery life

Well ill start off by saying I'm new here and this is my first post. I'm also very new to this stuff and have a lot to learn. A buddy of mine recently rooted and overclocked my phone using the sense 2.6.32.21 1.5ghz oc/uv kernel. I currently have it set to 1.19 max 768 min and am experiencing temps above 107 running emulators and just web browsing.. I am also seeing pretty poor batt life even using battery booster and advanced task killer.. any help is greatly appreciated!

Battery apps and task killers tend to have the opposite of their intended effect on battery. Android has a built in utility to watch battery usage, why do you need a 3rd party one? Also do some reading on task killers, you will see why they are unnecessary on Android. I've stopped using one and my phone runs faster and more stable than before.

768 min is VERY high. Might explain the heating and battery life drain quite a bit.
Try this for me, please. Set your governor to interactive and drop your min down to 245. Run that for a whole charge. You may be surprised.
Sent from my PG06100
Also, I second the post above me. Advanced Task Killer and anything like it ultimately cause more harm than good. Battery apps, such as Juice Defender, also shouldn't be necessary. Although, it is YOUR phone.

Thanks a lot for the replys. I set the min to 245 and am seeing serious changes in temps. I also uninstalled atk but installed appkik. I am also still running battery booster but may get rid of it soon.. I feel like this phone should have better batt life. Any suggestions?

bearsblack said:
Thanks a lot for the replys. I set the min to 245 and am seeing serious changes in temps. I also uninstalled atk but installed appkik. I am also still running battery booster but may get rid of it soon.. I feel like this phone should have better batt life. Any suggestions?
Click to expand...
Click to collapse
well they gave some suggestions. which it seems you dont want to listen to. you dont need task killers of any kind

Sorry I'm stubborn. Uninstalling now

No disrespect here, but seriously, if you don't know what and why you're overclocking, don't know the inherent risks, etc, why are you doing it?

Compusmurf said:
No disrespect here, but seriously, if you don't know what and why you're overclocking, don't know the inherent risks, etc, why are you doing it?
Click to expand...
Click to collapse
because all the cool kids are doing it smurf...duh.
But seriously, min. should not be set at anything greater then 245. Only use performance if you are benchmarking. Default at the moment should be interactive.

Just gonna add my 2 cents in from personal observation....after doing some reading on overlooking and stuff I've noticed when going into the different ## modes, the shift usually drops its processor cycles to pretty low numbers in the 200-300 mhz range when its just in standby or not doing anything...it only kicks it up when you need the power. So the heating up is probably caused by constantly running at what used to be its max territory...PLUS youre going above and beyond the original limits/specs at a constant so it never gets to relax even when the phone is idle...I hope that makes sense. So as one poster mentioned keep the min at the stock setting and if you really want to/need to then raise the max mhz to whatever your phone can handle reliably. Correct me if I'm wrong anyone who is more into the overlooked setups. Me personally, stock has been able to keep up with whatever I have thrown at it after 30 days and still getting 25+hrs on one charge.
Sent from my PG06100 using XDA App

I currently have it governed at 245 max screen off. Running 1.2ghz max interactive with no task killers or batt savers. Batt life seems to be somewhat better but temps still creep past 105. Thanks a lot for the info

alittle off of the beaten path, but i tried runing 245/1801 interactive on evervolv and noticed alot of random reboots. set it back at on demand and am having good luck with that. why is everyone leaning towards interactive??

Excuse me if I am wrong it's early and im too lazy to reread up on it but I believe the difference is with on demand there is a slight delay(second or two) and it gradually kicks up to where it needs to be where is interactive is a spike the second you need it...

JAREDR said:
alittle off of the beaten path, but i tried runing 245/1801 interactive on evervolv and noticed alot of random reboots. set it back at on demand and am having good luck with that. why is everyone leaning towards interactive??
Click to expand...
Click to collapse
Interactive is, usually, a lot better for battery life.
If you look at your cpu's scaling history when on the two, TYPICALLY, you'll see a whole lot more time in higher frequencies using ondemand.
That's not to say, however, that with some devices and some kernels they will act the same.
Sent from my HTC Speedy

help me with setcpu profiles

can someone help me with set cpu profiles. I think I set it correctly, but battery life not what i'm expecting. i'm running ACS newest rom. I have it set to ondemand 100-1000 as the base. then I have a profile for screen off that specifies 100-200 conservative. so shouldn't it basically just be sitting at 100-200 most of the time since the screen is usually off? when I check it seems to be using 1000 an aweful lot which is weird for something that isn't using that unless the screen is on.

Those settings look right to me. I bumped my idle up to 400 though incase any background services need it. If its too underclocked it will stress the battery even harder if a service needs more from my understanding. Try calibrating your battery and downloading juice defender. I caught some flack in the ACS thread for these two things but after 7 idle hours last night I only lost 6%. Having the screen on is the biggest drain but there may also be other factors at play in your case.

SetCPU app and it's effectiveness? Syndicate Frozen ROM

Hey there, I just a few days ago rooted and flashed the Syndicate Frozen rom and am not getting such good battery life...
I was wondering how big of a difference SetCpu makes on battery life/performance in general? With moderate/heavy use (internet browsing, facebook, email, txt messaging) how much should it improve battery life? am getting around 10hours at the moment with moderately light use... Is there any free alternative app that runs comparatively well?
I guess what I'm really asking is: is it worth it to buy setcpu, and will it make a dramatic difference on my battery life? This Rom is supposed to improve battery life, and I think I read is overclocked to 1.2... Will setcpu let me set this underclocked to 1,0 and then like 800 with screen off, 600 idle? Am new to the android thing [have had my EPIC only around 2 weeks today]
Thanks for any help!

Overclock widget does pretty much the same thing, and you're going to want to set something like
20mhz min 1 or 1.2ghz max
Then 100mhz min 400mhz max for screen off.

You can set the speed to.anything you want. If you want battery to be the best then.set it to 100/1000 on demand. If you emwant performance then 100/1200. Also I don't set profiles cause I was reading somewhere that they aren't good to use on any galaxy phone.
Sent From My Evo Killer!

http://www.setcpu.com/
Nice info read up on it and yes you can set it anyway you want like stated above. I bought mine from the market to support the dev for the hard work involved in making setcpu, dont know if you know but it is free for xda members just search for setcpu. It is only $2.00 well worth the price so please support the dev if you can.

063_XOBX said:
Overclock widget does pretty much the same thing, and you're going to want to set something like
20mhz min 1 or 1.2ghz max
Then 100mhz min 400mhz max for screen off.
Click to expand...
Click to collapse
20Mhz would freeze the phone. :O
I personally like running it @ 100 Mhz when screen is off and 1Ghz when screen is on.

Overstew said:
20Mhz would freeze the phone. :O.......
Click to expand...
Click to collapse
I am pretty sure XOBX meant 200, cause your right 20 is pretty much crawling...

Yep, I meant 200, the damn autocorrect kept changing mhz to Hz and I must've clicked backspace one too many times.

Thanks, so it would make a big difference in battery life?
Sent from my EPIC 4G FROZEN and Syndicated

androikid said:
Thanks, so it would make a big difference in battery life?
Sent from my EPIC 4G FROZEN and Syndicated
Click to expand...
Click to collapse
Don't expect it to magically give you another 4 hours up time. 1 extra hour would be high hopes.

I use SetCPU with the CPU set to 200/1000 and ondemand, and the battery life has improved GREATLY, well worth the $2 to support the Dev, IMO, even though XDA members get it free.

I've abandoned SetCPU and uninstalled it. Unnecessary consumption of system resources.
Same with any other user-space app/widget to control CPU speed scaling.
In the Bonsai ROM, the exact same capability, sans the profiles which I (and most people) don't use anyway, can be achieved by setting clock range and governor in /etc/init.d/24-cpufreq script. I expect that all the other OC kernels, if not every custom kernel, has a similar way to set CPU clock governor.

I have mine set to 100/1200 on demand, and it works well for the demands I put on it. Way low consumption at idle, but when I need something it instantly responds.
I routinely get 16-18 hours off the charger, and put it back on the charger with sometimes as much as 40% remaining, but as always YMMV. A lot of it has to do with the ROM, but I'd say that CPU scaling has realized a tangible gain for me.

dwallersv said:
I've abandoned SetCPU and uninstalled it. Unnecessary consumption of system resources.
Same with any other user-space app/widget to control CPU speed scaling.
In the Bonsai ROM, the exact same capability, sans the profiles which I (and most people) don't use anyway, can be achieved by setting clock range and governor in /etc/init.d/24-cpufreq script. I expect that all the other OC kernels, if not every custom kernel, has a similar way to set CPU clock governor.
Click to expand...
Click to collapse
Talking about Bonsai ROM tweaks on a Syndicate thread would be like me talking about BMW mods on a Honda forum. Either way, I looked around in the system folders and I can't find the 24-cpu file you're talking about. I upgraded yestereday from the 2.1 SyndicateROM to this, and for the first few hours, the ROM itself was definately quicker...I don't know if that's just because I came from 2.1 to 2.2, not to mention all the other 2.2 tweaks. After a few hours, I completely forgot that I could overclock this to 1.2Ghz. Installing SetCPU and bumping it to 1.2Ghz felt like just another jump. System resource consumption aside, it makes the phone all that much quicker while going between screen, apps list, closing apps, etc.
I could care less about battery life because I've learned to always have a charger around me since my days of the Moment, of hell, even my Treo's. I want fast, SetCPU is something I can see the difference in just from turning it on and off and seeing the differences.

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.