Hi,
I am trying to pair a Redmi Note 4 with a Samsung Gear S2 watch.
I've installed "Galaxy Wearable" app, "Gear S Plugin" and "Samsung accessory service" on the phone.
The phone finds the watch and starts pairing. They exchange PINs and I accept pairing with the same BT pin code.
Then it starts pairing process but it never ends.
What is wrong ?
mrmrmrmr said:
Hi,
I am trying to pair a Redmi Note 4 with a Samsung Gear S2 watch.
I've installed "Galaxy Wearable" app, "Gear S Plugin" and "Samsung accessory service" on the phone.
The phone finds the watch and starts pairing. They exchange PINs and I accept pairing with the same BT pin code.
Then it starts pairing process but it never ends.
What is wrong ?
Click to expand...
Click to collapse
Since no one answered. I will start with the basics. Have you reset the watch? Maybe try clearing apps caches for the 3 apps and any bluetooth related apps.
I have somewhere in this thread a link to versions of the apps needed as well. You might try those.
Maybe even try pairing in bluetooth settings first then gear app.
From my understanding it can be real finicky with non Samsung's.
TheMadScientist said:
I have somewhere in this thread a link to versions of the apps needed as well. You might try those.
Click to expand...
Click to collapse
which thread ?
the process requires resetting the watch so I did not reset additionally (maybe hard reset would help, I'll try)
I've deleted and reinstalled all 3 apps, so that covers clearing the cache and data of apps.
what else can I try ?
mrmrmrmr said:
which thread ?
the process requires resetting the watch so I did not reset additionally (maybe hard reset would help, I'll try)
I've deleted and reinstalled all 3 apps, so that covers clearing the cache and data of apps.
what else can I try ?
Click to expand...
Click to collapse
https://forum.xda-developers.com/gear-s2/development/1-5-gb-ram-bypass-gear-app-t3775732
Yea resets may do it too these watches can be picky sometimes
Related
hi,
until last night everything was ok
but today
(it is a coincidence, the update?)
after upgrading my Gear S2 (R720) (all right),
when I want to go to "see other watches dials" or "see other applications"
the Samsung Gear APP, after a quick "loading", displays white screen with error
"{"returnCode":"0","errorCode":"0003","errorMsg":"System Error!-[0003]"}"
for the rest, everything works.
I uninstalled the APP, the Gear S Plugins and Samsung Accesory Service. Also formatted Gear S2.
reinstalled everything but the error remains.
for the rest, everything works.
what could have happened?
thank you
I just picked up my Gear S3 (great!!) and I have the exact same error when clicking 'view more watchfaces' and 'view more apps'.
Any help greatly appreciated because on the internets I can't find anything (((
Fixed it by deleting all Samsung apps cache on the phone. This results in a soft reset on the watch. After re-pairing it works!
You don't have to reset your watch. Just wait and try again later. Looks like the server problem of the Gear shop. From time to time I get the same error, but after a while (20-30 minutes later) everything works fine.
thank you all
blackspp said:
Fixed it by deleting all Samsung apps cache on the phone. This results in a soft reset on the watch. After re-pairing it works!
Click to expand...
Click to collapse
done. but it does not work
mikekorn said:
You don't have to reset your watch. Just wait and try again later. Looks like the server problem of the Gear shop. From time to time I get the same error, but after a while (20-30 minutes later) everything works fine.
Click to expand...
Click to collapse
are more than 24 hours that does not work
we are not the only ones: in playstore there are already several complaints about this problem
Still working here, just checked
exact same problem on s2
Now fixed. Not even sure if what I did was the reason for the fix but here goes. Removed all relevant gear apps from my Nexus 6p and switched off. Switched on my old nexus 5 and paired with s2 installing Samsung apps as necessary. Light reset and once logged in all worked. Could see all my apps and could download. Then did the reverse back to my nexus 6p and it is all working fine again.
update: the third time, that uninstalling / reinstalling the app, everything is back to work
I own the following devices.
Xiaomi RedMi Note 3 Pro
android 5.1.1LMY47V
MIUI 7.5.1.1
Gear Fit2 SM-R360
software R360XXU1BPG3eChO
I installed the
Gear 2.2.16101261
Gear Fit2 Plugin 2.2.04.16111741N
Samsung accessory service 3.1.26_161116
I perform the pairing proccess from gear app where it normally sees the request and then the gear (app from mobile) is closed without any message and gear fit2 stays on screen writing "setting up" where nothing else happening and at the end sent message that "the setting has lasted more than expected. Do you want to try again; "
For the above issue I have tried the following:
1)
Remove all Samsung app's
cache cleaning
Factory reset gear fit2
Reinstalling app's
2)
Remove all Samsung app's
cache cleaning
Factory reset gear fit2
Reinstalling previous versions
Please HELP
My pebble kept disconnecting. I think it was due to permissions. I'd recommend making sure the gear fit app can autostart, use Bluetooth and stay active.
How
doncoop said:
My pebble kept disconnecting. I think it was due to permissions. I'd recommend making sure the gear fit app can autostart, use Bluetooth and stay active.
Click to expand...
Click to collapse
The thing is that i am trying to do this without any succes.
Anyone knows a way?
Thanks for reply
Got my S8+ at launch, reset my Gear 2 running Tizen and quickly had it paired using both the Gear app and Samsung Health.
Everything was running just fine until a about a week ago when the pairing stopped. I decided to reset the Gear 2 and re-pair it to my S8+.
After several unsuccessful tries, here's what happens:
1. Reboot phone and wait for boot to complete.
2. Start the Gear app (v2.2.17022862) on the phone.
3. From the Gear app select "Connect new Gear."
4. Power on the Gear 2 and select "Next / Next"
5. Back to the app on the phone select "Gear 2 (XXXX)"
6. Get a Blue tooth pairing request on both devices and confirm on both of them.
7. The Gear 2 shows "Waiting for confirmation from Gear Manager" and the Gear app on the phone shows "Connecting to Gear..."
8. Minutes pass and nothing else happens.
IOW, the Bluetooth pairing is successful but the actual link between the devices never finishes.
Any idea what I might try next to get this working?
TIA,
RIch
Having similar issue. eventually got a connection failed. This worked originally then I did the OTA update (I have an unlocked S8+) and the Bluetooth started acting up.
One post said unpair everything and now I cant get the phone to reconnect. Eventually Bluetooth recognizes the Gear2 and the Gear Manager (as disconnected).... and the watch stays in that factory reset mode.
Not sure exactly how, but I got mine working. After unpairing the Bluetooth connection, I also cleared the cache and data on both the Samsung Gear app and the Samsung Health app then removed both apps from my S8+ rebooting many times along the way. After reinstalling the Gear app and the Health app I was able to eventually get the pairing to be successful.
Sorry I can offer better detailed guidance. I hope you get yours working again too.
Thanks... I tried clearing S-Health's\Samsung Connect cache, unpairing the watch, deleting Gear Manager, and restarting. That didn't work. I'll give it another try.
Just out of curiosity, have you disabled anything like Bixby or Svoice? I have both disabled... I tried reenabling them before but that didn't help.
Nope. While I don't use either, both Bixby and SVoice remain active. Sorry I can't help more.
Yesterday afternoon my Gear S3 disconnected spontaneously from the phone (Redmi Note 8T) as it does from time to time and I haven't been able to reconnect or pair it again ever since.
I reset the watch, uninstalled and reinstalled the phone app but the pairing never finishes. It goes through the motions both on the phone and the watch, the watch appears in the list of paired BT devices but it always comes up with "Connection failed. Try again." on the watch and goes back to "Pick your device" on the phone app. I am at the end of my witts with this one.
Can anyone help?
I am experiencing the exact same thing, it started this morning. I did install a new ROM last night, no issues so its possible that is related but I'm not seeing anything on the ROM forum about this issue. Did you install a new ROM recently?
archael said:
I am experiencing the exact same thing, it started this morning. I did install a new ROM last night, no issues so its possible that is related but I'm not seeing anything on the ROM forum about this issue. Did you install a new ROM recently?
Click to expand...
Click to collapse
I am just running everything stock, so there may have been an official update to either the Tizen or Galaxy Wearable app in the background but nothing that I have done.
Yeah it seems like it, well I'm glad to know I didn't directly cause it, before your post I wasn't seeing this issue anywhere. I saw some posts from years ago but were fixed with minor changes that didn't work for me.
SOLVED.
FYI this has been resolved.
It was the Samsung Health app on the phone that was hogging the pairing for some reason. In desperation and trying everything possible I removed and reinstalled the Health and after that the S3 paired no problem.
I was very hopeful when I read your message! But that was not my problem. I tried reinstalling and no dice, tried uninstalling and trying to pair and still no luck. I'm glad yours is working now!
paulmin said:
SOLVED.
FYI this has been resolved.
It was the Samsung Health app on the phone that was hogging the pairing for some reason. In desperation and trying everything possible I removed and reinstalled the Health and after that the S3 paired no problem.
Click to expand...
Click to collapse
archael said:
I was very hopeful when I read your message! But that was not my problem. I tried reinstalling and no dice, tried uninstalling and trying to pair and still no luck. I'm glad yours is working now!
Click to expand...
Click to collapse
Try this, it worked for me:
Find "Gear S Plugin" app in All Apps List, force stop, then clear cache, clear data
Remove your Gear S3 from Bluetooth paired device
Uninstall, reinstall both Samsung Health and Galaxy Wearable apps
Restart your Gear S3 and go through setup steps in Galaxy Wearable app again
ardennguyen said:
Try this, it worked for me:
Find "Gear S Plugin" app in All Apps List, force stop, then clear cache, clear data
Remove your Gear S3 from Bluetooth paired device
Uninstall, reinstall both Samsung Health and Galaxy Wearable apps
Restart your Gear S3 and go through setup steps in Galaxy Wearable app again
Click to expand...
Click to collapse
Hey, thanks for the tip, it didn't work for me but I appreciate the attempt to assist.
It did end up being the ROM I was using, an update came out and fixed the issue.
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