Related
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 have been reading the many battery threads where people are posting screenshots and either complaining or raving about their particular Nexus 5’s battery performance. I am shocked that some people are turning off their Wifi, Mobile Data, GPS, Google Now, Sync, and every other feature that makes these phones so useful and still suffering with poor battery performance.
In this thread, instead of complaining or bragging about your battery performance, I thought that this could be used as a place where you all can post how you use your device and what you are doing to save juice and how it works. I’ll go first.
I have had 3 different Nexus 5’s. The first had the speaker/microphone problem and was RMAed. The second was doing great until it overheated and the LEDs at the bottom of the screen exploded. It was RMAed. My current one seems to have a weaker vibrator motor, but I’m going to live with it.
I use my phone instead of my laptop. It seems the only time I use my laptop these days it to flash my phone. I browse the web (Chrome), watch YouTube (YouTube App), read my email (Gmail), shop Amazon (Amazon App), manage my schedule (Calendar App, Pure Calendar Widget), get my news (Flipboard), participate in groups (Google Plus), Chromecast (Netflix, YouTube), participate in these forums (XDA Premium App), and various others. I don’t really play games and don’t tax the CPU to hard.
To save juice, I…
use LUX to manage my screen brightness and usually can function with the screen below 0% unless I’m outside.
use Tasker to turn on/off my wifi, data, gps, sync, and perform a few other tasks, kind-of-like juice defender, but a lot more reliable.
use Better Battery Stats to keep an eye on my apps and de-install apps with bad behavior. I plan on installing Greenify, but have not gotten around to it.
I usually get 12 to 14 hours with 3-4 hours screen time before I plug my phone in at night and have 25%-50% battery left. And, I don't feel I'm depriving myself of any performance.
Some things I have read…
With these new batteries, you never want to let them fully discharge. In fact, keeping them charged is very important, so having a charger at work, or in your car is a good practice.
When your phone gets hot, give it a rest. A hot phone is not working efficiently, and you can damage the battery permanently if it overheats.
It takes a few days for your phone to reach its best performance. When you first get it, it is working in the background to index files and such, which is keeping the phone from reaching deep sleep and is using juice.
After an update, if your phone just doesn’t seem right, it might not be. Do a factory reset and try again. If something didn’t update correctly, there is no telling what could be affected…even your battery performance.
If you have ideas on how to increase battery performance, or discovered apps or settings that drain your battery, please post them here.
Added From Comments Below...
Make sure your apps are configured properly. For example, make sure apps such as Google + are configured to only backup while charging.
In Settings / Locations, set mode to 'Battery Saving' . It passively detects your location which uses no battery. It has been reported that turning off 'location reporting' has no negative effect on Now and Maps. This is a big juice saver.
Kill apps when done using them. Some apps, if left open, will continue draining your juice.
Turn off 'Scanning Always Available' in Wifi /Advanced Settings.
Things I Have Been Experimenting With...
Greenify is a great app for battery optimization. I have apps on my phone that I don't use often, but seem to keep the phone awake. Greenify them and put the app to bed until you need it.
I've been experimenting with Kernels. After much experimentation, I used Franco Kernel on my GN, so I tried his out and have noticed a battery savings on my screen off time. This is a recommendation for rooted phones because the Franco Updater app on the Play Store does all the heavy lifting.
If you find this information helpful, please hit the 'thanks' button.
.
My battery life has been fantastic ever since I disabled Google+. It was constantly running in the background all the damn time and just destroying my battery when I wasn't even using it. Ever since I disabled it, I can easily pull down 4-5 hours of screen on time.
That being said, I'm definitely an opportunistic charger. I work from home so it's easy to keep my phone juiced up when I'm not using it. I rarely go below 50%.
Wow. On stock I easily get 5 hours screen on time with everything on, but only 14ish hours total. With light usage (2 1/2 hrs) close to 27 hours. However I've seen guys posting over 3 days so now I'm playing around with kernels (Franco at the moment) and multirom. I'm using ART but not sure how much difference honestly.
Sent from my Nexus 5 using Tapatalk
maxpower7 said:
My battery life has been fantastic ever since I disabled Google+. It was constantly running in the background all the damn time and just destroying my battery when I wasn't even using it. Ever since I disabled it, I can easily pull down 4-5 hours of screen on time.
That being said, I'm definitely an opportunistic charger. I work from home so it's easy to keep my phone juiced up when I'm not using it. I rarely go below 50%.
Click to expand...
Click to collapse
You can also just greenify Google+ and also check if you have the photo backup with it turned to on. I found my app running for half an hour while phone was off and it was due to the backing up of the photos.
Instead of opening "yet another thread", this could've been posted here, here, here, here, here and probably in many others..
I use Google+ every day all day. The impact it has on battery life is zero. Of course that's my experience. If it's murdering your battery them you don't have something set up properly or as they say "you're doing it wrong"
Sent from my Nexus 7 using XDA Premium 4 mobile app
rayiskon said:
Instead of opening "yet another thread", this could've been posted here, here, here, here, here and probably in many others..
Click to expand...
Click to collapse
Yea. But mostly you will read people bragging or complaining. There is a lot of good information in those threads, but to find it, you will have to dig. My intention is that this thread will be a place to find, test, and compile solutions for those suffering with poor performance.
Sent from my Nexus 7 using XDA Premium 4 mobile app
jbdan said:
I use Google+ every day all day. The impact it has on battery life is zero. Of course that's my experience. If it's murdering your battery them you don't have something set up properly or as they say "you're doing it wrong"
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I also use Google + every day with little impact. I checked my settings and I have it set to only back up while on WiFi and only while charging.
I also use Tasked to turn off sync when the screen is off keeping the phone in deep sleep.
Sent from my Nexus 7 using XDA Premium 4 mobile app
I greenify most apps, keep screen brightness down, GPS Bluetooth always off, data only on when screen on, etc. I got 1 day 15 hours with over 6 hours screen time with my usage. I mostly use my phone for xda, 9gag, some chrome browsing, and a couple other things.
prshosting.org
JamieFL said:
I also use Google + every day with little impact. I checked my settings and I have it set to only back up while on WiFi and only while charging.
I also use Tasked to turn off sync when the screen is off keeping the phone in deep sleep.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yup I use that same setting thanks for pointing that out :good:
Nexus5
IMO, I shouldn't have to do any of this to "save" battery life. It is what it is.
jbdan said:
I use Google+ every day all day. The impact it has on battery life is zero. Of course that's my experience. If it's murdering your battery them you don't have something set up properly or as they say "you're doing it wrong"
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Google+ kills my battery regardless of what my settings are. I literally only used it as an offline photo gallery - there was no syncing being done at all, no auto-awesome, no photo backups or any of that. I don't know how there could possibly be any user error in my setup.
I think literally the only thing that should be done to save battery life is to disable location reporting and to possibly disable autobrightness when indoors. Other than that, nothing needs to be done to get spectacular battery life. All I have is a tasker profile to disable autobrightness when connected to my wifi network and re-enable it when I am not connected, and then location reporting turned off. I get 6 hours screen on time daily.
muyoso said:
I think literally the only thing that should be done to save battery life is to disable location reporting and to possibly disable autobrightness when indoors. Other than that, nothing needs to be done to get spectacular battery life. All I have is a tasker profile to disable autobrightness when connected to my wifi network and re-enable it when I am not connected, and then location reporting turned off. I get 6 hours screen on time daily.
Click to expand...
Click to collapse
Location reporting is such a huge battery drain and it doesn't seem to have any real benefits. Google Now works fine without it.
maxpower7 said:
Location reporting is such a huge battery drain and it doesn't seem to have any real benefits. Google Now works fine without it.
Click to expand...
Click to collapse
Yea. I was very surprised that it had absolutely zero impact to turn it off for me. Google Now works perfectly fine. Maps works. Everything works. I guess the only negative is that you are not contributing information into the Google hivemind to help out others with traffic information and crap like that. . . . Otherwise there are no negative effects to turning it off, and doing so squashes the nlp wakelock bug completely.
For me at least, I went from about half a day on full battery to almost a day and a half by turning off LTE and Wi-Fi scanning with constant usage. I was conflicted a bit for choosing either LTE or battery life but I'm happier with choosing battery life.
Sent from my Nexus 5 using xda app-developers app
I added the suggestion about setting location reporting off. Thanks.
I've heard that if your area has poor LTE signal, that can cause a big battery drain. Can anyone confirm that? If this is true, this could be a big contributor to unexplained battery drain.
muyoso said:
Yea. I was very surprised that it had absolutely zero impact to turn it off for me. Google Now works perfectly fine. Maps works. Everything works. I guess the only negative is that you are not contributing information into the Google hivemind to help out others with traffic information and crap like that. . . . Otherwise there are no negative effects to turning it off, and doing so squashes the nlp wakelock bug completely.
Click to expand...
Click to collapse
Were you still able to get traffic notifications? It's weird that it doesn't seem to affect weather updates as well.
PsychDrummer said:
Were you still able to get traffic notifications? It's weird that it doesn't seem to affect weather updates as well.
Click to expand...
Click to collapse
Not sure about traffic notifications as I work from home and Google cannot comprehend that and thinks I work at the grocery store, but weather notifications work perfectly. Just traveled for Christmas and it was tracking me perfectly from city to city.
muyoso said:
Not sure about traffic notifications as I work from home and Google cannot comprehend that and thinks I work at the grocery store, but weather notifications work perfectly. Just traveled for Christmas and it was tracking me perfectly from city to city.
Click to expand...
Click to collapse
Gotcha. I mean it's not a huge deal. Google often thinks I'm driving to work/class when I'm not actually doing so and it's more useful to check traffic within the Maps app anyway. I'll try the reporting off for a few days though and see how much of a difference it makes.
This might seem like a question but its not.
Personally what is your opinion on the snapdragon battery guru? Like does it help you out at all?
Any comments on it? I Tried it on my HTC before i broke it (had it for 2 months lmfao) and it was in learning mode and started doing crazy stuff to my phone like turning things on and off and it got annoying but im thinking of using it now since my htc got like 16 hours of battery and i only get about half of that now even after tweaking everything.
Im currently not using it but yes it does help a bit
In my experience it wakelocked my device quite a lot, especially if you move around too much (work, travel). It's whole operation is based on user location, so it has to wake your phone to fetch location and do whatever it needs to do. In the it was a ****ton of wakelocks.
Your experience may vary, try it out yourself and monitor it with wakelock detector.
jaweinre said:
In my experience it wakelocked my device quite a lot, especially if you move around too much (work, travel). It's whole operation is based on user location, so it has to wake your phone to fetch location and do whatever it needs to do. In the it was a ****ton of wakelocks.
Your experience may vary, try it out yourself and monitor it with wakelock detector.
Click to expand...
Click to collapse
thanks to the wifi problem that comes with kitkat i have to keep my location on "device only" and the app keeps asking for 'location services required'
It Helps
I have been using it for months now. It does help with battery life. I like how it automatically refreshes apps based on usage. I have tons of apps but very few i want to refresh automatically. The low power mode is nice to get the most out of my remaining battery without me having to turn off everything and dim the screen manually.
I'm not sure what's considered high android system but mine is at 29% and looks like it's taking a toll on my battery. When I check the battery usage it's the highest thing listed. How can I lower this or fix this? Any help is greatly appreciated! I love this phone!
same problem here ... android system is at 24% with 59 minutes of CPU usage while screen was about 20% with more than 2 hours of screen on time !?! Why system is killing the cpu so much ? ... TouchWiz !!! *SMH*
Give it a week or so to even out.
This could be any app that is pulling your location. Most pull through your location through google play services, part of the android system. Not defending touchwiz usage but most likely the fault lies elsewhere.
xxsxx said:
This could be any app that is pulling your location. Most pull through your location through google play services, part of the android system. Not defending touchwiz usage but most likely the fault lies elsewhere.
Click to expand...
Click to collapse
I dont think so my location its off and still takes 29%, maybe a kernel issue. I heard they did the update we just got cause battery draining issues. maybe not fixed 100%
I get the same thing and I made sure to turn off notifications and apps that "push" and set em all to manual. I use the same apps and settings on my S5, and LG G3 and would be able to get around 6 hour screen time and total of 17-20 hours per charge. AND on those devices, the screen is usually the highest % and the android system is not even near that %
Right now I'm getting almost about the same as my S5 battery life, maybe a bit shorter...
Same problem here, about 42% on a normal usage. I did not have this problem before, on stock Rom but since I switched to cynanogenmod, my phone can't make it through the day.
What's more, I'd like to know if any of you know an xposed module or an app which can automatically turn switches on/off when starting/closing an app. Like turning GPS on when starting Google Maps and turning it back off when closing the app, for instance.
Sent from my Xperia Z1 Compact using XDA Free mobile app
Good queetion, I'd be interested in that as well
Sent from my SAMSUNG-SM-N910A using XDA Free mobile app
mines also like this
I found this was related to location services and / or google now.
I found these worked for me:
1. Turning GPS location to GPS only (i.e. not using wifi). I believe this stops passive location tracking, which in turns stops the other services always running
2. Turning off location tracking / history. As above, no detailed location, no other fancy things running all the time.
3. Turning off Google Now.
I listed the above in the order I would do it. Using just item one, you still get most of Google Now's functionality.
End of the day, what I found was there was a lot of "smart" stuff going on in the background around your location, and this is what caused most of the CPU time. If you look at your wake locks, you will see it drop off dramatically once you do the above steps.
Some people have reported turning location services back on after a while didn't result in a spike in CPU time.
This isn't a Note 4 thing, more a Android / Google Now thing in my opinion,.
Hope it helps.
mrja22 said:
I found this was related to location services and / or google now.
I found these worked for me:
1. Turning GPS location to GPS only (i.e. not using wifi). I believe this stops passive location tracking, which in turns stops the other services always running
2. Turning off location tracking / history. As above, no detailed location, no other fancy things running all the time.
3. Turning off Google Now.
I listed the above in the order I would do it. Using just item one, you still get most of Google Now's functionality.
End of the day, what I found was there was a lot of "smart" stuff going on in the background around your location, and this is what caused most of the CPU time. If you look at your wake locks, you will see it drop off dramatically once you do the above steps.
Some people have reported turning location services back on after a while didn't result in a spike in CPU time.
This isn't a Note 4 thing, more a Android / Google Now thing in my opinion,.
Hope it helps.
Click to expand...
Click to collapse
thanks for the advice and suggestions, but my s4 and s5 did not have the "android system" so high in usage. i've tried the turning off gps, then back on, and then restart phone thingy, but same results. i just hope sammy would address this issue as it seem pretty widespread.
MMakoto said:
thanks for the advice and suggestions, but my s4 and s5 did not have the "android system" so high in usage. i've tried the turning off gps, then back on, and then restart phone thingy, but same results. i just hope sammy would address this issue as it seem pretty widespread.
Click to expand...
Click to collapse
Just to clarify,Ii suggest turning location to GPS only. And leaving it off.
Turn off location reporting and history also. Then see what results you get and go from there
I'm having the same thing ...
I just received a update that is supposed to fix the battery drain issue. We shall see if it works.
railslave said:
I just received a update that is supposed to fix the battery drain issue. We shall see if it works.
Click to expand...
Click to collapse
The update that came out this week or a different one.
mrja22 said:
I found this was related to location services and / or google now.
I found these worked for me:
1. Turning GPS location to GPS only (i.e. not using wifi). I believe this stops passive location tracking, which in turns stops the other services always running
2. Turning off location tracking / history. As above, no detailed location, no other fancy things running all the time.
3. Turning off Google Now.
I listed the above in the order I would do it. Using just item one, you still get most of Google Now's functionality.
End of the day, what I found was there was a lot of "smart" stuff going on in the background around your location, and this is what caused most of the CPU time. If you look at your wake locks, you will see it drop off dramatically once you do the above steps.
Some people have reported turning location services back on after a while didn't result in a spike in CPU time.
This isn't a Note 4 thing, more a Android / Google Now thing in my opinion,.
Hope it helps.
Click to expand...
Click to collapse
Thanks a lot ...
Location tracking off made a big difference ... Things are already looking good. I will only turn on the GPS when need be.
Mr.37 said:
Thanks a lot ...
Location tracking off made a big difference ... Things are already looking good. I will only turn on the GPS when need be.
Click to expand...
Click to collapse
Good to hear.
I found I can have GPS on without any issues, as long as either Google Now or location tracking was off.
Any more info ?
I am having the same issue in tandem with weak battery signal. Do I wait for Lollipop or do I just sell my N4 and get an S6?
Hey All,
Been a fan of this phone for a while. I am currently on a BB Q10 (which I like a lot), and I just feel like going back to Android. I love the fact that this phone comes stock with AOSP, but I will definitely root and optimize. I have owned Motorola, Samsung, and HTC. I love the quality that Motorola provides, and I really like this phone. I feel as though it is optimized for AOSP. I was leaning towards the HTC One M9, but the whole S-Off issue is pushing me away.
The only thing I am worried about is battery life. People who own this phone, could you comment on your experience with performance and battery life? What would you like changed about this phone?
Thanks in advance!
996
I personally have no issues with battery. I run rooted CM 12.1 with clean master only. My day usually goes from 8am wake up to 12am sleep. I usually find myself at 60-70% by noon with moderate to high usage. Before I go to sleep, I'm usually 40-50%. I bike to and from work and track that so my location settings are on high accuracy (most draining one). I'm a person who doesn't mind charging my phone every day along with my moto 360. Other flagship phones of comparable calibre might statistically have a higher battery life because of a higher mah, but I feel I end up saving a lot of battery life with the active display feature for checking notifications.
In addition, the apps that I typically use have high battery consumption rate like hearthstone (especially) and browsing a lot of gifs and vids using Reddit Now. In terms of performance, I get lightning fast animations and load speeds in CM (and I'm sure in stock as well). I average 52% RAM usage by allowing a few key apps like fb, fb Msgr, sleep for android, android wear, and mightytext autostart and run in background on my ignore list. If you have anything specific to ask, go ahead since I've used this phone 3 months on stock (bootloader locked and unrooted) as well.
Edit: I should also mention I am XT1095 pure edition. Also, I took the advice of someone and started using system profiles so that when I'm on WiFi at work, home, or place that I frequently visit, I have data connection automatically shut off. I've noticed a significant difference.
Sent from my victara using Tapatalk
hi doug,
please describe a bit more about the system profiles, what you use for it and how significant is that diff. Thanks!
miklosbard said:
hi doug,
please describe a bit more about the system profiles, what you use for it and how significant is that diff. Thanks!
Click to expand...
Click to collapse
I use systems profiles to save battery by having my phone automatically turn off the data connection when I am connected to a list of chosen WiFi spots. Doing this actually improves the battery a ton because normally your phone tries to maintain a radio connection even if you're on WiFi. This causes unnecessary drain on battery, especially if you're in an area with bad coverage. You don't actually need the radio connection to receive texts and calls, only MMS which most people send via fb or whatsapp/etc nowadays.
Back to systems profiles, I have 1 profile I call 'default'. My settings for default are simple. Whenever my phone disconnects from a list of chosen WiFi connections, my data connection is turned on. Its quite simple to set up. There's an option clearly labelled WiFi where you choose from a list of WiFi spots your phone has connected to. Once you've chosen the list, you set the option 'trigger upon disconnect'. Then, I have a second profile with the same WiFi spots chosen, but with two differences: triggers upon connection to chosen WiFi spots; and results in disconnection of data connection.
It makes a pretty big difference because I work in an office area where the reception is not always good so my battery sometimes drains like 20-30% unnecessarily trying to reestablish data connection (this happens with all phones). If you usually aren't in areas with bad reception, this trick still helps if you're on LTE connections. I think there's a certain bug with LTE connections and Google play services for lollipop in general where maintaining an LTE connection is quite draining on battery. I myself mainly use 3G cause I find it fast enough. However, everything above is only relevant if you are frequently connected to WiFi. Hope this answered some questions
Moto X (2014) Pure Edition
dougisthelamb said:
Hope this answered some questions
Click to expand...
Click to collapse
It definately did, thanks
My only remaining question is what app you use for this? Tasker or llama or something else? I tried a some of these apps a few years back but then they were draining more battery than saving. Any suggestions there?
miklosbard said:
It definately did, thanks
My only remaining question is what app you use for this? Tasker or llama or something else? I tried a some of these apps a few years back but then they were draining more battery than saving. Any suggestions there?
Click to expand...
Click to collapse
I used to use both clean master and battery doctor. Now I only use clean master. When using clean master, make sure you give it root access and add all non essential apps to the 'block auto start' list. As well, close processes occasionally using either the clean master boost or the multi task window. Clean master is also really good for finding useless stuff that takes up memory for you to delete.
Moto X (2014) Pure Edition
Hey. Can you post screenshots of your battery graph with screen on time upon the end of your typical day?
I'd love to but I don't have enough posts to post outside links... Perhaps pm me and I can send them?
Moto X (2014) Pure Edition