Develop Bugs

Battery drain is ridiculous...please help

My battery is draining like CRAZY and i cant seem to find out what the issue is. Ive tried calibration several times and using a task manager that turns off running apps every few seconds(which seemed to make it worse) and that didn't help. Auto updates are turned off and fbook is only set to update every hour and brightness is set to minimum yet my battery only seem to last 8hrs. please help. i would really like to pinpoint what the issue is.
Oh...im running ERA Legendary 2.1, CPU speed and voltages are stock

That screenshot is worthless. It doesn't show anything useful. Percentages are meaningless. Get Betterbatterystats to see what is running as far as processes and partial wakes. Get CPUspy. To make sure your phone is going into deep sleep. Get Memory Booster Lite to see what is using your battery and get rid of the auto task killer. That will kill your battery fast.
Sent from my SPH-D700 using XDA App

kennyglass123 said:
That screenshot is worthless. It doesn't show anything useful. Percentages are meaningless. Get Betterbatterystats to see what is running as far as processes and partial wakes. Get CPUspy. To make sure your phone is going into deep sleep. Get Memory Booster Lite to see what is using your battery and get rid of the auto task killer. That will kill your battery fast.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
i only posted the screen shot to show the time vs percentage. i already got rid of the task killer and here is a screenshot from better battery stats. idk how to stop the processes though...

Again the percentages mean nothing. In Gingerbread everything goes through Android system so it will always be highest. If you use your phone only an hour or two a day then it will drop to around 60% with cell standby getting higher. They will always add up to 100% whether on a minute or 10 hours.
You didn't post the partial wake locks screen. Also did you check CPUspy for deep sleep? Did you uninstall the autokiller? You can go into settings>applications>running services and stop applications that shouldn't be running like Facebook or music and video players, etc. Sometimes it's best to get an app like Bloat freezer and freeze apps that keep reloading if you don't use them often.

CardnalSyn said:
My battery is draining like CRAZY and i cant seem to find out what the issue is. Ive tried calibration several times and using a task manager that turns off running apps every few seconds(which seemed to make it worse) and that didn't help. Auto updates are turned off and fbook is only set to update every hour and brightness is set to minimum yet my battery only seem to last 8hrs. please help. i would really like to pinpoint what the issue is.
Oh...im running ERA Legendary 2.1, CPU speed and voltages are stock
Click to expand...
Click to collapse
Another question and maybe the most important...what is your screen on time? I didn't see it in the screen shots. I think Max screen on Time I have gotten is right around 4hours. All the battery tweaks in the world wont help, if your screen is on a lot. Also...make sure to freeze drm, sns and system updates. Use randomlking's zip file.
If none of that works...wash, rinse, repeat. Wipe clean and reflash, rom and kernel.
Sent from my SPH-D700 using xda premium

As I'm sure you know, everyone's battery drainage is widely independent. However; I'm on "stock" Legendary 2.1 and recently with the updated Samurai kernel as well and run Juice Defender Ultimate. I've got some advance settings set but over the past 3-4 days, I average about 20 to 22 hours on a single charge.
My usage in an average day is: about 20-30 texts, about 10 minutes of phone calls, 10-12 emails in and out, 10 minutes of web, whatever app updates there may be and maybe about 15-30 minutes of light to medium use games.
If JDU is something you might want to look into, I would be more than willing to post my setup to get you started. <--For some reason, people are real stingy with their JDU settings.

This kinda thing just happens sometimes, and usually clears up on it's own. Especially common after flashing new software.
sent from my secret underground bunker

[Q] High "Awake" vs "Screen On" time

