battery drain and Snap with CM6? - EVO 4G Q&A, Help & Troubleshooting

CM6 is definitely great, I think without question it is a vast improvement.
The only issue I have is my battery life is ABSOLUTELY HORRIBLE. Could be the worst battery life I've had with any phone. But maybe that's just the EVO, with it's big screen and speedy processor. I underclock to 384 mhz sometimes but then the thing slows down and even freezes. I have 3 different batteries and they all perform about the same (not good.) Before I had a partial wake issue but that's gone, and battery life still stinks. I've also tried calibrating but nothing really seems to make it better.
I hear the snap thing is good for battery life but I everytime I open that thread I get a headache. I love this phone and am obsessed wtih it but that thread is a bit much even for me!
Can anyone give me a quick and dirty explaination of what snap is / how to use snap? Which kernel to flash? Some day I hope to digest that mammoth of a thread, but right now I'm too busy reading texts for college and Just want better battery life.
Thanks!

Download app System Panel. Will help show you what is eating up your battery/resources.
Then, download app Juice Defender. Worth it to get the paid version. Its like 3 bucks IIRC. This will help you get more battery life out of your phone.
-Sent from my Evo.

nyc_zx10 said:
Download app System Panel. Will help show you what is eating up your battery/resources.
Then, download app Juice Defender. Worth it to get the paid version. Its like 3 bucks IIRC. This will help you get more battery life out of your phone.
-Sent from my Evo.
Click to expand...
Click to collapse
Yeah, I tried System Panel but the things eating my battery were mostly system things, like Browser. I guess I could give it another go.
Why are Juice Defender reviews so bad? I've considered it before also, maybe will try playing with it again

snap 8.2 is the current release. you can try any of the kernels, but i would avoid the 7.0/7.1 SD Card implementations since that technology has been put on the back burner for a bit.
Snap allows you to you Overclock and Undervolt (aka: UV).
Overclocking of course is for speed and Undervolting may save battery.
all EVOs are not created equal. some like undervolting some do not. so snap is available in multiple flavors. each with a different UV floor. the lower the floor the more potential battery saving..but also the more chance for a random reboot or wifi/gps acting funny. remember UV retards the amount of power so things can act goofy. the different UV floors are 800mv - 925mv. for example...i use the 8.2_900 because it works well with my EVO. the 8.2_800 booted great but after a while started rebooting itself. 8.2_850 just hung at bootup. the 8.1 kernels didn't work for me at all. 7.3b1 was great.
HAVs is adaptive..so don't get stressed if your device fails to boot properly the first time. wipe the cache/dalvik and try again.
so download a few of the 8.2 kernels.
make your nandroid
begin trial and error (I'd suggest starting at 800, 850 then 900 to get a feel)
don't be afraid to wipe the Cache and Dalvik multiple times.
don't worry about the whole thread. just grab the last few pages and read the OP. then feel free to ask.
i also recommend setCPU. you can find some threads for SetCPU configurations to help. BUT....make sure SetCPU is disabled when flashing the new kernel. once you get a working kernel you can enable SetCPU...but during testing phase it will give you gray hair.
jmxp69 said:
Just a few quick thoughts on voltages/freqs after seeing a handful of discussion in the thread:
1) Every 8.2 kernel has voltages lower than stock. The default stock voltage @ 245 is something around 1050.
2) No real effort is made to UV at the top end. It's a little lower, but the objective at the highest CPU frequency is not to UV. Most of the benefit of UV comes at the low end of the scale when your phone is idle (most of the time). Less voltage = less draw.
3) nHAVS scales voltage at each step. There is a min.max voltage at every cpu frequency. This range is fairly small--50-75mv, but it enables HAVS to decide based on feedback from the CPU which one to apply. And the max at each step is lower than stock. So no matter how you slice it, even if you're running 925, you are undervolted. This becomes a question of how undervolted.
4) OC is not about undervolting, it's about overclocking. The differences is voltage vs. frequency. OC means we're increasing the CPU frequency beyond stock which is 998mhz in the case of Evo. If you move your SetCPU slider beyond 998mhz, you're overclocking.
The objective of overclocking is speed. The objective of undervolting is battery savings. Snap gives you both. We overclock when we increase the fequency with SetCPU. We undervolt automatically via nHAVS. As of this writing, UV is handled in the kernel, it happens most at the bottom end of the frequency scale.
I hope this helps clear up some of the questions. Great conversation by the way.
Click to expand...
Click to collapse

GREAT EXPLANATION Dragin!!!
and also, to the OP.... dont forget, if you do go with setcpu, do NOT 'set on boot' mmmmkay??? lol

Thank you Dragin!!!
That helps a lot! So once you have Snap setup at what you feel is "good" does your phone seem to perform as well as before you had it undervolted? Man, sounds like a pretty involved process - maybe I better wait until I can really sit down and play with it.

goodelyfe said:
GREAT EXPLANATION Dragin!!!
and also, to the OP.... dont forget, if you do go with setcpu, do NOT 'set on boot' mmmmkay??? lol
Click to expand...
Click to collapse
Do you mean for the first flash? Or every time you boot your phone?
If not set on boot, it means you have to start SetCPU manually after each boot. Doesn't seem right
Sent from my PC36100 using XDA App

foueddyf said:
Do you mean for the first flash? Or every time you boot your phone?
If not set on boot, it means you have to start SetCPU manually after each boot. Doesn't seem right
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
I think he's talking about when ur figuring out the best setup

