Database Info

Help with p40 pro and Galaxy watch 3

I've done everything I can think of, but my clock somehow wont work in stand alone mode, only in bluetooth.
I also have to input my samsung account often in my phone, not really sure why, it seems the watch is not connecting to my samsung account.
I have google in my p40 pro and tried many many things like reseting the clock several times, downloading the apps from the play store and appgallery.
Please any ideas?

Did you freeze the gfs or not? Because the notification push has to be activated

Nope, gfs is not frozen, all my notifications work flawlessly on my phone and watch on bluetooh. but somehow my samsung account is not connecting to my watch so remote mode and bixby dont work. when I choose samsung account in my watch it just says login into my phone but im already logged in
addx972 said:
Did you freeze the gfs or not? Because the notification push has to be activated
Click to expand...
Click to collapse

Question Any way to connect GW4 to new phone without resetting or pull health data without rooting?

Hello, i've got a non Samsung phone. Recently there has been a bug with recently released gw4 plugin app. Bug is that wear app force prompt user to update the app although its already up to date so wear app doesnt open and watch cant connect to phone.
Reinstalled the wear app and plugin apps on watch. During pairing setup stage "Getting your watch ready" it always stuck at 80-90% and doesnt complete setup so watch cant connect to phone. Cleared cache on watch via recovery menu but didnt help. Tried connecting another phone but watch doesnt allow it without factory resetting. I dont want to reset watch as i have some health and watch settings data on it that hasnt been backed up yet. There is an adb trick to connect wearos watches to another phone without resetting but seems like it doesnt work with wearos 3. Cant manually pull the data from watch via wifi debugging either because it's not rooted. Any solution would be much appreciated. Cheers

How to pair a Wear OS smartwatch to a new smartphone without resetting it – Phandroid
phandroid-com.cdn.ampproject.org

gettinwicked said:
How to pair a Wear OS smartwatch to a new smartphone without resetting it – Phandroid
phandroid-com.cdn.ampproject.org
Click to expand...
Click to collapse
Nope that trick dont work.
My Galaxy plugin today just forget how to be a plugin and stop connecting to watch restarting it does nothing so i clear data of it and oh boy i am formatting my watch right now.
That's great
PS. If anyone find some solution for this let me know xD i have a feeling that i might need it in the future

How To Guide GW4 "this watch isn't supported on this phone"

Hello,
I have recently purchased GW4 Classic, and had the "this watch isn't supported" message, It drove myself and appears others also nuts and frusterated, but the best solution is below.
If you have purchased a GW4 Watch and your device is either from a different country than your phone, or a different brand you will have a "region/device" lock the watch. When you use the Galaxy wearables app, the watch will not sync and a message "this watch isn't supported on this device" will appear.
There is a great and somewhat easy workaround that has been floating around the internet but it missed one very key important detail, don't try to use samsung health to connect, it will just fail.
Workound:
Apps - Wearos app
Galaxy wearables app
Steps:
1) go to wearos app settings
2) open Galaxy wearables
3) open wearos and try to connect your device, quickly switch to wearos app settings, and force stop "kill: wear os before the sync code appears on your phone and watch.
4) after force kill of the wear os, just continue on Galaxy wearables app.
and it will setup your device.
I hope this helps.

What do you mean by dont change page?

When i open wearOS it would ask me to link and pair my galaxy watch. Should i pair it then go to settings and force stop the app?

weng_cas said:
What do you mean by dont change page?
Click to expand...
Click to collapse
I mean just open the app, don't go to the sync page

weng_cas said:
When i open wearOS it would ask me to link and pair my galaxy watch. Should i pair it then go to settings and force stop the appointment the
Click to expand...
Click to collapse
weng_cas said:
When i open wearOS it would ask me to link and pair my galaxy watch. Should i pair it then go to settings and force stop the app?
Click to expand...
Click to collapse
When wearos asks to sync, force close before the sync code pop-up on your watch

I somehow solve the problem "this watch isn't supported on this phone"
But my watch is purchased from China, so I cannot connect to my google account.
Any solution to this?