Let me preface this by saying I'm not complaning about battery life as 36h is very good. That said, I feel like my phone is awake much longer that it should be. Anyone have any ideas why my Awake time is so much higher than my Screen-on time?
Once again, I'm not complaining but considering my phone was awake almost 5x longer than the screen was on, I feel like I could squeeze some more life out of the phone. I had 1 exchange account @ 15min, 1 gmail on push, no talk/g+, ~2-3 hours off wifi (4g), gps on, bluetooth off, 4.0.4, leanKernel.
When analyzing the wakelocks, I don't see anything that would explain almost 6 hours of extra awake time:
Considering most of this charge I was on wifi, I think I should have been able to achieve more than 1.5h screen-on time. Especially when I see people getting 4-5+ hours on theirs. What could be causing this seemingly excess awake time?

Since those screen shots, I've done another full cycle and here are my results. Same settings as before. It looks as if I did a bit better with the ratio of awake vs screen on, but I still only got ~20 hours. I'll admit, this had much more 4g time and heavier usage.
As you can see it's better, as it was only awake about 3x as much as the screen. You can see where I was at home in the second screenshot (The long bar of wi-fi) and that included me sleeping yet it shows that the phone was consistantly waking up overnight without any usage. Short of "email", I'm not sure what could be causing it. I got MAYBE 3 e-mails overnight.
Signed out of talk/g+/latitude
Location services was NOT disabled in either set of screenshots. Disabled it and charging now. Maybe that will help?

Have you checked out your wakelocks using BetterBatteryStats (found here on XDA)? Also, download CPU Spy from the market and check how long your phone is in what state. If it isn't in deep sleep too often, you might have an app or service keeping your phone awake. Background Data of any kind usually does that. Also, the first culprit I would investigate is Google Maps. Uninstall that bad boy and test your phone out. I am betting you that 60% of the time, the problem with your phone being awake too often is with Maps running unnecessarily in the background. And to be clear, Maps self-restarts itself even after logging out of Latitude and closing the app completely

armanatz said:
Have you checked out your wakelocks using BetterBatteryStats (found here on XDA)? Also, download CPU Spy from the market and check how long your phone is in what state. If it isn't in deep sleep too often, you might have an app or service keeping your phone awake. Background Data of any kind usually does that. Also, the first culprit I would investigate is Google Maps. Uninstall that bad boy and test your phone out. I am betting you that 60% of the time, the problem with your phone being awake too often is with Maps running unnecessarily in the background. And to be clear, Maps self-restarts itself even after logging out of Latitude and closing the app completely
Click to expand...
Click to collapse
I have attached all the wakelocks to the previous two posts. I didn't attach CPU spy but I did check it every time. Usually it's between 60-80% but most often it's >70% in deep sleep.
Just did a fresh wipe with a app restore using the market. Location services have been disabled. I have uninstalled all gMaps updates and disabled the app. Is this good enough? Should I convert to user and uninstall using TB?

Just wanted to chime in and say I'm seeing a very similar profile to what you posted. And I'm not entirely sure, but I think this started when I flashed this ROM. What I feel like I'm seeing is that active use of the phone seems to be more of a drain than it used to, but I'm not sure how much of that would be placebo (i.e. remembering when I first got the phone around the holidays and there were a lot of relaxed days at home with constant wifi).
But right now I'm seeing 5.5 hours of awake time and 1 hour of screen on time, with 27% remaining. Total time is 42 hours, which seems to round everything out to a decent battery life, but again, 1 hour of use for 70% of the battery seems lower than what I remember. Not sure if a vote for seeing the same behavior is one for this being normal or us both having the problem, but I can try to post screenshots/more detailed info later if it would help.
This is on the above linked rom with stock kernel, 4.0.4 radios.

That's the same ROM I'm using and I agree, 70% usage for 1h screen time seems too much. I've seen people get over 2.5h screen on time on pure 3/4g
I'm going to see if disabling maps and location services help. Will report back.
I would be interested to see any SS you have, might help.
Sent from my Galaxy Nexus using XDA App

This is after a fresh wipe, fresh kernel install, no maps, no g+, no gTalk, no GPS, no location services, just gmail and 1 exchange @ 15 minutes
Any advice as to what's going on would be very helpful. Thanks in advance.