Regarding Juice:
I didn't really read too much into the reviews for this particular app. It works. I was having battery issues. Downloaded Juice, got the settings somewhat right to my liking and so far no complaints. Unplugged my phone from charger this morning at roughly 9am, been using it moderately all day, and as of right now at 12:50am, I am at 29%.
Bad reviews or not, I can attest to it working and making a difference in battery life.
Sent from my PC36100 using XDA App

I had the same issue, left to stock with kingx.
Sent from my PC36100 using XDA App

nyc_zx10 said:
Regarding Juice:
I didn't really read too much into the reviews for this particular app. It works. I was having battery issues. Downloaded Juice, got the settings somewhat right to my liking and so far no complaints. Unplugged my phone from charger this morning at roughly 9am, been using it moderately all day, and as of right now at 12:50am, I am at 29%.
Bad reviews or not, I can attest to it working and making a difference in battery life.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Do you know what in particular Juice is doing to give you better battery life? like what does Turn off certain things based on conditions or?
That is some good battery life.

Correct.
You can set conditions to do certain things. Such as disable data/3g/wifi while screen is off. Also if you need data synced you can set a condition to enable data wifi or 3g for X minutes every X minutes/hours.
I am not affiliated with the dev in anyway but it def made a difference and was worth the price for it.
Sent from my PC36100 using XDA App

nyc_zx10 said:
Correct.
You can set conditions to do certain things. Such as disable data/3g/wifi while screen is off. Also if you need data synced you can set a condition to enable data wifi or 3g for X minutes every X minutes/hours.
I am not affiliated with the dev in anyway but it def made a difference and was worth the price for it.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Meh... see I really don't want to do those things. I can turn off data sync myself and just have gmail forward me a text message when I have an email. I just was hoping there was a way to get decent battery life without going back to the days of Winmo
I absolutely adore CM6, but I'm really starting to think that it is not battery friendly. Last night my battery went from full to 25% in 8 hours. I had nothing running, my partial wake was fine, and Android system took up 60%+. I really don't feel like doing another wipe, but it looks like I may have to. Just want it to work right at this point.
Again, I truly love CM6, the open source concept, the transparency, the whole clean idea of it, but there is something seriously wrong with the battery life (at least in every install I have tried)

berardi said:
I absolutely adore CM6, but I'm really starting to think that it is not battery friendly. Last night my battery went from full to 25% in 8 hours. I had nothing running, my partial wake was fine, and Android system took up 60%+. I really don't feel like doing another wipe, but it looks like I may have to. Just want it to work right at this point.
Again, I truly love CM6, the open source concept, the transparency, the whole clean idea of it, but there is something seriously wrong with the battery life (at least in every install I have tried)
Click to expand...
Click to collapse
i agree with you. but i also feel that CM6 is on par with the Official HTC/Sprint ROM when it comes to battery life expectancy. however, after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
as for finding your EVOs kernel made in heaven...
it's not too bad so long as you have some time. but if you are time strapped, need your phone in 20min and don't read the OP... you will curse and swear. expect to get hung up at the HTC splashscreen a few times and it will bootloop on you before your done. <I'd suggest just leaving your battery cover off until you are done muckn about for that session>
klick may be easier for the some end users because of fewer selections. I've never used his kernels. if i try them, i'll prolly wait till he's put out a few AOSP versions...to work out any bugs.
oh yeah...one odd thing, it seems that sometimes folks flash a incompatible kernel it gets 'stuck'. after that 'bad flash' they are unable to flash any kernel until after they have nandroided back and rebooted...then they can flash again. i had this happen twice....i was unable to get a known good kernel to load until after i restored from backup. /shrug
oh....try this. download the snap7.5_925 kernel. if it runs smooth. call it a day and you should be pretty happy with that until the new versions come out. yeah, if you got one of the _800 kernels running you may pull an extra 30-45min of time...but that requires a level of geekdom that not everyone has.

DraginMagik said:
i agree with you. but i also feel that CM6 is on par with the Official HTC/Sprint ROM when it comes to battery life expectancy. however, after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
as for finding your EVOs kernel made in heaven...
it's not too bad so long as you have some time. but if you are time strapped, need your phone in 20min and don't read the OP... you will curse and swear. expect to get hung up at the HTC splashscreen a few times and it will bootloop on you before your done. <I'd suggest just leaving your battery cover off until you are done muckn about for that session>
klick may be easier for the some end users because of fewer selections. I've never used his kernels. if i try them, i'll prolly wait till he's put out a few AOSP versions...to work out any bugs.
oh yeah...one odd thing, it seems that sometimes folks flash a incompatible kernel it gets 'stuck'. after that 'bad flash' they are unable to flash any kernel until after they have nandroided back and rebooted...then they can flash again. i had this happen twice....i was unable to get a known good kernel to load until after i restored from backup. /shrug
oh....try this. download the snap7.5_925 kernel. if it runs smooth. call it a day and you should be pretty happy with that until the new versions come out. yeah, if you got one of the _800 kernels running you may pull an extra 30-45min of time...but that requires a level of geekdom that not everyone has.
Click to expand...
Click to collapse
Thanks man, appreciate the breakdown.
You have inspired me, I'm going to bite the bullet and try this snap7.5_925 kernel. I'll report back my luck
I do enjoy this stuff, really - just right now it would be irresponsible for me to spend too much time on it. School comes first right now.

DraginMagik said:
... after i put on the snap kernel and copied someones setcpu config....i got 26+hrs of 'use it as i wish' time + still had about an hour of in-pocket time left. i was hooked. i bet you an imaginary dollar the same will happen for you.
Click to expand...
Click to collapse
Wow, I'd love to have that kind of time with CM6, right now I drain at about 10% an hour with no usage at all; where can I find that setcpu config? I really like CM6 but battery life is killing me right now.

