Related
I'm currently using Nik's Codename Jellybean ROM and am getting excellent battery life for the last week or so. I have used the kernel that has come along with it.
However, yesterday when I went out - I turned on GPS (turned on for a short period and then off) for the first time since flashing the ROM and since then, the GPSLocationProvider has been providing partial wakelocks every second whenever the phone is not on airplane mode and preventing deep sleep, killing my battery in the process.
I have attached a screenshot from BetterBatteryStats.
I have looked about in the forum and the only solution from a couple of old threads seem to be rebooting the phone so that the phone can go back into deep sleep mode, which is really not the best solution is it?
If there is any solution or a compatible kernel that prevents this, I'm happy to hear from you.
It may also due to your Google location services which is active. Take the dump again with all location, GPS turned off!!
Edit: Location wake lock dump shows its active for long time. Seems like its due to location service not GPS, which you turned on only for a short duration.
Cool - that may help isolate the problem. I will toggle Maps, Location Services, GPS and see what is causing the issue.
Many thanks
Happens to me also on other ROM and device. But only if i start some app, which is using GPS, but its not enabled yet.
In case I enable GPS, than start the app, use it, close app, disable GPS, then GpsLocationProvider is not running in background.
So since the latest Google Play Services update, I have been suffering some serious battery drain issues. There are various mentions all around the internet and most point to the issue being 4.2.1, which, we aren't running.
I spent some time over the last few days trying to figure out what the issue is and have some observations. But, for some background, last few days I have been getting no more than 10 hours battery with no more than an hour or two screen time.
Google Play Services is listed as the biggest battery drainer with 49%, so I started looking into that.
First off, I noticed in battery stats that if Wifi is on, the device doesn't deep sleep, even though wifi is set to never on when sleeping, the wifi never turns off and the phone never deep sleeps.
First thing to try was turning off wifi, so, I turned off wifi, straight away, phone deep sleeps again.
Next I began messing with Google related things, first of all I "uninstall updates" on GPlayS, tested with Wifi on, great, no more battery drain, phone sleeps, BUT, phone keeps bugging me with notifications to update.
Next was to update, battery drain returns. So, disable Google Now in its own settings, battery drain remains when on Wifi, however, if I kill "Google Search" after disabling Google Now, the battery drain stops.
Various mention on the internet has attributed it to location history and location services in the "Google Settings" however I have had those disabled for a few days now and they seem not to be the issue in this case.
My conclusion so far is that the link between the latest GPlayS and Google Now is the real killer.
At present, I have Google Now disabled, and no battery drain, Wifi turns itself off as it should and the phone sleeps. This isn't a great solution since I use Google Now regularly.
I'm hoping that unless someone has come up with a realistic solution that doesn't involve disabling services, Google will release an update to fix the issue.
Currently without access to another device other than my N10, I'm unable to test whether this particular version of the issue is specific to the XZ or the GoogleNow/GPlayS versions.
My next test is to install Network Info from F-Droid and Better Battery stats, and see if I can attribute the thing preventing wifi from turning off during sleep, and hence the failure for the device to deep sleep, to a particular activity going on.
Further, I have already tested the GPlayS related services by disabling everything such as Calendar and Contact Sync, disabled all of books, movies, photo sync, disabled Google Plus, none of these had any effect on the issue, which all but rule them out of the equation.
Has anyone else got observations on this, is anyone else suffering the issue, or has anyone got a real solution?
I'm off on Holiday on Saturday and would really like to have access to Google Now back, but not have the battery drain that's going to kill my battery while roaming the streets of Rome without access to a charger.
alias_neo said:
So since the latest Google Play Services update, I have been suffering some serious battery drain issues. There are various mentions all around the internet and most point to the issue being 4.2.1, which, we aren't running.
I spent some time over the last few days trying to figure out what the issue is and have some observations. But, for some background, last few days I have been getting no more than 10 hours battery with no more than an hour or two screen time.
Google Play Services is listed as the biggest battery drainer with 49%, so I started looking into that.
First off, I noticed in battery stats that if Wifi is on, the device doesn't deep sleep, even though wifi is set to never on when sleeping, the wifi never turns off and the phone never deep sleeps.
First thing to try was turning off wifi, so, I turned off wifi, straight away, phone deep sleeps again.
Next I began messing with Google related things, first of all I "uninstall updates" on GPlayS, tested with Wifi on, great, no more battery drain, phone sleeps, BUT, phone keeps bugging me with notifications to update.
Next was to update, battery drain returns. So, disable Google Now in its own settings, battery drain remains when on Wifi, however, if I kill "Google Search" after disabling Google Now, the battery drain stops.
Various mention on the internet has attributed it to location history and location services in the "Google Settings" however I have had those disabled for a few days now and they seem not to be the issue in this case.
My conclusion so far is that the link between the latest GPlayS and Google Now is the real killer.
At present, I have Google Now disabled, and no battery drain, Wifi turns itself off as it should and the phone sleeps. This isn't a great solution since I use Google Now regularly.
I'm hoping that unless someone has come up with a realistic solution that doesn't involve disabling services, Google will release an update to fix the issue.
Currently without access to another device other than my N10, I'm unable to test whether this particular version of the issue is specific to the XZ or the GoogleNow/GPlayS versions.
My next test is to install Network Info from F-Droid and Better Battery stats, and see if I can attribute the thing preventing wifi from turning off during sleep, and hence the failure for the device to deep sleep, to a particular activity going on.
Further, I have already tested the GPlayS related services by disabling everything such as Calendar and Contact Sync, disabled all of books, movies, photo sync, disabled Google Plus, none of these had any effect on the issue, which all but rule them out of the equation.
Has anyone else got observations on this, is anyone else suffering the issue, or has anyone got a real solution?
I'm off on Holiday on Saturday and would really like to have access to Google Now back, but not have the battery drain that's going to kill my battery while roaming the streets of Rome without access to a charger.
Click to expand...
Click to collapse
I shut it off it was draining my battery!
I had the same problem.
And here's a solution for you: Factory data reset
After that there will be no problems with battery drain.
NXT3 said:
I had the same problem.
And here's a solution for you: Factory data reset
After that there will be no problems with battery drain.
Click to expand...
Click to collapse
I did a factory reset and have the problem.
So the amount of battery drain has lowered significantly, but it is still there. I attached a screenshot from before the change and a screenshot from after.
use link 2 sd ( root required ) search at playstore
open it and seacrh google play service
option and sleep it..and u done
echopark15 said:
use link 2 sd ( root required ) search at playstore
open it and seacrh google play service
option and sleep it..and u done
Click to expand...
Click to collapse
it must be a way without root
Update Google play Service to version 5.x
Firstly, this is not another thread to complain about your horrible battery life due to Google Play Services. I'm tired of those (mostly on Reddit, but some here too. Either way, none of that here ). This is instead to try and find a root cause for it. "It's Google's fault" is not good enough for me, and if you truly care about your battery life it shouldn't be for you either. If all you're after is an easy way out to get your battery life back, then this thread is not for you. We're here to reach a solution where you can get location services and good battery life. I've done if before, on my Galaxy Nexus on 4.3, but it seems that something is wrong in KitKat. Let this be a place where we all dig deeper into this issue, perform tests, gather results, and then share and discuss them. Here's what I've got so far:
The wakelocks that cause this battery drain are NlpWakeLock and NlpCollectorWakeLock. Nlp stands for network location provider. As you may know, Android provides developers with two ways of gathering location information. One is through the GPS_PROVIDER, which uses the GPS, and the other is through NETWORK_PROVIDER, which uses cell towers and WiFi APs to get your position. According to their developer website[1] , NETWORK_PROVIDER uses less battery, is faster, but is less accurate. GPS uses more battery, takes longer, but is good if you want an accurate location. I'm assuming this particular wakelock uses NETWORK_PROVIDER.
I also did some digging using ROM Toolbox Pro's autostart manager. My guess was that Google Play Services must be triggered every time a certain intent is broadcasted, since nothing obvious is telling it to run. Turns out there are quite a few. 30, to be exact. However, many of them have to do with GCM and we don't really care about those. One of particular interest is one called com.google.android.location.internal.NlpNetworkProviderSettingsUpdateReceiver. It listens for the intent android.location.PROVIDERS_CHANGED. The LocationManager API's documentation[2] tells us this:
Broadcast intent action when the configured location providers change. For use with isProviderEnabled(String). If you're interacting with the LOCATION_MODE API, use MODE_CHANGED_ACTION instead.
Click to expand...
Click to collapse
I'd assume that this means when you change your location providers, such as enabling/disabling data, WiFi, GPS, etc.
However, location reporting only seems to use network location. If you're on KitKat, go to the location settings and choose device only. Then choose battery saving. It asks you to accept location reporting. Same thing when you choose high accuracy. What do both of those have in common? Network location. You can switch between those two as much as you want and it won't ask you to accept again. However, once you switch to device only and back it will ask you. This shows that it only uses network location.
I find that Google (Play) Services has 5% (+/- 1%) keep awake. Tested on both Nexus 5 running KRT16M and Galaxy Nexus running JWR66V. Both use a certain time of GPS, although that number is never increasing. I assume this is some sort of initial one-time lock. It can be disregarded.
One more thing I noticed is that this Google Play Services issue is much more prominent on KitKat. While they have happened before, often times a simple Play Store update would fix it. This time it seems to be location based. Guess what changed in KitKat? The way you deal with location settings. It may be that the way location settings are grouped in KitKat cause that intent to keep firing, and that in turn triggers something that eventually ends up being what you see as NlpWakeLock.
What I'm going to try next is disabling that intent receiver and then monitor that wakelock as well as if location reporting still works. Feel free to play around, and be sure to share your results.
To those who are suffering from these wakelocks, could you please share your settings? Such as what type of location mode you have (high accuracy, battery saving, device only), WiFi on or off, data on or off, signal strength, WiFi always scanning, Play Store and Play Services version, what device you have, Android build number, and what ROM/kernel you're using if you are using one? Any other info such as screenshots of battery screen, betterbatterystats, wakelock detectors, etc. will all be welcomed.
Here is the Reddit thread I created discussing the same issue: http://www.reddit.com/r/Android/comments/1rvmlr/nlpwakelock_and_nlpcollectorwakelock_discussion/
I don't have this device, nor do I know if I'll be getting it, but I must say that I applaud your method.
Bravo!
I just turn location reporting off then select 'battery saving' setting & accept the request for reporting when it pops up. This allows you to use network location without logging. Google now & maps work fine although not quite as accurate. I just turn on gps if i need navigation. Never get more than 2% usage from play services & it's giving me a total kept awake time of about 28mins out of 12hrs of use with 3hrs screen on time.
Sent from my Nexus 5 using Tapatalk
If I disable the wifi and 3g, leave my phone on battery saving location, google location set to on, it is using wifi always scanning only and it didnt consume 1% battery in a whole night
stumpy352 said:
I just turn location reporting off then select 'battery saving' setting & accept the request for reporting when it pops up. This allows you to use network location without logging. Google now & maps work fine although not quite as accurate. I just turn on gps if i need navigation. Never get more than 2% usage from play services & it's giving me a total kept awake time of about 28mins out of 12hrs of use with 3hrs screen on time.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
That is working for me right now.
Sent from my Nexus 5 using Tapatalk 2
ickboblikescheese said:
To those who are suffering from these wakelocks, could you please share your settings? Such as what type of location mode you have (high accuracy, battery saving, device only), WiFi on or off, data on or off, signal strength, WiFi always scanning, Play Store and Play Services version, what device you have, Android build number, and what ROM/kernel you're using if you are using one? Any other info such as screenshots of battery screen, betterbatterystats, wakelock detectors, etc. will all be welcomed.
Click to expand...
Click to collapse
I am experiencing this issue on my Nexus 5, as confirmed by betterbatterystats (NlpCollectorWakelock 5.5% awake time)
ROM: CyanogenMod 11 alpha
Build Number: KRT16S
Location Mode: High accuracy
Location Reporting: Off
WiFi On: Sometimes
Play Store Version: 4.4.22
Play Services Version: 4.0.34
This issue first appeared for me the other day. I noticed that my device was not appearing in the online Android Device Manager, nor the desktop version of the Play Store. To fix the ADM issue, I disabled remote wipe, cleared data for Play Services, reenabled remote wipe, and rebooted. To fix my device not appearing in the Play Store, I cleared data for the Play Store app. Both issues were thereafter resolved, but now I am experiencing the Network Location battery drain.
Is it possible the problem is related to requests from Android Device Manager? I was under the impression that location for that purpose was 'on demand' instead of logged, but what do I know.
Thanks for doing this! Others, please feel free to use my comment as a template, and post your own data.
So I was playing around with autostart, and I accidentally caused a bunch of FCs for Play Services. Ended up freezing/defrosting and then uninstalling updates then let it update itself, and I noticed this (may or may not have anything to do with what I did): Even though it wakelocks, it barely uses up any batter. I was in an area of 2-3 bar HSPA+, with sync on, location reporting on at high accuracy, etc. and it drained 1% per hour. Still kept phone awake ~5% of the time, but battery usage was significantly better over what I recorded to be 4.8%/hour from last Friday.
EDIT: The only other change I can think of making is temporarily freezing Cerberus. I'll have to look more into that. However, check which apps are requesting your location. The new location settings in KitKat make this simple enough. For me it's only Google Now and Google Play Services, and whatever app that happens to require GPS such as camera (geotagging) and maps.
ickboblikescheese said:
So I was playing around with autostart, and I accidentally caused a bunch of FCs for Play Services. Ended up freezing/defrosting and then uninstalling updates then let it update itself, and I noticed this (may or may not have anything to do with what I did): Even though it wakelocks, it barely uses up any batter. I was in an area of 2-3 bar HSPA+, with sync on, location reporting on at high accuracy, etc. and it drained 1% per hour. Still kept phone awake ~5% of the time, but battery usage was significantly better over what I recorded to be 4.8%/hour from last Friday.
Click to expand...
Click to collapse
So, how should I replicate this? I'm using the Xposed Module that dev posted in your Reddit post.
stumpy352 said:
I just turn location reporting off then select 'battery saving' setting & accept the request for reporting when it pops up. This allows you to use network location without logging. Google now & maps work fine although not quite as accurate. I just turn on gps if i need navigation. Never get more than 2% usage from play services & it's giving me a total kept awake time of about 28mins out of 12hrs of use with 3hrs screen on time.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
How do you do this exactly? If I turn location reporting off, then I can't select the battery saving method because it's greyed out. This also causes location based cards to stop working on Google Now and Maps can't locate me either.
---------- Post added at 11:24 PM ---------- Previous post was at 11:19 PM ----------
natezire71 said:
So, how should I replicate this? I'm using the Xposed Module that dev posted in your Reddit post.
Click to expand...
Click to collapse
Use Titanium Backup to FIRST backup Google Play Services. Then use it to uninstall GooglePlay Services. Then open Google Now or Maps, they will ask you install Google Play Services and take you to the app store.
If anything goes wrong, use Titanium to restore.
You need location toggled on. Go down to location services & click on Google Location Reporting. Select off for both settings. Then go back out & select battery saving mode & accept the terms.
Sent from my Nexus 5 using Tapatalk
stumpy352 said:
You need location toggled on. Go down to location services & click on Google Location Reporting. Select off for both settings. Then go back out & select battery saving mode & accept the terms.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Turns out that's exactly how I had set up after all, doh! Thank you.
I have actually been getting really decent battery life, noticeably better than my HTC One, with exactly similar usage patterns and same apps installed etc.
Also, Play Services is not the only app that uses this NlpWakeLock. Facebook also uses it & in my case has the highest time kept awake. I turned off location in chat & noticed that it is much better.
Sent from my Nexus 5 using Tapatalk
That's what I thought too. That could explain why some people have this issue more than others.
Sent from my Nexus 5
ickboblikescheese said:
That's what I thought too. That could explain why some people have this issue more than others.
Sent from my Nexus 5
Click to expand...
Click to collapse
Have you tried the Xposed module that filters wake locks? I've been using it and the NLP counts have drastically dropped
No, not using xposed. I understand that wake locks must occur for accurate location services (otherwise what is doing the reporting). What shouldn't be there is the incredible battery drain. Wake locks don't necessarily mean battery drain. You could have a 1h wake lock and drain 1% battery, or a 5 min wake lock that keeps CPU on high frequency causing a 10% battery drain. I don't mind wake locks as long as battery isn't affected too much.
Sent from my Nexus 5
ickboblikescheese said:
No, not using xposed. I understand that wake locks must occur for accurate location services (otherwise what is doing the reporting). What shouldn't be there is the incredible battery drain. Wake locks don't necessarily mean battery drain. You could have a 1h wake lock and drain 1% battery, or a 5 min wake lock that keeps CPU on high frequency causing a 10% battery drain. I don't mind wake locks as long as battery isn't affected too much.
Sent from my Nexus 5
Click to expand...
Click to collapse
That was the point of this module. https://play.google.com/store/apps/details?id=in.andro.wlt. Take a look and read the description. From my understanding, the location stuff still works--which for me has been the case. However, it stops the unnecessary wakelocks. I would like to believe my battery has improved.
Nice thread!!
I've changed my location settings and I'll report if it works!!!
Thanks!!!
natezire71 said:
That was the point of this module. https://play.google.com/store/apps/details?id=in.andro.wlt. Take a look and read the description. From my understanding, the location stuff still works--which for me has been the case. However, it stops the unnecessary wakelocks. I would like to believe my battery has improved.
Click to expand...
Click to collapse
Please keep us posted on this works out for you, it looks really promising!
the7thson said:
Please keep us posted on this works out for you, it looks really promising!
Click to expand...
Click to collapse
I think it's working.
natezire71 said:
I think it's working.
Click to expand...
Click to collapse
Can you tell us which apps you disabled wake locks for?
Sent from my Nexus 7 using Tapatalk 4
I'm opening this thread to clean up the Dev thread, since the most probable cause of battery drains are software/configuration related.
Here's my own experience with this matter.
Most of the drains I've seen are related to Location settings and Google Now. It seems Google's Location Reporting and Location History keep pinging WiFi for the location at a fairly high rate, so keeping the phone Awake and/or the WiFi running all the time. An usual indication of this is that in BetterBatteryStats you get:
1) Screen On % very low
2) WiFi On 100% of the time
3) WiFi Running 100% of the time.
4) Awake with moderate-to-high %.
To test it, here's what should be done:
1) Get BetterBatteryStats (BBS), enable Root, install it as system app (in advanced settings). Reboot.
2) Disable WiFi and GPS completely, preferably leaving Data Network also off. You may go all the way and just turn on airplane mode.
3) Leave the phone idle for at least 1h and check that there is no battery drain.
If you get any considerable drain (more than 5%/h), check Kernel Wakelocks and Partial wakelocks, or try again with 2G networks only. You may have a baseband problem. Consider this step as your "control group" as it ensures nothing in the hardware or in the ROM is wrong.
If there is no drain, enable WiFi and GPS again, but make sure all this settings are UNCHECKED:
1) Settings->WiFi-> Advanced: "Network notification", "Keep wifi on during sleep" set to "Never", "Scanning always available".
2) Settings->Location->Google Location Reporting: "Location Reporting" set to off and "Location History" set to off. Or just disable Location completely.
3) Check Settings->Security -> Device Administrators -> Disable at least Android Device Manager. If you can, disable everything else in this screen, such as Airdroid, Cerberus, etc
4) App drawer -> Google Settings -> Search -> Set Google Now to Off. You can also configure Android Device Manager here.
Leave the phone idle again for 1h and check BBS. In theory you shouldn't need to recharge completely, just enable the watchdog in BBS. Always check the wakelocks too.
You should get this on BBS:
1) Screen On % very low
2) WiFi On 100% of the time
3) WiFi Running with low % (anything less than 50% is ok, depending on Sync settings and background apps)
4) Awake with low %.
5) Deep Sleep with almost 100%
Go back enabling stuff as needed, one by one, leave the phone idle and check BBS. Rinse and repeat until you find the culprit.
One thing, make sure you do this after letting the phone sync some of the stuff. Don't do this immediately after a setting up a Google account.
Some people also reported that doing a factory reset solves the drains. It's always recommended anyway.
Any other hints are also appreciated.
For people with trouble making BBS work, Try getting the latest version, enable Root in Settings->Advanced and them System App, also in Settings-> Advanced.
Also:
1) When the phone is charging it WILL BE AWAKE WITH BOTH CORES, ALL THE TIME. Depending on the governor used, both cores may even stay at full speed (aka 1GHz). This is BY DESIGN and stock ROMs does that too. So any measurement while the phone is charging is useless.
2) Most "calibration" procedures are myths and don't have any effect. Erasing batterystats.bin also does nothing to increse battery life or remove drains (but may solve some charging issues, still unclear).
Very interesting.. Good thread and good options to test our battery drain ! thanks for the post.
I'll try this when I get home from school, thanks.
Weird thing happened last night, I thought the battery drain was gone when I recalibrated, but my phone discharged over night, weird thing is my settings show the phone didn't go to sleep once during the entire night, even though it was on airplane mode and I had already used it for like 3 or 4 hours with no apparent brain
There is a lot of battery drain only when WiFi in on. Even if the phone is idle.
I'm on:
Maclaw CM 11.0 [20131210]
I8190XXAMJ2
I'll do the exact tests and post my results.
Do you get notifications with wifi set to never during sleep?
RodHQ said:
I'll try this when I get home from school, thanks.
Weird thing happened last night, I thought the battery drain was gone when I recalibrated, but my phone discharged over night, weird thing is my settings show the phone didn't go to sleep once during the entire night, even though it was on airplane mode and I had already used it for like 3 or 4 hours with no apparent brain
Click to expand...
Click to collapse
Use the 1st step I wrote above with BBS. Check Kernel Wakelocks and Partial Wakelocks. You will be able to pinpoint exaclty what is keeping your phone awake.
I was about to start a thread on the same topic but my problem is with Carbon Rom 4.4.2 . The phone never goes into deep sleep and is awake 100% of the time. I'm attaching what I see as the culprit in B.B.S. I already disabled sync and yet the wakeclocks are sync related I hope anyone can help me with this.
i just changed to peagusq everything is fine
BBS How-to
ArtCar said:
I was about to start a thread on the same topic but my problem is with Carbon Rom 4.4.2 . The phone never goes into deep sleep and is awake 100% of the time. I'm attaching what I see as the culprit in B.B.S. I already disabled sync and yet the wakeclocks are sync related I hope anyone can help me with this.
Click to expand...
Click to collapse
Maybe BBS How-to will help you
http://forum.xda-developers.com/showpost.php?p=15869904&postcount=3
If not than post screens and collected dumps on BBS thread
gimme link to maclaw 4.4.2 for s advance
Sent from my GT-I9070 using xda app-developers app
Link
Here you are
http://maclaw.pl/downloads/
same here
eswarvf said:
i just changed to peagusq everything is fine
Click to expand...
Click to collapse
+1
ArtCar said:
I was about to start a thread on the same topic but my problem is with Carbon Rom 4.4.2 . The phone never goes into deep sleep and is awake 100% of the time. I'm attaching what I see as the culprit in B.B.S. I already disabled sync and yet the wakeclocks are sync related I hope anyone can help me with this.
Click to expand...
Click to collapse
Notice that the Count is 0 on both GoogleServices related wakelocks. To me this seems that Chrome and something else (maybe G+?) are trying to sync (perhaps the first one?) but are not getting enough network time/bandwidth to do so. I suggest you connect to an wifi, turn on the sync, and leave the phone awake for a while (try not to use the network very much). See if that solves. If not, backup and factory reset are your friends.
rcoacci said:
Notice that the Count is 0 on both GoogleServices related wakelocks. To me this seems that Chrome and something else (maybe G+?) are trying to sync (perhaps the first one?) but are not getting enough network time/bandwidth to do so. I suggest you connect to an wifi, turn on the sync, and leave the phone awake for a while (try not to use the network very much). See if that solves. If not, backup and factory reset are your friends.
Click to expand...
Click to collapse
I fixed my problem by switching back to dalvik and now my phone only looses about 5% battery overnight.
I've noticed that the battery life got worse with the latest 23.5.A.1.191 update. With previous version I could leave the phone on desk overnight and the battery did not drop at all (flat line in the battery usage graph). Now with the Stamina comeback I can see a 10 to 15% drop overnight. Can you please share your ideas what settings I should look into to fix it? Thanks
Have u check your wakelock? Play services often do this idiot bug.
Yes, Play services was the app draining the battery, but I remembered that I installed Google Fit in the meantime. Additionally something got messed up with the location after the last update, so I did not see a detailed route but just a large circle on the map in Fit (maybe permissions for gps location?).
However uninstalling Google Fit fixed it. I woke up today and saw a flat line in the battery usage.
I leave data usage over night and , since I have this phone, my battery draining from Google Play services is abnormal. I only synd gmail, no other service, no other permission. I've used Gservicefix without any result. Does anybody know why?
SoulFury said:
I leave data usage over night and , since I have this phone, my battery draining from Google Play services is abnormal. I only synd gmail, no other service, no other permission. I've used Gservicefix without any result. Does anybody know why?
Click to expand...
Click to collapse
There are lots of reasons why Google Play Services are eating your battery, try a few fixes yourself, check which version of Play Services you have installed , anything older than 9.4.52 needs replacing.
Remove your google account, wipe data for Play Services and Download manager, restart to recovery, wipe cache/dalvik. Restart phone, add account again.
There seems to be issues with fitness trackers and bluetooth, if you have bluetooth on all the time, see what happens if you turn it off?
I can recomend Greenify app that can make a difference in putting apps to sleep, it also helps you see which apps are awake and on.
Check in settings/developer options/running services to see what's on and using most memory, you might be surprised at what you find. To enable developer options go to settings/about phone - press on build 8 times, then you get a message that develper options are availabe in the settings menu.
SoulFury said:
I leave data usage over night and , since I have this phone, my battery draining from Google Play services is abnormal. I only synd gmail, no other service, no other permission. I've used Gservicefix without any result. Does anybody know why?
Click to expand...
Click to collapse
the first couple of days after an update or a factory reset, google play services collects a lot of information. It should go back to normal after some days. Anyway, I can give you some suggestion to limit the battery drain:
- new Stamina is a rebrand of the normal battery saver. Don't keep it always on.
- if you want something reminding the old stamina, download Greenify, follow instruction for adb command to enable Aggressive Doze and enable Doze on the go. Take away optimization from battery advanced setting for apps you need push notification from (e.g. whatsapp)
- disable wifi scanning when wifi is off (search in settings wifi scanning, though the search button. If your language is different from English (US) and you don't find the setting, switch to English (US) to find it)
- restrict google play services background data when not in wifi
- in account/google disable the sync for whatever you don't strictly need (play newstands, g+, ...)
With this settings, I can get 5 hours sot in a couple of day of usage, and almost no battery drain over night.
Well, my daily use consist on:
- Traffic data always on
- watch clock when needed
- +-45min WhatsApp
- Some random search.
- Some rare use of torch
- Sync with Gmail(ONLY Gmail)
I only use wifi for updates and don't have any gps or bluetooth use...Battery last above 48h this way and google services hast half of time with radio antena on.