I also have a problem with wake-locks.
Since phone is relatively new ~2weeks its still stock 4.0.2 GSM. After some time my battery life fell and thanks to XDA i think i found the problem Google backup.
I disabled Google backup to see if i get the same awake time tomorrow.
If the problem doesn't go away, is it possible to resolve this problem without factory reset of the phone?

Here are some screenshots I made the other day, taken a bit into a charge but immediately prior the phone was down to <6%. Didn't get a capture of the kernel wakelocks but as you reported, the screen on time falls far below the wake time, and the wakelocks don't seem to come anywhere near to explaining the difference.
I just installed the 6.3.0 google maps, which claims to increase battery performance for location and latitude services. I'll try to make a comparison next time my battery is drained.
I've signed out of latitude before but generally don't redo this upon rebooting the phone. Does it sign in by default on every reboot?

Well after disabling backup thing im still getting 90% wake time from backup service so i will try to do a factory reset over weekend and hope it goes away... Will post resoults in case some 1 else gets this problem.

JoeSyr said:
Here are some screenshots I made the other day, taken a bit into a charge but immediately prior the phone was down to <6%. Didn't get a capture of the kernel wakelocks but as you reported, the screen on time falls far below the wake time, and the wakelocks don't seem to come anywhere near to explaining the difference.
I just installed the 6.3.0 google maps, which claims to increase battery performance for location and latitude services. I'll try to make a comparison next time my battery is drained.
I've signed out of latitude before but generally don't redo this upon rebooting the phone. Does it sign in by default on every reboot?
Click to expand...
Click to collapse
This looks to me like some sort of Maps issue. Try to uninstall/disable maps and see if it goes away. Looks like it's stuck trying to locate you with maps somehow based on those wakelock names.

Catoss said:
Well after disabling backup thing im still getting 90% wake time from backup service so i will try to do a factory reset over weekend and hope it goes away... Will post resoults in case some 1 else gets this problem.
Click to expand...
Click to collapse
Hopefully the factory reset will fix it, that is an odd problem.

It seems to me like my problem was the version of leankernel I was using. I went from 10.0exp2 to 2.01exp2 and it's much much better

Actually, the kernel upgrade did not fix my problem. I did seem to figure out what was happening though.
This entire time I've noticed that my phone would standby and sleep very well on Wi-Fi but when I switched to data it seemed as if I would bleed juice. I discovered that my "Keep Wi-Fi on during sleep" was set to "always" and I believe that was causing my excess wakes.
I've changed it to "Never" and I'm doing some tests. I'll be sure to report back if anyone is watching this thread.

Timdor said:
Actually, the kernel upgrade did not fix my problem. I did seem to figure out what was happening though.
This entire time I've noticed that my phone would standby and sleep very well on Wi-Fi but when I switched to data it seemed as if I would bleed juice. I discovered that my "Keep Wi-Fi on during sleep" was set to "always" and I believe that was causing my excess wakes.
I've changed it to "Never" and I'm doing some tests. I'll be sure to report back if anyone is watching this thread.
Click to expand...
Click to collapse
mine is opposite of that, i standby fine on data but terribly on wifi. im guessing that is background syncing. i just have to figure out what is doing it

i have my wifi set to never too for better battery life. It seems counter intuitive, but wifi is better on power than 3g/4g. So preventing the phone from leaving wifi back to cellular is better for battery. All my phones have been like this.

yeah thats what i thought it does but mine drains faster on wifi...i leave it on cause i barely get signal in my room an if i sit on 3g it just takes a long time to do anything

What type of drain do you get over 3g vs wifi?
Yesterday I was playing around on 3g all day and I was seeing an average of 6%/hr. My phone is consistantly awake 20-25% of the time according to betterbatterstats. Screen on will always be far less than half of my awake time. Wifi drains around 1%/hr
I did a wipe of my 4.0.4 install and flashed a fresh kernel download. I'm not logging into exchange because, for some reason, I think that's my problem.

