Related
Leaving my OP in place, but I have rewritten the description with much more detail and pics here
http://forum.xda-developers.com/showthread.php?p=25401417#post25401417
I suggest skipping to there.
I am looking for general tips here. E.g., not asking you to diagnose my specific problem so much as give me ideas of what else to check or try.
Lately I have had unexplained (to me) battery drain. Yesterday I lost about 25 percent in an hour while the phone idled. It is not a constant thing, though. I can go an hour and loose 1 percent then loose massive amounts in the next hour.
Now, i have searched, but I have not found anything that applies to me.
I have:
Tried a different radio
Tried a different kernel
Reflashed my rom
Phone is entering deep sleep according to cpu spy
There are no unusual or excessive wake locks according to better battery stats
No apps are using a lot of battery.
I am in a low signal area at work, but putting the phone in airplane mode and dissabling background syn does not stop the drain.
Ideas?
might be your phone is loosing signal? i would check the battery stats in the settings menu to see if you have a poor mobile signal.
Zepius said:
might be your phone is loosing signal? i would check the battery stats in the settings menu to see if you have a poor mobile signal.
Click to expand...
Click to collapse
beren28 said:
I am in a low signal area at work, but putting the phone in airplane mode and dissabling background syn does not stop the drain.
Click to expand...
Click to collapse
So I don't think I can blame it on that.
Do you have any exchange sync on your phone?
Sent from my Galaxy Nexus using Tapatalk 2
can you give us screen shots of battery stats?
Herman76 said:
Do you have any exchange sync on your phone?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I do, and on reflection it is a possible culprit since I added it recently.
Didn't occur to me since it was producing no wakelocks and the battery stats did not showing as using much battery.
I shall turn it off for a bit and see if that helps. (unless there is some other way to test if it is the problem first.) I am off to the search button!
Zepius said:
can you give us screen shots of battery stats?
Click to expand...
Click to collapse
This is from yesterday when i set it down unused for about 90 minutes. The amount of wakes seems liek a lot, but it is similar to what i see when i have far far less drain, so I don't think that is the problem. I didn't get the app list screen, but out should screen as the only major drain with about 2 minutes.
I know it is shows poor signal strength, so immediately after that shot I put it in airplane mode, turned of sync, and rebooted. The battery continued to drain and graph had the exact same slope under those conditions. (Forget to get a pic though.)
Sent from my jitterbug using tapatalk.
System panel paid version with monitoring enabled is the best for tracking apps using CPU.
OK, still working on this.
To recap:
When the screen is off, and no apps are running I sometimes get inexplicable battery drain. This is occurring under conditions when I should be experiencing little or no drain at all. I say this becuase:
The screen is of and no bakground apps are running
the phone is NOT awake and IS entering deep sleep (as confirmed by cpuspy)
there are no unusual kernel or partial wake locks
there are no apps listed as using unexpected ammounts of battery
This is not a universal problem. The phone *often* behaves as expected. I can leave the phone off for an hour and see a 1% or 2% drain, and I am happy with that. However, sometimes, randomly, it goes nuts on my.
This graph from a few weeks ago shows what I mean. Look in the green box. The phone is sleeping, and the screen is off. The graph starts as a flatline, then, all of a sudden, it begins to drop precipitously.
Here is a graph that shows the battery dropping at the same rate whether the phone is awake or sleeping:
I have gone the following to try and narrow the problem down:
Done a completely fresh install of my Rom including a system wipe.
Tried two kernels (the aokp default and several relases of Franco's
Tried a different radio
Activated and installed a new sim card
I have come to suspect that the problem is network related. When the problem starts, sometimes going into airplane mode and back and/or toggling 2g only temporarily fixes the problem.
I suspect that something is happening with my connection to T-Mobile that keeps the network running and draining power. This is pure speculation, but it is all I can think of.
I installed juice defender (which I had not been previously running) and noticed the that, sometimes, it didn't turn of data when it should have. I also noticed the following two things happen:
I do not believe it is a rom problem, since if so, someone else would be reporting this. It might be an app problem, but if so the app is draining battery without a wake lock and while the phone is in deep sleep.
It is not exchange (as was suggested in this thread) since it continues when I ev my exchange account.
I have no idea what else to do or try.
Since it happens at random and takes a while to identify, uninstalling one app at a time to test for that could easily take months to narrow down a misbehaving app.
I know it is not a hardware issue since last month I got this:
That was with AOKP and Franco (earlier versions obviously)
I have google searched till my fingers bleed.
I am a long way form being an expert, and I suspect I may have overlooked something obvious.
Please, any thoughts??
Damn you definitely have a major issue and I don't know what it could be. But when my phone sleeps itstays dead flat with no awake bars, and drops 1% every 3 hours.
1. Calibrate battery
2. If you really wanna find the problem, install the rom with no mods or apps and run it and see if it still happens. Then add back each mod/app one at a time
derekwilkinson said:
1. Calibrate battery
2. If you really wanna find the problem, install the rom with no mods or apps and run it and see if it still happens. Then add back each mod/app one at a time
Click to expand...
Click to collapse
While I appreciate your effort, this is remarkable unhelpful for the following reasons:
1. "calibrating" the battery is a myth and doesn't actually do something. Even if it did, it would not explain the symptoms I have described. I have been around xda long enough to know it is the knee-jerk reaction to any battery question, but it is not relevant here.
2. Since the problem occurs at random, and sometimes takes hours to show up, (For instance, last night I charged to full and tried to catch it happening. For 4 hours nothing happened, it behaved perfectly. Then I went to bed and it immediately started to fall and was dead by morning) and since I have over 100 apps, your suggestion could easily take *over a year* to follow. Believe me, I have thought about it, but I started this thread hoping for ideas that would allow me to avoid it.
Here is that chart for last night.
I had about 1 hour and 30 minutes screen on time with 65% left when I went to bed. When I woke up, phone was dead.
RogerPodacter said:
Damn you definitely have a major issue and I don't know what it could be. But when my phone sleeps itstays dead flat with no awake bars, and drops 1% every 3 hours.
Click to expand...
Click to collapse
Mine often does that. But sometimes it doesn't. It is the fact that it happens seemingly at random that makes it so annoying and hard to track down.
I would replace the battery
One thing you haven't rulled out is that the battery itself is bad.
Have a friend you could swap with for a day, or at least long enough to see if the problem follows? If your battery drops on their phone that is also a good indication.
arw01 said:
One thing you haven't rulled out is that the battery itself is bad.
Have a friend you could swap with for a day, or at least long enough to see if the problem follows? If your battery drops on their phone that is also a good indication.
Click to expand...
Click to collapse
The thought has occurred to me, but unfortunately, no, I don't have a friend I can swap with. And really, since I have had the phone less than 3 months, the battery *shouldn't* be bad, but yeah, defective products happen.
If I cannot find any other cause I will likely order a new battery and see if that fixes it.
beren28 said:
While I appreciate your effort, this is remarkable unhelpful for the following reasons:
1. "calibrating" the battery is a myth and doesn't actually do something. Even if it did, it would not explain the symptoms I have described. I have been around xda long enough to know it is the knee-jerk reaction to any battery question, but it is not relevant here.
2. Since the problem occurs at random, and sometimes takes hours to show up, (For instance, last night I charged to full and tried to catch it happening. For 4 hours nothing happened, it behaved perfectly. Then I went to bed and it immediately started to fall and was dead by morning) and since I have over 100 apps, your suggestion could easily take *over a year* to follow. Believe me, I have thought about it, but I started this thread hoping for ideas that would allow me to avoid it.
Click to expand...
Click to collapse
1. yes battery calibration does make a difference.
2. ok, so an app can't run a process at random? especially when you have "over 100 apps"? Run the rom stock and see if it still happens, or even run the stock rom/kernel. if you don't want to try this then why are you asking for suggestions? christ
derekwilkinson said:
1. yes battery calibration does make a difference.
Click to expand...
Click to collapse
You are incorrect. But, in any case, I DID calibrate the battery just to cover bases in the case that I was wrong.
2. ok, so an app can't run a process at random? especially when you have "over 100 apps"?
Click to expand...
Click to collapse
We'll of course it can. That is kinda my point. If I go one app at a time waiting for it to "run a process at random" I am talking literally MONTHS of testing. I would have to wait many hours, if not days after installing or uninstalling an app to be sure whether or not it made a difference, then move on the the next. This is simply not an option. I started this thread in hopes that a realistic and doable solution might exist that I was unaware of.
Run the rom stock and see if it still happens, or even run the stock rom/kernel. if you don't want to try this then why are you asking for suggestions? christ
Click to expand...
Click to collapse
I am asking because there may be a solution that I am unaware of that doesn't require me to put my entire life on hold for months. It is possible that there is no such solution, but I asked in case there was one.
Sorry to have put you out so much.
You mentioned you recently installed exchange sync. Did turning off sync remedy this or have you not tried disabling all sync features?
One other thing to check is the background data usage of your apps. You'd find this under 'data usage' and make sure you enable the wifi tab so you can see data usage on wifi.
skadebo said:
You mentioned you recently installed exchange sync. Did turning off sync remedy this or have you not tried disabling all sync features?
when i did a complete quote and re flash i did not setup the exchange account, but the issue continued.
One other thing to check is the background data usage of your apps. You'd find this under 'data usage' and make sure you enable the wifi tab so you can see data usage on wifi.
Click to expand...
Click to collapse
I'll check that out. Thanks.
Sent from my jitterbug using tapatalk.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
My battery also drains at a rate similar to yours however I'm on the CDMA version. Hopefully you can figure out what's going on with yours.
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
I had been getting some higher battery drain with JB than I was with ICS, both were on rooted stock ATT roms. Early on I had posted that it was about the same as ICS, but after more and more use, I was starting to find that it really wasn't. I was consuming about 5-8% per hour idle and 10+ while actually using it. The idle bothered me the most because, obviously, using a phone will drain the battery
Two things have stood out as the high consumers: Media Scanner and poor signal.
To address the media scan drain, there have been suggestions to change CWM settings to backup as .tar rather than default .dup. This ONLY works if you re-do each nandroid that was a .dup as a .tar, delete the .dup backups, and clear the unused backup data through CWM. This removes the blobs folder files which will be in the thousands.
To address the poor signal drain, I flashed the UCLH9 modem (see modems thread in the development forum). Better Battery Stats is not showing any drain caused by poor signal, and this is also reflected by actual usage, the signal is simply... better.
Consumption is marginally higher than on ICS but not nearly as high as I was experiencing. If this has already been covered, my apologies for eating up server space...
Could you alternatively put a .nomedia file into the clockworkmod folder on the device? Would that prevent it from scanning that folder?
Well I'm bone stock and not rooted, I have no backups and the media is eating my battery like mad since the update. I've killed the process several times but it starts back up on its own. The only way I know to fix it will require root.
Sent from my SAMSUNG-SGH-I747 using xda premium
There is a rogue app in the stock TW that is doing it. I have seen it in every 4.1.2 port. Run a de-bloat and it will go away.
Do you know what bloat exactly is causing it?
shoestar said:
There is a rogue app in the stock TW that is doing it. I have seen it in every 4.1.2 port. Run a de-bloat and it will go away.
Click to expand...
Click to collapse
I have all the att and Samsung bloat frozen via TiBu.
Trust me, something is there. I never had the chance to figure out exactly which app it was though. I have a feeling that it may have something to do with a Samsung app.
I would suggest using OS Monitor from the Play Store. Make it show all system processes and see if you can dig deeper into it.
Edit: Also, here is my humble opinion too. People keep wanting new and better features. Well, that always comes at a cost. Just remember that. The iPhone boys are learning that the hard way too.
shoestar said:
Trust me, something is there. I never had the chance to figure out exactly which app it was though. I have a feeling that it may have something to do with a Samsung app.
I would suggest using OS Monitor from the Play Store. Make it show all system processes and see if you can dig deeper into it.
Edit: Also, here is my humble opinion too. People keep wanting new and better features. Well, that always comes at a cost. Just remember that. The iPhone boys are learning that the hard way too.
Click to expand...
Click to collapse
I agree with that sentiment... I'm considering reverting back to ICS but the smoothness of jelly beans is too enticing.
after making these changes yesterday I got a 40% battery consumption over 9 hours with average use which IMHO is plenty.
Solution is to reboot the phone OR unmount by going into settings, storage and unmount the USB there instead of from the notification bar. I think this solution works but have not tried it myself.
rebooting whenever the os gets out of hand, or unmounting the SD card, is not a viable option IMHO.
my post was directed toward root users who have cwm installed and are experiencing the media drain because of the blob files. the modem change I tried because all the reliable jelly bean ports seem to use the H9 modem. a weak mobile signal is detrimental to battery life, as is a weak or intermittent WiFi signal.
believe me, on my rooted phone, these two changes made a real and noticeable improvement in battery life in JB. I've gone half the day today on ICS and half the day on JB. battery consumption is now within the range I had on ICS.
one the one hand, I believe that some increase in consumption is due to the "omg I has the jelly beans and I'm going to use the bejeasus out of my phone" factor. I also believe that a good number of fixes and patches are simply a placebo effect. BUT, my phone had been getting hot and tearing up the battery due to signal searching in areas where it had been fine prior to the update. heck, we have an att tower within 100 ft if my office, I typically pull 69-70mbps at work. on the k3 modem I was regularly dropping data or losing LTE. not anymore.
Un mounting then re mounting seems to have worked for me the process can now be killed!
Sent from my SAMSUNG-SGH-I747 using xda premium
1% in the last hour and it wasn't idle the whole time. sent a few texts and spent a few minutes on Facebook. I'll take it...
Check you facebook mine wa at 51% I uninstalled it and re installed fixed battery drain
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Argh. k3 modem has been simply horrible. was constantly losing data though I initially thought it was the rom i was using. Is it safe to back flash from k3 to h9 or is there a certain procedure that needs to be done?
mtl171 said:
Argh. k3 modem has been simply horrible. was constantly losing data though I initially thought it was the rom i was using. Is it safe to back flash from k3 to h9 or is there a certain procedure that needs to be done?
Click to expand...
Click to collapse
I used the CWM flashable zip from the thread in development. I did the typical cache/dalvik cache wipe first.
the last4 hours the phone was on my nightstand unplugged doinga sleep drain test. 0.3% per hour.
Ok I have found something running on my SGS3 that wasn't running all the time before and now its open constantly. I need to know if anyone knows if this one is safe to FC and then disable. Any help would be appreciated. I mean heck I wake up in the morning and this is running and I definitely am not using maps in my sleep.LOL anyways anyone know?
bogdaryl said:
Ok I have found something running on my SGS3 that wasn't running all the time before and now its open constantly. I need to know if anyone knows if this one is safe to FC and then disable. Any help would be appreciated. I mean heck I wake up in the morning and this is running and I definitely am not using maps in my sleep.LOL anyways anyone know?
Click to expand...
Click to collapse
what is it?
OOPS! Sorry about that. MAPSserviceSamsung. I finally found the list of apps safe for disable and it is safe to disable. I'm seeing a bit of improvement in battery life. I also uninstalled facebook and reinstalled it and since doing these 2 things I'm things are getting much better.
I will have to try these. My battery is horrid. My OneX got easy 30+ hours of heavy use to a charge. My SG3 is lucky to get 8 hours. I average 10% an hour on mild use, heavy use and its as high as 15%
Sent from my SGH-I747M using xda premium
bogdaryl said:
OOPS! Sorry about that. MAPSserviceSamsung. I finally found the list of apps safe for disable and it is safe to disable. I'm seeing a bit of improvement in battery life. I also uninstalled facebook and reinstalled it and since doing these 2 things I'm things are getting much better.
Click to expand...
Click to collapse
I'd like to see that list too if you don't mind sharing the info
I think I'm going to do a factory reset soon. Pretty sure that these drains are caused by some leftovers from ICS...
Before I begin, let me state that I have already factory reset countless times and reflashed my firmware at least 3 times in the past week. Neither of these have helped me at all, so PLEASE do not suggest this. I've been trying to solve this problem for a week or two and everyone has suggested this to me and of course I've already done it, so it hasn't helped me at all.
PHONE: E980
FIRMWARE: Stock 4.4.2 E98020g
BASEBAND: APQ8064/MDM9x15M
SYMPTOMS:
-Battery draining ridiculously fast (appx 10%/hr, but before my last reflash, it was draining 50%/2hrs!)
-Phone only lasts about 5hours.
-Android OS is consuming about 80-90% of battery, followed by Screen at around 10%
-Phone is constantly warm
-Phone rarely enters Deep Sleep (it stays awake 95% of the time).
TESTS DONE:
-As I said, I factory reset numerous times with the same exact problem
-I reflashed my firmware 3x, with same problems
-I usually keep auto-sync on, but the issue occurs whether it is on or not.
-There is supposably a Kitkat 4.4.2 (in general) issue where the camera will consume a ton of CPU resources and get stuck that way. I haven't used my camera much, but do use Smart Stay, so I disabled this. No positive result.
-Disabled the Google Now "OK Google" hotword detection. This helped reduce the drain, but didn't solve it. Drain went from like 15%/hr to 10%/hr.
-Took battery out of phone for 10 minutes and placed back in. Seemed to help at first, but after about an hour or so, it returned.
-"Recalibrated" the battery numerous times. This was done by draining the battery until the phone shut itself off. Then I charged the phone to 100% while the phone was still off. Once the phone read as having 100% charge, I let it charge for another 1 hour. Then I unplugged the phone and booted it up. Again, this appeared to help at first, but after a while, the phone began to drain rapidly again.
NARROWING THE ROOT PROBLEM:
-Both WakeLock Detector and BetterBatteryStats show "wlan_wake" and "wlan_wd_wake" as being the largest wakelocks.
-As previously mentioned, "Android OS" is consuming a huge amount of battery
-Problem only seems to happen when wifi is on, whether it is connected to an SSID or not.
OTHER:
I have narrowed the issue down to wifi but I can't seem to figure it out any more than this.
Both of the "wlan_" wakelocks are caused by wifi being on and I need wifi on whenever possible because I can't afford a huge data plan. My current one is 2GB/mo and it is shared between 3 people.
I noticed today that my phone drained 10% within 1 hour after taking the phone off the charger, and I was connected to my home wifi. I then went to work, but still had wifi turned on on my phone. At work, I was only connected to mobile data (but the phone was just sitting in my pocket). The battery drained another 15% within an 1hr 30min, and the phone was warm in my pocket (very uncomfortable!). I then turned wifi off completely, and the battery drain completely disappeared!!! The battery life was amazing in fact!
PICTURES:
I've provided some screenshots with notes. Please take a look at them.
I'm going to manually make the problem happen again and will upload new pictures afterwards. They will be of WLD and BBS. Any current info I have is tainted since I turned wifi off and the problem temporarily turned off too. I want to get only screenshots of what is going on when the problem is happening.
EDIT: BTW, the problem occurs whether my mods are installed or not (the mods used to remove the icons in statusbar, AdAway, etc)..
The issue seems to be pureply related to wifi and nothing else.
IDEAS:
Could adding a wifi supplement scan interval to the build.prop solve this problem?
Is Wifi bugged in this firmware? (This never happened on Jelly Bean!!!!)
Is maybe the "Battery Saving for Wifi" feature bugged?
Would maybe flashing the Jelly bean modem (e98010p) solve this issue (since it didn't happen on Jelly Bean)? If so, does anyone have a flashable version of this? <- I just did some research and it seems that the baseband (AKA modem) is the same in Kitkat as it was in Jelly Bean. Weird....
These pictures were taken shortly after making my first post. I already had wifi turned off, so I turned it back on and after a few minutes, the battery began to plummet. I went from roughly 77% to 66% in just an hour!!!!
Just to make sure that it is clear, I have both BBS and WLD set to start recording data after the phone has been unplugged from the charger. So to restart the data collection, I simply plugged the phone into my charger for a few seconds and then removed it. THEN I turned wifi on. The data seen in the pictures should only have occurred between the time when I unplugged the phone and the time I took the pictures.
EDIT: Also just to make sure it's clear: All the data shown in the System picture is actually since I unplugged the phone this morning. I only posted these pictures to show any changes from the similar ones posted earlier.
PLEASE! Can anyone help me solve this!?
Or is this a major Kitkat bug!? (or ATT bug, or modem bug, etc etc).
After a full week of this problem, I think I just made another breakthrough. Unfortunately, I think it IS one of my Xposed modules, which is weird because I didn't think any of them would have a need to constantly connect to the internet.
All I know is that I just completely uninstalled the Xposed Framework and the phone started to sleep like a baby... with wifi on!
Now I just need to pinpoint the module, which I can do myself.
MODS CAN CLOSE THIS THREAD.
Sorry I created it and (mostly) solved my own problem. This happens to me a lot. I have a problem, can't figure it out, ask for help, then solve it myself. :/
spexwood said:
MODS CAN CLOSE THIS THREAD.
Sorry I created it and (mostly) solved my own problem. This happens to me a lot. I have a problem, can't figure it out, ask for help, then solve it myself. :/
Click to expand...
Click to collapse
Please do not be sorry for this thread :good:
Someone else may have a similar issue so we will just leave it as it is
Glad your issue is fixed
Toledo_JAB said:
Please do not be sorry for this thread :good:
Someone else may have a similar issue so we will just leave it as it is
Glad your issue is fixed
Click to expand...
Click to collapse
In this case, I need to be more specific about my solution then.
The problem seems to be caused by the module, Xposed Torch. It's still usable, but you need to tap the overflow (3-dot) icon and disable ads (it's free to do this). The module requires internet access permissions, which I was not aware of, and it constantly connects to the internet to stream the ads. This in turn causes the wifi to constantly receive data (thus the wlan_wd_wake and wlan_wake). When wifi is on, but not connected to a network, I think it forces wifi to constantly scan in order to find a connection so that it can get that ad data. I'm not sure why it doesn't just use mobile data though... unless it does and it's just more power efficient.
So far, I have disabled the ads via module settings and the phone is now sleeping like it should.
So if anyone else is having wlan_wake wakelocks of any kind, especially followed by wlan_wd_wake or wlan_rx_wake, then this means that something on your phone is constantly accessing the internet via wifi. FIrst turn off auto-sync, and if this doesn't help, then you need to uninstall apps until the problem ceases.
My phone is currently icy cold in my hand and I've never been so happy to feel it like this!
Problem came back today. I've basically uninstalled every app now and the battery is still draining whenever wifi is turned on.
Under Better Battery Stats, there is a process (?) called dhc_dpc that's been running the entire time my phone has had wifi on. There are also the wlan_wakes too. (NOTE: IIm backing up my phone right now, so these names are coming from memory).
According to this thread (different phone and unknown Android version, but similar problem), the wifi driver may be bugged. They recommend doing a reinstall, but I've done this many times now and it doesn't seem to help:
http://forum.xda-developers.com/galaxy-s2/help/dhddpc-t1246190
EDIT: I think I've found the culprit and while it is definitely wifi-related, it's NOT an app. It's the actual Android system constantly pinging the internet. According to my research, it's constantly collecting location data by using either mobile data or wifi and will do this whether you have location services (gps) or Location Reporting enabled. This has been described as a "bug." It was introduced by Google as a cool new feature, but it's implementation was buggy.
I am currently testing a fix to resolve this issue, but want to be certain that it's fully working first.
Just an an FYI, this fix SHOULD help anyone running Android 4.4.2 and experiencing high battery drain caused by Android OS. Even better, the fix does not require root, so anyone can do it!
have you try a full factory reset using lg driver to bring full stock rom back and not just a factory wipe from the phone
3617 said:
have you try a full factory reset using lg driver to bring full stock rom back and not just a factory wipe from the phone
Click to expand...
Click to collapse
Not to be rude, but the first sentence of my first post says I did this several times.
I had those ridiculous battery drains on both stock ROMs with xposed, but never found a direct connection with it.. So first, (if you already haven't), try to disable xposed completely and try again. LG's stock ROM doesn't like that kind of modifications. Also, one of the biggest problems I had with Kit Kat was Location services, so you should check them too.
If that doesn't help, check your apps and download stats, maybe there is something downloading or trying to download stuff.
zamajalo said:
I had those ridiculous battery drains on both stock ROMs with xposed, but never found a direct connection with it.. So first, (if you already haven't), try to disable xposed completely and try again. LG's stock ROM doesn't like that kind of modifications. Also, one of the biggest problems I had with Kit Kat was Location services, so you should check them too.
If that doesn't help, check your apps and download stats, maybe there is something downloading or trying to download stuff.
Click to expand...
Click to collapse
It's definitely Xposed related I think.
I've disabled Xposed during some testing a day or two ago and yeah, battery definitely improved.
The only modules I have installed are:
App Settings
Enable BatteryStats Permission (just to allow me to track this issue. I installed this after problems had already begun)
Greenify (all Xposed settings checked)
YouTube AdAway
I have also been using G2 TweaksBox up until last night. I only used it to declutter my status bar and to enable the advanced reboot menu. (I hate all the icons in the status bar!!!). Last night I disabled G2 TB and battery life improved dramatically!
I can't explain why G2 TB would cause battery drain, but I did notice it doing something odd yesterday. I have the lockscreen off sound enabled in the system settings, so I hear the sound whenever I lock the screen. Well, I turned my phone on yesterday for some reason when in my car. I then turned the screen off, heard the lock sound, and started driving. 15 minutes (NOT seconds!) into my drive, I randomly heard my phone make the locking sound, but the screen was not turned on!! I wonder if G2 TB delays my lock somehow.
I switched to GravityBox[KK] today since so many people claim that it works perfectly on their OGP, and so far, battery drain is MUUUUUCH better than with G2 TB activated, but it still may not be as good as pure stock. I need more time to figure it out though. This morning, my battery dropped 5% in 40 minutes while connected to my home wifi. I then left my house for a few hours, but left wifi turned on on my phone (it's hard for me to remember to switch it off and on all the time!). The battery seemed to be pretty stable after that, but I can't explain the weird 5% drop, but I did receive 2 missed calls and a text during that time too. Should I lose 5% just from getting a text and having my phone ring?
It's now night time and I'm at 75% battery. This past week, I would be at about 10% by now or even DEAD, so I'm happy as heck right now.
I would LOVE to be able to keep using GB, but I now just need to figure out if it too is draining battery, or if everything is stable. I'm going to continue comparing stock VS GB tonight and tomorrow. I'll live with stock if needed, but I'm just very OCD about the statusbar clutter.
In GB, I only disabled some icons, centered the clock, enabled advanced reboot menu, and enabled the lockscreen torch.
Try with GB and post results, it looks like it doesn't drain that much... Unfortunately for me, I had problems with every xposed module ever tried, so I simply gave up and now I'm using another rom. I think that LG's ROM is problematic, especially if you use a lot of SystemUI customisations, like GravityBox does.
Are wakelocks from orginal post still active?
G2 Tweaks aren't even compatible with our phone (as much I understood), never managed to do anything with them. I assume that G2's SystemUI is too different from OGP's, so that may be one of the problem sources.
With my normal usage (1-2 hours of music, 2-3 hours of internet - wifi or mobile, K9 sync, viber, sometimes games, ~60 SMS and few longer calls per day), battery was holding up to 35, sometimes 45 hours. With xposed, barely a day, if I turn mobile data and sync off. I usually have a dilemma about putting it to a charger before sleep, there is alway around 60-50% of battery at the end of the day.
zamajalo said:
Try with GB and post results, it looks like it doesn't drain that much... Unfortunately for me, I had problems with every xposed module ever tried, so I simply gave up and now I'm using another rom. I think that LG's ROM is problematic, especially if you use a lot of SystemUI customisations, like GravityBox does.
Are wakelocks from orginal post still active?
G2 Tweaks aren't even compatible with our phone (as much I understood), never managed to do anything with them. I assume that G2's SystemUI is too different from OGP's, so that may be one of the problem sources.
With my normal usage (1-2 hours of music, 2-3 hours of internet - wifi or mobile, K9 sync, viber, sometimes games, ~60 SMS and few longer calls per day), battery was holding up to 35, sometimes 45 hours. With xposed, barely a day, if I turn mobile data and sync off. I usually have a dilemma about putting it to a charger before sleep, there is alway around 60-50% of battery at the end of the day.
Click to expand...
Click to collapse
OK, so I just got home from work and today I not only had GravityBox disabled, but I also had the ENTIRE Xposed Framework uninstalled.
My battery is now at 30% and I was only gone for 7 hours!!!!!!!!!!!!!!!!!! This is ridiculous!!!!!!!!!
*sigh* <- frustrated with this whole situation
Yes, the wakelocks are still active.
The top two Kernel Wakelocks are "wlan_wd_wake" (46.3%) and "wlan_wake" (46.2%) in that order. The next in line is "PowerManagerService.Wakelocks" (8.0%) and then "msm_hsic_host" (6.1%). This was since my last reboot, which was about 2 hours ago (I had to rebooted after removing an app that I thought was the culprit... apparently it wasn't).
Again, I keep Auto Sync on, but disablign it seems to not help in this matter at all.
I also keep wifi on. When at work, it isn't connected to a network, but I often forget to disable wifi when I leave the house, or I come home and forget to enable it and end up sucking my data plan dry. Nonetheless, I also did this while on Jelly Bean and had no issues whatsoever.
My phone is only staying in deep sleep less than 10% of the time and the time when it is awake, the CPU is running at full 1.7GHz! This is causing the phone to get warm in my pocket. It doesn't hurt, but it's enough to make things uncomfortable.
According to the battery stats (in system settings), Android OS is consuming 83% of the battery.
The biggest network drainers are "Google Play Services" (33.3%), something simply called "0" (14.8%), and a weather app. I had the weather app open manually not too long ago though, so that explains that one, but the other two I can't. I have no clue what "0" is and I have not opened Play at all today.
It's something to do with wifi itself I think, and maybe not a specific app accessing wifi. (?)
I turned wifi completely off about an hour ago and the battery drain has been stable. It's been like this for days too. If I turn off wifi, the drain is "normal." If wifi is on and connected, drain is higher than with wifi off, but barely. If wifi is on and not connected, the battery level plummets like a rock in a pond.
OH! One thing I just thought about and should mention:
Before I discovered that G2 TweaksBox was causing serious drain, I was on another battery-related thread in the OGP forum. Someone told me to delete the "libiq_client.so" file from System/lib. He assured me this would give me excellent battery life (which apparently it did not). So I did. Normally, I just rename system files so I can restore them if needed, but I guess I accidentally deleted this one.
Could this be causing the drain, and if so, can someone upload a copy of libiq_client.so so I can try it on my phone (after setting it's permissions correctly)?
Um, that's not good.
Check wireless settings, and disable "Scanning always available" if enabled.
You don't have a nand backup, do you? I have E988 variant so maybe my file isn't good, I don't know if there are big differences between them. I can upload it if you want.
It is possible that Google Services are messing things up since they are between top processes... have you tried clearing their cache/data? Also, if you have a custom recovery, clear cache/dalvik cache, maybe it helps. Also, if High precision location is enabled, try disabling it if you don't need that service, I had some problems with that in combination with weather widgets.
What partial wakelocks are active?
zamajalo said:
Um, that's not good.
Check wireless settings, and disable "Scanning always available" if enabled.
You don't have a nand backup, do you? I have E988 variant so maybe my file isn't good, I don't know if there are big differences between them. I can upload it if you want.
It is possible that Google Services are messing things up since they are between top processes... have you tried clearing their cache/data? Also, if you have a custom recovery, clear cache/dalvik cache, maybe it helps. Also, if High precision location is enabled, try disabling it if you don't need that service, I had some problems with that in combination with weather widgets.
What partial wakelocks are active?
Click to expand...
Click to collapse
"Scanning always available" has been disabled since day 1
The only nand backup I have is after I already deleted the file :/
I did try clearing Google Service's cahce/data at one point and I think it helped for a few hours. It may have been a placebo effect though. I also di the recovery cache wipe and dalvik wipe with same results.
I don't keep location on at all since I don't use it. It's always off, but at one point, I did enable it to select the battery mode and then turned it off again. I did this mainly so that if and when I do use location, it would always use Battery and not High Precision.
I'm currently backing up my rom, so all partial wakelocks were cleared for now. Sorry.
I'm trying to reflash the stock rom real quick and grab the libiq_client.so file, then restore the backup and insert the file back into system. Unfortunately, I may not be able to tell if it solves the problem until sometime tomorrow.
EDIT: BTW, the only reason why I won't just start all over again on the reflash is because 1) I want to figure out what's causing this problem so it won't happen again, and 2) I don't have the time to spend hours setting my phone up again
EDIT2: Oh and every time I reflashed my ROM, the first things I did was rename/delete that library file and installed G2 Tweaksbox. And every time I had horible battery drain, so i'm really hoping it's due to the lack of this library file.
spexwood said:
"Scanning always available" has been disabled since day 1
I'm trying to reflash the stock rom real quick and grab the libiq_client.so file, then restore the backup and insert the file back into system. Unfortunately, I may not be able to tell if it solves the problem until sometime tomorrow.
EDIT: BTW, the only reason why I won't just start all over again on the reflash is because 1) I want to figure out what's causing this problem so it won't happen again, and 2) I don't have the time to spend hours setting my phone up again
EDIT2: Oh and every time I reflashed my ROM, the first things I did was rename/delete that library file and installed G2 Tweaksbox. And every time I had horible battery drain, so i'm really hoping it's due to the lack of this library file.
Click to expand...
Click to collapse
Try it. I can upload file from my backup if you're willing to experiment with that, to save you from all that flashing.
Also, if you edited your build.prop and changed pm.sleep_mode and ro.ril.disable.power.collapse, undo that. It only disabled deep sleep state for me (had similar problems few days ago when flashed a new rom, mmc1_detect, suspend_backoff and some other weird things, so I even tried that)
Have you tried using another roms?
zamajalo said:
Try it. I can upload file from my backup if you're willing to experiment with that, to save you from all that flashing.
Also, if you edited your build.prop and changed pm.sleep_mode and ro.ril.disable.power.collapse, undo that. It only disabled deep sleep state for me (had similar problems few days ago when flashed a new rom, mmc1_detect, suspend_backoff and some other weird things, so I even tried that)
Have you tried using another roms?
Click to expand...
Click to collapse
It's OK, I'll get the file from the flashing. I know it'll be a pain, but this may be safer just in case there is some sort of difference between the E988 and E980 versions. I doubt there would be, but better safe than sorry I guess.
I did add those settings to my build.prop as a test, but I was smart there and backed up my stock build.prop first and ended up restoring it a few hours later. It was causing my screen to not always turn on when I pressed the power button.
I have not tried any other ROMs. I prefer to stick to stock ROMs (or modified versions of stock... basically anything stock-based and not CyanogenMod or AOSP). I had bad experiences with AOSP-based ROMs on my old phone.
If I tried a stock-based ROM though, it must have everything working though. I mean everything: calls, texts, LTE, bluetooth, speaker phone, etc etc.
EDIT: OH MY GOSH!!!!!!
I just found where the libiq_client file went. I moved it to my internal storage.
Well, good to know I wasn't totally stupid and knew not to completely delete the file! Unfortunately I was still dumb enough to misplace it....
spexwood said:
EDIT: OH MY GOSH!!!!!!
I just found where the libiq_client file went. I moved it to my internal storage.
Well, good to know I wasn't totally stupid and knew not to completely delete the file! Unfortunately I was still dumb enough to misplace it....
Click to expand...
Click to collapse
Better to misplace than to delete it, trust me
Post results.
zamajalo said:
Better to misplace than to delete it, trust me
Post results.
Click to expand...
Click to collapse
I can see that as being true LOL
I'll need some time to test this, but I'll definitely post results ASAP.
spexwood said:
I can see that as being true LOL
I'll need some time to test this, but I'll definitely post results ASAP.
Click to expand...
Click to collapse
Libiq.so enables carrier IQ, its removal should only help battery drain, not cause it.
Just to ask, have you tried adjuating wifi scan interval? You can try as well the xposed module, "wifi deep sleep". Helped minimize my wifi related drain
I even broke my phone with App Ops trying to figure it out, disabling wake permissions for most apps which caused FC's and even reboots. I have since restored all permissions but I still get FC's whenever I leave an app or switch out of it. Not sure if it's really crashing, but I get a FC message every time. So much so that Substratum turned off its theming for Files because it "crashed" after every screenshot was successfully uploaded to this post. Btw I just removed CrossBreed Lite and it seems to have helped. So far no reboots doing the same stuff that caused reboots! Not sure why it caused problems though. I used it for a few days with no issues.
Anyway, back to my battery woes. 30-40% kernel system usage. Why is this happening? Even Snapchat which is abusing wake locks is nothing compared to kernel system.
I'm running the latest build of AIM 8.1 with EX Kernel. I have just visited the other thread about tweaking governer values to optimize battery life so I'll report back with results although I doubt that's relevant to my battery drain.
I've Googled quite a bit on the subject and it seems that each case is different. Usually caused by a certain bug, although a lot of people say it's "normal" which I strongly disagree with.
Update: optimizing the CPU has definitely made an improvement, but the kernel battery drain still exists.
Could it really be pick up to wake and wifi search behind the drain? Isn't this phone supposed to have a sensor hub that allegedly allows for all sensors to constantly be on while using minimal power? I never noticed this drain on any other phone with both of these features on.
Anyway, I disabled pick up to wake and I'll start trying to remember to turn off wifi when not in use.
I think you're trying too hard and running a bunch of stuff. The kernal usage looks about right. I wouldn't run Gsam and BBS at the same time. They can fight each other. What makes you think there's a problem? Nothing jumps out at me.
Sent from my [device_name] using XDA-Developers Legacy app
I also can't see anything out of the ordinary, except this one picture where it shows the phone being active while dozing. I don't know how to understand that because I don't use that app, maybe I'm reading it wrong. What does Android's built-in battery monitor show? Is it dozing properly while screen is off? What is your average SOT? Is your mobile signal strong? I'm also using AIM 8.1+EX combination with satisfying results. Is your radio up to date?
maybe Wakelock Detektor or Greenify can help you.
And if you currently have things crashing all the time, start with a factory reset. Much easier to diagnose the cause when the apps aren't doing random stuff.