Develop Bugs

S3 Massive battery and "Android System" usage with and without charging

I'm having a problem with my Samsung Galaxy S3 (rooted, but no custom ROM) through AT&T where it's losing battery power at a much higher rate than normal every once in a while.
Specifically, today, I was using the GPS feature and charging it in my car, and yet, even though it said it was charging, the battery continued to lose charge. Also, in the past, the phone has lost charge very quickly, and when I check the battery usage, "Android System" is very high on the list, up to 60% (with "Screen" being at 11%, which is usually the biggest culprit for me since I leave the screen on a lot). One time, I went to bed at around midnight and had forgotten to plug in my phone. When I woke up it was off. I turned it back on and looked at the battery stats using 3c's Battery Monitor Widget and saw that it lost charge quite slowly until about 5am, when suddenly the usage went up dramatically, and the phone went from about 60% to 0% in the course of an hour and a half of non-use.
Because this is not a problem I can reproduce on command, I'm not sure exactly what application/process is causing it. Does anyone have any suggestions or has anyone else experienced things like this happening before? (Besides me having to pay for the "betterbatterystats" app?)
Edit: Also, "Android System" sometimes is sometimes listed as "gsiff_daemon" in the battery stats, and within 3c's Battery Monitor Widget, Android System is separate from "gsiff_daemon", where gsiff_daemon's usage is almost 15 times the usage of Android System.

Checkout this thread to see if the gsiff_daemon is your problem. tl;dr when the system is hot and tearing through the battery, go to system settings -> Developer options -> and check Show CPU usage. If gsiff_daemon is the top or second highest on the list, then that is your problem. To solve it for the moment, use system tuner, or something else, to kill gsiff_daemon. There is no permanent cure at the moment, other than to delete gsiff_daemon. Both of those fixes require root, the non-root fix is to reboot.
If gsiff_daemon is not on the list, then something else is the problem, but Show CPU Usage should give you an idea of what system process is running hard.

Samsung Push problem
J M L,
Thanks for the information. I'll do that if the problem arises again. However I also did something else that looks like it may have been the solution for my particular problem, which was disabling the "Samsung Push" service in the Application Manager. So far, my battery life has gone back down to very reasonable levels.

dansushi said:
J M L,
Thanks for the information. I'll do that if the problem arises again. However I also did something else that looks like it may have been the solution for my particular problem, which was disabling the "Samsung Push" service in the Application Manager. So far, my battery life has gone back down to very reasonable levels.
Click to expand...
Click to collapse
Interesting, I installed "micro cpu monitor" shows thin line at top of screen showing both cores.
I haven't had this happen for some time now but after playing with google play and maps downloading offline maps etc I noticed my 2nd core pegged out.
Having seen this in the past & ignoring it I now realize that majorly drains the battery as well as it getting warm.
A simple reboot seems to be the only thing that fixes it. Clearing ram and closing recent screens dies nothing to clear the "cpu jam".
If left alone, it always shows the culprit as "android system"
As to what part of "android system" I don't know.
But until we figure this out for good, that little micro cpu monitor. App is sweet for peace of mind to know all is well or whether a reboot is needed. For what it's worth, I also noticed that after the event, that my auto rotate to landscape was mysteriously unchecked?
If it jams again, I'll have to see if it gets unchecked again, unknown if there is a relation.

dansushi said:
I'm having a problem with my Samsung Galaxy S3 (rooted, but no custom ROM) through AT&T where it's losing battery power at a much higher rate than normal every once in a while.
Specifically, today, I was using the GPS feature and charging it in my car, and yet, even though it said it was charging, the battery continued to lose charge. Also, in the past, the phone has lost charge very quickly, and when I check the battery usage, "Android System" is very high on the list, up to 60% (with "Screen" being at 11%, which is usually the biggest culprit for me since I leave the screen on a lot). One time, I went to bed at around midnight and had forgotten to plug in my phone. When I woke up it was off. I turned it back on and looked at the battery stats using 3c's Battery Monitor Widget and saw that it lost charge quite slowly until about 5am, when suddenly the usage went up dramatically, and the phone went from about 60% to 0% in the course of an hour and a half of non-use.
Because this is not a problem I can reproduce on command, I'm not sure exactly what application/process is causing it. Does anyone have any suggestions or has anyone else experienced things like this happening before? (Besides me having to pay for the "betterbatterystats" app?)
Edit: Also, "Android System" sometimes is sometimes listed as "gsiff_daemon" in the battery stats, and within 3c's Battery Monitor Widget, Android System is separate from "gsiff_daemon", where gsiff_daemon's usage is almost 15 times the usage of Android System.
Click to expand...
Click to collapse
That happened to me too. But for me, flashing another rom fixed it.
Sent from my SAMSUNG-SGH-I747 using xda premium

