7.1.1 Crazy Mega Bluetooth "Drain" - Nexus 6 Q&A, Help & Troubleshooting

I say "drain" because the phone is obviously not using as much battery as Android is saying it does. I'd need to tow around a car battery for this phone.
Anyway, ever since the update to 7.1.1, my Bluetooth battery reading says it uses so much battery, that the other apps dont even show up. I'm rooted but otherwise no mods. I've tried stock, Franco, and Elemental X kernels. I've even tried removing my Bluetooth headphones and car connection. No luck. I can turn bluetooth off, but that defeats the purpose of it when I want to use it.
The only thing I haven't tried is formatting the phone. Before I did that, I figured I'd ask and see if anyone has seen this or had ideas? Searching around for excessive bluetooth drain hasn't helped, and my battery life is just a little bit worse but it could be coincidence?
Ideas?

Well just a follow up, I tried resetting the phone...no luck. New and fresh now, still reading a huge battery drain.

FWIW, I'm seeing the same thing on the January 7.1.1 build and now the February one too. 32% today. A couple days ago it was between 40 and 45%.

It's been like this since 7.1.1 came out. I thought it was something to do with my Pebble but I guess not.

I went ahead and restored my original 7.1.1 backup. I tried flashing the 7.0 radio and no luck there either. My next change will be going back to 7.0. I'm assuming that will likely fix the problem

I see this as well on the latest Pure Nexus. I don't think I saw it on NitrogenOS since it was using older blobs.
EDIT: It might actually be caused the the new Instant Tether feature. Saw it mentioned on G+ and since turning Instant Tether off, I no longer have the battery drain or bluetooth having the highest percentage.

Same here on the 26Q version of 7.1.1. All my battery stats shows is bluetooth. Yesterday the "computed power use" value I swear was over 100K. I rebooted earlier today and it seems to be showing other items in that list now, but not what should be shown there. I have used apps and they arent showing up there.

Yep. This entire day that I've not had Instant Tethering, I've not had massive battery drain and bluetooth hasn't made the list of battery offenders.
Calling it fixed for me.

