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
Related
I have a weird problem with my Moto X 2014 (Pure Edition). It's randomly losing bluetooth connection in a background (basically any BT connection – to auto, smartwatch, etc.) but the phone itself says everything is fine (Bluetooth is on and devices are connected). But actual connection is not working: unable to play music via BT, unable to discover a new BT device, notifications not coming through to a smartwatch, etc. Bluetooth devices continue to show as connected even if I power them off, and when I turn them back on, they won't reconnect.
I meet this problem every 1-2 hours, sometimes even 10-20 minutes. The only way to fix this problem - to turn off BT and then turn it on again. Or keep Wi-Fi always off.
I tried to use another Moto X (2014, same software build version), to pair and unpair devices, to clean cache and even do a factory reset (with and without backup restoring) – the problem is still here. That's weird but this problem start appears 2-3 weeks ago, before everything was just fine.
Phone: Moto X 2014 Pure Edition @ T-Mobile, Lollipop 5.1 (TMO_Pure_5.1_LPE23.32-21.3_5_23.16.3.victara_tmo.tmo.en.US)
Devices: Pebble Time, Pebble Time Steel, Ford SYNC2, Moto Stream.
Things I tried that didn't help: deleting and re-pairing devices, deleting all old device profiles, clearing cache, reflash, factory reset, safe mode, flash CM12.
BT HCI Logs:
A disconnect at 1:28pm
dropbox.com/s/q3pka5egagq3e5g/01_btsnoop_hci.log?dl=0
A disconnect at at 3:09pm (or so)
dropbox.com/s/f2kl4rowr12lypt/02_btsnoop_hci.log?dl=0
Same issue here with a VZW XT1096, since OTA to 5.1. Factory reset does not help.
Up
Same issue here, same device & carrier & software build version & Pebble Time Steel. As long as I'm constantly making use of a BT connection, it seems to stay alive just fine, but as soon as it sits idle for more than a couple minutes, the connection drops (according to the BT device, but not according to the phone). I've tried all the same things with the same total lack of success. I have nothing new/helpful to offer, but at least you're not suffering alone.
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Just to say I have the same problem with a Pebble Time Steel and my 2014 Moto X. Have e to disable BT and dependable BT to get phone to connect to Pebble to only be dropped a few minutes later from Pebble side.
Lyre
AlexanderKirov said:
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Click to expand...
Click to collapse
I'm having the same problems and have also had it "go away" for extended periods of time only to reappear after a day or two. Mine will drop the BT connection even if I'm actively listening to audio over my headset.
Registered because I'm having the same issue. I'm running stock 5.1, no root. The connection to my Pebble Time Steel is very unreliable. The Bluetooth settings thinks it's still connected, the Pebble Time app on my phone thinks it's still connected, but my watch shows no connection and there's no communication to or from my watch. Sometimes it'll work for hours just fine and then drop, sometimes it'll only be a few minutes. It seems to be when the phone screen is off. Turning BT off and on always fixes it, it'll immediately automatically reconnect and show it on the watch.
I've tried the Pebble troubleshooting online (factory reset & recovery mode on watch, uninstall Pebble Time app, forget pairing on all devices, remove all other BT apps, reboot phone, reinstall Pebble Time app, re-pair) but the problem remains.
In the past, I've had it where my Fitbit One seems to have dropped the connection. Since the sync is so infrequent, I don't notice it much but I did catch it where it hadn't synced in a few days. (That app was uninstalled while I try to figure the Pebble thing out)
Next step is factory reset on the phone, but it sounds like that's not a fix for some people. That, or design a watchface that sends a keep alive signal to the phone, which runs an app to reset the BT when the connection drops. Since it's still listed as connected, I don't think Tasker will fix it.
Same issue. My phone is a Verizon Moto X and I've tried factory reset. Hoping that whenever they update to 6 that it will fix the issue, but I'm ready to smash my Moto x over this
AlexanderKirov said:
That's weird by the issue seems to be fixed somehow. Everything works just fine for almost 24 hours now, even with an active Wi-Fi.
Still testing.
Click to expand...
Click to collapse
While I hope your problem is "fixed" I would not be too hopeful. I have had this problem as long as I've had the phone. Sometimes it goes away for a while but it always returns. Right after I unlocked my bootloader and it did a complete factory reset the problem went away for a week but it eventually returned. I've seen similar problems reported with all the MX14 variations and nobody seems to have a solution. There was a thread on the Moto forums with folks reporting these issues to Moto but nothing ever came of it. Seems to be connected to wifi somehow because I don't seem to drop the BT connection if wifi is turned off. Not really a useful solution but it does seem to work. I just gave up and put a BT toggle button on my homescreen.
I had the same problem using marshmallow, I downgraded to 5.1 and it went to normal
Count me in on this 'issue' too. 5.1 XT1096 rooted and BL unlocked. It seems to have started around mid-December and I can't think of any particular change that caused it. Pretty much have to toggle BT 2-3 times a day at this point. FWIW, I started having the problem before the BL unlock so basically factory reset did nothing to fix the issue.
Is there perhaps a way to have the BT automatically toggle at fixed intervals a couple of times a day?
jimbo0914 said:
Count me in on this 'issue' too. 5.1 XT1096 rooted and BL unlocked. It seems to have started around mid-December and I can't think of any particular change that caused it. Pretty much have to toggle BT 2-3 times a day at this point. FWIW, I started having the problem before the BL unlock so basically factory reset did nothing to fix the issue.
Is there perhaps a way to have the BT automatically toggle at fixed intervals a couple of times a day?
Click to expand...
Click to collapse
Update: I changed over to Android M on CM13 and no longer have this issue. Nice not to have to power toggle the BT function a couple times a day anymore.
YMMV
Met the same problem after updating to Android M.
I often connect to BT during driving and after a few days working normally, my headset will be disconnect without any "notification".
My solution is to wipe cache, after that BT connection will work well for another few days.
Never met this issue in Android L, but I just love M so much.
Looking for better solution / fix.
I found this thread while searching for some solution for my BT+Android Wear problems. I have them since circa february / march 2017.
But today, I got a problem with non-Wear watch (Fossil Q Grant). I noticed my phone was locked even if I have smart lock set up. I checked fossil q app, the watch was connected, it received notifications so far. But in the phone settings, in smart lock, all my devices vanished. I checked the BT setting and saw the same. All my paired devices disappeared! It happened after nothing more than a restart, after my fossil lost connection earlier today and did not want to reconnect. So I restarted the phone.
This happened to me the second time already, but first time I somehow did not pay attention because I was frustrated by the Wear app problems and weekly factory resets to get my Wear watches working.
Could our issues be related? Some bluetooth software bug in phone? THIS IS PURE HELL!
Moto X4 cant come soon enough.
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)
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.
Hello all,
I have the 960U1 US Unlocked version of the Note 9 I've had since Day 1 release of last August. It's quite the powerhouse of a phone, and has everything of what you want in a smartphone. I was aggravated by how late the Pie update came, but I never expected how many issues came along with that changed the user experience since Oreo. After updating to Pie, I did a factory reset for a clean run but then I ran into these following issues:
Download, installing, and uninstalling apps from the Play store: I've tried to download apps, which get stuck at 99% or 100%, but then just hangs there to not install. Same thing with uninstalling. It'll say uninstall for an abnormally long time.
GPS issues: I travel frequently on weekends. Sometimes I would like to pull up my Google Maps timeline to review where I went and at what times. One weekend, I went out of town 3 hours away from home and yet my timeline showed me saying I stayed all day and night where my Home location is. Map guidance still worked, but it still showed me that my "current location" was still being at home.
Bluetooth Power indicator pop up: This is a recent issue I found that other Samsung users in other forums encountered as well. I have a Sony WI-1000x Bluetooth neckband that does extremely well for all the bells and whistles it does. I've noticed that after I factory reset again after experiencing the previous 2 issues to get them fixed, there is a pop up that keeps appearing every 10 or so seconds that tell me my headset is battery at 100%. I have found no way of disabling that, and I had to unpair/pair my headset as well as clear Bluetooth data in System App settings to try and get rid of it. Good thing it hasn't been doing that after several tries, but now there is another issue with BT.
Bluetooth notification sound output: I've noticed when my BT is connected, I don't hear notifications from my text messaging app, e-mail, Arlo, and social media apps. I've checked to see that my Sound settings are all up and running as it should be. Then I went to try and play a notification sound, and nothing came out of my phone speakers. It only played through the headset itself, and that's an annoyance as I don't wear them all the time in my ear unless I'm using it for phone calls or listening to media. It seems to be an Android Pie issue and I have yet to find a permanent solution as this wasn't an issue before on Oreo. The only workaround I've found is using the SmartThings Audio Output toolbar in the Notifications drop down and select to play Media from my device. The notification sounds work then, and I can still answer calls through my headset. But it's a dumb issue that I have to manually set this whenever I want to go back to listening media.
The Note 9 is a great phone despite the small shortcomings it had before the Pie update. Now it's after the Pie update, all these issues come up and I don't understand what happened in what Samsung did. I'm almost tempted in calling Samsung to ask if my phone just somehow became defective, but I don't want to have something done and they send me some refurbished model when I kept my phone in near mint condition. What are your guys' thoughts about the issues I've had and what solutions would you suggest?
GigaSPX said:
Hello all,
I have the 960U1 US Unlocked version of the Note 9 I've had since Day 1 release of last August. It's quite the powerhouse of a phone, and has everything of what you want in a smartphone. I was aggravated by how late the Pie update came, but I never expected how many issues came along with that changed the user experience since Oreo. After updating to Pie, I did a factory reset for a clean run but then I ran into these following issues:
Download, installing, and uninstalling apps from the Play store: I've tried to download apps, which get stuck at 99% or 100%, but then just hangs there to not install. Same thing with uninstalling. It'll say uninstall for an abnormally long time.
GPS issues: I travel frequently on weekends. Sometimes I would like to pull up my Google Maps timeline to review where I went and at what times. One weekend, I went out of town 3 hours away from home and yet my timeline showed me saying I stayed all day and night where my Home location is. Map guidance still worked, but it still showed me that my "current location" was still being at home.
Bluetooth Power indicator pop up: This is a recent issue I found that other Samsung users in other forums encountered as well. I have a Sony WI-1000x Bluetooth neckband that does extremely well for all the bells and whistles it does. I've noticed that after I factory reset again after experiencing the previous 2 issues to get them fixed, there is a pop up that keeps appearing every 10 or so seconds that tell me my headset is battery at 100%. I have found no way of disabling that, and I had to unpair/pair my headset as well as clear Bluetooth data in System App settings to try and get rid of it. Good thing it hasn't been doing that after several tries, but now there is another issue with BT.
Bluetooth notification sound output: I've noticed when my BT is connected, I don't hear notifications from my text messaging app, e-mail, Arlo, and social media apps. I've checked to see that my Sound settings are all up and running as it should be. Then I went to try and play a notification sound, and nothing came out of my phone speakers. It only played through the headset itself, and that's an annoyance as I don't wear them all the time in my ear unless I'm using it for phone calls or listening to media. It seems to be an Android Pie issue and I have yet to find a permanent solution as this wasn't an issue before on Oreo. The only workaround I've found is using the SmartThings Audio Output toolbar in the Notifications drop down and select to play Media from my device. The notification sounds work then, and I can still answer calls through my headset. But it's a dumb issue that I have to manually set this whenever I want to go back to listening media.
The Note 9 is a great phone despite the small shortcomings it had before the Pie update. Now it's after the Pie update, all these issues come up and I don't understand what happened in what Samsung did. I'm almost tempted in calling Samsung to ask if my phone just somehow became defective, but I don't want to have something done and they send me some refurbished model when I kept my phone in near mint condition. What are your guys' thoughts about the issues I've had and what solutions would you suggest?
Click to expand...
Click to collapse
I had issues with android pie sprint model. Ended up flashing android oreo back and no more issues. Theirs guides out their all u need to do is download the correct files and flash file ,real easy process just follow instructions. Do your research and ull be good
GigaSPX said:
...
I have the 960U1 US Unlocked version of the Note 9...
The Note 9 is a great phone despite the small shortcomings it had before the Pie update...
What are your guys' thoughts about the issues I've had and what solutions would you suggest?
Click to expand...
Click to collapse
timex300 said:
I had issues with android pie sprint model. Ended up flashing android oreo back and no more issues. Theirs guides out their all u need to do is download the correct files and flash file ,real easy process just follow instructions. Do your research and ull be good
Click to expand...
Click to collapse
Hey GigaSPX, noting you have a 960U1 US Unlocked, I've been working on this step-by-step for a 960U1:
Confirm These Steps to Downgrade US Unlocked SM-N960U1 from Pie to Oreo
If you decide to go this route, take a look and share your experience.
Thanks for the links and guide tips to downgrade to Oreo, but I enjoy One UI too much to give up on that user experience. I still have my Note 8 and I know it benefited significantly from the pie update to have it last all day unlike before on Oreo.
GigaSPX said:
Thanks for the links and guide tips to downgrade to Oreo, but I enjoy One UI too much to give up on that user experience. I still have my Note 8 and I know it benefited significantly from the pie update to have it last all day unlike before on Oreo.
Click to expand...
Click to collapse
You're welcome.
Good to know about your Pie experience on your Note 8.
So here's a wierd one. Have a SM-N960U1 on Android 9. Everything's been fine but as of last Friday every time it pairs with a Bluetooth device (headphones, car, etc.) it starts calling itself? I re-paired all devices, turned BT off and back on, restarted phone, etc., but this behavior persists. Music is also terrible during this time, but realized by accident when I press Device Care widget to optimize phone the BT device announces 'Call Ending', and music again sounds great. However there's no record of any outgoing call in Phone App. I didn't realize what # was being called until I got in my car and saw it was dialing itself, but again, this phantom call does not show up in Recent Calls history? Any ideas?
Ugh... Same
Same man. Just letting you know you're not alone and following for a resolution.
smart lock on?
Removed all trusted devices from smart lock and it still happened.
Did a support Chat with Samsung, they recommended a soft reset (Vol dn + Power, similar to a Battery pull) which solved it temporarily when I turned on Bluetooth but since then the bug continues. No new updates or setup changes I'm aware of before this started happening. They also suggested running in safe mode and disabling Apps one at a time to see if the issue can be isolated (aren't these supposed to 'be' smartphones? Evidently there's no log of what it's doing) Will try that or another Chat session when I get some time again.
Ive been having this issue for a week or so as well. Every time I get in my car, I have to end the call. Its got to be a software update that caused the issue.
I'm thinking now it could be related to Bixby. I don't use it (remapped to google assistant & flashlight on long press using bxActions) but I recall I allowed it to update recently in case it gets better in the future.
Same issue here ... Sprint Note 9 on Pie ... Bluetooth headphones even has issues. I have to make a phone call and end it to be able to control volume from the headset (changing it from in-call audio to media audio).
Yup, those are the symptoms. Bluetooth headphones sound terrible and has no device control until the 'phantom' call that starts on it's own is manually ended.
I had this same problem and finally narrowed it down to a single app. In my case, it was the RC Phone (Ring Central) app. Upon contacting the vendor, they confirmed it was a known issue with a recent update.
With it uninstalled I have no issues.
Good luck
ogretech said:
I had this same problem and finally narrowed it down to a single app. In my case, it was the RC Phone (Ring Central) app. Upon contacting the vendor, they confirmed it was a known issue with a recent update.
With it uninstalled I have no issues.
Good luck
Click to expand...
Click to collapse
Awesome tip!
I use Ring Central App for keeping up with work phone messages. A few days ago started the phone in safe mode and had no BT issue, then back in 'un-safe' mode at first it didn't happen but cycling the headphones on and off it did occur again so I was faced with narrowing it down to which App. After reading your post I went into RC Phone settings, Mobile App Settings, Default Launching, and turned off 'Call From Android Dialer' since I don't use that feature and so far no issue!
Thanks for the tip, hopefully this setting change continues to solve this.
Still good after a couple days and weekly auto phone restart (Sat @ 3:00 AM). So nice not to have to end a phantom call that interrupts the stereo after 10 seconds every time I start the car.
Thanks again for the RC Phone tip.
You guys are definitely not alone. I unfortunately do not use the ring central app so I am not sure what is causing it for me...
I'm on the note 10 and have only had this problem pop up recently out of nowhere... I have no idea what could be my problem as I do not have RC Phone installed on my phone
Possible Solution
Hey, I posted a few days ago about having this same problem and not being a user of ring central. I got to thinking and tested this out. The Voxer app was the issue for me. I uninstalled this app and I haven't had any problems since. I am not sure about why the most recent Voxer update caused my phone to start doing this but I hope this helps someone else.
Possible Solution
Some may have tried this. Let me know.
My wife has Honda Hands Free 2016. In the past 30 days it started this same freaky behavior as all of you list.
She has a Samsung s9+.
She also has had Voxer installed on her phone and has had for many years. I will have to check to see if a recent update hit.
But, this is what seems to work for me at this point........
Told Honda Hands Free to completely forget her s9+. Then disabled blue tooth on the s9+.
Turn Entire Honda car off.
Turn Honda back on, told it to connect to my Samsung phone SM-J320A. Verified Honda was connecting properly to my SM-320A with no issues. All good with no freaky behavior. As info Voxer is not installed on my SM-320A.
Turned bluetooth back on s9+ then added the Samsung s9+ back to Honda Hands Free and told it to completely forget my SM-320A.
So far this has stopped the freaky behavior. If it comes back I will update here and then I will try uninstalling Voxer.