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.
My 360 has been working flawlessly since I got it 3 weeks ago. I just flashed a new ROM and now it won't connect. It won't show up on my Android Wear app even though Bluetooth is on. Do I have to factory reset my 360 every time I flash a new ROM?
Hello All! been having some difficulty with my Moto 360. Recently flashed a new CM13 nightly to my Verizon LG G3 and lost bluetooth pairings no big deal will just reset the watch. The watch no matter of battery level or if still docked on the charger will not unpair and factory reset. When off the charger it will make an attempt and turn off. On the charger it will attempt reboot and give me an error that android wear isn't responding i believe.
I have tried restoring bluetooth pairing through tibu on the phone in hopes of getting the watch back but it hasn't worked. The last thing i have not tried is going back to a older build and then trying to restore bluetooth pairings in hopes of getting the watch to be recognized.
I realize the bootloader is currently not unlockable on MM but is there a way to enter stock recovery and reset the watch or some other method i don't know of. I would like to avoid having to send the watch in for service.
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.
My pixel 3 xl will connect to Android auto via USB.... Work for a few minutes then randomly disconnect. Never happened with my pixel 2.
Any suggestions??...I have tried new USB cable.... Still does same thing.
Sent from my Pixel 3 XL using Tapatalk
I have had occassional issues with Android Auto as well -
When I first got the Pixel XL I was able to connect fine via USB and even wirelessly to my Kenwood headunit - but the other day, after connecting to Android Auto, when I tried to make a phone call, Blue Tooth was not connected and I could not get it to connect. I eventualy toggled on and off Airplane Mode - and after that
it connected fine. Havn't had an issue since (knock on wood)
for your situation, have you made sure that USB Debugging i turned off? It won't work with that turned on....
Same problem here.
Never had an issue with my Pixel XL, Pixel 2 or Pixel 2 XL. Yesterday I received my new Pixel 3 XL and Android Auto keeps disconnecting. Sometimes it does last a few minutes, sometimes it does so after a few seconds. It doesn't matter if an app like Spotify or Maps is being started or if I just connect the cable. Android Auto doesn't stop on the phone but only disconnects.
As you can't deinstall Android Auto I already tried wiping cache, wiping data and deactivate. I even tried three different cables.
When I connect my work phone Pixel 2 I don't see this problem. The connection is kept as usual.
I'm getting grey hair over this.
Has anyone found a solution or workaround for this issue?
I've tried absolutely everything, even rolled back to a nano SIM after started with an eSIM.
Gonna RMA this week and cross my fingers.
I wonder if it's a hardware issue or software. Unfortunately I don't have another phone that runs pie so I can't test it. My v30 running nougat works fine. I'm kinda waiting for the next pixel update to see if it fixes it.
If you do rma your phone let us know if that fixes the issue.
Turn off adaptive battery and see if that helps you
Nope, that doesn't help. As I mentioned I have every previous Pixel and all of them work flawlessly with my head unit. All preferences are the same.
There's only one obvious difference: Android Auto is pre-installed on the 3 XL.
Unfortunately I don't know anybody with Android Auto in the car nor owning a Pixel 3 XL to check out if it's something with my head unit.
In a German forum 2 people say they have it working properly...
One of the most frustrating parts is that - for me - it sometimes it works 10 minutes. After I switched back to nano SIM yesterday on my drive home I connected, listened to great music, whatsapped my wife that it is working and boom...disconnect and from then on the known behavior started again.
Did the new rma device fix the issue?
Just send it today and because I bought from provider I've a couple of days for the new one. Used my good ol' Pixel XL today working like a charme...
I'll update when the replacement has arrived.
Experiencing same issue with Pixel 3 non-xl and 2016 Honda Accord. Android Auto disconnects anywhere from 20 minutes to just seconds after I've connected.
I've tried the following:
-Variety of brands of USB-C > A cables
-Disabling all power saving options (whole phone, specific apps)
-Setting screen to stay on when charging (solved AA disconnect issues on my LG V20)
-Re-pairing bluetooth with car
-Re-pairing AA with car
-Resetting car head unit
-Resetting phone
I've had no issues with disconnects, but I use wireless connection with Pioneer headunit.
I got my replacement today and for now the problem looks to be solved but I only sat 20 minutes in the garage messing around with it but that are 19:50 more than my last attempt with the old one.
But I already installed both Android Auto app updates that came in the last couple of days.
/me is crossing his fingers
I'll drive about one hour in the evening and hope everything stays how it is now
It's a pixel 3 software issue. Big thread in the Android Auto support forums. Google doesn't seem to be in a hurry to fix it. Said the November update should, it did not.
Anyone ever find a fix for this? I'm having the same issue, but now cannot connect at all. (Was working. Stopped the car, went into Starbucks, came out and AA won't connect.) My Pixel 2 XL works fine, but I want to sell it.
Like I said I RMAd it and it works flawlessly ever since.
Android Auto Closing Out on Pixel 3
Did anyone find a fix for this? I'm having same problem with a new Pixel 3 (not XL). It will project to the car screen/monitor temporarily, but then disconnect and close out of Android Auto. Sometimes it will automatically switch back in a few seconds. Other times I need to disconnect the USB cable from the car and reconnect to get it to project the screen again. It closes out Bluetooth and stops playing from the phone too. This seems to be an issue with the phone, as I've had this problem in multiple cars. My only solution is to run AA on the phone and not project it. Is Google doing anything about this?
Wahoodean said:
Did anyone find a fix for this? I'm having same problem with a new Pixel 3 (not XL). It will project to the car screen/monitor temporarily, but then disconnect and close out of Android Auto. Sometimes it will automatically switch back in a few seconds. Other times I need to disconnect the USB cable from the car and reconnect to get it to project the screen again. It closes out Bluetooth and stops playing from the phone too. This seems to be an issue with the phone, as I've had this problem in multiple cars. My only solution is to run AA on the phone and not project it. Is Google doing anything about this?
Click to expand...
Click to collapse
My phone connects fine to AA. It stays connected with the cable. Perhaps try a new cable to connect it. I'm on stock rooted.
Sent from my Pixel 3 XL