Database Users

Nlpwakelock causing device to stay awake

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..

Recent S-health update creates wakelocks

Updated S-health app yesterday and today I discovered a 17h. wakelock by the S-health app. Can't make the phone sleep without killing S-health. I have S-health going in the background all the time to have the stepcounter going, but never had wakelock issues before updating. I had a backup of old S-health and rolled back and now all is well again.
Anyone having a remedy or am I to wait for fix/update?
N910FXXU1ANK4
(I have xposed framework installed and thus S-health secure server disabled. Busybox also installed)
Sent fra min SM-N910F via Tapatalk

i dont use s health very often (sometimes in the gym for my heartrate)
but i updated it yesterday, and at the end of the day my SOT was only 1 h and 20 minutes or less, and my battery was around 60% !!
normally i allready have 2 or 3 hours of SOT when i reach 60 %
i dont know if it has anything to do with S Health (could not find it in battery stats tough)
but all i know is that it sucked.

S-Health battered my battery from the day I got my phone so I turned it off and my battery improved a lot. The steps function was so easily cheated simply by shaking the phone that it didn't seem worth having.

... you don't sit around shaking your phone do you really? The step counter works quite all right and can be relied on as any other step counter device. And it uses no battery to speak of. Really!
In Samsung app store many has complained about the same wakelock issue draining battery like h... the last days. I guess we'll have to wait for fix.
So, DO NOT UPDATE TO RECENT S-HEALTH BEFORE FIX HAS BEEN MADE!
Sent fra min SM-N910F via Tapatalk

I updated to the latest S-Health but I see no extra wakelocks coming from it, even though I wear a Gear Fit all day so S-Health is frequently syncing and gathering data from it. However, yesterday I noticed a rapid battery drain, with Android OS and Android System shown as the culprits, leaving the Screen at the 3rd place in battery stats, which is really weird. Maybe it is S-Health acting up after all.

Same problem here. After update, I was having a hugh battery drain. Installed Wakelock Detector and it showed more than 1500 wakelocks in 12 hours (most of them were alarm manager). I have uninstalled the update, waiting for a fix...

It seems it woun't sync properly on autosync and then hangs for hours. When I did manual sync in settings/accounts it is fine again, but everytime it autosyncs, it's a new hang. In Samsung store it got a new date on it now, Jan. 30. I don't know if it's an attempt to fix, but it's not a success. Reverted to old backup yet again
Sent fra min SM-N910F via Tapatalk

mikkelrev69 said:
Updated S-health app yesterday and today I discovered a 17h. wakelock by the S-health app. Can't make the phone sleep without killing S-health. I have S-health going in the background all the time to have the stepcounter going, but never had wakelock issues before updating. I had a backup of old S-health and rolled back and now all is well again.
Anyone having a remedy or am I to wait for fix/update?
N910FXXU1ANK4
(I have xposed framework installed and thus S-health secure server disabled. Busybox also installed)
Sent fra min SM-N910F via Tapatalk
Click to expand...
Click to collapse
I also checked out my battery behaviour this night and was very disappointed. Although my phone was in flight mode and every peripherals and services shut down, today morning my phone was crying for energy. So I made a quick investigation in my power diagram and found out, that "Android OS" requested a wakelock during the whole power-on time. So I installed "CPU Spy" to check in which states the phone was really over the whole charging period. I couldn't believe my eyes. Although the kernel should do it's job good, cause most of the CPU times are in lower freqeuncy states, the deep sleep mode was never activated.
Therefore I installed an app called "Wakelock Detector" to check out which apps could cause that. I found out, that S Health had a big amount of wakelocks and also active-time, so the first thing was to disable S Health. After some minutes I checked back, but nevertheless still no deep sleep time in "CPU Spy".
So I searched around and found another one arguing about the wakelocks and that they could be the products of some programming issues concerning WiFi. The should be gone, after turning off WiFi and rebooting yout phone. And it seems that he was right. I waited some time and hooray, "CPU Spy" listed the phone state "Deep Sleep" the first time as an active state and also with the major active-time. So at least that was some step ahead. (I have to remark, that S Health was already unfrozen at this time, so S Health should not be responsible in any way.)
The next step was to reactivate WiFi, leave it on and set the phone on standby. After some time I checked back again the phone showed even more deep sleep time. So that was an improvement. I reactivated everything and waited some time... Deep Sleep all over the time. Can't figure out for now, if it was S Health, WiFi, or anything else that caused the wakelock for sure. At least the reboot helped. I'll check that out on a long-term test, maybe I get some further conclusions.

Battery drain.. Phone always on

Hi.
Running stock Marshmallow, with root and used wakelock detector and battery monitor to find that when not in airplane mode, three kernel wake locks (see screen shots) as far as I can tell, seem to be causing my phone to stay awake all the time and hence use battery.
I also use Greenify BTW.
How do I remedy this?
Thanks
Im333

I had the same issue. I found out that it was because I had blocked a Bluetooth wake service and it freaked the phone out keeping it awake. I would suggest enabling each service you disabled one by one going through them to find out which one is causing your issue. Or you can uninstall greenify and any other apps that disable services like amplify and servicely. I found that my battery life had gotten better after doing so.

No deep sleep and high battery usage

