I recently purchased a Redmi Note 8, and have owned a Samsung Gear S3 watch from before, fully functioning. However after making the switch and resetting my watch and trying to pair it with my phone through bluetooth, a few moments in each time, a consistent error popped up: 'Connection Failed, try again'
All plugins and apps have been installed, the watch has been reset, the watch shows up and stays on the bluetooth list just fine, however the issue arises when I try to pair the two. Can anyone help me out? I use this watch a lot and I need it to work with this.
floopydisk said:
I recently purchased a Redmi Note 8, and have owned a Samsung Gear S3 watch from before, fully functioning. However after making the switch and resetting my watch and trying to pair it with my phone through bluetooth, a few moments in each time, a consistent error popped up: 'Connection Failed, try again'
All plugins and apps have been installed, the watch has been reset, the watch shows up and stays on the bluetooth list just fine, however the issue arises when I try to pair the two. Can anyone help me out? I use this watch a lot and I need it to work with this.
Click to expand...
Click to collapse
Same problem. It is the ReNo8 problem. I use the galaxy watch and never can pair. No issues on A20 or Realme C2 which I tested on. Seems no solution so far so will most likely sell this phone
i am trying to connect a Samsung S3 frontier to a Xiaomi Redmi note 8T , but i can't. Same problem as above. Any ideas?
Related
I've updated to the new Connect app, and the app on the phone works fine, but none of the new features will sync to the watch. I've tried restarting the watch, resetting the watch, uninstalling and reinstalling both Android Wear and the update to the Connect app (on a Moto X, so I can't fully uninstall Connect).
Anybody seeing this? Maybe I need to do all that in a particular order?
I am having the exact same issue. Using a Moto X 2014. The app updated and works on thr phone but none of the new features will sync
In the same boat as well...
Same with me. Running lg g3. I've read the issue is the phone that your 360 is connected with. Some people paired their 360 with a different phone and then the new watch faces finally appeared. But once they would try to pair their 360 back to their current phone, the watch faces would still not show.
No problem here on my Nexus 5
you won't see anything different on the phone after the motorola connect update in terms of the Body app. However, if you go into the start menu on the watch itself, you should see moto body features such as calories, steps, heart activity, and heart rate. hope this is helpful.
Won't work on my S4 either, tried everything. Bummer!!!
Works fine with my s4. Try restarting phone?
ditto
Same issue on my moto x 2013. Can't do anything to get them to show up. Done everything short of a hard reset on the phone
same here, nexus 5 on lollipop
I had the same problem. I use it with my Nexus 5 running an AOSP Lollipop Build.
Solved it by uninstalling the Motorola Connect App and reinstalling. After that everything new appeared on the 360.
Hope this helps :good:
mc-paulo said:
I had the same problem. I use it with my Nexus 5 running an AOSP Lollipop Build.
Solved it by uninstalling the Motorola Connect App and reinstalling. After that everything new appeared on the 360.
Hope this helps :good:
Click to expand...
Click to collapse
Many thanks this worked for me. I was dreading having to do a factory reset.
Edbogue
I previously had a Galaxy S6 Edge with the first generation Gear VR headset. Everything worked fine.
I got a new Galaxy Note 7 and decided to pick up the 2nd generation Gear VR headset to try it out. The phone clips in and installs all of the required Oculus apps as expected. Once that is done, I plug back in and get into the virtual lobby. Every time I try to install an app, the app downloads and then instead of saying 'installing', the download button reappears. The headset works fine. I can navigate around and look at different menus, but am unable to install any apps.
I have tried the following:
- Tried to install multiple apps - All have the same issue of not installing
- I factory reset my phone and set everything up again only to have the same issue
- I replaced my Note 7 with a non-explosive one and set up the headset again. Still have the same issue
- I even created a new Oculus account and tried to set up and install apps that way.
I can't imagine it is a problem with the headset since that is simply a way to view the content on your phone. Every app I try to install goes through the download process fine, but then instead of installing, it just goes back to the download button.
Very frustrating. Anyone else with a Note 7 and 2nd generation Gear VR having similar issues?
Wow, that sucks. I haven't had a problem with my Gear VR for the N7. I didn't have a problem with my N4 gear VR either. Hope you find the solution.
I was running my galaxy watch on my pixel 3xl, Android R dp1 with just some lag. Today my phone updated to dp2. It seemed as if the lag on the watch went away. Anyways, I did a factory reset on my phone and now my watch won't finish pairing. It goes thru the process where it says that it paired and to approve the permissions. But then I get a lovely pop-up that says "companion device manager keeps stopping". The watch just says to check phone to complete setup, meanwhile the wear app just goes in a loop of pairing, asking for permissions, going to the settings, then companion app stopping. Does anyone have any ideas? I've tried resetting the watch and I can't find anything on Google or xda. Thank you in advance.
Sinds a few day/a week my Samsung S20 with all latest updates installed is rebooting when connecting to my car with Android Auto. The S10 of my wife is still working fine.
Today tested with another Samsung S20 and this one has the same issue.
Also tried clearing cache and rebooting in safe mode but nothing seems to fix the problem.
Anyone can help?
wouterverboom said:
Sinds a few day/a week my Samsung S20 with all latest updates installed is rebooting when connecting to my car with Android Auto. The S10 of my wife is still working fine.
Today tested with another Samsung S20 and this one has the same issue.
Also tried clearing cache and rebooting in safe mode but nothing seems to fix the problem.
Anyone can help?
Click to expand...
Click to collapse
I'm facing the same issue with my S20 - only started happening in the last week. I have tested with two other phones and the headunit works perfectly. Also tested with another S20 and the phone just reboots
As a work around, I've installed headunit reloader until an update is released for it
Seems u have indeed exactly the same problem.
What does your workaround do? i'm little confused here
wouterverboom said:
Seems u have indeed exactly the same problem.
What does your workaround do? i'm little confused here
Click to expand...
Click to collapse
Sorry I bought the headunit reloaded app( it does an android auto emulator on your headunit)... but a friend sent me the fix this morning. It looks like its caused by the latest update to google chrome, if you uninstall the latest update it should fix your issue. I just tested and it worked for me ( There is a thread on another site about it )
Cool! This was the workaround for me 2 Now it's working again.
I am having the exact same problem. Right after the latest Verizon update. Plug it in to the Car and automatically reboots. After the major Android update, wireless AA stopped working. And now, Android Auto will not even load when plugged in. Charges fine outside the car. Looks like it's time to dump this super expensive POS phone. Too many issues are piling up
I recently started wearing my galaxy watch that I've had for a couple years and I have a rooted stock OnePlus 9 pro on the latest firmware and version and the watch initially connected to my phone and did the whole set up, got notifications and everything then I opened the wearable app and it's now giving me an issue with needing to update the watch plugin but when it goes to the playstore it only gives me the option to uninstall is the update only for Galaxy phones? Anyone know of a way to fix it?