Related
MY gear manager just updated and after update it crashed. I uninstalled and and went to reinstall it and its no longer in the samsung app store.
raiu said:
MY gear manager just updated and after update it crashed. I uninstalled and and went to reinstall it and its no longer in the samsung app store.
Click to expand...
Click to collapse
Try factory resetting your watch, rebooting your phone, and checking again. Make sure that your galaxy app has updated and your phone is updated to the latest software os
I too can't find it in the app store.
Does anyone have a link to the most recent version's apk? It worked great for me with tizenmod 3.0
edouble312 said:
I too can't find it in the app store.
Does anyone have a link to the most recent version's apk? It worked great for me with tizenmod 3.0
Click to expand...
Click to collapse
yup, did all that and then some. Still doesnt show in the samsung app store
I've reverted to this gear manager from July, seems to be working fine with notifications. I'd still like the most recent working apk, I think it was from october. obviously the new update broke something, so they're in the process of fixing it and releasing another update (at this point, gear manager is not in the galaxy app store)
Working with GN4, Tizenmod 3.0:
http://www.mediafire.com/download/ex3ddaf7q4q9f1g/Gear+Manager_2.1.14071502.apk
edouble312 said:
I've reverted to this gear manager from July, seems to be working fine with notifications. I'd still like the most recent working apk, I think it was from october. obviously the new update broke something, so they're in the process of fixing it and releasing another update (at this point, gear manager is not in the galaxy app store)
Working with GN4, Tizenmod 3.0:
http://www.mediafire.com/download/ex3ddaf7q4q9f1g/Gear+Manager_2.1.14071502.apk
Click to expand...
Click to collapse
Im trying this. I book marked it a while back and forgot where I found it on XDA but thanks to who every is keeping up with it
https://www.mediafire.com/folder/e7h23e12rzesi//Gear Manager
raiu said:
Im trying this. I book marked it a while back and forgot where I found it on XDA but thanks to who every is keeping up with it
https://www.mediafire.com/folder/e7h23e12rzesi//Gear Manager
Click to expand...
Click to collapse
whoa, awesome! I'll probably run with the July build, for now anyway. seems fine. let me know how your device turns out.
I got the update yesterday. Post update gear manager crashes on clicking settings. So much for QA by samsung.
Embarrassing for them.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
raiu said:
Im trying this. I book marked it a while back and forgot where I found it on XDA but thanks to who every is keeping up with it
https://www.mediafire.com/folder/e7h23e12rzesi//Gear Manager
Click to expand...
Click to collapse
Every time I try to use a previous build it automatically updates to the newest broken build.
Sent from my Nexus 7 using xda premium
When the gear manager wants to update, bring up the task list and swipe it away. Launch it again and it won't ask to update.
Sent from my SM-N900A using Tapatalk
just a heads up, I uninstalled it again today and it showed in the app store and I reinstalled it and its back to working like normal. There is now an emergency notification system built in to the watch and the settings are in that menu.
I've been having the same problems. Firsrgear manager was crashing when trying to open settings. Then it wouldn't open at all. I uninstalled and reinstalled complete with full wipe and still nothing. I used the other build that someone provided a few posts back and that works for now. But now I'm noticing that the other watch face apps I use (MW and WS) have disappeared from the app store. Had anyone else noticed this?
Side question. I'm new to the gear 2, just purchased last week. If I was to reroot the gear and find an MW apk, is there a way to side load the MW apk without using the phone but still have the phone recognize it?
Newer Version makes it worse.
How do you keep the old version running when the warning box forces you to install the newest crap version that won't allow the connection? Mine is a brand new Black Friday Gear 2 Neo that was working fine at first, then wouldn't hold the connection. Now it won't connect at all. December update? I downloaded an older version and got them to connect, had everything connecting with the old version and then my phone got commandeered and the newest version just installed.
[email protected] said:
How do you keep the old version running when the warning box forces you to install the newest crap version that won't allow the connection? Mine is a brand new Black Friday Gear 2 Neo that was working fine at first, then wouldn't hold the connection. Now it won't connect at all. December update? I downloaded an older version and got them to connect, had everything connecting with the old version and then my phone got commandeered and the newest version just installed.
Click to expand...
Click to collapse
I kept the old version from this post:
http://www.tizenexperts.com/2014/09...092299-do-you-still-have-problems-need-a-fix/
I keep cancelling the notification to upgrade and it's fine.
kc2kzz said:
When the gear manager wants to update, bring up the task list and swipe it away. Launch it again and it won't ask to update.
Sent from my SM-N900A using Tapatalk
Click to expand...
Click to collapse
Thanks for the thought. I spent 3 hours a couple of nights ago with a nice Samsung tech who tried everything and then admitted he had had 4 calls that day from people whose Gear 2 would not connect to their phone after the latest (December 1, 2014) update. So in spite of all the updates, Samsung keeps making things worse instead of better.
The idea of swiping it off hasn't worked for me on my Note 3. But I have developed a workaround (not a solution) similar to the Ipse_Tase suggestion just above. I downloaded a really old version of Gear Manager at http://www.mediafire.com/download/yo17ta4qyrx50zj/GearManager1_2.apk , installed it, paired the device to the watch, and a connection was established. If you try to actually open the old Gear Manager after the pairing you will get a threatening warning screen saying they're going to delete everything from your Gear 2. But if you just leave the Gear Manager open and running with the warning screen on (don't click cancel or OK), use the phone normally with Gear Manager running, you can use the pre-installed Samsung programs on the watch. If I click cancel the Gear Manager closes and I have to start over. You can turn off automatic updates in the Galaxy App Store, but you'll still get the threatening message that they're going to hard reset your Gear 2. Just leave the message on the screen, let the program run, and use whatever other programs you want to on the phone.
Advantages: Your Gear is not a brick or just a time piece. You are paired. You're not hard resetting the device or trying to pair and connect all the time. You have access to Schedule, Notifications, Weather, Phone functions, S Voice, anything Samsung-based. You can control any app that can be adjusted from the watch itself.
Disadvantages: You can't change or adjust any app that would have to be done from the phone. Third party apps don't work because you can't use the Galaxy App store to get them or install/run them.
But it's better than nothing until Samsung gets its act together and provides an update that actually improves things rather than bricking your watch.
Has anyone found a way to actually use an older version of Gear Manager to download apps, manage the watch, etc. since all the recent updates seem to cut off the bluetooth connection?
Fluke Recovery
I decided to try to install the newest Samsung update to Gear Manager one more time--just to get a log to send to Samsung. Cleared Bluetooth pairing, uninstalled everything, reinstalled newest version. Failed several times, then finally paired, then finally ran through the bootup process and I am now connected and reinstalling programs, pictures, etc. on the Gear 2 Neo. We'll see how long this lasts. I'll keep you posted. For now, I'm illogically hopeful.
Refusing to connect again.
[email protected] said:
I decided to try to install the newest Samsung update to Gear Manager one more time--just to get a log to send to Samsung. Cleared Bluetooth pairing, uninstalled everything, reinstalled newest version. Failed several times, then finally paired, then finally ran through the bootup process and I am now connected and reinstalling programs, pictures, etc. on the Gear 2 Neo. We'll see how long this lasts. I'll keep you posted. For now, I'm illogically hopeful.
Click to expand...
Click to collapse
Bad news. Back to square 1. The newest (December 1) update to Gear Manager is no good for Gear 2 Neo with Galaxy Note 3. It will pair and you can get a brief bluetooth connection from the watch to the phone, and sometimes even from the phone to the watch. But it disappears after about 60 seconds. I'm sure it's the Gear Manager update. You can get certain apps to work during the brief periods of connection, but you can't do any settings from the phone, or use the Gear App store through the Gear Manager.
Does anyone know a way to uninstall or bypass the current new version of Gear Manager and install an older version alongside it? If I uninstall it I have learned from bad experience that it will hard reset the watch and I will lose all the time I have spent (3-4x in the last 3-4 days) setting it up. And worst of all, it will delete all Gear Apps that I have paid for from the phone, and I will have to reinstall them whenever I get a connection, and set them all up again.
Workaround
As I was suggesting last night, the best workaround I can come up with is still to install the older version (linked above) by APK, and then leave the warning message running. This way you can get a steady bluetooth connection for as long as you need it, and you can operate all Samsung apps and some 3rd party apps too. You can't, however, use the Gear Manager. You can only make changes/adjustments that can be done from the watch. But it's better than nothing until Samsung gets its act together.
[email protected] said:
As I was suggesting last night, the best workaround I can come up with is still to install the older version (linked above) by APK, and then leave the warning message running. This way you can get a steady bluetooth connection for as long as you need it, and you can operate all Samsung apps and some 3rd party apps too. You can't, however, use the Gear Manager. You can only make changes/adjustments that can be done from the watch. But it's better than nothing until Samsung gets its act together.
Click to expand...
Click to collapse
Just FYI, I got the same setup as you and out of curiosity I DID update Gear Manager (now called Samsung Gear) to get a fully functional S Health (also updated)...seems to be working fine so far. Even Watch Styler still works.
Sounds like I should try it
Ipse_Tase said:
Just FYI, I got the same setup as you and out of curiosity I DID update Gear Manager (now called Samsung Gear) to get a fully functional S Health (also updated)...seems to be working fine so far. Even Watch Styler still works.
Click to expand...
Click to collapse
Thanks for this tip. I think you mean that you went ahead and ran the update on the new version (December 1?). Or do you mean you ran an update on the older version I mention above? I'd like to try it to see if they've gotten rid of the bug. Are you saying everything seems to be working fine and your phone updated acceptably?
---------- Post added at 07:08 PM ---------- Previous post was at 07:07 PM ----------
[email protected] said:
Thanks for this tip. I think you mean that you went ahead and ran the update on the new version (December 1?). Or do you mean you ran an update on the older version I mention above? I'd like to try it to see if they've gotten rid of the bug. Are you saying everything seems to be working fine and your phone updated acceptably?
Click to expand...
Click to collapse
Also curious about how long you have been running the new update. It worked for me for about 12 hours--then would not connect after that....
Hi
Since I've woken up I've had trouble logging into the store. It keeps asking me for a password and sometimes says it's wrong, even though it's been reset. If I enter the 'watch faces' menu in the Gear app on my phone, it hangs forever, installing watch faces also fails, they install forever. I have deleted the app, soft reset the watch and reinstalled, still the same problem.
Is anyone else having this today? I've had no issues before with any of this. I'm wondering if it's something at their end. I'm on a standard non-rooted moto x, nothing has been changed since yesterday.
I'm also having problems connecting to the Gear App Store from Gear Manager on my Galaxy S4. It gives me an error that there is "No network connection". Funny, all my other apps get on the network just fine. I have a strong signal on a very fast WiFi network. I guess the "network connection" that is broken is at their server(s).
I'm having trouble too. The gear app seems to work fine until I try to download a watch face or other app. Then I just get a message that day no response, times out. Haven't been able to download from the gear store for 3 days now. I'm on pure nexus....
I have an other issue: totally blank and empty Gear Apps Store. Everything else works fine for me (notifications, S health, settings in Gear app).
I installed Samsung Gear, Gear plugin, Samsung Accessories Service, S Health from Play Market without any problems.
http://forum.xda-developers.com/gear-s2/help/blank-empty-samsung-gear-app-store-t3275190
Hi all, I just picked up the lovely S3 Frontier.
When I click "view watch faces" or "view more apps" in the gear app
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 Gear app, the Gear S Plugins and Samsung Accessory Service. Rebooted the S3.
Reinstalled everything but the error remains.
For the rest, everything works just fine.
I can't find anything googling so any help would be greatly appreciated.
Thanks in Advance!!!
blackspp said:
Hi all, I just picked up the lovely S3 Frontier.
When I click "view watch faces" or "view more apps" in the gear app
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 Gear app, the Gear S Plugins and Samsung Accessory Service. Rebooted the S3.
Reinstalled everything but the error remains.
For the rest, everything works just fine.
I can't find anything googling so any help would be greatly appreciated.
Thanks in Advance!!!
Click to expand...
Click to collapse
I've no problems so far with my Gear S3 Frontier in combination with my Samsung Galaxy S7Edge...
To what phone are you connected? Probably not a Samsung product?
If not: Gear Apps Store is part of "Galaxy Apps": maybe Galaxy Apps must be installed too on your device? "Samsung Account"?
Hi, mate 9. Everything else is working fine. I'll install galaxy apps, see what that does, thanks.
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!
I'm having the exact same problem, only for me it doesn't go away after a reset. I've tried resetting all apps, even reinstalling them, resetting the S3, restarting my phone, but nothing seems to work. I can install apps from the watch itself just fine (just the 10 suggestions), but the Gear app just doesn't work.
I did all that after which it worked but I did do something else in between.
I downloaded the galaxy apps apk, from somewhere, ran it but it said no go, only run on Samsung phones.
Maybe that app flipped a bit somewhere, who knows!
I have a similar issue, get a pure white screen on the gear phone app. When I try and load the apps store. Fixed it by resetting watch deleting all the samsung apps, and then reinstalling and re setting everything up. It worked for about a day, and then failed in exactly the same way. I give up with this device, and I shall not be wasting another 30 mins doing the same long-winded process again. Samsung makes nice hardware, but as usual, the software is crud!
I note that Samsung changed the website end of the gear apps store the other day - looks like they fouled it up and have not bothered to fix it yet.
Mine has been working just fine after fixing it and I'm on the gear app store a lot at the moment fooling around with new stuff.
I do agree with you, Samsung is the worst sw developer. Take a look at my 3000 bucks smart tv, it's such a mess!
Mine 'fixed' its self this morning. The white screen is where the app loads content web browser style, they fouled something up server side is my guess. It still fails sometimes, and getting any app to actually install requires several attempts. Pish software.
Sent from my SGP621 using Tapatalk
i just got my Gear S3 and i'm having the same problem how did you guys fixed this?
Thanks in advance
Any fix for this problem???
I had this issue as well. Some apps or watchfaces would install but most wouldn't. I connected phone and watch to home WiFi and everything installed. I have Sprint LG v30+ paired with watch. Over the network, it's hit or miss but on WiFi all seems to work.
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