I had to send in my phone for repair (likely will take a good while since it's the holidays and all) so in the mean time I'm using an old phone but having major pains trying to get these two to work together. I get the FastConnect prompts from the PW app, though it always fails immediately after PIN confirmation, and the watch just mindlessly does that "circle going around the rectangle" searching animation, and the overlay on the phone says it failed to connect, and offers me the option to "open app." As long as the watch animation is going, the PIN codes on my phone just repeat, never going anywhere, so trying again just fails anyway due to "incorrect PIN" as they don't even display on the watch at that point.
Eventually, after maybe 5-10 mins, the watch gives up, says it "can't pair with devices," and presents only the option to "reconnect," which forces a reboot and the process to start anew once more.
I've attempted to pair it with the Bluetooth settings instead, only for it to fail there, as well.
ONE TIME I somehow got it to pair, then when I made it to the step to set up Assistant, it failed twice to do so before I opted to skip that, but it DID finish and I got to the main PW app menu. Unfortunately, I was distracted by something after messing with the Pixel Watch app on the phone, only to look back and see it was "disconnected" and my watch said it had "failed to connect," and now I'm back at square one, with a pretty paperweight strapped to my wrist. I'd like to be able to track my sleep and heart rate for the time being until my phone is repaired. Any suggestions?
Have you reset the watch to factory settings? I can only pair a watch with a fresh reset of the sotfware, I get the offer to connect and link without the reset but it always fails, and I had to remove the watch from the fitbit app as well.
Multiple times.
Related
I've been trying to get my MDA Compact III working with my built-in car bluetooth hands-free system (Land Rover Freelander 2) for the last 3 weeks or so with varying degrees of success, but I think I've messed something up...
Until the weekend, I could enter the PIN my car generated into the phone and it would spend several seconds trying to pair; sometimes it would, sometimes it wouldn't, but it would always take several seconds to make the effort. However, now as soon as the car generates the PIN, it goes straight to "failed to connect", the phone doesn't even give the chance to enter the PIN and shows no indication that anything's tried to connect to it.
Is there anyway I can "flush" my bluetooth settings without a hard reset? I wasn't doing any registry tweaks, the only thing I think I did before it went wrong was selected the "set as hands free" on the list of connected BT devices on the phone.
Any help greatly appreciated!
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.
Hi
Just got my ZenWatch and I paired it with my phone. And charged it to full 100%.
At this time the watch asked to do an update, and I said yes.
But now the watch starts and only gets to swirling color dots and no further.
I am new to the watch, and the ASUS e-manual always refers to something on the watch. But I can not access anything.
What can i do to enter recovery mod or do a factory reset or something else?
Just wants it to work again or at least ask for a BT connection to connect and get the latest version of Android wear from ASUS.
A bit desperate here
I've been having an issue since at least January. I was hoping either the Feb or March update would fix it, but it hasn't. My Pixel 2 XL has been acting strangely, but only when driving. When I drive, the device will either soft boot (states that PIN is required after restart, but opening terminal and checking uptime shows it hasn't physically booted) or soft lock (black screen that won't come on until hard booted). When it happens, my music will stop and my car's screen will go black. After a period of time, it'll ask me to reconnect the phone, either due to the device being encrypted until the PIN is entered after the soft boot or because it's simple no longer responding in the case of a soft lock. I've tried:
Removing the bluetooth connection for the car
Removing all known cars from Android Auto
Clearing cache
Uninstalling a few driving-specific apps
I was hoping maybe someone had an idea of anything to try besides a factory reset. I really hate reconfiguring my device from scratch (or even from TiBu backups).
I ended up trying multiple different kernels (Elixir and Evira) with the same results, so I broke down and did a factory reset. I reloaded apps and data from Titanium Backup. I'm no longer having the soft boot issue, but a different one instead. Now, randomly, my phone seems to disconnect from Bluetooth, audio it was playing plays through the phone speaker, and my car's display blanks out. I noticed my watch also shows that it has been disconnected from my phone. After a few moments, Android Auto returns to my car's display, but upon selecting anything (for instance, the music I had been listening to), it shows that the device is not compatible.
If I check the phone at this point, every app that had been running has been stopped. My notification bar is empty, and it usually has a few permanent notifications. The phone hasn't hard or soft booted, as it doesn't request the "PIN after restart". It just killed literally everything that was running. I have set both Android Auto and my music apps to not be battery optimized, as I assumed that might have been a problem, but with no better results. If I unplug and plug back in the USB cable, the phone operates normally. I haven't had any especially long trips to see if the issue occurs a second time. I'm lucky enough that my trips to work take 8-10 minutes.
Has anyone seen this or have any suggestions on things to try?
Well, your first post sounds a little similar to this thread: https://forum.xda-developers.com/pixel-2-xl/help/alert-using-adguard-private-dns-causes-t3896243 , Having tried dns.adguard.com private dns on my phone, that setting also survivied a factory reset. No idea about the second post. Shot in the dark.
cliff6056 said:
Well, your first post sounds a little similar to this thread: https://forum.xda-developers.com/pixel-2-xl/help/alert-using-adguard-private-dns-causes-t3896243 , Having tried dns.adguard.com private dns on my phone, that setting also survivied a factory reset. No idea about the second post. Shot in the dark.
Click to expand...
Click to collapse
It was similar, but I wasn't using Adguard. I had been using 1.1.1.1 for DNS, but when I stumbled on that post, I removed custom DNS settings without success. Thanks for the thought, though!
In all my years with Android, I haven't had such an infuriating issue. It's almost enough to make someone go to *gasp* iPhone! ... Not really.
For what it's worth, while you mention bluetooth audio and your watch disconnecting, of which I don't use either, I did have somewhat similar issues with Android Auto which it sounds like you also used as you mentioned plugging in. Sometimes AA was disconnecting, sometimes the phone not being recognised when plugged in. It's been a year so can't remember all the symptoms, but at the end of the day, it was the charging port that was malfunctioning, and which Google nicely replaced for me. This also caused adb and fastboot to be intermittent, and not see "devices" which also confirmed the charging/data port. Again, just another shot in the dark for you to consider.
Well, I went on vacation a few hundred miles away last week. On the way up, the phone freaked out repeatedly. I had my wife try to disable WiFi. Same issue. I had her try to disable Bluetooth. Same issue. Both disabled. Same issue. While at our resort, the phone freaked out a few times on the drive to breakfast (literally a 2 minute drive).
On the way back, I decided to disable Location services and revoke all Location permissions. I drove 50 miles with no problems. I had my wife enable Location and drove 30 miles. No problem. I had her tick on apps that I felt needed Location permission, one by one, every 10 miles. No problems at all. I ended up with all of the apps that I feel need Location turned on and haven't had a problem since. So something was choking on Location data, but unfortunately, I have no idea what app it was. I think it might have been Action Services, but I can't be sure. I'm just glad it's fixed, frankly.
I know this is an older post, but I wanted to get my "fix" posted, just in case someone else runs across a similar issue. At least they'd have something to try.
This just happened to me for about the fifth time.
1) After workout or other activity, I take the watch off and rinse it in the sink
2) I dry it off with a towel, and when I look at the face again, it says "Resetting..." (ARRRRRGH!!)
Now, I'm sure anyone reading this will guess the first thing I guessed: that somehow, I was holding down the buttons in some fashion while drying the watch off. But since thinking this, i've been very careful about trying not to press any buttons while drying it, and it still happened again recently. I've looked up the method for intentionally factory resetting, and supposedly it's a requirement that the watch is powered off before even starting. I can't imagine I could accidentally perform the exact sequence needed so many times according to those instructions.
I now have the watch automatically backing up every week. So it's not a huge deal to run a restore, but I still have to reconfigure my cards in samsung pay from scratch each time, and the whole process is extremely annoying because it just shouldn't happen.
Anyone else?
Phreaker47 said:
This just happened to me for about the fifth time.
1) After workout or other activity, I take the watch off and rinse it in the sink
2) I dry it off with a towel, and when I look at the face again, it says "Resetting..." (ARRRRRGH!!)
Now, I'm sure anyone reading this will guess the first thing I guessed: that somehow, I was holding down the buttons in some fashion while drying the watch off. But since thinking this, i've been very careful about trying not to press any buttons while drying it, and it still happened again recently. I've looked up the method for intentionally factory resetting, and supposedly it's a requirement that the watch is powered off before even starting. I can't imagine I could accidentally perform the exact sequence needed so many times according to those instructions.
I now have the watch automatically backing up every week. So it's not a huge deal to run a restore, but I still have to reconfigure my cards in samsung pay from scratch each time, and the whole process is extremely annoying because it just shouldn't happen.
Anyone else?
Click to expand...
Click to collapse
Only thing that I have encountered is that Samsung Pay resets itself sometimes. Has happened to me maybe 4 times in one year. Really embarrassing when I'm out shopping without phone.
Sent from my SM-G975F using Tapatalk
I had my watch factory reset by itself and now I'm with a watch with reactivation lock on.
Yep - mine was same situation - I took it off to rinse off in the sink, but didn't set water lock mode first. The screen locked, and the water running over the screen was interpreted as too many wrong passcode attempts -> self destruct. I was out of town at the time, too.
Freaking. Infuriating.
shmaque said:
Yep - mine was same situation - I took it off to rinse off in the sink, but didn't set water lock mode first. The screen locked, and the water running over the screen was interpreted as too many wrong passcode attempts -> self destruct. I was out of town at the time, too.
Freaking. Infuriating.
Click to expand...
Click to collapse
Now I know why my watch resets for a third time now. So it was the watch interpreting multiple wrong passcode attempts as a security threat thus resetting itself.
Watch self-reset for the second time--no water involved
Thanks for this thread! At least I'm not alone. I was hunting for clues because my Galaxy Watch just factory reset itself again for the second time. No water involved. The first time it happened, I had put it in my pocket while doing something messy, so I guessed that the bezel rotated randomly and caused a string of bad PIN attempts. This time it was on my arm when I discovered it had reset itself again. I can't be certain that I unlocked the watch after I put it on, so m-a-y-b-e I somehow bumped-in too many random PINs. It's possible, but I'm kinda doubtful.
Fortunately my watch backups restored after a few timeouts and repeat attempts. But restoring Samsung Pay was such a pain in the neck the first time that I think I'll give up on it for a while.
I am thinking to leave the PIN lock feature turned off for a while to see of the random reset happens again--to rule our some other defect.
I wish Samsung could handle this better, like hard-locking the watch and requiring us to enter our Samsung password into the phone app to unlock the watch.
Experiencing absolutely the same issue, guys.
I've been using it for a year and during this time it was unintentionally reset to factory defaults about 10 times, and I'm not even sure how that happens. The problem occurs on a lock screen (I use PIN to lock the entire watch, not just Samsung Pay), usually after a series of random screen touches and failed unlocking attempts (power button NOT involved). Most often, in a shower. Not exclusively though, so using water lock mode is not a solution.
I can't reproduce it intentionally, but I've noticed several times how after a series of random touches instead of setting the usual 30 seconds unlocking timeout the watch just displays a notification "Watch will reset", then a spinner with "Resetting..." label and then it reboots itself.
Every time it takes some time to restore it from the latest backup and load all my bank cards back, so it's really annoying and I'd like to know how to avoid that too. In my opinion, timeouts are pretty fine for security since it's completely possible to make bruteforcing a PIN a matter of years with them. Resetting a watch should be possible, but after several confirmations. Doing it after a couple of wrong PINs is too much, the harm is more than benefit.
Just sharing my experience...
Same as post #5
After 1 year and 3 moths of using and washing it (yes, with water and little tiny bit of liquid soap) every often and than, last month it showed the "Resetting" message.
I was really mad
I deduced it was the excessive wrong pin number attempts. I guess I was right :fingers-crossed:
Had it restored and had to activate the credit cards on spay again.
I used to have a problem with turning off the "water protection mode". Never again after a reset before the accidental one, but I stopped using it for sometime.
(just a tip I found here on xda.... if you don't restore, the battery tends to be better. Probably because something on the backup not allowing the watch to "sleep" properly)
For the people with random "Resetting", I suggest doing a "Reset" and do not restore the backup of the watch. I know it sucks, but... it might work