Database Info

10/24/14 gear manager breaks connection with gear 2 after update!!!!!

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....

Gear Apps Store Wont Load

Hi
As of yesterday at about 9PM, the gear Apps store is refusing to load - the app on my phone just shows a 100% white screen when I select 'Samsung Galaxy Apps'. This is 100% repeatable and occurs after restarting phone and watch and after re-installing the gear app on the phone.
Start App -->Goto Settings Tab --> Select 'Samsung Galaxy Apps'
Start App --> Goto Info Tab --> Select 'View More Watchfaces'
Start App --> Goto Info Tab --> Select 'View More Apps' under 'Suggested Apps'
Each of the above results in a 'Loading' dialogue followed by a 100% white screen from which I can only press the Androud 'Back' button to get back into the gear App. Extremely poor...
Interestingly this occurred about an hour after I left a poor review for the Gear App (Which I think is extremely poorly written) on the Play Store. I wonder if they have the ability to disable the watches features for anyone who expresses discontent with them!?
Nigel

I have a Samsung phone so I'm not sure if the steps would be the same for you. Go to Settings -> Applications -> Application manager and then find galaxy apps and clear cache and data if you can find it. For me on my Samsung phone it's a separate app from the Gear app. Hopefully that works for you.

Someone watching you Neo... What a ridiculous suggestion and theory about significant importance of your comment

Gio999 said:
Someone watching you Neo... What a ridiculous suggestion and theory about significant importance of your comment
Click to expand...
Click to collapse
Lol, ever heard of 'tongue in cheek'?
Thought not!!
I fixed this by re-installing everything. It worked for a day (failing to load intermittantly), and then did exactly the same thing again - white screen, 100% failure to load gear app store. I now have no way to install apps until Samsung fixes whatever they broke.
Appears from another thread on here that I am not alone. Minded to just return the damn thing. Have avoided Samsung stuff for years due to poor quality software - looks like they have not improved.
Nigel
Sent from my SGP621 using Tapatalk

Outbreak444 said:
I have a Samsung phone so I'm not sure if the steps would be the same for you. Go to Settings -> Applications -> Application manager and then find galaxy apps and clear cache and data if you can find it. For me on my Samsung phone it's a separate app from the Gear app. Hopefully that works for you.
Click to expand...
Click to collapse
Thanks, tried that my phone does not have a 'galaxy apps' item installes never has had. I reset the cache for the three samsung components that the watch requirea, but still a blank screen rather than the apps store.
I think I will just give up and send it back! Shame cause the hardware side of it is great.
Nigel
Sent from my SGP621 using Tapatalk

veletron said:
Thanks, tried that my phone does not have a 'galaxy apps' item installes never has had. I reset the cache for the three samsung components that the watch requirea, but still a blank screen rather than the apps store.
I think I will just give up and send it back! Shame cause the hardware side of it is great.
Nigel
Sent from my SGP621 using Tapatalk
Click to expand...
Click to collapse
Don't give up, mine did the same, so nothing, but I got it to work. I talked about it on the S3 forum here.

It 'fixed' itself this morning, but still fails intermittantly. Consoled myself by playing with the clever (but pretty pointless) youtube app for the watch. XENOZU

is it soleved yet ? i have the watch since december and this is the 8th time that i get the white screen on apps store. first it whas 2 or 3 days after reset my watch. but the last 3 mounths it whas good every day until today. i opened the gear apps store with bluetooth turned off.

Any solution guys, mine seems to have the same problems, and tried everything, is there a way to boot the phone in safe mode? and check

thanoss44 said:
Any solution guys, mine seems to have the same problems, and tried everything, is there a way to boot the phone in safe mode? and check
Click to expand...
Click to collapse
Have you tried factory resetting the phone? I've used a couple of different phones with the watch and experienced an error similar to what's been described. The problem was solved by doing a clean install of the Samsung apps (via factory reset).

so annoying I got it working for a while by installing older version of gear manager and gear s plug-in but stopped again. The only other way it works is on the watch itself.
If you scroll through your watch face collection on watch, and go to get more watch faces you can access app store. But very limited function.

