Database Develop

NlpWakeLock and NlpCollectorWakeLock Discussion

Firstly, this is not another thread to complain about your horrible battery life due to Google Play Services. I'm tired of those (mostly on Reddit, but some here too. Either way, none of that here ). This is instead to try and find a root cause for it. "It's Google's fault" is not good enough for me, and if you truly care about your battery life it shouldn't be for you either. If all you're after is an easy way out to get your battery life back, then this thread is not for you. We're here to reach a solution where you can get location services and good battery life. I've done if before, on my Galaxy Nexus on 4.3, but it seems that something is wrong in KitKat. Let this be a place where we all dig deeper into this issue, perform tests, gather results, and then share and discuss them. Here's what I've got so far:
The wakelocks that cause this battery drain are NlpWakeLock and NlpCollectorWakeLock. Nlp stands for network location provider. As you may know, Android provides developers with two ways of gathering location information. One is through the GPS_PROVIDER, which uses the GPS, and the other is through NETWORK_PROVIDER, which uses cell towers and WiFi APs to get your position. According to their developer website[1] , NETWORK_PROVIDER uses less battery, is faster, but is less accurate. GPS uses more battery, takes longer, but is good if you want an accurate location. I'm assuming this particular wakelock uses NETWORK_PROVIDER.
I also did some digging using ROM Toolbox Pro's autostart manager. My guess was that Google Play Services must be triggered every time a certain intent is broadcasted, since nothing obvious is telling it to run. Turns out there are quite a few. 30, to be exact. However, many of them have to do with GCM and we don't really care about those. One of particular interest is one called com.google.android.location.internal.NlpNetworkProviderSettingsUpdateReceiver. It listens for the intent android.location.PROVIDERS_CHANGED. The LocationManager API's documentation[2] tells us this:
Broadcast intent action when the configured location providers change. For use with isProviderEnabled(String). If you're interacting with the LOCATION_MODE API, use MODE_CHANGED_ACTION instead.
Click to expand...
Click to collapse
I'd assume that this means when you change your location providers, such as enabling/disabling data, WiFi, GPS, etc.
However, location reporting only seems to use network location. If you're on KitKat, go to the location settings and choose device only. Then choose battery saving. It asks you to accept location reporting. Same thing when you choose high accuracy. What do both of those have in common? Network location. You can switch between those two as much as you want and it won't ask you to accept again. However, once you switch to device only and back it will ask you. This shows that it only uses network location.
I find that Google (Play) Services has 5% (+/- 1%) keep awake. Tested on both Nexus 5 running KRT16M and Galaxy Nexus running JWR66V. Both use a certain time of GPS, although that number is never increasing. I assume this is some sort of initial one-time lock. It can be disregarded.
One more thing I noticed is that this Google Play Services issue is much more prominent on KitKat. While they have happened before, often times a simple Play Store update would fix it. This time it seems to be location based. Guess what changed in KitKat? The way you deal with location settings. It may be that the way location settings are grouped in KitKat cause that intent to keep firing, and that in turn triggers something that eventually ends up being what you see as NlpWakeLock.
What I'm going to try next is disabling that intent receiver and then monitor that wakelock as well as if location reporting still works. Feel free to play around, and be sure to share your results.
To those who are suffering from these wakelocks, could you please share your settings? Such as what type of location mode you have (high accuracy, battery saving, device only), WiFi on or off, data on or off, signal strength, WiFi always scanning, Play Store and Play Services version, what device you have, Android build number, and what ROM/kernel you're using if you are using one? Any other info such as screenshots of battery screen, betterbatterystats, wakelock detectors, etc. will all be welcomed.
Here is the Reddit thread I created discussing the same issue: http://www.reddit.com/r/Android/comments/1rvmlr/nlpwakelock_and_nlpcollectorwakelock_discussion/

I don't have this device, nor do I know if I'll be getting it, but I must say that I applaud your method.
Bravo!

I just turn location reporting off then select 'battery saving' setting & accept the request for reporting when it pops up. This allows you to use network location without logging. Google now & maps work fine although not quite as accurate. I just turn on gps if i need navigation. Never get more than 2% usage from play services & it's giving me a total kept awake time of about 28mins out of 12hrs of use with 3hrs screen on time.
Sent from my Nexus 5 using Tapatalk