loupy said:
Wow, I'd love to have that kind of time with CM6, right now I drain at about 10% an hour with no usage at all; where can I find that setcpu config? I really like CM6 but battery life is killing me right now.
Click to expand...
Click to collapse
Yeah dragin, don't hog those sweet settings! I'm enjoying Snap 7.6 and it seems to be helping out my battery life a bit, but I'd love to see your SetCPU details.

I've found that the issue for me is bluetooth. If I have it on constantly my battery will drain 10-15% per hour. With bluetooth off it's only draining 1%-2% per hour.
Seems like the bluetooth needs work on CM6 in order to have the efficiency that the other ROMs i've tried (Fresh and EViO) have. Nonetheless, I'm sticking with CM6 and just use the bluetooth when necessary.

I have the same issue with bluetooth on CM 6.0.0. I am running the stock kernel that comes with cyanogenmod, so this is definitely not a snap issue. There was a bug submitted about a month ago:
code.google.com/p/cyanogenmod/issues/detail?id=2136
I *really* hope this can get fixed for the 6.1 release, but it is currently listed with a low priority. I really love CM6, but basically making bluetooth unusable for more than a few hours really makes me struggle with the using this rom.

Why not the 7.6 with turbo...just wonderin

Related

[Q] HTC EVO -- Best Battery life ROM???

Can anyone tell me which ROM (STABLE) provides the best battery life on HTC EVO???
Thanks!
I have been through just about all on this site and Fresh's newest seems to work best for me. With moderate daily usage I can go without charging for about 22-24 hours. Of course all I need to go is 12-14 b/c I charge every night anyway, but I did leave off charger one day just to see how far I could go. I'm giving Calk's latest a try right now to see how it goes. Just be sure to give whatever ROM you try a couple charges before making a final decision, as it usually takes this amount to get an accurate read on true battery life.
how many of these post are we going to need lol
buddho81 said:
Can anyone tell me which ROM (STABLE) provides the best battery life on HTC EVO???
Thanks!
Click to expand...
Click to collapse
I know that the latest kernels off the latest build have been killing my battery, it's horrible for my EVO.
But you really have to try different rom/kernel/PRI/radio combinations to find the best battery life for your Evo. I wish there was a preset rating system for each rom though, just to see how things work for everyone else(i.e. battery life, quadrant scores, force close problems, etc.)...but there really are a lot of variables, so I don't think that may ever happen.
Yeah I agree there isn't a clear cut winner. Everyone uses their phone different so it will differ for everyone.
Totally agree to give it a few full charges... I suggest when you get a new rom and/or kernel installed to reset the battery stats (can be done in recovery) then use it till it dies then charge to full before turning it back on.
Personally, I've been using Fresh 3.3 w/ the Kings #6 kernel and not only has the phone been screamin' fast the battery has been good. I'm only on my 2nd charge up though so I still have one or two to go before everything smooths out.
buddho81 said:
Can anyone tell me which ROM (STABLE) provides the best battery life on HTC EVO???
Thanks!
Click to expand...
Click to collapse
2.2 Evo Kernels Tested and charted
admorris said:
I have been through just about all on this site and Fresh's newest seems to work best for me. With moderate daily usage I can go without charging for about 22-24 hours. Of course all I need to go is 12-14 b/c I charge every night anyway, but I did leave off charger one day just to see how far I could go. I'm giving Calk's latest a try right now to see how it goes. Just be sure to give whatever ROM you try a couple charges before making a final decision, as it usually takes this amount to get an accurate read on true battery life.
Click to expand...
Click to collapse
What kernel are you using for the battery life?
Sent from my PC36100 using XDA App
catseyenu said:
2.2 Evo Kernels Tested and charted
Click to expand...
Click to collapse
As posted here, the tests showed that CM w/ Snap 7.5 probably has the best battery life - and it seems by a lot.
download juice defender
[ROM]CM-B2_Supersonic-XV a.k.a [email protected]$T(SuperMOD) UPDATE#5 w snap 7.5
I'm using the latest Fresh and I just plugged my phone in at 15% battery after 37 hours. I'm pretty happy with that.
Fresh Rom always gave me good battery.. I'm just using the rooted stock OTA and am getting great battery life.
Sent from my HTC Evo 4G using XDA app.
Sporkman said:
how many of these post are we going to need lol
Click to expand...
Click to collapse
Until someone takes the time to make a section that covers the different problems. Battery problems, Battery Problems w/ ROMS, Apps not loading, etc. etc.
Wishful thinking. I do like the search in the search to help cut down this crap
Wallabe said:
Until someone takes the time to make a section that covers the different problems. Battery problems, Battery Problems w/ ROMS, Apps not loading, etc. etc.
Wishful thinking. I do like the search in the search to help cut down this crap
Click to expand...
Click to collapse
I think it would be a great idea for this kind of stuff to happen. Some aggregated source where everyone can submit their information using various roms, kernels, etc. Whether it be information regarding Quadrant scores, linpacks or battery life. On computer hardware forums they generally have a section dedicated to OCing records with charts listing someones entire setup while attaining the clock speeds. I don't see why a similar implementation can not be done here.
Wallabe said:
Until someone takes the time to make a section that covers the different problems. Battery problems, Battery Problems w/ ROMS, Apps not loading, etc. etc.
Wishful thinking. I do like the search in the search to help cut down this crap
Click to expand...
Click to collapse
How about if we make a section purely for questions and answers? That could work.
Two words......juice defender
Sent from my PC36100 using XDA App
i use Fresh's Rom made my battery life live avg abt 15 hours
Over 40 kernels were tested and benchmarked in 7 different ways, and the results are posted here.
Should tell you everything you want to know, without bringing roms into the picture (since battery life is most affected by the kernel used, not the rom)
edit - looks like I'm a bit late withthat link - I see the thread for that site was already posted above. It's a great resource.
Fresh 3.2, hands down best battery life for me. 3.3 was pretty bad, as was myn's release....which sucks, because myn's rom is otherwise awesome.
I am using Fresh 3.3.0.1 with a baked kernel that is able to over clock. I then have SetCPU installed with profiles for different states of the phone. If my screen is off I have the cpu set to a max of 500MHz to save battery if there are any processes running in the background. I then have my cpu set to 1119MHz when the phone is plugged in or at 100% with the screen on just because I like a snappy phone. Then when the battery drops below 50% I have it return to stock speeds.
I use my phone heavily for things like subsonic, QIK, FB, Calendar, wireless tether, and of course since unlimited data, calling to any cell, and texting I am on it a lot keeping in touch with friends. I also use the sprint nav at least twice a week.
Results will vary from user to user but so far the phone has been on 7 hours and after some moderate use it's only down to around 75% on the battery.
Again this is how I MYSELF use my phone with this rom and kernel this may not be how you use your phone and you may see different results.
What I have done is searched roms and installed them in total I have used 4 different roms. Baked, Cyanogen, Fresh, and Virus. After installing each rom and setting up my phone I made a nand backup of each so I can flash between them as needed to test. I have found out of all of these roms Fresh 3.3.0.1 with a kernel from the baked roms has worked the best for MY daily use.

