Related
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....
Been use for two days now just one reconnect issues once disconnect from phone it really have hard time to reconnect by itself I must either turn off Bluetooth from phone or restart watch every annoying
Sent from my D6503 using XDA Free mobile app
paullu said:
Been use for two days now just one reconnect issues once disconnect from phone it really have hard time to reconnect by itself I must either turn off Bluetooth from phone or restart watch every annoying
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
Mine disconnects if I go over 50ft from my phone but quickly re-connects when I get back in range. I love the watch!
I have the same problem: mine never reconnects automatically, i always have to turn off bluetooth and turn it back on. Maybe a Nexus 4 (LG) Problem?
paullu said:
Been use for two days now just one reconnect issues once disconnect from phone it really have hard time to reconnect by itself I must either turn off Bluetooth from phone or restart watch every annoying
Sent from my D6503 using XDA Free mobile app
Click to expand...
Click to collapse
mark2k said:
I have the same problem: mine never reconnects automatically, i always have to turn off bluetooth and turn it back on. Maybe a Nexus 4 (LG) Problem?
Click to expand...
Click to collapse
Yes, I have the same problem and it's very annoying. Every time I flash a new rom or update a rom(Vanir LP) to my phone(LG G3), I have the hardest time getting it to reconnect. I always have to reset the watch to get it to connect again.
Mine worked, connected and reconnected flawlessly and quickly the first five days that I owned it. However the last few days, it's disconnected when I wake up and I have a hard time reconnecting. Now the watch says that it's connected to the phone, but the phone (Android Wear App) can't see the watch. Very weird. I've reset the watch three times. I've un-paired and re-paired the devices in bluetooth. I've cleared cache and cleared stored data and uninstalled Android Wear App, then re-installed it. The Android Wear App just can't find the watch anymore, but the the Watch still shows it's connected. This is maddening.
mark2k said:
I have the same problem: mine never reconnects automatically, i always have to turn off bluetooth and turn it back on. Maybe a Nexus 4 (LG) Problem?
Click to expand...
Click to collapse
FWIW, I don't have any problem with my ZenWatch and Nexus 4. I've had the watch for a few weeks now, and no connection problems with it. I do notice that it doesn't maintain the connection for as large a distance as my old Sony Smartwatch did, but it doesn't have any problem reconnecting. I figure the distance issue is because of the use of Bluetooth v4 instead of v3 with the Sony.
Disconnection to Apple Iphone 5
I have the same problem. Does not reconnect. I've tried everything. The only way to reconnect is to unpair the watch which resets the watch to factory default and establish a new connection to the watch.
After software update cannot answer calls etc.
Functionality wise not very good especially to iphone.
Good looking watch though.
I have problem with reconnection of my SW3 to my Note 3 with Android 5.0 when I am away for longer time period.
Maybe this problem is connected with lollipop or newer Android Wear App, because about month ago this was going well.
Strange is that on watch is "no connection" icon and on phone is "connected". So phone is making no atteption to reconnect, even bluetooth on/off does not help, I have to restart my phone.
Any help with this problem?
Factory reset your watch then in the wear app press "Forget Watch" that's what fixed that problem for me.
Hi,
I've had this watch over a year now. Everything was working fine until probably last update or two. Now the watch just turns off randomly even when battery level is high. And sometimes it won't turn on unless its connected to the charging dock. I've tried deleted android wear, clearing cache, unpairing, factory resets, restarts. Nothing has worked, i've tried it close to 10 times now and just another factory reset this morning. Haven't been able to use the watch for like 2 months now. Its just a desk clock now. Please help.
Android Wear version - 1.3.0.2166028
Play Services = 7.8.99
Android OS = 5.1.1
is the watch actually shutting down like when you go into the screen and tell it to shut off or does it just go blank right away?
If the later then I hate to say it but it sounds like something inside the watch is broken. Perhaps a contact or solder point near or on the battery. Hard to say without sending it for service.
SirDigitalKnight said:
is the watch actually shutting down like when you go into the screen and tell it to shut off or does it just go blank right away?
If the later then I hate to say it but it sounds like something inside the watch is broken. Perhaps a contact or solder point near or on the battery. Hard to say without sending it for service.
Click to expand...
Click to collapse
It just goes blank. No notification at all. It's been on for 20 percent now. But I am sure it will turn off again. Maybe it's because it gets hot. I dunno.
bustanut666 said:
Hi,
I've had this watch over a year now. Everything was working fine until probably last update or two. Now the watch just turns off randomly even when battery level is high. And sometimes it won't turn on unless its connected to the charging dock. I've tried deleted android wear, clearing cache, unpairing, factory resets, restarts. Nothing has worked, i've tried it close to 10 times now and just another factory reset this morning. Haven't been able to use the watch for like 2 months now. Its just a desk clock now. Please help.
Android Wear version - 1.3.0.2166028
Play Services = 7.8.99
Android OS = 5.1.1
Click to expand...
Click to collapse
Did the watch suffer any kind of mechanical shock ?
Cst79 said:
Did the watch suffer any kind of mechanical shock ?
Click to expand...
Click to collapse
Not that I know of or anything very severe. I have pumped it on a wall before but that's it. Never dropped or anything. Just seemed like after the updates it when crazy. And I've tried almost every solution I've read on these forums.
So only turned off once yesterday which was good. This morning took it off dock and it didn't pair. Tried turning on/off bluetooth on phone no luck so I restarted watch. Then it says "android is starting". "App 1 of 12". Why does it do this sometimes? Does it alot. And it will not finish the process and boot up the watch unless it is docked. If wearing watch. It just shuts off.
bustanut666 said:
So only turned off once yesterday which was good. This morning took it off dock and it didn't pair. Tried turning on/off bluetooth on phone no luck so I restarted watch. Then it says "android is starting". "App 1 of 12". Why does it do this sometimes? Does it alot. And it will not finish the process and boot up the watch unless it is docked. If wearing watch. It just shuts off.
Click to expand...
Click to collapse
That sounds like it is trying to update or download the apps to the watch... which it sounds like you have 12 installed on your phone.
Have you tried deleting ALL the apps from you phone (only the 12 apps for the moto 360) and then uninstall Android wear and factory reset the moto 360 and then download Android wear to your phone and pair the 360 as a new watch and test it for a while and see how it works?
I have the same issue, watch shuts down while I am jogging and listening to Android Wear music from the watch throught Bluetooth. Watch shuts down around 75-80%. When I start it says: Loading Apps 1 out of 12... then shuts down (I assume its a safeguard mechanism for watch not to start without full battery to ensure all apps load completely).
When I wear the watch normally, it never goes off during the day, issue presents itself only when using Bluetooth headphones (perhaps the heating of BT transmitter forces the watch to malfunction and shut down)
ykazimir said:
I have the same issue, watch shuts down while I am jogging and listening to Android Wear music from the watch throught Bluetooth. Watch shuts down around 75-80%. When I start it says: Loading Apps 1 out of 12... then shuts down (I assume its a safeguard mechanism for watch not to start without full battery to ensure all apps load completely).
When I wear the watch normally, it never goes off during the day, issue presents itself only when using Bluetooth headphones (perhaps the heating of BT transmitter forces the watch to malfunction and shut down)
Click to expand...
Click to collapse
I never connect the bluetooth to listen to music. It just shuts down.
Maybe you are doing something that causes it to overheat. Do you leave it on for prolonged periods of time?
Been having this same issue. The Moto 360 powers off and when I press the power button to turn it back on I see the splash "M" image then it turns off. The only way to get it to stay on is to put it back on the dock and when it turns on it says shows the updating apps screen. Any fixes?
I haven't figured out fix. Because of this I barely use my watch anymore. Sucks.
Sent from my SM-G900V using Tapatalk
yep, haven't used my 360 in 6 months because of this problem. it's a shame really. my warranty went out like a week ago too :/
Same thing has been happening to me as well. Not doing anything on the watch, it just goes into sleep of death and I have to put it back on the charger. Battery level is usually above 60 or 70 %.
Same issue!!!
Guys even I had same issue, my watch will heat up suddenly and turns off. I've to put it in dock to turn it on again. This issue never occurred after stopped using some of the new watch faces which allows dim option. I'm currently using some of the old watch faces which are working fine. May be these new watch faces are not working fine with latest update. Now I don't face any problem and battery life is also great.
Try this solution and let me know.
Watch faces has nothing to do with it. My watch will not fully boot into android wear unless it's on the dock no matter which watch face I am using. Even the minimal face.
Sent from my SM-G900V using Tapatalk
Anybody able to find a fix? This is so annoying
I'm having the same problem. I purchased a used Moto 360 off eBay for $120 and it turns off randomly even when the battery is pretty high for example it just turned off randomly at 80%. Then when I try to turn it on it boots up till the M logo or sometimes to the colorful part but then turns off again. It also only turns back on by putting it on the charging dock. Also it shows the Installing App 1 of 1 at startup and then suddenly shuts down again. I am extremely annoyed and frustrated because of this as I spend $120 on this watch and now I get this which makes it unusable and a waste of money. Please tell me guys if any of you find a solution!
Unfortuanately, mine is doing the exact same thing. I thought I had it working again, but as soon as I tried to give GPS permission to Google Fit (wouldn't run without it), it spun there and just went black. I literally just took the watch off the charger, so it isn't that. Now, if I hold the power button or press it multiple times, it tries to boot up, and will stop before it even gets past the normal Android boot animation. Sometimes, it won't even get past the Motorola boot animation. Now, when I put it on the charger, it seems to load perfectly fine, and even gets past the 'Starting apps' phase. Again, once it loads back up, my watch shows +90% battery. I've tried a factory reset, unpair/repair, and still no go.
Found a pattern
My app does the same but i have at least a pattern when it happens. It seems like it is as soon as there has been an update either in Android ware app or in soem app that has an wear application.
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.