If I disable the wifi and 3g, leave my phone on battery saving location, google location set to on, it is using wifi always scanning only and it didnt consume 1% battery in a whole night

stumpy352 said:
I just turn location reporting off then select 'battery saving' setting & accept the request for reporting when it pops up. This allows you to use network location without logging. Google now & maps work fine although not quite as accurate. I just turn on gps if i need navigation. Never get more than 2% usage from play services & it's giving me a total kept awake time of about 28mins out of 12hrs of use with 3hrs screen on time.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
That is working for me right now.
Sent from my Nexus 5 using Tapatalk 2

ickboblikescheese said:
To those who are suffering from these wakelocks, could you please share your settings? Such as what type of location mode you have (high accuracy, battery saving, device only), WiFi on or off, data on or off, signal strength, WiFi always scanning, Play Store and Play Services version, what device you have, Android build number, and what ROM/kernel you're using if you are using one? Any other info such as screenshots of battery screen, betterbatterystats, wakelock detectors, etc. will all be welcomed.
Click to expand...
Click to collapse
I am experiencing this issue on my Nexus 5, as confirmed by betterbatterystats (NlpCollectorWakelock 5.5% awake time)
ROM: CyanogenMod 11 alpha
Build Number: KRT16S
Location Mode: High accuracy
Location Reporting: Off
WiFi On: Sometimes
Play Store Version: 4.4.22
Play Services Version: 4.0.34
This issue first appeared for me the other day. I noticed that my device was not appearing in the online Android Device Manager, nor the desktop version of the Play Store. To fix the ADM issue, I disabled remote wipe, cleared data for Play Services, reenabled remote wipe, and rebooted. To fix my device not appearing in the Play Store, I cleared data for the Play Store app. Both issues were thereafter resolved, but now I am experiencing the Network Location battery drain.
Is it possible the problem is related to requests from Android Device Manager? I was under the impression that location for that purpose was 'on demand' instead of logged, but what do I know.
Thanks for doing this! Others, please feel free to use my comment as a template, and post your own data.

So I was playing around with autostart, and I accidentally caused a bunch of FCs for Play Services. Ended up freezing/defrosting and then uninstalling updates then let it update itself, and I noticed this (may or may not have anything to do with what I did): Even though it wakelocks, it barely uses up any batter. I was in an area of 2-3 bar HSPA+, with sync on, location reporting on at high accuracy, etc. and it drained 1% per hour. Still kept phone awake ~5% of the time, but battery usage was significantly better over what I recorded to be 4.8%/hour from last Friday.
EDIT: The only other change I can think of making is temporarily freezing Cerberus. I'll have to look more into that. However, check which apps are requesting your location. The new location settings in KitKat make this simple enough. For me it's only Google Now and Google Play Services, and whatever app that happens to require GPS such as camera (geotagging) and maps.

ickboblikescheese said:
So I was playing around with autostart, and I accidentally caused a bunch of FCs for Play Services. Ended up freezing/defrosting and then uninstalling updates then let it update itself, and I noticed this (may or may not have anything to do with what I did): Even though it wakelocks, it barely uses up any batter. I was in an area of 2-3 bar HSPA+, with sync on, location reporting on at high accuracy, etc. and it drained 1% per hour. Still kept phone awake ~5% of the time, but battery usage was significantly better over what I recorded to be 4.8%/hour from last Friday.
Click to expand...
Click to collapse
So, how should I replicate this? I'm using the Xposed Module that dev posted in your Reddit post.

stumpy352 said:
I just turn location reporting off then select 'battery saving' setting & accept the request for reporting when it pops up. This allows you to use network location without logging. Google now & maps work fine although not quite as accurate. I just turn on gps if i need navigation. Never get more than 2% usage from play services & it's giving me a total kept awake time of about 28mins out of 12hrs of use with 3hrs screen on time.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
How do you do this exactly? If I turn location reporting off, then I can't select the battery saving method because it's greyed out. This also causes location based cards to stop working on Google Now and Maps can't locate me either.
---------- Post added at 11:24 PM ---------- Previous post was at 11:19 PM ----------
natezire71 said:
So, how should I replicate this? I'm using the Xposed Module that dev posted in your Reddit post.
Click to expand...
Click to collapse
Use Titanium Backup to FIRST backup Google Play Services. Then use it to uninstall GooglePlay Services. Then open Google Now or Maps, they will ask you install Google Play Services and take you to the app store.
If anything goes wrong, use Titanium to restore.

