Hey everyone, first I'm not really sure if this belongs in a Tasker forums. Seeing as I use a N5, I figured it could also go here. Anyway, I've been having some problems with Npl wakelocks. I downloaded wakelock terminator with xposed and it seemed to have helped, however something didn't seem right as my battery was draining the same amount as when the wakelocks were happening. The only time I wasn't having the drain was when location was set to device only, which makes sense.
I'm completely new to tasker. I've watched a few tutorials and I've messed around with it a bit but with not much luck. I wanted to do one of two things. Either have location set to battery saver/high accuracy when the screen is on, and have it set to device only when the screen is off. Another option is to have it set to battery saver/high accuracy when google now/maps is open and device only the rest of the time. I feel like this shouldn't be that hard but I messed around with it and got no where. Anyway, what are your guys' opinion about this strategy and would anyone be able to help me with implementing these tasks. Thanks!
I wouldn't go the route of using tasker for your problem. And I would ditch that xposed module for wakelocks too. I run rooted with xposed on high accuracy at all times. My battery life is great. You need to find the source of your battery drain and eliminate it. Don't look for a bandaid fix using tasker. My guess is you have some rogue app killing your battery. Give us a list of all your apps, or delete them all, and install them one by one to track down the culprit. Also, are you running stock Rom and kernel? What other mods do you have?
Lokke9191 said:
I wouldn't go the route of using tasker for your problem. And I would ditch that xposed module for wakelocks too. I run rooted with xposed on high accuracy at all times. My battery life is great. You need to find the source of your battery drain and eliminate it. Don't look for a bandaid fix using tasker. My guess is you have some rogue app killing your battery. Give us a list of all your apps, or delete them all, and install them one by one to track down the culprit. Also, are you running stock Rom and kernel? What other mods do you have?
Click to expand...
Click to collapse
I can run the phone as normal today with location and everything on and post my BBS log after. Basically, when I'm at home the battery is great. However, ever since updating to the new google search app I've been having extreme wakelocks from the Npl whenever I would leave my house. Which is why I found a thread on xda that was talking about that exact wakelock. You're right though. I'm going to get rid of the app because it seemed weird. The wakelocks weren't showing up on BBS but I feel like it didn't get rid of them. Who knows though, maybe you're right and it is something else that's draining the battery which is why the wakelock app didn't help.
Anyway, I'm running stock ROM/kernel with xposed. I use greenify module, appOpsX, snapshare, gravity box, and gesture navigation module. With gravity box I just use custom quick settings, smaller nav bars, some status bar mods like the day and double tap to sleep. However, again I have had the same GB mods since before the drain. I use a pebble however I've never had a drain from that and I've been using it since Dec. Most of my apps are greenified including facebook, instagram, as well as all my music streaming apps. A lot of the google services I don't use are disabled like books/magazines/movies. I have snapchat, but I don't use it too much, and facebook messenger that I don't greenify. When I check GSam stats though, android system and kernel take the most battery, followed by music players if I was streaming music that day. The rest of the apps are way down the list.
I posted in the battery thread asking if anyone had the same problem with the wakelocks after having the latest google play services. I noticed mine is still 4.3 for some reason so I might just update manually from androidpolice and see if theres a difference. But yeah, I will keep this updated with todays logs.
Try this. Use titanium backup to uninstall Google play services and Google search. Then launch maps, and reinstall both from the play store.
PsychDrummer said:
Another option is to have it set to battery saver/high accuracy when google now/maps is open and device only the rest of the time.
Click to expand...
Click to collapse
This is what I ended up doing. You will need the secure settings plugin for tasker.
Set up a new profile for application "Maps".
When on, launch task GPS On (Secure settings, configuration GPS enabled)
Exit task, launch task GPS On (Secure settings, configuration GPS disabled)
I used the app factory to create an app for this, and use that on my N5 and my second phone too. Works great. Enables GPS when I launch Maps for navigation, and switches to battery saving when I exit Maps
PsychDrummer said:
I can run the phone as normal today with location and everything on and post my BBS log after. Basically, when I'm at home the battery is great. However, ever since updating to the new google search app I've been having extreme wakelocks from the Npl whenever I would leave my house. Which is why I found a thread on xda that was talking about that exact wakelock. You're right though. I'm going to get rid of the app because it seemed weird. The wakelocks weren't showing up on BBS but I feel like it didn't get rid of them. Who knows though, maybe you're right and it is something else that's draining the battery which is why the wakelock app didn't help.
Anyway, I'm running stock ROM/kernel with xposed. I use greenify module, appOpsX, snapshare, gravity box, and gesture navigation module. With gravity box I just use custom quick settings, smaller nav bars, some status bar mods like the day and double tap to sleep. However, again I have had the same GB mods since before the drain. I use a pebble however I've never had a drain from that and I've been using it since Dec. Most of my apps are greenified including facebook, instagram, as well as all my music streaming apps. A lot of the google services I don't use are disabled like books/magazines/movies. I have snapchat, but I don't use it too much, and facebook messenger that I don't greenify. When I check GSam stats though, android system and kernel take the most battery, followed by music players if I was streaming music that day. The rest of the apps are way down the list.
I posted in the battery thread asking if anyone had the same problem with the wakelocks after having the latest google play services. I noticed mine is still 4.3 for some reason so I might just update manually from androidpolice and see if theres a difference. But yeah, I will keep this updated with todays logs.
Click to expand...
Click to collapse
Just run device only all the time, like everyone else does. It's a problem with Google's code, and the same bad coding is clearly seen throughout their entire app lineup.
Lokke9191 said:
Try this. Use titanium backup to uninstall Google play services and Google search. Then launch maps, and reinstall both from the play store.
Click to expand...
Click to collapse
What would that do though?
jj14 said:
This is what I ended up doing. You will need the secure settings plugin for tasker.
Set up a new profile for application "Maps".
When on, launch task GPS On (Secure settings, configuration GPS enabled)
Exit task, launch task GPS On (Secure settings, configuration GPS disabled)
I used the app factory to create an app for this, and use that on my N5 and my second phone too. Works great. Enables GPS when I launch Maps for navigation, and switches to battery saving when I exit Maps
Click to expand...
Click to collapse
Thanks! So, how would I set this up using device only/high accuracy? I'm also super new to tasker so if you don't mind I might PM you asking for help.
Aerowinder said:
Just run device only all the time, like everyone else does. It's a problem with Google's code, and the same bad coding is clearly seen throughout their entire app lineup.
Click to expand...
Click to collapse
Well, I actually like to use maps and google now. However, I don't actually need the location on when I'm not using either of the two services which is why I wanted to setup tasker.
It'll change them from being system apps to user apps. This has solved nlp wakelocks for many others experiencing the same problems.
PsychDrummer said:
Thanks! So, how would I set this up using device only/high accuracy? I'm also super new to tasker so if you don't mind I might PM you asking for help.
Click to expand...
Click to collapse
Sure.
It isn't that hard - install the secure settings plug in first, and when prompted, give it Superuser access. Then, create a new profile in tasker - call it whatever you want. Set up the profile for the application "Maps"
When Maps is launched, set it up to fire a new task (I called it GPS On) - this task just enables the GPS setting in the secure settings (under third party plugins)
GPS on -> high accuracy
GPS off -> battery saving mode
Set up an exit task (I called it GPS Off) - this turns the GPS settings in the secure settings off.
I can send you the apk if you want (but you don't really know me, so you probably shouldn't use an apk from a stranger! lol!), or you can try to import this attached xml into tasker (rename the file to remove the .txt extension - filename will be AutoGPS.prj.xml) - the xml option should be safe.
I haven't tried importing an xml, but it should be fairly straightforward (Save profiles in /sdcard/tasker/profiles and then, in tasker, long press the profiles "tab" and "import"). Before doing this, backup your existing profiles in tasker, just in case. Also, make sure you have secure settings set up before you import this.
jj14 said:
Sure.
It isn't that hard - install the secure settings plug in first, and when prompted, give it Superuser access. Then, create a new profile in tasker - call it whatever you want. Set up the profile for the application "Maps"
When Maps is launched, set it up to fire a new task (I called it GPS On) - this task just enables the GPS setting in the secure settings (under third party plugins)
GPS on -> high accuracy
GPS off -> battery saving mode
Set up an exit task (I called it GPS Off) - this turns the GPS settings in the secure settings off.
I can send you the apk if you want (but you don't really know me, so you probably shouldn't use an apk from a stranger! lol!), or you can try to import this attached xml into tasker (rename the file to remove the .txt extension - filename will be AutoGPS.prj.xml) - the xml option should be safe.
I haven't tried importing an xml, but it should be fairly straightforward (Save profiles in /sdcard/tasker/profiles and then, in tasker, long press the profiles "tab" and "import"). Before doing this, backup your existing profiles in tasker, just in case. Also, make sure you have secure settings set up before you import this.
Click to expand...
Click to collapse
Cool, thanks I will give it a try. And it would be the same if I want to have location on when using google search/now?
PsychDrummer said:
Cool, thanks I will give it a try. And it would be the same if I want to have location on when using google search/now?
Click to expand...
Click to collapse
Yes, it should be. But in my experience, I haven't found Google Search/Now really requiring high accuracy GPS level location for any of the features yet. It gets by fine with just battery saving mode. So, I only enabled this for the Maps application.
Actually, now that I think about it, I don't know how you'd enable it for Google Now - since it runs in the background to notify you about upcoming events. Since you aren't launching Google Now most of the times, I don't know how you'd set up Tasker to enable the high accuracy GPS for that (and it is possible that Google now using active GPS may be part of the battery drain issue - I don't know for sure)
jj14 said:
Yes, it should be. But in my experience, I haven't found Google Search/Now really requiring high accuracy GPS level location for any of the features yet. It gets by fine with just battery saving mode. So, I only enabled this for the Maps application.
Actually, now that I think about it, I don't know how you'd enable it for Google Now - since it runs in the background to notify you about upcoming events. Since you aren't launching Google Now most of the times, I don't know how you'd set up Tasker to enable the high accuracy GPS for that (and it is possible that Google now using active GPS may be part of the battery drain issue - I don't know for sure)
Click to expand...
Click to collapse
I actually wanted to keep the device on "device only" location instead of battery saving. For Google now I wanted the traffic card, but I would only need it if I physically open google now. I don't really need the notification.
PsychDrummer said:
I actually wanted to keep the device on "device only" location instead of battery saving. For Google now I wanted the traffic card, but I would only need it if I physically open google now. I don't really need the notification.
Click to expand...
Click to collapse
To keep device only, you should use Location mode (in secure settings) and set it to Device only or whatever you need, instead of GPS.
Note that "Device only" still uses active GPS and "This mode may use more battery power and take longer to determine your location" (Ref: https://support.google.com/nexus/answer/3467281?hl=en)
The traffic card still works on "battery saving" because it uses cellphone triangulation, and shows you the traffic in your vicinity, and based on your destination.
jj14 said:
To keep device only, you should use Location mode (in secure settings) and set it to Device only or whatever you need, instead of GPS.
Note that "Device only" still uses active GPS and "This mode may use more battery power and take longer to determine your location" (Ref: https://support.google.com/nexus/answer/3467281?hl=en)
The traffic card still works on "battery saving" because it uses cellphone triangulation, and shows you the traffic in your vicinity, and based on your destination.
Click to expand...
Click to collapse
I know, I have always used battery saving. The problem is that with battery saving, I'm having these extreme wakelocks and Google is constantly searching for my location which is what I think is the cause of the drain I'm having. I'm going to use my phone today by just using device-only location and see how the battery lasts. It should be much better since I'm hoping the phone will be deep sleeping longer. Basically, when I take my phone off the charger in the morning and I'm still at home for the first 2 hours of the day the standby time is great. It usually goes down 1-2% in those 2 hours even if I use the phone a little. However, once I leave the house is when I get constant wakelocks from location services and the battery stats to deplete a lot faster. I mean, I can still get through a day just because I don't use the screen a lot. I tend to only use about 1 hr 30 min on a regular day but I just want to play around with settings to see what works.If I can get the same standby time throughout the day that I get within the first two hours when im at home that would be great.
PsychDrummer said:
I know, I have always used battery saving. The problem is that with battery saving, I'm having these extreme wakelocks and Google is constantly searching for my location which is what I think is the cause of the drain I'm having. I'm going to use my phone today by just using device-only location and see how the battery lasts. It should be much better since I'm hoping the phone will be deep sleeping longer. Basically, when I take my phone off the charger in the morning and I'm still at home for the first 2 hours of the day the standby time is great. It usually goes down 1-2% in those 2 hours even if I use the phone a little. However, once I leave the house is when I get constant wakelocks from location services and the battery stats to deplete a lot faster. I mean, I can still get through a day just because I don't use the screen a lot. I tend to only use about 1 hr 30 min on a regular day but I just want to play around with settings to see what works.If I can get the same standby time throughout the day that I get within the first two hours when im at home that would be great.
Click to expand...
Click to collapse
That's strange. With battery saving mode, I get no wakelocks, which with device only or high accuracy, I used to get a lot of wakelocks by the location services.
But yes, no harm in trying out the options. Tasker+secure settings should be able to set up the battery saving or device only (as described above)
jj14 said:
That's strange. With battery saving mode, I get no wakelocks, which with device only or high accuracy, I used to get a lot of wakelocks by the location services.
But yes, no harm in trying out the options. Tasker+secure settings should be able to set up the battery saving or device only (as described above)
Click to expand...
Click to collapse
You get Npl wakelocks? So far I haven't gotten it and that's the wakelock that usually keeps my phone awake for 2 hours or so. basically, I think the way it works is that the device only setting uses more battery when using apps that use location such as maps but when the apps are not in use it uses no battery on location.
PsychDrummer said:
You get Npl wakelocks? So far I haven't gotten it and that's the wakelock that usually keeps my phone awake for 2 hours or so. basically, I think the way it works is that the device only setting uses more battery when using apps that use location such as maps but when the apps are not in use it uses no battery on location.
Click to expand...
Click to collapse
No. Ever since I switched to battery saving (and tasker toggling to high accuracy when I use maps), I have no location based wakelocks (no NPL wakelocks)
jj14 said:
No. Ever since I switched to battery saving (and tasker toggling to high accuracy when I use maps), I have no location based wakelocks (no NPL wakelocks)
Click to expand...
Click to collapse
Interesting, I've been having the opposite. I even took a screen shot of the wakelocks on the stock battery app where when the screen is off there's a huge amount of individual lines for awake (of course this is backed up by BBS). However when using device only the awake and screen on match almost perfectly.
PsychDrummer said:
Interesting, I've been having the opposite. I even took a screen shot of the wakelocks on the stock battery app where when the screen is off there's a huge amount of individual lines for awake (of course this is backed up by BBS). However when using device only the awake and screen on match almost perfectly.
Click to expand...
Click to collapse
Not sure why the difference, but regardless, as long as the individual 'fix' works, that's all that matters
Hey guys,
I had the issue with the 40% battery burn overnight again. According to WLD, the CPU was awake for 96% of the ~11 hours since it was charged (which explains it). I want to make sure I'm reading these right, so I've posted screens of wakeup triggers and CPU wakelocks.
I've got Google Now turned on, the "OK Google" keyword detection turned off, location reporting on, location history on, and location services set to high accuracy (I use navigation and what not and would prefer to not have to toggle it constantly). Please see the attached screenshots.
Some googling of my own told me it's location reporting keeping it awake, which I'm afraid is the case, as I didn't have this issue for a while when it was off (it's also been on for several days and I haven't had this issue).
So, I have two questions in total. Is it Google Now's location usage that's draining my battery and keeping my phone awake? Also, since this isn't an every night issue, do you have any suggestions or recommendations to solve it without losing Gnow functionality?
I am running Carbon (July 1st nightly) and the Franco Kernel r55. Thank you very much in advance, this issue has alluded me and annoyed me for months.
Update: upon further research, I'm seeing that blocking wakelocks from Google Search / Google Now related location services will eliminate the problem without affecting Gnow functionality - is there any truth to this? I've also seen people claim to have disabled location reporting without loosing their weather, nearby events, etc. I worry that disabling the wakelock will impede functionality because I don't have the screen on often while traveling. I just can't seem to get a straight answer!
Update 2: after a phone call to Google (yes, they actually gave me a good answer), I was told that Location Reporting *only* tracks where you've been to give you travel time and similar things. Turning it off doesn't disable weather, nearby events, parking location, and so on, so it's looking like just disabling it is a good place to start.
turbofandude said:
Hey guys,
I had the issue with the 40% battery burn overnight again. According to WLD, the CPU was awake for 96% of the ~11 hours since it was charged (which explains it). I want to make sure I'm reading these right, so I've posted screens of wakeup triggers and CPU wakelocks.
I've got Google Now turned on, the "OK Google" keyword detection turned off, location reporting on, location history on, and location services set to high accuracy (I use navigation and what not and would prefer to not have to toggle it constantly). Please see the attached screenshots.
Some googling of my own told me it's location reporting keeping it awake, which I'm afraid is the case, as I didn't have this issue for a while when it was off (it's also been on for several days and I haven't had this issue).
So, I have two questions in total. Is it Google Now's location usage that's draining my battery and keeping my phone awake? Also, since this isn't an every night issue, do you have any suggestions or recommendations to solve it without losing Gnow functionality?
I am running Carbon (July 1st nightly) and the Franco Kernel r55. Thank you very much in advance, this issue has alluded me and annoyed me for months.
Update: upon further research, I'm seeing that blocking wakelocks from Google Search / Google Now related location services will eliminate the problem without affecting Gnow functionality - is there any truth to this? I've also seen people claim to have disabled location reporting without loosing their weather, nearby events, etc. I worry that disabling the wakelock will impede functionality because I don't have the screen on often while traveling. I just can't seem to get a straight answer!
Update 2: after a phone call to Google (yes, they actually gave me a good answer), I was told that Location Reporting *only* tracks where you've been to give you travel time and similar things. Turning it off doesn't disable weather, nearby events, parking location, and so on, so it's looking like just disabling it is a good place to start.
Click to expand...
Click to collapse
The data we need to see isn't shown in your screenshots. This is why I prefer BBS. You can just post a log and nothing will be missing.
Aerowinder said:
The data we need to see isn't shown in your screenshots. This is why I prefer BBS. You can just post a log and nothing will be missing.
Click to expand...
Click to collapse
Ugh, I knew I should have left it. I've got it installed now and will post a screenshot if it happens again. I've got Location Reporting turned off. I want to see if it will still give me the features I want, and if the battery drain issue stops, yippee. I will leave BBS there, however, in case it happens again.
turbofandude said:
Ugh, I knew I should have left it. I've got it installed now and will post a screenshot if it happens again. I've got Location Reporting turned off. I want to see if it will still give me the features I want, and if the battery drain issue stops, yippee. I will leave BBS there, however, in case it happens again.
Click to expand...
Click to collapse
All of the wakelocks that start with Nlp are due to location. Switching the location mode to Device only will stop them. Anything that relies on GPS still works fine. This should be the default setting.
I did a factory restore of the phone, latest Gapps, Carbon rom (07/07 nightly + 07/06 firmware), latest ElementalX Kernel now (so far, better temp/performance + equal or better battery). I know it's only an hour's worth of use, but a problem is pretty apparent.
Location reporting/history is off, Gnow is enabled, keyword detection is off. WiFi is on, and location services are in high accuracy mode. Why is a wakelock created by never released and how do I avoid that?
Is there any reliable setting I can use to avoid a random software issue eating up my battery? This inconsistency is driving me insane.
Found something helpful today.
Many of you must have noticed that "NlpCollectorWakeLock" keeps the phone awake for long durations (running into multiple hours per day sometimes). Now, it may appear that this has something to do with network location and one might think that disabling it would affect your phone's location capabilities. But, as it happens, this doesn't affect your phone's location capabilities. This wakelock is for something else apparently, so just go ahead and bypass it! Here's the method:
REQUIREMENTS: KitKat, Root, Xposed Framework
DOWNLOAD: "Wakelock Terminator" from Play Store
The app is accompanied by an Xposed Module, so you'll need to restart to enable it. Don't do any tinkering in the app before restarting.
After restarting, go in to the app, find "Google Play services", tap on it once, check the "Prevent Wake Lock" checkbox.
Tap on "Filter Wake Lock" and type in "NlpCollectorWakeLock" in the provided area. (Check the spelling and cases.) (Multiple entries here, if you fancy, need to be in separate lines. You can optionally include "NlpWakeLock" and "Checkin Service" - or "CheckinService" - though they aren't as big hoggers as the other one.)
Restart phone once.
DONE!
You should be able to see a visible reduction in battery drain. I did.
The good thing about this is it doesn't affect your phone's location capabilities. Maps will work as they should. Google Now's location-based features will work as they should.
Also, be aware, this doesn't completely disable the wakelocks. But it WILL considerably reduce the amount of time they are taking by spoofing them. (Read Wakelock Terminator's website)
Nevertheless, take it with a pinch of salt. Report any unforeseen side-effects here.
Hope this helps!
Oh, and here's where I found this.
Meanwhile on Planet Xposed:
There's another fix for the ridiculous Nlp wakelocks.
Check this out.
It increases the alarm interval at which Play services runs these wakelocks. This is certainly a better approach as it will still allow you all the functionality of the Google Location services. By default, Play services has an alarm interval of 60 seconds (yep, that often). This Xposed module will let you increase that to any value (I'm currently keeping it at 10 mins). Please note, the UI where you can change these intervals is currently accessible only through the Modules page in the Xposed Installer app.
Don't forget to unblock the wakelocks from Wakelock Terminator or CM Privacy Guard (if you have done so).
I have disabled Location reporting / History, wifi scanning and location itself.
But when I check privacy gaurd I see Location services, Play services and android system using fine location, cell scan and wifi scan.
Can anyone suggest what to do to stop google from accesing my location completely?
Any one?
mkiriti said:
I have disabled Location reporting / History, wifi scanning and location itself.
But when I check privacy gaurd I see Location services, Play services and android system using fine location, cell scan and wifi scan.
Can anyone suggest what to do to stop google from accesing my location completely?
Click to expand...
Click to collapse
Here is an solution, it also improve your battery life
Google has been recommending developers use Google Play Services for Android Device location GPS functionality which allows for Google Play Services to batch GPS requests, hopefully preserving battery life. However, developers still have access to the native Android location APIs which they could leverage to request device location.
Example image:
The solution
Fortunately if you’re using Cyanogenmod on your device, you can use the built-in Privacy Guard feature to limit Google Play Services ability to wake the device, which will permit your device to stay asleep unless you’re actively using it. You can also keep Google Play from being able to keep the phone awake, which will allow your device to sleep quicker, preserving battery for Angry Birds and Pandora.
Keep in mind, there are pros and cons to everything.
So, it’s not my fault if your everything begins to suck once you do this. The easy thing is that you can make changes, then toss your phone in your pocket and check back later and see if there is a noticable improvement in battery life. You will see in the same UI I’ll show below a long listing of how many times permissions were requested and if they were denied or not.
Consider denied events to be your battery life getting longer and longer
So, step one for your GPS problem + better battery life, go to settings on your device. Go down to Privacy.
Go to Privacy Guard
Click the three dots / hamburger bun / overflow menu and check the box for Show built-in apps.
Wait…it takes a LOOONG time to list all of the apps. Browse down to Google Play Services and then long press on the icon.
Scroll down to the options and based on the pros/cons above, choose your destiny and toggle some of the options.
Restart phone.
DONE.
Google wont start the GPS like you requested
Your battery life is also improved because Google Play Services is disabled :good:
Extra info
To reserve back, turn the options back to ON you have disabled.
NOTE: You will get an error popup that Google Play Services stopped if you start your GPS for example "Navigation" like TomTom, Navigon, ETC.
I hope it helped.
Stanely thank you for your reply, however the original question I had asked was different.
Why is play services using cell scan and wifi scan even when location is completely off? What else do i need to disable to stop it?
Also denying keep awake and wakeup causes play services to crash.
Been finding a solution couple of years now.Is there any way to completely turn off google track my location?Google has always a way to track us,even location services are completely turned off.