Database Info

[INFO] NFC Service and Market

Learn from my Fail.
I was cleaning out some bloat yesterday by freezing a bunch of stuff I didn't need or want. After a reboot, I noticed that NFC Service was still running, even though it was frozen. I came to the obvious conclusion that it would be best to just uninstall it, nothing near me uses NFC anyways...
This was a mistake.
My Market started acting flaky... I could run it, and browse apps, and I could even update apps and install things I pushed through the web market, but as soon as I tried to view details about an app, Market would force close on me.
I tried all the obvious things like wiping Market data and cache, to no avail. Started poking through logCat and noticed that something was trying to talk to NFC Service around when I try to view an app. I restored NFC Service from titanium backup, rebooted, and the market works as expected again.
TL;DR: Do not uninstall NFC Service, otherwise your Market will force close when you try to view an app's details.
Hope this helps someone!
m.

what does it need nfc for?

jessejames111981 said:
what does it need nfc for?
Click to expand...
Click to collapse
Good question, I have no idea... just reporting my findings. Perhaps someone more knowledgeable can shed some light?
m.

I did the exact same thing for the exact same reason, but I only had issues when I used Google Play Store, when I did uninstall updates it worked fine. Unfortunately, it would always update itself, so I ended up flashing a custom ROM. Wonder why you can't freeze it or force close it?? Why is NFC always running?

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

What could be causing Lost Root?

it's not a big deal, as I can easily reboot to recovery and re-flash root.
however it's getting annoying, and I'm trying to figure out what could be the possible causes that might cause root to "randomly" disappears.
I've tracked down a couple of possible scenarios where root can be lost, due some failed patching of some sort, but it still doesn't explains other cases like when launching a game from the Google Play store, then hanging and after End Task, to find out that Root is gone.
I use an app called Auto Mount along with my 120GB microSD so I can keep all my apps/games running without filling up the built-in storage. I also use Titanium backup and Droid Wall, BusyBox and many other Utility Apps that needs root.
Yet all those are well known trusted apps, so I have no clue what or if anything is being send down from Google Play store to reset root
Recently Google Play have been doing weird things, and needs to often delete the cache / data, so things can be downloaded or updated properly, otherwise you'll get those typical play store error codes.
Anybody else suspect or got an idea what could be causing this issue?

so, after additional test, I noticed anytime I make a change to the blocking rules in DroidWall, it causes the problem after applying the new changes.
Another app that seems to also kills root is CSR racing update by itself, after letting it update, it also kills root.
newer version of CSR does not uses google play to update, also it ignores the blockings in DroidWall

Alot of the issue could be that the way android mounts the SD card it was never made for apps. I will bet that if you stop using auto mount and store the apps an the normal storage you will stop seeing this issue.

Why is Play Store so problematic? Stop DL at 99%; Download Pending all the time...

I've run into this for quite some time now, on both my Note 9, and my Huawei Mate 20 Pro.
All the things I find on resolving this suggest killing play store, deleting cache, deleting data etc. But even after that, it does not work well.
Seems it is a very important part of Android's eco-system, and yet very problematic.
Can anyone shed some light and/or permanent fix to this?

I'm a bit surprised there is no input on this.
I just needed to ininstall/reinstall an app. It was taking forever waiting on download. I deleted data and cache, and rebooted.
App ininstalled. The reinstall downloaded to 99%, and is not just sitting there.
I have to say it is VERY frustrating. I'm about ready to ditch Android. But that would be even more painful.

Did you use some VPN app when you downloaded apps with Google Play?

No. Although I do have NordVPN installed. But I have found that many sites are problematic to get to with it, both in the phone and PC. So I've stopped enabling it but haven't uninstalled it.
I'm guessing you think the VPN could be responsible.
I'll uninstall it and see if it changes anything.

Uninstalled, and rebooted. Trying to do update on some apps and it appears to have not helped.
Another interesting thing that happens at the same time that starts with the Google play store, is that I have a to-do app called DTG GTD. It gets to where the reminders coming from it, which flow through Light Flow, come in hours late. I had decided on my Note 9 that it was a problem with the phone. That's why I decided to get another new one, this Huawei mate 20 pro.
Now I just really don't know what to think. This starts about a month after I have either reflashed a phone or in this case bought a new one. I had factory reset and reloaded the Note 9 three times before I moved to this new phone.
I do have quite a few apps on my phone. Maybe it has to do with the mix of apps. Although, I wouldn't think it would take a month for it to start acting up.

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.