I'm running CM6.1 RC2, and the past couple of days I have experienced excessive drain, mainly in the first 50%. I attached a picture of the issue. I went to spare parts battery history to see the network usage, since in the about phone battery usage cell standby was 84% of the battery usage, and under network usage there was just an entry for 0, using the most network. When I clicked on '0' the settings application crashed. Yesterday it dropped 35% in 2.5 hours, before it slowed down. It was ridiculous, never used to have this problem, and the battery is only a couple of weeks old so it has to be software. Today it is at 53% after 7.5 hours, which is pretty decent, but at around 70% I disabled 3g and background data to save some energy for a few hours. Is there any way of figuring out what is causing this, or should I reflash? Could it be a CM6.1 RC2 bug? Anyone else having this issue? Thanks in advance
BTW I have no idea why the dialer was so high in usage I only had like MAYBE 15 minutes total of voice calls in 2 hours. The 0 is what I'm concerned about.
Anyone? Bump? No one else is having the issue? Still happening to me on RC3.
I've been getting that problem too.
I used to have battery life of up to 4 days (Mostly standby), now I'm lucky if I get 1.5 (Same usage).
I went in to spare parts and it crashed for me too.
Battery drain here too since cm 6.1
Sent from my T-Mobile myTouch 3G Slide using XDA App
Well '0' is he system's ID, 0 is root. In the graph the blue is bytes sent, red is bytes received. Have you checked other usage like CPU usage? That might be a better indicator of what's using your battery. Then from there you can start to narrow it down to a specific process or app. I'm using the latest nightly and don't have that issue, never have. I use a bit more battery than I think I should but nothing crazy.
Do you have wifi or bluetooth on? Those drain your battery like no other.
I havent used wifi at all today, unplugged at around 6:30, it's 3:45 now and I'm at 63%, but from around 9:50 to 11:45 and then from 12:20 to 2:20 I had airplane mode enabled since the time without a signal was at 70%, very low signal area. So it seems like for only 4 hours or maybe 5~ of non airplane mode time I should be at above 63%. I only had wifi on for a half an hour today. I'm considering going back to stock for a few days just to see the battery life comparison, and then nandroiding back to CM6.1. I always end up going back to AOSP-based roms in the end. I don't have a data plan on my phone at the moment, getting it today I'm pretty sure, so could all of the blue be from the phone continuously trying to access a website? But other people said they have the same issue and I'm assuming that they have data plans, so that can't be too much related. Hmm.
I also checked cpu usage and such like you suggested, there were a lot of things listed but all but two of them were too small to even have a bar. The two that did have a bar visible were minuscule to put it lightly, so that can't be an issue. Battery use in the about phone area always has cell standby at the top, normally between 40 and 80%. It would seem like there is way too much cell communication going on, moreso than normal. Cell standby stays at the top in even high signal areas, so it's not the signal levels. Kind of stumped here.
Well if the cell is in standby then it's linked to a tower and awaiting activity. Every now and then it 'checks in'. If it's doing that too often then that could seriously drain the battery. You're right though, I'd just switch back. Trouble shooting the exact issue wouldn't be worth the time. Maybe try flashing it again later, could have just been a corrupt download that didn't flash properly.
After conditioning my battery religiously (full to empty with every charge cycle) I am back up to about 15 to 16 hours from full battery to system shut down which is way better than the 10-12 hours I was getting when I first loaded RC2. CR_OTA ROM gave me up to 24-30 hours off of one charge with the exact CPU/2g/3g/wi-fi "routine" as I am using with RC2. Tracked battery usage with System Panel app and RC2 has a steady and even drain pattern ... an even diagonal line down the graph (100% to 0%). Cell standby uses a ridiculous 40% of the battery from full charge! On the stock ROM System Panel app shows plateaus throughout the day when the phone screen is off/sleeping where battery use is virtually non-existent. I'm going to load RC3 today and track the cell standby and battery usage. This time I am not going to use setCPU and just let the ROM run as the CM team designed it to be used and see if anything has changed. I tried this with RC2 and the battery still trended absolutely evenly from 100% to 0%. I can live with a 16 hour battery cycle for the CM ROM because it is very smooth and never has a glitch. The stock ROM is smooth as well but it has some buggy behaviors that I just cannot stand for and it does not run the latest GAPPS.
I've noticed i have exacly the same problem(was actually gonna post it when i found this thread)
Needless to say that on eclair my battery lasted ~48 hours constantly, not its drained in max 24...
The highest I have EVER gotten was 24 hours, and that was on a cm6.1 nightly build, pre RC2. I loaded cr_mod and experienced a HUGE drain. I had airplane mode on, just to test, and it dropped 7% in an hour, in AIRPLANE mode, with no screen on time. I went into spare parts and looked at the usage, and sure enough, "running" was at the top, with 99% of the time spent without sleeping. This has never happened before though, so I can probably attribute that to my modifications. I deleted a few apk's and de-odexed it before I flashed it, and I have a feeling something I did corrupted something else, so I'll flash plain old cr_mod and see where that leaves me. I should probably get back into the habit of full charge/drain every cycle. I used to do that until my battery started lasting longer than I was awake for, so I always had to plug it in at around 15 to 30%. I'll run some more "trials" and see what's going on.
Also, on an unrelated note, I love the stock rom, I always love the sense UI, but I hate HTC_IME compared to the froyo Latin_IME, is there any way at all I could port the froyo Latin_IME to the eclair stock rom?
Edit: also, I flashed dumfuq's OC kernel over cr_mod, could that have been the culprit to the battery drain?
Shouldn't be the culprit. It would drain quicker because of the clock speed but shouldn't be too bad.
Yes Latin_IME should be able to be used with sense. Just delete htc_ime and clicker.apk then install latin_ime and it's corresponding clicker.apk which you can get from various roms'. Btw, clicker is used to calibrate the keyboard so you don't have to install it.
NJAZ, what's the result on using CM6.1 without SetCPU? Big difference or not?
KCRic said:
Shouldn't be the culprit. It would drain quicker because of the clock speed but shouldn't be too bad.
Yes Latin_IME should be able to be used with sense. Just delete htc_ime and clicker.apk then install latin_ime and it's corresponding clicker.apk which you can get from various roms'. Btw, clicker is used to calibrate the keyboard so you don't have to install it.
NJAZ, what's the result on using CM6.1 without SetCPU? Big difference or not?
Click to expand...
Click to collapse
Actually, by process of elimination, the kernel was the issue. I remember hearing about there being a bug in the older dumfuq kernels with something idle being null, I really don't remember but it had something to do with sleeping. I flashed pure CR_mod and then 3.5 dumfuq and I experienced the same issue where it wouldn't sleep. I flashed 4.0, but I think it's too soon to determine whether or not the same issue with sleep is occurring.
I tried doing what you said with LatinIME.apk, I even imported the lib file from /system/lib on CM6.1, but the it was nowhere to be found in the system when I booted. It wasn't under keyboard settings, and HTC_IME was gone. I figured it was an incompatibility between froyo and eclair, since the stock sense rom is eclair and the LatinIME.apk is from a froyo ROM. Do I have to something more than just adb push the apk and lib file? I also tried installing it with a file manager, and no surprise, problem parsing the package. It's a system apk so I didnt expect it to be able to install via a file manager. Do I have to use adb install instead of adb push? I'm wondering if htc IME is so wired into the system that it won't work that way. What if I rename LatinIME.apk to htcime.apk or whatever the name of HTCime is and see if that works, because the system may be is treating that as the stock android keyboard, rather than a third party one, because it is labeled touch input in settings, just like LatinIME in aosp roms.
I'll experiment some more I guess
edit: Nevermind, 4.0 is draining as well, albeit less rapidly. Ah well. I guess I'll have to go back to CM6.1 if I want to do overclock. Shame, I love sense so much.
ANOTHER edit: nevermind, you were right, it isn't the kernel at all. It happens when I turn wifi off. I'm assuming that's because I don't have a data plan so it's continually retrying a server that it can't access. I don't know why it didn't do this on the stock HTC kernel, but I'm pretty sure it's the issue. If I turn wifi AND mobile data connection off, it stays at normal drain as well. Well, I'm at 11% and my battery app is estimating roughly 1 hour and 20 minutes remaining, so I don't know if that's GOOD, but I'll give it a good full charge tonight and run it tomorrow. I hopefully will have data activated tomorrow so I can really test it.
Hey guys new to the slide forum but not new to the site. I come from the G1 thread and we had the similar problem. How is your battery life on a 2.1 ROM? I have my phone rooted with a Sense ROM and it has 2.2 and i do see a bad battery drain as well. I remember froyo ROMs battery life may not be the greatest yet. I remember that was always a big problem over there and it looks like it still hurts here. Have you tried setcpu settings?
Maybe this information will help, i forgot to mention last time i posted that i'm not using a HTC device, i'm using Samsung Galaxy S, and there are more ppl with this problem on our forum aswell, so maybe someone can use this information correctly, i mean, it's either a program that's doing this or some strange freaky froyo process that not everybody has? or idk..
We'll need to get a log or something from one of the phones doing this and see if we can pinpoint the issue. Anyone experiencing this issue using compcache? Maybe it's doing some sort of background compression/decompression or swap is swapping too much while the phone is 'off'. Like I said, we'll need a log dump uploaded so we can sift through it.
As far as the latin_ime, try getting the one from a 2.1 vanilla rom. Check the slide rom bible for the 'senseless' roms like CM5 or something. That should do it.
KCRic said:
We'll need to get a log or something from one of the phones doing this and see if we can pinpoint the issue. Anyone experiencing this issue using compcache? Maybe it's doing some sort of background compression/decompression or swap is swapping too much while the phone is 'off'. Like I said, we'll need a log dump uploaded so we can sift through it.
As far as the latin_ime, try getting the one from a 2.1 vanilla rom. Check the slide rom bible for the 'senseless' roms like CM5 or something. That should do it.
Click to expand...
Click to collapse
Well my desire was to get the froyo latinIME onto eclair, since it's prediction engine was so much improved, but I'm getting used to HTC_IME so it doesn't matter.
As for the battery, for me at least, running the cmkernel from dumfuq, v4.0, I get BETTER battery life than the stock HTC kernel. Weird right? If I enable data I get tons of blue in spare parts, under network usage, for things like calendar and contacts. I'll have to assume that's because of the lack of data plan, my data plan doesn't become effective until december 9th. Otherwise, I have no excessive drain. It must be a cm6 issue, with cell polling. Cell standby was always up in the 70%+ range in battery usage in cm6, and on the stock rom it's around 27%. Wi-fi and display are highest, and I still get 20-25 hours.
I agree, to pinpoint the cause of the problem in cm6, someone needs a log to analyze, I'm not actually that smart with these things, nor am I running cm anymore, so can't really help there, but it'd be a good start.
MusicMan374 said:
Well my desire was to get the froyo latinIME onto eclair, since it's prediction engine was so much improved, but I'm getting used to HTC_IME so it doesn't matter.
As for the battery, for me at least, running the cmkernel from dumfuq, v4.0, I get BETTER battery life than the stock HTC kernel. Weird right? If I enable data I get tons of blue in spare parts, under network usage, for things like calendar and contacts. I'll have to assume that's because of the lack of data plan, my data plan doesn't become effective until december 9th. Otherwise, I have no excessive drain. It must be a cm6 issue, with cell polling. Cell standby was always up in the 70%+ range in battery usage in cm6, and on the stock rom it's around 27%. Wi-fi and display are highest, and I still get 20-25 hours.
I agree, to pinpoint the cause of the problem in cm6, someone needs a log to analyze, I'm not actually that smart with these things, nor am I running cm anymore, so can't really help there, but it'd be a good start.
Click to expand...
Click to collapse
Well I just recently saw this almost exact same issue (maybe not as extreme) on the samsung tablet running Cyanogen. They removed the phone, telephony, mms, and one more .apk to resolve it. This issue was caused by the lack of a use for those .apks but the system was still using them... a lot. It seemed similar but not exact, maybe some of us more tech savvy people can look into those and see if there's an issue.
KCRic said:
Well I just recently saw this almost exact same issue (maybe not as extreme) on the samsung tablet running Cyanogen. They removed the phone, telephony, mms, and one more .apk to resolve it. This issue was caused by the lack of a use for those .apks but the system was still using them... a lot. It seemed similar but not exact, maybe some of us more tech savvy people can look into those and see if there's an issue.
Click to expand...
Click to collapse
Yeah that'd be cool. It must have something to do with that, since it's the cell radio sucking battery.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I flashed 6.1.0 stable, battery drain seems to be slightly less. I'm still at around 5 or 10% below where I was at this time on stock, with 9.5 hours off the charger, current level 57%. Although, I did use airplane mode for almost 2 hours, so really I'm like 10 or 20% below where I should be. I just can't figure it out, cell standby is at like 80% usage in this ROM. It's ridiculous, is it the polling intervals or something? How can it be so much less battery efficient than stock?
I flashed 6.1 RC2 with a low battery and had trouble with battery life. TMO's service was acting very strange for a couple of weeks and my cell standby was consuming a lot of juice. Flashed 6.1 RC3 with a well conditioned full battery. At first I used no setCPU just to see how things would go ... 11 hours from full battery to empty. Added setCPU to RC3 and got 27+ hours out of a full charge. Either TMO fixed it's towers or RC3 was better with cell standby because my network usage was not cranking overtime like it had been. Finally, I flashed 6.1 stable with setCPU and I average around 22 to 24 hours on one charge.
One observsation - when I first flashed RC2 I was really into my phone again. I was constantly tweaking it and flipping through options, testing apps, digging new Gapps, etc. ... bottom line I was just using my device waaaaay more than usual and I think that played a huge role in my (supposed) poor battery performance. All seems to be well with 6.1 stable.
Ok guys n gals, here's a puzzle for you all.
A few days ago, I noticed that my standby consumption had gone from around 10 mA to around 40mA using mobile data but with all other radios and GPS off.
For testing purposes I disabled location services through wireless. No effect.
I have tried with several Froyo and Gingerbread ROMs and the results are identical.
I have also tried with different radios, flashed using both fastboot and recovery.
I have used the ROMs without settings or app restore and I haven't installed any other apps than those included in the various ROMs. Additionally, i have tried various kernels.
Using Airplane mode shaves of a couple of mA.
aLogcat isn't showing any weird lines, mostly garbage collections.
I have tried searching far and wide and I have tested freezing various potential culprit apps using titanium backups' freeze function and all the battery calibrations/fixes I have found, but nothing helps.
At the moment I am using Oxygen RC6 with their recommended radio 5.09.05.30_2 and I am still seeing the same issue. The phone has gone from making it almost two days with moderate usage to barely a day with little usage.
The phone is S-OFF and I am using the N1table.
Can anyone please help with this? Apologies if this problem has been described before. I really tried searching before writing tis, but it could be that my search fu is weak.
Have you found a solution? In my case i'm getting ~100mA with the phone sleeping... and I can't seem to fix that.
Oxygen2.0-RC6 here.
Set wifi sleep policy to never.
Wireless and network-wifi-hit menu
Seams to help some people.
Sent from my HTC Desire using XDA App
TheGhost1233 said:
Set wifi sleep policy to never.
Wireless and network-wifi-hit menu
Seams to help some people.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Yeah, did that. No joy.
Maybe i'm totaly off, but, do you use Facebook app v1.5 ? If so, that's one power drain app because they messed up with new chat feature.
To anyone in Japan with horrible battery life, this might be helpful!
Solution for battery drain:
Just found this japanese guy who had the same problem with an Oxygen rom.
http://d.hatena.ne.jp/majadroid/20101223/1293094736
He explains what he changed in build.prop and has packaged it as an update here:
http://www.multiupload.com/5EAK6IUSQR
I am flashing it now and will report problems (or success I hope) in a while. According to the OP he managed to get to 1~2% hour drain which is very promising.
EDIT: It seems to have worked!!! I am back to about 10mA with screen off!
Thanks for all the replies.
The last thing I tried was a total restore using a HTC RUU, so I am now S-ON
This didn't help much though, even if I was down to 27 mA on some occasions, maybe that's normal for HTC roms
I have rooted it again but not S-OFFed and I am running the latest CM7 build (#12).
@TheGhost1233: I have tried the wifi sleep policy.
@m4dm4n123: No I don't use facebook app. Additionally, I have tried removing as many apps as possible only keeping some google apps and currentwidget.
@slyn4ice: Thanks for the tip. I have just flashed it but I am not noticing any big difference. I am seeing a few mA:s reduction, but still far from 5-10 mA in standby... I'll let it run for a day and see if it improves.
I am still open for suggestions...
Hello all. Ever since I got my EVO, I've been experiencing random restarts, even before I was rooted. Right now, I am running CM7.1 and Tiamat from kernel manager, and I probably have to do about 8 restarts and 5 battery pulls a day, no matter how often I use the phone. For instance, today I woke up and had to do a battery pull because the screen would not turn on. The light was also still orange despite the battery being fully charged. I unplugged it at about 8 in the morning and by 10 with no use, I had to pull the battery again because the screen was frozen off once again. Once I got it back on, the battery was down to 80%. I tried using it and half the apps would force close immediately, so I restarted... You get the picture. Some roms have been better than others, and kernels don't seem to make any difference, and I figured it was about normal. Then, I installed what is supposed to be a really buggy CM7 on my touchpad, and have only had to restart it once in the past 2 days, which makes me question how stable my phone actually should be. Does it seem like I should take it in to sprint, or is my experience about normal?
I also never overclock because of my already poor battery life and have tried underclocking, but don't see any noticible difference
bump. should I post somewhere else?
Run an RUU but stay s-off for the moment and see if the problem persists. If your phone begins working properly, then you can flash a recovery and flash whatever rom you want - but don't restore your backup. I'd start totally fresh if RUUing fixes your problems, don't restore your apps and data, just download them from the Market as you need them.
If the RUU doesn't help and the problem continues, take it in to Sprint. It's up to you if you want to s-on before taking it in - I've never heard of anyone getting problems from Sprint with s-off but without root, but I think it's a general rule to do so.
I hope everything works out for you!
Sent from my Evo + MIUI using Tapatalk!
I have heard and seen on here many times that random reboots are caused by battery problems, and bad software installs. Try calibrating the battery, also use battery monitor widget to see what ur batt temps are. Then reinstall all your apps, do not restore them then see if that helps.
Sent from my PC36100 using XDA App
I'll try an RUU when I get enough time to do some thorough testing. I have reinstalled everything directly from the market multiple times since I've had the phone, and also have used a total of four batteries with no change in behavior. I Will try the RUU soon though. Thanks for the replies
Hey guys
So i recently updated my S3 to 4.4.2 (about 2 weeks ago) and my battery life has become completely horrible afterwards. My phone is rooted and im using the stock Telus 4.4.2 update.
Some days the battery seems ok and other days its completely terrible. Yesterday and today for example i charged up my phone over night (like ive always done), and within an hour the battery dropped about 20% and i did nothing but check the weather for today.
Someone told me there was a camera issue and to just open and close the app and that would fix that issue...... made no difference. I dont have skype installed since i heard there was a battery drain issue with that app as well.
The only thing i have running in the background constantly is WeatherBug, WidgetLocker, NiLS, & GSAM Battery Monitor (both of which i used before the update to 4.4.2). I tried rebooting into recovery mode and clearing my cache and that made no difference either.
I even use an app called Greenify to put some apps in hibernate that i dont use often.
I have location turned off (like always) and i changed all my sync settings to sync only the stuff i need (work email and contacts basically). I dont have the cloud setup to backup anything, nor do i have anything setup under Backup and Reset either (again like always).
I have very limited data so ive gone though every single app under Data Usage and told them all to restrict background data. Im on wifi 99% of the time anyways (at work and home. the only time im not on wifi is when im driving). Ive turned off the stupid HP and Samsung print service plug-ins as well.
The only thing i really do on my phone is check my email when it comes through (which is set to sync every hour). Mayyyybe the odd quick facebook check, and text back and forth with my wife. And whenever im not using the phone i always lock it immediately after, otherwise the screen timeout is set to 30 seconds. Ive also got my brightness adjustment set to low.
Basically im at my wit's end on what to try next. Here are a couple screen shots ive just taken. Please help?
Edit: I should also mention that before i updated to 4.4.2 i was on 4.3 and my battery life was way better. At the end of the day i would be at roughly 30-50% battery life on average. It all depends on what i did with my phone during the day. I also notice that for some reason when the battery gets below 40-50% now it will drop off like crazy, especially when im at home for some reason.
JohnnyV84 said:
Hey guys
So i recently updated my S3 to 4.4.2 (about 2 weeks ago) and my battery life has become completely horrible afterwards. My phone is rooted and im using the stock Telus 4.4.2 update.
Some days the battery seems ok and other days its completely terrible. Yesterday and today for example i charged up my phone over night (like ive always done), and within an hour the battery dropped about 20% and i did nothing but check the weather for today.
Someone told me there was a camera issue and to just open and close the app and that would fix that issue...... made no difference. I dont have skype installed since i heard there was a battery drain issue with that app as well.
The only thing i have running in the background constantly is WeatherBug, WidgetLocker, NiLS, & GSAM Battery Monitor (both of which i used before the update to 4.4.2). I tried rebooting into recovery mode and clearing my cache and that made no difference either.
I even use an app called Greenify to put some apps in hibernate that i dont use often.
I have location turned off (like always) and i changed all my sync settings to sync only the stuff i need (work email and contacts basically). I dont have the cloud setup to backup anything, nor do i have anything setup under Backup and Reset either (again like always).
I have very limited data so ive gone though every single app under Data Usage and told them all to restrict background data. Im on wifi 99% of the time anyways (at work and home. the only time im not on wifi is when im driving). Ive turned off the stupid HP and Samsung print service plug-ins as well.
The only thing i really do on my phone is check my email when it comes through (which is set to sync every hour). Mayyyybe the odd quick facebook check, and text back and forth with my wife. And whenever im not using the phone i always lock it immediately after, otherwise the screen timeout is set to 30 seconds. Ive also got my brightness adjustment set to low.
Basically im at my wit's end on what to try next. Here are a couple screen shots ive just taken. Please help?
Click to expand...
Click to collapse
Well the stats you posted don't look bad.
To really know what's draining your battery though, you should install BBS (BetterBatteryStats), which can be found on here, in the app section. Let it monitor a full charge and post the results.
Alright i'll install that and post the results when i get them.
Said to hell with it and installed CM 11 on my S3 and now the phone is a HELL of alot faster and the battery life is just insane!
Thanks anyways!
I noticed you said your data is limited. To save data and battery life, give my lightweight app a shot, LeanDroid. There's a thread here on XDA with thousands of happy users
http://forum.xda-developers.com/showthread.php?t=2743316
Sent from my Nexus 5
Same issue with 4.4.2 update
I took the OTA 4.4.2 update and my battery life took a big dump as well as the battery / phone started getting hot. At first I just thought my extended 4200 mah battery was on the way out ....so I bought a new one and still have the same problem. So upset that I took that update ....and surprised not to find more complaints here. I assume I can go back to 4.3 or whatever the previous version is ?? Anyone have any suggestions??
(Conspiracy theory) This is probably AT&T 's way of getting people to buy new phones.
The SG3 is stock / unrooted
I'm using PureKat ROM for my Desire Z, and recently I've noticed that the battery drains so fast when I'm on career's 3G network (WiFi doesn't have this problem). I suspect on Google Play Services and I've disabled to auto-start, wake up and keep awake the phone and most of it's unnecessary services using this tutorial but it doesn't help. I've attached battery usage statistics after charging (all is normal there as you can see). Also I want to mention that 3G is mostly off (especially when it charges) so battery lasts as long as it is disabled (it can last for several days without 3G I think), and charging is really fast!
Has anyone had this problem?
Just to be on the safe side, check to see if this also happens on a stock ROM. I remember my old G2 did something like this. Can't check it anymore because my son killed it when I left him use it.
tronmech said:
Just to be on the safe side, check to see if this also happens on a stock ROM. I remember my old G2 did something like this. Can't check it anymore because my son killed it when I left him use it.
Click to expand...
Click to collapse
Thanks for the suggestion! Which exactly stock ROM version to use? And if I do that, it will disable root and restore to S-ON, right?
I thought that the problem was with battery, but when I replaced and tested it again, it still acts the same :/
Can anyone help me?
I think that is normal because my desire z give me only 3 hours on 3g and about 6.5 hours on WiFi and now using htc one it also have quit same battery timing like that !
Sent from my HTC One using XDA Free mobile app
I think that I've solved it with SetCPU profiles. Battery life is noticeably better now.