Related
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
Welcome to the new Battery Life Help thread.
Please post the recommended screen shots from post 4 when posting here.... Or you will only get guesses as replies... If you get any.
Read the first 4 posts here before posting. You may not even need to post after you have!
If you are on a device other than a Nexus 5, that's fine, but please state that up front.... Or things may get confusing for all of us. ?
I'm not the "technician" of this thread, as there are many knowledgeable members on battery life savings and troubleshooting. Sometimes opinions vary... And that's always how things are...especially on the interwebz. Usually that's a good thing.
All are encouraged to participate!!!!
Most battery issues are non device specific.... Most. And troubleshooting is almost universal. Occasionally there's device specific issues and bugs, but mostly its about basic setup and usage patterns. No matter the device.
So, some guidelines to make finding issues efficient. (A lot of this won't be possible if you are not rooted....so do your best)
1. Please please please.....use Gsam (my favorite) or Better Battery Stats (BBS) or Wakelock Detector when posting screenshots. No one can stop you from posting shots from the stock battery usage screens in settings....but 9 times out of 10 you'll be asked to use one of the above apps....cause the stock screens say to little to be useful finding an issue. Just install one of the apps. Use it until your issue is solved...then get rid of it if you wish. Tho really, they are great tools to have, and NO, they don't consume heavy amounts of battery life. At all.
2. No screenshots will probably get you no useful help. As any attempt to assist you would just be guesses and generic tips.
3. As of Kit Kat, you either need an xposed module found Here or if you use Gsam, also install Gsam Root Companion. Both found on Play Store. Without any of those, you can't see wakelocks in Kit Kat.
4. Here are the standard screenshots that will get you the quickest help. In Gsam anyway....or the equivalent screens in the other apps.
For Gsam, you should post....
- The main screen.
- App sucker screen.
(In app sucker, click the drop down for the rest...)
- Times waking device.
- Time held Awake.
- Kernel wakelocks.
Yes, that is 5 screenshots. A lot I know. But together those will give almost all the info needed to help you. Usually.
5. Obviously, above your screenshots, post your issue in as much detail as possible. Like your setup (location on or off... Gnow on or off...screen settings...signal strength on Data especially... And anything else you feel may matter) and your usage. Gaming? Navigation? Etc.
All of the above will lead to much quicker help, without the need for people trying to help having to ask you a bunch of questions.
Be patient!! Some battery issues are very hard to lock down.....but 95.6 percent of them can eventually be solved. And remember....usage plays a big part! You may be stuck with 3 hours screen on time because of your usage. Sorry. Games for example. And a really poor signal strength while on data is a battery death march.
Tips for better Battery Life
These tips are going to be a collection of all I know, as well as contributions from you guys over time...that I will add in. Unless of course I completely disagree. Lol. (I.E. Task killers, Juice Defender type apps....etc)
First thing is first, since it seems to cause the most problems......and so many can't live without it. Lol. Location Services.
Location Services
Location Services is so very poorly implemented in Android, its almost absurd. The service itself isn't so much to blame for battery issues, but its weakness to getting exploited by other apps. Social apps being the worst offenders. Its also very hard to pin down the offending apps. Yes, many have no issue with location services. They're the lucky ones. Sooooo many do lose a tonne of battery life to it tho, usually by excessive wakes caused by apps accessing it.
So, my first piece of advice. TURN IT OFF! Use your toggles. On when needed, off when done. It doesn't take long, its a couple clicks. Guaranteed you see FAR greater battery life because of it.
If you must use it....just must.....know that Batter Saver is NOT the most battery friendly setting. Device only is. (GPS only). Don't know why, talk to Google for an explanation. Signal strength for data I bet. And of course, high accuracy will drop your battery the quickest.
Location history reporting. Battery killer.
Android Device Manager. Found in Google settings app. "Remotely locate this device", battery killer. Neat feature....but will cost you battery time. And the other option, "remote lock and erase"....surely takes its share of the battery pie also.
So, device only is your best bet, but not so great indoors. Probably won't find the satellites. But it will be far better on your Juice. One way to use location on and help stop apps from abusing it, is Grrenifying the apps that use it, or using app ops or its equivalent to change app permissions and disallow them location permission.
K, I bashed on location enough. But it is the number one item in most issues I see.
Signal Strength
A weak signal is about the quickest drain a phone can have. If your signal is very weak and spending time out of service and scanning for a signal.....your battery can literally drop like a rock. The worst part, Gsam and similar apps don't really indicate the signal, radio or anything else is draining your battery. I'm not sure why these apps can't report the loss from signal, but I guess its just not possible.
Very hard to "fix" this issue.
- Your first option, get on WiFi. Its not really the text and phone part of the radio draining you, its data. If your signal is poor or non existent and apps are trying to sync over data.....the phone is working overtime trying to transfer the data. Getting on WiFi will fix this. Even with poor signal strength on the radio.
- Next option, toggle off data in poor coverage. No, your social apps and what not won't work. But you'll still get texts and calls. When you have a signal. This will dramatically slow the battery drain.
- Last option. Airplane mode. Yes, you will be completely cut off from the world. But your battery will barely drop.....assuming you have no issues and your standby drain is good.
Of course, combine poor signal with location services on high accuracy or battery savings....with data on....and you will be charging by lunch time or have a dead phone.
Roms and Kernels
I won't say much about this. There's those who will agree with me and those that always ask "what's the best ROM/kernel for battery life?". MOST experienced users will agree....ROM/kernel combos will make minor differences occasionally. Its all about setup and usage.....and signal strength.
I always say.....I could run any ROM or kernel (and I almost have) and will still get 24 hours plus with 6 hours SoT consistently, with my lean setup and low CPU demand usage. Guaranteed. Now, if you want me to prove it.....I wanna be paid for my time. And I'm not cheap.
Kernel tweaking, such as under volting/clocking, may gain you small battery life returns at best. And also possible lag and instability. Lots will disagree with me here. But thoroughly test it out yourself and see. ��
But to each their own I always say. Personally, I can't remember the last time I changed any kernel settings from whatever one I'm running. I just don't see the point. Fun and experimentation perhaps.....but big battery savings.....not gonna happen.
Last kernel thing......double tap to wake, even with the timeouts it has now.....lots of battery drain.
Greenify
I use it. Some don't. I use it on anything I know is going to run when it feels like and possibly steal my battery juice or cause any issues. One app I've always greenified is Maps. If it comes with the ROM, I convert it to a user app with titanium backup and then Greenify it. Games, any I ever have, greenified. I don't need or want to know my farm is ready to harvest. Lol. I'll find out when I open the game.
Use at your discretion. I wouldn't Greenify anything I use often, like dolphin or Tapatalk.....it'll just use more juice constantly loading them into memory. Social also won't sync if greenified. And be very careful greenifying system apps. That can cause you issues for sure.
Greenify tip from @Lethargy:
The paid version of Greenify let's you choose an option for Greenified apps called GSM push, when used with Xposed and the Greenify module activated. It allows you to still receive push notifications from hibernated apps. So you can Greenify those social apps that like to spam location services and burn data when your not even using them....and they will be awoken when you get a push notification. Will help with the drain from these apps better than doing nothing with them for sure! . A happy middle between always running and totally hibernated.
Screen Brightness
I think we all know a bright screen will cost you lots of juice. Out in the sun, there's not much we can do about it. I go back and forth sometimes. If I'm outside all day, I just usually put on auto brightness. But, nothing will help you save juice more than setting it manually. Someone not long ago mentioned an app called "Display Brightness ". Its free, and puts a very customizable slider anywhere around the edge of your screen that you want it. It gives you a quick access slider on your screen and its always there no matter what app you're in. You can change its size, location, color, transparency... Etc. Great little app.
Anyway.....if you keep the screen as dim as is comfortable for you, you'll get big gains in battery time.
I'm not convinced about LUX and its equivalents.... But many swear by them. Definitely something to look at too.
Tasker
I know little of tasker, I've never really got into it much. I did pay for it....and can't say when I last used it. Lol
You can do amazing things with it....to automate much of the things I've mentioned. A great tool for sure!!!
I've just never minded using toggles myself.
A few Quick Ones
- The more vibrating your phone does, the more juice it will drink.
- Games. We all know they kill the battery fast. Nuff said. . (Keep the screen dim)
- Social apps and other things that sync....the more you have, the more your battery time decreases. Especially picture heavy ones, like Facebook. It takes data transfer and CPU time to load all those images. Also, some wake your device a crazy amount of times to keep you up to date with your friends. (See Post Number 3 for help on controlling these and much more!!!!)
- Task killers. Guaranteed they waste more battery than they claim they'll save. Opening apps over and over is far worse on the battery than them sitting in memory idle. (In most cases. Greenify the exceptions). Android RAM is meant to be used. Too much free RAM is not helping, its wasted RAM.
- Juice Defender and other battery saver apps. Most will agree, some may not....but again, waste more juice than they save. For a moderate to heavy user, setup juice defender and look at your times held awake later. It can easily get over 2000 wakes per day.
Now...for a very light user.....very light....like you barely touch your phone all day....then Juice Defender may actually help you. But only the very light user.
Summary
Not all of these things are for everyone....but with each piece of advice you take, you'll save a little more juice.
Is my phone no longer a smartphone? Many have said that. Lol. Well guess what....in a few clicks, my phones intelligence can skyrocket. I just don't need things running 24/7 when I don't need them....or never use them.
So, here is a quick checklist of what I personally do after I install any ROM. And again, my battery life is as good as most I've seen. I'm just sharing this, not suggesting everyone do it. And also, all of our needs, usage and apps we use vary.....so there's no way to all have the exact same setup. Or the same battery times!!
After every install:
- I go into accounts/Google. Unchecked the things I don't want to sync. Usually I only have gmail, calendar and contacts checked.
- I turn location to device only, location history reporting is usually off for me by default, so I don't need to remember when I actually use it, then I turn it off completely.
- I go into Google settings app. In android device manager, they are both unchecked. Google Now is off. In ads, I check opt out of customizable ads. Location is already off.
- Sound settings. I uncheck all the options at bottom. No click sound, no vibrate on touch...etc. ( my keyboard makes no sound or vibration either). My phone only vibrates if I set it to vibrate. Otherwise it never vibrates on calls or notifications.
- I change a few cosmetics. (No battery impact here)
- I download titanium backup and restore my apps. Only user apps, and only data on the ones I don't want to setup again.
- change my wallpaper black. Not sure on an N5 if it helps battery life whatsoever.....its just my visual preference.
- Go into titanium backup and freeze, NOT uninstall...everything I never use.
- reboot.
- I Greenify all the apps I usually Greenify.
- Nova gets data restored, so not much to usually setup there. Its just how I had it.
- Restore the only widget I use. An agenda widget.
- Start LMT, Gsam, Display Brightness app and light flow...on some ROMs. The ones that have customizable notification LEDs by default, i don't use light flow. All of these get restored with data, so no setting up preferences required. Kii keyboard as well. And I disable the Nav keys.
Well, that's my setup routine. Again, to each their own. Just sharing my way. ��
That's all I have for now. Formatting (and spell and grammer check) will be tweaked to be easier to read in days to come. So no need to comment on my many mistakes. Lol. Plus additions I think are helpful from the community will be added. Along with credit, unless you don't want it.
Just whipped this up quick to help those that want it. I'll make it prettier soon. Promise!!
Good luck! ��
Managing syncs and services with "Disable Service"
Google Services drain? Syncs magically re-enabling themselves? Useless social app syncs?
Google apps and various social media apps use syncs. They'll put themselves under the "Accounts" section in Settings if they have any. At first the concept sounds fine, but the thing is, most of them are useless, abusively used and just waste your battery. Sync services cause wakelocks as they can't run while in deep sleep. Multiple syncs active causes dispersed wakeups, draining even more battery. Syncs also (for some unknown reason) sometimes re-enable themselves when you've unchecked them previously! Greenifying Google Play Services isn't a good idea since it'll constantly kill and automatically restart the services, which probably does more harm than good. It can also cause issues and break things, so what can you do about it?
There is a solution, use the app "Disable Service", found here: https://play.google.com/store/apps/details?id=cn.wq.disableservice
True to it's name, it allows you to selectively disable services for apps, completely preventing them from being used, as if they didn't exist:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see above, I only have a Sync for Gmail, it's the only one I have a use for and the others are completely disabled, not just unticked (they sometimes re-tick themselves..).
[Note: "* Google Play Services" is a hidden sync that's for Google Account settings, I can see it because I'm using the Greenify Donation Package along with Xposed, the feature called "Reveal Hidden Sync". Its integrated into the core of Google Play Services so you can't disable it completely without causing issues (unticking is fine). It doesn't cause any wakes anyways since it's only active for a moment when you manually change account settings in Google Settings (i.e. device is awake anyways and it's not like you're always changing the settings).]
Now Google Play Services, various Google apps and social media apps have a lot of services. How do we tell which ones to disable?
They have "Sync" in the name and begin with what they're syncing.
For example:
Under Google Play Services, PeopleSyncService is the sync for "People" under your Google account.
Under Google+, AutoBackupSyncService is the Auto Backup sync for Photos.
Simply uncheck the boxes to disable a service:
If you're unsure which sync is which, the best way to tell is going to the sync page (In Settings > Account, see the first screenshot of this post), then opening Disable Service, disable a service and see which sync disappears. Re-enable it if it turns out to be a sync you rely on. If you're not 100% sure what a service is for, feel free to mention me in this thread, I'll provide an answer if I know what is is.
Social media apps also use syncs for purposes such as "find your friends", "contacts sync" and "photo album sync". Useful for some, but not everyone. They also use syncs to "refresh" automatically while you're not looking at them. There isn't really any need for that.. I mean, it'll refresh posts when you open up the app again and your notifications are pushed to your device anyways, right?
Waste of battery. You can disable all these too with no issues. Extremely helpful if you have a bunch of social media apps which nag you for syncs.
Also keep in mind that Google apps put all their syncs under the Google account and you'll have to go their respective apps to disable them (usually with "Adapter" in its name, but not always). For example, the Google+ and Google Chrome syncs get merged under your Google account.
If you also have the Greenify Donation Package and Xposed Framework, you can enable "Wakeup Timer Coalescing". This feature causes your syncs to all sync at the same time, rather than leaving them to sync whenever they want. It'll save a bit of battery because it'll only need to wake once rather than multiple times. Useful if you still rely on a few actually useful syncs such as Gmail.
The Disable Service app is also useful for disabling useless services which other apps tend to activate even if they're not being used. One example is YouTube. It wakes up screen cast services even if they're not being used, which subsequently wakes up Google Play Services. If you never use screen casting, you can disable it so it won't wake Play Services pointlessly whenever you open YouTube. Examples of some other services you can disable if you don't use them are Wearable Services, Play Games, Analytics. Don't disable any services with "Gcm", "gtalk" or "push" in them or you risk missing notifications from apps which use GCM cloud to push notifications to your device.
If you never use location you can also disable everything with "geo" or "location" in it, so it'll be completely disabled. No more location wakelocks. Ever.
Do keep in mind that disabling some could render an app useless if it legitimately needs to use it.
Titanium Backup won't work on Disable Service as it doesn't actually store any data itself and disables it in the system ("pm disable"). The "cut off wakeup path" feature of Greenify Donation Package + Xposed does the same thing, but (as far as I know) temporarily as it stores it in Greenify's data, and you can only disable them once they come up, not selectively.
Luckily, Disable Service has a hidden backup/restore function which you'll probably miss. Its in Overflow Menu > About. Helpful when flashing new ROMs/clean flashing. Puts DS_backup.txt on your Internal Storage.
For a general idea of what most of us have disabled without issues, I've dumped screenshots of what I personally have disabled. Please note that not everyone's would be the same, and some people may still need specific services to be enabled. Here: http://imgur.com/a/YyPtT
Blocking the wakelock permission on Play Services isn't a bad idea either, see my post here: http://forum.xda-developers.com/showpost.php?p=54516634&postcount=332
If you're a user of location but you don't want the services to always be active when you don't need them (e.g. you only need them for driving/maps), you can use Tasker to enable and disable them. Create a new task, add action: Script > Run Shell. The command is "pm disable package.name/package.name.service".
e.g. for disabling AnalyticsService:
Code:
pm disable com.google.android.gms/com.google.android.gms.analytics.service.AnalyticsService
Make sure to check "Use Root". To enable a service you use pm enable instead of pm disable, of course. Try not to toggle them too much (e.g. enable/disable if Google Maps is open or not), as it'll probably cause a lot of lag. Manual toggles are probably best.
Enjoy your device without the annoyance of Play Services wakelocks/syncs:
(13% left, might've made it to 2 days with 7 hours SOT but I was tired so put it on the charger)
For those who want to disable OTA services (and it's possible wakelocks) PROPERLY:
Elluel said:
adb shell su -c pm disable com.google.android.gms/.update.SystemUpdateService
adb shell su -c pm disable com.google.android.gms/.update.SystemUpdateService$ActiveReceiver
adb shell su -c pm disable com.google.android.gms/.update.SystemUpdateService$Receiver
adb shell su -c pm disable com.google.android.gms/.update.SystemUpdateService$SecretCodeReceiver
adb shell su -c pm disable com.google.android.gsf/.update.SystemUpdateActivity
adb shell su -c pm disable com.google.android.gsf/.update.SystemUpdatePanoActivity
adb shell su -c pm disable com.google.android.gsf/.update.SystemUpdateService
adb shell su -c pm disable com.google.android.gsf/.update.SystemUpdateService$Receiver
adb shell su -c pm disable com.google.android.gsf/.update.SystemUpdateService$SecretCodeReceiver
Click to expand...
Click to collapse
(you can also just "su" then "pm disable com.whatever" via a Terminal app)
How to analyze and improve your idle battery drain
If you need help to analyze your battery life, please use BetterBatteryStats to report logs.
1. Charge your phone to 100% then unplug it.
2. Leave your phone idle for at least 7 hours (do not touch the screen)
3. Open BBS and make sure that the start reference is "Unplugged" and the stop reference is "Current" or "Screen on"
4. Hit the Share button, select "Text Dumpfile" and save. The file is stored in the root of your sdcard.
5. Attach it in this thread
Note: Make sure that "Enable while charging" is NOT checked in BBS > Settings > Advanced
Any other information and screenshots about your usage pattern might help.
Here are a few screenshots from last night
‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗‗
Gsam has a lot of easy to follow info available, if you have root companion as well, and know where to look. Many battery issues will show their faces in these screens somewhere. Many, not all.
Please go from 100% to 10 or 15 percent battery left before taking screen shots.....for an accurate idea what's going on.
Here are samples of the important Screenshots from Gsam. Include these in your post and other members will quickly get an idea of what's happening. Hopefully. (not all issues are easy to find)
These are from Gsam with Gsam Root Companion also installed. Without Root Companion, or if you are not rooted....you won't have all these available. So do what you can.
Main Screen
App Sucker Screen
Number of Times Waking Device (in App Sucker drop down)
Time Held Awake (in App Sucker drop down)
Kernel Wakelocks (in App Sucker drop down)
Also, if you have a weak signal a lot...maybe include Phone Radio screen
If your using Auto Brightness especially, the Screen screen can say a lot
And from the systems settings menu, under battery. Click on the graph for a more detailed graph....(tho really not necessary if you posted the first 5 above....and Radio screen if you think your signal is weak)
That's about it, from Gsam anyway.
I know we have a battery thread with 3000 posts....but its cluttered now, as all threads get eventually. Its in General, not Q&A, where troubleshooting is usually found. And its title is Nexus 5 battery results....designed to share times, more so than fix issues. It just became the go to issue place.
Time for a more new member friendly thread that stands out.
Reserved. For moi'
Good idea for the thread. It might also be helpful if you detailed your usage. Of course, people's usage should be what works for them and even if someone emulated your usage they will most likely get slightly different results. However, having said that I think a lot of people will ask for it anyway. I am curious myself as well of course =]
PsychDrummer said:
Good idea for the thread. It might also be helpful if you detailed your usage. Of course, people's usage should be what works for them and even if someone emulated your usage they will most likely get slightly different results. However, having said that I think a lot of people will ask for it anyway. I am curious myself as well of course =]
Click to expand...
Click to collapse
I'll be putting my setup, and general tips in post 2 when I get some time.
My setup is simple really, turn all the frills off. Toggle them when needed. Screen dimmer, and manually adjusted. Greenify anything that can hurt battery life. I don't usually game... I have an N7 for that. I mostly use the browser, Tapatalk...and text. Yes, boring, I know. Lol
And try not to be running data in poor signal coverage areas. That's number one! Use WiFi, or turn off data and use it only when needed. Texts and calls still work with data off.
My setup definitely isn't for everyone....but decent battery life should still be obtainable with a more robust setup. Its all priority. Give up some things, gain more time. Keep some things, lose some time. And definitely squash any abnormal issues. I've ran just about every ROM out there, and always got similar battery life...setup the same on all of them of course.
And I hope others will see what I put and add to it anything I missed.
As I said, this isn't MY thread to oversee.....its just hopefully going to be a more efficient place for help. Assuming the appropriate screenshots accompany the posts. ?
It will be simplistic, nothing fancy. I'm not much into kernel tweaks and what not, not for the small amount of battery life they can add.
The purpose of the thread is for people to post issues, and for people to help solve them.
My tips won't be new to most, just gathered in an easy to find location....especially to help newer folks.
Oh....and the answer to the majority of battery issues......Location Services. Lol
Not location services alone perhaps....but it and the apps using it combined.
Thank Google. They just can't seem to get location services right.
Want significantly better better battery life immediately? Turn it off. Yes, off. Toggle it when needed (2 screen touches usually....a swipe and a click). And toggle it off when done.
Best tip there is. Yes, a sacrifice to some....but usually, great results.
KJ said:
Oh....and the answer to the majority of battery issues......Location Services. Lol
Not location services alone perhaps....but it and the apps using it combined.
Thank Google. They just can't seem to get location services right.
Want significantly better better battery life immediately? Turn it off. Yes, off. Toggle it when needed (2 screen touches usually....a swipe and a click). And toggle it off when done.
Best tip there is. Yes, a sacrifice to some....but usually, great results.
Click to expand...
Click to collapse
So freaking true. I've set up my rom's tile to toggle between High Accuracy and Off. When I need maps or location, I hit the toggle and once I'm done, hit it again :cyclops:
Looking good
Sent from my Nexus 5 using Tapatalk
Just going to put this out there - if you put your brightness on the lowest settings and your device isn't awake too much while the screen is off (i.e. wake locks managed, Greenify/ROM's wake lock blocker), average screen on time should be 4-6 hours EASILY. Everything else is has minimal impact (apart from listening to music with the screen off, which would be keeping your device awake, nothing you can do about that.).
There is NO magic setup that will give you phenomenal battery life - short of a battery case but that doesn't count.
This is 4 and a half hours of continuous use, almost always SoT (4 hours 15 mins SoT). Just browsing forums on Tapatalk while listening to music. Still have a quarter left of my battery:
Sent from my Nexus 5
Lethargy said:
Just going to put this out there - if you put your brightness on the lowest settings and your device isn't awake too much while the screen is off (i.e. wake locks managed, Greenify/ROM's wake lock blocker), average screen on time should be 4-6 hours EASILY. Everything else is has minimal impact (apart from listening to music with the screen off, which would be keeping your device awake, nothing you can do about that.).
There is NO magic setup that will give you phenomenal battery life - short of a battery case but that doesn't count.
This is 4 and a half hours of continuous use, almost always SoT (4 hours 15 mins SoT). Just browsing forums on Tapatalk while listening to music. Still have a quarter left of my battery:
Sent from my Nexus 5
Click to expand...
Click to collapse
Agreed. ?
No, there's no "magic" setup, but 3 hours average to 6 hours average screen time is a huge difference. And setup, usage and signal strength all play a role. The more features off....the longer you'll go. Yes, screen is huge....but things like location services (along with a bunch of social apps) gnow, android device manager...and certain apps can also make a huge difference.
KJ said:
Agreed. ?
No, there's no "magic" setup, but 3 hours average to 6 hours average screen time is a huge difference. And setup, usage and signal strength all play a role. The more features off....the longer you'll go. Yes, screen is huge....but things like location services (along with a bunch of social apps) gnow, android device manager...and certain apps can also make a huge difference.
Click to expand...
Click to collapse
Agree 100%, but by "setup" I meant ROM, kernel, etc. I hate it when people claim that a certain kernel or ROM would give you better battery life - we know otherwise. To some extent maybe, but its only a minor impact compared to other factors that may influence your battery life.
But yes, setup in the form of apps and whatnot could impact battery life but really that's just down to your own usage and management. I have a bunch of social apps on my device but I have them managed properly with Greenify and whatnot. My battery life is fine.
In the end the only real excuse is signal strength. But I guess that's what this thread is for - to help people with the other factors.
And yeah, always nuke location. Its useless and just wants your battery.
Sent from my Nexus 5
The guys saying "my battery sucks", yet have every single feature on, auto brightness, 6 different social apps...etc...etc....are the ones who don't know these things. And they have 3 hours SoT. Well....that's about right. Lol.
So hopefully with tips on what to cut out....they can pick and choose what the can live without. And times will increase with each cut or change.
KJ said:
The guys saying "my battery sucks", yet have every single feature on, auto brightness, 6 different social apps...etc...etc....are the ones who don't know these things. And they have 3 hours SoT. Well....that's about right. Lol.
So hopefully with tips on what to cut out....they can pick and choose what the can live without. And times will increase with each cut or change.
Click to expand...
Click to collapse
You should add it to the OP along with mentioning that a ROM or kernel will hardly make your battery life any better.
And I just hit 5 hours SoT with 15% battery left. I'm doing this just to see how much SoT I would get since I don't drain my battery down very often - and my device is asleep 99.99% of the time the screen is off (with the exception of music lol) - its just good management.
Also, I do have autobrightness enabled - but since I'm on a custom ROM I've changed the brightness levels really, really low, stock values are horrible i.e. battery drainer.
Sent from my Nexus 5
Lethargy said:
You should add it to the OP along with mentioning that a ROM or kernel will hardly make your battery life any better.
And I just hit 5 hours SoT with 15% battery left. I'm doing this just to see how much SoT I would get since I don't drain my battery down very often - and my device is asleep 99.99% of the time the screen is off (with the exception of music lol) - its just good management.
Also, I do have autobrightness enabled - but since I'm on a custom ROM I've changed the brightness levels really, really low, stock values are horrible i.e. battery drainer.
Sent from my Nexus 5
Click to expand...
Click to collapse
Awesome!!
Post 2 will have all the tips I can think of, no matter how harsh...Lol. As well as tips others contribute. Like yours!
Probably won't get to it til the weekend.
This is not a good battery cycle.
unsivil_audio said:
This is not a good battery cycle.
Click to expand...
Click to collapse
Seems pretty good to me??
Its on the borderline of acceptable to me. Location set to device, no GN. I can't tell if FB is a killer or not. I mean my wakelocks are under control (40 mins of that is listening to music). My battery life really seems to vary by the day with virtually no setup changes. I'm going back to location off today. We'll see if it helps.
v----This on the other hand was awesome...
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.
Android 5.1 stock rom, everything is up-to-date.
Yesterday, before to go to bed I've done the following:
I turned off wifi, set the phone to plane mode and activated the power save under the battery settings (which should reduce a lot of things). Before to lock the screen my battery was at 57 %. After 8 hour my battery was at 44 %.
Thanks to "BetterBatteryStats" - BBS - I've found, under the "Alarms" section, that the process com.google.android.gms was reported to be active at 56 %.
I am sure that I don't have other WakeLocks, firstly because no Wake Locks are reported by BBS - and the deep sleep is correctly reported also by BBS, and secondly because the phone is only awake when the screen is on:
I ask to myself: why Google Play Store remains active when there is no active connection on my phone, and when the sync is disabled? Furthermore, under the wifi option I also disabled the option wifi scan always available.
I think I'm on the right way to solve this issue. I've done some research and I installed "Disable Service" from the playstore.
First of all, please keep in mind that I use just few Google Apps: Gmail, Google App (to use the vocal assistant) and the Play Store. With the following changes all these apps still work without issues (at least for now).
last night i left my phone in standby as yesterday (plane mode, wifi turned off and powersave activate): for 8 hours is always stayed at 91 % of charge
Here the services of which I got rid:
LockScreenService
BackupTransport
Googlelocationservice
GoogleLocationManagerService
GcmService
These four services were always active as background processes on my phone.
Then, using Gemini App Manager, I went to Google Play Services, and by going under "AppOps" I turned off the "Wake Lock" authorization.
Furthermore, I also disabled other services related to G apps which I don't use:
com.google.android.gms.drive.api.DriveAsyncService com.google.android.gms.fitness.sync.FitnessSyncAdapterService
com.google.android.gms.games.service.GamesSyncServiceMain
com.google.android.gms.games.service.GamesSyncServiceNotification
com.google.android.gms.drive.metadata.sync.syncadapter.MetadataSyncService
com.google.android.gms.plus.service.OfflineActionSyncAdapterService
com.google.android.location.reporting.service.ReportingSyncService
com.google.android.gms.kids.restrictions.sync.RestrictionsSyncService
com.google.android.gms.drive.metadata.sync.syncadapter.SyncAdapterService
com.google.android.gms.subscribedfeeds.SyncService com.google.android.gms.kids.timeouts.sync.TimeoutsSyncService
com.google.android.gms.fitness.wearables.WearableSyncService
and all services related to Google Drive.
But the above section i'm not sure which is useful, since I never seen these services active on my phone, also because I uninstalled a lot of g-apps (Drive, Games, Plus, Books, News, Music).
I will keep updated this discussion when/if I will encounter some trouble (eg I want to test Google Maps and the GPS).
Dude i got the same problem!! But i play quite a lot with my Mi4c so i sould care what i'm going to stop!
This thing is really annoying anyway :/
How did you uninstall them my ex synced our phones plus added things to spy but its not even letting me forcestop some of them what he has added and is remote using or bridgung....has able to see everything text messages phone calls my pictures everything. ..HELP PLEASE HELP
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.