Thread hijack! Lol. Anyways. Is cell standby supposed to use up a crap load of battery too?
Sent from my SAMSUNG-SGH-I747 using xda premium

Swaggernaut said:
Thread hijack! Lol. Anyways. Is cell standby supposed to use up a crap load of battery too?
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
No there is a cwm flashable fix floating around here for that
Galaxy SIII via XDA premium

do any of you guys have the "increase volume in pocket" setting on in phone-->settings?
also do any of you have motion settings enabled and/or autorotation on?
Seems it has to do with the gyro issue
also are you guys rooted or non-rooted?

Contact sync?
i noticed this today and while troubleshooting, noticed contact sync from google says "sync is currently experiencing problems..." maybe?

dansushi said:
I'm having a problem with my Samsung Galaxy S3 (rooted, but no custom ROM) through AT&T where it's losing battery power at a much higher rate than normal every once in a while.
Specifically, today, I was using the GPS feature and charging it in my car, and yet, even though it said it was charging, the battery continued to lose charge. Also, in the past, the phone has lost charge very quickly, and when I check the battery usage, "Android System" is very high on the list, up to 60% (with "Screen" being at 11%, which is usually the biggest culprit for me since I leave the screen on a lot). One time, I went to bed at around midnight and had forgotten to plug in my phone. When I woke up it was off. I turned it back on and looked at the battery stats using 3c's Battery Monitor Widget and saw that it lost charge quite slowly until about 5am, when suddenly the usage went up dramatically, and the phone went from about 60% to 0% in the course of an hour and a half of non-use.
Because this is not a problem I can reproduce on command, I'm not sure exactly what application/process is causing it. Does anyone have any suggestions or has anyone else experienced things like this happening before? (Besides me having to pay for the "betterbatterystats" app?)
Edit: Also, "Android System" sometimes is sometimes listed as "gsiff_daemon" in the battery stats, and within 3c's Battery Monitor Widget, Android System is separate from "gsiff_daemon", where gsiff_daemon's usage is almost 15 times the usage of Android System.
Click to expand...
Click to collapse
I read the thread about gsiff_daemon culprit. I had it listed as a possible battery drain culprit. The thread says the issue may happen after a hot reboot...which I did have. Killing gsiff_daemon was not immediately effective. I renamed the file so it wouldn't get used...like the thread recommended. I had to reboot to get normal battery drain back and have yet to see the issue again. But i wont know for some time...or maybe when/if i get a hot reboot...which is really rare. Do yourself a favor, and buy better battery stats. Its a must have tool...and it's not expensive.

I wonder if this problem has been solved with latest lj7 jellybean from sprint
Sent from my SPH-L710 using xda app-developers app

so with some trial and error i found some resolutions ..
first, i used Watchdog and it told me that the media services is killing battery too.
so doing a full wipe does not always fix this.. but what does, is reboot and wait about 1 hour charging and it will calm down. this was just something i noticed. so what i did is wipe out my SD cards, both of them, cleared them out 100% formatted the External SD, and used recovery to format the internal. From there it seem to work, i put my stuff back, and it seems ok.
problem is, when you install a lot of rom's and have bad reboots some files get messed up and you have to do it all over again..
problem was with AOPK, CM and TW roms.