Hi everyone,
most of the time, my Axon 7 eats the battery absurdly fast, when only lying around (Standby). I opened a different thread that I caught it once discharging the battery even when turned off, but several other times, it did not do that again.
I noticed that BetterBatteryStats tells me that there is almost 0 time for "Deep Sleep" (3s) while it is "Awake (Screen Off)" almost all the time. Since I have no root, I do not know how reliable the data is (100% Awake + 21% Screen On + 0% Deep Sleep = 121% = lol).
I have checked the power management for all apps. All have "Allow deep sleep" activated.
The battery discharging is so heavy that one charge is not enough for one day of usage (with some hours screen on time).
Do you have experienced something like this, even with a different phone? Any ideas are welcome.
Regards,
Puni

You must have some app eating your battery. Try to remove some latest apps and reboot. If that doesn't work clear cache.. After that is only factory reset left...

FATPunisher said:
I noticed that BetterBatteryStats tells me that there is almost 0 time for "Deep Sleep" (3s) while it is "Awake (Screen Off)" almost all the time.
Click to expand...
Click to collapse
Okay, this is not really specific to the Axon 7, but it will work anyway. I precise I'm NOT ROOTED as well.
First :
- you better also install Gsam Battery Monitor, you'll have access to a better looking stats for Doze Mode. However, under Battery Manager (sorry, doesn't know how it is in english) / Battery Usage / Time battery used, you should have "Awake time" and monitor it here as well
- install Greenify as well, to try to apply Doze mode asap.
Second:
- Wifi on the axon, even when "turned off while screen is off", isn't. Manually switch the wifi off if needed.
- The same is for the GPS/Location services. Even when the toggle is OFF, you are still being tracked. Long-clic on the toggle, and make sure location is disabled (unless you need it). It will reset if you 'allow' Google Maps to enable location for yourself. Don't do it.
Third :
- Fiddle with Energy management, and learn about the 4 available toggles (disallow at startup, force close when screen is off, delay wake up, do not allow wakeup when in doze mode). Be careful about notifications tho, activating some switches might remove or delay them
- Go to security, administrators : do you have an app that shouldn't be there (which can wake up the phone)?
- Go to acessibility, same
- Do a reboot
- Watch what happens next
- Please report back here with BBStats + Gsam + Energy manager screenshots at least

Thanks a lot!
I will try your hints.
But disabling Wifi and GPS/Location is not really useful for me, because I need both all of the time. Could try it for seeing if it helps though.

Activating Air Plane mode allows Deep Sleep. Not useful, but nevertheless interesting.

I noticed that my Medion tablet with Android 4.4.2 (!) has the same issue. Must be an app installed on both I guess.
Wakelock Detector says it's Android System, AlarmManager. That is not too helpful.

On my Axon 7, Bluetooth triggers the Wakelock. It's 100% reproducible. Cannot be the whole story though, there must be more. The battery lasts at least twice as long without Bluetooth.

Solved!
Solved it!
It was the app MeinVodafone. It causes Wakelocks when Bluetooth is enabled.
I found a forum posting by somebody else confirming that.
Very nasty.
Thanks everybody!
P.S.: My tablet is a different story. Bluetooth is never active there. The wakelock vanished, but I have no idea what happened. Doesn't matter, unrelated.

Doze-Wakelock

Better Battery Stats shows Doze-Wakelock as my worst offender of Kernel wakelocks at 75% with the next offender, power manager service at a measly 13%. I have reset, reflashed, uninstalled, reinstalled, wiped cache, wiped dalvik, yet the wakelock persists and I can not find anything about it on any thread. I currently use greenify, power nap, amplify, and force doze on Stang5.0litre rom. However I have noticed the wakelock on Echoe and stock rom. It persists with Force Doze off (I don't use Greenify's Aggresive doze.) If anyone has any info on this wakelock, please inform me.

link77709 said:
Better Battery Stats shows Doze-Wakelock as my worst offender of Kernel wakelocks at 75% with the next offender, power manager service at a measly 13%. I have reset, reflashed, uninstalled, reinstalled, wiped cache, wiped dalvik, yet the wakelock persists and I can not find anything about it on any thread. I currently use greenify, power nap, amplify, and force doze on Stang5.0litre rom. However I have noticed the wakelock on Echoe and stock rom. It persists with Force Doze off (I don't use Greenify's Aggresive doze.) If anyone has any info on this wakelock, please inform me.
Click to expand...
Click to collapse
I'm also on the Stang rom and i just noticed it after gsam showed my phone being held awake for over an hour during 2 and a half hours of standby. Seemed to start when i turned on the AOD but i can't be sure.

Omegeddon said:
I'm also on the Stang rom and i just noticed it after gsam showed my phone being held awake for over an hour during 2 and a half hours of standby. Seemed to start when i turned on the AOD but can't be sure.
Click to expand...
Click to collapse
Do you use any if the apps I mentioned above. Ive noticed the wakelock isnt as prominent if the phone is left stationary. So I feel as though it might be greenify or force doze trying to force doze, but android system noticing the motion and not letting it do so, creating a loop and constant conflict. But as I said i can not find anything about this on xda or Google.

Omegeddon said:
I'm also on the Stang rom and i just noticed it after gsam showed my phone being held awake for over an hour during 2 and a half hours of standby. Seemed to start when i turned on the AOD but i can't be sure.
Click to expand...
Click to collapse
Turned the aod off this morning. Definitely the culprit. However noticed 4 random reboots while the phone was inactive. The problem goes away when i turn aod back on. Currently investigating this new problem.

Freezing always on display in titanium Backup after disabling it fixed the random reboot issue. Currently enjoying no doze-wakelock in bbs with a great increase of deep sleep time.

The only one i use is greenify.