Also, changing to Never didn't really fix my issue.

[Q] Dumb wakelocks, wakeups, help?

Upon loading up BBS, I come across these rather annoying wakelocks:
"wlax_rx_wake" (37m)
"battery-monitor" (27m)
"wlan_wake" (13m)
"mdm_hsic_pm0" (12m)
Partial Wakelocks:
"NetworkLocationLocator" (2m)
Basically, these are repete foes. Their times vary, but they're always there. Sometimes, they go up to hours.
Also, I'm noticing that Maps always has a top 3 spot in my battery usage (using the stock battery info). I'm not using maps, I have location services turned off, but it's always there. I tried clearing the data, didn't do a thing.
Last, I've noticed that many apps "wake up" my GN2 (found it in BBS). Ebay Mobile woke it up over 700 times, so I uninstalled that. Maps wakes it up over 300 times, not even sure why.
Android OS also has a "stay awake" time of 3h, 49m, 45s.
What's going on? How can I solve these issues?
I'm on Jedi 3.3.

Android os is, well, android os, some usage will always be there to run your phone.
That said, if 37 min wakelocks in the span of a full day, is not much. Wakelocks are necessary for some services to run. If you have maps wakelock for several hours with location services off, my guess is an app that is badly coded is checking for location even though it's off.
It would be helpful with a screenshot of kernel and partial wakelocks.
Sent from my GT-N7100 using Tapatalk 2

Here are some screens, keep in mind that they have been much, much worse on my past charging cycles.
Oh and the maps data in these is after I killed maps, dug deeper to disable location services, and wiped maps' data.
37 minutes is the span of after a reboot, I'd say about 6 hours. They've increased (in the screens) over the past few hours. Pre-reboot, the wakelocks were up in the 1.5-2hr mark.

Please post with "since charged" or unplugged, since battery stats shows thirteen hours uptime.
The maps lock is only 3 mins and negligible, despite the intimidating red line You might rather have an app using wifi constantly unless you've actively been using wifi for a long time, or you have bad signal or a poorly configured wifi.
Sent from my GT-N7100 using Tapatalk 2

for the first time ever my phone drained 10% or more over night, its never done that before even though i had every off.. and i did the same as i normally do, but for some reason it seemed to have drained a lot more last night

Ah, I'll have to post those tomorrow. I don't have a reference point saved it says.
That 3 minutes used to be close to 30 before I wiped the data and rebooted, I'm only concerned because maps is showing up as one of my battery killers in the stock battery info dialog, even though I haven't used it all day.
I did see through Watchdog that "friendservice" and its related processes have been running up pretty high, but I have latitude and everything else disabled?

Event log service battery drain

I currently have a problem that "Google services -> event log service" is draining my battery a lot,
I was asking this in another thread about this problem but got told I should ask here in the specific forum for my phone.
I fully charged it during night and at 2:30am I rebooted the phone and unplugged the charger.
Now in the afternoon at 5pm I checked again (haven't used the phone since then) and battery was at 62 %
Wakelock detector is showing an activity of Google-services/Event log service with 1 hour 43 minutes.
Wlan off, 3G on, GPS off, bluetooth etc off.
I disabled all unessesary syncs including google backup/restore, not helping at all.
I checked developer settings for log recording etc.. but everything is off.
It's the international E975 model btw,

I have the same issue. I think i tweaked it too much lol.
Partial wakelocks in BBS indicates EventLogService has been on for 5h.. -_-
Have you done any tweaks to it? I.e: freeze anything from titanium, greenify, etc

This is a result of frozen apps.

jiexi said:
This is a result of frozen apps.
Click to expand...
Click to collapse
hi there
so if i check what apps are frozen and uninstall them, this will get rid of the problem basically, that simple??

It may just cause more problems. The reason the wakelock is even appearing as event log service is because the app is frozen, but causing wakelocks. But wait, didn't we freeze it?.. how can it still be causing wakelocks? Some other system level app is still capable of waking it, so it may or may not be something important.

jiexi said:
It may just cause more problems. The reason the wakelock is even appearing as event log service is because the app is frozen, but causing wakelocks. But wait, didn't we freeze it?.. how can it still be causing wakelocks? Some other system level app is still capable of waking it, so it may or may not be something important.
Click to expand...
Click to collapse
cheers, actually i have LOTS of wakelock time taken from these 2:
1) Alarm Manager - Android System. this one grows by 5 units every time i unlock the phone and check, NORMAL??
2) Event Log Service - Google Services, this one is a bit more quiet but still growing silently.
Things i have on:
usually sync, but those 2 above grow regardless of sync being on or off, then i have 2 alarms in the calendar, one active and one not and some calendar notifications.
are those responsible? right now my phone is doing around 2% battery use but i notice that it grows very easily, just now i lost 1% in only 25 minutes.
the "awake" graph under battery looks strange.. sometimes it matches screen off (so good), sometimes, it seems to be on, with screen OFF for no reason whatsoever.
any idea?
thanks