eatonjb said:
so with some trial and error i found some resolutions ..
first, i used Watchdog and it told me that the media services is killing battery too.
so doing a full wipe does not always fix this.. but what does, is reboot and wait about 1 hour charging and it will calm down. this was just something i noticed. so what i did is wipe out my SD cards, both of them, cleared them out 100% formatted the External SD, and used recovery to format the internal. From there it seem to work, i put my stuff back, and it seems ok.
problem is, when you install a lot of rom's and have bad reboots some files get messed up and you have to do it all over again..
problem was with AOPK, CM and TW roms.
Click to expand...
Click to collapse
My experience with froyo/gb/ics is that things have been getting progressively better over the years. But with each so called UPGRADE of an OS or even APPS, we often have to deal with bugs or incompatibilities. I am eager to upgrade to a stock based JB soon, but wisdom says, for 20 things improved, there will be 5 things broken....or hurting in some way. Early adopters suffer the most as usually these issues get ironed out...most of them.
BUT...these stuck drains...wake locks etc., it seems they will happen when they do no matter how many issues get fixed. Over the years, I've had random standby drains caused by Maps/Nav. Maybe it's ok for months, then after a particular update, it's back...and unpredictable. The YES...a reboot, just like with a PC, is a quick short term workaround.
Finally, with the App CURRENT WIDGET, there is a provision to watch for high drain in standby. It watches MilliAmp (ma) readings over time..to determine if you have a rogue drain. That's different than monitoring the CPU. (Some drains do not cause much CPU activity) BUT UNFORTUNATELY, that app won't work with our S3's because of a lack of hardware support. Works great with HTC and many others. It's a bummer because I used to use it and have my HD2 reboot if a 15min consecutive high drain was recorded in standby....thereby saving the battery and usually killing the bug.

Crapppp
Jellybean didn’t solve it. Gsiff_daemon just popped up for me. Just renamed it AGAIN.
Hopefully it won't pop up again
Sent from my SPH-L710 using xda app-developers app

[Q] S3 Battery Drain after Jelly Bean

So I searched all day for an answer similar to mine and I did not see what I could do.
I was on rooted on ICS until this weekend when I updated to Jelly Bean and rooted again.
My Battery usage was working fine in ICS, what I would call normal battery drain.
After the update I am getting terrible battery use!!!!
I have tried closing, diabling all apps, radios, I have diabled bloatware.
But my battery keeps draining at a rate of 10% and hour!
All this with minor use.
I have opened a few apps and the Play Store but nothing else.
The S3 has just be inJust in standby.
In the settings, under battery it show my main power consumption is the SCREEN at 60%
I dont know how!
When the screen is off, I dont have a video wallaper and when I do power up the screen its so DIM I can hardley see anything.
All this happened after the Jelly Bean update!
Any idea on what I can do?
Do you think a factor restore would help?

Yes, back your dat up first though (contacts, calender, ect.) because you will have to redownload your apps. I did a reset and was on stock after updating but still had terrible battery life. The fix? Take the battery out 40 minutes, put it back in and run it COMPLETELY dead, and recharge it while it's turned off. Make sure you have time to do this without needing the phone because it takes a while. Like 7-8 hours. I've went a day now without much usage at all (still at 90% charge) and have a day left on standby. The battery reset helped more than anything I believe.

Yep same as mine jb update has a heavy battery drain..and my skyvalex callrecorder stopped working..i just flash back to ICS.
Sent from my SAMSUNG-SGH-I747 using xda premium

My opinion, factory wipe and Re-root it.
Install SetCPU and the Ktoonsez kernal to manage the power settings. Also Go Power Master is a good app to tweak power settings.
In SetCPU you can have it clocked down when the screen it off.

Had the same problem. Called att went through the ranks until I was told by att warranty supervisor that they had no work around and I should root my phone. Shocking they told me that. But I found the problem. I uninstalled the update to Google now and then shut it down. Battery seams to be doing good now.
Got a free battery from att though. I guess cause there higher ups have no idea how to fix drain.
Sent from my SAMSUNG-SGH-I747 using xda premium

Luckily your type of phone has a removable battery....unlike me...cannot replace to a higher battery capacity
Sent from my MT27i using xda premium