jazzpasta said:
I somehow solve the problem "this watch isn't supported on this phone"
But my watch is purchased from China, so I cannot connect to my google account.
Any solution to this?
Click to expand...
Click to collapse
Could you please let me know how you solved it? I also has Chinese version Galaxy watch 4 classic. But my phone is SM-G977N (Korea version), so I can't connect my watch to my phone.

jazzpasta said:
I somehow solve the problem "this watch isn't supported on this phone"
But my watch is purchased from China, so I cannot connect to my google account.
Any solution to this?
Click to expand...
Click to collapse
I have the same issue，I believe it's something to do with the OS maybe doesn't have Google services like most devices here

phoenix377 said:
Could you please let me know how you solved it? I also has Chinese version Galaxy watch 4 classic. But my phone is SM-G977N (Korea version), so I can't connect my watch to my phone.
Click to expand...
Click to collapse
My watch and device is same as yours, use wearos to initialize the pairing but quickly force close it before the watch displays a pop-up to connect the watch, switch over to galaxy wearables and go through the steps as usual. Any problems then it's the timing of closing wearos

flor00451 said:
My watch and device is same as yours, use wearos to initialize the pairing but quickly force close it before the watch displays a pop-up to connect the watch, switch over to galaxy wearables and go through the steps as usual. Any problems then it's the timing of closing wearos
Click to expand...
Click to collapse
I tried it, but it's not working.
Could you please let me know your OS version, Galaxy wear app version and wear os app version?
Thanks.

phoenix377 said:
I tried it, but it's not working.
Could you please let me know your OS version, Galaxy wear app version and wear os app version?
Thanks.
Click to expand...
Click to collapse
Sure, I can tell you that, but it's mostly the timing issue, you need to be very quick before your phone and watch gives you a sync code, basically as soon as wearos finds your device and you change pages to sync you should switch over to the app control and kill the app process
Phone: Android 12, UI 4.0
Wearos: V.2.52
Galaxy wearable: V.2.247

Mine is back working now. I just uninstalled gpay on the watch and reinstalled it, try it for yourselves

flor00451 said:
Sure, I can tell you that, but it's mostly the timing issue, you need to be very quick before your phone and watch gives you a sync code, basically as soon as wearos finds your device and you change pages to sync you should switch over to the app control and kill the app process
Phone: Android 12, UI 4.0
Wearos: V.2.52
Galaxy wearable: V.2.247
Click to expand...
Click to collapse
Finally, I succeed at connecting my watch following your instructions.
Thanks.

phoenix377 said:
Finally, I succeed at connecting my watch following your instructions.
Thanks.
Click to expand...
Click to collapse
Glad it helped

flor00451 said:
Glad it helped
Click to expand...
Click to collapse
Sorry to bother you, but I'm new to this and I'm not sure if I understand correctly.
If I manage to connect Chinese watch to the app this way, it will change geo location of the watch?
Because I managed to connect it (had the same error) by pairing watch with phone (in Bluetooth menu) and then quickly clicking on the watch in the Samsung app.
But it remained a Chinese version without any Google services, and trying to connect to the Chinese Samsung website for signing in to the account (with error I must add)

mWatcher said:
Sorry to bother you, but I'm new to this and I'm not sure if I understand correctly.
If I manage to connect Chinese watch to the app this way, it will change geo location of the watch?
Because I managed to connect it (had the same error) by pairing watch with phone (in Bluetooth menu) and then quickly clicking on the watch in the Samsung app.
But it remained a Chinese version without any Google services, and trying to connect to the Chinese Samsung website for signing in to the account (with error I must add)
Click to expand...
Click to collapse
mWatcher said:
Sorry to bother you, but I'm new to this and I'm not sure if I understand correctly.
If I manage to connect Chinese watch to the app this way, it will change geo location of the watch?
Because I managed to connect it (had the same error) by pairing watch with phone (in Bluetooth menu) and then quickly clicking on the watch in the Samsung app.
But it remained a Chinese version without any Google services, and trying to connect to the Chinese Samsung website for signing in to the account (with error I must add)
Click to expand...
Click to collapse
This way is just to connect to a non Chinese phone, of course the watch will remain Chinese because of the OS, not because region lock

Question cant connect google account to watch ( couldn't copy your google account error) FIXED !!!!!

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

General Unable To Connect Watch 4 [Samsung Android 13/OneUI 5.0]

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.