Doze hasn't worked since 6.0.1 OTA - anyone else?

Since getting the OTA, Doze hasn't worked at all. I haven't installed any new apps, and am stock/unrooted. Here's the battery graph from last night with the phone sitting on the nightstand.
Any ideas?

Same here. So you had a flat line before the update?

Yep, flat line before the update. Here's the detailed battery view (4% after my first screenshot, but serves the same purpose). Looks like something is keeping the phone awake but nothing else changed outside of updating the OS.
I restarted and that didn't help. Maybe it has to re-optimize.

Doze appears to be working on mine but I've only had it for a day and am using it a lot. When not in use for an extended period of time the battery graph completely levels out and doesn't decrease at all. Then again I think I've only gone about 20 minutes without touching it since I took it off of the charger this morning.

Check your Developer Options > Running Services for any suspicious activity.
I had Google Maps "offline Maps service" hammering my device during sleep the other day even though I've never saved an offline map yet.

See attachment for Doze. It works better on my 5x than 6p. I'm not sure why. Total flatline.

Looks solid to me

Hi,
You can see if Doze is active if you have any app that records data periodically. Leave it running over night and you should be able to see a reduction in samples in the early morning. For example, when logging current usage with "Current Widget", when Doze kicks in the sampling slows way down. If I leave it on overnight set to take a sample about once a minute by the time I wake it is 2 to 3 hours between samples. I've had higher current drain when I though Doze wasn't working, but upon looking at the Current Widget log file, I could see that Doze was active.
Frank

mtca said:
Hi,
You can see if Doze is active if you have any app that records data periodically. Leave it running over night and you should be able to see a reduction in samples in the early morning. For example, when logging current usage with "Current Widget", when Doze kicks in the sampling slows way down. If I leave it on overnight set to take a sample about once a minute by the time I wake it is 2 to 3 hours between samples. I've had higher current drain when I though Doze wasn't working, but upon looking at the Current Widget log file, I could see that Doze was active.
Frank
Click to expand...
Click to collapse
Wait, Current Widget actually works properly with you with the 5x? It rarely updates for me. All software current monitoring tools seem to do so.
I figured it must be something with how the power regulation works on this device.
With my Nexus 5 it would update exactly as intended and could be plotted on the graph, until the phone entered deep sleep then the updates became infrequent. This was on Lollipop before Doze existed, so that tells me that it is because of Deep Sleep not Doze.

bblzd said:
Check your Developer Options > Running Services for any suspicious activity.
I had Google Maps "offline Maps service" hammering my device during sleep the other day even though I've never saved an offline map yet.
Click to expand...
Click to collapse
You may have solved my problem. Using Wakelock Detector, I saw that Google Maps was slamming my phone too keeping from dozing. I deleted my offline maps and disabled the option. Hopefully that fixes it for me