I had a very similar issue to this. I will copy/paste my post from another thread. Maybe it will work for you all:
"OK so you know how when you are first attempting to setup the watch it asks you to visit a website? You HAVE to visit that website if you want it to work on a non-Samsung phone! You cannot go to the Play Store and search for the Samsung Gear App. Why Samsung did this I have no idea. Basically what they have are TWO DIFFERENT Samsung Gear apps that appear to be identical; except one is for Samsung phones and one is for all others. WHY THEY DECIDED NOT TO STATE THIS ON THE APP PAGE IS BEYOND ME.
Anyway if you are having this problem, uninstall your Samsung Gear app. Then go to your watch, go to settings and choose the option to connect it to a new phone. On your cell phone, go to the website it tells you to. The website will ask you if you are using a Samsung phone or another phone, so obviously don't click the Samsung option. This will give you a direct link to the Samsung Gear app that is meant for all other phones.
Again it's a really bizarre thing on Samsung's part but I am so glad to have figure it out and I hope my post helps you guys or anyone else Googling this issue in the future."
EDIT: The website is http://apps.samsung.com/gear

OK did that chose the non Samsung phone and it redirected me on the app store for gear app. Downloaded it and had the same result... Go figure

Go figure
After going to the site it was stating and choosing the non galaxy version it went to the app store. Apparently I installed it and voila... The same happened..... What the...

Have you tried setting it up using a different phone?

You are right, installing it on my galaxy s6 is working right, but that's not the point since it does not work on my u11. Apparently that's the new way of forcing people to buy Samsung phones. Making products working correctly only with their brand. I feel pity for them.....

I have the same issue with zenfone 3. Its nearly one month of buying gear s3 and i factory reset my gear 4 times cuz of reinstalling the gear app. Its a shame for a top brand like samsung to have a software problem like this with a brilliant smart watch

Cannot pair or connect a previously connected watch

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.

Question Anyone using Samsung Pay? Doesn't work on my Galaxy Watch4 Classic

I am trying to set up Samsung Pay on my new Galaxy Watch4 Classic. No matter what I do, I can't get past this screen! Paired with Z Fold3. Touching the button with the arrow does nothing. Any help would be appreciated!

Update: Maybe this has something to do with it? Every time I open the Samsung Pay watch plug in on my phone it tells me it needs to update the Samsung Pay app on my watch. But every time it fails. Yes I've rebooted. No reason given. Any ideas? Phone is Z Fold 3.

maybe ur watch region CSC dont allow samsung pay .
samsung pay work in ur fold3 ?
check ur watch region

carlitobahsoun said:
maybe ur watch region CSC dont allow samsung pay .
samsung pay work in ur fold3 ?
check ur watch region
Click to expand...
Click to collapse
Yes works fine on ZF3 and on my GW3 up until I cleared it. I'm in the USA and it's a US watch purchased directly from AT&T.

I had the same issue with mine when I first got it. I THINK what I did was disconnect from my phone and make sure the watch was connected to my home WiFi. Then it updated and I could set it up. It's been awhile so I can't remember for sure. Hope that helps!

roaddog665 said:
I had the same issue with mine when I first got it. I THINK what I did was disconnect from my phone and make sure the watch was connected to my home WiFi. Then it updated and I could set it up. It's been awhile so I can't remember for sure. Hope that helps!
Click to expand...
Click to collapse
I will try that thank you.

roaddog665 said:
I had the same issue with mine when I first got it. I THINK what I did was disconnect from my phone and make sure the watch was connected to my home WiFi. Then it updated and I could set it up. It's been awhile so I can't remember for sure. Hope that helps!
Click to expand...
Click to collapse
Nope didn't work, or I didn't do it right. I've had my watch disconnected from the phone (even turned off remote connection), WiFi only, for 2 hours now. Opened the Samsung Pay app many times, never prompted for an update and nothing ever happened on its own. Still can't get past that Get Started screen with the arrow button. Is there a way to manually trigger an update or clear data for an app directly from the watch? I couldn't find Samsung Pay in the Play store either to update or reinstall.

Ok, I may not be remembering correctly either. I would try resetting the samsung pay watch app in the Galaxy Wearable app. Watch settings>apps>app settings>samsung pay. Get into the settings there and check the version, it may let you update the watch plug in from there. If not I'd use the reset option.