You need location toggled on. Go down to location services & click on Google Location Reporting. Select off for both settings. Then go back out & select battery saving mode & accept the terms.
Sent from my Nexus 5 using Tapatalk

stumpy352 said:
You need location toggled on. Go down to location services & click on Google Location Reporting. Select off for both settings. Then go back out & select battery saving mode & accept the terms.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Turns out that's exactly how I had set up after all, doh! Thank you.
I have actually been getting really decent battery life, noticeably better than my HTC One, with exactly similar usage patterns and same apps installed etc.

Also, Play Services is not the only app that uses this NlpWakeLock. Facebook also uses it & in my case has the highest time kept awake. I turned off location in chat & noticed that it is much better.
Sent from my Nexus 5 using Tapatalk

That's what I thought too. That could explain why some people have this issue more than others.
Sent from my Nexus 5

ickboblikescheese said:
That's what I thought too. That could explain why some people have this issue more than others.
Sent from my Nexus 5
Click to expand...
Click to collapse
Have you tried the Xposed module that filters wake locks? I've been using it and the NLP counts have drastically dropped

No, not using xposed. I understand that wake locks must occur for accurate location services (otherwise what is doing the reporting). What shouldn't be there is the incredible battery drain. Wake locks don't necessarily mean battery drain. You could have a 1h wake lock and drain 1% battery, or a 5 min wake lock that keeps CPU on high frequency causing a 10% battery drain. I don't mind wake locks as long as battery isn't affected too much.
Sent from my Nexus 5

ickboblikescheese said:
No, not using xposed. I understand that wake locks must occur for accurate location services (otherwise what is doing the reporting). What shouldn't be there is the incredible battery drain. Wake locks don't necessarily mean battery drain. You could have a 1h wake lock and drain 1% battery, or a 5 min wake lock that keeps CPU on high frequency causing a 10% battery drain. I don't mind wake locks as long as battery isn't affected too much.
Sent from my Nexus 5
Click to expand...
Click to collapse
That was the point of this module. https://play.google.com/store/apps/details?id=in.andro.wlt. Take a look and read the description. From my understanding, the location stuff still works--which for me has been the case. However, it stops the unnecessary wakelocks. I would like to believe my battery has improved.

Nice thread!!
I've changed my location settings and I'll report if it works!!!
Thanks!!!

natezire71 said:
That was the point of this module. https://play.google.com/store/apps/details?id=in.andro.wlt. Take a look and read the description. From my understanding, the location stuff still works--which for me has been the case. However, it stops the unnecessary wakelocks. I would like to believe my battery has improved.
Click to expand...
Click to collapse
Please keep us posted on this works out for you, it looks really promising!

the7thson said:
Please keep us posted on this works out for you, it looks really promising!
Click to expand...
Click to collapse
I think it's working.

natezire71 said:
I think it's working.
Click to expand...
Click to collapse
Can you tell us which apps you disabled wake locks for?
Sent from my Nexus 7 using Tapatalk 4

[Q] Optimizing battery for S6 Edge Verizon

Obviously, the battery has been terrible on this device. I disabled Google Play Services for a day and I want to say my life tripled. However, not having Google Play Service is no way to live; can't access the Play Store, location services don't work, Gmail doesn't work, etc.
I've come across a way to disable only some of the Google Play Services via DisableService app. However, it needs to be rooted. I can't root it via PingPong because my Baseband version ends with 0F1
What are my options here? Wait til I can root it? Wait for 5.1.1 and put up with the subpar battery life? Anything else to significantly improve the battery?

If you have OF1, as of now there is no wait for root. Another exploit may be found but for now, if your on OF1, root is gone, possibly forever.
Sent from my SM-G925V using XDA Free mobile app

