Develop Bugs

[Q] Battery life has me at my wits end! Help please!!!

Ok. So I have a G2, with CM7R4. I have SetCPU with all sorts of profiles and JuiceDefender on Extreme. I still can't get more than 6-7 hours out of my battery. I take it off the charger before I leave for work, and before I even clock out, the phone is dead. This is whith even minimal usage. The thing is, with minimal and heavy use, I get about the same battery life. What could possibly be causing this?
I went in to Battery Stats, and Cell Standby was at 60% or more, but my browser (which I've been using for 3 or so hours, and a game I've been playing for about the same, are both only at 2%. I went in to Spare Parts, and it showed the phone has been running constantly for about 3 hours with no sleep, even though I've shut the screen off and stopped using it completely numerous times in the last 3 hours.
There has got to be something I can do. How are people getting 2 days uptime when I can't even get 8 hours? Someone help please!
Edit: Thank you everyone for your suggestions! I drained my battery, wiped battery stats, removed a bunch of SetCPU profiles, and installed Green Power to regulate my data usage. I've seen no decline in functionality, but I have already begun to see a vast battery life improvement.

Stop using setcpu.
Sent from my G2 running Cyanogenmod 7.

Do you have a reason for this? I was told to start using SetCPU the last time I brought this issue up.

What are you setCPU profiles?

Oh yeah, if you made your profiles all whack, the cpu will be constantly running. Specifically if you've set a performance governor anywhere. The more you mess with the profile creator, the more battery life you can free up easiest way to learn is to play around with the governors from time to time.
Sent from my HTC Vision using XDA Premium App

Kevin001111 said:
What are you setCPU profiles?
Click to expand...
Click to collapse
In descending priority they are:
Screen off 245/245 ondemand
Temp >45.5c 806/245 ondemand
Charging 1516/245 ondemand
Battery <10% 286/245 powersave
Battery <25% 768/245 ondemand
Battery <50% 1113/245 ondemand
And my default is 1516/245 ondemand

detox702 said:
In descending priority they are:
Screen off 245/245 ondemand
Temp >45.5c 806/245 ondemand
Charging 1516/245 ondemand
Battery <10% 286/245 powersave
Battery <25% 768/245 ondemand
Battery <50% 1113/245 ondemand
And my default is 1516/245 ondemand
Click to expand...
Click to collapse
Why are you charging your phone at 1516 max? Your max for charging should be 806 (stock clock), to prevent excessive heat.
Have you tried wiping battery stats in ClockworkMod recovery?

I had the same when I flashed CM7 RC4!
How I fixed it:
1: let the battery drain, until it goes off.
2: you still have power to boot it in the recovery mode.
3: delete the battery stats (advanced tab)
4: reboot the device
5: charge it (device on or off doesn't really matter I think).
My battery was drained after 8 hours without much usage... now I get over 28 hours even with average use
also I only got 2 profiles @ setCPU: screen off min 386/ max 786mhz and the main profile: 806mhz max / 386 min and my device is not laggy or sluggish.
Using the pershoot kernel 2.6.32.36 and stock radio.

SnowOokami said:
I had the same when I flashed CM7 RC4!
How I fixed it:
1: let the battery drain, until it goes off.
2: you still have power to boot it in the recovery mode.
3: delete the battery stats (advanced tab)
4: reboot the device
5: charge it (device on or off doesn't really matter I think).
My battery was drained after 8 hours without much usage... now I get over 28 hours even with average use
also I only got 2 profiles @ setCPU: screen off min 386/ max 786mhz and the main profile: 806mhz max / 386 min and my device is not laggy or sluggish.
Using the pershoot kernel 2.6.32.36 and stock radio.
Click to expand...
Click to collapse
is it really necessary to let the battery drain in order to wipe the battery stats? I'm thinking about trying this myself, but there's some debate on whether or not the battery should be drained or not in other threads.
Sent from my HTC Vision using XDA Premium App

ohshootrawr said:
is it really necessary to let the battery drain in order to wipe the battery stats? I'm thinking about trying this myself, but there's some debate on whether or not the battery should be drained or not in other threads.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
True it's not "healthy" to drain a li-on battery, but it's not 100% drained and I've been without power several times because I forgot to turn it off before I got home to charge it
Also in my opinion a 1-time total drain doesn't damage the battery. Just let your navigation on till it's empty (leave the screen on too) it will go off, you will be able to boot the phone once or twice after that, so it's not a 100% drain, boot in recovery mode then delete the battery stats, reboot and put the charger in it. That did the trick for me. Hopefully it works for you too
I guess you could do it the other way around, charge the phone completely, wipe the battery stats, drain it till it goes off and reboot. That takes a bit longer I guess.

You said it was the "phone" using most of your battery? I know there was or is a setting in cm "flip to ignore" that when enabled it kept the phone awake. Worth a shot...

Why are you charging your phone at 1516 max? Your max for charging should be 806 (stock clock), to prevent excessive heat.
Click to expand...
Click to collapse
That's why I have the temp. profile. I basically have to have my phone in a charger at all times, otherwise it dies. So I have it set to run at max so my games and whatnot work well.
I had the same when I flashed CM7 RC4!
How I fixed it:
1: let the battery drain, until it goes off.
2: you still have power to boot it in the recovery mode.
3: delete the battery stats (advanced tab)
4: reboot the device
5: charge it (device on or off doesn't really matter I think).
My battery was drained after 8 hours without much usage... now I get over 28 hours even with average use
also I only got 2 profiles @ setCPU: screen off min 386/ max 786mhz and the main profile: 806mhz max / 386 min and my device is not laggy or sluggish.
Using the pershoot kernel 2.6.32.36 and stock radio.
Click to expand...
Click to collapse
Thanks! I'll try this today, because my phone will undoubtedly die before I get home from work. I'd love to get 28hrs use. Last night, I got 7h30m30s on battery. That's good compared to what I usually get, but it left me without a phone during the deadest part of my shift.
You said it was the "phone" using most of your battery? I know there was or is a setting in cm "flip to ignore" that when enabled it kept the phone awake. Worth a shot...
Click to expand...
Click to collapse
Thanks! I'll look and see if this is causing it. I wouldn't've turned it on, but maybe it's on by default?

You need to recalibrate it by doing what that one post said, after using so many roms, your phone battery needs to be recalibrated

Since I've got the phone, I've only used CM, but I have used at least 5 different versions. I'm working on killing it right now. It'll be dead much earlier than usual with all the use its's getting, and I was smart enough to bring a charger so I can charge it as soon as it dies and gets recalibrated.

Let me know if it works for you!

detox702 said:
In descending priority they are:
Screen off 245/245 ondemand
Temp >45.5c 806/245 ondemand
Charging 1516/245 ondemand
Battery <10% 286/245 powersave
Battery <25% 768/245 ondemand
Battery <50% 1113/245 ondemand
And my default is 1516/245 ondemand
Click to expand...
Click to collapse
I had a setup similar to this (many different profiles) and I had awful battery drain. I read in a thread somewhere here that it was setcpu that was the culprit of the excessive drain because having many profiles has it constantly using cpu power.
I have since switched my default to 1017/245 on demand and now I only use a screen off profile at 245/245. Since making that change, my battery life improved significantly (25-30% improvement)
I don't do anything that requires the full 1.5ghz on my phone which is why I now run at 1ghz but definitely feel that the setcpu profiles cause some major drainage...

SnowOokami said:
True it's not "healthy" to drain a li-on battery, but it's not 100% drained and I've been without power several times because I forgot to turn it off before I got home to charge it
Also in my opinion a 1-time total drain doesn't damage the battery.
Click to expand...
Click to collapse
Its unlikely, but possible your battery will not take a charge after you discharge the battery too low (safety circuit does not properly kick in). I've seen this problem crop up (pretty occasionally) from time to time back on the Touch Pro 2 forums, and have seen it happen here to a couple people on the Vision as well.
The battery meter is not all that accurate, anyway. Most of what you suggest if fine: to delete battery stats, let it charge to full, but then drain to 10% or so. You aren't really gaining much by doing that versus totally empty, and its safer.

TrueYears said:
You need to recalibrate it by doing what that one post said, after using so many roms, your phone battery needs to be recalibrated
Click to expand...
Click to collapse
There is no such thing as calibrating a Li-ion battery. You are calibrating the battery meter on the phone.

[Q] What is the best kernals for Cyanogen mod 7 rc4

Hi I've been looking around to find good kernals while running cyanogen mod 7 rc4. Some of the kernals I install like netatchy gives the screen a weird flickering. Can someone suggest a good kernal that's overclockable and stable. Thanks

Netarcys kernel really isn't for cm7 that's probably why its flickering. You should try savage zens latest sbc or non sbc kernel or tiamats sbc kernel both are pretty good. I'm running the tiamat sbc 3.3.4(great battery life) and I'm pretty happy with it.
Tiamat link. Be sure to get the evo version because he does kernels for the incredible also.
http://forum.xda-developers.com/showthread.php?t=972746
Sent from my PC36100 using XDA Premium App

Thanks! Ill try them and I'm kinda new to kernals so what is the difference between SBC and no SBC

chvezsd said:
Thanks! Ill try them and I'm kinda new to kernals so what is the difference between SBC and no SBC
Click to expand...
Click to collapse
In a nutshell, sbc is a method of charging that allows you to "fully"(trickle) charge your battery. Normal kernels really only let you charge to about 90% for safety measures; while sbc lets you fully charge letting your battery completely fill. There's a few threads that talk about it if you search around to get more "details". I've been using them for months without any problems whatsoever. Good luck

Honestly I get great performance out of the stock kernel.
Sent from my PC36100 using XDA App

Thanks, I just flashed the tiamat 3.3.4 SBC and everything so far is great! Btw I couldn't find it in the changelog but does this fix 4g cuz on stock kernal both the 3g icon and 4g icon show
Sent from my PC36100 using XDA App

It's called a kernel.
Sent from my PC36100 using XDA App

chvezsd said:
Thanks, I just flashed the tiamat 3.3.4 SBC and everything so far is great! Btw I couldn't find it in the changelog but does this fix 4g cuz on stock kernal both the 3g icon and 4g icon show
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
That happens to me sometimes but not all the time. I believe that's still a problem with cm7 in general though. For best results I recommended going to settings/ cyanogenmod settings/ performance/CPU settings then use the "smart ass" governor. It has provided me with the best overall battery/performance. I also have my min freq at 245 and max freq at 1152.

Those are also my settings, I've discovered my evo can't go beyond 1.15ghz without locking up. I've been trying to get to 1.2 but no go
Sent from my PC36100 using XDA App

chvezsd said:
Those are also my settings, I've discovered my evo can't go beyond 1.15ghz without locking up. I've been trying to get to 1.2 but no go
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Ahh neither can mine its reboot nation once I pass up 1190mhz.

Yeah wish i was a lucky one :/, so after installing kernels I'm getting 41.2 mflops and my quadrant benchmark is 1221
What are you getting?
Sent from my PC36100 using XDA App

chvezsd said:
Yeah wish i was a lucky one :/, so after installing kernels I'm getting 41.2 mflops and my quadrant benchmark is 1221
What are you getting?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I don't really put so much stock in scores anymore they don't mean anything to be honest. Dirk used to be a score whore but I just removed the apps so I wouldn't worry about it anymore. I came to terms that my scores won't go much higher then what they already were. Just ran 40 mflops and 1220 bench.

Yeah I just like the braging rights, hopefully they can figure how to overclock the gpu soon tho
Sent from my PC36100 using XDA App

chvezsd said:
Yeah I just like the braging rights, hopefully they can figure how to overclock the gpu soon tho
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Bragging rights how's this for bragging rights; my 12 year old cousin has a tmobile g2(newer processor) which is stock clocked at only 800mhz. His phone scores a 60 on linpack and over 1500 on benchmark and its not even rooted lol. This is why I don't care about scores anymore

I just died a little inside :/ lol I wanna upgrade to the evo 3d soon tho and that's a dual core
Sent from my PC36100 using XDA App

dirkyd3rk said:
In a nutshell, sbc is a method of charging that allows you to "fully"(trickle) charge your battery. Normal kernels really only let you charge to about 90% for safety measures; while sbc lets you fully charge letting your battery completely fill. There's a few threads that talk about it if you search around to get more "details". I've been using them for months without any problems whatsoever. Good luck
Click to expand...
Click to collapse
I just wanna correct this misconception because it led me astray and it took a good amount of research to realize this was wrong.
All kernels will charge the phone to 100%. That's not an issue. What happens is, once they are charged to 100%, they start draining battery again, and coupled with the fact that li-ions inherently lose charge over time, and the fact that most people haven't conditioned their battery's memory by properly charging it, by the time you pull your phone off the charger it's already lost that 10% (give or take).
Trickle charging hopes to fix this by "trickling" a small charge into the battery constantly once it hits 100%, to compensate for discharge, so that it stays at 100%. The problem with this is, it pushes a current through the battery constantly, and that tends to shorten the life of lithium-ion batteries over time. You may get better immediate battery life off the charger, but you'll kill your battery quicker. Come months from now, your battery life isn't going to be what it should, whether you notice it or not.
If you want to minimize the discharge, you can take a couple safer steps:
- Condition your battery. Charge it to a true 100%. This will mean turning the phone off and on a few times while it's on the charger to make sure it's actually at 100%. Then completely discharge it until the phone cannot turn back on. Do this a couple times in a row, and repeat every month or so. This conditions your li-ion battery's internal charging memory so it knows its true charge potential.
- Charge your phone while it's off. It won't drain nearly as much battery this way, so when you're ready to take it off the charger it'll be much fresher.
- Avoid prolonged charging and continuous charging, because it can confuse the li-ion's internal charging memory. Rather than re-charging it when it hits 60%, let it drain as low as possible before you bother recharging it. Bursts of short charges don't harm the battery, but they make it "forget" how much it can be charged.
In short, SBC kernels are bad for your battery.
---
Also, Savaged-Zen 1.0.1 BFS no-SBC has been the best kernel I've found for the Evo 4G. Granted I haven't had this thing that long and there may be another gem lying around somewhere, but given the popularity of SZ, I doubt it. It's a very good, smooth kernel. It's giving me the best performance of what I've tried (most of the popular ones).
As for CFS vs BFS, flip a coin. Some will swear CFS is smoother, others will swear BFS is supposed to be smoother. BFS gives me more responsiveness personally, but I think it mostly depends on your workload. I keep scarcely-used tasks killed and I don't use widgets, so the lack of many processes may be what makes BFS better for me. Try both and see which feels smoother in daily use.

router54g said:
I just wanna correct this misconception because it led me astray and it took a good amount of research to realize this was wrong.
All kernels will charge the phone to 100%. That's not an issue. What happens is, once they are charged to 100%, they start draining battery again, and coupled with the fact that li-ions inherently lose charge over time, and the fact that most people haven't conditioned their battery's memory by properly charging it, by the time you pull your phone off the charger it's already lost that 10% (give or take).
Trickle charging hopes to fix this by "trickling" a small charge into the battery constantly once it hits 100%, to compensate for discharge, so that it stays at 100%. The problem with this is, it pushes a current through the battery constantly, and that tends to shorten the life of lithium-ion batteries over time. You may get better immediate battery life off the charger, but you'll kill your battery quicker. Come months from now, your battery life isn't going to be what it should, whether you notice it or not.
If you want to minimize the discharge, you can take a couple safer steps:
- Condition your battery. Charge it to a true 100%. This will mean turning the phone off and on a few times while it's on the charger to make sure it's actually at 100%. Then completely discharge it until the phone cannot turn back on. Do this a couple times in a row, and repeat every month or so. This conditions your li-ion battery's internal charging memory so it knows its true charge potential.
- Charge your phone while it's off. It won't drain nearly as much battery this way, so when you're ready to take it off the charger it'll be much fresher.
- Avoid prolonged charging and continuous charging, because it can confuse the li-ion's internal charging memory. Rather than re-charging it when it hits 60%, let it drain as low as possible before you bother recharging it. Bursts of short charges don't harm the battery, but they make it "forget" how much it can be charged.
Click to expand...
Click to collapse
What he said
http://forum.xda-developers.com/showthread.php?t=894880

Thanks for all the info! I'm just gonna try SBC for a month then try non SBC for a month and see witch I would prefer better. Also for the Zen kernels do they break anything that's not already working? And would they give better 3d performance then the tiamats kernel?
Sent from my PC36100 using XDA App

chvezsd said:
Thanks for all the info! I'm just gonna try SBC for a month then try non SBC for a month and see witch I would prefer better. Also for the Zen kernels do they break anything that's not already working? And would they give better 3d performance then the tiamats kernel?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
That's a great plan man. I visited the savage zen kernel thread earlier and some are complaing about their newest build causing charging issues or something along with 100% wake time idk. If you give it a shot use their 1.0.0 instead of the 1.0.1. Just give the kernels about a week and see how well they hold up. Its mainly about personal preference(sbc or non sbc) I'm actually testing the tiamat sbc but I was previously on savage zen. I like to give all kernels a chance(1 or 2 weeks) to see how well my phone performs with them.

Ok well ill just wait till Friday to install a new one then and see how the Zen works out
Sent from my PC36100 using XDA App

Root/rom/battery question

Droid incredible. Rooted, virtually every rom through rom manager causes my phone to battery to drain very fast.
After a charge itll drop to 90% in about twenty minutes. Iv heard thats a droid thing.
From that point, it steadies but still is losing juice FAST. Phone has been awake for 8hrs today with light usage and is currently at 70%. Gps off, wifi off, etc. No vibrating feedback, auto brightness.....all settings geared for battery conservation.
Im using Incrom 1.6 with a stock kernal. Any ideas or thoughts are appreciated as i dont stop hearing that everyone in the world is rooted and enjoying their batterys new ability. Ohhh, btw extended battery, red htc one in case that matters.

mikeurce said:
Droid incredible. Rooted, virtually every rom through rom manager causes my phone to battery to drain very fast.
After a charge itll drop to 90% in about twenty minutes. Iv heard thats a droid thing.
From that point, it steadies but still is losing juice FAST. Phone has been awake for 8hrs today with light usage and is currently at 70%. Gps off, wifi off, etc. No vibrating feedback, auto brightness.....all settings geared for battery conservation.
Im using Incrom 1.6 with a stock kernal. Any ideas or thoughts are appreciated as i dont stop hearing that everyone in the world is rooted and enjoying their batterys new ability. Ohhh, btw extended battery, red htc one in case that matters.
Click to expand...
Click to collapse
Try flashing some new kernels..try a couple out. If that doesn't work did you over charge your phone? Or use a car charger?
sent from my Dinc

Its not the battery cause when i revert to stock the battery is normal for what im used to. The change is noticable wen i use any of the custom roms.
Right now wrkng on flash radio, hit a bump waiting for email back.
Ne other suggestions from u or nebody wud be apreciatd

I use the app batterycalibration after flashing new roms it works well for me
Sent from my ADR6300 using XDA Premium App

Everybody's definition of "light usage" is different. Losing 20% in 8 hours doesn't seem that bad to me unless you litterally never turned your screen on. That said, here are some things you can try:
1. I've found that the auto brightness sucks and I'm better off just manually setting it to 25% or so. That's fine for indoor use and you can't see the screen in bright sunlight anyway regardless of the setting so why bother burning battery trying?
2. Try flashing a kernel that allows you to underclock and undervolt. Perhaps one of Ziggy's nonHAVs kernels (I have found that HAVS kernels to be unstable, but YMMV). Either use the smartass governor or setCPU to cap screen off at 384 MHz.
3. Carry a charger with you

I'd see what is using your battery in settings.
Also, you could try chad's sense (12/28 I think) incredikernel, which sets the max clock speed really low when the screen's off (defaults to smartass governer).
If you wanted to try CM7, gingerbread has a much better battery usage UI that'll give you a nice graph of battery usage vs. time for phone awake time, signal strength, wifi and some other stats.

Battery nosedive upon wake? CM7 SZen kernel.

Hi, I was wondering if it's typical for the Evo's battery to take a rather large dip upon unlocking it after not using it for awhile but keeping it on. Around 15% under within the few minutes that I used it after waking it up from maybe about 4 hours or so of not using it and just keeping it locked without any phone calls or other disruptions.
Why does it seem to want to ramp up something like crazy when turning the phone on after not using it for awhile? Or does it actually need to do that to function? Thinking about trying out the conservative governor and jacking up the minimum MHz so the performance isn't horrid.
Using CM7.0.3.1 with SZen, have tried the SZ, smartass, and InteractiveX (current) governors.
Radios and what not are all up to date.

Trying other governors doesn't seem to help this issue at all (if it is an issue).

tried a reflash? I think i had some battery issues the first time i installed CM7. I currently use SZ 2.1 i think with SBC and BFS. My governer profile is set on savagezen and I get pretty good battery life. My phone never has huge battery drops unless I'm using the ever living crap out of it.

Nah, I had a 100% clean flash two times over, I reflashed last time for a different problem which was fixed because i was messing around with settings, not from the system/kernel. I mean I could reflash it again but I've had tons of clean flashes and always have noticed the issue, now that mostly everything else is fixed for me I'm getting around to this issue to see if it even is one.

Same problem drops 5% with in 2 minutes, I've calibrated tried cm7, miui, and stock they all do it...even bought a new battery...
Sent from my PC36100 using Tapatalk

Mine doesn't necessarily drop a certain % in a certain way/timeframe, just a large dip after not using it for awhile. As if it's taking an enormous amount of resources to try and wake itself back up and stay awake after being asleep for so long.

larry2513 said:
Same problem drops 5% with in 2 minutes, I've calibrated tried cm7, miui, and stock they all do it...even bought a new battery...
Click to expand...
Click to collapse
I switched to a SBC kernel and fixed this issue. used to drop from 100 to roughly 85 % in as little as 10 min off the charger

did you re-calibrate you battery stats???

This is w an extended battery and an amount of usage today...its all about finding the right combo.

I reset battery stats every new kernel/ROM I change. Is it useful for any reason to reset after switching governors? I'm going to try Tiamat next probably.

BigRed Productions said:
I switched to a SBC kernel and fixed this issue. used to drop from 100 to roughly 85 % in as little as 10 min off the charger
Click to expand...
Click to collapse
I use SZ as well, doesn't help it.
Or rather, there's no immediate drop like i said for me. Just quickly depletes after a long wait.

stkiswr said:
This is w an extended battery and an amount of usage today...its all about finding the right combo.
Click to expand...
Click to collapse
What do you use out of curiosity? I'd love for mine to have a steady drop like that instead of a massive dip, 8hrs on a very decent amount of use too. Even with the extended battery that seems like so much. Unless the extended is literally double the life?

[Q] horrible battery life with any ROM

Hey all,
I'm having serious battery drain on MIK 2.56 and pretty much any ROM that I flash. I'm running Chopsuey9.2.7 along with SetCPU profiles. I underclock the majority of the times.
My SetCPU profiles are:
Set on Boot = 691max/245min conservative
Charging = 1152/245 performance priority 100
Screen off = 245/245 ondemand priority 99
In-call = 1152/245 performance priority 98
Battery <50% = 691/245 conservative priority 97
Temp >43.7 degrees = 614/245 conservative priority 96
My evo doesn't like to be clocked at 128 or even 499. It reaches temps as high as 115-120 degrees during charging and while in my pocket (I'm thinking it may have got damaged when I used to run the SBC kernels in the early stages). Im starting to think that i have a bad battery. My battery will drain from 100% down to 80% within 5 minutes and usually will be dead within 2 1/2 hours after being off of the charger with moderate usage such as calls
text and checking email. I have Autokiller running and have set memory Lowmem settings to extreme thru Darktremor a2sd.
Any ideas/suggestions?

I personally would stop messing with setcpu, its cool to see a phone all Super fast and what not, but isn't completely necessary to govern everything you do [calling, sleeping, etc..] I only find it cool to use when I'm playing a cool ass game like contract killer: zombies for nice smooth graphic, or running a benchmark.. otherwise messsing with setcpu tends to do awkward things like drain battery when not properly adjusted, **Especially when overclocked.

My stock battery lasts all day with my current setup. I have setcpu as well but don't really mess with it. I use Smartass governor with 1075/245 for normal everyday use. If I have too many drinks and have to crash at a friends house without my charger I'll drop the max speed to about 700 and use conservative or just switch the governor to powersave. Then I've got more than enough time till I need to get back to a charger.

i got good life on that ROM using Aggressive Freedom kernel & using set cpu at 245/768 set at boot....no profiles.

So you think the use of profiles is the issue? I'm not completely sure the profile for screen off is working correctly; I ssh'd into my EVO and took a look at /proc/cpuinfo but it will not show the current cpu speed.
I'll give it a shot without profiles and see. As for the govenors, I believe Smartass was removed and replaced with InteractiveX; is InteractiveX as good?

j7jman said:
I personally would stop messing with setcpu, its cool to see a phone all Super fast and what not, but isn't completely necessary to govern everything you do [calling, sleeping, etc..] I only find it cool to use when I'm playing a cool ass game like contract killer: zombies for nice smooth graphic, or running a benchmark.. otherwise messsing with setcpu tends to do awkward things like drain battery when not properly adjusted, **Especially when overclocked.
Click to expand...
Click to collapse
I agree but with the way my profiles are set, I'm underclocking the majority of the time and only overclock when charging or on a phone call.

ive noticed i get wose battery life if i set up profiles. Worth a shot.

Sprint will test the battery for charge free I actually did it today
Sent from my PC36100 using XDA App

Could be your baseband or pri. Or maybe update ur prl through a sense rom.
If your phone has a horrible signal it will drain like crazy.
Sent from my PC36100 using Tapatalk

r.storm85 said:
Could be your baseband or pri. Or maybe update ur prl through a sense rom.
If your phone has a horrible signal it will drain like crazy.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
That's correct. Also check your spare parts app for any wake lock.
Also, if you're using a havs kernel, setcpu will conflict with the kernel. And in general, you'll always get better battery life on AOSP.

try using setcpu sometimes that will help save battery.

Disabled Profiles in SetCPU....no luck
So I disabled profiles in setCPU and am underclocking at 691/245 and battery life is still the same. I have the most recent radios/PRI/PRL as well and still getting rapid battery drain. One weird thing it does is the phone will hit 0% and shutdown; I'll place it on the charger (AC wall charger, not the usb adapter) until the orange LED stops blinking; I'll turn the phone on and once it's fully booted it will read 53%......all of this within 5mins of going dead! WTF!!!
I just wiped battery stats again in recovery and will boot and see what that does for me. I'm really starting to think the battery is partially bad....

Just left Sprint. They tested the battery and it tested bad and was swollen. I got a stock replacement free of charge although he said they normally would have charged me because the 1yr factory warranty expired. He also went on to say that the battery going bad was possibly caused from my phone being rooted which he may be partially correct. The problem began when SBC first came out and I was testing on the beta stage. It nice to have my phone off of the charger and not be down to 60% within 45 mins!
Sent from my PC36100 using XDA App

lostsoul77 said:
So I disabled profiles in setCPU and am underclocking at 691/245 and battery life is still the same. I have the most recent radios/PRI/PRL as well and still getting rapid battery drain. One weird thing it does is the phone will hit 0% and shutdown; I'll place it on the charger (AC wall charger, not the usb adapter) until the orange LED stops blinking; I'll turn the phone on and once it's fully booted it will read 53%......all of this within 5mins of going dead! WTF!!!
I just wiped battery stats again in recovery and will boot and see what that does for me. I'm really starting to think the battery is partially bad....
Click to expand...
Click to collapse
my phone has been doing this exact same thing but i took it to sprint they said my battery was good should i go to another sprint tech and let them test it out?