Hi guys,
I got a really annoying issue with my 1+1, got my phone for 2/3 months.
I did already a lot to fix this issue but couldn't find a fix.
Battery status: battery savings..
Pics:
http ://imgur.com/a/dMmVb
Does anyone know a trick to fix the android system draining bug?
Your screenshots show absolutely no information. You need root and one of the following apps,
- BetteryBatteryStats
- GSam
- Wakelock Detector
Root required. From that point on, you'll know what app is causing your battery to drain via partial wakelocks and alarms.
Have you tried a fresh stock install of 38 r? Ota seems to result in poorer performance. Assuming your using 11s?
Disable "wake lock" and "stay awake" in Privacy guard to Google play services.
Related
I've noticed that periodically I'd get a very long lasting wakelock. It doesn't seem to cause horrendous battery usage, per se, but it does seem to keep the phone up for a long time, and so I'd notice that battery performs slightly worse than usual.
BBS shows a wakelock caused by EntriesRefresh_wakelock, and under Running App, I'd see an entry for Google Search (EntriesRefreshIntentService).
Running - Omni Rom (latest)
Faux Kernel ( No custom settings)
noobismyname said:
I've noticed that periodically I'd get a very long lasting wakelock. It doesn't seem to cause horrendous battery usage, per se, but it does seem to keep the phone up for a long time, and so I'd notice that battery performs slightly worse than usual.
BBS shows a wakelock caused by EntriesRefresh_wakelock, and under Running App, I'd see an entry for Google Search (EntriesRefreshIntentService).
Running - Omni Rom (latest)
Faux Kernel ( No custom settings)
Click to expand...
Click to collapse
Might be worth your while posting in the better battery stats thread. They are good at diagnosing wakelocks
Here's a link: http://forum.xda-developers.com/showthread.php?t=1179809
BuT_TeR said:
I've noticed that periodically I'd get a very long lasting wakelock. It doesn't seem to cause horrendous battery usage, per se, but it does seem to keep the phone up for a long time, and so I'd notice that battery performs slightly worse than usual.
BBS shows a wakelock caused by EntriesRefresh_wakelock, and under Running App, I'd see an entry for Google Search (EntriesRefreshIntentService).
Running - Omni Rom (latest)
Faux Kernel ( No custom settings)
Click to expand...
Click to collapse
I had the same issue, so disabling Google now (opening Google now, settings, toggle it off) has stopped this wakelock for me!
Sucks a bit to turn it off, but I'd rather not have the wakelock than have good now info, I'll just wait for an update/fix.
YoHoJo said:
I had the same issue, so disabling Google now (opening Google now, settings, toggle it off) has stopped this wakelock for me!
Sucks a bit to turn it off, but I'd rather not have the wakelock than have good now info, I'll just wait for an update/fix.
Click to expand...
Click to collapse
Hopefully this works, what kinda **** is this google..
I've been playing around with some 4.4.2 nightlies (Slim, PA, CM, Gummy, OSE, etc) and I've noticed that all of them have some battery stat issues.... the stock battery app is registering the phone as awake 100% of the time (verified with other apps as not accurate)... and secondary battery apps like GSAM, BBS, WLD, all show odd information. GSAM (companion installed as system app) shows the correct totals for a module's total "held awake" time, but the actual wakelocks all have the same count and time (which all add up to the overall total... it's guessing). WLD also shows (totals are OK, but individual stats are junk). BBS isn't/can't filter out the zero'd stats and some of those stats are shown in such a way that it looks like it lacks some specific information and is trying to fill in the gaps.
I know Google messed with battery stats a bit to lock them down... I've installed the GSAM companion as well as the Xposed module to open them back up again. But this doesn't explain the STOCK battery app's problem in getting accurate results.
Anyone else see this? I've been trying to track down a wlan_ctrl_wakelock problem when I load 4.4.2 ROMs, but without the granular power stats, I really can't see anything of use (and what IS there, I can't really trust).
Is this just a case of things being too new with KK?
I'm on cm11 12/21 and ever since the battery stuff was changed back around the 12/16 nightly things have been weird. My stock battery app shows zero awake time, but GSam and BBS show the correct wake times (also have GSam companion and Xposed module for KK battery stats).
The problem appears in those apps when I try to see partial wakelocks - they're all ridiculously low, like 15 seconds with a 20 hour uptime. BBS says all the wakelocks are kernel wakelocks, buy when you check those it's all just PowerManager wakelocks, which are all the partials lumped together
For a wlan_ctrl_wakelock you can try the app Network Log - if you're getting those wakelocks, you'll see a lot of packets bouncing around from your phone to your router, or other traffic on the router (specifically if the kernel is sending/receiving a bunch of packets)
Sent from my SCH-I535 using XDA Premium 4 mobile app
scorchedsky said:
I'm on cm11 12/21 and ever since the battery stuff was changed back around the 12/16 nightly things have been weird.
Click to expand...
Click to collapse
Pretty much. I just loaded a nightly from last night... battery stats got fixed in the base code from the looks of it.
Thanks on the logging app... going to give it a look.... might just be a simple adjustment in my network, I hope.
There is more drain than 4.3 roms, but I'd venture to say it's related to coding of the device to the framework and it will improve as the roms advance. Wakelocks are the main culprit so get Better Battery Stats and see what's keeping the device awake.
For wlan, turn off wifi scanning in advanced wifi options.
Looks to me like there is a higher idle drain with the OTA/OTA Incremental update.
I'm seeing a 3-4x increase in amperage draw.
7-9mA before the update.
30-40mA after the update.
Nothing new installed.
Is anyone else seeing the same problem?
May have to go to my backup if this doesn't somehow fix itself.
My battery hasn't been great from the beginning. This update does seem to have made it significantly worse though.
It's starting to seem like it's worse than my Nexus 5!
mbudden said:
Looks to me like there is a higher idle drain with the OTA/OTA Incremental update.
I'm seeing a 3-4x increase in amperage draw.
7-9mA before the update.
30-40mA after the update.
Nothing new installed.
Is anyone else seeing the same problem?
May have to go to my backup if this doesn't somehow fix itself.
Click to expand...
Click to collapse
Turn off the " OK google " stuff , i had experience of it waking up device quite often and draining my battery, try turning them off ...
Other place to look out for what is walking up your device most of the time and deny them the access to wake up your phone , to hunt those apps , check
settings -> privacy -> privacy guard -> menu -> advanced -> device tab .
I found my facebook app / google play services was constantly waking up my device when on sleep , i denied "keep awake" to boost some more battery life ...
Hope that helps
For the first day, the phone was wakelocked by google play services. I used privacy guard to block it and unblocked it after a day and the drain has disappeared.
kokocabana said:
For the first day, the phone was wakelocked by google play services. I used privacy guard to block it and unblocked it after a day and the drain has disappeared.
Click to expand...
Click to collapse
For me it's been Android OS. It's used more than twice the battery as the screen and in 6 hours off battery has had 2 hours of "keep awake."
As a note I had disabled the google play services that was causing the drain when I first got the phone last month.
Vote for the issue here!
https://jira.cyanogenmod.org/browse/BACON-599
In wakelock, the process that are the cause of the most wakelocks are : ActivityManager-Launch, LocationManagerService, SyncLoopWakeLock and RILJ, anyone knows how I can fix this?
I've tried to disable and enable location, still getting Android System or Android OS as causing the most battery drain. This started yesterday, before, I didn't have it.
Hey guys.
Lately whenever I'm flashing a new kernel either on KitKat or Lollipop I get terrible wakelocks that kill my battery. Not sure why this is happening. I'm using CWM. Basically after flashing I can just notice a huge battery drainage and I tend to install either GSam or WakelockDetector to see what's the problem. WakelockDetector (Rooted) gives me an overall idea of my battery problem. Usually SystemUpdateService, Audiomix "1013", "NlpWakeLock" , "EventlogService" and "CheckinService" drain my battery the most. Sometimes "ConfigFetchService" as well.
Thanks
KodRoute said:
Hey guys.
Lately whenever I'm flashing a new kernel either on KitKat or Lollipop I get terrible wakelocks that kill my battery. Not sure why this is happening. I'm using CWM. Basically after flashing I can just notice a huge battery drainage and I tend to install either GSam or WakelockDetector to see what's the problem. WakelockDetector (Rooted) gives me an overall idea of my battery problem. Usually SystemUpdateService, Audiomix "1013", "NlpWakeLock" , "EventlogService" and "CheckinService" drain my battery the most. Sometimes "ConfigFetchService" as well.
Thanks
Click to expand...
Click to collapse
[Battery Life Help] Troubleshoot battery issues here!
Application wakelocks have absolutely nothing to do with the kernel.
Keep in mind a "wakelock" is simply a request to keep the device awake; they can happen regardless whether the screen is on or off, they are only an issue if they occur while the screen is OFF.
SystemUpdateService is a pretty obviously named wakelock, it's used while an OTA is being downloaded. You can disable the service and it's receivers with an app like Autorun Manager (https://play.google.com/store/apps/details?id=com.rs.autorun, open in advanced mode, go into it's settings to enable for system apps, tap on Google Play Services, disable everything with SystemUpdateService in it's name).
AudioMix is triggered every time there is an audio event, including touch sounds. Harmless as it's usually only used while the screen is on.
NlpWakeLock is a location wakelock.
EventlogService and CheckinService are harmless, unless they occur 24/7 and don't go away EVER, which means you disabled their services but not their receivers.
ConfigFetchService is mostly harmless, it simply fetches your settings from Google's servers when you open a Google app, if that app stores it's settings on the cloud instead of locally.
Lethargy said:
[Battery Life Help] Troubleshoot battery issues here!
Application wakelocks have absolutely nothing to do with the kernel.
Keep in mind a "wakelock" is simply a request to keep the device awake; they can happen regardless whether the screen is on or off, they are only an issue if they occur while the screen is OFF.
SystemUpdateService is a pretty obviously named wakelock, it's used while an OTA is being downloaded. You can disable the service and it's receivers with an app like Autorun Manager (https://play.google.com/store/apps/details?id=com.rs.autorun, open in advanced mode, go into it's settings to enable for system apps, tap on Google Play Services, disable everything with SystemUpdateService in it's name).
AudioMix is triggered every time there is an audio event, including touch sounds. Harmless as it's usually only used while the screen is on.
NlpWakeLock is a location wakelock.
EventlogService and CheckinService are harmless, unless they occur 24/7 and don't go away EVER, which means you disabled their services but not their receivers.
ConfigFetchService is mostly harmless, it simply fetches your settings from Google's servers when you open a Google app, if that app stores it's settings on the cloud instead of locally.
Click to expand...
Click to collapse
Disabling the receivers works indeed. Thanks! By the way, another issue I'm having is that my Nexus 5's CPU heats too fast operating in UI and doing basic stuff, like installing apps from Play Store or watching videos on YouTube. Normally after about 5 min. of running if I go to System Monitor the CPU's temp is around 40-47ºC on action, in standby cools down to 34-35ºC but then after I use it again the temp rise to 45-47ºC. Usually when this happens the battery's temperature is also triggered and reaches 28-30ºC. Is this normal?
KodRoute said:
Disabling the receivers works indeed. Thanks! By the way, another issue I'm having is that my Nexus 5's CPU heats too fast operating in UI and doing basic stuff, like installing apps from Play Store or watching videos on YouTube. Normally after about 5 min. of running if I go to System Monitor the CPU's temp is around 40-47ºC on action, in standby cools down to 34-35ºC but then after I use it again the temp rise to 45-47ºC. Usually when this happens the battery's temperature is also triggered and reaches 28-30ºC. Is this normal?
Click to expand...
Click to collapse
The CPU throttles at 65C by default (some kernels change this or give you an option to change it), and shuts down at 105C. 47C is hardly anything.