Related
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.
Hi! Before i have got a drain of 3-6 mA with most of the roms, but suddenly all roms dain 16-20 mA. No matter if it is MIUI , cm7 or sense roms. They all have the same drain .. is my battery bad ?
Got my phone waterdamaged 2 weeks ago , but this bad battery time started yesterday...
First you need to calibrate the battery.
Charge your phone until Current Widget shows 0mA. Then go into recovery and delete battery stats. Let the phone discharge until it shuts down by itself, then charge until it is back to 0mA. That will calibrate the battery.
Secondly, new ROM's do take a few days to "learn" how to use the battery most efficiently so you wont get the best battery life instantly.
raze599 said:
First you need to calibrate the battery.
Charge your phone until Current Widget shows 0mA. Then go into recovery and delete battery stats. Let the phone discharge until it shuts down by itself, then charge until it is back to 0mA. That will calibrate the battery.
Secondly, new ROM's do take a few days to "learn" how to use the battery most efficiently so you wont get the best battery life instantly.
Click to expand...
Click to collapse
I know that ROM´s need a few days , but i have waited a few days ,and noticed that it is allways the same drain... But i will try calibrate my battery next
And please make sure that during the period of charging it the second time that you do not take it off the charger. That will mess up the calibration and you will have to start all over again.
you might want to try a new radio too
same for me. I tried everything I could.
I tried these roms:
-coredroid
-ARHD
-honey
-virtuous
-MIUI(current)
I tried these methods:
-multiple new recommended radio + ril
-battery calibration app + clear battery stats(recovery) @ 100%.
-full wipe 1.5
-re-root(hack kit v12.3)
-different kernels
When I first rooted my phone battery was perfect on any roms until I flashed ARHD,thats when my battery drainage happened.
P00t said:
same for me. I tried everything I could.
I tried these roms:
-coredroid
-ARHD
-honey
-virtuous
-MIUI(current)
I tried these methods:
-multiple new recommended radio + ril
-battery calibration app + clear battery stats(recovery) @ 100%.
-full wipe 1.5
-re-root(hack kit v12.3)
-different kernels
When I first rooted my phone battery was perfect on any roms until I flashed ARHD,thats when my battery drainage happened.
Click to expand...
Click to collapse
Same here lol. The drainage started after flashing ARHD, witch is the best rom out there .. so dunno how to solve this
shadowraiin said:
Same here lol. The drainage started after flashing ARHD, witch is the best rom out there .. so dunno how to solve this
Click to expand...
Click to collapse
how many hours you are getting now....with regular usage ????
I'm getting the same here... Started with ARDH too, then LeeDroid, now Virtuous.
Clean installs each time, apps restored using Titanium. Also re-flashed the recommended Radios too and calibrated the battery once.
Current drain is 15% / hour on Standby ~70+mA.
I noticed no unusal Wake Locks either.
I'm loving Virtuous, but thinking to go back to stock if the new Viruous update doesn't solve this.
Just whilst typing this I lost 2% :-(
Yeah this is no fun...
Sent from my Desire HD using XDA App
Delete all htc account and calibrate the battery
I've been having some strange battery issues.
TLDR: Phone battery drains and warms up when in use, but not when in sleep. Resetting batterystats doesn't fix it. Closing all processes doesn't fix it. It does it on a bunch of ROMs, which were always clean installed. The usual battery saving tricks do nothing.
More detailed:
Basically, whenever I use my S3, I get a considerable amount of battery drain. I used to have fantastic battery life when I was running LiquidSmooth RC5, where I was capable of 4-6 hours of screen time in a day. Now I can only get 2 or less hours of screen time in a single charge. This seemed to start after flashing LiquidSmooth RC8, but I also have the same issue in LiquidSmooth RC9, LiquidSmooth 4.2 beta, Task & Ktoonsez 4.1, Task & Ktoonsez 4.2, Slimbean, and Cynagenmod 10/10.1. So I don't think it is my ROM.
Anyways, so the battery drain only seems to happen when the phone is in use. During that time, the bottom of the phone around where the CPU is located gets considerably warm after just a few minutes of use. Otherwise, when the phone is locked, it deepsleeps fine with no drain. It still does it even when I go through my entire process list (and cached process list) and stop everything, it doesn't help. I've tried the whole batterystats reset where I charged to 100, drained, then charged to 100. That didn't help. I do make sure to clean install my ROMS, including clearing user data, cache, dalvik cache, and formatting my /system. When I look at my battery usage, it usually seems to be Android System using my battery the most. It can also be Android OS, Google Services, and Media sometimes. I've tried a ton of fixes, nothing helps. And of course it still does it with WiFi, data, GPS and all that off.
Help would be appreciated
battery life is an issue with many different factors.. there can be a bad app, bad battery, bad rom, anything really. if your phone is having issues then maybe 4.2 isn't the best for your phone there are many different roms to choose from and many are very stable.
Running 4.2 isn't the issue, though. It does it on 4.1 ROMs too. I'm not even on a 4.2 ROM right now.
Sounds like a rogue app or widget draining it. Get better battery stats. Type it in xda search. That will tell you for sure what exactly is draining the battery. Good luck.
Maybe your battery is just shot and its time for a new one
Sent from the scary door....
No, all these guys are wrong. Your phone is shot. I did everything you did. Better Battery Stats, calibrated battery, changed battery, changed SIM card, all radios shut off like data, GPS, Bluetooth, et cetera, no rogue apps, deep sleep according to BBS. You name it, I done it. And no one knows why our phones are doing this.
Sent from my SGH-I747 using xda app-developers app
Deggy said:
No, all these guys are wrong. Your phone is shot. I did everything you did. Better Battery Stats, calibrated battery, changed battery, changed SIM card, all radios shut off like data, GPS, Bluetooth, et cetera, no rogue apps, deep sleep according to BBS. You name it, I done it. And no one knows why our phones are doing this.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Except two of my friends that have S3s have the same issue, as well as another friend with an S2. I don't think all of our phones are defective.
I have recently installed cyanogenmod 10.1 onto my galaxy s3. The battery life since then has been very poor. If I leave my phone on without even using it, it drains about 1% every couple of minutes. When I look at the battery it says that the process of "phone" is taking up a huge amount of battery. Can anyone tell me why this is or how I can fix it?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
I have recently installed cyanogenmod 10.1 onto my galaxy s3. The battery life since then has been very poor. If I leave my phone on without even using it, it drains about 1% every couple of minutes. When I look at the battery it says that the process of "phone" is taking up a huge amount of battery. Can anyone tell me why this is or how I can fix it?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
crayonslayer said:
I have recently installed cyanogenmod 10.1 onto my galaxy s3. The battery life since then has been very poor. If I leave my phone on without even using it, it drains about 1% every couple of minutes. When I look at the battery it says that the process of "phone" is taking up a huge amount of battery. Can anyone tell me why this is or how I can fix it?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Generally these issues are user related and not ROM related.
I was so frustrated with some of the ROMs when I first started out but then realized I was doing a few things wrong (mainly because these ROMs, including CM10 have very decent battery life).
First, I would recommend a clean reflash:
factory wipe / reset
wipe cache (some say twice)
wipe dalvik cache
install ROM
after rom loads, wait 5 minutes (don't touch at all) then reboot
now you must wait.. sometimes it takes 24 hrs or so for a ROM to correctly load.
Not sure how true it is, but some say to now drain battery down, then fully charge.
At any rate, I follow these steps all the time and works great!
Also, keep in mind that most of battery issues are user related.. so think about what settings, apps and kernels are being used on your end before question a ROM. This is why waiting 24 hours or so before installing all of our "crap" will give give the ROM more time to settle.
Hope this help!!!! Happy Flashing
Thanks for the reply. However, I have looked at what apps and processes are draining my battery. And it appears it is the "phone" process that is doing this.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Just to piggyback on spenny88's reply, exactly what did you come from (stock?) and how did you wipe and flash?
This is all key as to how well your device will perform.
xBeerdroiDx said:
Just to piggyback on spenny88's reply, exactly what did you come from (stock?) and how did you wipe and flash?
This is all key as to how well your device will perform.
Click to expand...
Click to collapse
I have noticed something similar. I am coming from stock. I am going to guess my battery life is in the neighborhood of 10% less. I wiped everything before I installed CM. That said, this feels so much faster than stock.
Same Battery Issue on p1 (TMobile original Galaxy Tab 7.0)
spenny88 said:
Generally these issues are user related and not ROM related.
I was so frustrated with some of the ROMs when I first started out but then realized I was doing a few things wrong (mainly because these ROMs, including CM10 have very decent battery life).
First, I would recommend a clean reflash:
factory wipe / reset
wipe cache (some say twice)
wipe dalvik cache
install ROM
after rom loads, wait 5 minutes (don't touch at all) then reboot
now you must wait.. sometimes it takes 24 hrs or so for a ROM to correctly load.
Not sure how true it is, but some say to now drain battery down, then fully charge.
At any rate, I follow these steps all the time and works great!
Also, keep in mind that most of battery issues are user related.. so think about what settings, apps and kernels are being used on your end before question a ROM. This is why waiting 24 hours or so before installing all of our "crap" will give give the ROM more time to settle.
Hope this help!!!! Happy Flashing
Click to expand...
Click to collapse
Having the same issue with my Samsung Galaxy Tab P1000 (p1 in Cyanogenmod). "Cell Standby" is taking as much juice as "Screen", and I am using Wifi only. I don't even have a sim card in the device. Wish there was a way to disable Mobile Networks without disabling Wifi via Airplane Mode.
I installed through Rom Manager as upgrade from CyanogenMod 9.1 with wipe. I will try the recommendations above and report back.
Try the latest nightly (or RC4) of CM10.1. The battery life has definitely improved a bit.
Samsung Galaxy s3 intl battery drain cm10.1
I recently installed cm10.1 nightly on my international S3, it has cut the battery life down drastically and seems to drain over 10% an hour, even when not being used.
I've tried everything that i've came across by searching and still haven't had any real gain on battery life. Doing a full wipe and reinstalling doesn't help, and i've given it time for battery to calibrate; no difference. Even with wi-fi and location services off i'm getting a big drain. I've even tried switching to Slim Bean, if anything the battery was worse still.
Firstly i'm getting that Android OS is eating up a large chunk (usually above 60%) and using BetteryBatteryStats i don't see anything out of the ordinary in terms of partial and/or kernel wakelocks. I really don't wanna have to put the stock Touchwiz rom back on but that seems like the ways it's going. Any help would be greatly appreciated. Is there anything else i can try?
i find i get terrrible battery life on AOSP when i restore google through the setup. i skip thru the installation and open the play store to enter my gmail. then, before restoring my apps, i let it charge to 100%. honestly AOSP still doesnt have decent battery life, but it does improve if you play with it and try different things
hapticxchaos said:
i find i get terrrible battery life on AOSP when i restore google through the setup. i skip thru the installation and open the play store to enter my gmail. then, before restoring my apps, i let it charge to 100%. honestly AOSP still doesnt have decent battery life, but it does improve if you play with it and try different things
Click to expand...
Click to collapse
I would respectfully disagree with you. I have run a number of ASOP based ROMs and find them better than stock in terms of battery life. Certainly better in terms of not making my eye bleed (as I hate touchwiz, but that is a personal preference). I find that SlimBean gets me the best battery life of the CM based ROMs.
To clarify, I get just over 1%/hour battery drain, when idle (as measured by BBS) with GPS and google sync enabled, mostly on LTE. My phone happily spends almost all the time I am not actively using it in deep sleep.
The recipe to achieve this is to disable google location reporting and history, avoid tons of widgets that constantly update themselves, disable samsung services that you do not use, and monitor battery usage to look out for rogue apps that do stupid thengs, like hold wakelocks when they should be idle. Dropping the minimum frequency to 192 MHz, and going to ASSWAX (CPU scheduler) and ROW (I/O scheduler) also helps.
To get decent performance you do need to install things properly. Which means ensuring that you don't have conflicting settings or random leftovers. I tend to dirty flash updates but you reallly do get better and more consistent performance going through the pain of a complete clean install (format system, clear cache, reload apps from the store) when you are switching ROMs. Only use TiBu to restore app data. Once you do this, in my experience rogue wakelocks are the biggest cause of lousy bettery perfromance, and you can track down and eliminate these. I have around 150 apps loaded and do not run any task manager/autokiller. My phone typically runs without any reboots or power cycles between ROM updates which equates to rebooting every couple of weeks to a month. I have seen over 2 months of uptime.
Certainly should be able to go 16-20 hours between charges which I would consider real world all day functionality. I guess my point is that rock solid stability and all day battery life is possible if you are systematic about how you do things.
crayonslayer said:
I have recently installed cyanogenmod 10.1 onto my galaxy s3. The battery life since then has been very poor. If I leave my phone on without even using it, it drains about 1% every couple of minutes. When I look at the battery it says that the process of "phone" is taking up a huge amount of battery. Can anyone tell me why this is or how I can fix it?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I have the same problem..... Battery lose 1 % every 2 mins thats terible. :crying:
How could i find a fix ? plz if u have fix yours tell me ???
Hey guys,
my Endeavoru PVT (Tegra3 International) is now about one and a half year old, I can't remember how it was in the beginning, but now my battery drain is too heavy in my opinion.
At first I had AHRD, then I switched between some ROMs but now I am stuck at CyanogenMod 10.1.3 because as time went by, I started to hate Sense and I love the standard Android look. The thing is, since I switched from OrDroid to CM 10.2 or better said from Android 4.1 to 4.2+, the drain got heavy.
I removed all wakelocks, I use XM-Kernel with Smartmax+Row and limited the CPU freq, I turned off sync, gps and I only use 3G if I need the speed.
I mostly use whatsapp and rarely browse the internet with my phone, when I wake up at 7:00 AM I disconnect it from the charging cable, then I go to work etc. and at about 9:00 PM the battery only has 20-30% left and the average screen on time is maximum 2 hours overall and that's clearly not ok...
As I already said, I removed all wakelocks, the only wakelocks come from the kernel when the screen is active. So please do not link the ultimate battery life thread or something like that... I have no wakelocks and my settings are ok.
And when I start gaming, the battery drains 1% per minute which is insane! So I can't play any games at all.
With OrDroid and XM-Kernel I had the best battery life and almost no bugs.
Today I wanted to install Skydragon 2.0, but it was pretty buggy. So I switched to AHRD but with the XM-Kernel (17 beta for Sense5) my computer didn't detect the One X, I switched back to Stock Kernel, then it got recognized but the files were all displayed like a mess and I couln't copy any files onto the One X. Then I was pissed and restored my CM 10.1.3 backup... Is there any way to fix this??? Please no mass storage mods, these are not stable and don't work sometimes..
A few days ago I bought a One X+ battery, it should arrive next week. Maybe the battery is broken, but that doesn't explain why it drains so fkng much battery when I start to play games! And it doesn't fix my problems with Skydragon or AHRD. I would love to stay at CM, but there are the common issues which force me to switch to a sense rom.
I will probably switch back to OrDroid with XM-Kernel when the new battery arrives, hopefully it will fix the heavy drain. Can someone explain what could cause this massive drain? I mean, a phone should last at least 24 hours not 14...
Or is there any fully working AOSP rom with Android 4.1 for the One X? So I could benefit from the battery life and the look of Android 4.1.
Did you try erasing your sd card? Corrupt files might cause heavy media drain on aosp without showing wakelocks. I would recommend trying a sense 5 Rom, get a custom kernel and set it to smartmax and row like you are used to. If that doesn't work, replacing the battery is your last call. Good luck!
Go for a full wipe of your device & SD card first than try installing anew sense 5 rom and see whether the issue still persists?
donkyshot said:
Did you try erasing your sd card? Corrupt files might cause heavy media drain on aosp without showing wakelocks. I would recommend trying a sense 5 Rom, get a custom kernel and set it to smartmax and row like you are used to. If that doesn't work, replacing the battery is your last call. Good luck!
Click to expand...
Click to collapse
My sdcard is almost empty and the problem doesn't only happen on aosp but on all Android 4.2 or higher roms.
Did you even read my post? I already said, I tried Skydragon and ARHD and I had bugs... and yes, I made a full wipe 3 times.
shawly said:
My sdcard is almost empty and the problem doesn't only happen on aosp but on all Android 4.2 or higher roms.
Did you even read my post? I already said, I tried Skydragon and ARHD and I had bugs... and yes, I made a full wipe 3 times.
Click to expand...
Click to collapse
Stop being rude to someone trying to help you. Yes I did read your post obviously. You didn't state if you wiped your sd card. So what do you expect from the community if you figured it out all by yourself? If it's not the software it's the hardware, replace the battery.
Sent from my HTC One X using XDA Premium 4 mobile app
donkyshot said:
Stop being rude to someone trying to help you. Yes I did read your post obviously. You didn't state if you wiped your sd card. So what do you expect from the community if you figured it out all by yourself?
Click to expand...
Click to collapse
I didn't meant the part with the sd card, I meant the sentence were you said I should try a sense rom, which I already tried as I stated.
I'm sorry if you interpreted my post as an insult.
Edit: Ok I fixed the USB problem, I installed the newest HBoot and used lyapotas Kernel, now it works without problems. Now I'm going to fix all wakelocks and wait for my new battery.
I removed all wakelocks now and I got about one hour more since then, but at some times the drain is heavyer, I tried to backtrace the drain with GSAM and BBS (root) but there are no Problems with wakelocks. The battery drained from one minute to the other from 72 to 78, I don't know if the stats didn't refresh correctly, but I am now pretty sure it's the battery.
Okay, my battery arrived. I replaced it and besides I fixed my Wi-Fi with a piece of aluminium foil. The drain on the first start was heavy, but I think it has to undergo some full charges to calibrate.
But I have one more problem.. I'm on ARHD 33.1 with lyapotas LM kernel (XM beta didn't work very well), but I can't undervolt with SetCPU (paid for root version). Every time I want to save the undervolt settings SetCPU itself crashes and I don't really want to use TricksterMod for undervolting.
Is it because of lyapotas kernel?
I already reinstalled SetCPU two times..
Update: Wow, I never had 78% battery left after work! I guess it was my battery that was broken, so the thread can be closed.