Semi-solved
I somewhat have solved my problem.
What I did was Factory Reset from the Setting menu. I thought I would have lost Root doing this.
It was already set in my mind to just wipe the S3 clean and start over but the root did not get washed out.
So, I used Kies to only restore my contacts.
Instead of having any old apps restored I downloaded them all over again from the Play Store.
So far so good!!
I have better battery life than prior to the reset.
I had been losing 8% and hour in Standby and 10%+ when in use.
So far today I have used the phone with my screen brightness high, made about 10 calls, surfed youtube and I only down 6% in the last 2 hours.
I consider that better.
If there are some things I can add to my diable list that you all know of to give me an EVEN BETTER result please let me know!

Poor battery life here too. Battery settings says screen is eating 78% and Maps eating 10%. I'm a heavy user but its mostly surfing this site and Facebook. I don't play games or watch YouTube much

Does this solve the battery drain issue?
Hiya all.
I haven't got a S3 so I can't confirm this works.....
A friend was having the same battery drain issue and I was going through his settings and noticed that "Sync All" was on.
Turned it off and the battery drain stopped. We think.
It seems to easy to be true. So I'd like more S3 owners to try.

Archienj7 said:
Yes, back your dat up first though (contacts, calender, ect.) because you will have to redownload your apps. I did a reset and was on stock after updating but still had terrible battery life. The fix? Take the battery out 40 minutes, put it back in and run it COMPLETELY dead, and recharge it while it's turned off. Make sure you have time to do this without needing the phone because it takes a while. Like 7-8 hours. I've went a day now without much usage at all (still at 90% charge) and have a day left on standby. The battery reset helped more than anything I believe.
Click to expand...
Click to collapse
Hi have the lte version that i got couple of days back and i have the same problem. I have not rooted and it came stock with jb. So you have to do a factory reset and remove the battery and try or just the battery?
Also how to remove some stock apps, I don't use any.

My battery life stinks. I had to get the Mophie case with extra battery built in. works great

battery draining too fast new or old

im on a stock rom not rooted and new battery and old battery both discharge really fast. Totally dead in 5-6hrs light use. Im guessing there is a hardware issue with the phone as this isnt normal. Any ideas?
lets see I did a factory reset after Jellybean update
changed the battery for a new one
biggest power drain is showing up as screen 33-39%
I have the thing on power saving mode and mobile data I turn off when not in use.
only thing I can think of that I didnt try is flashing another radio. But I doubt thats it because ive put it in airplane mode and it still looses power fast.

craig198 said:
im on a stock rom not rooted and new battery and old battery both discharge really fast. Totally dead in 5-6hrs light use. Im guessing there is a hardware issue with the phone as this isnt normal. Any ideas?
lets see I did a factory reset after Jellybean update
changed the battery for a new one
biggest power drain is showing up as screen 33-39%
I have the thing on power saving mode and mobile data I turn off when not in use.
only thing I can think of that I didnt try is flashing another radio. But I doubt thats it because ive put it in airplane mode and it still looses power fast.
Click to expand...
Click to collapse
Get Better Battery Stats and check your wake locks. A lot of information in that thread. Might have a rogue app draining you.
Edit: also screen on is always going to be your biggest drain. Keep brightness down as much as you can. App called screen filter is good for achieving lower brightness than system allows. You could try the ktoonsz kernel, undervolted as well. Turning off sounds in settings (key press, vibrate, etc as well). Toggle data and WiFi when not using. These are just some basic suggestions.
Sent from my cracked out SGS3

This is my second s3 and the first one never had a problem going 10-12 hrs normal use. Im thinking it is a hardware issue as I did a factory reset and it still persists on fast draining.
Edit.. I just disable google talk maybe that was causing it?

It's not Google Talk. Check your battery and it'll show you what's drainage ng it the most. Also check screen brightness
Sent from my GT-I9300 using xda premium

Benconquerer said:
It's not Google Talk. Check your battery and it'll show you what's drainage ng it the most. Also check screen brightness
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
well after the screen 40% we have android OS @ lower 30%

Do you have an SD-Card in?
I was getting the same battery life, took out my SD-Card, and I'm getting 7 hours on screen time with stock battery.