roaddog665 said:
Ok, I may not be remembering correctly either. I would try resetting the samsung pay watch app in the Galaxy Wearable app. Watch settings>apps>app settings>samsung pay. Get into the settings there and check the version, it may let you update the watch plug in from there. If not I'd use the reset option.
Click to expand...
Click to collapse
Thank you, good advice. Unfortunately that's the first thing I tried and there actually is no option to reset. Usually you can click on Storage and then have Clear Cache and Clear Data. Clicking on Storage for Samsung Pay does nothing. No option to clear anything. Can't uninstall either. The closest I could come to this was uninstalling and reinstalling the Samsung Pay Watch Plugin from my phone, and that didn't help. I did talk to Samsung and they want me to bring it to a service center or ship to them for physical repair, which is about what I was expecting for an answer. I did try resetting the watch back to factory defaults and reinstalling the wearables app on my phone, no luck. Brought me right back to the same place. I guess I will try exchanging it since I just bought it, and if the new one doesn't work I'll just go back to my GW3. Thank you for your help.

Did you tried to reset App data from ADB? ADB is a debug protocol for Android devices. With ADB you can do things which no allowed to do in User Interface. In Android OEMs like Samsung are disabling to much features in UI because they think people are dumb and they don't wanna mess your phone if you are not experienced user. With ADB you can do too much things in Android devices. I don't know how to reset app data with ADB but I did it before, just search the web.

Its easy. i had the same issue, only solved by doing this. Install APKPure and search for updates for your apps. it should appear there.update it, and afterwards you can uninstall the APKPure.
Best of luck mate.

Hi, was this ever solved in the end? I am just experiencing this issue... It's because of the new update for the Watch Plug-In, for some reason it cannot update the app on the watch itself or communicate to that app at all... I still experience that same stuck screen!! Any help would be appreciated.

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

Just thought id put this up in case anyone else is going round in circles after an update to A13/OneUI 5.0 on Samsung devices
Updated my S20+ 5G overnight and only one issue so far...unable to connect my Watch 4 to it
Sometimes get as far as pairing code shown before inevitable fc
Issues with Watch 4 connection noted on S22's, so may be related
You would think they would test this stuff, wouldnt you.....
Bloody Samsung, premium price for garbage software updates
Im going back to A12 or start looking round for a new phone....why cant Google make a decent Pixel without buggy hardware...life was so easy when they did
Update:
Reading the S22 threads theres a whole host of issues with A13 and OneUI 5.0
Really, how does Samsung do this on a flagship??? Its like a clown show

73sydney said:
Just thought id put this up in case anyone else is going round in circles after an update to A13/OneUI 5.0 on Samsung devices
Updated my S20+ 5G overnight and only one issue so far...unable to connect my Watch 4 to it
Sometimes get as far as pairing code shown before inevitable fc
Issues with Watch 4 connection noted on S22's, so may be related
You would think they would test this stuff, wouldnt you.....
Bloody Samsung, premium price for garbage software updates
Im going back to A12 or start looking round for a new phone....why cant Google make a decent Pixel without buggy hardware...life was so easy when they did
Update:
Reading the S22 threads theres a whole host of issues with A13 and OneUI 5.0
Really, how does Samsung do this on a flagship??? Its like a clown show
Click to expand...
Click to collapse
check lot of iPhone problems..
btw, Oneplus had problem with connection GW4 after upgrade from 12 to 12.1. only one solution was reset GW. now on 1+ A13 doesnt work Google Wallet/Payments with cloned apps enabled.. Samsung is better competetion..

I haven't had the 1st issue (knock on wood) and it paired up with my GW4 right away. I flashed my One UI 5 manually

HyperChick said:
I haven't had the 1st issue (knock on wood) and it paired up with my GW4 right away. I flashed my One UI 5 manually
Click to expand...
Click to collapse
Yup, since im rooted it was a manual clean flash for me via ODIN
It seems very random according to what ive seen....but ever since Watch 4 came out its been one connection problem after another, and Watch 5 users have been plagues by them too

Try updating google play services to the latest beta (apkmirror). Solved my issue

shaharofir said:
Try updating google play services to the latest beta (apkmirror). Solved my issue
Click to expand...
Click to collapse
tried latest beta (22.45.15 (190400-488417729) beta (190400))
absolutely no difference

