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.
Lately whenever I'm flashing a new kernel either on KitKat or Lollipop I get terrible wakelocks that kill my battery. Not sure why this is happening. I'm using CWM. Basically after flashing I can just notice a huge battery drainage and I tend to install either GSam or WakelockDetector to see what's the problem. WakelockDetector (Rooted) gives me an overall idea of my battery problem. Usually SystemUpdateService, Audiomix "1013", "NlpWakeLock" , "EventlogService" and "CheckinService" drain my battery the most. Sometimes "ConfigFetchService" as well.
Thanks
KodRoute said:
Hey guys.
Lately whenever I'm flashing a new kernel either on KitKat or Lollipop I get terrible wakelocks that kill my battery. Not sure why this is happening. I'm using CWM. Basically after flashing I can just notice a huge battery drainage and I tend to install either GSam or WakelockDetector to see what's the problem. WakelockDetector (Rooted) gives me an overall idea of my battery problem. Usually SystemUpdateService, Audiomix "1013", "NlpWakeLock" , "EventlogService" and "CheckinService" drain my battery the most. Sometimes "ConfigFetchService" as well.
Thanks
Click to expand...
Click to collapse
[Battery Life Help] Troubleshoot battery issues here!
Application wakelocks have absolutely nothing to do with the kernel.
Keep in mind a "wakelock" is simply a request to keep the device awake; they can happen regardless whether the screen is on or off, they are only an issue if they occur while the screen is OFF.
SystemUpdateService is a pretty obviously named wakelock, it's used while an OTA is being downloaded. You can disable the service and it's receivers with an app like Autorun Manager (https://play.google.com/store/apps/details?id=com.rs.autorun, open in advanced mode, go into it's settings to enable for system apps, tap on Google Play Services, disable everything with SystemUpdateService in it's name).
AudioMix is triggered every time there is an audio event, including touch sounds. Harmless as it's usually only used while the screen is on.
NlpWakeLock is a location wakelock.
EventlogService and CheckinService are harmless, unless they occur 24/7 and don't go away EVER, which means you disabled their services but not their receivers.
ConfigFetchService is mostly harmless, it simply fetches your settings from Google's servers when you open a Google app, if that app stores it's settings on the cloud instead of locally.
Lethargy said:
[Battery Life Help] Troubleshoot battery issues here!
Application wakelocks have absolutely nothing to do with the kernel.
Keep in mind a "wakelock" is simply a request to keep the device awake; they can happen regardless whether the screen is on or off, they are only an issue if they occur while the screen is OFF.
SystemUpdateService is a pretty obviously named wakelock, it's used while an OTA is being downloaded. You can disable the service and it's receivers with an app like Autorun Manager (https://play.google.com/store/apps/details?id=com.rs.autorun, open in advanced mode, go into it's settings to enable for system apps, tap on Google Play Services, disable everything with SystemUpdateService in it's name).
AudioMix is triggered every time there is an audio event, including touch sounds. Harmless as it's usually only used while the screen is on.
NlpWakeLock is a location wakelock.
EventlogService and CheckinService are harmless, unless they occur 24/7 and don't go away EVER, which means you disabled their services but not their receivers.
ConfigFetchService is mostly harmless, it simply fetches your settings from Google's servers when you open a Google app, if that app stores it's settings on the cloud instead of locally.
Click to expand...
Click to collapse
Disabling the receivers works indeed. Thanks! By the way, another issue I'm having is that my Nexus 5's CPU heats too fast operating in UI and doing basic stuff, like installing apps from Play Store or watching videos on YouTube. Normally after about 5 min. of running if I go to System Monitor the CPU's temp is around 40-47ºC on action, in standby cools down to 34-35ºC but then after I use it again the temp rise to 45-47ºC. Usually when this happens the battery's temperature is also triggered and reaches 28-30ºC. Is this normal?
KodRoute said:
Disabling the receivers works indeed. Thanks! By the way, another issue I'm having is that my Nexus 5's CPU heats too fast operating in UI and doing basic stuff, like installing apps from Play Store or watching videos on YouTube. Normally after about 5 min. of running if I go to System Monitor the CPU's temp is around 40-47ºC on action, in standby cools down to 34-35ºC but then after I use it again the temp rise to 45-47ºC. Usually when this happens the battery's temperature is also triggered and reaches 28-30ºC. Is this normal?
Click to expand...
Click to collapse
The CPU throttles at 65C by default (some kernels change this or give you an option to change it), and shuts down at 105C. 47C is hardly anything.
Hi all,
I have a Pixel 4a with stock Android 11 (up to date, no root, with Nova Launcher).
I have a rowing machine that comes with an app (ErgData, by concept2) that can connect to the machine via bluetooth or via usb cable: while rowing the app logs the workout data (like pace, heart rate etc).
I wanted to do the following: watch a video while the ErgData app logs my workout, so I started ErgData, connected it to the rower, configured the workout and, once ready to start rowing, I switch to the video player and start rowing.
It worked fine a bunch of times, but one day it stopped working: at the end of the workout (like after 20-30min), when I switch back to ErgData the app is in its default screen (like the one you get at startup) and it has logged nothing. When connecting via bluetooth, the app has also lost the connection to the rower. When connecting via usb the connection is there but the app has still logged nothing.
Things I've done:
disable battery optimization for ErgData, Bluetooth and Bluetooth MIDI
disable adaptive battery
use a different media player (android built-in, VLC)
uninstall / reinstall ErgData
clear Bluetooth storage/cache
disabled "Suspend Execution for Cached App" (developer mode)
No joy.
I tried a different app (ErgZone) and it has the same behavior.
I tried staying with ErgZone foreground for 3min before switching to the video player and in that case, ErgZone logged something, but not the totality of the workout.
So it really seems that somehow, when I switch to the video player, ErgData / ErgZone gets "paused" (killed ? cached ?).
Anything I can try ? Anything the app developers should do to prevent this ?
Thanks !
Sorry for the late response, I normally dont browse this forum. I am rooted and always have been, so all the solution I have used in the past are dependent on root. However, one idea to try is checking if the background app is killed while the phone is plugged into a charger? I know that being plugged in keeps the phone awake even when the screen is off.
HornetMaX said:
So it really seems that somehow, when I switch to the video player, ErgData / ErgZone gets "paused" (killed ? cached ?).
Anything I can try ? Anything the app developers should do to prevent this ?
Click to expand...
Click to collapse
Does the ErgData/Zone app start a persistent notification when recording? That's the way to keep a service running in the background. I had a phone with a tendency to kill anything not in the foreground, but it never killed active apps (including background with persistent notification).
If the app dies despite this, there may be a hint in the logcat. You have to enable developer mode to fetch that.
a1291762 said:
Does the ErgData/Zone app start a persistent notification when recording? That's the way to keep a service running in the background. I had a phone with a tendency to kill anything not in the foreground, but it never killed active apps (including background with persistent notification).
If the app dies despite this, there may be a hint in the logcat. You have to enable developer mode to fetch that.
Click to expand...
Click to collapse
No, ErgData/ErgZone do not have a persistent notification. Guess that's a potential solution then.
At the moment my workaround is to use the "pop-up" feature of VLC so that I have the video on top of the other app (ErgData/ErgZone), so that the other app stays foreground. That works, but it's not a real solution.
Hmm they gave me a beta version of the app with the persistent notification thingy and it works perfectly.