hey, i've been using the Gear S3 since half a year now, after being disappointed by AW 2.0 ruining my Moto 360 2nd gen
since the 3.0 update, i often get an error using s-voice with simple commands like "set timer for ten minutes"
sometimes it works, but often getting an error after a few seconds, show either "an error has occurred. i'm unable to answer your question. please try again later" or "an error has occured, try again later"
has anyone else encountered this problem and found a fix?
i did a factory reset twice now, didn't help, not changing the s voice language from automatic to us english
the other stuff i wanted from the update also didn't happen, but i guess that's a different discussion
I am having the same problem. I had purchased the S3 Frontier when it 1st came out. I returned it due to problems with svoice. I just purchased it again last week and svoice is still garbage. Was hoping for it to be better. Will be returning again.
i did not have this problem with 2.x, voice commands like this never showed the error, for me it started after the 3.0 update
Same problem here can't reply to a message with voice and errors when simple commands like the OP stated.
I get around the message problem by setting the language to English UK
I still get the error message after the latest update on the gear update. I need to re-flash the stock Tezin on it hoping it will fix it.
Same issue with S3 Classic
Same issue here with my S3 Classic. Occasionally it works but most of the time I get the error. Reported it to Samsung but they were unaware of the issue and were non-responsive.
View attachment 4365678my fix for this issue was to clear cache for s-voice. you can do it from s-voice menu
bottom button that looks like refresh
Same x 2
My S3 Tmobile LTE failed in 6 days. They exchanged it for a new one at the store yesterday and that one failed also. So I returned it since it's a defective product. I'll buy again when the issue is fixed.
S-Voice implementation on the watch is just total garbage. No way around it.
I like the notification system and the magnetic payments, but nothing is intuitive and nothing can be trusted to just work without having to re-try three times. Voice commands are an exercise in frustration.
Nine times out of ten, my watch says it can't understand me, can't find the contact I want or can't find any contacts at all even though I can open contacts on the watch and they're all there. I'm sitting here with a Galaxy s8+ and their flagship Gear S3 Classic watch and they don't complement each other at all.
Implement FREAKING GOOGLE ASSISTANT you lamebrains!
WaxysDargle said:
View attachment 4365678my fix for this issue was to clear cache for s-voice. you can do it from s-voice menu
bottom button that looks like refresh
Click to expand...
Click to collapse
how often to you have to clear out the s-voice ??
matthewinaz said:
how often to you have to clear out the s-voice ??
Click to expand...
Click to collapse
Every time you want it to work.
gboybama said:
S-Voice implementation on the watch is just total garbage. No way around it.
I like the notification system and the magnetic payments, but nothing is intuitive and nothing can be trusted to just work without having to re-try three times. Voice commands are an exercise in frustration.
Nine times out of ten, my watch says it can't understand me, can't find the contact I want or can't find any contacts at all even though I can open contacts on the watch and they're all there. I'm sitting here with a Galaxy s8+ and their flagship Gear S3 Classic watch and they don't complement each other at all.
Implement FREAKING GOOGLE ASSISTANT you lamebrains!
Click to expand...
Click to collapse
I have the exact same experience Gboybama! Some contacts i can call, some produce an error message, some let svoice "synchronice contacts", which is never finished, letting the problem persist even after clearing cache, stopping the app, restart etc... **** this.
matthewinaz said:
how often to you have to clear out the s-voice ??
Click to expand...
Click to collapse
i only had to do it once. it has been working "fine" ever since.
s-voice never quite works properly. never has. i doubt it ever will. seems like samsung just doesn't care.
I just got my s3 today to go with my new s8+ having tons of iss6 with s voice. Looks like I'm not alone. Probably going to be returning this and researching other options.
good and bad to hear it also happens in combination with Samsung phones.
the last response i got from them:
"@SamsungSupport: There will be slight compatibility trouble considering it is not paired to a Samsung device. ^Aaron"
i removed all apps from my phone, reset the watch, reinstalled the apps and set up the watch as new. worked for a couple of days then back to the same, 9 out of 10 (or even more) it would simply give me the "an error has occurred"
i don't understand the error doesn't include an error code, how are they even supposed to understand what's going wrong with just "an error has occurred"
I'd fire the developer, project manager or whoever thought this was ab good idea
but indeed, Samsung doesn't seem to care
good and bad to hear it also happens in combination with Samsung phones.
the last response i got from them:
"@SamsungSupport: There will be slight compatibility trouble considering it is not paired to a Samsung device. ^Aaron"
i removed all apps from my phone, reset the watch, reinstalled the apps and set up the watch as new. worked for a couple of days then back to the same, 9 out of 10 (or even more) it would simply give me the "an error has occurred"
i don't understand the error doesn't include an error code, how are they even supposed to understand what's going wrong with just "an error has occurred"
I'd fire the developer, project manager or whoever thought this was ab good idea
but indeed, Samsung doesn't seem to care
Related
I have a Nexus 4 and followed the tutorial on how to get things working on it in regards to the gear. Most of the stuff works now but i have an odd issue with s-voice:
When i open it on the gear, it will run, but the first time i run it after a restart, the phone shows an error: "Unable to get VoiceEngineWrapper"
On the gear, the voice sounds distorted and pitched with some weird echo. It also replies with "I didn't catch that" to whatever command i give it.
I tried to google the error i'm getting on the phone since i'm assuming it's connected, but nothing comes up. I was trying to get the google now voice engine to replace the s-voice tts since i've heard it can be done but i can't find any info on how to do it. Only thing i found was settings-tts-download us voice and set it as default.
If anyone smarter than me has some ideas on what in the world that error means or what else to try, I would appreciate it.
Thanks!
noctrin said:
I have a Nexus 4 and followed the tutorial on how to get things working on it in regards to the gear. Most of the stuff works now but i have an odd issue with s-voice:
When i open it on the gear, it will run, but the first time i run it after a restart, the phone shows an error: "Unable to get VoiceEngineWrapper"
On the gear, the voice sounds distorted and pitched with some weird echo. It also replies with "I didn't catch that" to whatever command i give it.
I tried to google the error i'm getting on the phone since i'm assuming it's connected, but nothing comes up. I was trying to get the google now voice engine to replace the s-voice tts since i've heard it can be done but i can't find any info on how to do it. Only thing i found was settings-tts-download us voice and set it as default.
If anyone smarter than me has some ideas on what in the world that error means or what else to try, I would appreciate it.
Thanks!
Click to expand...
Click to collapse
I have the very same problem on a Nexus 5 device.
noctrin said:
I have a Nexus 4 and followed the tutorial on how to get things working on it in regards to the gear. Most of the stuff works now but i have an odd issue with s-voice:
When i open it on the gear, it will run, but the first time i run it after a restart, the phone shows an error: "Unable to get VoiceEngineWrapper"
On the gear, the voice sounds distorted and pitched with some weird echo. It also replies with "I didn't catch that" to whatever command i give it.
I tried to google the error i'm getting on the phone since i'm assuming it's connected, but nothing comes up. I was trying to get the google now voice engine to replace the s-voice tts since i've heard it can be done but i can't find any info on how to do it. Only thing i found was settings-tts-download us voice and set it as default.
If anyone smarter than me has some ideas on what in the world that error means or what else to try, I would appreciate it.
Thanks!
Click to expand...
Click to collapse
Same issue here. I have searched everywhere and can't seem to find any solutions. I've seen videos of people using s voice on the gear 2 with a nexus 5, but not sure what firmware versions, etc. they are using. Are there any other threads or solutions out there?
Hi There,
I am facing issue with S Voice on my Gear S3, it always say "I'am unable to process your request, try again later", it works on wake up command with no problem but when I command it to do something and the error appear, anybody have same issue? or know how to fix it? Thanks.
I connected mine directly to Wi-Fi and tried some voice commands and that fixed it, but only for a week it's gone again now. Getting cheesed off now.
Same issue here. Was working fine on Wednesday but just getting an error now.
I figured out the problem with mine. The S voice app got updated yesterday and I think something went wrong with the install. So I backed up my data through the Samsung gear app and did a factory reset on the watch. All my apps then transferred back automatically including the update for S voice which installed correctly this time.
I have noticed a "weird" error with S-Voice. If you ask it the time when it's something like #:0# (ie 4:04am). S-Voice will say the time is 4-4am. Completely ignoring the zero.
S Voice is garbage. For several days, all I've gotten is unable to process your request. Bluetooth and Wifi.
I have an issue since I upgraded to Tizen 3 that I can't find the answer for. I keep getting a recurrent message saying EAS requires a PIN to access email content. The dumb thing is I already have a PIN and the phone is set to Gear Lock with Payments only. I type in the PIN I have and re-enter it only for the message to come back again in a few minutes.
This problem is very new for me since Tizen 3 and it happens even after a factory reset. It is so annoying.
I have a corporate email on my phone but I don't understand why it keeps coming up even though I have a PIN already on the watch.
Please help!!
I have the same issue its crazy frustrating how can we fix?
Is that a new issue for you since Tizen 3 update? This has never happened to me prior to the update.
As others have said before I'm pretty unhappy with this update. I have worse battery life, the Gear VR integration hasn't worked for me, and this PIN thing is crazy frustrating.
I'm having the issue as well, and I have no corporate email, just Gmail. This only started happening after the Tizen 3.0 update and has persisted through a device hard reset.
One thing I'm wondering is if my watch strap is causing the issue. It seems Tizen 3.0 is handling things differently with determining if you're wearing the watch by relying on the heart rate sensor. I think it relied on gyroscope before. All I know is my NATO strap suddenly prevents AOD entirely and notifications only work if I set it to show them even when I'm not wearing the watch. I'm guessing the strap running between the watch and my wrist might be causing the PIN issue because it thinks I'm taking my watch off.
The thought about the strap is an interesting one and one I thought may be at play as well. It would be a disaster if that is what is causing it because I don't know if there is a good fix for that.
Anyone recommend any straps that potentially could fix this problem?
arjuna_ said:
The thought about the strap is an interesting one and one I thought may be at play as well. It would be a disaster if that is what is causing it because I don't know if there is a good fix for that.
Anyone recommend any straps that potentially could fix this problem?
Click to expand...
Click to collapse
I just put a regular strap back on and AOD and notifications work normally now. Unfortunately it doesn't affect the issue in this thread. Even with a regular band that doesn't go between the watch and my wrist I'm still getting the EAS PIN issue.
Seems like there is NO solution to this problem. I'm about to sell this it's driving me nuts.
Knock on wood, I just updated to Beta 6 Oreo on my GS8+ and have not yet seen this error.
Clear your phone's app data
I fixed this problem a while back... I also had a problem with the gear app on my phone crashing repeatedly. I think it was by going to settings on my phone, selecting storage, internal storage, apps, Samsung gear, clear data. It will erase your steps, etc. But in my case fixed the problems. By the way, I got this fix by calling Samsung support.
Hello,
I have the Note 10+ and the new Galaxy Watch 4. Since a recent update now on the phone it says that the Samsung Galaxy watch 4 Plugin keeps stopping. I've tried wiping cache and data on the plugin, the wear app on the phone, wiping cache and dalvik, going back to the last version all without any resolution. I'm wondering if anyone else has run into this and if there's a fix for it.
Thanks in advanced
drivel2787 said:
Hello,
I have the Note 10+ and the new Galaxy Watch 4. Since a recent update now on the phone it says that the Samsung Galaxy watch 4 Plugin keeps stopping. I've tried wiping cache and data on the plugin, the wear app on the phone, wiping cache and dalvik, going back to the last version all without any resolution. I'm wondering if anyone else has run into this and if there's a fix for it.
Thanks in advanced
Click to expand...
Click to collapse
I'm having the same problem on a Note 20 ultra.
The watch is discovered by my phone. They Bluetooth pair just fine, but I can never get past the "Agree" screen to actually get the watch connected to galaxy wear before the app crashes.
- Removed and uninstalled the Galaxy Watch Plugin (for the 2018 model)
- Unpaired my Galaxy watch (2018)
- Uninstalled Smart Things (Suggestion on another forum)
- Uninstalled Android System Webview (suggestion on another forum)
- Factory reset my phone and did not restore
Nothing I do works, Samsung support was rude to say the least. They are replacing the watch as that's what they suspect the problem is.
I suspect crappy app development.
BadSquishy86 said:
I'm having the same problem on a Note 20 ultra.
The watch is discovered by my phone. They Bluetooth pair just fine, but I can never get past the "Agree" screen to actually get the watch connected to galaxy wear before the app crashes.
- Removed and uninstalled the Galaxy Watch Plugin (for the 2018 model)
- Unpaired my Galaxy watch (2018)
- Uninstalled Smart Things (Suggestion on another forum)
- Uninstalled Android System Webview (suggestion on another forum)
- Factory reset my phone and did not restore
Nothing I do works, Samsung support was rude to say the least. They are replacing the watch as that's what they suspect the problem is.
I suspect crappy app development.
Click to expand...
Click to collapse
I finally got mine to work. Is your phone stock or is it rooted and bootloader unlocked? I found that my issue was actually due to a plugin or whatever in magisk, once I disabled it, I was able to set everything up fine!
drivel2787 said:
I finally got mine to work. Is your phone stock or is it rooted and bootloader unlocked? I found that my issue was actually due to a plugin or whatever in magisk, once I disabled it, I was able to set everything up fine!
Click to expand...
Click to collapse
No, not rooted just stock from my carrier. I'm legit ready to just send it back and look for a galaxy watch (2018) with LTE
BadSquishy86 said:
No, not rooted just stock from my carrier. I'm legit ready to just send it back and look for a galaxy watch (2018) with LTE
Click to expand...
Click to collapse
I don't blame you. Have you looked at the plugin version and seen if you can roll back to a later apk to test it? Cleared cache/data and uninstalled and reinstalled? Any weird third party apps installed?
drivel2787 said:
I don't blame you. Have you looked at the plugin version and seen if you can roll back to a later apk to test it? Cleared cache/data and uninstalled and reinstalled? Any weird third party apps installed?
Click to expand...
Click to collapse
I was suspecting third party apps so I just factory reset and uninstalled and many apps as I was allowed to uninstall. (Carriers here have almost no bloatware).
Unfortunately the version I have for the plugin appears to be the only version. I might be able to roll back the galaxy wear app. The only other thing I can think of is an issue with the latest update for my phone.
drivel2787 said:
Hello,
I have the Note 10+ and the new Galaxy Watch 4. Since a recent update now on the phone it says that the Samsung Galaxy watch 4 Plugin keeps stopping. I've tried wiping cache and data on the plugin, the wear app on the phone, wiping cache and dalvik, going back to the last version all without any resolution. I'm wondering if anyone else has run into this and if there's a fix for it.
Thanks in advanced
Click to expand...
Click to collapse
I have similar issue and no resolution. My phone is OnePlus 7T Pro and the Galaxy Watch4 plugin keeps crashing if I try to open Galaxy Wearable app. This started happening only on the second evening after installing that app and pairing the watch.
I have looked at the stacktrace by sending feedback and checking the details. The stacktrace indicates my crashes have something to do with Samsung Pay which isn't even available in my country (Finland).
eldis said:
I have similar issue and no resolution. My phone is OnePlus 7T Pro and the Galaxy Watch4 plugin keeps crashing if I try to open Galaxy Wearable app. This started happening only on the second evening after installing that app and pairing the watch.
I have looked at the stacktrace by sending feedback and checking the details. The stacktrace indicates my crashes have something to do with Samsung Pay which isn't even available in my country (Finland).
Click to expand...
Click to collapse
I could for sure remove samsung pay, i don't even use it (I use google pay).
This is really dumb though, it shouldn't be this difficult to setup a watch.
eldis said:
I have similar issue and no resolution. My phone is OnePlus 7T Pro and the Galaxy Watch4 plugin keeps crashing if I try to open Galaxy Wearable app. This started happening only on the second evening after installing that app and pairing the watch.
I have looked at the stacktrace by sending feedback and checking the details. The stacktrace indicates my crashes have something to do with Samsung Pay which isn't even available in my country (Finland).
Click to expand...
Click to collapse
Interesting.... My phone has samsung pay on it but I have it frozen with Titanium backup and so far no issues here. Other than Samsung did an EPIC fail releasing this watch with no BP monitor since that's the main reason I bought it. Luckily I found a work-around here on XDA to fix that
drivel2787 said:
Interesting.... My phone has samsung pay on it but I have it frozen with Titanium backup and so far no issues here. Other than Samsung did an EPIC fail releasing this watch with no BP monitor since that's the main reason I bought it. Luckily I found a work-around here on XDA to fix that
Click to expand...
Click to collapse
No dice for me, same issue even without Samsung pay.
BadSquishy86 said:
No dice for me, same issue even without Samsung pay.
Click to expand...
Click to collapse
If I'm interpreting the stack trace correctly, the problem is that the app (Watch4 plugin) receives an invalid response or something it doesn't understand. It's trying to update something related to Samsung Pay from a server or from watch.
I guess it will get fixed with an update and hopefully soon.
PS. Next time when the crash dialog pops up could you press the report button and then check the details of what would get sent? In the details there's a button to open the stack trace. Check if the first few rows mention anything about Samsung Pay
eldis said:
If I'm interpreting the stack trace correctly, the problem is that the app (Watch4 plugin) receives an invalid response or something it doesn't understand. It's trying to update something related to Samsung Pay from a server or from watch.
I guess it will get fixed with an update and hopefully soon.
PS. Next time when the crash dialog pops up could you press the report button and then check the details of what would get sent? In the details there's a button to open the stack trace. Check if the first few rows mention anything about Samsung Pay
Click to expand...
Click to collapse
After today's update to Galaxy Wearable app and to the watch the crashes are now gone. I'm trying to not touch anything Samsung Pay related in the wearable app or the watch to not trigger whatever was causing the crashes. It might still be that it's some scheduled job that only starts after a while like it did on the first time.
eldis said:
If I'm interpreting the stack trace correctly, the problem is that the app (Watch4 plugin) receives an invalid response or something it doesn't understand. It's trying to update something related to Samsung Pay from a server or from watch.
I guess it will get fixed with an update and hopefully soon.
PS. Next time when the crash dialog pops up could you press the report button and then check the details of what would get sent? In the details there's a button to open the stack trace. Check if the first few rows mention anything about Samsung Pa
Click to expand...
Click to collapse
eldis said:
If I'm interpreting the stack trace correctly, the problem is that the app (Watch4 plugin) receives an invalid response or something it doesn't understand. It's trying to update something related to Samsung Pay from a server or from watch.
I guess it will get fixed with an update and hopefully soon.
PS. Next time when the crash dialog pops up could you press the report button and then check the details of what would get sent? In the details there's a button to open the stack trace. Check if the first few rows mention anything about Samsung Pay
Click to expand...
Click to collapse
Unfortunately, it won't let me actually see the log files of what happened. Just lets me send them off to Samsung via Samsung members. I can't even view the logs there either.
They probably go off to an unmonitored inbox
eldis said:
After today's update to Galaxy Wearable app and to the watch the crashes are now gone. I'm trying to not touch anything Samsung Pay related in the wearable app or the watch to not trigger whatever was causing the crashes. It might still be that it's some scheduled job that only starts after a while like it did on the first time.
Click to expand...
Click to collapse
same problem for me still
Hi same problem here, Oneplus 7T Pro. Any fixes? It's very annoying. Tried everything except for clean wipe my phone.
solanum80 said:
Hi same problem here, Oneplus 7T Pro. Any fixes? It's very annoying. Tried everything except for clean wipe my phone.
Click to expand...
Click to collapse
For me it stopped after the watch got update and I've not touched anything Samsung Pay related since. Have you already got the watch update?
GUYS I GOT IT WORKING!!!
1) Uninstall the galaxy watch 4 plugin
2) Clear cache and atorage
3) Unpair the watch4 if it actually Bluetooth paired
3) Download and install the Galaxy Watch 3 plugin (I had to download the apk outside the ayatore)
4) setup your watch again. I was shocked when the app didn't crash.
BadSquishy86 said:
GUYS I GOT IT WORKING!!!
1) Uninstall the galaxy watch 4 plugin
2) Clear cache and atorage
3) Unpair the watch4 if it actually Bluetooth paired
3) Download and install the Galaxy Watch 3 plugin (I had to download the apk outside the ayatore)
4) setup your watch again. I was shocked when the app didn't crash.
Click to expand...
Click to collapse
Wait - you replaced watch4 plugin by watch3 plugin? While pairing Galaxy Watch 4?
had this same issue today, tried everything.
managed to fix, heres what i did
uninstalled watch manager plugin and galaxy wearable completely
install galaxy wearable
install Galaxy Watch4 Plugin_v2.2.11.21120251 apk manually
start setup and all fine, seems its an issue with the latest plugin Galaxy Watch4 Plugin_v2.2.11.22012751
all back working and paired now
hope this helps someone
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