73sydney said:
Yup, since im rooted it was a manual clean flash for me via ODIN
It seems very random according to what ive seen....but ever since Watch 4 came out its been one connection problem after another, and Watch 5 users have been plagues by them too
Click to expand...
Click to collapse
There's your problem, root! But there are workarounds available. Just search in this forum and you'll find some

DaReDeViL said:
There's your problem, root! But there are workarounds available. Just search in this forum and you'll find some
Click to expand...
Click to collapse
Cheers, but just for reference, im quite involved in Magisk circles and hiding root (have modules to assist in this)...im usually helping others hide stuff or deal with root issues.....so i know what im doing
Also the same setup i use had no such issues in Android 12, its very much a Samsung making life harder for everyone, on purpose, because theyre basically acting like the new Apple and want to lock everything down. Ive decided to go back to Pixel, off to buy one soon, Samsung has gotten their last $ from me, they can go hang...

73sydney said:
Yup, since im rooted it was a manual clean flash for me via ODIN
It seems very random according to what ive seen....but ever since Watch 4 came out its been one connection problem after another, and Watch 5 users have been plagues by them too
Click to expand...
Click to collapse
Rooted Samsung Phones doesn't connect to Samsung Watches anymore.
You need to modify 2 files in vendor partition,
Vendor - build prop and remove SAKV2 from security keys
Vendor/etc/Wintf - Empty the Manifest.xml file
reboot and the watch will connect fine.

JazonX said:
Rooted Samsung Phones doesn't connect to Samsung Watches anymore.
You need to modify 2 files in vendor partition,
Vendor - build prop and remove SAKV2 from security keys
Vendor/etc/Wintf - Empty the Manifest.xml file
reboot and the watch will connect fine.
Click to expand...
Click to collapse
You prolly missed this module of mine in my signature (signatures dont show on mobile) , but i was already using that method and had been for a while :
GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices
Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices - GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" f...
github.com
I did later figure it out, will post my outcome separately

73sydney said:
You prolly missed this module of mine in my signature (signatures dont show on mobile) , but i was already using that method and had been for a while :
GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices
Removes "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted Samsung devices - GitHub - stylemessiah/SamsungHealthSecurityProps: Removes "sakv2" f...
github.com
I did later figure it out, will post my outcome separately
Click to expand...
Click to collapse
Thank you for this.
I will use this If I ever lose the R/W ability in my device.
For now I have R/W - so I wrote to the file directly.