ozv101 said:
Obviously, the battery has been terrible on this device. I disabled Google Play Services for a day and I want to say my life tripled. However, not having Google Play Service is no way to live; can't access the Play Store, location services don't work, Gmail doesn't work, etc.
I've come across a way to disable only some of the Google Play Services via DisableService app. However, it needs to be rooted. I can't root it via PingPong because my Baseband version ends with 0F1
What are my options here? Wait til I can root it? Wait for 5.1.1 and put up with the subpar battery life? Anything else to significantly improve the battery?
Click to expand...
Click to collapse
I would disagree that battery is terrible, but some basic battery saving techniques without root include dim the screen brightness, disable battery hungry apps such as facebook, S Voice, and instagram, use tasker to automate everything, turn off con.nectivity services such as wifi and bluetooth when not in use, and use greenify (even though root is required for this app to be automated). Also avoid using Googles widgets. Dont use vibrate mode either. Everything else requires root.

i dont have root. my battery is acutally great then when i first very bought the phone. i cycled the battery only to charge it at 2-5% left on battery to full did that for almost one month now and my battery has improved alot. i use the phone quite alot as well. my phone can last a whole day without charge. i have facebook instagram tumbler snapchat installed. using stock launcher as well. i just make sure to close all the apps ive used before my phone goes back into my pocket. when i get home i usally have around 33% battery left. oh i also keep a small powered fan next to my phone when its charging cause the phone does get little hot when it charges but keeping that fan on. when it charges it has changed alot my battery is way better.

Have you tried disabling S-health in App Manager?

(Note 8) Something Is Really Stuffing My Battery

Got the phone at launch and the battery was brilliant, 5 hours SOT no problems. But the last couple of months Google Play Services has been killing my battery. I've tried everything I could think, removing location permissions for all apps, disabling bloat, installed PDP to go that extra step further on apps that wouldn't allow it. Factory reset, cache wipe, I've done it all. Yet still, Play Services is ruining my phone, of the 10% I've lost so far in my 45 minuntes of being awake, Play Services accounts for 5% of that. I've gone through every individual app to see if any have a matching battery usage that doesn't show in the battery usage section under battery, but none do, not even close. I am at my wits end with this, it's ruining a truly fantastic phone.

kopkiwi said:
Got the phone at launch and the battery was brilliant, 5 hours SOT no problems. But the last couple of months Google Play Services has been killing my battery. I've tried everything I could think, removing location permissions for all apps, disabling bloat, installed PDP to go that extra step further on apps that wouldn't allow it. Factory reset, cache wipe, I've done it all. Yet still, Play Services is ruining my phone, of the 10% I've lost so far in my 45 minuntes of being awake, Play Services accounts for 5% of that. I've gone through every individual app to see if any have a matching battery usage that doesn't show in the battery usage section under battery, but none do, not even close. I am at my wits end with this, it's ruining a truly fantastic phone.
Click to expand...
Click to collapse
Have you tried not disabling things? Seen quite a few reports here where disabling some bloat actually led to higher standby drain, Google Play services drain, etc.

sefrcoko said:
Have you tried not disabling things? Seen quite a few reports here where disabling some bloat actually led to higher standby drain, Google Play services drain, etc.
Click to expand...
Click to collapse
I haven't....I'll factory reset and give that a try. At this stage I've lost track of everything I've turned off lol. Thanks for the heads up

Try using wakelock detector, greenify, GSam or betterbatterystats to check what wakelocks are causing drain.

sefrcoko said:
Have you tried not disabling things? Seen quite a few reports here where disabling some bloat actually led to higher standby drain, Google Play services drain, etc.
Click to expand...
Click to collapse
Yeah I had to reset my device and start all over going as far as Odin. Anything I disabled using BK Disabler didn't start working even after the factory reset, so I had to Odin firmware on the device. Prime one being Bixby. No matter what I did she would not work at all. Was like if the button was a dummy.
Battery life with things disabled was garbage. Either Samsung had a "lie to me" thing going with this device or the services related to those disabled things, are actively trying to enable them, causing the battery to drain.

