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....
Has anyone been able to successful install new apps or update existing ones on the Samsung Gear store? I have a Oneplus One, and so far everything else has been fine. Surely there is a way to get it to work.....
itslels said:
Has anyone been able to successful install new apps or update existing ones on the Samsung Gear store? I have a Oneplus One, and so far everything else has been fine. Surely there is a way to get it to work.....
Click to expand...
Click to collapse
I have only had my S2 for two days. On the first evening, I was able to install a couple apps from the store. But since last night and all day today, I am unable to install any apps. After about 30 seconds I get "No response. Timed out"
Anyone else having this issue?
Jsalinger said:
I have only had my S2 for two days. On the first evening, I was able to install a couple apps from the store. But since last night and all day today, I am unable to install any apps. After about 30 seconds I get "No response. Timed out"
Anyone else having this issue?
Click to expand...
Click to collapse
I uninstalled all the Gear apps from my phone, reinstalled them, which prompted the phone to do a soft reset. After doing all that, I was able to install apps from the Gear store again. Not sure which part fixed things, but it's working now.
After 2 weeks of flawless operation i could no longer install apps from my Note 4 to my T-Mobile Gear S2 4g. Samsung tech unable to help me solve problem and had me send it in for repair - waiting for it's return
itslels said:
Has anyone been able to successful install new apps or update existing ones on the Samsung Gear store? I have a Oneplus One, and so far everything else has been fine. Surely there is a way to get it to work.....
Click to expand...
Click to collapse
I also uninstalled and reinstalled all the Samsung apps (Gear, Gear plug in, Accessory manager) and it prompted a soft reset on the watch. It then accepted updates to apps as well as installing apps. Good to have the functionality for going forward, but for now the appstore for the Gear S2, especially if not using a Samsung phone sucks actually.
I was getting a message saying my gear wasn't connected to the phone, and it wouldn't install any apps.
Performing a soft reset did fix this, although I did not uninstall any apps from the phone.
I am now able to install apps again.
Sent from my SM-N920T using Tapatalk
I had the time out problem and I just uninstalled/reinstalled the Gear Plugin which forced a reinstall of the Accessory service and light reset of the watch. That seemed to do the trick.
Fred
Guys i need urgent help i am rooted with magisk and have installed latest version. i have magisk hide enabled and have chosen snapchat in the options. Magisk hide perfectly works with other apps that i want to hide it from but it doesnt with snapchat. I now have been locked out of my snapchat account for 1 week and i urgently need help. i don't know what the issue is my snapchat i downloaded clean from the playstore but it keeps saying you are trying to access snapchat from third party apps. literally any help appreciated.
Thanks
Also i do not have xposed
Unroot. Install snapchat and confirm it works. Then root and hide with Magisk.
Or you can do my trick, take a backup of Snapchat (and it's data) with titanium backup, then uninstall Snapchat and restore it with Titanium Backup, I never had to put magisk hide like this for many years now and it has always worked even with rom updates and every flash of roms I did so far.
Hope it helps.
vinct94 said:
Or you can do my trick, take a backup of Snapchat (and it's data) with titanium backup, then uninstall Snapchat and restore it with Titanium Backup, I never had to put magisk hide like this for many years now and it has always worked even with rom updates and every flash of roms I did so far.
Hope it helps.
Click to expand...
Click to collapse
Do I back it up when I'm rooted or do I unroot then take a backup?
1. Uninstall snapchat
2. Flash magisk uninstaller in recovery
3. Start phone
4. Install snapchat and login
5. Reinstall magisk an enable magisk hide bevore opening snapchat
You're the first other person I've been able to find online reporting this issue. I've had the same problem and it started in December.
It doesn't seem to have anything to do with Magisk being hidden or being logged in beforehand. Even if I restore a logged in backup from another phone or unroot, log in, then root again, Snapchat force logs me out after a day or so. Then when trying to log in again, it'll say the account has been temporarily locked, and eventually if I wait long enough, I can log in again and have a message from Team Snapchat telling me my account was locked for X hours. I got up to 72 hours and gave up on Snapchat. Tried making a brand new account as well bad same thing happens.
I'm not sure what the hell they are detecting or how. I've never used any third party Snapchat clients and Magisk is the only thing I'd suspect them to be looking for. But I've no clue how and why no one else in the online world seems to be having this problem but us two... However, OxygenOS could possibly be a contributing factor in some way as we both as OP device (I have a 6T).
NarenParashara said:
FINALLY someone who has the same problem as me. OnePlus 3T here, have you guys tried uninstalling substratum?
Click to expand...
Click to collapse
no i actually don't have substratum i really don't know the problem, i unrooted and rerooted however i cant actually check because im still banned for a week from snapchat i think im just gonna give up. however no i have a new problem when i reboot the phone i get the red message saying its corrupted and may not work it still boots tho but that message is really annoying
Mofo50C said:
i did have the settings database thing but that was a long time ago and i didnt modify any settings i got it so i can take a backup of its apk and send it to a friend. (dont ask XD) but other than that no i dont even have substratum. Right also i tried unrooting it and rerooting it and now my phones giving the red message saying its corrupted and may not work properly. it still turns on but it says that at boot. Is there a way to fix this
Click to expand...
Click to collapse
You mean the screen that says "the device cannot be checked for corruption"? That doesn't mean it is corrupted. It just means through bootloader is unlocked so it can't guarantee the system hasn't been modified from stock. But that's the whole purpose of unlocking the bootloader, so you just have to live with seeing it whenever you reboot.
---------- Post added at 09:31 PM ---------- Previous post was at 09:27 PM ----------
NarenParashara said:
Then Titanium Backup, maybe?
By the way, how do you check how long you've been locked out for?
Click to expand...
Click to collapse
It's so stupid. They send you so message through Snapchat itself from "Team Snapchat", so of course, you don't know how long you were locked out for until after the fact ?
It seems to start at 12 hours and go up by 12 mkre hours each time they lock it.
Its not Titanium Backup. I have it and Snapchat with no issues (Magisk). I don't have any theme modules though.
So the other night, I uninstalled Magisk on my old OP5T bad logged into Snapchat. Its been a couple days and I am still logged in and they haven't locked my account or anything. So it seems that somehow, it is detecting Magisk on our phones, despite any attempts at hiding it. ?
I'm just absolutely puzzled by how this is only affecting a few of us. I suppose there could be more of us out there who just haven't posted about it, like myself until I came across this thread.
Something I have noticed that may help people on OOS. I have Snapchat cloned through Parallel Apps cause I have a few logins, it seems the accounts that always get banned and detect Magisk are running on the original app, the cloned app hasn't been banned once.
Snapchat can be i PITA when rooted ... Magisk Hide works currently for me on OOS 9.0.3 though.
Don't know if this changed, but it only checks for root at login. So Unrooting -> Logging in Snapchat -> Rooting with Magisk Hide enabled worked previously for me.
But right now, Magisk Hide seems to fool it even during the login process, didn't get any error message like "We can't login right now" (Which it used to say when it detected root)
Guys this is really lame. It started for me a few days ago. I have Pixel 2 XL and I am up to a week now as well. I love SnapChat. I did not have an Instagram until this happened to me the first time. Let them lose valuable active users when they are trying to secure more. The SnapChat update for Android is kind of trash from the few minutes I got to use it like. The camera already was supported on my device well. Now I cannot share multiple memories in one message from chat. I have to go to memories and individually send them. *edit: replaced a censored word with 'trash'
DevonDeception said:
Guys this is really lame. It started for me a few days ago. I have Pixel 2 XL and I am up to a week now as well. I love SnapChat. I did not have an Instagram until this happened to me the first time. Let them lose valuable active users when they are trying to secure more. The SnapChat update for Android is kind of trash from the few minutes I got to use it like. The camera already was supported on my device well. Now I cannot share multiple memories in one message from chat. I have to go to memories and individually send them. *edit: replaced a censored word with 'trash'
Click to expand...
Click to collapse
lose active users? You do understand that root users are like less then 1 or 2% so they dont really care about those uses if you can make the system more secure.
There are dozens of us! Yeah, well I am, or was pretty active. I don't disagree that we are small in numbers, and I'm not sure if the amount of people rooting is growing or shrinking. I have not installed custom ROM in years, but still root.;
My banking app seems to recognize Magisk after a couple days no matter what I do as well.
Got the same problem on my S9. Magisk 18.1 on a modified samsung ROM. Works flawlessly without magisk, pretty much instant account-lock when I install it. Hide or not, doesn't matter.
Ok so I read this whole thread up to now and I have the exact same issue with an Xperia XZ Premium. Now I only rooted and unlocked my bootloader around a week ago. Prior to this when I was on oreo I used the Andromeda substratum non root method and even modified the theme on Snapchat without issues no ban what so ever. I then updated to pie on locked bootloader and still fine. Only to the point I rooted did I get ban issues. So I have no magisk modules and only around 3 root apps (one being substratum which wasn't even working for me anyway).
Yesterday it would not let me login and I found that my safetynet checks were both false and I'm not sure how they were because every other time I checked they were true and I never flashed anything. I managed to fix this by uninstalling magisk and restoring my system backup. I then installed magisk again and used magisk hide. I just got banned not too long ago.
I think they must be detecting the actual magisk app rather than root itself. That's my theory, the only way to know for sure is just to have the APK installed without magisk flashed but I don't want to get the account banned again. For now I've decided that I'll not have magisk flashed and that I'll just go without it since I wasn't really using any root apps anyway. If I still get banned after that then we would know that it's not magisk but I can report back after. I've noticed that the ban happens at 5.40pm UK time for me every 1 day.
I have an Xperia Z2 which has super su installed but it isn't rooted since I just use it as a spare phone I used Snapchat on it temporarily and didn't get any bans on that. I'll try it on my XZ Premium as is without magisk installed and if I still get banned then I'm not sure what it would be.
Okay so after not having magisk installed I now got a 2 day ban and I'm not sure how because I do not have root installed and all my other apps that are installed are the same from before I ever even rooted so I'm unsure as to why I have this ban now which is beyond stupid. The only thing I can put it down to now is the screen recording app I have but I don't even have magisk installed so I don't understand how it wants to decide to ban me for an app I don't even have installed. If anyone can work anything out with this is would be great. I do still have an unlocked bootloader.
RJASSI21 said:
Okay so after not having magisk installed I now got a 2 day ban and I'm not sure how because I do not have root installed and all my other apps that are installed are the same from before I ever even rooted so I'm unsure as to why I have this ban now which is beyond stupid. The only thing I can put it down to now is the screen recording app I have but I don't even have magisk installed so I don't understand how it wants to decide to ban me for an app I don't even have installed. If anyone can work anything out with this is would be great. I do still have an unlocked bootloader.
Click to expand...
Click to collapse
even if you did not modify it it's still a good idea to reinstall the app after ban(or even wipe data if possible). I had this problem before when after unrooting i got banned, i formated data and then i was fine.
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
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.