Heres what i found out......
TLDNR version:
Dont backup and restore Samsung Wearables Apps - even if you previously were able to do this for eons, like i had. I have used Migrate to backup and restore apps and app data for eons (important to note i always left the app data (middle column in Migrate GUI) disabled for Samsung Wearables apps. Always let the Watch be detected as part of device setup on stock ROM OR install the Galaxy Wearable live from the Play Store (after clearing Google Play Services/Store sata and achieving Integrity check if you are rooting your device)
Longer version:
The other night i finally got time to flash back to A12, ran my normal procedure, rooted, USNF...clear data on GP/GS and then connected Watch...only it still wouldnt connect, even though the app restore was taken from a clearly working A12 (just before i flashed A13)
So i had to alter my procedure in leaving out the backed up Samsung wearables apps during restore, and then let the installed ROM detect the presence of the Watch 4 AFTER i have rooted, USNF...clear data on GP/GS and then connect Watch...
Looks a little like this:
* Flash ROM via ODIN (including my special AIO.zip to install TWRP, format data, decrypt data etc)
* Watch 4 WAS powered on and waiting to be detected when setup wizard looks for it towards end of setup - ignored/cancelled setup this time - going to do the root, USNF module and integrity check thing firsties
* Finish setup
* Reboot to TWRP recovery
* Root with Magisk (renamed to .zip) via TWRP
* Reboot
* Install Magisk App to complete install (you can just use the stub installer which will download the full app, but im used to doing it this way)
* Reboot
* Install USNF (Mod) and put device in airplane mode clear data on Google Play Store/Services to pass Integrity Check
* Reboot
* Take device off airplane mode....
* Open Google Play and confirm its certified (just needs to show version (Device Is Certified of course comes later - as along as it doesnt say Device Is Not Certified, all is well)
* Watch 4 automatically detected (Wearable Manager Installer - this is i think obviously a stub installer to detect and call the latest Galaxy Wearable from the Play Store) and Watch setup commences
* Watch setup completes
* Restore remaining apps via Migrate (leaving wearables unselected - will leave them unchecked on next backup)
NOTE: you must do (and ALWAYS have had to do) the Watch connection AFTER clearing data on GP/GS to get Integrity to pass. If you do that data clear after you connect the Watch it will sever the connection, as it tied to GS
Noter 2: Ultimately i decided id had enough of Samsung tomfudgery, and i bought a Pixel 6 Pro and departed for sanity back to Pixel Lyfe.....

My watch 5 out of nowhere stopped connecting to the wearable app, but was still connected to Bluetooth. Tried clearing cache on my s22 and the watch, reset data to the wearable app, uninstalled it and the watch 5 app, reset the watch, nothing works.. Now that I reset the watch I can't get it set up.. It downloads the watch 5 app, I click OK on accept updates, then it says error then the wearable app crashes.. I tried installing an older version of the app, but it wants to update before it'll do anything. Anyone able to get past this? I can't use my watch at all. Sooo aggravating.

gettinwicked said:
My watch 5 out of nowhere stopped connecting to the wearable app, but was still connected to Bluetooth. Tried clearing cache on my s22 and the watch, reset data to the wearable app, uninstalled it and the watch 5 app, reset the watch, nothing works.. Now that I reset the watch I can't get it set up.. It downloads the watch 5 app, I click OK on accept updates, then it says error then the wearable app crashes.. I tried installing an older version of the app, but it wants to update before it'll do anything. Anyone able to get past this? I can't use my watch at all. Sooo aggravating.
Click to expand...
Click to collapse
That behaviour has been noted on S22, and well even the Watch 4, once disconnected could be a pain to get connected again, involving a Watch reset (which of course you have tried
Samsung got wise to the whole "install and older version fo the app" thing a little while ago, because it was a legit way to get Samsung Health working on rooted Samsungs, and so now its a forced upgrade on some of the wearables related apps....
As i said above, the backup (that started all this) i had was from a working install where everything worked and had for many months, but when restoring it, which id done a couple of dozen times, this last time it caused chaos. the ONLY way i could get it working was the way i outlined above, which wasnt an issue for me as i was already clean flashing, but from an installed system, well i dont know what to tell you , i tried various clearing/uninstalls of apps and could never get it to connect until i did what i did in the last post
But i dont even know if youre using a rooted S22...im guessing not
You could try clearing data on the Google Play Store and Google Play Services as they also play a part in the Watch connection (i.e. if you clear data on these ever with the Watch connected, you WILL sever the connection) and then try running Watch connection setup again

73sydney said:
That behaviour has been noted on S22, and well even the Watch 4, once disconnected could be a pain to get connected again, involving a Watch reset (which of course you have tried
Samsung got wise to the whole "install and older version fo the app" thing a little while ago, because it was a legit way to get Samsung Health working on rooted Samsungs, and so now its a forced upgrade on some of the wearables related apps....
As i said above, the backup (that started all this) i had was from a working install where everything worked and had for many months, but when restoring it, which id done a couple of dozen times, this last time it caused chaos. the ONLY way i could get it working was the way i outlined above, which wasnt an issue for me as i was already clean flashing, but from an installed system, well i dont know what to tell you , i tried various clearing/uninstalls of apps and could never get it to connect until i did what i did in the last post
But i dont even know if youre using a rooted S22...im guessing not
You could try clearing data on the Google Play Store and Google Play Services as they also play a part in the Watch connection (i.e. if you clear data on these ever with the Watch connected, you WILL sever the connection) and then try running Watch connection setup again
Click to expand...
Click to collapse
Yeah, not rooted. I'll give the clearing play store and services data a whirl. I also have a conversation going with Samsung support on Twitter. Thanks for replying!

DaReDeViL said:
There's your problem, root! But there are workarounds available. Just search in this forum and you'll find some
Click to expand...
Click to collapse
Root has nothing to do with, the Galaxy Wearable app doesnt stop working if your knox has been tripped.
Ive had the last 3 Galaxy watches and all my phones have been rooted with custom roms, any issues ive had connecting/pairing were user error.