Jammol said:
Yeah I had to reset my device and start all over going as far as Odin. Anything I disabled using BK Disabler didn't start working even after the factory reset, so I had to Odin firmware on the device. Prime one being Bixby. No matter what I did she would not work at all. Was like if the button was a dummy.
Battery life with things disabled was garbage. Either Samsung had a "lie to me" thing going with this device or the services related to those disabled things, are actively trying to enable them, causing the battery to drain.
Click to expand...
Click to collapse
Yes the posts I read specifically mentioned Bixby (among a few other apps), so I tend to agree that something Sammy has done results in exactly what you said...when those apps are disabled the phone keeps trying to enable them causing added and unexpected drain. Hope the reflash worked out for you (and OP as well). I think it will

sefrcoko said:
Yes the posts I read specifically mentioned Bixby (among a few other apps), so I tend to agree that something Sammy has done results in exactly what you said...when those apps are disabled the phone keeps trying to enable them causing added and unexpected drain. Hope the reflash worked out for you (and OP as well). I think it will
Click to expand...
Click to collapse
Yeah reflash is what fixed mine. I'm currently experimenting with completely removing the apps and related services on a rooted Rom BlueFox made.

Bluetooth drain

Morning all
Probably a silly question but while Bluetooth is on - myy s10 doesnt go to sleep and the battery drains very fast.
With it off its fine.
Unfortunately I use BT for my sony wireless buds and Galaxy watch.
Are there any tweaks to help out with battery life?
Its connected to the watch all the time while im wearing it so is this something i need to get used to?

adesad said:
Morning all
Probably a silly question but while Bluetooth is on - myy s10 doesnt go to sleep and the battery drains very fast.
With it off its fine.
Unfortunately I use BT for my sony wireless buds and Galaxy watch.
Are there any tweaks to help out with battery life?
Its connected to the watch all the time while im wearing it so is this something i need to get used to?
Click to expand...
Click to collapse
Hmmn. I keep mine on to connect to my Xiaomi Mi Band 5 though I notice it Bluetooth does turn off occasionally. Hadn't noticed S10e draining faster (it does seem to still go to sleep) but maybe I haven't been paying enough attention. I'll be interested in any replies.

Try disabling all power management.
Load Karma Firewall. Android Services and Goggle Play Services* are big offenders.
Unfortunately if your on Q or higher Karma's logging feature doesn't work. This shows you real time what's hogging the internet and battery.
Another reason I'm still on Pie.
* enable briefly to access Gmail etc.

I have been using Better Battery Stats to keep an eye on it.
While BT is on the CPU sits at 1.95 at over 90% of the time I've tested it against.
With BT off - it does goto sleep and battery is loads better.
I need it on for the reasons above but its a right hog.

adesad said:
I have been using Better Battery Stats to keep an eye on it.
While BT is on the CPU sits at 1.95 at over 90% of the time I've tested it against.
With BT off - it does goto sleep and battery is loads better.
I need it on for the reasons above but its a right hog.
Click to expand...
Click to collapse
Disabled all power management.
Try clearing apk data and going back to factory load.
Clear system cache on boot menu.
Disable any 3rd party apks other than Wearables using bt.
Start locking down apks that don't really need internet access with Karma Firewall* until you find the hog. Probably a system apk and the drain may actually be from constant internet traffic. Misreporting which apk is the culprit isn't uncommon as many have related dependencies.
*if you're running Q or higher it's logging function is disable I believe. It works fine with Pie and is an important tool. Otherwise you'll need to do it the hard way. Thanks Google, you suck.
Android Services, Google Play Services, Google Backup Transport and Google Framework are all hog candidates. Best to package block the last two and clear apk data on all but Android services as needed. This what I did to take my 10+ running on Pie.

Question Google play services is at it again

Hi all,
Is anyone facing an issue with google play services draining the battery...I get so angry when I see that damn app draining my battery...the battery stats says it's running in the background...why, I don't know! It's recent phenomenon and has been running since the past 20hrs or so...how do I solve this? I'm not sure cleaning the data/ cache would be ideal as this would only lead to more drain since play services will try to download all the info that it has previously....any help will be greatly appreciated!

So 1% battery loss from a system service running for 20 hours in the background is a big problem...?
I'm a bit confused here...

NippleSauce said:
So 1% battery loss from a system service running for 20 hours in the background is a big problem...?
I'm a bit confused here...
Click to expand...
Click to collapse
Actually, it's a bit more than 1%...more like 23% over the past 6 days or so...here's the screenshot...I don't know if this apt battery usage or if google play services need to be given a knock on its head...

