A few days ago my S3 developed the most annoying problem. Every time I turn on a bluetooth device I get a notification that says "Bluetooth connection request." Then I have to pull down the notifications, click on the notification and approve the connection. And if I don't do this all within about ten seconds the opportunity to connect disappears and I have to power cycle my BT device.
This is with a paired device that is in the list of known devices, and it has happened with multiple devices.
I've had my S3 for nearly a year and I've never seen this before. And I've never seen it with any previous Android phone. Usually if I turn on a paired device it automatically connects. I have not done anything to my knowledge that would cause this. I am rooted and running completely stock 4.1, I have not upgraded to 4.3 although I'm tempted to upgrade now in hopes that it will clear this up. It is very annoying.
I have searched XDA and Google for a solution to this and there's really nothing out there. What is going on? Please help.
TIA
If I leave my phone on my office desk and walk away, the watch will not pair back to the phone (Samsung S5). I have to reboot the watch to get it to reconnect. Inside the android wear app it shows as "connecting" and even if I hit the icon to stop and restart the connection process no dice.
TL;dr
I have no issues with random disconnects but when I get out of range it will not reconnect when I am back in range.
I've a note 3 running 4.4.2 rooted stock. No issues here reconnecting.
Have you tried this? https://play.google.com/store/apps/details?id=org.myklos.btautoconnect&hl=en
Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?
Noticed the same with my 360 and Nexus 5. Both on stock latest versions.
Issue with mine is that the Moto360 constantly says Disconnected when trying to connect to my Note4. I click connect, it says connected and then quickly changes to Disconnected.
Been trying to figure it out for 3 days now.
I think I realized that the issue is in reconnecting.
I still don't know why sometimes it disconnects, but disconnecting itself wouldn't be an issue if then it proceeds to reconnect on its own.
But I realized that when I'm at home, I leave my phone by the computer and walk around. If I walk outside of the bluetooth range, then it disconnects. That's fine. But then it should reconnect when I come back into range, and it never does. It says "Connecting" and never reconnects unless I do it manually as I said in the OP.
So I guess the question becomes: why does it get stuck on "connecting" when it's in range and should be connected? Is this a Samsung issue or a Moto360 issue?
I have seen the same issue with my Moto 360 and an original Moto X. It normally reconnects but then once in a while it just won't. The easiest solution I have found is to turn bluetooth off and then on again on my Moto X. That always brings it back, a reboot of the 360 does not.
Well as I said in the OP, if I go into Android Wear, click Disconnect and then click Connect, it works. But there is absolutely no reason why it shouldn't auto-connect. If it disconnects, and I don't notice, the rest of the day I go without notifications until I realize the watch has disconnected. That's not how this should work.
Max_Pain said:
Has anyone else experienced frequent disconnects between the watch and the phone?
It was happening with my modded Note 3, which had a custom kernel so I was thinking it may be that. But now (for 2 weeks) I've been on a stock Note 4, and it keeps happening. Every once in a while, once a day or maybe once every two days, the phone and watch disconnect.
Android Wear says "connecting" but never does unless I click on Disconnect and then click on Connect, at which point it connects immediately.
I had "Find My Phone" installed, which would notify me when I got disconnected, so I thought it may be that. Uninstalled it a few days ago. Still happens. It's not a huge deal, but it's annoying and I don't see why it should happen.
Any idea?
Click to expand...
Click to collapse
Hi, i have the same problem, my watch always disconect to my phone (moto x), and then the bluetooth system never start again. When I enter in setup ---- bluetooth---- the bluetooth switch doesn t turn on again until phone reboot.
this is so annoying. and it seems like there's a few people experiencing the same thing but nobody seems to have hit a solution. I have yet to come up with one. if I do, i'll post on here.
Same happens with mine. It just prompts me with a "connect" screen on my phone once in a while. After connecting 2-3 times, it won't appear until next time I turn off Bluetooth.
I get this problem about 2 times per day...running with a Note 2 running 4.4.2 stock but rooted....
Is there an easy way (other than rebooting the watch) to force the watch to reconnect to the phone?
I find that sometimes I wander away from my desk (where my phone usually stays) and when I return to close proximity to the phone, the ZenWatch never reconnects. The Android Wear app on the phone will just say "trying to reconnect..." forever. Although rebooting the watch will fix this, surely there's a better solution? Is there a watch-app that can force the watch to reconnect?
In the Android wear app, from the 3 dot menu, disconnect then reconnect the watch.
A permanent solution though is to uninstall everything, factory reset the watch and go through the whole setup process again.
Sent from my ASUS_Z00AD using Tapatalk
My sw3 has worked for 6 months. I was having some connectivity issues with two of my apps so decided to do a factory reset and reconnect to force the apps to update. Done this at least twice successfully. But this time I go through the process...
-uninstall AW,
-reset my watch,
-reinstall AW,
-start the watch,
-open AW,
But the pairing code doesn't show on in AW...but it shows on the watch. I can connect in the phone bluetooth menu and get the "paired notification'' then the watch goes to the updating screen followed by 'syncing'. Usually this where I get the 'updating apps 3 of 23' but it just stays on syncing. At the end watch is not connected to my phone no apps are loaded. The phone is never visible in AW. Now if I go in and repair the devices it looks like they are connected but I can't.
I think something is wrong with AW.
update
I think its actually something in my phone... my wife's Samsung Note connects in AW. Why can't my Nexus 6 see the watch.
If you haven't done so already, try restarting the phone immediately after uninstalling Android Wear app on your phone. If that doesn't fix it, you may have to factory reset your phone.
working
tomtecs said:
If you haven't done so already, try restarting the phone immediately after uninstalling Android Wear app on your phone. If that doesn't fix it, you may have to factory reset your phone.
Click to expand...
Click to collapse
Thanks... I think its working... Add one more step to the process.
mrf51 said:
Thanks... I think its working... Add one more step to the process.
Click to expand...
Click to collapse
What have you do to work again? My phone have the same problem...
Thanks.
I have to this every couple months when my phone won't connect with my phone. Some sort of bluetooth issue.
- factory reset watch
- go into android wear and remove the watch
- forget the watch in bluetooth settings
- uninstall android wear
- restart the phone
- install android wear
- restart the phone
- use wear to connect to the phone
Sometimes I have to do this twice and it might take 45 mins to update my apps.
Perfect for me.
The only issue remaining is the unexpected unlinking with the phone, but it isn´t new.
Phone Bq Aquaris E6 4.4.2, watch Sony SWR50 6.0.1.