Related
I've had my Nexus 4 for about two weeks, so everything should be synced up already and I can't blame it for the battery drain. In the battery settings, I noticed the Android OS would keep my Nexus 4 "awake" for almost the majority of the phone's battery life.
I unchecked one setting in Google Now and the keep awake time is significantly reduced. My battery is also lasting longer.
1. Go into Google Now settings (scroll all the way down in Google Now to see settings button)
2. Click Voice
3. Uncheck Hotword detection (make sure it's off - I also unchecked Block offensive words and Personal Recognition)
4. Reboot phone
Albeit, I'm not a heavy user like some of you guys, but doing this has given me more confidence in the battery. I have Google Now, location history, GPS, and sync enabled. My brightness is set to Auto and haptic feedback/NFC are off. My service is T-Mobile and I rarely use Wifi.
I think the Hotword detection was keeping the phone awake to listen for the word "Google."
Let me know if you guys see a change in battery life.
Thanks.
Thanks for the tip, giving it a try now.
It only listens for the word "Google" when you're on the Google Now / Google Search app. This is just a placebo; you're seeing the effect you want to see.
nawoa said:
It only listens for the word "Google" when you're on the Google Now / Google Search app. This is just a placebo; you're seeing the effect you want to see.
Click to expand...
Click to collapse
What he said. I don't know where the OP came from this idea that Google Now is a culprit of battery life. Where is your evidence of this?
I know that if you have Google Now with cards on with constant GPS on, it would drain. But if you turn off the cards you don't want (or all of them) then you won't have any problems.
Personally for me, I only leave the tracking of my orders on. I leave hotword and personalization on and its fine.
Battery life for me yesterday, http://zephik.com/upload/Screenshot_2012-12-14-19-05-58.png -- I don't think that this is causing any problems.
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 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?
"Bluetooth Share" draining battery...even after full wipe and flash from 5.1.1 to 6.0
Hey guys - for the last few weeks I've noticed "Bluetooth Share" as the top culprit for my battery drain...haven't had this problem before and can only fix it by turning off Bluetooth...I'm accustomed to leaving Bluetooth on 24/7 because it's a pain in the butt to turn it on and off every time I get into my car, and the battery drain has never been significant.
Anyways, I was eager to update to 6.0, figuring that would cure the problem...but after wiping, flashing, wiping again...Bluetooth Share is still killing my battery! The only Bluetooth item I have paired is my car stereo.
See the attached screenshots.
Please let me know if you have any advice for solving this. Thanks!
I had the same issue turned out to be the app "Tasker." Dunno if you have that app at all but I figured I'd say since I had exactly the same issue and deleting some random profile I had setup for something that didn't have anything to do with bluetooth ended up fixing it.
StykerB said:
I had the same issue turned out to be the app "Tasker." Dunno if you have that app at all but I figured I'd say since I had exactly the same issue and deleting some random profile I had setup for something that didn't have anything to do with bluetooth ended up fixing it.
Click to expand...
Click to collapse
Hmm I hope I don't have to go through the painful process of uninstalling all my apps until it stops! I don't have Tasker installed right now so maybe it's something else...thanks for the heads up.
exactly same problem here...have to say that first days on android 6 didn't notice this wakelock, but started after second charge.
i am also using tasker to change the audio setting when i connect to my car bluetooth, but also uses android smart lock to disable security code with my pebble.
did you try to disable bluetooth scanning from location settings menu?
beren said:
exactly same problem here...have to say that first days on android 6 didn't notice this wakelock, but started after second charge.
i am also using tasker to change the audio setting when i connect to my car bluetooth, but also uses android smart lock to disable security code with my pebble.
did you try to disable bluetooth scanning from location settings menu?
Click to expand...
Click to collapse
Yeah that's the first thing I tried - disabling that Bluetooth scanning setting - but it didn't change anything.
Have you tried disabling Tasker to see if it fixes your problem?
not yet, i am going to do and check in the next hour.
btw it's strange that this problem didn't come out since the first charge, as i activated tasker immediately...
this is my first charge on android M:
http://forum.xda-developers.com/showpost.php?p=63262307&postcount=2610
disabled only the tasker profile that checks for bluetooth interface that i have in my car and seems that the problem is solved....now i have 8 alarms/hour made from bluetooth.
don't know if i should put tasker in the whitelisted apps for Doze, maybe this would help...
beren said:
disabled only the tasker profile that checks for bluetooth interface that i have in my car and seems that the problem is solved....now i have 8 alarms/hour made from bluetooth.
don't know if i should put tasker in the whitelisted apps for Doze, maybe this would help...
Click to expand...
Click to collapse
I'm curious if we have the same sort of issue - I know I don't have Tasker installed but another app may be doing the same thing...however I did have this issue on 5.1.1 as well, so I don't believe it's Doze causing it.
Seems tasker is not the problem after a while the wakelock comes again, now I am focusing on smart lock, will try to remove all trusted devices...
Inviato dal mio Nexus 6 utilizzando Tapatalk
Having similar issue on Nexus 5 with 6.0. Just removed android wear and disabled smart unlock. In looking around, it seems like many things seem like a fix but come back after the device is charged. Or certain bluetooth devices are connected and then disconnected. On disconnect, the wakelock occurs so rooted users are killing bluetooth and having luck with that. Also found this older, but still active group. https://code.google.com/p/android/issues/detail?id=87778 many there have found apps that are causing the issue. GassBuddy being number one.
acwalter said:
Having similar issue on Nexus 5 with 6.0. Just removed android wear and disabled smart unlock. In looking around, it seems like many things seem like a fix but come back after the device is charged. Or certain bluetooth devices are connected and then disconnected. On disconnect, the wakelock occurs so rooted users are killing bluetooth and having luck with that. Also found this older, but still active group. https://code.google.com/p/android/issues/detail?id=87778 many there have found apps that are causing the issue. GassBuddy being number one.
Click to expand...
Click to collapse
Ooh interesting - I use GasBuddy - I wonder what it needs Bluetooth for...
jeffreii said:
Ooh interesting - I use GasBuddy - I wonder what it needs Bluetooth for...
Click to expand...
Click to collapse
Wow I just tested 10 minutes with Gasbuddy enabled...then froze it with TiBu and tested 10 more minutes...and the Bluetooth Share drain was down from 14% to 0.3%...
What a shame that the new app permissions in 6.0 don't allow you to take away Bluetooth access...I really like GasBuddy...time to email the dev.
Great find! Thanks for the help!
may i ask if you see bluetooth in android battery stats? because i don't see it, but i notice wakelocks only in BBS.
btw for me it's related to pebble time, if i leave the smartwatch disconnected the wakelocks go down. Will try to remove android wear as suggested...
beren said:
may i ask if you see bluetooth in android battery stats? because i don't see it, but i notice wakelocks only in BBS.
btw for me it's related to pebble time, if i leave the smartwatch disconnected the wakelocks go down. Will try to remove android wear as suggested...
Click to expand...
Click to collapse
For me it was "Bluetooth Share" in GSAM Battery Monitor. I don't recall if I saw it in the normal battery stats or not.
I was slowly picking my way through apps, uninstalling and watching the bluetooth usage. I lost patience after removing maybe 15 apps, I don't use any of the "usual suspects". I ended up doing a complete wipe and flashing the 6.0 factory image and am now adding apps back in one by one. For reference, I enable all services and do not turn them off... Wifi, bluetooth, location, Wifi scanning etc. I am too lazy to turn them off and on.
Day 1 - Nothing but factory installed apps, google authenticator and bar code scanner. No bluetooth devices paired but bluetooth in on. Battery last forever, not wake lock.
Day 2 - Added strava app and connected to bluetooth HRM. No wakelock, same battery performance
Day 3 - Added android wear, moto connect and paired moto360. No wake lock and bluetooth keep awake is increasing by about 1 minute per hour so battery life is looking good. Have not enabled smart lock yet, will do that tomorrow.
I keep bluetooth on all the time and complete a full 24 hour cycle with full charge just to make sure that is not part of the problem. Based on my experience, the issue is not the OS or android wear. That leaves misbehaving apps, you just have to find which one through trial and error.
thanks for reporting, can you check how many alarms/hour you have from bluetooth?
Not sure what you mean by alarms/hour. It takes forever for bluetooth to show on my usage now. Yesterday bluetooth got to 2% of total usage for the day.
On day 4, Wi-Fi started rising to the top of the battery used list. Came out of nowhere and it seems like it is an actual bug Google is working on. The fix for me was 3 steps:
1. In Settings/Location click triple dot in top right and select Scanning, disable Wi-Fi scanning
2. In Settings/Backup & reset select Network setting reset
3. Reboot phone
This greatly improved battery life for me. The change is dramatic, I barely went under 50% per day over the weekend. I would suggest everyone try it, it took 4 days to show up but after the battery is outperforming my clean install with no apps. I still have all other services turned on.
I have this same issue!! I Have had the 6 for almost a year now and sinse day 1 I have had BT on almost 24/7. I have my MiBand connected the entire time, LG Tones and Tones+, a couple hours a day also connected to my vehicle (when tones aren't in use) and BT has never ever been a battery drain.
Switch to 6.0 BAM Bluetooth all over the place! I do not have any new apps, no android wear, google fit, pebble, gas buddy etc installed. Nothing new aside the same devices and apps that were there before 6.0.
But at the same time, by battery isn't lasting any less than before, at times a bit longer too (20+ hours) So I don't know if the BT battery data is just skewed? BBS, GSam and Phone all have different stats. I'll post screenshots in a few.
Today isn't the best example of screenshots as the first hour unplugged I had WiFi on (and not connected, forgot to turn off) GPS, MapMyRide app running GPS, Bluetooth and Google Play music all on at the same time (screen off though) and then I downloaded a Rom and Gapps but I'm showing the differences in the battery stats I get
Jeimygirl said:
Today isn't the best example of screenshots as the first hour unplugged I had WiFi on (and not connected, forgot to turn off) GPS, MapMyRide app running GPS, Bluetooth and Google Play music all on at the same time (screen off though) and then I downloaded a Rom and Gapps but I'm showing the differences in the battery stats I get
Click to expand...
Click to collapse
It seems as though certain apps are not working well with 6.0 and causing this issue...GasBuddy seems to be the most popular. I haven't had any problems since I disabled it last week.
You might have to manually determine which app is causing it by uninstalling/reinstalling apps until you find the culprit...
If you do, please post it here so others can find the answer without going through that hassle!
The other choice is to wait until the app gets fixed or Google issues a fix.