Database Develop

Disconnected...

OK say I have paired it with a Sony Xperia Z1 compact.
As soon as the screen turns off it loses connection with the phone. It still thinks it's connected (there is no cloud with a line through it on the watch face screen) and when you say ok google it tries to interpret but then I get the screen that says
disconnected and to the right is a little icon of a cloud with a line through it and underneath there are options for built-in functions like "show my steps", show me my heart rate" , etc
If I manually disconnect and reconnect using the Android Wear app on the phone it works again straight away.
Anyone else seeing this behaviour?

I had that problem right at the start. Can't remember how I fixed it
Restart both devices? Uninstall and reinstall wear app on phone? Update to latest watch firmware?

Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app

skitty said:
Do you have stamina activated which us turning your Bluetooth off on screen off?
Sent from my D6503 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hey that could be it. I do have stamina enabled because the battery in my phone is going down rapidly with the watch connected. I'll turn stamina off and see what happens. Cheers!
EDIT: I think this might be fixed now after turning off stamina mode. I'll need to test furtehr thugh. Thanks skitty

I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?

shadeofgrey said:
I'm still getting this quite a bit. Is anyone else still experiencing random bluetooth disconnects? It still thinks that they're connected until I try to do a google now search and then it tells me they're disconnected. I tried uninstalling the wear app on the phone and reinstalling. I also cycled bluetooth and that seems to fix it in the short term. Suggestions?
Click to expand...
Click to collapse
I'm pretty sure, for me, the answer was to disable stamina mode on my xperia phone. I very very rarely see the disconnected message any more.
Cycling BT also used to help for me but all that was doing was temporarily foxing the stamina setting. It always switched itself off again.

I'm having the same issues, here's my post in the general android wear help forum
"So I've searched around a bit and not really found anyone else having this issue... Is it just me or is no one complaining?
The Bluetooth connection shows to be solid on the phone "connected, running sync loop" shows in the notification bar and the little connection lost cloud is not displayed on the watch.
However, notifications will not push and if I try to initiate a voice command it spins for while and then tells me that it is "unable to reach the Google server" turning Bluetooth on and then back off will rectify the issue temporarily. And... To make things more complicated it will randomly happen a lot one day and hardly at all another day ( of course it always acts up when someone starts asking questions about the watch and wants a demo, which in turn makes you look like a gullable early adopting fool.)
I'm currently using a gear live with a nexus 5 running the latest stable build of cm11. Ive also tested with and without WiFi enabled, because I thought I noticed a correlation but there seems to be none.
Is it me? Am I doing something wrong?"
I have also tried running stock faces vs custom with no change
hasn't happened since 9:00 this morning.. today... yesterday I missed almost every notification

disconnect
Not sure if this is related or if anyone can give advice but for me (HTC one max) whenever my Samsung gear live is disconnected from phone...phone randomly restarts all by itself. Tried factory reset, was fine until I set it up again. Made sure android wear was off...just tried turning off Google now see if that helps.... Anyone else experiencing the restarts? Sorry on phone so messy post...

Woah sorry i forgot about this post. My issue was the stock kernal for cm11. When i switched to another kernal, my issue vanished.

I am having the issue where if my phone is asleep I cant do any searches. Now I know or at least I'm pretty sure that its not the watch or the app but something on the phone. Phone is a galaxy note 3 sprint version running temasek's unofficial cm12 rom. The watch is stock of course. When I get a notification the watch will happily wake up and tell me about it, but when I try to tell the watch a command with the phone sleeping is where the problem presents itself. The issue appeared after a few of the rom updates (happens even with a clean install) and I know he's a busy guy (temasek) but I would like to see if anyone here could help me figure it out to be able to provide a solution to others that are having my same issue. Any and all help is appreciated.

Lollipop bluetooth

So my dad is having issues with his Droid turbo. It just updated to lollipop and since then, his bluetooth disconnects every time the screen shuts off. It doesn't matter what he's connected to. As soon as the screen is off, it's as if his bluetooth wasn't even on. He's got a fitness tracker that he has an sync app for and it's supposed to be a background thing. Won't stay paired to his vehicle either. He's toggled bluetooth on and off, un-paired and re-paired and cleared data and cache under the Bluetooth sharing app. Nothing is working.
Anyone gotta fix or experience this as well?

Most likely it is a power saving program that is installed. Check settings in any battery apps you have installed for anything about bluetooth.

Like PittAussie said, he probably has one of those bull**** battery saving programs installed that's doing it.

Bluetooth issue

This problem started last week.
It started when I noticed that my Nexus 6 cannot connect to my car's bluetooth. At first I thought it was the car since the bluetooth icon on my phone is on.
Then I realized that it was my phone, After a restart, it would connect again.
Now most of the time it won't connect automatically, I have to try to toggle the bluetooth on the phone on and off to try to connect. But when I try to toggle it on and off, it would be very slow to toggle or even won't toggle at all.
So now I'm noticing that after the phone is idle/sleep, the bluetooth won't connect. And when I try to turn it off, sometimes it won't turn off. Sometimes it says it's off from the setting but the bluetooth icon is still on top. Sometimes after it's off, it won't turn back on for a couple of minutes. So it would take more than 5 minutes after turning it on.
It was working perfectly before, it's just started last Sunday.
Any help would be helpful . Thanks