This was before instant tether and before 7.1. The first mention of bluetooth battery drain was as soon as 7.0 was released.
Try clearing cache, then open bluetooth share apk and clear data. (it's a temp solution)

What's instant tether?

@scoonie
https://www.xda-developers.com/google-rolling-out-instant-tethering-to-pixel-and-nexus-devices/

scoonie said:
What's instant tether?
Click to expand...
Click to collapse
Ha! Not keeping up with your reading...
As it happens, I see it on the right-hand sidebar beside your post:
https://www.xda-developers.com/google-rolling-out-instant-tethering-to-pixel-and-nexus-devices/
Look right... "Analysis and Opinion".

velishka said:
This was before instant tether and before 7.1. The first mention of bluetooth battery drain was as soon as 7.0 was released.
Try clearing cache, then open bluetooth share apk and clear data. (it's a temp solution)
Click to expand...
Click to collapse
This temp solution fixed it for me. Thanks!
Sent from my Nexus 6 using XDA Labs

teinwhite said:
I see this as well on the latest Pure Nexus. I don't think I saw it on NitrogenOS since it was using older blobs.
EDIT: It might actually be caused the the new Instant Tether feature. Saw it mentioned on G+ and since turning Instant Tether off, I no longer have the battery drain or bluetooth having the highest percentage.
Click to expand...
Click to collapse
I turned my instant tethering off and everything is back to normal as far as what's showing in the battery stats. I might turn it back on to double check but I'm confident instant tethering was causing it for me.

Just an update but I've stayed on 7.1.1 and didn't give myself time to downgrade to 7.0. I began having problems with Google Now not populating and constantly being blank as well as the incorrect battery usage.
I went ahead, turned off instant tethering, cleared both the cache and data in the Google App, and installed the newest Google beta 6.13.21.21. Now my Google Now has been working great for 3 days but my battery usage reading are back to normal as well. It could be a problem with the google app? Or it could be an issue with the instant tethering as mentioned because that is part of the google app?

What can I do if instant tethering is nowhere to be found. Pure Nexus 711 dynamic Gapps full edition

I have this problem. It started on 7.1.1. When Bluetooth is on, but not connected to a device its constantly scanning. Its detecting hundreds or even maybe thousands of devices throughout my work day. I work and travel around Manhattan 5 days a week. Once I get home, I have a Bluetooth system I stay connected to all the time and the drain is totally absent. I've observed the same pattern for the past week. Is there any way to stop it from scanning? I don't want to constantly turn Bluetooth off and on when I need to use it. I would love to decide when it scans for Bluetooth.

.me said:
What can I do if instant tethering is nowhere to be found. Pure Nexus 711 dynamic Gapps full edition
Click to expand...
Click to collapse
afm1118 said:
I have this problem. It started on 7.1.1. When Bluetooth is on, but not connected to a device its constantly scanning. Its detecting hundreds or even maybe thousands of devices throughout my work day. I work and travel around Manhattan 5 days a week. Once I get home, I have a Bluetooth system I stay connected to all the time and the drain is totally absent. I've observed the same pattern for the past week. Is there any way to stop it from scanning? I don't want to constantly turn Bluetooth off and on when I need to use it. I would love to decide when it scans for Bluetooth.
Click to expand...
Click to collapse
Try what I did. Clear your cache and data from the Google app. Then find the 6.13.21.21 beta Google App apk online and install it. I rebooted from there and things have been great since Tuesday

Turn of Bluetooth Scanning in three dots menu under location. That solved several Bluetooth issues for me

twan69666 said:
Try what I did. Clear your cache and data from the Google app. Then find the 6.13.21.21 beta Google App apk online and install it. I rebooted from there and things have been great since Tuesday
Click to expand...
Click to collapse
My Google app is functional 100% I've had problems like you experienced with the Google app in the past but now it's loaded up just fine. I turned instant tethering off and I'm going to wipe every cache I can think of so Well see what happens.
muiriddin said:
Turn of Bluetooth Scanning in three dots menu under location. That solved several Bluetooth issues for me
Click to expand...
Click to collapse
Turned that off yesterday and today I still experienced 86% Bluetooth in the battery and nothing else over 10 hours.
Edit I just checked out the battery stats and it says 120% so there's definitely something wrong with Bluetooth here. I'm stock rooted from the tool kit. I'm going to wipe and flash something custom, hopefully it's better.

Related

Wifi keeps turning off during sleep...?

Wifi keeps turning off during sleep...?
.. and yes, I've turned 'Keep Wi-Fi on during sleep' to always. Tried a couple of 'keep wifi on' type apps, no help. Any thoughts? thanks, jf
friedsonjm said:
Wifi keeps turning off during sleep...?
.. and yes, I've turned 'Keep Wi-Fi on during sleep' to always. Tried a couple of 'keep wifi on' type apps, no help. Any thoughts? thanks, jf
Click to expand...
Click to collapse
Mine does to, but I don't have it set to "always", since I kind of prefer it that way. I'll give it a shot to see what the results are. Do you notice any difference between the two settings, as far as how long it stays active and on?
phonic said:
Mine does to, but I don't have it set to "always", since I kind of prefer it that way. I'll give it a shot to see what the results are. Do you notice any difference between the two settings, as far as how long it stays active and on?
Click to expand...
Click to collapse
Have not tried the 'when plugged in only,' will try it now..
EDIT: Nope, that was no better.. <sigh>
friedsonjm said:
Have not tried the 'when plugged in only,' will try it now..
EDIT: Nope, that was no better.. <sigh>
Click to expand...
Click to collapse
31 Minutes on hold - so far - with Google device support...<sigh>
friedsonjm said:
31 Minutes on hold - so far - with Google device support...<sigh>
Click to expand...
Click to collapse
FYI - "Always on" seems to be working fine for me. I turned my screen off about an hour ago, and just connected into the system via Cerberus. In the past, wifi would have shut off within a few minutes and I would get a connection timeout warning. So maybe your unit is having issues with it. I've also only lost MAYBE 1% in battery power, so I think I will leave mine in this state as opposed to disabling wifi on sleep.
I have this problem on some of my devices on 1 of my wife access points but not the other. I believe I could possibly tweak some settings on the access point as I don't believe it is the android device. I use an app called WIFI Fixer and that keeps things working.
friedsonjm said:
Wifi keeps turning off during sleep...?
.. and yes, I've turned 'Keep Wi-Fi on during sleep' to always. Tried a couple of 'keep wifi on' type apps, no help. Any thoughts? thanks, jf
Click to expand...
Click to collapse
Happening on multiple devices. Try advanced WiFi lock on the market. Its one of the first apk's I install and always works.
Sent from My Ball of Fire™
SirWill said:
I have this problem on some of my devices on 1 of my wife access points but not the other. I believe I could possibly tweak some settings on the access point as I don't believe it is the android device. I use an app called WIFI Fixer and that keeps things working.
Click to expand...
Click to collapse
Seemed to work for a while last night... but woke up this morning and it was off again <sigh>.
Does keeping wifi "always on" adversely affect your battery?
clankfu said:
Does keeping wifi "always on" adversely affect your battery?
Click to expand...
Click to collapse
Yes. How much depends on how many apps you have set for auto-updates, I suppose. If you're running several games and social networking apps and they're set for auto-updates, you'll experience a battery drain from them checking for updates every 5 minutes. How much, I can't say. I still don't have my Nexus 7. But if your device drops off the WiFi signal, those apps will know that there is no data connection and not try to update until there is one.
Not to change the subject of the thread, but if I see one more <sigh> I'm going to snap.
Also, OP, why do you need WiFi to be always on? If you can't live without it try: http://bit.ly/MdurdU
As I mentioned, "always on" is working fine for me. Tested it over a period of a few hours. Even moved from one AP to another (ie: work to home), and it auto joined the new wlan.
Battery drain is very minimal in my case. Maybe 0.5-1% an hour, if that.
Yeah but then the apps can't update. IMHO, if you don't want constantly-updating apps, don't enable them to.. If they are checking as often as you think, I would find a different app which gives you what you want but doesn't do that sillyness..
I keep Wi-Fi on 24/7 on all my devices. GPS and BlueTooth too.
I *REFUSE* to let my device "run my life". I find a way to make my battery life happy, and still enjoy my devices. I disable all of the other senseless crap like Facebook or FriendStream, or bloatware-apps.. I don't EVER use an app like ATK or JuiceDefender, or if I do, I only use it instantly to kill an app and then I make it kill itself too. In my 3+ years experience with Android and 30+ devices, I've found that a LOT of apps will TRY to restart even if you kill them. Imagine ATK killing an app, it restarting, ATK auto-killing it again, it restarting again, ATK re-killing it AGAIN, loop()... get my point? Uninstall the problem app and/or find a similar one which doesn't treat your device like it's own playground..
miketoasty said:
Not to change the subject of the thread, but if I see one more <sigh> I'm going to snap.
Also, OP, why do you need WiFi to be always on? If you can't live without it try: http://bit.ly/MdurdU
Click to expand...
Click to collapse
,,
I want to use my table as a phone via VOIP when I travel, need to get incoming 'phone' calls.
That app is coming across in play as not compatible with the N7 ? <darn> <grin?>
I use my Nexus 7 as a speaker phone so had to set "Keep Wi-Fi on during sleep" to "Always". Easy fix.
mi7chy said:
I use my Nexus 7 as a speaker phone so had to set "Keep Wi-Fi on during sleep" to "Always". Easy fix.
Click to expand...
Click to collapse
Yes... and as I said in the post that started this thread, on my N7, it still turns off.... easy, but no fix.
friedsonjm said:
Yes... and as I said in the post that started this thread, on my N7, it still turns off.... easy, but no fix.
Click to expand...
Click to collapse
Now rooted and still trying... still keeps auto-turning-off !
This might be a defect in your units. I have gone many, many hours (12+) with my unit in standby mode without it losing wifi connection. It will also continue to sync with email, etc. during this time (and provide audio notifications).
I only lose .5-1%/hour, so I've left it "always on".
I'm having the same issue. On overnight sleep, the wifi is off when I turn it on. It won't reconnect until I toggle wifi on and off. Nothing I've tried so far has worked. Little worried its not as widespread of an issue as I thought it would be.
ssahnan said:
I'm having the same issue. On overnight sleep, the wifi is off when I turn it on. It won't reconnect until I toggle wifi on and off. Nothing I've tried so far has worked. Little worried its not as widespread of an issue as I thought it would be.
Click to expand...
Click to collapse
Since mine has worked flawlessly (stock rom) for very long periods of sleep with an active wi-fi connection, I would have to believe you have a defect in yours. Either that, or a problematic AP.

5.0 Lollipop Battery drain and phone is HOT!!!

I have updated to the lollipop update like many and my phone is warm and sometimes hot.
I am not using my phone and it still gets warm and drains the battery life.
In 4 hours I will go from 100% to dead with no use.
My screen was off but shows it as being on. **See attached photo
I searched the MOTO threads and cant find anything as of now to resolve this issue.
Anyone else having this issue and find a fix?
Tried wifi channels to see if this issue fixes this, cleared cache and nothing........
Hope help comes quick!
If I can get some help I will buy them a beer or coffee!
Okay here's an updated seems to fix the issue......
I disabled the WiFi location settings, download clean master -- https://play.google.com/store/apps/details?id=com.cleanmaster.mguard -- and seemed to have fixed the issue so far.
Keep you posted as the day goes on.
After you updated, did you do a factory reset? If not, and before you do, what apps do you have installed? You might have an unruly app that's just constantly running. I hear Google Fit hasn't been too friendly...
Since Google services is pretty high on the usage list, it could have something to do with syncing errors or maybe problems with updating Google Play services/Play Store. Make sure you have the latest versions.
Google Play services (6.5.85) - http://www.apkmirror.com/apk/google.../google-play-services-6-5-85-1589008-438-apk/
Google Play Store (5.0.38) - http://www.apkmirror.com/apk/google-inc/google-play-store/
Also, unsync any services in your Google account that you aren't using.
Don't forget to turn off extraneous radios like WiFi (if you don't use it for location), GPS, NFC, and Bluetooth when you're not using them.
If all else fails, factory reset and pay attention to the apps that are being downloaded. Uninstall garbage and disable what you can't uninstall, but don't use. Hopefully this helps.
EDIT: Seems you fixed it. Nice! Well, use this as a reference for your next step if things don't stay behaved.
Anfeldt24 said:
I have updated to the lollipop update like many and my phone is warm and sometimes hot.
I am not using my phone and it still gets warm and drains the battery life.
In 4 hours I will go from 100% to dead with no use.
My screen was off but shows it as being on. **See attached photo
I searched the MOTO threads and cant find anything as of now to resolve this issue.
Anyone else having this issue and find a fix?
Tried wifi channels to see if this issue fixes this, cleared cache and nothing........
Hope help comes quick!
If I can get some help I will buy them a beer or coffee!
Click to expand...
Click to collapse
Clear cache and reboot. If you still have the problem, do a factory reset. Also, has the phone stabilized? Have you been through a couple of charge/use cycles? There could be a load of background processes setting up for the first day or so.
Seems the Qualcomm battery guru is a culprit as is the xfinity WiFi app.
Motorola said do a factory reset but I don't want to if something else can be done.
Think it's fixed by the WiFi location and the clean matter app showing the apps that kill the battery.
Here is a great article about asps that keep restarting in lollipop. It's a bug in ART. Google is working on a fix.
http://www.androidpit.com/android-5-0-lollipop-bug-apps-frequently-restart-in-background
Another great way to help save battery. http://www.androidpit.com/android-5-0-lollipop-problems-and-solutions
Best method... Root and use greenify...
Sent from my XT1092 using XDA Free mobile app
I'll post my battery drain/overheating story just to join the fray...i updated to Lollipop 4 days ago and I have had to charge my S5 at least a dozen times. I have tried power save mode, disabling every nonessential app and anything else I can find in the forums.
I used to get 15-16hrs of battery life (6am-10pm) with charge to spare, but immediately after the update my CPU sits maxed (monitored by Micro CPU Monitor) and constantly overheats (GSAM Battery Monitor). The phone went from 95°F to 105°F in 10min with standard use. I only had it overheat one other time in the last year (on my dash in the summer). I hope Google/Verizon will replace my battery because this abuse of it is going to shorten the life considerably!
See screen shots from the last charge at 4pm to now (10:15pm) all while UNUSED and in powersave mode plus battery at 107°F (a new record for me)!
I really don't want to reset the phone and lose my app settings, plus it seems to be hit/miss with other's issues. Any suggestions would be great.
Seems hit or miss.
Not sure what to tell you but try making sure you're Wi-Fi isn't always searching for locations when not connected. Seems this is a huge problem for many as Verizon threads and Android forums are filling up. I don't have an S5 but will keep looking for the fix.
Quick read-
http://www.gottabemobile.com/2015/02/09/verizon-galaxy-s5-lollipop-update/ many are having this issue but not all.
Posted from my Moto X 2014
i am facing similar problem with my moto g2 if you find any solution please let me now
same problem to me also friend if u found any solution for it please mail to me [email protected]

Fixed my connectivity and battery life

Let me preface this by saying that after changing this setting and 20 hours later with multiple separations of phone and watch, I have yet to miss a notification and battery life is much much better. My specific problems were: Watch would randomly stop receiving notifications. I would realize this after a few hours go by without any notifications and pull my phone out and see what I've missed. This would happen despite the Wear app showing 'connected' status. Another issue I had was giving a voice command and after a few seconds the watch would return a 'disconnected'message, again the Wear app showed connected. All of this under known working network connections, whether Wi-Fi or cellular. I was also experiencing what I feel is short battery life at about 14 hours per day. I've had and used the watch for two weeks now and have restarted it many many times.
The following is the ONLY thing I have changed since the major improvement in performance. I don't have the depth of knowledge to prove or describe why this worked for me, and maybe it wasn't the cause, but I (knock wood) have a perfectly operating watch now with the battery life indicating about 2 days remaining at noon today.
Go to Settings> Bluetooth> and select the settings icon on your connected device. Then select 'connection access' and choose 'automatic'. Mine defaulted to 'always ask'.. I'm guessing this caused a hangup with the connection between Wear app and watch leading to my problems.
Edit: I'll add that my phone is an LG G2 on 4.4.2 , rooted and running xdabbeb's Rom.
Edit 2: I reset my watch, synced the watch via the Wear app on phone and NOT the Bluetooth screen and now I'm running strong after two days. Made sure automatic was checked as well.
Bugger
I don't have that option in my bluetooth settings
I don't have any problems with mine so far but just checked my settings and it was on always ask.
Could anyone confirm what it should be set as? I have changed mine to automatic anyways.
Thanks for the heads up.
Phil
Not seeing that option in Android 5.0.1 on my HTC One GE. But I have not been having any of the issues mentioned in the OP.
Sent from my Nexus 10 using Tapatalk
Here is a pic of the screen where you make selection. Always Ask is NOT what you want, which is what is pictured. Select Automatic. Sounds like this isn't available on Android 5.0 from what I see in responses so far.
I don't think I saw this option on any of the ROMs I ran, but there may be devices out there that have it and default to it, and this one would really break wear connectivity - so it may help someone someday.
I'm on 5.0, lg g3 and have both options.
Although i havnt had a problem with always ask and only switched it to automatic tonight.
Judging from the description, it will work as long as the watch stays connected, but a reconnect from the watch side would ask for confirmation (and could be possibly even silently denied under some circumstances).
Phone -> Watch = no problem
Watch -> Phone = problem
and it's possible (and likely) there are more connections going on than just the primary one, and if the connection is flaky there might be a dead one and a new one from either side...
you could just have been lucky, so far
My issues returned last night. I left my watch at home and went to dinner and out with friends, came back home after several hours. I left the watch in theater mode while I was out and over night. I woke up this morning, put watch on and realized the battery had tanked overnight and I was no longer receiving notifications, again, wear app showing connected. I looked at the battery graph for the watch and it is totally flat while I was out last night and appears to tank fast as soon as I got home and my phone was in proximity to the watch again. It's like it is constantly trying to handshake with the phone or something. The only thing that fixes this problem is a reboot of the Watch itself. I still think the connection setting was helpful because I have yet to see battery life like that or a solid link for that long. I would love to know what exactly is going on here. Bad hardware?
For the sake of comparison, I have android wear in my pull down bar saying 'connected, running sync loop' 100% of the time. It never goes away. Is this what everyone else sees?
That's what I have also since I own the watch.
Stbrightman said:
For the sake of comparison, I have android wear in my pull down bar saying 'connected, running sync loop' 100% of the time. It never goes away. Is this what everyone else sees?
Click to expand...
Click to collapse
That would be because you have Android Debugging turned on in the phone settings.. Means nothing..
mic18u said:
That would be because you have Android Debugging turned on in the phone settings.. Means nothing..
Click to expand...
Click to collapse
Nope, shows also when out of the box so without android debugging.
Just a normal operation notification
I just discovered another possible contributor to connectivity issues: I just tried to use my watch to voice dial and after multiple attempts I got the disconnected message. I took my phone out and Wear app says connected and I had full 4G signal. My phone is set with a pattern lock. After unlocking it and checking the above mentioned, I tried the watch again and it worked. Could locking your phone have something to do with these problems?

WiFi keeps turning on and off on its own

I don't know what might have happened, but this morning, I tried to connect my Phone to WiFi, and for some reason, it wouldn't. The WiFi toggle button that you see when you pull down the Notification Bar, now that WiFi button keeps turning on and off constantly. The time it takes between each toggle (on to off or off to on) is just about 0.5 - 1 sec. This is crazy. I can't connect to my WiFi.
I googled for solutions, no luck. I hard reset my Phone, no luck still. I wiped Partition Cache too. I entered into the Safe Mode, the same behavior happened. It's weird. It's like my Phone is possessed or something. A virus maybe?
Any input would be much appreciated. My phone is running the latest Firmware from T-mobile. And I got the update maybe 1-2 weeks ago and it had been working fine until this morning the issue started.
My phone just started doing this as well. Wifi keeps turning off and on. If I want to keep it off I have to restart my phone. If I want to use the wifi I have to manually toggle it from the wifi settings. Just weird it started doing this just recently. Maybe an app we both have installed?
I think I've found the issue. Sadly only after 3x reformatting the phone.
Go to Settings, Location, then click on Improve Accuracy, then turn off WiFi and Bluetooth Scanning (actually just the WiFi scanning would do the trick, but I decided to just turn off both of them). I suspect an update to one of Google system apps might have caused the phone's WiFi to behave weirdly like this. For the past 2-3 years I've had this phone, it had been fine with these two options turned on. It changed yesterday.
Let me know if this solution works for you.
febzz88 said:
I think I've found the issue. Sadly only after 3x reformatting the phone.
Go to Settings, Location, then click on Improve Accuracy, then turn off WiFi and Bluetooth Scanning (actually just the WiFi scanning would do the trick, but I decided to just turn off both of them). I suspect an update to one of Google system apps might have caused the phone's WiFi to behave weirdly like this. For the past 2-3 years I've had this phone, it had been fine with these two options turned on. It changed yesterday.
Let me know if this solution works for you.
Click to expand...
Click to collapse
Haha I was about to post this solution as well! Turning off the wifi in location accuracy fixed it. You're right about probably some Google app is causing this as this hadn't happened before yesterday. Sorry you had to format your phone to find this out...hopefully google or samsung can fix this from their end.
Thanks for this! Working for me (I'm on Tekxodus URv7.4R2 N5R9 with Emotion Kernel (r23).
Was driving me nuts. I'm a bit concerned about the loss of wifi for location accuracy though since my phone's GPS has been borked ever since i can remember.
Update: I noticed a recent review on the Play Store for Android Wear referring to a recent Wear update possibly causing the issue. I have Wear installed for a watch. Just curious if anyone experiencing this problem does NOT have Wear installed?
muzzy996 said:
Thanks for this! Working for me (I'm on Tekxodus URv7.4R2 N5R9 with Emotion Kernel (r23).
Was driving me nuts. I'm a bit concerned about the loss of wifi for location accuracy though since my phone's GPS has been borked ever since i can remember.
Update: I noticed a recent review on the Play Store for Android Wear referring to a recent Wear update possibly causing the issue. I have Wear installed for a watch. Just curious if anyone experiencing this problem does NOT have Wear installed?
Click to expand...
Click to collapse
I just uninstalled wear and same issue persist. Last app from Google that I did an update on was Google home...formally known as chromecast.
---------- Post added at 10:30 AM ---------- Previous post was at 10:04 AM ----------
I just uninstalled Google home and the issue went away.
I do have Google Home and Android Wear installed as well. I checked the Google Home App Play Store Page and someone commented there pointing out about the issue too.
febzz88 said:
I do have Google Home and Android Wear installed as well. I checked the Google Home App Play Store Page and someone commented there pointing out about the issue too.
Click to expand...
Click to collapse
Yup that was me leaving a comment haha
i have had exactly the same problem for a day or two. while disabling "location>improve accuracy>wifi scanning" stops the bug temporarily it doesn't really solve the problem. wifi scanning is an important location feature when navigating. in narrow streets or in buildings one usually does not have gps reception, also the wifi scanning technique for determining the devices location is usually faster and uses less battery than gps (how ironic).
this bug is extremely annoying. i am on an unbranded, unrooted s5 on 6.0.1 (g900f). i can not believe that this also happens with s7 and pixel phones, this is really ridiculous (see similar thread on androidcentral forum. can't post url because this is my first post). if anyone finds a permanent solution for this problem, please tell us!!!
androidschmandroid said:
i have had exactly the same problem for a day or two. while disabling "location>improve accuracy>wifi scanning" stops the bug temporarily it doesn't really solve the problem. wifi scanning is an important location feature when navigating. in narrow streets or in buildings one usually does not have gps reception, also the wifi scanning technique for determining the devices location is usually faster and uses less battery than gps (how ironic).
this bug is extremely annoying. i am on an unbranded, unrooted s5 on 6.0.1 (g900f). i can not believe that this also happens with s7 and pixel phones, this is really ridiculous (see similar thread on androidcentral forum. can't post url because this is my first post). if anyone finds a permanent solution for this problem, please tell us!!!
Click to expand...
Click to collapse
Do you have Google Home installed? After I uninstalled that the wifi issue stopped
alanmv567 said:
Do you have Google Home installed? After I uninstalled that the wifi issue stopped
Click to expand...
Click to collapse
no, i do not.
muzzy996 said:
Thanks for this! Working for me (I'm on Tekxodus URv7.4R2 N5R9 with Emotion Kernel (r23).
Was driving me nuts. I'm a bit concerned about the loss of wifi for location accuracy though since my phone's GPS has been borked ever since i can remember.
Update: I noticed a recent review on the Play Store for Android Wear referring to a recent Wear update possibly causing the issue. I have Wear installed for a watch. Just curious if anyone experiencing this problem does NOT have Wear installed?
Click to expand...
Click to collapse
Is it your GPS or the Compass? If it can still detect your location but when you use, for example, the Google Maps Navigation, it couldn't really detect where/which direction you're going then it's probably just a compass issue. All you need is some calibration.
I fixed my friend's phone compass issue (and she thought her GPS was broken too) last week. The easiest way to calibrate: just download the GPS Status app and tap on the Calibration option and follow the instruction there.
Always try to calibrate your compass first as the first possible fix whenever you think your GPS is starting to go crazy, it might help.
Go to location>improve location>unchecked wifi scanning. It just worked for me
Uninstalling android wear seems to have worked for me.
febzz88 said:
Is it your GPS or the Compass? If it can still detect your location but when you use, for example, the Google Maps Navigation, it couldn't really detect where/which direction you're going then it's probably just a compass issue. All you need is some calibration.
I fixed my friend's phone compass issue (and she thought her GPS was broken too) last week. The easiest way to calibrate: just download the GPS Status app and tap on the Calibration option and follow the instruction there.
Always try to calibrate your compass first as the first possible fix whenever you think your GPS is starting to go crazy, it might help.
Click to expand...
Click to collapse
Definitely not the compass, been through the calibration process. Attempted many fixes including special GPS settings and utilities. At times the phone can sit there with screen on for over 10 minutes without acquiring a single satellite. I'm thinking hardware issue, possibly contacts for the antenna. In any case, not relevant to this thread...
I rebooted into recovery and wiped both CACHE and this fixed the issue. I did not change any settings in any apps either.
DirtySant0 said:
I rebooted into recovery and wiped both CACHE and this fixed the issue. I did not change any settings in any apps either.
Click to expand...
Click to collapse
I had tried this prior to reformatting my phone and it didn't help. I then wiped the cache again and reformatted the phone; in fact I reformatted and cleared cache 3x because the issue kept coming back after I reinstalled apps again. This is weird, the situation and resolution vary a lot from one user to another. Then I simply turned off WiFi Scanning under Improve Accuracy in Location, and the issue went away.
WHEW! Uninstalling Wear and Home did it for me. For now, anyway. I "fixed" it this morning by toggling Ultra Power Saver on and off, and it worked all day until I came home from work. Then nothing helped until I found this thread. Changing GPS settings didn't do it for me, but I'm still on Lollipop so my location settings are a little different.
Thank you, Febzz and Alan!
Google home was the issue!!
Sent from my SM-N910T using Tapatalk
Changes in router's Wireless Security had caused it in my case
This is old thread but still I am posting this solution as it could be useful tip for someone in future.
I had this issue and was causing me real headache. I initially thought it was hardware failure of my phone but later I found reason is something else.
For some reason I had changed Wireless Security of my WiFi router from WPA2 Personal to something else (I guess WEP).
That was causing my phone (intex cloud 4g) often to turn on and off WiFi on its own. I changed the Wireless Security back to WPA2 Personal and phone is now back to normal (not turning WiFi on and off on its own)

Bluetooth Constantly Becoming Disabled

Within the last few weeks I have noticed that upon reset or simply after a period of time, my Bluetooth will either disconnect with my Moto 360 Sport or will become disabled altogether. If I restart my phone, the Bluetooth toggle in settings is always disabled.
Several users have been discussing this issue over in the PureNexus ROM forum, but we have not identified the culprit yet. Some who are experiencing it have Android Wear devices, but not all people do. Those who are experiencing it are on different ROMs, or different builds of the same ROM, leading me to believe that it is an app and not specific to a ROM. Also, for everyone who is experiencing it, it started withing the last few weeks.
I wanted to start a thread to allow people experiencing this issue to find a common cause so that we can correct it.
I'll also tag those who have said they are having this issue to lead them to this post: @Moguledyouth @uberbdon @MVLJR @ethanhunt123 @MysticKing32 @danman7 @hawkz28
I'm unsure which thread is the most appropriate to post this in, so I'll throw it here.
I don't believe the entire issue is tied to 7.1.1. I believe it originated in 7.1.0 or earlier, but got worse in 7.1.1. (Side note, I did on occasion get a "Bluetooth Share has stopped" notification, but only if I was actively using the phone).
My phone's bluetooth began "cycling" at the very latest in 7.1.0. I first noticed the issue when using an app called "wear aware," an app designed to let you know if you leave your phone behind (on your android wear watch). It was frequently giving me "false positives," so I ultimately uninstalled the app. I also began to have issues with android auto, where it would occasionally freeze and stop showing me data. Likewise, when I'd be on a phone call, my radio would randomly turn on and I'd assume the call got disconnected -- until I realized the other party was still on the line but now on speaker phone.
The reason I believe it got worse in 7.1.1 is because it used to cycle bluetooth. At least when it crashed, it restarted. Now it appears to require intervention to re-enable it. As a temporary work-around, I have Trigger set up to enable bluetooth if it gets disconnected from my watch. It doesn't work 100% of the time, but at least it re-enables bluetooth frequently for me (it claims to have run 10 times in the last 2 hours).
It's probably also worth noting that it's been reported on at least the Nexus 6 and the Pixel, from what I've seen.
My current setup:
PureNexus (1/21 release, rooted)
Franco Kernel
Huawei Watch
Prior to this, I was running Stock, unrooted, with the same issues.
Thanks for the workaround (Trigger) - like the speakerphone issue we are experiencing, it might not be an official fix but it works for now. It seems like the more updates we get, the more bugs we get. Seriously, 6.0.1 was about perfect, and I might flash back to that and add the additional Nougat features via xposed.
Post deleted
Finally getting some traction on this issue: Many users are experiencing random Bluetooth disconnects on the Pixel and Pixel XL
Fvolfrine said:
Finally getting some traction on this issue: Many users are experiencing random Bluetooth disconnects on the Pixel and Pixel XL
Click to expand...
Click to collapse
Anyone try to revert to an earlier dialer app or is it in the framework of the Feb patch?
I don't think it's the phone app. I get Bluetooth share disconnects with just a Pebble smartwatch.
As is stated in the second article, this issue is not related to the phone dialer app. I'll delete that post as it might cause some confusiom
Sent from my Nexus 6 using Tapatalk
I thought my phone was dying. I'm having this issue as well. I found that uninstalling Heart Trace, which records my heart rate every 15 minutes from my Huawei Watch, helped a lot with the Bluetooth issue.
It used to be that my Bluetooth would turn off in the middle of the night and I lose my sleep tracking data from my watch (Sleep as Android).
Don't google test their sofware?
This is a poor show by them.
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
semsem_605 said:
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
Click to expand...
Click to collapse
But how often do you have to keep doing this?
Fvolfrine said:
Within the last few weeks I have noticed that upon reset or simply after a period of time, my Bluetooth will either disconnect with my Moto 360 Sport or will become disabled altogether. If I restart my phone, the Bluetooth toggle in settings is always disabled.
Several users have been discussing this issue over in the PureNexus ROM forum, but we have not identified the culprit yet. Some who are experiencing it have Android Wear devices, but not all people do. Those who are experiencing it are on different ROMs, or different builds of the same ROM, leading me to believe that it is an app and not specific to a ROM. Also, for everyone who is experiencing it, it started withing the last few weeks.
I wanted to start a thread to allow people experiencing this issue to find a common cause so that we can correct it.
I'll also tag those who have said they are having this issue to lead them to this post: @Moguledyouth @uberbdon @MVLJR @ethanhunt123 @MysticKing32 @danman7 @hawkz28
Click to expand...
Click to collapse
I'd like to say that after (dirty) flashing the 2/15 update, my issue is resolved. When I reboot now, BT remains enabled.
danman7 said:
I'd like to say that after (dirty) flashing the 2/15 update, my issue is resolved. When I reboot now, BT remains enabled.
Click to expand...
Click to collapse
What is the 2/15 update?
@home said:
What is the 2/15 update?
Click to expand...
Click to collapse
PureNexus ROM. And I'm glad to hear that it resolved this issue, might be time to flashback over from stock.
On a side note, the one thing that I feel stock is missing, and this is minor, is a battery percentage that is not in the icon. Google has added just about everything I wanted to stock except for this one small detail, and yet I'm going to flash over because of it.
Sent from my Nexus 6 using Tapatalk
I'm on stock firmware and Project Fi on Nexus 6 and been having this problem lately yet I have had no updates since the Oct 5 2016 security update on Android v7.0. I wear a fitbit Charge 2 and occasionally use either a bluetooth headset or my car's bluetooth audio. I try real hard to keep my battery charge above 40% at all times. Normally I'm at 70% or higher when these problems occur. [edited to add] Forgot we also have a few Tiles and a LugLoc.
When not using bluetooth at all I frequently find bluetooth has disabled itself on my phone.
When using the bluetooth headset during a phone call bluetooth shuts off and my headset reports it has lost a connection to my phone.
In my car bluetooth is flawless and never shuts down even on long drives 2-4 hours.
I have also enabled trusted devices in Security when certain devices are connected via bluetooth.
Sometimes bluetooth settings loses a device. Sometimes they come back on their own but more often than not I have to repair the device to the phone.
Right now there are so many issues with this phone (including dust in the camera sensor) that makes it real frustrating as an owner.
@home said:
But how often do you have to keep doing this?
Click to expand...
Click to collapse
Only had to do it once
semsem_605 said:
Only had to do it once
Click to expand...
Click to collapse
I just did this about ten minutes ago and rebooted. Bluetooth turned back on after the boot, which is nice. Hopefully it stays on. Thanks for the tip!
semsem_605 said:
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
Click to expand...
Click to collapse
Fvolfrine said:
I just did this about ten minutes ago and rebooted. Bluetooth turned back on after the boot, which is nice. Hopefully it stays on. Thanks for the tip!
Click to expand...
Click to collapse
I tried this earlier today. Made it through two one hour conference calls with only one hiccup between the bluetooth headphones and the phone which did reconnect. No disabled bluetooth yet. I hope this is the fix!
semsem_605 said:
Had the same issue and it stopped after clearing the data on the Bluetooth Midi service and the Bluetooth share apps
Settings> Apps> Show system> scroll down to these 2 apps and Clear data
Click to expand...
Click to collapse
Are you on 7.0 or 7.1.1 & also which security patch?
Thanks

Categories

Resources