Related
I'm getting quite annoyed with my S3 and its piss poor battery life - currently seeing as little as 5 hours. On average, 55% of my battery goes to "Android System". I've tried a variety of battery monitors, but none can dig deep enough to determine which of the processes under Android System are sucking up all my juice. I'm on stock (rooted) and have tried to uninstall as much as I can (including the notorious Google+). Any tips on an app that can determine exactly which process is draining? I've also disabled as many Samsung apps as I can. I *did* try CM10 for a bit, but too many small things were not working right, so I nandroid'ed back to stock again.
ScottC said:
I'm getting quite annoyed with my S3 and its piss poor battery life - currently seeing as little as 5 hours. On average, 55% of my battery goes to "Android System". I've tried a variety of battery monitors, but none can dig deep enough to determine which of the processes under Android System are sucking up all my juice. I'm on stock (rooted) and have tried to uninstall as much as I can (including the notorious Google+). Any tips on an app that can determine exactly which process is draining? I've also disabled as many Samsung apps as I can. I *did* try CM10 for a bit, but too many small things were not working right, so I nandroid'ed back to stock again.
Click to expand...
Click to collapse
I had this problem numerous times before. If it is Android System that is taking up battery, then its most probably a bad kernel. Your nandroid backup probably was bad. (it sucks, i know). Redownload the stock rom, flash it in odin, before starting up reboot in recovery and factory reset, then start it up. Your problem should be resolved. dont restore any apps and start fresh. Like I said it sucks but what can you do?
Hey ScottC,
Definitely doesn't sound normal. At the end of the day, I'm sitting around 10% lost to android system, 15% tops (of course this can vary on what you use and how you use it, but if your battery dies in 5 hours, certainly something is wrong). It's possible that in the process of nandroiding back, something messed up. I'd recommend a complete wipe (factory reset, wipe dalvik, etc), then test it out for a day or two. If the issue persists, you will likely want to Odin back to stock. If it still persists (highly unlikely), I'd call in for an exchange. Best of luck to you, and please let us know the results!
Thanks for the tips - to clarify, it was doing this before I ever nandroided back - but I have a feeling wiping might be the best bet (or trying out a better JB leak).
I think you may be getting the gsiff_daemon bug. Next time you have the battery start draining like that, turn on show cpu usage under developer options in settings. If you see gsiff_daemon at the top, then that's what's causing the android system battery suck.
The fix is simple go to /system/bin with a root explorer, mount r/w and rename gsiff_daemon to .Bak or delete it. This won't hurt anything. Then reboot.
There is a thread about this in QA. If you check it out keep in mind it's full of wags and speculation.
Sent from my SGH-T999 using xda premium
I have the same issue. My phone was 100 percent and I've been sitting here watching the Texans game and I'm getting the worst battery life today that I have in my week or so of owning this phone. My phone is bone stock.
Sent from my SGH-T999 using xda premium
I have the same issue
ibous said:
I think you may be getting the gsiff_daemon bug. Next time you have the battery start draining like that, turn on show cpu usage under developer options in settings. If you see gsiff_daemon at the top, then that's what's causing the android system battery suck.
The fix is simple go to /system/bin with a root explorer, mount r/w and rename gsiff_daemon to .Bak or delete it. This won't hurt anything. Then reboot.
There is a thread about this in QA. If you check it out keep in mind it's full of wags and speculation.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Add another one to the list for this problem. I've had my phone since Sept. 27th (so 3 weeks?) and up until about 4 days ago it was great. Great battery life, even with all the bells and whistles turned on, and several apps that update constantly. For some reason a few days ago it started to battery drain HARD, downing to 25% of the battery life in less than 6 hours. That's with the phone sitting idle, not touching it, on wi-fi (not 4G) with excellent signal. Last night I plugged the phone in at 10% battery, did some chores, and returned some 3 hours later to find the battery at 5%. It drained while it was plugged in!
The battery drain issue seemed to start after the phone decided to have a certain level of diffuculty finding a 4G signal. I had to reboot the phone to get it to connect to the network. After that, the Android System will take anywhere from 55% to 76% of the battery drain.
I have shut off numerous programs, disabled the Samsung apps that were said to possibly be a problem, and looked for the gsiff_daemon in the CPU list (my top process is "com.android.systemui"). I searched com.android.systemui to see if I could find a fix, and all I'm really seeing is "flash a new ROM" or "Your kernal is bad, reset or reflash it." I'm running a 100% stock phone, and actually had no intention of rooting or flashing this phone yet, and I didn't want to have to factory default it. It's starting to look like that's my only option. Someone said that this bug seems to crop up out of pure chance and I think they may be right. My husband has the identical phone, bought, charged and activated the same day, and he doesn't have this problem. He's still getting the incredible battery life that I used to get.
So what's the skinny? Is my only option on this a factory reset? I've seen threads referrring to a thread dedicated to this topic, yet no links. If there's more info to be found, I'd love to read it.
This thread might as well be titled "all noobs thread". It is known widely that android system in jb leaks is a problem but of course u cant know that cuz reading and searching are two words that sound like chinese to you.
lazarat said:
This thread might as well be titled "all noobs thread". It is known widely that android system in jb leaks is a problem but of course u cant know that cuz reading and searching are two words that sound like chinese to you.
Click to expand...
Click to collapse
Actually I have "searched" and "read". I wouldn't have posted had I been able to find an answer. Everything I've found has been for ROOTED/FLASHED ROMs, and I'm on stock. I don't want to root/flash this phone, I'd like to fix it without having to return it or factory default it if possible. I also mentioned that I had gone through threads and tried as many of the tips there that applied to my situation.
While I'm not nearly the level of many here, I'm also not a n00b. I've flashed, rooted and hacked many devices, I'm just trying to avoid that here. I didn't run across anything called "jb leaks" in my search, so if you'd care to be helpful and elaborate on that term, it might prove useful.
I believe this is the thread you were told about.
http://forum.xda-developers.com/showthread.php?t=1755180
When you checked cpu use, how did you check it? There's an option in Dev Options to Show CPU Usage and you can see real time what's running. Just fyi in case you did it differently.
Sent from my SGH-T999 using xda app-developers app
Thanks for the Link, Doc! It's much appreciated. As far as checking the CPU, I used the option under the Dev Options menu and watched it bounce about. Many different programs would take top spot, but when the phone was idling it was always com.android.systemui at the top. When it wasn't top, it was never far below.
Have you tried booting into recovery and wiping dalvik cache?
If it comes to it, before factory resetting since you want to avoid that, download the official stock FW and flash with Odin. I'm pretty sure it will keep your data and apps intact. Backup data first in case I'm remembering wrong. If that doesn't do it then factory reset may be your final option.
Check settings > Battery, and open Android System (I'm betting its at the top). This may give you a better idea of what the root cause could be, maybe...
Sent from my SGH-T999 using xda app-developers app
CorbieMessenger said:
Actually I have "searched" and "read". I wouldn't have posted had I been able to find an answer. Everything I've found has been for ROOTED/FLASHED ROMs, and I'm on stock. I don't want to root/flash this phone, I'd like to fix it without having to return it or factory default it if possible. I also mentioned that I had gone through threads and tried as many of the tips there that applied to my situation.
While I'm not nearly the level of many here, I'm also not a n00b. I've flashed, rooted and hacked many devices, I'm just trying to avoid that here. I didn't run across anything called "jb leaks" in my search, so if you'd care to be helpful and elaborate on that term, it might prove useful.
Click to expand...
Click to collapse
You are not the op of this thread so i cannot comment about your problems. The first posts regard rooted devices running jb leaked roms and in the jb leaked roms threads all people talk about is android system taking a high percentage of the battery usage. So one must be really blind not to notice what is the problem and fix if there is any. There is no fix and it is kernel issue. Thats the reason why it is called leak and not official release. U can post some screenshots of ur battery usage and firmware version you are running if u want people to help u since u claim u r all stock and still android system usage is high 76%.
Doc-
I tried booting into recovery, but since I'm not a rooted user I can't clear the delvick cache. Somehow in the process of attempting booting into recovery I managed to lose my set wallpaper and most of my homescreen widgets, though the rest of my data and programs seem perfectly intact (accidentally went into a safe mode option). I did clear the cache partition in recovery, and tried another trick someone listed of pulling the battery and holding down the power key (I'll try anything at this point) and oddly it seems to be behaving better so far. Sitting on my desk it didn't discharge at all, and having just put all my widgets back it's only drained a few points. The screen is now the big spender at 39% with Cell Standby next at 12% (previously is was Android System being the hog at 50-70%). I have no idea which of the things I did actually did anything, but I think this just saved my tail.
I'm going to charge the phone normally tonight and leave it loose all day tomorrow like I usually do, and see what happens. If it starts battery draining again, I'm going to try flashing with Odin. Here's hoping I'm one of the few lucky ones where the problem simply "goes away".
Thanks again for your help!
Well that's kinda weird...good, but weird!
I've heard of people going into safe mode but its never intentional and I've never found how to do so at will.
As long as it goes back to normal though! Hope it does! Good luck!
Sent from my SGH-T999 using xda app-developers app
I know that this sounds pretty simple and you may have already tried this, but it always works like a charm for me. Try draining the battery ALL the way down until it automatically shuts off. Then keep turning it on until it won't even turn on our vibrate anymore. Plug it in and turn it on. Leave it plugged in until it's at 100% again, I do this overnight so there's no usage other than standby. Hopefully this will get your battery back in shape. Good luck!
DocHoliday77 said:
Well that's kinda weird...good, but weird!
I've heard of people going into safe mode but its never intentional and I've never found how to do so at will.
As long as it goes back to normal though! Hope it does! Good luck!
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Sometimes I wonder how I got into Safe mode.
forum.xda-developers.com/showthread.php?t=1821557
Well, It behaved for about an hour, then it started the massive drain again. Sadly I just backed a few things up and then factory defaulted it. We're leaving on a trip tomorrow, and I need it to not be a power-sucking brick. Oddly, everything that my CPU report was showing was identical to my husban'd phone, which has no issues with battery life. The Gsiff daemon never once showed up.
As far as safe mode, I held down the volume down button while I powered up the phone. It went into safe mode. Don't know if it'll work for y'all, or if it was just a fluke on my part. :>
Thank everyone for your help in trying to troubleshoot this. One of these days I'd love to have an electronic device that just worked without me having to poke around in it's guts. ;>
If its still acting up after the factory reset, your best bet is to flash the stock FW with Odin. If the factory reset didn't wipe your internal sdcard, you may need to to wipe it in recovery by using format data as well. (Factory reset should do this anyway as long as you're on stock recovery)
I've seen on some jb leaks where this would significantly help. I know your not using jb but its worth mentioning anyway.
Good luck!
Sent from my SGH-T999 using xda app-developers app
Hi folks,
I have an at&t galaxy s3 that I bought sometime in late January, immediately flashed with Task's AOKP rom, and enjoyed some great battery life with. I was going 15 hours of moderate use (occassional texting, IM, email, browsing, auto-sync on, no wifi, only LTE) with 38% of battery life still remaining. I only have a screenshot from that long ago because I used it to boast to my non-android friends (haha/boohoo).
After a few updates to the ROM, I started noticing my battery life getting significantly worse. It got to a point where within 7 or 8 hours it would run down to under 15% of battery life remaining, with very similar usage patterns and apps. I have very good reception where I work, good wifi (experimented with this as well). I tried doing a full wipe and reinstalling the rom, tried the liquid smooth rom as well (last few screens), but nothing seems to be fixing it.
I installed better battery stats as well and I'm not sure how to be reading the info from the tool. I'd appreciate it if anyone could look at the screens I already have, and recommend any additional info that could help me figure this one out. Thanks!
I know only wakelock detector. its easy to understand. but someone will chime in. but if your usage hasnt changed then something must be causing that drain.
when you did the wipe did you restore data? did you do clean flashes? my only suggestion is try wakelock detector. charge your phone. let it sit for a few hours or with light use.
your screen shot shows that your phone was awake a lot when screen wasnt on. what app causes this im not sure. but find it and get rid of it if you dont need it
sevengroove said:
Hi folks,
I have an at&t galaxy s3 that I bought sometime in late January, immediately flashed with Task's AOKP rom, and enjoyed some great battery life with. I was going 15 hours of moderate use (occassional texting, IM, email, browsing, auto-sync on, no wifi, only LTE) with 38% of battery life still remaining. I only have a screenshot from that long ago because I used it to boast to my non-android friends (haha/boohoo).
After a few updates to the ROM, I started noticing my battery life getting significantly worse. It got to a point where within 7 or 8 hours it would run down to under 15% of battery life remaining, with very similar usage patterns and apps. I have very good reception where I work, good wifi (experimented with this as well). I tried doing a full wipe and reinstalling the rom, tried the liquid smooth rom as well (last few screens), but nothing seems to be fixing it.
I installed better battery stats as well and I'm not sure how to be reading the info from the tool. I'd appreciate it if anyone could look at the screens I already have, and recommend any additional info that could help me figure this one out. Thanks!
Click to expand...
Click to collapse
Try and see if AT&T will give you another battery. They are usually good about doing this. Give 611 a call and see what you can achieve. If you go into a corporate store I would recommend going to stock first. Of course making a nandroid is optimal. If this does not correct your issue at least their records will so such so you can work on getting a warranty repair.
s384 said:
when you did the wipe did you restore data? did you do clean flashes?
your screen shot shows that your phone was awake a lot when screen wasnt on.
Click to expand...
Click to collapse
i'd like to add by asking when you say full wipe, what did that include for you?
You said after a few updates. Try reflashing a backup to when you had the best battery life. Most likely it's because of additional features. Your battery stats doesn't show any wakelock issue.
Sent from my SAMSUNG-SGH-I747
s384 said:
I know only wakelock detector. its easy to understand. but someone will chime in. but if your usage hasnt changed then something must be causing that drain.
when you did the wipe did you restore data? did you do clean flashes? my only suggestion is try wakelock detector. charge your phone. let it sit for a few hours or with light use.
your screen shot shows that your phone was awake a lot when screen wasnt on. what app causes this im not sure. but find it and get rid of it if you dont need it
Click to expand...
Click to collapse
I'll definitely install wakelock detector and give it a go - now that I think about it, I sometimes notice that my phone will be warm when I pull it out of my pocket.
xBeerdroiDx said:
i'd like to add by asking when you say full wipe, what did that include for you?
Click to expand...
Click to collapse
When I say full wipe, I wipe data/factory reset, wipe dalvik cache, format /system. I let google restore all my apps on startup though.
S384, does that constitute a clean flash for you?
aybarrap1 said:
Try and see if AT&T will give you another battery. They are usually good about doing this. Give 611 a call and see what you can achieve. If you go into a corporate store I would recommend going to stock first. Of course making a nandroid is optimal. If this does not correct your issue at least their records will so such so you can work on getting a warranty repair.
Click to expand...
Click to collapse
This was going to be my last alternative - flash back to stock, and if the problem persists, get a new battery. I've only had the phone for about 2 months, so it is indeed unlucky if my battery itself is defective.
Domoo said:
You said after a few updates. Try reflashing a backup to when you had the best battery life. Most likely it's because of additional features. Your battery stats doesn't show any wakelock issue.
Sent from my SAMSUNG-SGH-I747
Click to expand...
Click to collapse
But surely Task isn't including features on his rom that drains battery faster .. ? This is worth a shot though, a better alternative than going to stock for sure.
Wakelock detector screenshot attached - not sure if this is enough of a span to make any inferences, but I'll keep monitoring it.
yes, a full wipe constitutes wiping data, cache, dalvik and formatting system.
i would wipe data and both caches and flash back to stock. then do a full wipe and flash your rom of choice and wipe data and cache again. i'd almost bet this clears your issue up. as someone already said, grab the release that was working well for you if you want to stick with tasks 4.2.2.
i'm on aokp's 4.1.2 release from october and i get about a day or 2 of use. depending on my usage
---------- Post added at 08:44 PM ---------- Previous post was at 08:41 PM ----------
this is a recovery-flashable stock firmware zip with root injected from upndwn4par: http://d-h.st/8OQ
in case you're interested in my suggestion
xBeerdroiDx said:
yes, a full wipe constitutes wiping data, cache, dalvik and formatting system.
i would wipe data and both caches and flash back to stock. then do a full wipe and flash your rom of choice and wipe data and cache again. i'd almost bet this clears your issue up. as someone already said, grab the release that was working well for you if you want to stick with tasks 4.2.2.
i'm on aokp's 4.1.2 release from october and i get about a day or 2 of use. depending on my usage
---------- Post added at 08:44 PM ---------- Previous post was at 08:41 PM ----------
[/COLOR]this is a recovery-flashable stock firmware zip with root injected from upndwn4par: http://d-h.st/8OQ
in case you're interested in my suggestion
Click to expand...
Click to collapse
This may be a basic question, but are you recommending this because you think there is a rogue app somewhere that needs to get wiped, or because somewhere along the way something may have fundamentally gone wrong with ROM installations, switching around etc?
sevengroove said:
This may be a basic question, but are you recommending this because you think there is a rogue app somewhere that needs to get wiped, or because somewhere along the way something may have fundamentally gone wrong with ROM installations, switching around etc?
Click to expand...
Click to collapse
my suggestion is based on several things:
1. you used release updates. perhaps even OTA.
2. you flashed another aosp-based rom and werent coming from stock
these types of things will bog your system down. dont get me started on a custom roms updates. dirty flashing repeatedly will cause things that used to work to become buggy.
always try to flash an aosp-based rom over stock. just works best.
Yup, I've definitely had that bogginess before on my old SII when I didn't do clean wipes, but the problem always went away when I did a clean wipe and reinstall, even though it wasn't from stock to aokp.
I'll wait and see if we can catch something through the wakelock detector - if that comes up empty, seems like this is the way to go.
sevengroove said:
Yup, I've definitely had that bogginess before on my old SII when I didn't do clean wipes, but the problem always went away when I did a clean wipe and reinstall, even though it wasn't from stock to aokp.
I'll wait and see if we can catch something through the wakelock detector - if that comes up empty, seems like this is the way to go.
Click to expand...
Click to collapse
keep me posted. if you reset, do full wipes before and after flashing the stock firmware zip (its for at&t btw. i'm assuming you are too?)
xBeerdroiDx said:
keep me posted. if you reset, do full wipes before and after flashing the stock firmware zip (its for at&t btw. i'm assuming you are too?)
Click to expand...
Click to collapse
Yup, I'm on at&t.
Another Wakelock update from this morning, + BBS info - still on LiquidSmooth. Thoughts?
More stats ... looks like the battery did a little better than usual today, but still not even close to what it used to be.
Does anyone see anything out of the ordinary? I'm just trying to figure this out to make sure it's not user- or app-induced, so that I don't repeat the problem again.
does seem like a lot of wakelocks. I really dont know how to fix that but I have much less. like maybe max of a minute used by top app. and maybe 3 or 4 apps with wakelocks. but it might depend on your usage.
s384 said:
does seem like a lot of wakelocks. I really dont know how to fix that but I have much less. like maybe max of a minute used by top app. and maybe 3 or 4 apps with wakelocks. but it might depend on your usage.
Click to expand...
Click to collapse
Over a span of 7 - 8 hours? Hmm wow - yea, I wish I had these numbers from when my battery was running well because honestly these apps are the same ones that I used at that point. Google music for commute, email, kik/whatsapp for im'ing, (maps is a little odd, don't remember using that today) ...
Any inferences from the BetterBatteryStats?
just another suggestion. try clearing data from email services and anything else that you use often. I believe excess data in apps can cause the wakelocks. I know it might suck but every now and then I just go through my phone and delete stuff. or download something like clean master and it will delete temp files and what not from your storage.
in your situation I would probably do these things. try again. or else do a factory reset and system wipe and reinstall a rom and not restore data to your phone but rather redownload your apps. I used to do this all the time due to just not knowing otherwise and it worked.
---------- Post added at 09:48 PM ---------- Previous post was at 09:44 PM ----------
or sorry go into application manager works too. find apps you use a lot and clear the data and cache. some apps this is not recommended because you dont want to lose data but it does help. for example my maps currently has 13mb in cache. I clear that and it seems to make no difference in what the maps app will do for me. theres also lots of threads on xda about wakelocks.
s384 said:
just another suggestion. try clearing data from email services and anything else that you use often. I believe excess data in apps can cause the wakelocks. I know it might suck but every now and then I just go through my phone and delete stuff. or download something like clean master and it will delete temp files and what not from your storage.
in your situation I would probably do these things. try again. or else do a factory reset and system wipe and reinstall a rom and not restore data to your phone but rather redownload your apps. I used to do this all the time due to just not knowing otherwise and it worked.
---------- Post added at 09:48 PM ---------- Previous post was at 09:44 PM ----------
or sorry go into application manager works too. find apps you use a lot and clear the data and cache. some apps this is not recommended because you dont want to lose data but it does help. for example my maps currently has 13mb in cache. I clear that and it seems to make no difference in what the maps app will do for me. theres also lots of threads on xda about wakelocks.
Click to expand...
Click to collapse
I typically redownload my apps instead of restoring the data - but clearing the cache etc sounds like a good idea anyway. I did it for the email and music app, let's see if things change.
sevengroove said:
More stats ... looks like the battery did a little better than usual today, but still not even close to what it used to be.
Does anyone see anything out of the ordinary? I'm just trying to figure this out to make sure it's not user- or app-induced, so that I don't repeat the problem again.
Click to expand...
Click to collapse
Dude add up all the wake locks in that bottom picture and its like 30% of your battery. That's terrible. Thus is what it should look like. Add mine up and you are at only a couple %.
Sent from my SAMSUNG-SGH-I747
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 ???
I had noticed when I first went to 4.2.X that the butter was fantastic- super smooth, crazy fast responsiveness, and decent battery life (I'm a fairly heavy user). For me- if I could get 12 hours of battery life, I'd be super happy.
I'm a total crack flasher- but I almost always wipe system, wipe cache, wipe dalvik, format system, then install the ROM, set up the basics (Google), allow all my apps to download, restart, then use TB for a couple of items (like 2...and App only, not app and data), and reinstall any other apps fresh by just installing the APK and rebuilding. I find this method to be as clean as I can do it...obviously it takes some time.
I've noticed though that the more I crackflash the more the smoothness is lost and battery life drops.
So I was wondering if anyone has any suggestions for my issues:
1- I get phone lag at times. Sometimes it's super crazy fast, and others- it can be completely unresponsive for a minute or two...then crawl...then I just reboot. I try to not use the phone for a minute or two after restarting so it can really get booted up (since it takes a minute for all the 'fresh' downloading to happen, Lux to get running, light flow to get going, etc.).
2- my battery life is trash. If I have my phone on for 4-5 hours, and actually using it for 2, the battery will be WELL below 50% (more like 15%). I have the standard battery, and the factory upgraded 2100mAh battery. I usually use the big boy, and the standard as my backup. I can literally kill both in one day. It's not like I'm constantly streaming/downloading, although I do do some streaming. For example: I can do 45 minutes of iHeartRadio streaming in the AM while reading some news articles, then some texting/phone calls, then play a bit of WordsWithFriends. Now it's been 4 hours, and I'll be at 30% or less battery life.
ROM's: I usually run APOP's AOKP, sometimes stuff by PrimeDirective, sometimes stuff by DroidTh3ory
Kernels: I usually run Franco's nighlies...but I have played with AK, lean kernel, whatever the compiler's default is, etc. I usually run interactive.
So should I do some kind of full unroot, kill everything, go back to factory radios, then rebuild from total scratch...and get a new battery? Or can you think of anything else? I asked Apop, and he suggested I go for the re-lock the device and then unlock and go from scratch. While this is probably the best bet- I'd really like to avoid that as it is quite a bit time intensive.
PS- Most of this was from a PM to APOP so sorry if any of it sounds weird...I tried to clean it up. Again- I love his work and don't like when people ask a question then go and ask others...I just wanted to see if there's something him and I didn't think of so I don't go through all that for nothing. THANK YOU ALL!!!
As of Sunday my Google Play Services has been KILLING my battery. It's been using over 25% of the battery and draining FAST...it's already at 25% today and it's only 1pm.
Typically I am at around 70% at 1pm.
What changed? NO idea.
I have done some googling. and I have done everything it said to do.
Clear cache on the app, reboot.
Clear the phone cache and reboot
Etc.
I did that Monday night and everything was pretty good Tuesday...Wednesday, not so much.
Anyone have any ideas?
Please help, battery life IS life!!
THANKS!!
ryanvan9 said:
As of Sunday my Google Play Services has been KILLING my battery. It's been using over 25% of the battery and draining FAST...it's already at 25% today and it's only 1pm.
Typically I am at around 70% at 1pm.
What changed? NO idea.
I have done some googling. and I have done everything it said to do.
Clear cache on the app, reboot.
Clear the phone cache and reboot
Etc.
I did that Monday night and everything was pretty good Tuesday...Wednesday, not so much.
Anyone have any ideas?
Please help, battery life IS life!!
THANKS!!
Click to expand...
Click to collapse
The only thing U have done when this occurs is to clear cache in recovery. I have had to do it twice on occasion. It sounds like you already did that. The only other thing I can think of is maybe some other app is causing google services to run. Any new apps or app updates or changes in the way you use them that correspond to the time it began might be the cause. You may want to post in the general Q&A section since more people probably look there and you will get a wider range of experience to draw from.
Smithfolk4 said:
The only thing U have done when this occurs is to clear cache in recovery. I have had to do it twice on occasion. It sounds like you already did that. The only other thing I can think of is maybe some other app is causing google services to run. Any new apps or app updates or changes in the way you use them that correspond to the time it began might be the cause. You may want to post in the general Q&A section since more people probably look there and you will get a wider range of experience to draw from.
Click to expand...
Click to collapse
Yes, I did that in recovery. I will post it there...thanks for the advice.
I don't post on forums often.