andybones said:
Do you have an SD-Card in?
I was getting the same battery life, took out my SD-Card, and I'm getting 7 hours on screen time with stock battery.
Click to expand...
Click to collapse
lol sd card?? well I tried it anyway and no, it still drains like a pissing racehorse. Ive noticed this phone gets pretty warm sometimes even with light use. Im not sure what is causing this but must be a factor in why the battery life is so poor. When I talk on phone, not very often, the ear piece actually gets hot. Im gonna send this puppy to samsung and see what they can do.

GSam Battery Monitor can offer better details about your battery usage, including wakelocks, cpu usage, etc.. It's more detailed than what Android offers.
I'd also recommend using an AOSP based rom as they include out any carrier/Samsung services that may adversely affect your battery life, particularly in a fringe coverage area or with many sync and push items. I'd also stay away from powersave mode for the time being.
If you want to know for sure, I'd do something like this:
- update PRL on current rom
- wipe and format everything in CWM
- flash rom as per developer suggestions
- wipe battery stats
- boot and do not sign in with your Google account (very important!)
- do not install or restore any apps
- turn off auto-sync and leave data on
- enable auto brightness
- confirm that phone signal is somewhere between -50 and -90dbm
- turn off phone and charge overnight
- turn on in the morning and use normally for the day
- install GSAM if issues persist
Please post back with updates.

It could be a hardware problem also you know.... if something ground off in the phone then the battery will drain faster than anything....I had a n96 with a grounded problem and it use to dead in 4 hrs....

[Q] Battery Charging Issues.

Okay, I currently run CM10, about a week ago I flashed another developers version of CM10, and started having battery percentage reporting issues while charging, So I flashed back to the original ROM, formatted, cleaned battery stats and for some reason the battery will charge up to like 75-80% and stop reporting the correct percentage until I reboot the phone, even when back on the old ROM, I am using simonssimons34 ION kernel, which running it before with the old ROM, reported fine, so I don't think it has anything to do with the kernel.
I have almost always let this battery deplete to about 1-2% before a charge, and never over charged it, so I am a little annoyed that my battery stats are mis-reporting now until I reboot. Is there any fix for this? Or do I need to try another ROM or something? It only reports incorrectly while recharging, it depletes normally and never has issues with that.

This happens to me every day. Learn to live with it.
Sent from my HTC One V using xda app-developers app

You can clear battery stats in recovery. There's also a few root apps that let you do this. (search for clear battery stats)
It'll take a while for it to rebuild accurate battery stats, but it sounds like at the moment any fresh stats is better than what you have now.

You can try calibrate with this app:
https://play.google.com/store/apps/details?id=com.nema.batterycalibration
Sent from my One V using xda premium

I've laready tried as both of you have suggested before, and it hasn't helped me yet, I did it two ways I did battery wipe in recovery, and through a 3rd party app, but the phone still wants to stop reporting the correct percentage until I reboot my phone.
And I even tried letting hte phone completely deplete after wiping battery stats, and it's still wonky ='(.

Ugh this is soooo annoying ffs, anyone ever had any luck on fixing this issue? I've tried:
Flashing two different ROM's, nothing
Charging, rebooting wiping stats, calibrating, draining to 0, rebooting, nothing
Using calibration apps
None of this has worked for me what so ever, the only thing that seems to work is rebooting after the phone has stopped reporting then it will show 99% then charged.
What I don't get is it will charge to 100% if the phones off, but if it's on the phone reports an incorrect percentage, wth?
I am about to try a full RUU reflash and see if that will fix it, but that's a last resort. HELP PLEASE!

FreakyFreakGA said:
Ugh this is soooo annoying ffs, anyone ever had any luck on fixing this issue? I've tried:
Flashing two different ROM's, nothing
Charging, rebooting wiping stats, calibrating, draining to 0, rebooting, nothing
Using calibration apps
None of this has worked for me what so ever, the only thing that seems to work is rebooting after the phone has stopped reporting then it will show 99% then charged.
What I don't get is it will charge to 100% if the phones off, but if it's on the phone reports an incorrect percentage, wth?
I am about to try a full RUU reflash and see if that will fix it, but that's a last resort. HELP PLEASE!
Click to expand...
Click to collapse
Try this: http://forum.xda-developers.com/showthread.php?t=1947559
It gave, at least to MY hov, the right percentage...

Cyanogenmod 10.1 terrible battery life

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 ???