Related
Google services is to battery consumer because it keeps phone awake. Something to do with location services causing it based on screenshot below. I'm latest nightly CM and seems to be the only one affected by this issue since nobody else complained about it
Sent from my SGH-I337 using Tapatalk 4 Beta
Same crap here as well. As u can see I'm on a totally different device. There was another thread on it with no solution I think.
---Sent from a viperx-ed OneX
Turn network location off. You really don't need it on all the time. That's the only way I know of getting rid of that wake lock.
I just realized. Location reporting turned itself back on, on maps app
I turned it back off. Will see if that helps.
When it was off I'd probably get 1min of that wakelock for the entire day.
---Sent from a viperx-ed OneX
mibtnt said:
I just realized. Location reporting turned itself back on, on maps app
I turned it back off. Will see if that helps.
When it was off I'd probably get 1min of that wakelock for the entire day.
---Sent from a viperx-ed OneX
Click to expand...
Click to collapse
If its of from boot, I don't get any.
jd1639 said:
Turn network location off. You really don't need it on all the time. That's the only way I know of getting rid of that wake lock.
Click to expand...
Click to collapse
x-actly.
NLP stands for Network Location Provider I would guess as it appeared to me first when Google Location Services asked me to switch on the WLAN location detection for "more accurate results".
Might be helpful if in some building where you don't get GPS locked but isn't really needed that much otherwise.
i have location access OFF and have HUGE DRAIN on Nlpwakelock
I had a similar problem on my Nexus4 - after I turned location services on and off again, the NlpWakelock would keep my phone awake and not go to deep sleep.
However, I found a fix for this issue. The culprit service is called GoogleLocationManagerService, and the solution is to disable this service only (I have no idea what other complications may arise from this, but at least my phone now goes to deep sleep). This service can be disabled with ROM Toolbox or a similar app.
In ROM Toolbox you go to App Manager, find Google Play Services and select Advanced Freeze. Now find the service (has a red border) called GoogleLocationManagerService and disable it. Now I can switch on and off location and still go to deep sleep, and location IS working.
ameinild said:
I had a similar problem on my Nexus4 - after I turned location services on and off again, the NlpWakelock would keep my phone awake and not go to deep sleep.
However, I found a fix for this issue. The culprit service is called GoogleLocationManagerService, and the solution is to disable this service only (I have no idea what other complications may arise from this, but at least my phone now goes to deep sleep). This service can be disabled with ROM Toolbox or a similar app.
In ROM Toolbox you go to App Manager, find Google Play Services and select Advanced Freeze. Now find the service (has a red border) called GoogleLocationManagerService and disable it. Now I can switch on and off location and still go to deep sleep, and location IS working.
Click to expand...
Click to collapse
i've been searching for a solution for ages and even followed the advice of another thread to disable location finding on both maps and google now and for some reason the nlpwakelock is still showing up. i'm going to try your fix but i was wondering if you've encountered any issues ever since disable googlelocationmanagerservice?
I often noticed nlpwakelock being the main culprit for Google Services battery usage. I even saw that it kept my phone awake for hours some days...
I tested some fixes and found that disabling the "use wireless networks" in the location services settings completely removed that wakelock.
Personally, I'd rather have that feature than save the little battery it uses. Despite keeping my phone awake for 1-2 hours on most days, as reported by GSAM Battery Monitor and Wakelock Detector, it uses a pretty small amount of battery:
Typically my phone's battery monitor will report about 20-30% of the battery used by Google Services. GSAM Battery Monitor seems to break that down into two parts: about 10% Google Services and 15% kernel, on average. However, these numbers are deceiving. That 10% that Google Services is only 10% of "App Usage" as reported by GSAM. Furthermore, App Usage is often only about 50% of my battery usage.
If my battery is at 50%, that means Apps only usage 50% * 50% = 25% of my 100% battery. Then, Google Services only used 10% of that 25%...so 2.5% of my overall battery capacity. I found this quite surprising considering the report that the wakelock keeps my phone awake for 1-2 hours...
So while Google Services is often shown as my #1 or #2 battery user in the App Sucker page, at 10-15% usually, that's only like 2-5% of the total 100% battery capacity each day. If I'm really going to be pushing my battery limits I might disable it to save some juice, but generally I find it's not worth disabling the feature to save such a small portion of my battery.
ender127 said:
i've been searching for a solution for ages and even followed the advice of another thread to disable location finding on both maps and google now and for some reason the nlpwakelock is still showing up. i'm going to try your fix but i was wondering if you've encountered any issues ever since disable googlelocationmanagerservice?
Click to expand...
Click to collapse
Hi. No, I've not had any issues,*but unfortunately the fix doesn't always work - but if the wakelock still persists, shutting down the service or location service again removes the wakelock, but it takes the manuel action of re-disabling the service again. Still better than having a wakelock though..
So I posted this in a different thread but figured I would post it here to see if anyone could duplicate my findings. I have a Note3 from T-Mobile and for whatever reason leaving the Wi-Fi on will not allow the phone to go into deep sleep mode. I noticed when I was down to 40% battery after 10 hours with only one hour of screen on time. After running some tests I had only 2 minutes of deep sleep those entire 10 hours (tested using BetterBatteryStats) I tried setting "Keep Wi-Fi on during sleep" to Never and unchecking "Always allow scanning" under advanced network settings but neither of them fix the issue. In fact, after several tests I concluded that setting never for "Keep Wi-Fi on during sleep" wasn't even functioning as my access points still showed the client connected while the phone was asleep.
Can anyone else confirm this issue is actually a bug and not just my phone being defective?
Here's my original post on the topic regarding how I found the problem and what I have tested so far:
OK so after only 2 days of owning this phone (got it late Monday night, the T-Mobile variant) I finally figured out why I'm getting such bad battery, and I suspect the same thing may be happening for the other people in this thread. Hopefully this information helps at least one person.
My battery stats was almost identical to all the other users in this thread that had bad battery, I would get barely around 10-12 hours on the phone with less than 2 hours of screen on time. After using multiple apps to track down the issue I finally got what it was.
Wireless. Yes, wireless was my cause. But the thing is Wi-Fi didn't show up at all in any of the battery apps so I assumed it was a non issue. I've had other phones and have always kept the wireless turned on the entire time without problems. The basic problem is not that Wi-Fi is using power itself but it's that by default the phone cannot enter deep sleep while connected to Wi-Fi. This is why trying to use apps like BetterBatteryStats will lead you nowhere initially (though they were useful in finding out what was causing the issue) You can discover this by turning on Wi-Fi and connecting the phone to a charger, then disconnecting it so your BBS information will reset. Then power off the screen and power it back on after 10 minutes. You'll notice in the other section that deep sleep will have less than a minute time while awake probably has close to 9 minutes, if not more. This is with everything else turned off, almost no apps, and no special Samsung stuff enabled.
Under Apps > Settings > Wi-Fi > Menu > Advanced there are two options that should help this: "Keep Wi-Fi on during sleep" and "Always allow scanning" I set the "Keep Wi-Fi on during sleep" to Never and unchecked Always allow scanning and rebooted the phone. And low and behold...nothing. Yes, these options don't work (at least not to fix this problem) The phone still won't enter deep sleep mode while the wireless is enabled. Based on my company's wireless devices I can see that even with the screen off for well over 10 minutes it still shows connected as a client meaning the wireless is not turning off properly while it's in sleep mode. Or perhaps it can't go into sleep mode because the wireless is on which stops it from going into sleep mode and turning off the wireless. My guess is that it's a Samsung bug.
The reason why there's so many people here to get good battery usage is because they're either used to turning Wi-Fi on only when needed and keeping it off. You'll also not notice it if you have more than 6 hours of screen on time because you could easily assume that it would make sense that you phone would only last 10 hours total with that much screen on time, even though it should have technically lasted 20+ hours with only 6 hours of screen on time if the phone could have entered deep sleep.
So what's the real fix for this? Unless it's by design my belief is that it's a bug and won't be fixed until Samsung/T-mobile notices. I can't test to see if the same thing happens on other carriers so if someone feels like testing this theory out it would help.
For now, I guess we're just left to manually turning Wi-Fi on only when needed and leaving it off in all other cases. For those that have the T-mobile variant, make sure you also go into Settings > General > Backup and reset > Collect diagnostics and uncheck the "Allow Diagnostics" as that will probably be the highest offender of Partial Wakelocks (it'll show up as com.carrieriq.tmobile.wakelock or System Manager Application)
If anyone wants more information on my testing let me know!
Click to expand...
Click to collapse
That's because the 'Keep WiFi during sleep: Never" setting only disconnects, it doesn't shut down the WiFi radio.
You're going to have to use a manager (Like Deep Sleep Battery Saver).
Or just hit the toggle yourself... If you're going to keep it disconnected in sleep anyway, just swipe down the notification bar and hit the bloody toggle.
ShadowLea said:
That's because the 'Keep WiFi during sleep: Never" setting only disconnects, it doesn't shut down the WiFi radio.
You're going to have to use a manager (Like Deep Sleep Battery Saver).
Or just hit the toggle yourself... If you're going to keep it disconnected in sleep anyway, just swipe down the notification bar and hit the bloody toggle.
Click to expand...
Click to collapse
The problem is that it doesn't disconnect, the access point 100% shows it is connected and transferring data every now and then. But the real issue isn't weather it disconnects or not but it's the fact that Wi-Fi will not allow the phone to go into deep sleep mode. For now I am fine with switching Wi-Fi off and on as needed, but with no other phone have I needed to do this before and definitely seems like a bug.
But regardless, what I'm trying to figure out if this is a legit bug that I should submit to Samsung/T-mobile or if it's just my phone and I should ask for a replacement. If anyone has BetterBatteryStats and could test this with their Note3 that would help.
My stupid phone has just started this same issue!!!! Freaking annoying, after only 8 hrs from 100% charged state, the battery is at 46% with only 26 mins screen ontime, I checked out that the phone never goes into deep sleep. What is going on and what can be causing this? Did you manage to resolve your issue?
PS I checked out wakelock detector but doesn't tell me a thing, as what program is keeping the phone awake all the time. Starting to hate this phone and miss my S3
What is your GPS accuracy setting set to? GPS, Wifi or Networks? Try setting it to GPS only.
GameBoiye said:
So I posted this in a different thread but figured I would post it here to see if anyone could duplicate my findings. I have a Note3 from T-Mobile and for whatever reason leaving the Wi-Fi on will not allow the phone to go into deep sleep mode. I noticed when I was down to 40% battery after 10 hours with only one hour of screen on time. After running some tests I had only 2 minutes of deep sleep those entire 10 hours (tested using BetterBatteryStats) I tried setting "Keep Wi-Fi on during sleep" to Never and unchecking "Always allow scanning" under advanced network settings but neither of them fix the issue. In fact, after several tests I concluded that setting never for "Keep Wi-Fi on during sleep" wasn't even functioning as my access points still showed the client connected while the phone was asleep.
Can anyone else confirm this issue is actually a bug and not just my phone being defective?
Click to expand...
Click to collapse
Well, your issue looks pretty similar to mine, which I solved with this Xposed mod (you could give it a try if you're on KitKat): http://forum.xda-developers.com/xposed/modules/mod-wi-fi-deep-sleep-t2752947. I was experiencing that even when "Keep Wi-Fi on during sleep" is set to Never, Wi-Fi still was awake most of the time according to battery stats.
This is after the 4.4 update.
I can't figure out the exact cause, but there are several occasions where I have left the phone idle for several hours, only to discover that the phone has not entered deep sleep, having instead been kept awake by Mediaserver the entire time. Unfortunately, I can't get access to the Partial Wakelock stats via BetterBatteryStats, but the time for the PowerManagerService.WakeLocks "container" under the Kernel Wakelock section roughly matches the awake time.
I have done some googling for solutions to this problem and most threads suggest a potential issue with media scanning (e.g. a corrupted .mp3 causing a background process to get stuck in a loop). However, I haven't been able to eliminate the problem with any of the proposed solutions.
However, the last few times this has happened, I have noticed that Bluetooth was enabled and paired with my headset. Also, in each case, the awake time for the Mediaserver process (under battery stats) continues to increment UNTIL I disable Bluetooth, at which point the awake time counter stops incrementing. Also, since I started paying closer attention to this behavior, I have yet to see the same deep sleep (i.e. wakelock) issue while Bluetooth is disabled.
I believe this is enough evidence to prove that the offending wakelock is somehow related to Bluetooth.
Does anyone else see this behavior?
I've seen it on other phones. And adding Bluetooth into the mix may make my advice unhelpful.... But that aside, rebooting after unplugging from charger every time has fixed that issue in the past.
Sent from my XT1058 using Tapatalk
Hi guys,
I have read countless threads on battery life & wake locks on XDA, Reddit, etc. Trying to find a solution to what I still find the Achilles heel of android, wake locks.
I am running stock on MHC19Q build
Adaptive brightness off
Wifi scanning off
Bluetooth scanning off
Battery Optimization on all apps except for DMService and Google Play Services
Some days I will go 2-3 hours with 30 minutes SOT and my battery only drops 10%. Doze works as it should. I will get through a full day at about 4 hours SOT (6am to 10pm).
On other days (like today) I am unplugged for 3 hours at 80% with 10 min SOT. I have rebooted the device 3 times since unplugging it and my wake locks are still occurring. My signal is perfect green through and through. Bluetooth off and connected to wifi.
I find the issue comes and goes. Some days the phone will start out great, only to have wake locks start occurring mid day. I think Android OS appears to be the issue.
Anyone else encountering wake locks that come and go?
Any help would be greatly appreciated! :victory:
AndroidFS2 said:
Hi guys,
I have read countless threads on battery life & wake locks on XDA, Reddit, etc. Trying to find a solution to what I still find the Achilles heel of android, wake locks.
I am running stock on MHC19Q build
Adaptive brightness off
Wifi scanning off
Bluetooth scanning off
Battery Optimization on all apps except for DMService and Google Play Services
Some days I will go 2-3 hours with 30 minutes SOT and my battery only drops 10%. Doze works as it should. I will get through a full day at about 4 hours SOT (6am to 10pm).
On other days (like today) I am unplugged for 3 hours at 80% with 10 min SOT. I have rebooted the device 3 times since unplugging it and my wake locks are still occurring. My signal is perfect green through and through. Bluetooth off and connected to wifi.
I find the issue comes and goes. Some days the phone will start out great, only to have wake locks start occurring mid day. I think Android OS appears to be the issue.
Anyone else encountering wake locks that come and go?
Any help would be greatly appreciated! :victory:
Click to expand...
Click to collapse
Absolutely same situation. No new application in monthes.
Google play services is usually the battery waster I found when moving around, I tend to place phone down when I can to save juice but you really need to identify your wakelocks first. I'm rooted and use bbs.
Disabling location may help, if rooted and using xposed, amplify may help too.
Google play services get updated when it's pushed out, sometimes it has bugs.
Maybe if you haven't updated any of your apps for months, then possibly one may need updating now.
For some reason, my phone just won't sleep even when I sleep! Do you guys have a fix for this? Thank you.
I already did the wipe cache thing and I restarted the phone mamy times. I also tried package disabler pro.
For my Sprint GS7E, wakelock is caused by GpsLocationServices_ex from Android System. Workaround is to turn off Location.
Sent from my SM-G935P using Tapatalk
I have the exact same problem. Has anyone contacted Verizon about this issue? Has anyone found a solution?
Thanks.
zx12cv34 said:
For some reason, my phone just won't sleep even when I sleep! Do you guys have a fix for this? Thank you.
I already did the wipe cache thing and I restarted the phone mamy times. I also tried package disabler pro.
Click to expand...
Click to collapse
Same thing. I've factory reset my VZW GS7 Edge three times since receiving it in March. It seems ok for a couple of days and then goes right back to not sleeping. I have location turned off. Any ideas?
troydh said:
Same thing. I've factory reset my VZW GS7 Edge three times since receiving it in March. It seems ok for a couple of days and then goes right back to not sleeping. I have location turned off. Any ideas?
Click to expand...
Click to collapse
Try to recall what you installed before that situation happens and uninstall the software and then reboot the phone to see if it solves the issue.
yiyi28 said:
Try to recall what you installed before that situation happens and uninstall the software and then reboot the phone to see if it solves the issue.
Click to expand...
Click to collapse
Sorry. I should have been more descriptive in my troubleshooting steps. After the last reset:
Day 0: Left wifi off, bluetooth off, no email syncing at all, no location services, no Facebook, no Google photos sync. Awesome battery life.
Day 1: Turned on wifi (home and at the office). Left everything else as above. Still awesome battery.
Day 2: Added bluetooth & used it. Awesome battery life.
Day 3: Added email manual sync for Outlook account. Awesome battery life
Day 4: Added Google photos sync. Still awesome battery life
At that point, was thinking I had it nailed. The reset fixed it. But I still took it easy on the phone; making no additional changes. Two or three days later, battery life went from showing 2+ days to barely getting 24 hours. The Android O/S was keeping it awake like 20 hours. Reboots didn't help the situation. Yesterday, I barely got 18 hours out of it.
This afternoon, I was reading the forums again and thought I'd try leaving everything the way it was and just turning off wifi. Phone hasn't had a call or text today. 5 minutes checking email is about all the activity on it.
Almost completely in standby today.
12:45 p.m. - turned off wifi
Phone on battery 9 hr, 3 minutes.
Android OS 16 % - Stay awake 5 hr 53 minutes.
Looking at the usage graph, the phone started going into doze not long after turning off wifi. Is wifi really the culprit? If so, why didn't it start on day 1 when I activated it after the reset?
Maybe try removing some of the syncing accounts if you have any. I had battery drain on exchange or contact sync before but they would show up in battery status. The Android OS thing is abnormal. If you can't solve it by yourself, you can try returning the phone and get a new one.
Sent from my Nexus 6P using Tapatalk