amirage said:
Actually, it's a bit more than 1%...more like 23% over the past 6 days or so...here's the screenshot...I don't know if this apt battery usage or if google play services need to be given a knock on its head...
Click to expand...
Click to collapse
Ah, so 0.16% battery per hour. So a bit more than normal. What version of the phone do you have (which processor) and what apps do you have installed that weren't listed?
Also, how do you keep charging your phone so slightly as shown in the picture?

Oh yes, GPlayS will eat up the battery...
Download Karma Firewall and block Google Play Services. It may be shown by it's UID, on my 10+ it's 10044.
You can unblock it as needed like for Gmail or Playstore (block Playstore as well*).
Block Android Services as well, UID 1000.
It's pretty useless but polls the internet 2 times every minute, GPlayS is 4 times a minute.
On Pie Karma's logging feature works so I can see what each apk is doing or not... Q and up sucks.
*disable if you have a package blocker except when needed. A reboot is required and GPS must be unblocked too for Playstore.
Clear Google Play Services, Backup Transport and Framework data as well. Best to disable the latter two. Someone told the latter two aren't present in Q... I can't verify that either way.

NippleSauce said:
Ah, so 0.15972% battery per hour. So a bit more than normal. What version of the phone do you have and what apps do you have installed that weren't listed?
Also, how do you keep charging your phone so slightly as shown in the picture?
Click to expand...
Click to collapse
Hi, I have the 21Ultra 12/256. The funny thing is that play services started acting up only lately...I have been using the phone for 1 week+ and this app starting going berserk just 20 hours ago! It's very likely a rogue update could have caused this issue and I'm sure if I uninstall the update all should be fine...let me do that and see how it performs...

amirage said:
Hi, I have the 21Ultra 12/256. The funny thing is that play services started acting up only lately...I have been using the phone for 1 week+ and this app starting going berserk just 20 hours ago! It's very likely a rogue update could have caused this issue and I'm sure if I uninstall the update all should be fine...let me do that and see how it performs...
Click to expand...
Click to collapse
My AT&T Note 10+ did the same thing and it wasn't an update that triggered it.
Power management was part of the problem.
I run now with all power management disabled except for fast charging and Optimized screen/cpu setting.
When I turn this phone off it goes into deep sleep...

blackhawk said:
My AT&T Note 10+ did the same thing and it wasn't an update that triggered it.
Power management was part of the problem.
I run now with all power management disabled except for fast charging and Optimized screen/cpu setting.
When I turn this phone off it goes into deep sleep...
Click to expand...
Click to collapse
Power management, you refer to the ones that show in the battery settings right? But I don't know how the battery power management settings relate to google play services drain...I have betterbatterystats and it shows that google play is the top most draining app...why I can't understand...

I have a feeling it's the feb update that's messing with the battery settings..Jan update was cool...is there a way to roll back to update before AUB6?

Here's an update...I uninstalled the updates to google play services and cleared the cache. Rebooted...and all's going well so far.

Definitely try out the suggestions made by @destz0r in the video that he left. I guess that I don't ever experience the same problem as I always leave location services disabled unless I'm directly using them for navigation. But I never would've guessed that GPS occasionally leads to more GPlay Service specific battery consumption (as I had thought that GPlay Services were primarily for inner-Google app data communication)...

NippleSauce said:
Definitely try out the suggestions made by @destz0r in the video that he left. I guess that I don't ever experience the same problem as I always leave location services disabled unless I'm directly using them for navigation. But I never would've guessed that GPS occasionally leads to more GPlay Service specific battery consumption (as I had thought that GPlay Services were primarily for inner-Google app data communication)...
Click to expand...
Click to collapse
I already had all those suggestions in place right at the time of setting up the device initially..but yes, uninstalling the play services update cleared the issue...for the moment...

amirage said:
Power management, you refer to the ones that show in the battery settings right? But I don't know how the battery power management settings relate to google play services drain...I have betterbatterystats and it shows that google play is the top most draining app...why I can't understand...
Click to expand...
Click to collapse
Power management seems to create conflicts after a few days running. GooglePS includes Backup Transport and Framework. Even when turned off they continue to run in the background on my device.
Play with it, see what you find but don't ignore and let this trashware toast your battery.