Hi everyone, thanks in advance for your help. I've searched and searched on this site and all over the internet to no avail. If you can help me, I'd be most appreciative!
First off, I have basic knowledge of this stuff with the help of tutorials, but am not even close to being fluent in it. That said, I had my gear s2 paired with my old Note 4 a few years ago. Last year, I bought a Pixel on Black Friday and found a way to root the watch and put Android Wear on it so that it would work with the Pixel. It worked fine for over a year. Recently, it was giving me problems, every few seconds crashing saying Google Services were not working. I factory reset the watch and it is now fresh with Android Wear on it. However, it will not find my phone and vice versa to connect them.
I told it to "forget" my phone and repair, even uninstalled Android Wear on my phone and reinstalled it, and nothing. The BT function of both my phone and watch work fine, as they are able to find other BT devices near them, just not each other.
Anybody have any ideas? It's driving me crazy. Thanks!
m0ssman said:
Hi everyone, thanks in advance for your help. I've searched and searched on this site and all over the internet to no avail. If you can help me, I'd be most appreciative!
First off, I have basic knowledge of this stuff with the help of tutorials, but am not even close to being fluent in it. That said, I had my gear s2 paired with my old Note 4 a few years ago. Last year, I bought a Pixel on Black Friday and found a way to root the watch and put Android Wear on it so that it would work with the Pixel. It worked fine for over a year. Recently, it was giving me problems, every few seconds crashing saying Google Services were not working. I factory reset the watch and it is now fresh with Android Wear on it. However, it will not find my phone and vice versa to connect them.
I told it to "forget" my phone and repair, even uninstalled Android Wear on my phone and reinstalled it, and nothing. The BT function of both my phone and watch work fine, as they are able to find other BT devices near them, just not each other.
Anybody have any ideas? It's driving me crazy. Thanks!
Click to expand...
Click to collapse
How did you manage to get Android Wear on this watch? Are we talking about the regular gear S2 or the classic?
Related
Hi XDA
I have a bit of a problem with my Smartwatch. I have tried every single 'fix' out there (self proclaimed techie, I usually google my problems first. making a post is a last resort). I got the watch since Christmas, and I've been working on it since
Heres my problem
I use a Feiteng N9300+ (S3 clone) and my smartwatch would pair to it, but disconnect every time I turn on the watch to check the time then reconnect around 5-10 seconds later. Apps wont work, they used to (with sheer luck, approx. 4% of the time) but after I formatted my phone apps don't show up at all.
I tried the watch with my Viewsonic G Tablet and it works, so I've narrowed it down to a faulty bluetooth chip within my phone, or a software related problem. Its probably the software
Any fixes? (I've tried Bluetooth keep alive and around 10 other apps, and around 20 'fixes' )
Thanks in advance
I just got my hands on the 2017 gear 360 two days ago and all was well until today. Suddenly it wouldn't connect. Everything that went through my mind was could it of been the firmware update, updating the app or what did I disable that I shouldn't have in my beer fuled craze last night. Well after trying all the normal solutions and coming up empty handed I turned to Google. All the sound for people with the same problem but no Solutions anywhere. It wasn't till to be honest stupid blind luck that I uninstall the Samsung Accessory Service app and that was the ticket. It reinstalled itself and everything went smooth from there for the most part. When it finally did connect the resolution options were grayed out and stuck at 10fps. I just hit reformat for the camera and everything was back to normal finally. My dream of making my own VR porn is now at least possible now again! Ya I know not likely but I still have my beer. I hope this helps somebody out.
iluvsporks said:
I just got my hands on the 2017 gear 360 two days ago and all was well until today. Suddenly it wouldn't connect. Everything that went through my mind was could it of been the firmware update, updating the app or what did I disable that I shouldn't have in my beer fuled craze last night. Well after trying all the normal solutions and coming up empty handed I turned to Google. All the sound for people with the same problem but no Solutions anywhere. It wasn't till to be honest stupid blind luck that I uninstall the Samsung Accessory Service app and that was the ticket. It reinstalled itself and everything went smooth from there for the most part. When it finally did connect the resolution options were grayed out and stuck at 10fps. I just hit reformat for the camera and everything was back to normal finally. My dream of making my own VR porn is now at least possible now again! Ya I know not likely but I still have my beer. I hope this helps somebody out.
Click to expand...
Click to collapse
Check which mode the camera is in. Then check camera settings.
I have just aquired an Honor 10 and this watch. Try as I might, no amount of clearing data/cache has worked. Everything reinstalled multiple times... I have upgrade the firmwar pn the watch by pairing with another phone.
Basically the watch will pair with the phone, but the app/plugin crashes as soon as i accept the pairing. I'm not sure if this is better posted here or in the Honor 10 forum, but to be honest this is driving me mad.
I would really appreciate it if anyone could throw any light on this!!
I got a new Watch 4 LTE from TMobile and I did get Google Pay set up on it, and it works, with limitations. It appears that when I tip my wrist back to place the watch near the reader, the screen shuts off and apparently, this may be preventing the NFC from working. If I contort myself the opposite direction so the screen doesn't shut off, Google pay works fine, but it's uncomfortable and just looks weird. As for Samsung Pay, I had it set up on my old watch and I told it I would be moving it to the new watch. This apparently requires an update of the watch app on the Watch 4, which consistently fails. I had a similar issue on my old watch and turning off WiFi on my phone seemed to fix it, but that's not the case here. Anyone have ideas? Can I sideload the Samsung Pay watch app through wireless ADB?
spyderveloce said:
I got a new Watch 4 LTE from TMobile and I did get Google Pay set up on it, and it works, with limitations. It appears that when I tip my wrist back to place the watch near the reader, the screen shuts off and apparently, this may be preventing the NFC from working. If I contort myself the opposite direction so the screen doesn't shut off, Google pay works fine, but it's uncomfortable and just looks weird. As for Samsung Pay, I had it set up on my old watch and I told it I would be moving it to the new watch. This apparently requires an update of the watch app on the Watch 4, which consistently fails. I had a similar issue on my old watch and turning off WiFi on my phone seemed to fix it, but that's not the case here. Anyone have ideas? Can I sideload the Samsung Pay watch app through wireless ADB?
Click to expand...
Click to collapse
Well... I tried Google pay at another shop and it worked fine when the screen turned off... So I'm down to Samsung Pay. Honestly, I don't have to have it with GPay working right now, but it's gonna bug the heck outta me not being able to update it.
Are your phones rooted?
inningsdefeat500 said:
Are your phones rooted?
Click to expand...
Click to collapse
No. I used to root every phone I had long ago, but I stopped doing that when I started using Google Pay and Samsung Pay. These days, I don't find a lot of reason to root anyway.
spyderveloce said:
I got a new Watch 4 LTE from TMobile and I did get Google Pay set up on it, and it works, with limitations. It appears that when I tip my wrist back to place the watch near the reader, the screen shuts off and apparently, this may be preventing the NFC from working. If I contort myself the opposite direction so the screen doesn't shut off, Google pay works fine, but it's uncomfortable and just looks weird. As for Samsung Pay, I had it set up on my old watch and I told it I would be moving it to the new watch. This apparently requires an update of the watch app on the Watch 4, which consistently fails. I had a similar issue on my old watch and turning off WiFi on my phone seemed to fix it, but that's not the case here. Anyone have ideas? Can I sideload the Samsung Pay watch app through wireless ADB?
Click to expand...
Click to collapse
Yeah I have the same issue with Google Pay. When I move my wrist to place it close to the card reader, a clock appears on top of the screen and prevents Google Pay from doing anything.. Really annoying.
I saw other people complaining about this as well on Reddit. Don't know what the solution is for now as I have already turned off the wrist gesture in the settings.
Hello, I tell you that I was able to make NFC payments work with the BBVA GO Apk in Argentina, I comment on why I think that in Latin America, it saved Chile, Brazil and Mexico, there is no application to use NFC Pay. If anyone is interested I can show them how I did. I cannot create a new thread as I am not reaching the level. Best regards Miguel.
I tried the 4 classic on my pixel 4 xl. It won’t finish setup. Tried three times. Took it back. Best Buy guy said there’s a software bug that prevents the Galaxy watch 4 classic from working on any non s22 or s21 phone.
What’s going on?
Wearables needs all it's many permissions or it will not load/work true even on a Samsung.
There's been an issue with the Pixels and Google even locked a thread about it on their own forum with no solution found.
Talk about sticking their head in the sand...
What does this mean? Basically you need an S21/22?
I run the app on the phone. It starts the setup and sits there about 50%. Then a notipops up saying you need to connect to the watch. It’s already connected. Tapping connect or cancel or whatever does nothing. The pop up just times out and goes away. The 50% set up or whatever the % is, it just stays there. Tried 3 x then returned the watch. The BB guy said it’s a software issue that no phones will work now with the current software unless the phone is the S21/22.
I don’t get it.
buggs1a said:
What does this mean? Basically you need an S21/22?
I run the app on the phone. It starts the setup and sits there about 50%. Then a notipops up saying you need to connect to the watch. It’s already connected. Tapping connect or cancel or whatever does nothing. The pop up just times out and goes away. The 50% set up or whatever the % is, it just stays there. Tried 3 x then returned the watch. The BB guy said it’s a software issue that no phones will work now with the current software unless the phone is the S21/22.
I don’t get it.
Click to expand...
Click to collapse
I don't know. Invariably Samsung will eventually fix the issues just don't hold your breath waiting for it.
As with most of the Samsung accessories it's optimized and integrated for the Samsung ecosystem. Even some Samsung users are having issues apparently.
The other side of this is sometimes you need to play with Samsung apps a bit. My Buds+ will run at first on the latest version of Wearables but eventually the audio screws up. Solution, install the older version which works, has a better UI and then Firewall block the the update UID for it so it doesn't auto update and self destruct
I make adjustments as needed... got a 2nd pair of Buds+ order, which shows you how rattled I am.
Wow lol. It’s been months and they haven’t fixed it. Insane. Could be on purpose too. Wanting to sell Galaxy phones. Hmm.
buggs1a said:
Wow lol. It’s been months and they haven’t fixed it. Insane. Could be on purpose too. Wanting to sell Galaxy phones. Hmm.
Click to expand...
Click to collapse
Well that could be Best Buys intent.
You give Samsung too much credit; this likely wasn't planned... which is why it happened
The original Buds were a mess when first released. It took a year worth of sequential firmware updates to dial them in.
There been reported problems with newer models as well I believe I saw as I was reading. Anymore I'll never preorder or be the first to buy their products or "test" their updates. Instead I buy when known to be good. It's always been hit or miss with Samsung to a greater or lesser degree. They are capable of producing exceptional products and bone rattling duds.
Best Buy intent? I was saying Samsung maybe did this on purpose.
Anyway.
buggs1a said:
Best Buy intent? I was saying Samsung maybe did this on purpose.
Anyway.
Click to expand...
Click to collapse
I have zero faith in Best Buy. They are a horror to deal with... they tried my patience for the last time 2 years ago.
buggs1a said:
I tried the 4 classic on my pixel 4 xl. It won’t finish setup. Tried three times. Took it back. Best Buy guy said there’s a software bug that prevents the Galaxy watch 4 classic from working on any non s22 or s21 phone.
What’s going on?
Click to expand...
Click to collapse
there is a software issue or something make watch 4 classic dont work on non samsung or even older samsung like s9 s10 that make you have trouble and think about upgrading the phone which personally im sure its on purpose by samsung you may be able to connect the phone doing factory reset but me and alot of people cant connect google account to the watch afterward which there is no fix till now ofc hoping the new upcoming wear os 3.5 and one ui 4.5 update will fix it but if not thats just it personally i was so intrested in s22 ultra and was thinking to buy it before this happened but if the update wont fix it i will never pay samsung in my life in any sort of way
omid_nr said:
there is a software issue or something make watch 4 classic dont work on non samsung or even older samsung like s9 s10 that make you have trouble and think about upgrading the phone which personally im sure its on purpose by samsung you may be able to connect the phone doing factory reset but me and alot of people cant connect google account to the watch afterward which there is no fix till now ofc hoping the new upcoming wear os 3.5 and one ui 4.5 update will fix it but if not thats just it personally i was so intrested in s22 ultra and was thinking to buy it before this happened but if the update wont fix it i will never pay samsung in my life in any sort of way
Click to expand...
Click to collapse
Factory reset is a waste of time; try a network reset instead!
Even with the Buds+ the getting them working takes some effort sometimes. The spen can be the same way.
If the Wearables app is screwed up, nothing may work. An older version may work but it requires some effort to load and keep from updating which would break it again.
Deliberate? No Samsung doesn't need to intentionally try to screw things up, it comes naturally Sammy's been dropping balls a lot lately.
I`ve been using my watch 4 classic with my 4XL without any issues since May before upgrading to my P6P. And after upgrading to my P6P I didn`t run into any issues. What I`ve experienced when setting up my watch 4 classic for the first time was that the samsung wearable app was switching screens after providing credentials for my g account and therefore was hiding the permissions quote and the wearable app was waiting for the authorisation to use the g account. Those sammy blue dots were circling around for many minutes. Happened to me twice. Using the back ´gesture let me grant the permissions needed and t he setup process just went through smoothly.
bluetigger68 said:
I`ve been using my watch 4 classic with my 4XL without any issues since May before upgrading to my P6P. And after upgrading to my P6P I didn`t run into any issues. What I`ve experienced when setting up my watch 4 classic for the first time was that the samsung wearable app was switching screens after providing credentials for my g account and therefore was hiding the permissions quote and the wearable app was waiting for the authorisation to use the g account. Those sammy blue dots were circling around for many minutes. Happened to me twice. Using the back ´gesture let me grant the permissions needed and t he setup process just went through smoothly.
Click to expand...
Click to collapse
The infamous circling blue dots make me cringed every time I see them now. Like some alien from Star Trek eyeballing you
Wearables will puke all over unless all permissions* are granted. Something I really hate about Wearables. Reminds me of the bixby spyware. Lol, don't worry Samsung servers are secure... until the next hack
*check that all permissions have been checked manually as it doesn't always happen during installation for whatever reasons.
Thanks all.
I had the S22+. No issue. But returned the watch and phone because the phone screen shuts off if I don’t touch it for a bit when playing games. Some games I play auto battle and takes awhile so no need to touch. So I returned them both yesterday.
buggs1a said:
Thanks all.
I had the S22+. No issue. But returned the watch and phone because the phone screen shuts off if I don’t touch it for a bit when playing games. Some games I play auto battle and takes awhile so no need to touch. So I returned them both yesterday.
Click to expand...
Click to collapse
Only 8gb of ram, max 256gb internal storage and no expandable storage, rounded display corners... yeah I'm not feeling it.
Good call.