Better Battery Stats - what's causing "NetworkStats" & related Partial Wakelocks?
I think I've isolated my battery drain down to a few things through BetterBatteryStats and GSam Battery Monitor:
1. "NetworkStats" as the longest Partial Wakelock and "RILJ" and "AlarmManager" as the highest count Partial Wakelocks in Better Battery Stats.
2. In GSam battery monitor "Android System" is almost always #1 for number of times waking devices, and usually followed in #2/3 by "Google Maps" and "Google+". Google+ sync'ing is turned off, but the "Sync Instant Upload" is turned on. I can't for the life of me figure out why Google Maps is always high on this list, even when I don't open the app all day.
Does anyone have any tips for how I can figure out what is triggering these NetworkStats/RILJ/AlarmManager/Android System/Google Maps wakelocks?
I'm thinking they are all related to each other through something like Calendar, or some other Android service gone awry. I don't know of any other way beyond Better Battery Stats and GSam to isolate the drain down to something more specific and measurable. Any thoughts or tips are appreciated.
Just wondering, is Google location services, gps satellites, location and Google search turned on?
erwaso said:
Just wondering, is Google location services, gps satellites, location and Google search turned on?
Click to expand...
Click to collapse
I did not turn off Google Location Services.. what apps/services fall under that?
I also did not turn off Location and Google search, but that shouldn't be causing wake locks when I'm not using my phone, right?
GPS Satellites were turned off.
I have the same issue on my nexus. I have all three option disabled but get google keeps have the network location service running in the background. I even cleared maps cache and force stop. it really annoying
r29 said:
I have the same issue on my nexus. I have all three option disabled but get google keeps have the network location service running in the background. I even cleared maps cache and force stop. it really annoying
Click to expand...
Click to collapse
Sorry to hear - but glad to hear I'm not the only one that has noticed this. Are you running stock, custom rom, or what? One suspect is the HTC weather widget, I have that on my home screen but it's set to sync only once every 4 hours.
There must be some way to delve into what is triggering "NetworkStats".
So some of the things I've done so far that have helped:
Uninstalled the applications on{x} and Pageonce. Both were regularly showing large amounts of wake locks.
Disable Google+ sync'ing in BOTH Settings->Accounts AND within the Google+ application. Within Google+ there are separate Notification, Messenger, and Hangout sync settings. I'm not positive that disabling from within the app is necessary but I was still getting wake locks from Google+ after disabling it within Settings->Accounts. I'll know soon enough if that helps.
Disable redditnews from checking for new mail. I had accidentally set this to check for new reddit mail every 15 minutes!
Disable GPS satellites, Google Location Services, and Location and Google search from within the Settings->Location menu. I did this to see if it would eliminate the Google Maps wake locks that I can't seem to get rid of or pinpoint the cause of. It's only been a day but it seems the Google Maps wake locks have been cut down, but not completely. It's driving me crazy not knowing what is triggering Google Maps to wake lock my phone. The hunt continues...
I am on a custom rom LiquidSmooth 4.0.4 base.. I have tried removing anything that deals with maps but that stupid service still starts
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
Since I (involuntarily) had to upgrade to firmware 14.4.A.0.157, I noticed unwanted periodic (~every 15min) location pings.
After a long time of trying to determine the culprit, I'm pretty sure it is "Google Play Services 6.5.99 (1642632-036)". If I downgrade it to version 6.1.05, the periodic location pings disappear.
My location mode is "Device only" because I don't want Google to send anonymous location data in the background.
I set "Location reporting" and "Location history" to "Off".
BTW, these settings are rendered in a grey fonts suggesting they are disabled, but I can operate them. I'm guessing this is Google trying to discourage people to mess with these settings, but the grey font could also be an indication of an issue. When I use a very old "Google Play Services" version, the font is black. Can anyone confirm this is normal?
I don't have any wake-lock problems, I just don't want these completely pointless (GPS does not work indoors) and battery consuming (GPS takes a toll on battery) location pings.
I suspect new versions of "Google Play Service" do more location pinging because of the recent "Google Fit" integration, but that's just conjecture.
Can anyone confirm the location pings?
With the above settings (I guess the location mode is important, otherwise GPS won't be used), you should be seeing periodic ticks in the "GPS on" bar when looking at the "History details" battery usage chart by going to "Settings | Power management | Battery usage" and tapping on the top chart.
Any ideas of what I could be doing instead of repeatedly reverting to Google Play Services 6.1.05? The shame is that they automatically update to 6.5.99 from time to time. I don't get how the latter is possible without the user's consent, in particular Goog
If you are that conseious, why not turn off Location Service all together ?
I'd suggest confirming weather indeed Location Pings are happening or not. Install [APP][2.1+][21 Dec. - V2.0RC4] BetterBatteryStats Follow the instructions on that thread on how to install and pull an Idle Log. Take a look at the Text Log. If it has Entries such as "NLP Service" then there are pings. It will also tell you which application is requesting location.
You might also wish to review [GUIDE] Insanely Better Battery Life When Idle - Battery Life Thread
It might not be your device, but the thread is applicable nonetheless.
Perseus said:
If you are that conseious, why not turn off Location Service all together ?
Click to expand...
Click to collapse
If I want to use an application like Maps, I'd like to be able to simply start it and use it without having to manually enable "Location Service" first (and then disable "Location Service" again, once I'm done).
This has been working fine before and I believe it is reasonable for "Location Service" to be enabled all the time but actual resources (like GPS) only be used when necessary.
I may should add that I'm not too worried about my location being known -- although I deny browsers and apps to know about my location per default because it is nobody's business where I am, I'm not overly fuzzed if something should leak -- but I'm against anything depleting my battery, in Google's case probably for their good, rather than mine.
Perseus said:
I'd suggest confirming weather indeed Location Pings are happening or not. Install [APP][2.1+][21 Dec. - V2.0RC4] BetterBatteryStats Follow the instructions on that thread on how to install and pull an Idle Log. Take a look at the Text Log. If it has Entries such as "NLP Service" then there are pings. It will also tell you which application is requesting location.
Click to expand...
Click to collapse
Thanks a lot for this suggestion, but I understand doing the above would require a "rooted" phone. I'm using a stock ROM, non-rooted, bootloader locked and initially planned to just use the phone, instead of discovering a whole new world of spending one's time.
I can see that I will eventually become someone running a custom ROM (e.g., to get back AppOps), but for now I just want to enjoy the phone (retaining warranty being part of the motivation).
Perseus said:
You might also wish to review [GUIDE] Insanely Better Battery Life When Idle - Battery Life Thread
Click to expand...
Click to collapse
Thanks heaps!
I'll have a look now.
Greetings,
After going through many forums trying to find a solution for these Wakelocks, all I found was switching off Location or Google Location History to get rid of RILJ and using Amplify to increase the interval of Nlp.
However, Turning off location or GLH is not a practical solution for me, and Amplify is not that easy to work with, so I was back to square one.
I found out that Nlp Wakelocks are associated with Google Play Services, Google Services Framework. RILJ is associated with Phone (Telephony) functions.
*The solution:
An Xposed module called (No Wakelock) in the Play Store that is capable of controlling Partial and Full WLs, aligning alarms and controlling sync for the selected apps, including system apps with the donation package.
*The results:
After disabling Partial/Full Wakelocks and enabling Aligning alarms for the aforementioned apps, Location and GLH are On.
They are no longer showing in BBS or WLD. AT ALL.**
Android Device Manager is capable of locating my phone.
SMS/Phone calls are working Fine.
No Frozen Screen, SoD, etc.
Gmail sync is delayed a few hours/minutes, without changing its settings in the module.
** Since everything is working perfectly fine even though these WLs are not showing at all, then what is the Real purpose of having them working in excess like that?
Kindly note that I'm not affiliated with the module or the developer in anyway.
If you would like to use it, please use common sense and do it at your own risk.
Cheers.
What did you disable?
I'd like to know that too
do you have fix for nougat? i use forcedoze and it works well with every service. But google services still trigger wakelock and drain my battery.
However, this problem had a temporary fix, if i switch on battery saver. this problem will stay away for awhile.
But i don't like this kind of method.
im also interesting how to fix it in Nougat
On stock and android 11 unrooted phone.
Coming from rooted android 10 the battery drain is way higher on android 11
Done all the usual stuff to stop drain and debloated few things but what else can anyone recommend for battery saving
Thanks
Things that help me are:
DEBLOAT
Debloat Oneplus account
Debloat Oneplus cloud
Debloat Oneplus wireless emergency alerts.
Debloat Google Pictures
Debloat Google Movies
Debloat Google Music
Debloat Google Gmail
SETTINGS
WIFI Scanning settings: Turn OFF
Bluethooth/Printing : Turn OFF
NFC: OFF, never use it.
Adaptive brightness : OFF ( Always adjusting consumes battery)
Use a dark Wallpaper & Screen time out is 30s
Notification, only allow the apps you want. Or switch off, every notification wakes the phone from Doze mode.
Location: OFF
Battery : Optimise every user app, including Google Play store & Google Play Services (Battery HOGS)
Accounts: Switch Sync data off
Hope this helps you.
@soka said:
Things that help me are:
DEBLOAT
Debloat Oneplus account
Debloat Oneplus cloud
Debloat Oneplus wireless emergency alerts.
Debloat Google Pictures
Debloat Google Movies
Debloat Google Music
Debloat Google Gmail
SETTINGS
WIFI Scanning settings: Turn OFF
Bluethooth/Printing : Turn OFF
NFC: OFF, never use it.
Adaptive brightness : OFF ( Always adjusting consumes battery)
Use a dark Wallpaper & Screen time out is 30s
Notification, only allow the apps you want. Or switch off, every notification wakes the phone from Doze mode.
Location: OFF
Battery : Optimise every user app, including Google Play store & Google Play Services (Battery HOGS)
Accounts: Switch Sync data off
Hope this helps you.
Click to expand...
Click to collapse
Thanks for the above
Optimise the battery on most apps and not getting some notifications ie Gmail so take it this is one of the side affects
Yep, stuff that runs in the background always eat battery. Especially Google apps.
@soka said:
Yep, stuff that runs in the background always eat battery. Especially Google apps.
Click to expand...
Click to collapse
Goggle play Services, Playstore, Google backup Transport and Framework are prime offenders.
The former two I kept disabled unless I need them. The latter two are package blocked.
Sync is turned off. Gmaps is kept firewall blocked unless needed otherwise it constantly is running in the background.
@soka said:
funkyirishman said:
Thanks for the above
Optimise the battery on most apps and not getting some notifications ie Gmail so take it this is one of the side affects
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Optimization can eat battery and cause erratic behavior. Developer options>Standby apps, all buckets should show as active. Otherwise power management is active and it will cause trouble.
Dependencies... disabling some apps can cause seemingly unpredictable consequences and higher battery consumption. Goggle play Services has lots of dependencies but killing it saves battery. Turning off location helps too.
Turn off all carrier, manufacturer and app feedback.
Disable OTA updates; only update if proven to be worthwhile. Most updates harm the usability and provide little improvement. If the phone is running fast, stable and fulfilling its mission leave it be. Most carrier Android phones need to be optimized or they will run like pigs. Updates generally just complicate the optimization process.
Each Android and user are unique requiring different solutions. Play with it.
With Google you're not the customer, you're the product... the less Gookill, the better.
blackhawk said:
Goggle play Services, Playstore, Google backup Transport and Framework are prime offenders.
The former two I kept disabled unless I need them. The latter two are package blocked.
Sync is turned off. Gmaps is kept firewall blocked unless needed otherwise it constantly is running in the background.
Optimization can eat battery and cause erratic behavior. Developer options>Standby apps, all buckets should show as active. Otherwise power management is active and it will cause trouble.
Click to expand...
Click to collapse
Was looking at this but what do you mean by 'all buckets'?
Some of the apps are on WORKIng_SET /ACTIVE or RARE and a few on FREQUENT
Anything to do on these to save battery
Also I have Dont Keep Activities ticked but even when I close the apps its still running and press clear all
funkyirishman said:
Was looking at this but what do you mean by 'all buckets'?
Some of the apps are on WORKIng_SET /ACTIVE or RARE and a few on FREQUENT*
Anything to do on these to save battery
Also I have Dont Keep Activities ticked but even when I close the apps its still running and press clear all
Click to expand...
Click to collapse
*These are the buckets. Google terminology not mine. More Google bloatware.
If you can't change their run state there then power management is disable... as is best.
Simple close apps when done with them.
If they continue to cause trouble try limiting background battery and/or data usage.
Ditch the really bad actors if can't get them to behave.
Power management apps will cause nothing but trouble and eat battery. Android manages its self well without this junk with well written apps.