Related
Hello all,
I first posted this in Q&A on the home forum. There doesn't seem to be any interest so I thought I'd post it here again. Below is what I wrote on the original post.
"If you’ve been supremely annoyed with the AOS bug like I have , here’s some interesting information I’ve found (Did a search and it appears no one else has found this yet). It’s a paper written (in 2010)by Rafael J. Wysocki which touches deep into the subject. What I hope is that it will help some developers understand this bug and ultimately integrate a work around / fix as soon as possible. Hopefully this will help some users understand what is going on with their phones as well.
I have and Epic 4g Touch and all the ROMS I’ve tried have this bug but according to the article, looks like a kernel problem. My suspend / events/0 processes runs for a long time, eating up cpu and I don’t have it as bad as some people but thought it's worth mentioning.
Basically what I get from the paper is that…
1. The suspend (and by association the events/0 process) process is Google’s implementation of a power management system, an add on to the Linux Kernel
2. That the wakelock / suspend feature is , to make a long story short , not working the way it’s supposed to.
3. “Poorly” written apps, or apps that are written without the inner workings of how suspend /wakelocks work, will trigger this bug. This can be ANYTHING.
4. Supposedly, kernel version 2.6.37 will fix this. The Epic 4g Touch kernels are all .35 as far as I know which explains the fact that so many Epic 4g Touch owners complain about this.
Would love for the smarter than me people to give their take on this?
Since this is my first post, it won't let me post a link. Do a google search for Rafael Wysocki suspend_blockers.pdf and it should be the first link that shows up."
Hopefully there's more interest here!
http://systemsens.cens.ucla.edu/~cs219/lectures/Suspend-Blockers.pdf
sent from the near past
Danial, thanks for the reply. Not sure if it was intentional but that's not the document I was referring to. However it looks like useful info and simplifies some of the explanations and even uses the the document written by Wysocki as a reference so thanks for that.
Bump! for battery life lovers!!!
how do I check to see if this bug is causing battery drain on my phone. thanks!
Sent from my SPH-D710 using Tapatalk
pcmanager said:
how do I check to see if this bug is causing battery drain on my phone. thanks!
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
If you go to Settings, About Phone, Battery usage, you'll see "Android OS" take an unusal amount of battery time. Mine varies from 25-80%, some others I've read, consistently get 80%. You should be running on battery for a while before you check this since if you've only been on battery for a few hours, that stats may be misleading.
A more precise way is also to download the free Battery monitor Widget, and in the statistics section, you'll see the processes "suspend" and "events/0" take hours of usage when it shouldn't. You also may see *wakelock* take up hours of time.
Some dwho have it bad, download watchdog, and monitor on the fly, which processes go over a certain amount of % usage. If your batter drains quickly, suggest this route to confirm its suspend and events/0.
thanks for all those great infos. my android os is usually under 10 percent after several hours of use so I don't think that is buggin me. Could you explain exactly what a wakelock is? I know I could use the search button but the info you provide here in this thread might help a lot of other people trying to resolve battery drainage issues. Thanks!
Sent from my SPH-D710 using Tapatalk
saejin2000 said:
Hello all,
Since this is my first post, it won't let me post a link. Do a google search for Rafael Wysocki suspend_blockers.pdf and it should be the first link that shows up."
Click to expand...
Click to collapse
I'm assuming you were talking about this site, which was the second search result:
http://lwn.net/images/pdf/suspend_blockers.pdf
As a side note, my Android OS is at 7% of my battery usage right now.
faceyourfaces said:
I'm assuming you were talking about this site, which was the second search result:
http://lwn.net/images/pdf/suspend_blockers.pdf
As a side note, my Android OS is at 7% of my battery usage right now.
Click to expand...
Click to collapse
May I ask,
1. How long your phone is on battery for?
2. Kernel Version?
3. ROM?
Would love to be @ 7% for Android OS!
1. How long on battery 1:15
2. Kernel Version EL29
3. ROM StrongSteve blue, Odex
4. Android OS 3%
I will let you know what the OS % is at the end of the day before the battery dies ......
Would love to be @ 7% for Android OS![/QUOTE]
Sent from my SPH-D710 using Tapatalk
pcmanager said:
thanks for all those great infos. my android os is usually under 10 percent after several hours of use so I don't think that is buggin me. Could you explain exactly what a wakelock is? I know I could use the search button but the info you provide here in this thread might help a lot of other people trying to resolve battery drainage issues. Thanks!
Sent from my SPH-D710 using Tapatalk
Click to expand...
Click to collapse
A wakelock is, as I understand it, a process in the Android kernel that temporarily tells the Android device to hold off sleeping (stop the suspend process).
This allows for a process , application or device (such as your wi fi antenna) to turn back on and do what it needs to do. The suspend process is suppose to tell the phone to go back to sleep but with this bug, either or can get stuck and therefore use up more cpu that it's supposed to.
pcmanager said:
1. How long on battery 1:15
2. Kernel Version EL29
3. ROM StrongSteve blue, Odex
4. Android OS 3%
I will let you know what the OS % is at the end of the day before the battery dies ......
Would love to be @ 7% for Android OS!
Click to expand...
Click to collapse
Sent from my SPH-D710 using Tapatalk[/QUOTE]
Interesting, I'm on EL29, have used Strong Steve's ROM but it still persists for me. Next thing I will try is to install Steve's ROM only, no additional apps.
I've gotten 2 days , 9 hours battery life (on light use, about 3 hours screen time, lowest setting) my last round but I've Juice Defender configured it to heck and undervolted as well. I think if I figure out what app may be contributing to this I just may get 3 days, may be 4 days battery life.
thanks for the info!
EOD report...
1. How long on battery 1:15
2. Kernel Version EL29
3. ROM StrongSteve blue, Odex
4. Android OS 3%
1. How long on battery 9:24
2. Kernel Version EL29
3. ROM StrongSteve blue, Odex
4. Android OS 21%
5. Display on 2:09
6. Percent battery left 29%
Not a great day for battery stats but i did change my modem from ek02 to el29 last night trying to solve a gmail keeps sending issue i am having. Last time i was on el29 it seemed to consume more juice so i switched back to eko2.
So i have system updates always running. When I go to try and update PRL and firmware etc, it gives me an error. I assume I need to re-flash a stock ROM, then update? I wonder if my problem is this: My used my phone for a few weeks, then ported over a new number. Under phone info, it still shows the original number. It uses the original number for a hotspot confirmation. But my phone clearly has a new number. Is this need for the phone to update causing the battery drain?
gk325 said:
So i have system updates always running. When I go to try and update PRL and firmware etc, it gives me an error. I assume I need to re-flash a stock ROM, then update? I wonder if my problem is this: My used my phone for a few weeks, then ported over a new number. Under phone info, it still shows the original number. It uses the original number for a hotspot confirmation. But my phone clearly has a new number. Is this need for the phone to update causing the battery drain?
Click to expand...
Click to collapse
PRL's (and profiles) should update despite having a custom ROM. Firmware won't however.
I think it's unlikely that the fact you can't update is causing a battery drain. To be sure, you need to find out which process the phone uses to do updates and see if they are taking up alot of CPU (OS monitor or battery monitor widget will help you with CPU usage.)
I think you simply have the OS bug like the rest of us.
pcmanager said:
EOD report...
1. How long on battery 1:15
2. Kernel Version EL29
3. ROM StrongSteve blue, Odex
4. Android OS 3%
1. How long on battery 9:24
2. Kernel Version EL29
3. ROM StrongSteve blue, Odex
4. Android OS 21%
5. Display on 2:09
6. Percent battery left 29%
Not a great day for battery stats but i did change my modem from ek02 to el29 last night trying to solve a gmail keeps sending issue i am having. Last time i was on el29 it seemed to consume more juice so i switched back to eko2.
Click to expand...
Click to collapse
Yeah your battery life is dismal but the Android OS percentage is not nearly what I would expect it to be if the bug was causing this.
I would at least try a free battery saving app if you haven't already. You could probably get a few extra hours out of it.
Might want to turn 4g off also and see how much more mattery life you get.
A bit dated of a post, but most if not all still relevant. We have a lot of non-TW ROMs for this phone which sacrifice battery life for improved functionality, not by choice, but mainly because Samsung's lack of GPL compliance with regards to sharing kernel sources. Our community devs have done an incredible amount of work with their kernel forks, but Samsung's paid development teams obviously have a lot more time and incentive to work on it, and as such our community devs' graciously find even more fixes once source drops, then merge them into the community kernels we're all using. So as we wait in limbo for them to share their JB kernel contributions to our community:
Anyone that wants to add anything to the list, post to the thread and I'll keep collecting.
Workarounds for D710 battery drainers:
battery saver scripts:rmikulus found this sweet piece of development gold: if you know how to run scripts,"Die Hard Battery Calibrator" will calibrate your battery in only about 20 minutes (must be plugged in that entire time)
Probably better to use the latest and greatest here instead, much easier to install, just a simple CWM zip AIO scripts:
Jelly Bean Tweak Pack for Epic 4G Touch Fixes Various Errors
--appears to help battery life and other various issues.
Voodoo LOUDER (paid) supercurio - Project Voodoo
--not battery-related, probably causing opposite effect actually, but many find an issue with headphone audio being maxed out at lower dB than desired. I'll confirm this works on CM10 nightlies.
WiFi : Turn it off when not in use, just like anything else. Tasker does a great job of automating this process.
raise the network scan interval to reduce background wifi radio usage (Rom Toolbox allows build.prop tweaks such as this,)
change the sleep policy for the wifi to Never While Charging to allow wifi connection to die when phone is off (toggle is in the touchkey menu while viewing wifi settings.)
NOTE: WiFi is a more desirable data connection than 4G as far as batt life is concerned. 4G is auto disabled when wifi is on for most ROMs. 4G (WiMax) is a new technology that still has yet to be perfected, not unlike these latest developments in ICS.
4G Radio: Also turn off when not in use. Use the latest modems available. Note that modems won'tt install from ODIN/mODIN flashes, gotta use CWM zip installs.
Haptic Feedback: Turn off haptic feedback, vibration kills. (Particular to CM9 ROM, haptic is set too strong right now, TouchWiz-based ROMs are fine, but if you can live w/o it...)
LED notifications: Another wakelock offender. Turn them off for now, it's one of the reasons the device stays awake when it should be sleeping. Sleep is good.
Get BetterBattery Stats by chamonix : Take a look at it after a long period of uptime without restarting (quick or full) to allow a greater set of data to parse into stats. Some apps you use may be eating away at your battery from the background. Spare Parts Plus and it's root-friendly brother BladeBuddy is also valuable.
Use the latest kernels available. If you're flashing CM nightlies, you're good to go, kernel modifications are updated in the same process.
Touch sounds and screen lock sound: These still cause partial wakelocks , leading to some amount of battery drain. System Settings>Sound menu to turn these off for now. (thx coiledwire)
The CM9 Team put together a similar list with a few things not listed here. Check the 'Power Saving Options' section on the CM9 Blog
----
Android-specific:
BatteryStats.Bin This little file keeps a record of your battery usage, power amperage, etc. and every time you flash a rom, it gets wiped. The system's ability to track the exact power level of your battery is DIRECTLY dependent on this file, so if you don't allow the newly flashed system a few days to calculate averages over time, it won't really have time to realize how charged it really is. NOTE: this file has NOTHING to do with improving battery life, only calculating what the battery % shows in the statusbar (and in the battery statistics charts in the system settings menus.) I've sat at 5% battery life for an entire hour with screen on surfing the 'net. No way it was really 5% that entire time.
While wiping battery stats won't increase battery life, it will improve the calculation of the charge, if done properly. Stats are saved in /data, when a ROM is installed, initially the stats will not have much data to extrapolate from, and the battery probably isn't entirely full to begin with, therefore making a mess of a new ROM's recognition of the cell's true charge. It's best to wipe stats when your charge is above 4180mV (E4GT stock battery size.) I've seen mine as high as 4202mV. Also, if you've got aftermarket cells that aren't the same mAH rating, the results will be slightly wonky. Battery Calibration app can set a reminder to flush the battery stat counter file when the phone is charged, if you need to charge with your device on.
I notice that flashing roms with a battery @100% and charging will help in this regard, then once the system is fully booted, unplug it and drain it to 15%, then charge to 100%, then do :
Bump Charging is suggested by HTC developers to potentially DOUBLE your battery life.
Battery Tuning: We're running Lithium Ion batteries. Don't kill it to 0%. Ever. Tip: Condition your new cell phone’s battery to make it last longer (but be sure to condition it properly)
Live Wallpapers and other background services: If you can live without them, turn off the services. Many common apps trigger network connections on a periodic schedule, further causing drain. increase sync periods, or just sync manually.
Sync: Yet another form of background services. If your sync is running all the time from frequent emails, gvoice msgs. etc... and the like, try turning off some of your heavier data tranx and refreshing manually when you need it.
Again, please tack on posts for this thread if you have good additions to make, I'm just trying to collect a one-stop shop of battery life savers, and a place to point newbs when they start trainwrecking dev threads with questions about it. This is my humble way of giving back cuz I was one at one point.
Thanks, some of these tips most users may know but the one that helpped me was the notification light when running cm9! I worked 10 hours a day and cant use my phone but my battery was draining like crazy! Much better!
Solid advice. I do everything mentioned here. I also throw in a bump charge to finish it off..old habits die hard
Sent from my SPH-D710 using Xparent Blue Tapatalk 2
so is bump charging still a valid method? I've read that HTC developers suggest it, but you're saying old habits so I'm assuming you're aware of something about it.
[url="http://forum.xda-developers.com/showpost.php?p=25060053&postcount=1] Bump Charging [/url]
Dudebowski said:
so is bump charging still a valid method? I've read that HTC developers suggest it, but you're saying old habits so I'm assuming you're aware of something about it.
[url="http://forum.xda-developers.com/showpost.php?p=25060053&postcount=1] Bump Charging [/url]
Click to expand...
Click to collapse
Well, its just my routine. I charge to full, power down charge to full, unplug, power on, plug back in. When. I open Battery Calibration app, if battery shows 100% but only like 4110mV instead of 4180mV+ I will unplug and plug back in a minute later then wipe stats when it shows anything over 4175mV and 100% charge...confusing enough?! Lol
Sent from either ET4G or NS4G using Xparent Tapatalk 2
Thanks For the Guide.
I was really dissapointed with ICS.
I was still running EL29- Rooted and was running everyday on 14hrs with Wi-Fi always on. so after seeing that most bugs were fixed on FD24 i updated and yesterday i was running on 5hrs tops with Wi-Fi on.
So i did some suggested tweaks.
Wi-Fi off.( only ON when i need it)
GPS- I unchecked the last to option on the location.
Adjust haptic
uncheck some Sync from Google.
by the way what's? "Internet Sync"
and now.... im at 66% after 7hrs of being unplugged.
Internet sync meaning anything that may transfer data in the background like google talk, weather apps, Skype, etc.
Glad to hear those stats ! Take a screen Cap of the battery stats when it gets below 10% and post here
Sent from my SPH-D710 using XDA
Dudebowski said:
We're currently in a lull period between development phases now that ICS is blowing up all of our E4GT's. Samsung's kernels leave a lot to be desired, hence the current work towards a proper aftermarket kernel. ICS roms are very new, especially the custom ones going on in the dev kitchen right now. Software level ROM coding is one thing, the devs will get that fixed, but ultimately they're dependent on a solid kernel... and one of the biggest problems with the kernel, is that ever-elusive battery life.
so:
God-Tier devs, correct me if I'm wrong, and please add your thoughts, additions, and suggestions below. I'll try to keep a live OP post for a universal E4GT battery tweak guide.
Things that eat up our E4GT battery for now, with workarounds:
WiFi : Turn it off when not in use
raise the network scan interval (Rom Toolbox allows build.prop tweaks such as this,)
change the sleep policy for the wifi to Never While Charging to allow wifi connection to die when phone is off (in spare parts).
NOTE: WiFi is a more desirable data connection than 4G as far as batt life is concerned. 4G is auto disabled when wifi is on for most ROMs.
4G: Also turn off when not in use. Use the latest modems available. Flash with odin/mobileOdin because the CWM flashables sometimes don't stick.
Haptic Feedback: Turn off haptic feedback, vibration kills. (Particular to CM9 ROM, haptic is set too strong right now, TouchWiz-based ROMs are fine, but if you can live w/o it...)
LED notifications: Another wakelock offender. Turn them off for now, it's one of the reasons the device stays awake when it should be sleeping. Sleep is good.
Get BetterBattery Stats by chamonix : Take a look at it after a long period of uptime without restarting (quick or full) to allow a greater set of data to parse into stats. Some apps you use may be eating away at your battery from the background. Spare Parts Plus and it's root-friendly brother BladeBuddy is also valuable.
Suggestion, with disclaimer: Use the latest stock or Rogue kernels and modems. sfhub keeps the most updated modem D/L list . Don't forget that you should not flash ANYTHING from ICS kernel/recoveries yet!!! There are known issues with these kernels, and every last one of them is a beta stage leak from samsung along with a custom recovery and some little tweaks to work with the various ICS roms. The flashing HAS bricked MANY phones! There will be great fanfare and notices from the developer teams once we have an ICS kernel that works. It's mostly dependent on Samsung releasing sourcecode, although there are some teams working on porting the source of the other Galaxy II's... the race is on!
Touch sounds and screen lock sound: These currently cause partial wakelocks in Galaxy S2 ICS ROMs , leading to some amount of battery drain. System Settings>Sound menu to turn these off for now. (thx coiledwire)
----
Universally true:
Live Wallpapers: If you can live without electricsheep or the other various animated wallpapers, do so. I can't
Battery Tuning: If you didn't condition your battery when you first got it, good luck. In any event, try to condition it from here on out by burning it out completely (phone won't boot with it) then charge 100%, keep it off charge until it dies again, CWM Wipe Battery Stats, run the battery down again without charge. Repeat the charge/kill cycle a couple times. New kernel or ROM? Start from scratch again. Battery stats are saved in /data, so old stats can mess with a new ROM's recognition of the cell's true charge. Also, if you've got aftermarket cells that aren't the same mAH, you'll only get as good a conditioning as the weakest battery can take. Battery Calibration app can set a reminder to flush the battery stat counter file when the phone is charged, if you need to charge with your device on.
Sync: If your sync is running all the time from frequent emails, gvoice msgs. etc... and the like, try turning off some of your heavier data tranx and refreshing manually when you need it.
EDIT:
Darchstar and the CM9 Team put together a similar list with a few things not listed above. Check the 'Power Saving Options' section on the [url="http://e4gtcm.blogspot.com/p/customization-guide.html] CM9 Blog[/url]
I've also since learned that wiping battery stats does nothing with prolonging battery life. There's numerous articles quoting official Google/Android developers where they explain this flat out It may help your system recognize the true percentage of your charge, but that's about it.
[url="http://forum.xda-developers.com/showpost.php?p=25060053&postcount=1]Bump Charging[/url] is suggested by HTC developers to potentially DOUBLE your battery life.
Click to expand...
Click to collapse
Links in your edit post dont seem to work.
I've found that taking the wifi frequency band off of auto and changing to your desired frequency helped my battery when Im on wifi and the phone is sleeping
Sent from my SPH-D710 using XDA
Dudebowski said:
Internet sync meaning anything that may transfer data in the background like google talk, weather apps, Skype, etc.
Glad to hear those stats ! Take a screen Cap of the battery stats when it gets below 10% and post here
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Ok here are my screencapture for FD24.
I just updated to FD26 using NoData It looks like preserve all my settings so I'm gonna give it a shot tomorrow , I will report back.
CM9 when you finally get phone to sleep nice and soundly
....or just stick with GB roms that work and stop suffering yourself these ICS leaks.
Some of us have flash addiction. Some of us enjoy bring Guinea pigs for development. I for one just left my last phone running cm7 and couldn't bear the austerities of a stock ROM. The GB twiz hacks are alright, but it doesn't feel like home to me.
Sent from my SPH-D710 using XDA
A few of us are actually doing better with battery on ICS. One problem is that we get so many leaks and ROMs that the battery might not be having a chance to settle
Sent from my SPH-D710 using Xparent Blue Tapatalk 2
Beejis said:
Links in your edit post dont seem to work.
Click to expand...
Click to collapse
*fix'd.
im0rtalz said:
CM9 when you finally get phone to sleep nice and soundly
Click to expand...
Click to collapse
w00t w00t!
I get pretty good battery on AOKP:
Good thread, thanks for the tips.
Transmission sent from my slim n trim Galaxy S II.
Agree with just about everything. One thing that I disagree with is letting your battery die at all. It actually decreases the life of the battery in lithium ion batteries. Its an old school method for old batteries. Try never going under 15% if possible. Everything else is correct as far as I can tell.
Sent from my SPH-D710 using xda premium
On the topic of battery calibration, if you know how to run scripts, the creator of V6 Supercharger and 3G Turbocharger scripts has also created "Die Hard Battery Calibrator" which will calibrate your battery in only about 20 minutes (must be plugged in that entire time)
http://forum.xda-developers.com/showpost.php?p=18703418&postcount=5021
LordLugard said:
....or just stick with GB roms that work and stop suffering yourself these ICS leaks.
Click to expand...
Click to collapse
What he said
Sent from my SPH-D710 using XDA
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
Hi,
I follow the forums here for years but have not posted yet, hence not allowed to post on the dev forum in the appropriate thread, had to open a new one
A couple of days ago I installed "[ROM][JB][4.3.1][JLS36I] CyanogenMod 10.2 Alpha (Build 3)" on my wife's phone. Until then she was still using the stock GingerBread ROM. The phone got so slow to the point of not being usable at all.
After I flashed to CM 10.2 it feels like a new phone. Lightning fast, good looks, everything works - fantastic, very much appreciated and thank you very much @ Devs!!! :good::good::good:
One big problem though:
When running the stock ROM the battery usually lasted about 2 days. Now, with CM10.2 it is empty after half a day. Since I did a full wipe before she is using less Apps as compared to before and there is no single big consumer. Just the typical mail apps, facebook etc.
When I look at the wakelocks there is one app consuming most CPU which is CSipSimple. But that app was also running before the upgrade when the battery lasted 2 days.
The screen seems to consume more power though, is that possible? Anyone else with similar experiences?
Thank you very much!
nuukee said:
Hi,
I follow the forums here for years but have not posted yet, hence not allowed to post on the dev forum in the appropriate thread, had to open a new one
A couple of days ago I installed "[ROM][JB][4.3.1][JLS36I] CyanogenMod 10.2 Alpha (Build 3)" on my wife's phone. Until then she was still using the stock GingerBread ROM. The phone got so slow to the point of not being usable at all.
After I flashed to CM 10.2 it feels like a new phone. Lightning fast, good looks, everything works - fantastic, very much appreciated and thank you very much @ Devs!!! :good::good::good:
One big problem though:
When running the stock ROM the battery usually lasted about 2 days. Now, with CM10.2 it is empty after half a day. Since I did a full wipe before she is using less Apps as compared to before and there is no single big consumer. Just the typical mail apps, facebook etc.
When I look at the wakelocks there is one app consuming most CPU which is CSipSimple. But that app was also running before the upgrade when the battery lasted 2 days.
The screen seems to consume more power though, is that possible? Anyone else with similar experiences?
Thank you very much!
Click to expand...
Click to collapse
try to flash madridi kernel .. and install greenify app from playstore to greeinfy apps which run in background
Ahmed.ragab said:
try to flash madridi kernel .. and install greenify app from playstore to greeinfy apps which run in background
Click to expand...
Click to collapse
ok thanks let me do some reading.
Also yesterday I deactivated the SIP app and that helped of course. Still strange that the app consumed to much less power on Gingerbread compared to CM10.2
Thanks,
Sven
You can try out battery calibration app before new kernel. Cause there is no "wipe battery stats" on cwm 6.0.4.4. I had same problem, and its a bit effected on cm 10.2. It's free. Maybe it will solve your problem.
Battery Calibration
That sounds very good, let me try that!
I have the same issue with increased battery drain. Yet I've not been able to identify the source. I disabled a lot of services (with Disable Service), also deactivated unnecessary system apps.
Cell standby is also shown as a huge drainer, although I usually have a good signal and no losses (checked with Better Battery Stats). There are no wake locks out of the ordinary.
Now I'll try battery calibration to see if that helps at least some amount.
Actually for me nothing really helped.
I eventually identified the 3 apps that drained the battery via Wakelock detector.
Those apps are Facebook, GMX Mail (based on K9 mailer) and CSipCimple.
Before the update to 4.3 my wifes phone was running the stock gingerbread and did not have an issue at all with those apps.
Yet on CM4.3 they are draining the battery.
Once I uninstalled the apps the batter life is back to normal. Which is sad, because she needs those apps. But no other solution so far from my side....
nuukee said:
Actually for me nothing really helped.
I eventually identified the 3 apps that drained the battery via Wakelock detector.
Those apps are Facebook, GMX Mail (based on K9 mailer) and CSipCimple.
Before the update to 4.3 my wifes phone was running the stock gingerbread and did not have an issue at all with those apps.
Yet on CM4.3 they are draining the battery.
Once I uninstalled the apps the batter life is back to normal. Which is sad, because she needs those apps. But no other solution so far from my side....
Click to expand...
Click to collapse
maybe if ur wife want to use fb checjlk her email... myb use broeser is okay... u can download opera mini or uc browser... it very fast and smooth browser.... or u can flash other rom like oneofakind.... growl (battety) version),,,,, hope this will help you!
hotriffs said:
You can try out battery calibration app before new kernel. Cause there is no "wipe battery stats" on cwm 6.0.4.4. I had same problem, and its a bit effected on cm 10.2. It's free. Maybe it will solve your problem.
Battery Calibration
Click to expand...
Click to collapse
Again the myth with whiping battery stats / battery calibration. Make a full charge and unplug the charger. This will whipe your battery stats.
And for the ones who never get this. The stats are just some data about apps consumption collected while the battery gets discharged. The ROMs are whiping them by itself on each full charge and after shuting down the phone.
This data has no Infulence to how long a battery lasts. It´s just collected to show you visually the statistics.
honeyx said:
Again the myth with whiping battery stats / battery calibration. Make a full charge and unplug the charger. This will whipe your battery stats.
And for the ones who never get this. The stats are just some data about apps consumption collected while the battery gets discharged. The ROMs are whiping them by itself on each full charge and after shuting down the phone.
This data has no Infulence to how long a battery lasts. It´s just collected to show you visually the statistics.
Click to expand...
Click to collapse
+10
honeyx said:
This data has no Infulence to how long a battery lasts. It´s just collected to show you visually the statistics.
Click to expand...
Click to collapse
Thanks ... yeah well did not really expect it, but when you're desperate
At least I thought it helps with the effect that the first 50% of the battery last 3 times as long as the last 50%, but not even that changed
nuukee said:
Hi,
One big problem though:
When running the stock ROM the battery usually lasted about 2 days. Now, with CM10.2 it is empty after half a day. Since I did a full wipe before she is using less Apps as compared to before and there is no single big consumer. Just the typical mail apps, facebook etc.
When I look at the wakelocks there is one app consuming most CPU which is CSipSimple. But that app was also running before the upgrade when the battery lasted 2 days.
The screen seems to consume more power though, is that possible? Anyone else with similar experiences?
Thank you very much!
Click to expand...
Click to collapse
I had the same problem with my S4 running CM 10.2 stable. The battery was empty after 8 hours. What I did was to change the theme, and today i got 12 hours and only 20% of the battery gone and wi-fi/3g all the time. Well, I still have only one hour of screen up time, but that is how it was before... I don't know, i'm just saying! Maybe it helps. The theme i added is LunarUi 2.
All the best!
Guys,
i need some help. Over the last two days, my battery has just gone. The attached screenshots are from earlier this morning. I'm really not sure what's causing this. I lost 11% in under an hour and my phone was telling me it has 4 hours of battery left. I haven't installed anything new in the last two days.
I've tried using better battery stats in the past. I'm not sure how these apps work. I noticed my cell service isn't that good but I'm at home, always on WiFi. Can someone point me in the right direction? This phone is not even two months old.
Thanks in advance.
I highly advise you to turn aeroplane mode on and enable WiFi calling if you have it. It saves so much battery! This is whilst your indoors of course. Keep your brightness below 40, disables location when you don't need, disable auto update and sync behavours, disable NFC and Bluetooth if not being used. Disable animations via developer menu.
Your screenshots don't seem to show how much battery Android OS is using and there's nothing battery draining in what you did include, so I don't know that anyone can really do a lot to help you beyond offering very general suggestions.
What Rom or version of Android are you running? If you are running stock did a monthly OTA update install recently? It is that time of the month.
It's possible you have a rogue app but there's nothing showing up in your screenshots. It's possible that Google, Facebook or some other app is getting sync errors. Where you would check for that would depend on what OS you are running.
You could contact Pixel Support but my guess is that they would have you try a factory reset, which might be your best course of action based on the limited information you have provided.
My battery percentage currently shows 61% 1 day and 7 hours left, so you definitely have something wrong.
I would personally start with a factory reset. You could also run the phone in safe mode for a while and see if the problem persists. If it doesn't then the issue is likely a third party app.
When I had my battery issues, I factory reset and just ran stock for a couple days. It turned out I had to RMA it due to a bad battery. Phone was dying between 20-60%. I would barely get 1 hr SOT
sefirosu0522 said:
Guys,
i need some help. Over the last two days, my battery has just gone. The attached screenshots are from earlier this morning. I'm really not sure what's causing this. I lost 11% in under an hour and my phone was telling me it has 4 hours of battery left. I haven't installed anything new in the last two days.
I've tried using better battery stats in the past. I'm not sure how these apps work. I noticed my cell service isn't that good but I'm at home, always on WiFi. Can someone point me in the right direction? This phone is not even two months old.
Thanks in advance.
Click to expand...
Click to collapse
Your screen was on for the majority of that time. And that 4 hours left means at the current rate you're going you'll only get another 4 hours. That is nothing more than an estimate and it will change all throughout the day based on you're use. Try letting you're battery drain all the way to zero 3 times. This should calibrate the battery. Try monitoring it after that.
And a side note. Use you're web browser for Facebook. The Facebook app has been a known battery destroyer forever.
jhs39 said:
Your screenshots don't seem to show how much battery Android OS is using and there's nothing battery draining in what you did include, so I don't know that anyone can really do a lot to help you beyond offering very general suggestions.
What Rom or version of Android are you running? If you are running stock did a monthly OTA update install recently? It is that time of the month.
It's possible you have a rogue app but there's nothing showing up in your screenshots. It's possible that Google, Facebook or some other app is getting sync errors. Where you would check for that would depend on what OS you are running.
You could contact Pixel Support but my guess is that they would have you try a factory reset, which might be your best course of action based on the limited information you have provided.
My battery percentage currently shows 61% 1 day and 7 hours left, so you definitely have something wrong.
I would personally start with a factory reset. You could also run the phone in safe mode for a while and see if the problem persists. If it doesn't then the issue is likely a third party app.
Click to expand...
Click to collapse
I:m running Pure Nexus ROM with the Elemental kernel.
Thanks for all the responses everyone. I will try to drain my battery and see if that helps.
I had this problem. I went in and disabled all of my Google apps. I then went back and re updated them in the Play store After that I did a restart and I haven't had one since. I also recommend not having a battery case as both the Mophie and ZeroLemon both caused huge wakelocks for me. Cheers. ?