psxindo said:
This problem started last week.
It started when I noticed that my Nexus 6 cannot connect to my car's bluetooth. At first I thought it was the car since the bluetooth icon on my phone is on.
Then I realized that it was my phone, After a restart, it would connect again.
Now most of the time it won't connect automatically, I have to try to toggle the bluetooth on the phone on and off to try to connect. But when I try to toggle it on and off, it would be very slow to toggle or even won't toggle at all.
So now I'm noticing that after the phone is idle/sleep, the bluetooth won't connect. And when I try to turn it off, sometimes it won't turn off. Sometimes it says it's off from the setting but the bluetooth icon is still on top. Sometimes after it's off, it won't turn back on for a couple of minutes. So it would take more than 5 minutes after turning it on.
It was working perfectly before, it's just started last Sunday.
Any help would be helpful . Thanks
Click to expand...
Click to collapse
I have the exact same issue. I have a Nexus 6 (Verizon) and a 2011 Ford Sync. No problem at all before the recent update.

psxindo said:
This problem started last week.
It started when I noticed that my Nexus 6 cannot connect to my car's bluetooth. At first I thought it was the car since the bluetooth icon on my phone is on.
Then I realized that it was my phone, After a restart, it would connect again.
Now most of the time it won't connect automatically, I have to try to toggle the bluetooth on the phone on and off to try to connect. But when I try to toggle it on and off, it would be very slow to toggle or even won't toggle at all.
So now I'm noticing that after the phone is idle/sleep, the bluetooth won't connect. And when I try to turn it off, sometimes it won't turn off. Sometimes it says it's off from the setting but the bluetooth icon is still on top. Sometimes after it's off, it won't turn back on for a couple of minutes. So it would take more than 5 minutes after turning it on.
It was working perfectly before, it's just started last Sunday.
Any help would be helpful . Thanks
Click to expand...
Click to collapse
dasCoder said:
I have the exact same issue. I have a Nexus 6 (Verizon) and a 2011 Ford Sync. No problem at all before the recent update.
Click to expand...
Click to collapse
+1
Same exact issue as above. My Nexus 6 will not auto connect via bluetooth to my Pioneer 8500BHS unless I reset the phone. It was working fine until last week. When this is happening I can turn bluetooth off, but then it will not come back on unless I reset.

+1
My phone has exactly the same issue

DigitalPerson said:
+1
My phone has exactly the same issue
Click to expand...
Click to collapse
+1 Same here....
Approximately it started in this month.... every 1-2 days my bluetooth is stopping to work. And the only way to restore it - reboot!

Well, can't speak for everyone, but a simple cache clear with twrp fixed my bluetooth issues

A2CKilla said:
Well, can't speak for everyone, but a simple cache clear with twrp fixed my bluetooth issues
Click to expand...
Click to collapse
I had the same problem since the latest Android update. I cleared the cache and data in the Bluetooth Share app in: Settings/Apps/All/Bluetooth Share
After a restart, no more bluetooth connection problems.

Yes, clearing cache seems to be working...
Thanks

Wiping cache and dalvik fixes most anything that is not an actual code bug. Should be first step in any attempt to troubleshoot.

psxindo said:
Yes, clearing cache seems to be working...
Click to expand...
Click to collapse
The same here! It helped!

vagifzeynalov said:
The same here! It helped!
Click to expand...
Click to collapse
Hahaa. Anytime your device changes on it's own something is locked in logic. Same as on PC need to at least reboot. Clearing your dalvik/art/cache unlocks whatever is hung up as it has to reload from scratch.

vagifzeynalov said:
The same here! It helped!
Click to expand...
Click to collapse
Clearing the cache worked for me as well. Thanks.

Losing Bluetooth Connection

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.

Bluetooth keeps turning off

I upgraded my Z3C to MM a few months ago, and since then I've started noticing that bluetooth seems to be off most of the time. Under KK it was on all the time and rock solid - it was always there, and for example the phone would always connect to my car when I started the engine. Now, BT on the phone is off more often than on, which is tedious, especially when I don't notice that the phone doesn't connect to the car, and then a call comes in
I've verified that BT doesn't come back on after a manual restart, which it always used to. The phone always restarts after running its Titanium backup overnight, so that could be why BT is more usually off than on. But as I say, it didn't used to be like that. I will be keeping a closer eye on it in future to see if BT turns off at other times for no apparent reason.
Does anyone know if there is a new setting in MM that could be causing this, or have any other suggestions as to how to go about preventing this extremely annoying behaviour?
TIA

OK, so it now seems to be confirmed that Bluetooth doesn't come back after a restart. The question is: why? It never used to behave that way. I'm pretty sure now that it's since I upgraded to Marshmallow that it's being doing this.
I'd dearly love to find a way to fix this!

Update on this problem: around the turn of the month it went away - bluetooth came back on after a reboot just like it had always used to. No idea why, or what if anything caused the change. Most likely a app somewhere was my guess, since that's all that changes on the device these days.
However, after a week or two the problem came back. Again, I'd changed nothing apart from allowing apps to update.
In order to investigate the app hypothesis further, I tried restarting the phone in safe mode. No joy. Normal mode, bluetooth on; restart in safe mode: bluetooth doesn't come back on. Safe mode, bluetooth on; restart in safe mode: bluetooth doesn't come back on.
So it looks like it's not an app after all.
I have now found a workaround using the Smart Connect app to schedule a task which turns bluetooth on in the early hours of the morning. But it's annoying that I have to do this when the problem simply shouldn't be happening.

Bluetooth is a ***** on MM
Try the following: Switch BT on - Be sure that it can connect to any device. Leave it on - Do not switrch BT off now.
Reboot and wait until system full stated.
Now it should work stable - even if you switch it on/off.
After that: Be sure that you have BT ON before reboot.