Related
I installed a new ROM on my Note 3 and in order to re-pair it with the phone I reset Moto 360 and now I cannot get it paired again. In the Android Wear app it just shows as "Connecting" but I was able to pair it via Bluetooth settings. Now it is just stuck at a " Just a minute" with a circle going around. Before I started the pairing process Moto 360 was at 84% battery, so not sure if it's a battery issue.
With that said, is there any other way to pair the watch other then resetting to stock?
ajamils said:
I installed a new ROM on my Note 3 and in order to re-pair it with the phone I reset Moto 360 and now I cannot get it paired again. In the Android Wear app it just shows as "Connecting" but I was able to pair it via Bluetooth settings. Now it is just stuck at a " Just a minute" with a circle going around. Before I started the pairing process Moto 360 was at 84% battery, so not sure if it's a battery issue.
With that said, is there any other way to pair the watch other then resetting to stock?
Click to expand...
Click to collapse
You may have to reset the watch a few times, I saw someone else having an issue with getting it to connect before resetting it three times.
TheJesus said:
You may have to reset the watch a few times, I saw someone else having an issue with getting it to connect before resetting it three times.
Click to expand...
Click to collapse
Thanks, I got it working after resetting it few times.
Scribbled on Note 3.
Good christ mine has been a PitA to get up and running. The original update kept failing on me despite the fact it was charged to 100%.
Now, Ive reset it multiple times after the update, but i keep getting stuck on "connecting" on the phone and "just a minute" on the watch. This is after the pair code in the app and everything.
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....
Hey guys, so over the weekend, my watch suddenly said "Offline" when I try to send s text through Ok Google. I've restarted both my watch and phone, reset my watch, reinstalled all android wear apps on my phone, turned Google Cards on and off on my phone, and location as well. Nothing has worked and I tried Googling it but I still didn't get any results. The watch is connected to my T-Mobile GS6 Edge. Does anyone have any ideas? Thanks.
idksomuch said:
Hey guys, so over the weekend, my watch suddenly said "Offline" when I try to send s text through Ok Google. I've restarted both my watch and phone, reset my watch, reinstalled all android wear apps on my phone, turned Google Cards on and off on my phone, and location as well. Nothing has worked and I tried Googling it but I still didn't get any results. The watch is connected to my T-Mobile GS6 Edge. Does anyone have any ideas? Thanks.
Click to expand...
Click to collapse
I get the same thing occasionally, but usually a restart of the watch fixes it.
I can usually tell when it's going to happen cos the "OK Google" text re-appears on the watch face when it turns on.
idksomuch said:
Hey guys, so over the weekend, my watch suddenly said "Offline" when I try to send s text through Ok Google. I've restarted both my watch and phone, reset my watch, reinstalled all android wear apps on my phone, turned Google Cards on and off on my phone, and location as well. Nothing has worked and I tried Googling it but I still didn't get any results. The watch is connected to my T-Mobile GS6 Edge. Does anyone have any ideas? Thanks.
Click to expand...
Click to collapse
I have been seeing the same thing happen on mines which I purchased yesterday. Really annoying especially when it just hangs showing the little circle doing nothing.
It happens when you have no data connection on the phone. I use a data management app for battery life extension which turns off data or wifi when the screen is off and turns it on every 15 mins., my moto is disconnected tillI wake up the phone.
TLR - Make sure data is working on your phone.
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.
I purchased a sont smartwatch 3 about a month ago and when I first got it and charged it up, it paired right away to my phone. Over the course of a few weeks I would notice there would be times when it would not connect to my phone. Turning bluetooth off and back on would fix this. I got tired of doing that so I unpaired the watch and deleted all android wear from my phone to start fresh. The watch would not connect. I have now been trying for a few weeks to get it working again. I'll list everything I have tried below ( not in order but as I think of them).Hoping for a new idea on this I haven't found:
- clear play services and play services framework cache
- in adb shell :adb shell am start -a android.bluetooth.adapter.action.REQUEST_ENABLE
- factory reset on watch
- forget all bluetooth devices on phone
- rooted watch and tried 6.0.1 rom
- hold power button till watch restarts 3 times
- locked and unlocked bootloader
- xperia connect software repair
Is there a bluetooth testing method anyone is aware of or a way to check my bluetooth integrity ? Maybe flash a bluetooth module ?
wich phone ? I have BT issue with my xperia Z5C : SW2, SW3, Zenwatch2....
non rooted nexus 5
It's working ! This makes no sense how though. I let the watch sit for days after my last attempt to pair it. Used Sony companion to return it to stock. Today I decided to try again. It was dead and had been for a week or so. I connected it to my computer via usb and I turned it on after letting it charge for about 5 mins. On my laptop I decided to check what bluetooth devices my computer could see. My smartwacth shows up in this list. I wish there was a camera on my face, it would've been priceless. I grab my phone and reinstall android wear. It finally shows in the app. I have been trying to fix this for weeks now and it just randomly works now. Maybe this may give something new steps to try for those that run into this issue.
2gttalon said:
It's working ! This makes no sense how though. I let the watch sit for days after my last attempt to pair it. Used Sony companion to return it to stock. Today I decided to try again. It was dead and had been for a week or so. I connected it to my computer via usb and I turned it on after letting it charge for about 5 mins. On my laptop I decided to check what bluetooth devices my computer could see. My smartwacth shows up in this list. I wish there was a camera on my face, it would've been priceless. I grab my phone and reinstall android wear. It finally shows in the app. I have been trying to fix this for weeks now and it just randomly works now. Maybe this may give something new steps to try for those that run into this issue.
Click to expand...
Click to collapse
my sony smart watch 3 5.1.1 dont pair with my galaxy A8 6.0.1 via bluetooth i tried every way please help me... thanx
Same Issue
2gttalon said:
It's working ! This makes no sense how though. I let the watch sit for days after my last attempt to pair it. Used Sony companion to return it to stock. Today I decided to try again. It was dead and had been for a week or so. I connected it to my computer via usb and I turned it on after letting it charge for about 5 mins. On my laptop I decided to check what bluetooth devices my computer could see. My smartwacth shows up in this list. I wish there was a camera on my face, it would've been priceless. I grab my phone and reinstall android wear. It finally shows in the app. I have been trying to fix this for weeks now and it just randomly works now. Maybe this may give something new steps to try for those that run into this issue.
Click to expand...
Click to collapse
My SW3 won't pair with my phone (OP2), i try all the optiosn you say
I try other phones too
BeStMaker said:
My SW3 won't pair with my phone (OP2), i try all the optiosn you say
I try other phones too
Click to expand...
Click to collapse
I dont think the fault lies with the watch and phone but more so with Google play services as this is needed to run and connect android wear as far as I know. Try uninstalling play services and reinstalling on the phone. If that doesnt help then try resetting the watch in pc companion. If this doesbt help then im unsure but I could only blame gplay services as all my android wear issues have been with this such as apps like watchmaker deleting itself off the watch after rebooting my phone (xperia Z2 rooted custom rom). I even tried factory resetting both but the issue still persisted so I gave up with it and decided to manually resync apps after every reboot.
You can try resetting your devices but I cant garentee this will solve your issues.
RJASSI21 said:
I dont think the fault lies with the watch and phone but more so with Google play services as this is needed to run and connect android wear as far as I know. Try uninstalling play services and reinstalling on the phone. If that doesnt help then try resetting the watch in pc companion. If this doesbt help then im unsure but I could only blame gplay services as all my android wear issues have been with this such as apps like watchmaker deleting itself off the watch after rebooting my phone (xperia Z2 rooted custom rom). I even tried factory resetting both but the issue still persisted so I gave up with it and decided to manually resync apps after every reboot.
You can try resetting your devices but I cant garentee this will solve your issues.
Click to expand...
Click to collapse
RJASSI21 Many thanks! i clear the google play services data and now all is working fine.
Thanks!
I have this problem occasionally with my LG G4. It works fine then all of a sudden it won't connect to the phone. Shows up in Bluetooth devices, but not in Android wear. Only way I find to sort the problem out is to unpair the watch from the phone which then activates a factory reset. Once done all is good again........well for a few weeks or so.
I let the clock DIE (battery) and then work for 2 weeks, now the same problem.