Best ROM for battery life

I need opinions, anyone?
I keep flashing different ROMS and the battery has always had bad life
I've done a lot of different methods to fix battery life issues, but no go.
Having good luck with Swagged Out Stock.
Sent from my PC36100 using XDA App
A lot of people say AOSP ROMs are good on battery life cuz the sense is gone.
Try out Xplod RLS (one of my favs) test it out see how it goes for you. It's an AOSP btw.
For sense I recommend Tommytomatoes Classic v0.0.0.4 its awesome!
How long does your battery last? Are you running mobile data all day? GPS?
I can get around 20-24 hours put of my battery with real heavy usage. Around 2 days with normal use.
I keep my 3g and everything off until i need it.
HTC EVO 4G running Mikg 2.58
Don't know who your talkin too but I'll reply lol
On Classic I'm gettin roughly about 1d 19h 43m with pretty decent usage text, call, xda, browsing jus putting it to charge right now
I have always had the best success with AOSP and custom kernel.
Currently running ICSmod7 with latest tiamets. With 4g it drops fast but without I get through a full day no worries medium use. Text, fb, music during workout ect...
Sent from my PC36100 using xda premium
Getting good battery life with MikG 2.61.
mikg rom to me is best for battery life .and very stable rom and clean so try and let us know .im running miui and battery life is pretty good but not as good as my mikg rom
sense-free
I've been experimenting with ROMs and kernels for the last 18 months, always looking for best battery life with regular to heavy use. A good custom kernel will sometimes give you an extra 10-15 %. Using setCPU or another app like systemtuner (my pref) to turn CPU down while screen off can also give you 5-10%. Far and away the best thing for my battery is to use an alternative launcher (ADW for me) and then use Titanium backup pro or systemtuner to freeze sense. you just find the two elements in the process list that start with "HTC sense" and freeze them. Night and day. FYI I run synergy and have always come back to Myn's ROMs cause they are good for battery from the start, but they also take well to pretty much any custom kernel, which isn't true for all ROMs. I like everything to work so I always ditch AOSP ROMs a few days after trying them.
sam9696 said:
I've been experimenting with ROMs and kernels for the last 18 months, always looking for best battery life with regular to heavy use. A good custom kernel will sometimes give you an extra 10-15 %. Using setCPU or another app like systemtuner (my pref) to turn CPU down while screen off can also give you 5-10%. Far and away the best thing for my battery is to use an alternative launcher (ADW for me) and then use Titanium backup pro or systemtuner to freeze sense. you just find the two elements in the process list that start with "HTC sense" and freeze them. Night and day. FYI I run synergy and have always come back to Myn's ROMs cause they are good for battery from the start, but they also take well to pretty much any custom kernel, which isn't true for all ROMs. I like everything to work so I always ditch AOSP ROMs a few days after trying them.
Click to expand...
Click to collapse
Underclocking your CPU typically causes higher battery drain... unless you're overclocking. As long as nothing is really hammering the CPU in the background (which is the problem, not the CPU speed!), then it's better to let the CPU enter higher power states in order to finish the work quicker and return to low power sleep state. Intel calls this HUGI (Hurry Up and Get Idle). Overclocking can have bad effects with HUGI due to the higher voltage required to run at those frequencies. Lol'd at your AOSP comment though. I suppose some people are okay with subpar android, aka sense .
My Evo can last a week on a single charge. CM7.1, 1850 mAh aftermarket battery (slim, stock battery cover), Tiamat 4.1.0 kernel, aggressive undervolting and monitoring of wakelocks combined with 90% wifi usage (3g is the #1 source of battery drain!).
Sent from my Transformer TF101
Tommytomatoes The Classic is a solid sense rom with good battery life its fast as hell, has lots of mods and themes and is pretty sick I've been stuck on it for over a month now I've flashed other roms but always come back to the classic after a few hours
Sent from my Classic-EViLizED-ToMAToFiED-EVo4g-
maybe a dumb question. What is the difference between underclocking and undervolting?
Gary13579 said:
Underclocking your CPU typically causes higher battery drain... unless you're overclocking. As long as nothing is really hammering the CPU in the background (which is the problem, not the CPU speed!), then it's better to let the CPU enter higher power states in order to finish the work quicker and return to low power sleep state. Intel calls this HUGI (Hurry Up and Get Idle). Overclocking can have bad effects with HUGI due to the higher voltage required to run at those frequencies. Lol'd at your AOSP comment though. I suppose some people are okay with subpar android, aka sense .
My Evo can last a week on a single charge. CM7.1, 1850 mAh aftermarket battery (slim, stock battery cover), Tiamat 4.1.0 kernel, aggressive undervolting and monitoring of wakelocks combined with 90% wifi usage (3g is the #1 source of battery drain!).
Sent from my Transformer TF101
Click to expand...
Click to collapse
Underclocking is when you set the speed of the processor to a lower setting than the stock clocks where as undervolting is lowering the voltage needed to run it at a certain speed be it stock underclocked or overclocked. Simplest way I understand it.
Sent from my PC36100 using Tapatalk
Real culprit for batt issues
Has anyone ever bothered to understand that theres a pesty bug no one knew of.. Called CIQ "carrier IQ"
Ya this is one of the main reasons behind bad batt.. Sprint and other carriers allow a company to monitor and chart everything we do and it mirrors off txts and data sent and is designed to pick up on.key words... Basically an Invasive tracking monitor. It's a huge in noticed drain... And its been shown to be removed from system/app in many custom roms. But it never does cause its so strattled throughout the OS.
Sent from my PC36100 using XDA Premium App
IMPuLSe EX said:
I need opinions, anyone?
I keep flashing different ROMS and the battery has always had bad life
I've done a lot of different methods to fix battery life issues, but no go.
Click to expand...
Click to collapse
I have been using evodeck v1.3 with the lee kernel and the rom just sips on my battery and gives me outstanding battery life with amazing speeds
lojak29 said:
Has anyone ever bothered to understand that theres a pesty bug no one knew of.. Called CIQ "carrier IQ"
Ya this is one of the main reasons behind bad batt.. Sprint and other carriers allow a company to monitor and chart everything we do and it mirrors off txts and data sent and is designed to pick up on.key words... Basically an Invasive tracking monitor. It's a huge in noticed drain... And its been shown to be removed from system/app in many custom roms. But it never does cause its so strattled throughout the OS.
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
"no one knew of" are you kidding me? Carrier IQ has been known about for at least a year now... and no, it's not responsible for any significant amount of battery drain...
Sent from my Transformer TF101
Definantly aosp in my experience. Cm7 gets my vote for battery life
Gary13579 said:
Underclocking your CPU typically causes higher battery drain... unless you're overclocking. As long as nothing is really hammering the CPU in the background (which is the problem, not the CPU speed!), then it's better to let the CPU enter higher power states in order to finish the work quicker and return to low power sleep state. Intel calls this HUGI (Hurry Up and Get Idle). Overclocking can have bad effects with HUGI due to the higher voltage required to run at those frequencies. Lol'd at your AOSP comment though. I suppose some people are okay with subpar android, aka sense .
My Evo can last a week on a single charge. CM7.1, 1850 mAh aftermarket battery (slim, stock battery cover), Tiamat 4.1.0 kernel, aggressive undervolting and monitoring of wakelocks combined with 90% wifi usage (3g is the #1 source of battery drain!).
Sent from my Transformer TF101
Click to expand...
Click to collapse
So you clearly don't talk on the phone at all.
Sent from my PC36100 using XDA App
alaman68 said:
So you clearly don't talk on the phone at all.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Ah yes, the people that come in arguing and debating my claims. This happens every time. I use my phone quite often, and still get amazing battery life.
Sent from my Transformer TF101
Gary13579 said:
Ah yes, the people that come in arguing and debating my claims. This happens every time. I use my phone quite often, and still get amazing battery life.
Sent from my Transformer TF101
Click to expand...
Click to collapse
Dude you have a serious problem I honestly think you need to quit thinking people are attacking you this is the 3rd time I've seen you in a thread that I'm in and not once have I seen you post anything good or helpful I honestly think you should refrain from posting that's my opinion only cause I think your on a kid level and you really can't carry an easy conversation with someone sometimes I wonder if you even have this phone and if your trolling EVO Forum instead of the Transformer Forum.
TrevE Supporter!
If you like being on this site everyday!
I suggest you click this link a fill it out!
http://americancensorship.org/
Then HIT THE THANKS!

Did I FRY my CPU??

First of all im not putting down anyone and there custom roms. As I am an avid flasher of them and there great features..
However.. Ive noticed with every rom I flash, my battery life SUCKS. I know kernels are suppose to have battery saver mods, but never seem to work for my phone. The only way I seem to get great battery life is if I odin back to stock. Its seems to last forever on stock.
On stock.. I would average around 10% drain every two hours of moderate use.. mainly texting..
On Custom roms I average 10 to 15 % drain every hour with same moderate use..
My question is, Could Overclocking have caused this problem??
Orion78 said:
First of all im not putting down anyone and there custom roms. As I am an avid flasher of them and there great features..
However.. Ive noticed with every rom I flash, my battery life SUCKS. I know kernels are suppose to have battery saver mods, but never seem to work for my phone. The only way I seem to get great battery life is if I odin back to stock. Its seems to last forever on stock.
On stock.. I would average around 10% drain every two hours of moderate use.. mainly texting..
On Custom roms I average 10 to 15 % drain every hour with same moderate use..
My question is, Could Overclocking have caused this problem??
Click to expand...
Click to collapse
Quite possibly... And unfortunately, you have to test different Kernels with your ROM to see what works best, or just ask the Dev which Kernel they used when developing the ROM... That's a good way to get the best battery life because after all, that's the Kernel the Dev based the ROM off of. Another option is to check out Marcusants post on setting up your Kernel for your ROM, and I apologize if you've already tried that... I'm just trying to list options... I've had problems with different kernels on different ROMS... Well at least until Rodderik started making his Kernels with Viper ROMS... Then it started working perfect lol. How are you running your clocking? Conservative? Performance? Also, are you using SetCPU with an OC/UV kernel and the Voltage Control app? If you use the two together, it could cause a lot of issues, you'd have to choose one or the other.
On the other hand, I could be 100% wrong and it could be just your flux capacitor... You know how touchy those things are. Try chucking your phone over 88 MPH and see how that works. The next step is VERY important though... Whatever you do, don't forget to put your phone in airplane mode before you throw it in the air or it'll just fall right back down after a couple feet... Keep it in the air I always say.
The Serpents Shall Rise Again... And This Time, They're Bringing The Powers Of The Angels, And Shall Be The Vengeful Striking Hammers Of God. Rest Your Weary Eyes, For A Great Time Of Prosperity Will Surely Ensue.
Viper Squad now recruiting!
Im hoping once I hit 88MPH it will go back in time to when my phone actually worked. haha
I usually just use the Kernel that comes with the rom..
However I have used Set CPU and Voltage control together once. I messed around with the setting between performance and conservative.
Orion, first off. If u remember how "beepers" worked back in the day, if u ever had one, that's how text messaging works. It triggers a small ping when being sent or receiving message. So text messages really hardly use power. As far as ur battery is concerned, try this method if u like, just to see what kind of results u get. Charge battery completely with phone on first and then off. Then boot into cwm and wipe ur battery stats. Then drain ur battery completely without charging it. Then completely charge it up, and then see how ur battery does.
Sent from my SPH-D700 using xda premium
One more thing. Anytime u change rom or kernel, update ur prl and profile, then reboot ur phone..it does make a difference doint this.
Sent from my SPH-D700 using xda premium
LORDFIRE00 said:
Orion, first off. If u remember how "beepers" worked back in the day, if u ever had one, that's how text messaging works. It triggers a small ping when being sent or receiving message. So text messages really hardly use power. As far as ur battery is concerned, try this method if u like, just to see what kind of results u get. Charge battery completely with phone on first and then off. Then boot into cwm and wipe ur battery stats. Then drain ur battery completely without charging it. Then completely charge it up, and then see how ur battery does.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
True, just don't wipe your battery stats too much, it could end up doing more harm than good. But good call, I overlooked that cuz I was being a smart ass lol... Please don't throw your phone, that's never a good idea haha.
The Serpents shall rise again... And this time, they bring the powers of all of the Angels in heaven with them, becoming the vengeful striking hammers of God. Rest your weary eyes, for a great time of prosperity shall ensue.
Team Viper now recruiting!
Were you overclocking when your battery life sucked? What uses more gas, riding at 55MPH or 90MPH? What was your battery life like on custom ROMs with stock frequencies?
Sent from my SPH-D700 using XDA App
LORDFIRE00 said:
Orion, first off. If u remember how "beepers" worked back in the day, if u ever had one, that's how text messaging works. It triggers a small ping when being sent or receiving message. So text messages really hardly use power. As far as ur battery is concerned, try this method if u like, just to see what kind of results u get. Charge battery completely with phone on first and then off. Then boot into cwm and wipe ur battery stats. Then drain ur battery completely without charging it. Then completely charge it up, and then see how ur battery does.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Yeah, I always Wipe that stats after a fresh rom install..
I dunno, im due for an upgrade in april, so hopefully the new GS3 is on its way by then
kennyglass123 said:
Were you overclocking when your battery life sucked? What uses more gas, riding at 55MPH or 90MPH? What was your battery life like on custom ROMs with stock frequencies?
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Battery was ok when I overclocked.. went down hill after that. Except whenever im on stock EI22 Gingerbread and it runs all day.
On custom roms with stock frequencies I would still see a significant drain.
I don't think you fried it if it's still running fine on stock. I'd be more likely to think you're overclocking with an aggressive governor that is making your cpu stay at higher frequencies.
I havent been doing any OC or UV in months now and still have the problems on custom roms. Perhaps I got the phone that doesnt like to be modded.. Damn Sprint ha
also screen brightness has a HUGE effect on battery life. also do you do games and such? Those can be very draining as well. I am on a viper rom going on 14hrs and still at 78%. but i mostly text with my phone. about 15,000 a month to be exact. and use f.b. and xda pretty heavily. and different kernels can make the difference between 6 hours and 20.
---------- Post added at 08:58 AM ---------- Previous post was at 08:55 AM ----------
Orion78 said:
I havent been doing any OC or UV in months now and still have the problems on custom roms. Perhaps I got the phone that doesnt like to be modded.. Damn Sprint ha
Click to expand...
Click to collapse
i will say that my phone is particular on what rom i do run no matter what kernel i use
I just mainly text and surf the web occasionally. Funny part though the only game I play rarely is Deer Hunter Challenge which is a pretty high def large file game and when i play that my battery doesnt seem to drain. Right now Ive gone down 10% over the last hour just sending about 15 texts. And I have my display set to auto brightness
It's real simple...overclocking equals faster cpu AND faster battery drain. Do not overclock or do not complain about battery...one or the other.
Sent from my SPH-D700 using XDA App
No. Your battery capacity is deminishing. Its normal.
Sent from my SPH-D700 using Tapatalk

CM10 Performance

I've been running the 9/15 nightly, and while I haven't had excellent battery life, it has typically lasted around 8 hours or more. Today was a little different; with only an hour of screen time, my battery was down to 30%. On top of that, it usually takes 3 or 4 presses of the home button to wake my phone up.
EDIT: I forgot to add that my screen usage usually accounts for 60%, or more, of my battery usage--and that's with minimal usage. It always seemed like my screen was draining the battery even when it was off. It is much less now.
I read on the forums that a simple increase of the minimum frequency can resolve the waking issue. However, it didn't; instead, my battery life improved dramatically. I'm used to a pretty jagged and sharp battery graph, but now it's as smooth and linear as I have ever seen it.
Can anyone explain why raising the min freq improved my battery life?
Sent from my SAMSUNG-SGH-I747 using xda premium
Why don't you update? Its Oct 5th. Maybe give that a try? Old build man.
Well, I've considered it, but I always check the main thread first. It always seems like people are having LTE or GPS issues with the new build. Everything, aside from the battery life and screen waking, has been working exceptionally well. Not to mention, school and work hasn't given me enough free time to experiment with the new builds. I might try this tonight though.
Sent from my SAMSUNG-SGH-I747 using xda premium
DStevens5833 said:
Well, I've considered it, but I always check the main thread first. It always seems like people are having LTE or GPS issues with the new build. Everything, aside from the battery life and screen waking, has been working exceptionally well. Not to mention, school and work hasn't given me enough free time to experiment with the new builds. I might try this tonight though.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
The rom actually updates EVERY DAY you have missed many many updates here is a changelog http://changelog.bbqdroid.org/#d2att/cm10/1349329973
well all devices are not created equal. i suppose its possible that the ideal minimum frequency for your device is a above stock (or whatever you had it at before). raising the minimum frequency can improve cell connection, screen flickering issues, ect (things that cause battery drain).
also i advise you to update your cm build. either that or switch to cm monthly or another rom that doesn't push out critical updates every night. Try a rom that is considered stable like liquidsmooth, slimbean..
On the Oct 3 build and it's very fast. Batter life has been quite bad, have to charge it twice a day. Had a lot of crashing yesterday, phone decided to reboot continuously. Apollo has stopped error persisted until I cleared cache, and keep getting email/exchange devices have stopped errors until I disabled email.
Battery is the only thing that really bugs me though
Not sent from my toilet with a soap bar.
@nccu_eagles & @jefferson9: To be honest, I never realized the minimum frequency affected so many different elements outside of power saving. I admit I haven't kept it up-to-date; I'm always afraid to update after seeing some of the bugs people post. Perhaps I would be better off with a more stable release--at least until the semester is over, which will leave me with much more time to dabble. If I finish my homework in time, I might try a few different roms tonight.
@adammur: Those are the type of bugs that keep me from updating.
On another note, today's battery life has been great. My battery would normally drain between 12-20% an hour. Today, I'm averaging 5% an hour with similar usage. :good: Anyways, thank you guys for the replies. I'll see if I can't find something to better suit me.... for now :fingers-crossed:.
Before playing with the TouchWiz Jellybean Milestone 5 (Firefly) ROM by Drew Garen, I was running the JellyBro's euroskank October 3rd nightly along with LeanKernel as well as JuiceDefender Ultimate...
My Galaxy S3 could literally last 2 days with that setup. It was UNREAL.
The problem is, I really actually do like the TouchWiz interface (I know I know, I'm one of the few).
But if ultimate battery life is your goal with the Samsung Galaxy S3... Do a factory reset / cache wipe and install the Oct 3rd version of JellyBro's euroskank for the d2att... Then go ahead and install yourself the tmobile / AT&T version of leankernel...
You WILL NOT be sorry!
DStevens5833 said:
I've been running the 9/15 nightly, and while I haven't had excellent battery life, it has typically lasted around 8 hours or more. Today was a little different; with only an hour of screen time, my battery was down to 30%. On top of that, it usually takes 3 or 4 presses of the home button to wake my phone up.
EDIT: I forgot to add that my screen usage usually accounts for 60%, or more, of my battery usage--and that's with minimal usage. It always seemed like my screen was draining the battery even when it was off. It is much less now.
I read on the forums that a simple increase of the minimum frequency can resolve the waking issue. However, it didn't; instead, my battery life improved dramatically. I'm used to a pretty jagged and sharp battery graph, but now it's as smooth and linear as I have ever seen it.
Can anyone explain why raising the min freq improved my battery life?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
What did you increase it to, if you don't mind me asking?
I normally use up-to-the-moment builds (downloading 10/07 ad I write) and my battery life has been reasonable - up to two days total with light use. Seems to me to be a matter of making sure you're not running too many (any?) battery-hogging apps (BetterBatteryStats has been enormously helpful in this respect).
Unfortunately, I was unable to play with anything last night due to homework. I did, however, purchase and install BBS and JD. I'm actually at work right now, so I can't really post much other than a few screenshots.
Sent from my SAMSUNG-SGH-I747 using xda premium
Cuddlesy said:
What did you increase it to, if you don't mind me asking?
Click to expand...
Click to collapse
I increased it from 384 to 486. So far it seems to have helped a lot. I'm actually about to try a couple different ROMs and see how they go. Wish me luck :cyclops:
dpav02 said:
The problem is, I really actually do like the TouchWiz interface (I know I know, I'm one of the few).
Click to expand...
Click to collapse
You are not alone, I enjoy the functions/features of the OTA ROMs.
Notification accessible when in full screen apps, the multi-window screen lets you "clear all" and access task manager&Google Now, the stock dialer has more efficient functions(Displays all calls from a contact if selected, slide right/left to call/send sms)
But going back on topic, I set my cpu to be conservative but I'm not sure if that'll save battery.
I want to be able to game when at work but not have the power-saving setting limit it yet still be able to last me a day. The OTA ROMs' power-saving feature was able to do that.

[Q] AOKP Ktoonsez + KT747 = ?

Hey I want to know how KT747 kernel works with AOKP Ktoonsez and Task650. From what I hear its pretty good. My main concern is battery life. I heard some people get around 5 hours of onscreen time which is incredible. If you are running these two together, what are good settings for good battery life? I'm using KT747 with CM10 M2 and Ktoonservative/noop but battery life is kinda bad. Thanks
I'm running that setup and although i can't really compare my battery stats to your as i have a 4400mah battery, i can say that for my phone atleast the battery life is superb. I actually just plugged it in after 67 hours, with about 7 hours screen on time. Obviously this isn't going to happen on a stock battery (mine came with a 2100mah), you could realistically expect a little less than half these numbers. I would suggest taking a look at this thread, which discusses overclocking and undervolting settings. I have posted pics of my personal undervolting settings (page 15, post 150), however your device may differ. I discuss why and my suggested method to finding the best value's for your device in the same thread, post 152 on page 16. Of course the discussion has many other opinions and suggestions as well so try them out until you find the one that works best for you. One thing i didn't mention is to disable the cpu settings in the settings>rom control>performance menu as it will conflict with the settings in ktweaker and can actually drain the battery much faster than normal.
dntesinfrno said:
I'm running that setup and although i can't really compare my battery stats to your as i have a 4400mah battery, i can say that for my phone atleast the battery life is superb. I actually just plugged it in after 67 hours, with about 7 hours screen on time. Obviously this isn't going to happen on a stock battery (mine came with a 2100mah), you could realistically expect a little less than half these numbers. I would suggest taking a look at this thread, which discusses overclocking and undervolting settings. I have posted pics of my personal undervolting settings (page 15, post 150), however your device may differ. I discuss why and my suggested method to finding the best value's for your device in the same thread, post 152 on page 16. Of course the discussion has many other opinions and suggestions as well so try them out until you find the one that works best for you. One thing i didn't mention is to disable the cpu settings in the settings>rom control>performance menu as it will conflict with the settings in ktweaker and can actually drain the battery much faster than normal.
Click to expand...
Click to collapse
Thanked*. Will take a look at the thread. Last time I undervolted I used some guys settings which were extremely wonky and cause a lot of mishaps. I'm still looking for good ones so I might try yours. Thanks.
DarthDerron said:
Thanked*. Will take a look at the thread. Last time I undervolted I used some guys settings which were extremely wonky and cause a lot of mishaps. I'm still looking for good ones so I might try yours. Thanks.
Click to expand...
Click to collapse
Sounds like too much undervolt.
jethro650 said:
Sounds like too much undervolt.
Click to expand...
Click to collapse
Just tried it, it was a little to much so I bumped everything up a little bit. Seems fine now. Going to flash AOKP later today.
Thats actually how i got those settings, i used what someone said was stable on theirs. It wasn't, playing pretty much any game on my phone would cause a reboot in less than 5 minutes. I think i ended up about 20 mv higher on all steps than his settings. You just have to find what works for you phone.
dntesinfrno said:
Thats actually how i got those settings, i used what someone said was stable on theirs. It wasn't, playing pretty much any game on my phone would cause a reboot in less than 5 minutes. I think i ended up about 20 mv higher on all steps than his settings. You just have to find what works for you phone.
Click to expand...
Click to collapse
Indeed. I have AOKP with Ktoonsez/sio and voltage a little higher than yours. Works fine, battery is good.
I have recently switched to the noop scheduler after an article i read which basically said there is no need for a scheduler using flash memory. All the other schedulers are designed for physical hard drives which have seek times, flash does not. Using these schedulers actually creates an artificial seek time, thereby wasting cpu clock cycles and burning precious energy in the process.
dntesinfrno said:
I have recently switched to the noop scheduler after an article i read which basically said there is no need for a scheduler using flash memory. All the other schedulers are designed for physical hard drives which have seek times, flash does not. Using these schedulers actually creates an artificial seek time, thereby wasting cpu clock cycles and burning precious energy in the process.
Click to expand...
Click to collapse
Was always on noop and ktoonservative. Most people recommend those two together
Boss-njo said:
That rom is no go.
Click to expand...
Click to collapse
Care to elaborate?
Boss-njo said:
That rom is no go.
Click to expand...
Click to collapse
I think its pretty good. I find it more stable than other roms, imo.
KT747/Cm10 m2
Hi,
I installed Cm10 m2, then ran it, rebooted, and installed kt747, cleared caches and fixed permissions, could not boot afterwards, Anyone else have this problem?
Mitch.sc said:
Hi,
I installed Cm10 m2, then ran it, rebooted, and installed kt747, cleared caches and fixed permissions, could not boot afterwards, Anyone else have this problem?
Click to expand...
Click to collapse
Hmm, I've never had that problem with KT. Make sure you have correct version, AOSP JB. I would recommend flashing CM10.0.0, the latest CM10 stable build.

Categories

Resources