so after 6mounth using this watch suddenly watch disappeared from wearable app and it wouldn't connect again always stuck on 80% or 90% of the process i searched many people faced this issue and had to reset the watch to connect it again and i'm using it on huawei phone (as before i was using) so wearable wont let you connect and you need to force it by samsung and now that i'm connected i cant signing my google account to my watch to restore my apps and watch faces now this google signing problem is there for all wearos users and many people face this problem i tried resetting the phone and watch several times using different google accounts and even tried to do this in a samsung device still the same result any one have any experience or idea about this? me and many others cant use their watches
FIXED!!!
UPDATE : After search for a long time and couple of factory resets and every single way that ppl said it fixed it for them it didnt worked for me until i saw someone had the same problem like me and only connecting to a Canada vpn fixed it for it sounded too random but i tried and it worked so if you have the same problem and other ways dont fix it try this first connect to a canada vpn then start copy account from wearable app on phone
I have a Samsung Galaxy S22 Ultra but ran into this issue when I first bought my Galaxy Watch4 Classic. What I ended up having to do is delete the Google account from my phone all together. Then setup the watch. Once I got the watch setup on the Galaxy Wear app, I reloaded my Google account on the phone, and all worked fine.
dalepl said:
I have a Samsung Galaxy S22 Ultra but ran into this issue when I first bought my Galaxy Watch4 Classic. What I ended up having to do is delete the Google account from my phone all together. Then setup the watch. Once I got the watch setup on the Galaxy Wear app, I reloaded my Google account on the phone, and all worked fine.
Click to expand...
Click to collapse
i tried almost all the ways that fixed some people problems like redoing multiple times disabling screen locks turning wifi off clearing data and caches removing g accounts almost everything out there but still there is too many people with the issue remaining idk why they make it so hard to do this when i could just put in my gmail and password in my watch simply
bhello same problem for 3 days, it annoys me crazy!!! I so regret having bought it, autonomy level is zero and now this bug with Google Frankly is too much
Hello. I had the same problem. After googling for longe time i found out it was a dns related issue.
Link (unfortunately only in german)
Long story short, as i could not figure out how to set up my router, i got it running by simply using mobile data instead of WIFI.
EDIT: I am not sure if i disabled "Private DNS" setting in Android as well
tu Still no response from Samsung? Does anyone know how to fix the problem? Me, I've tried all of them and I'm at the end of it
ste27.jah said:
tu Still no response from Samsung? Does anyone know how to fix the problem? Me, I've tried all of them and I'm at the end of it
Click to expand...
Click to collapse
frankly me too i stopped using the watch couple of days now im gonna redo all the processes that i found in the internet if no luck im just gonna get rid of it cuz it was all working and suddenly stopped connecting to phone and wearable app so it will happen again someday
Did you try using Google DNS 8.8.8.8 while copying?
david.siebauer said:
Did you try using Google DNS 8.8.8.8 while copying?
Click to expand...
Click to collapse
yes still no luck. i noticed after many reset factories my watch still connects to my wifi ap without required password and most of the people who cant solve this problem are using android 9 even on samsung s8 and s9 series
oh yes exactly, very strange the fact that the watch automatically reconnects itself to the wifi and that without any passwords and all that without any restoration!!
JI really hate against Samsung, because no solution is offered anyway went crazy. As usual, the customers remain in a dead end without any help from the manufacturer.
ste27.jah said:
oh yes exactly, very strange the fact that the watch automatically reconnects itself to the wifi and that without any passwords and all that without any restoration!!
Click to expand...
Click to collapse
ste27.jah said:
JI really hate against Samsung, because no solution is offered anyway went crazy. As usual, the customers remain in a dead end without any help from the manufacturer.
Click to expand...
Click to collapse
its either the watch is not wiping the data completely and the issue still remains or they are aware of this problem and cant solve it and even worse they wanna force ppl to upgrade their phones cuz all the new devices can fix the issue but the older devices running android 9 cant fix this and i searched lots of posts on samsung and google forums no official staff answering to the ppl only other ppl trying to help out. i mean why you should need to copy google account from the phone? why not just log into it with your freakin watch
It's not just Android 9. My OnePlus 10 Pro can't sign in. The Samsung sign in send you to a web browser to press continue to sign and just puts you in a death loop of continue button until failure. If you skip this part it fails to log in to Google account and then the wearable app has a bleeping seizure. I've tried resetting the device, restarting both phone and watch, wiping data from app uninstalling and reinstalling all needed apps and plugins.... I think this is a server side issue from Samsung bc when I go to Samsung website after creating my account I'm unable to to link my Google acct just a non functional set up button on the screen... At least my OnePlus watch can tell time this is just a useless wearable until patch is released
RickCambio34 said:
It's not just Android 9. My OnePlus 10 Pro can't sign in. The Samsung sign in send you to a web browser to press continue to sign and just puts you in a death loop of continue button until failure. If you skip this part it fails to log in to Google account and then the wearable app has a bleeping seizure. I've tried resetting the device, restarting both phone and watch, wiping data from app uninstalling and reinstalling all needed apps and plugins.... I think this is a server side issue from Samsung bc when I go to Samsung website after creating my account I'm unable to to link my Google acct just a non functional set up button on the screen... At least my OnePlus watch can tell time this is just a useless wearable until patch is released
Click to expand...
Click to collapse
i updated the first post check it out it fixed it for me i hope it helps you aswell
I have the same proble, VPN no works, I cant copy account google to watch... It is ....
found solution. downgrading gms to 23.05.14 worked for me
Related
Does anybody else have a problem with the screen timeout settings? It seems to remain the same 10-15 seconds no matter what I put it on. Even if I set it to 10 minutes
Good for your battery life! ?
Are you talking about the lock screen or the normal display after you unlock it. There is no way to change the timeout of the lock screen.
I get that too. It times out no matter what time I set it!
This is driving me crazy!!
joshlee80 said:
I get that too. It times out no matter what time I set it!
This is driving me crazy!!
Click to expand...
Click to collapse
Might have something to do with face recognition. (Smart Stay) try messing with those settings too. I receive mine today so ill look into it too.
I'm having the same issue. Spent all night messing with every setting to no avail. Incredibly frustrating.
think its about smart stay, or did you use any battery saver that comes with the phone?
Does the same thing with smart stay on or off (unless you're staring right at the screen in good lighting), no battery saving modes used. On the phone with Samsung right now
[email protected] said:
Does the same thing with smart stay on or off (unless you're staring right at the screen in good lighting), no battery saving modes used. On the phone with Samsung right now
Click to expand...
Click to collapse
Please let me know? I would like to find out what Samsung says!
They used smart tutor to access my phone and looked at all the settings. Said they would call me back when they have a solution. Didn't ever verbally confirm it as an issue, not holding out much hope
[email protected] said:
They used smart tutor to access my phone and looked at all the settings. Said they would call me back when they have a solution. Didn't ever verbally confirm it as an issue, not holding out much hope
Click to expand...
Click to collapse
just for your info, I did spoke to Samsung as well and I reset the phone as they told me to. They are thinking there is something contradiction between your old backup data and current. It actaully fixed the issue but now I found a dead pixel.... shoot. Now I will have to go to T-mobile for the replacement phone. Hope they accept it.
So did they just have you do a factory reset? Sorry to hear about the dead pixel what a bummer. Anything you could tell me about what they had you do would be much appreciated.
Thanks!
I'm glad its not just me, I'm going to factory reset to see what happens. I've been using a Stay Alive app in the meantime
Installed the T-Mobile software update, made no difference. So far the only thing that seems to work for me is a factory reset and to set it up as a new device; restoring any devices through Google seems to result in the same issue. Restoring data from devices linked to Samsung account (which I have to if I log into Samsung account while setting up for some reason) doesn't seem to matter one way or the other.
Mine is working for now going to start installing my apps and hope it continues to do so
[email protected] said:
Installed the T-Mobile software update, made no difference. So far the only thing that seems to work for me is a factory reset and to set it up as a new device; restoring any devices through Google seems to result in the same issue. Restoring data from devices linked to Samsung account (which I have to if I log into Samsung account while setting up for some reason) doesn't seem to matter one way or the other.
Mine is working for now going to start installing my apps and hope it continues to do so
Click to expand...
Click to collapse
Hi, Thanks for the info. So which one did have an impact? Google backup or Samsung Cloud? I only restored phone number and picture from google and didn't even try Samsung cloud.
joshlee80 said:
Hi, Thanks for the info. So which one did have an impact? Google backup or Samsung Cloud? I only restored phone number and picture from google and didn't even try Samsung cloud.
Click to expand...
Click to collapse
Samsung cloud seems to have no effect. Restoring app data (can add Google accounts etc. just do not restore data from any other devices when prompted) from any devices linked to my Google account causes the issue eveytime. Set up as a new device and manually selected apps to install from my list of apps in play store and all is well.
Hope this helps
[email protected] said:
Samsung cloud seems to have no effect. Restoring app data (can add Google accounts etc. just do not restore data from any other devices when prompted) from any devices linked to my Google account causes the issue eveytime. Set up as a new device and manually selected apps to install from my list of apps in play store and all is well.
Hope this helps
Click to expand...
Click to collapse
Thanks a lot! it helps! I am getting a warranty exchange for the dead pixel. You cannot get this exchange from Samsung directly but from the service provider.
[email protected] said:
Samsung cloud seems to have no effect. Restoring app data (can add Google accounts etc. just do not restore data from any other devices when prompted) from any devices linked to my Google account causes the issue eveytime. Set up as a new device and manually selected apps to install from my list of apps in play store and all is well.
Hope this helps
Click to expand...
Click to collapse
Thank you so much, so much help. It worked
I find even playing games my phone goes onto lock mode if I'm not touching screen.
Annoying.
I am trying to set up Samsung Pay on my new Galaxy Watch4 Classic. No matter what I do, I can't get past this screen! Paired with Z Fold3. Touching the button with the arrow does nothing. Any help would be appreciated!
Update: Maybe this has something to do with it? Every time I open the Samsung Pay watch plug in on my phone it tells me it needs to update the Samsung Pay app on my watch. But every time it fails. Yes I've rebooted. No reason given. Any ideas? Phone is Z Fold 3.
maybe ur watch region CSC dont allow samsung pay .
samsung pay work in ur fold3 ?
check ur watch region
carlitobahsoun said:
maybe ur watch region CSC dont allow samsung pay .
samsung pay work in ur fold3 ?
check ur watch region
Click to expand...
Click to collapse
Yes works fine on ZF3 and on my GW3 up until I cleared it. I'm in the USA and it's a US watch purchased directly from AT&T.
I had the same issue with mine when I first got it. I THINK what I did was disconnect from my phone and make sure the watch was connected to my home WiFi. Then it updated and I could set it up. It's been awhile so I can't remember for sure. Hope that helps!
roaddog665 said:
I had the same issue with mine when I first got it. I THINK what I did was disconnect from my phone and make sure the watch was connected to my home WiFi. Then it updated and I could set it up. It's been awhile so I can't remember for sure. Hope that helps!
Click to expand...
Click to collapse
I will try that thank you.
roaddog665 said:
I had the same issue with mine when I first got it. I THINK what I did was disconnect from my phone and make sure the watch was connected to my home WiFi. Then it updated and I could set it up. It's been awhile so I can't remember for sure. Hope that helps!
Click to expand...
Click to collapse
Nope didn't work, or I didn't do it right. I've had my watch disconnected from the phone (even turned off remote connection), WiFi only, for 2 hours now. Opened the Samsung Pay app many times, never prompted for an update and nothing ever happened on its own. Still can't get past that Get Started screen with the arrow button. Is there a way to manually trigger an update or clear data for an app directly from the watch? I couldn't find Samsung Pay in the Play store either to update or reinstall.
Ok, I may not be remembering correctly either. I would try resetting the samsung pay watch app in the Galaxy Wearable app. Watch settings>apps>app settings>samsung pay. Get into the settings there and check the version, it may let you update the watch plug in from there. If not I'd use the reset option.
roaddog665 said:
Ok, I may not be remembering correctly either. I would try resetting the samsung pay watch app in the Galaxy Wearable app. Watch settings>apps>app settings>samsung pay. Get into the settings there and check the version, it may let you update the watch plug in from there. If not I'd use the reset option.
Click to expand...
Click to collapse
Thank you, good advice. Unfortunately that's the first thing I tried and there actually is no option to reset. Usually you can click on Storage and then have Clear Cache and Clear Data. Clicking on Storage for Samsung Pay does nothing. No option to clear anything. Can't uninstall either. The closest I could come to this was uninstalling and reinstalling the Samsung Pay Watch Plugin from my phone, and that didn't help. I did talk to Samsung and they want me to bring it to a service center or ship to them for physical repair, which is about what I was expecting for an answer. I did try resetting the watch back to factory defaults and reinstalling the wearables app on my phone, no luck. Brought me right back to the same place. I guess I will try exchanging it since I just bought it, and if the new one doesn't work I'll just go back to my GW3. Thank you for your help.
Did you tried to reset App data from ADB? ADB is a debug protocol for Android devices. With ADB you can do things which no allowed to do in User Interface. In Android OEMs like Samsung are disabling to much features in UI because they think people are dumb and they don't wanna mess your phone if you are not experienced user. With ADB you can do too much things in Android devices. I don't know how to reset app data with ADB but I did it before, just search the web.
Its easy. i had the same issue, only solved by doing this. Install APKPure and search for updates for your apps. it should appear there.update it, and afterwards you can uninstall the APKPure.
Best of luck mate.
Hi, was this ever solved in the end? I am just experiencing this issue... It's because of the new update for the Watch Plug-In, for some reason it cannot update the app on the watch itself or communicate to that app at all... I still experience that same stuck screen!! Any help would be appreciated.
Hello, good people.
So I recently bought a gw4 and I literally tried everything to pair it with my s20+ with no success.
I tried EVERYTHING except factory reset of the phone. Installed and uninstalled the Wear app, wiped cache everywhere I thought I should be etc etc.
The step where the problem appears is when I need to accept terms and conditions. It's just a blank page and I can't agree with the terms and proceed with pairing! Also, while on that step, Play store is looking for an update for Wear infinitely and I need to force stop it later lol. Pls see the attached Screenshot.
The seller obviously won't take it back because it connected successfully with their S21 and I have no reason not to believe that the problem is between the watch and my phone.
I had a real hard time getting my watch to pair with my S22 Ultra. In the end, I had to remove my google account from my phone and then it setup just fine. Once completed, just readded my google account.
dalepl said:
I had a real hard time getting my watch to pair with my S22 Ultra. In the end, I had to remove my google account from my phone and then it setup just fine. Once completed, just readded my google account.
Click to expand...
Click to collapse
Did you have a problem with accepting the terms?
I didn't try removing my Google account, might try that.
No, my issue was when the Wear app was trying to transfer my Google account to the watch. It won't hurt to try. It will not mess things up.
I will try anything before the factory reset haha
Sigh, factory reset solved the issue...
Sorry to hear that, but at least it fixed it. Been bad if a reset still had the same issue.
LOL, so true! I think I'd snap.
Hello everyone,
My Galaxy Watch4 has been great. But I've come across a few occasions where my watch mysteriously disappears from the Galaxy Wearable app and the list of paired bluetooth devices. Unfortunately, the watch fails to recognize my phone as the same device and forces me to reset it.
I have debloated my phone and I did notice that it happened once after resetting network settings (although that could be an annoying but correct behavior). I wouldn't be bothered as much if I could just repair it as-is but this has happened about 3 times since I've owned the watch.
I did use a debloater script on my S22 but not the watch. The issue persists after reversing the debloat. Is this a known issue? Are there ways to locate logs/settings that may be causing this?
Alternatively, is there a developer/hidden option to bypass the erase requirement?
It happened to me when I cleared Google Play Services Data.
JazonX said:
It happened to me when I cleared Google Play Services Data.
Click to expand...
Click to collapse
I can't recall if that happened in my circumstance, but I know of one instance where it didn't and it happened back to back, requiring me to reset my watch 3 times. Could be user error on my part since I tinker with my phone but knowing that it relies on GPS is a step in the right direction
https://www.reddit.com/r/WearOS/comments/p7lhir
Just thought id put this up in case anyone else is going round in circles after an update to A13/OneUI 5.0 on Samsung devices
Updated my S20+ 5G overnight and only one issue so far...unable to connect my Watch 4 to it
Sometimes get as far as pairing code shown before inevitable fc
Issues with Watch 4 connection noted on S22's, so may be related
You would think they would test this stuff, wouldnt you.....
Bloody Samsung, premium price for garbage software updates
Im going back to A12 or start looking round for a new phone....why cant Google make a decent Pixel without buggy hardware...life was so easy when they did
Update:
Reading the S22 threads theres a whole host of issues with A13 and OneUI 5.0
Really, how does Samsung do this on a flagship??? Its like a clown show
73sydney said:
Just thought id put this up in case anyone else is going round in circles after an update to A13/OneUI 5.0 on Samsung devices
Updated my S20+ 5G overnight and only one issue so far...unable to connect my Watch 4 to it
Sometimes get as far as pairing code shown before inevitable fc
Issues with Watch 4 connection noted on S22's, so may be related
You would think they would test this stuff, wouldnt you.....
Bloody Samsung, premium price for garbage software updates
Im going back to A12 or start looking round for a new phone....why cant Google make a decent Pixel without buggy hardware...life was so easy when they did
Update:
Reading the S22 threads theres a whole host of issues with A13 and OneUI 5.0
Really, how does Samsung do this on a flagship??? Its like a clown show
Click to expand...
Click to collapse
check lot of iPhone problems..
btw, Oneplus had problem with connection GW4 after upgrade from 12 to 12.1. only one solution was reset GW. now on 1+ A13 doesnt work Google Wallet/Payments with cloned apps enabled.. Samsung is better competetion..
I haven't had the 1st issue (knock on wood) and it paired up with my GW4 right away. I flashed my One UI 5 manually
HyperChick said:
I haven't had the 1st issue (knock on wood) and it paired up with my GW4 right away. I flashed my One UI 5 manually
Click to expand...
Click to collapse
Yup, since im rooted it was a manual clean flash for me via ODIN
It seems very random according to what ive seen....but ever since Watch 4 came out its been one connection problem after another, and Watch 5 users have been plagues by them too
Try updating google play services to the latest beta (apkmirror). Solved my issue
shaharofir said:
Try updating google play services to the latest beta (apkmirror). Solved my issue
Click to expand...
Click to collapse
tried latest beta (22.45.15 (190400-488417729) beta (190400))
absolutely no difference
73sydney said:
Yup, since im rooted it was a manual clean flash for me via ODIN
It seems very random according to what ive seen....but ever since Watch 4 came out its been one connection problem after another, and Watch 5 users have been plagues by them too
Click to expand...
Click to collapse
There's your problem, root! But there are workarounds available. Just search in this forum and you'll find some
DaReDeViL said:
There's your problem, root! But there are workarounds available. Just search in this forum and you'll find some
Click to expand...
Click to collapse
Cheers, but just for reference, im quite involved in Magisk circles and hiding root (have modules to assist in this)...im usually helping others hide stuff or deal with root issues.....so i know what im doing
Also the same setup i use had no such issues in Android 12, its very much a Samsung making life harder for everyone, on purpose, because theyre basically acting like the new Apple and want to lock everything down. Ive decided to go back to Pixel, off to buy one soon, Samsung has gotten their last $ from me, they can go hang...
73sydney said:
Yup, since im rooted it was a manual clean flash for me via ODIN
It seems very random according to what ive seen....but ever since Watch 4 came out its been one connection problem after another, and Watch 5 users have been plagues by them too
Click to expand...
Click to collapse
Rooted Samsung Phones doesn't connect to Samsung Watches anymore.
You need to modify 2 files in vendor partition,
Vendor - build prop and remove SAKV2 from security keys
Vendor/etc/Wintf - Empty the Manifest.xml file
reboot and the watch will connect fine.
JazonX said:
Rooted Samsung Phones doesn't connect to Samsung Watches anymore.
You need to modify 2 files in vendor partition,
Vendor - build prop and remove SAKV2 from security keys
Vendor/etc/Wintf - Empty the Manifest.xml file
reboot and the watch will connect fine.
Click to expand...
Click to collapse
You prolly missed this module of mine in my signature (signatures dont show on mobile) , but i was already using that method and had been for a while :
GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices
Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices - GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" f...
github.com
I did later figure it out, will post my outcome separately
73sydney said:
You prolly missed this module of mine in my signature (signatures dont show on mobile) , but i was already using that method and had been for a while :
GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices
Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices - GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" f...
github.com
I did later figure it out, will post my outcome separately
Click to expand...
Click to collapse
Thank you for this.
I will use this If I ever lose the R/W ability in my device.
For now I have R/W - so I wrote to the file directly.
Heres what i found out......
TLDNR version:
Dont backup and restore Samsung Wearables Apps - even if you previously were able to do this for eons, like i had. I have used Migrate to backup and restore apps and app data for eons (important to note i always left the app data (middle column in Migrate GUI) disabled for Samsung Wearables apps. Always let the Watch be detected as part of device setup on stock ROM OR install the Galaxy Wearable live from the Play Store (after clearing Google Play Services/Store sata and achieving Integrity check if you are rooting your device)
Longer version:
The other night i finally got time to flash back to A12, ran my normal procedure, rooted, USNF...clear data on GP/GS and then connected Watch...only it still wouldnt connect, even though the app restore was taken from a clearly working A12 (just before i flashed A13)
So i had to alter my procedure in leaving out the backed up Samsung wearables apps during restore, and then let the installed ROM detect the presence of the Watch 4 AFTER i have rooted, USNF...clear data on GP/GS and then connect Watch...
Looks a little like this:
* Flash ROM via ODIN (including my special AIO.zip to install TWRP, format data, decrypt data etc)
* Watch 4 WAS powered on and waiting to be detected when setup wizard looks for it towards end of setup - ignored/cancelled setup this time - going to do the root, USNF module and integrity check thing firsties
* Finish setup
* Reboot to TWRP recovery
* Root with Magisk (renamed to .zip) via TWRP
* Reboot
* Install Magisk App to complete install (you can just use the stub installer which will download the full app, but im used to doing it this way)
* Reboot
* Install USNF (Mod) and put device in airplane mode clear data on Google Play Store/Services to pass Integrity Check
* Reboot
* Take device off airplane mode....
* Open Google Play and confirm its certified (just needs to show version (Device Is Certified of course comes later - as along as it doesnt say Device Is Not Certified, all is well)
* Watch 4 automatically detected (Wearable Manager Installer - this is i think obviously a stub installer to detect and call the latest Galaxy Wearable from the Play Store) and Watch setup commences
* Watch setup completes
* Restore remaining apps via Migrate (leaving wearables unselected - will leave them unchecked on next backup)
NOTE: you must do (and ALWAYS have had to do) the Watch connection AFTER clearing data on GP/GS to get Integrity to pass. If you do that data clear after you connect the Watch it will sever the connection, as it tied to GS
Noter 2: Ultimately i decided id had enough of Samsung tomfudgery, and i bought a Pixel 6 Pro and departed for sanity back to Pixel Lyfe.....
My watch 5 out of nowhere stopped connecting to the wearable app, but was still connected to Bluetooth. Tried clearing cache on my s22 and the watch, reset data to the wearable app, uninstalled it and the watch 5 app, reset the watch, nothing works.. Now that I reset the watch I can't get it set up.. It downloads the watch 5 app, I click OK on accept updates, then it says error then the wearable app crashes.. I tried installing an older version of the app, but it wants to update before it'll do anything. Anyone able to get past this? I can't use my watch at all. Sooo aggravating.
gettinwicked said:
My watch 5 out of nowhere stopped connecting to the wearable app, but was still connected to Bluetooth. Tried clearing cache on my s22 and the watch, reset data to the wearable app, uninstalled it and the watch 5 app, reset the watch, nothing works.. Now that I reset the watch I can't get it set up.. It downloads the watch 5 app, I click OK on accept updates, then it says error then the wearable app crashes.. I tried installing an older version of the app, but it wants to update before it'll do anything. Anyone able to get past this? I can't use my watch at all. Sooo aggravating.
Click to expand...
Click to collapse
That behaviour has been noted on S22, and well even the Watch 4, once disconnected could be a pain to get connected again, involving a Watch reset (which of course you have tried
Samsung got wise to the whole "install and older version fo the app" thing a little while ago, because it was a legit way to get Samsung Health working on rooted Samsungs, and so now its a forced upgrade on some of the wearables related apps....
As i said above, the backup (that started all this) i had was from a working install where everything worked and had for many months, but when restoring it, which id done a couple of dozen times, this last time it caused chaos. the ONLY way i could get it working was the way i outlined above, which wasnt an issue for me as i was already clean flashing, but from an installed system, well i dont know what to tell you , i tried various clearing/uninstalls of apps and could never get it to connect until i did what i did in the last post
But i dont even know if youre using a rooted S22...im guessing not
You could try clearing data on the Google Play Store and Google Play Services as they also play a part in the Watch connection (i.e. if you clear data on these ever with the Watch connected, you WILL sever the connection) and then try running Watch connection setup again
73sydney said:
That behaviour has been noted on S22, and well even the Watch 4, once disconnected could be a pain to get connected again, involving a Watch reset (which of course you have tried
Samsung got wise to the whole "install and older version fo the app" thing a little while ago, because it was a legit way to get Samsung Health working on rooted Samsungs, and so now its a forced upgrade on some of the wearables related apps....
As i said above, the backup (that started all this) i had was from a working install where everything worked and had for many months, but when restoring it, which id done a couple of dozen times, this last time it caused chaos. the ONLY way i could get it working was the way i outlined above, which wasnt an issue for me as i was already clean flashing, but from an installed system, well i dont know what to tell you , i tried various clearing/uninstalls of apps and could never get it to connect until i did what i did in the last post
But i dont even know if youre using a rooted S22...im guessing not
You could try clearing data on the Google Play Store and Google Play Services as they also play a part in the Watch connection (i.e. if you clear data on these ever with the Watch connected, you WILL sever the connection) and then try running Watch connection setup again
Click to expand...
Click to collapse
Yeah, not rooted. I'll give the clearing play store and services data a whirl. I also have a conversation going with Samsung support on Twitter. Thanks for replying!
DaReDeViL said:
There's your problem, root! But there are workarounds available. Just search in this forum and you'll find some
Click to expand...
Click to collapse
Root has nothing to do with, the Galaxy Wearable app doesnt stop working if your knox has been tripped.
Ive had the last 3 Galaxy watches and all my phones have been rooted with custom roms, any issues ive had connecting/pairing were user error.