Related
I am planning to buy a new phone, pocophone f1 is an option, but I don't know if the galaxy watch will work properly with it. Any one has experience with pairing it to pocophone or other non Samsung phones? Thanks.
Mine is paired to an Honor 8 Pro. It paired right out of the box with no problems. Works much better than my old Moto 360 2nd Gen. I don't have Samsung Pay but I don't care about that.
Mister-B said:
Mine is paired to an Honor 8 Pro. It paired right out of the box with no problems. Works much better than my old Moto 360 2nd Gen. I don't have Samsung Pay but I don't care about that.
Click to expand...
Click to collapse
What about recieving notifications on the watch and downloading applications from galaxy store from your phone?
MHH76 said:
What about recieving notifications on the watch and downloading applications from galaxy store from your phone?
Click to expand...
Click to collapse
I used my former S3 with a former Honor 8 and had no problem with notifications or downloading apps from Galaxy store. I wouldn't expect problems with the Galaxy.
Has anyone had their watch receive calls and your phone never rings and then when you turn your watch off phone calls go right to voicemail?
MHH76 said:
What about recieving notifications on the watch and downloading applications from galaxy store from your phone?
Click to expand...
Click to collapse
No problems whatsoever.
I have had NO issues with the watch and my Oneplus 5T.
MHH76 said:
I am planning to buy a new phone, pocophone f1 is an option, but I don't know if the galaxy watch will work properly with it. Any one has experience with pairing it to pocophone or other non Samsung phones? Thanks.
Click to expand...
Click to collapse
If phone is not rooted, bootloader locked, and so play store device status is certified :
You can download and install galaxy gear app, from which you'll be able to pair and manage the galaxy watch.
It's what i done on my oneplus 5 : unrooted, re-locked. Everything works. As a non samsung phone owner, the only things that do not are :
- samsung pay
- integrated tizen email app
Or you can download the apk from apkmirror and use it with root. That's what I'm doing now. Samsung pay may or may not work, I don't use it so I don't know.
You need Samsung accessory service, the galaxy gear plugin and the galaxy wearble app. Mine works flawlessly with a custom ROM with xposed, rooted.
davtse said:
Or you can download the apk from apkmirror and use it with root. That's what I'm doing now. Samsung pay may or may not work, I don't use it so I don't know.
You need Samsung accessory service, the galaxy gear plugin and the galaxy wearble app. Mine works flawlessly with a custom ROM with xposed, rooted.
Click to expand...
Click to collapse
Can you download them without rooting, or must I root the phone?
You can do it without root but you need to enable the install from unknown sources option
they have a modded Samsung store to stop that root check they have magisk mods to hide root
I can confirm that this works on non-samsung devices. I get everything pushed to my watch from my phone as long as I have the notification for the app enabled at the time. The only issues I see with the Samsung Pay is if you don't have the app installed on your phone due to the fact that it uses NFC to make the transaction now so as long as your phone supports NFC you can use Samsung Pay as well. If not then you can use the ported version of Google Pay, but I wouldn't personally recommended due to the fact that it is ran by a third-party developer. As for root, I have not seen an issue or been lock out of anything in the watch due to being rooted so I can't confirm nor deny if it is fully root functional.
Rooted pixel 2 xl and everything works as it should.
Hi Everyone.
Keen to get a cellular version of the galaxy watch (keener for a cellular version of the watch active but apparently its not coming our with a cellular version) but I have a huawei mate 9,
Can anyone tell me...
Will it work with a mate 9?
If not what functions are not active?
Does it matter if the watch is a cellular version? does it being cellular mean it can connect directly to apps and access required information.
Apologies if this has been asked before, I have gone looking but cant find any reference ..
Thanks Tony
I have a Samsung phone so I'm not certain that this is 100% the truth, just what I have read from people in here or over the galaxy watch subreddit.
It should not matter what android phone is most things will work fine just like with a Samsung phone, I've only seen people talking about some compatibility issues with iPhone.
Now about the esim..
What I've read about it is that it works as if you have the phone with Bluetooth with you, you will get all the notifications but you don't have apps on the watch.
All of the notifications will be just mirrored from the phone notifications and the apps you can get on the watch right now are really limited.
Well you have Spotify and Samsung mail but for the others you can only do the same as on the phone notifications, read most of them, answer some things but it's going to be limited, on messaging apps you can see the last 10 but once you close the notification you have to wait until you get another etc.
If you often go out to do things like some kind of sport that doesn't allow you to bring the phone or you think you could use it while doing other things, it can be worth it but it's not going to work fully as a secondary smartphone, just as a app notification center + phone.
I'm using a cellular Galaxy Watch with a Huawei P20 Pro and it works perfectly.
Cheers,
Tom.
In all honesty, since they now allow you to download/install the Galaxy Weable app on pretty much any device now, you can use it with whatever device the app will work with.
I mean, there are always limitations and whatnot, but rule of thumb, yeah, it's not locked to Samsung phones only. Hell, they even let i(cough)Phone users use it! (unlike that fruity company with their watches).
Thanks!
Does the Samsung Galaxy Cellular smart watch work with huawei pro20?
Um said:
Does the Samsung Galaxy Cellular smart watch work with huawei pro20?
Click to expand...
Click to collapse
You may have to activate LTE on a samsung phone. S7 or newer.
I'm on a p30 pro. Panicked when I tried to activate LTE through the wearable app and it wouldn't work. Borrowed an S10, put in sim card and activated. All good now.
Works a treat with my OnePlus 8 Pro! Cheers
I'm using Galaxy Watch Active 1 and Honor 9 lite, all function on watch work well ( pairing, get whatsapp,email, SMS notification, purchasing app). And I can access galaxy store without phone (using Wifi network).
tomc99 said:
I'm using a cellular Galaxy Watch with a Huawei P20 Pro and it works perfectly.
Cheers,
Tom.
Click to expand...
Click to collapse
I have Galaxy Watch R800 (BT, WiFi only) and Huawei P20 PRO and I cannot make a Galaxy Store on the watch to work. Any idea?
Everyone I try to run Galaxy Store on my GW i get error. I can run galaxy store on my phone and it works. I have the same problem with Bixby. Any other app works great.
I get this error even on WiFi connection.
My advice for those who want to perfectly match the smartphone with the watch: If you own a huawei smartphone then buy a huawei watch and if you own a samsung smartphone then buy a samsung watch! Otherwise, after few updates of one or another nobody guarrantee if pair samsung/huawei/xiaomi or whatever will still work without bugs...
Hi all, I had just bought a new xiaomi mi 9 phone and I installed galaxy wearble application, galaxy watch plugin and Samsung accessory service, and gave them all permissions, but I can't log in my Samsung account to restore my watch backup or install new faces from store, when trying it gives my a blanc white popup instead of signing in screen, what to do?
Same thing is happening to me on a Pixel 3. Did you manage to fix it at all?
SdkDel said:
Same thing is happening to me on a Pixel 3. Did you manage to fix it at all?
Click to expand...
Click to collapse
No, I tried my best, looked in all settings and gave all permissions, the strange thing is that samsung pay and Samsung health can sign in normally but galaxy wearable and galaxy store can't, I hope someone can help.
MHH76 said:
No, I tried my best, looked in all settings and gave all permissions, the strange thing is that samsung pay and Samsung health can sign in normally but galaxy wearable and galaxy store can't, I hope someone can help.
Click to expand...
Click to collapse
I can't even get Samsung Pay to show up, even having sideloaded the apk onto my Pixel 3...
There's more people with the white page issue here:
https://us.community.samsung.com/t5...ar-app-on-phone-White-screen/m-p/585638#M7720
Same problemm on my S3 & Watch 42 mm + Huawei M10P. I changed the apk and same result. Chinese phones are banned by samsung?
I don't think so, people have the same issue with LG and pixel phones
Same problem here, moto g 6plus + galaxy watch
Can't sing in on app and white window
It appears to be an Android issue since I tested using my work iPhone and there I can login!
Also annoyed as hell bought the watch yesterday when the issue appears to have started also noticed Samsung accessory service was updated 2 days ago..
IMHO in Samsung world... Samsung Android phones have System app for Account crap...
IMHO it is missing on non Samsung Phones...
No idea if possible to install this System app...
Only as idea...
Best Regards
I have the same issue with One Plus 6T. It looks like issue with Android Oreo support. No response from Samsung by when issue will bebresolved.
Any way we can sideload facer and get additional watch faces ?
I made a thread on thursday morning about this. It's been going on for that long
I installed Samsung Account apk . Now when I click on Error Reports I get login page but even after entering credentials it never logins.
Seems like Galaxy Wearable tries to find the linked Samsung account for login.
Here,
I use a Huawei phone and have the same issue. I just bought my Galaxy Watch and can't seem to login to my Samsung Account.
I was looking into solutions online and came across sideloading .wgt files. Would that work for the Galaxy watch?
Any other way we can sideload Facer or any watch companion to have more watch faces ?
I have the same problem....
I called Samsung customer care as well. They sound as if they don't even know there exists and app called Galaxy Wearable.
Guys good news. After 3 days of fighting with samsung over twitter, email, phone, chat , this issue is resolved.
Please try at your end. I am able to login in my One Plus 6T.
At last, better late than never.
Working at last
Worked this morning, problem solved thanks God.
Hi fellas
I got it finally to work, after updating to Android Pie
Time to share how I did it and be aware, I did not test this again in different ways, so there are some uncertainties, I will incorporate them into the places where they belong, so I recommend to first read this guide before doing it, so you are aware of what it requires, what the "risks" are and what restrictions I found so far.
Risks:
No guarantee it works for your devices. I already know from my own testing, it does not work on Android 8.X.
No guarantee this won't damage your phone or something, but that said, I am using this since over 1 year now, no adverse effect or anything
Untested if updating of the watch or Tab S4 breaks this - but in my case, I was on the newest version of Android, Tizen, and the needed apps already. That said, sofar updating the watch is not breaking this, after 1 year and several updates.
This is faking the phone's identity to a Galaxy Note 9, this leads to some side effects, ie. in my case the navigations button are stuck on the bottom, pin keypad is only usable horizontally, etc. BUT this is only for the procedure, you can revert after pairing, etc. and it worked ever since for me, even updating the watch software was no problem whatsoever - updating the watch software (the apps on it) you need to do temporary this trick again
Specs of my devices:
Samsung Galaxy Tab S4 LTE (SM-T835)
Android 9.0 - ROOT IS REQUIRED and this will void the warranty of your Galaxy Tab S4, as it is breaking Knox and this is not undoable (afaik)!
Here the exact Android version I use - which is meant for my provider (Swisscom), so please use your appropriate provider version! Only posting if someone is wondering (installed via Odin)
Here the guide which I used to root it (I have also some suggestions that should make it more clear)
Samsung Galaxy Watch LTE 46 mm (SM-R805F)
Tizen 4.0.0.1 (R805FXXU1DSB2/R805FOXA1DSB2/R805FXXU1DSB2 - according to Galaxy Wearable)
IIRC with this new guide you can activate the eSIM normally, in case it does not work:
Activate the eSIM with a known compatible device [but it must have the physical sim card your eSIM is connected to, insert before pairing up ofc.], ie. Galaxy S9, Galaxy S20, Galaxy Note 9 and then connect it with the guide below
Things you need to get this working:
Root (see above)
[Probably] Magisk Module so that Bluetooth connection is not forgotten: "libsecure_storage companion for rooted Samsung devices" (by ianmacd)
Build Prop Editor app (I used this one), hence the root
Galaxy Wearable app (tested on version 2.2.24.19031361) - If you download it at the beginning you can find it on the Play Store, otherwise you can find it on apkmirror as well
A file explorer with root capabilities
How to install:
At this point I strongly recommend installing ianmacds "libsecure_storage companion for rooted Samsung devices" in the Magisk Manager app! Otherwise, the tablet will forget the Bluetooth connections! Do not restart as we need to do this in a few moments anyways
Install the Galaxy Wearable app from the Play Store
Open your Build Prop Editor
Change the following stuff to fake your Tab S4 identity (mine is SM-T835, yours might be different) to a Galaxy Note 9 (in this case this specific model SM-N960F) - in the app I suggested you can do that by clicking on the pen top right:
ro.product.model=SM-T835 to ro.product.model=SM-N960F (Note: I could very well imagine this works with another model than the Note 9, as well, I haven't tested it though)
ro.build.characteristics=tablet to ro.build.characteristics=phone
ro.config.tima=1 to ro.config.tima=0 (this is to get Samsung Health app to work, I know this app is refusing to work on rooted phones, maybe other Samsung apps are also affected?)
Save the changes (in the app I suggested there is a save symbol top right) and restart the tablet (to apply)
Yes some of the UI is a bit weird, do not worry, we will revert to the correct identity at the end and everything should be back to normal
Launch the Galaxy Wearable app
Close the app again
Open root file explorer (give it root rights if you have not already done so)
Go to "data/data/com.samsung.android.app.watchmanager/files" and there open rules.xml
Edit the following lines:
Somewhere you will see: <group name="Gear S4" wearable tye [etc]
Below that line are 3 nearly identical line, all like that: <item supportNonSamsung="false" supportTablet="false" pairingImageName[etc]
In any case, all 6 of them (in 1 line there are 2, as there are 3 lines, that makes 6) should be "true"! If that is not the case, change them accordingly
!!! This might have to be redone if the Galaxy Wearable app is updated !!!
Start the Galaxy Wearable app again
Press "Connect to new phone" on your Galaxy Watch (or if it is brand new, then you should be also in the screen it asks to pair up with a new device) - beware: This "resets" your Galaxy Watch (except eSim info), so I suggest to back it up beforehand if you can
In the main menu of the Galaxy Wearable app, you should now see the Galaxy Watch, then click on it
Now it should pair up without any problems and set up properly (at least for me it did work all 4 times )
As said, if the mobile network setup fails, you need to setup the eSim beforehand with a known compatible device, as written somewhere above
You can restore a backup from here if you chose to, though you still have to setup some of the stuff again - I tried it without and it still worked without problems
If you have an eSim, check your watch if you have a mobile data connection (go to settings > mobile network > put it on ALWAYS ON just for that test)
Afterwards if you want to use it as a standalone outside your Bluetooth tablet range, I suggest AUTO or ALWAYS ON (beware ALWAYS ON eats a lot of battery, your watch might hold only 12h+ hours) and set in the Galaxy Wearable under "Account and backup", "Remote Connection" to on (which requires the tablet to have a data connection of its own)
Now I suggest to install & update all the necessary apps, see the guide below!
How to update watch apps or install watch apps:
Open your Build Prop Editor [you can skip these first 3 points if you are coming from first install part from above]
Change the following stuff to fake your Tab S4 (mine is SM-T835, yours might be different) identity to a Galaxy Note 9 (in this case this specific model SM-N960F) - in the app, I suggested you can do that by clicking on the pen top right:
ro.product.model=SM-T835 to ro.product.model=SM-N960F (Note: I could very well imagine this works with another model than the Note 9, as well, I haven't tested it though)
ro.build.characteristics=tablet to ro.build.characteristics=phone (this is essential, otherwise, we would need to change some XML file as well)
Save and restart the device
[Resume here if you are coming from the install part above] Open Galaxy Wearable
Open Galaxy Store
Open the 3 lines on the top left, go to Updates and then use the Watch tab
After you have done all the watch app updates & installs
Open your Build Prop Editor
ro.product.model=SM-T835 [SM-T835 is my tablet, yours might be different]
ro.build.characteristics=phone
Save and restart and all should be working as before
Enjoy your fully functional Galaxy Watch with your Galaxy Tab S4!
In case you are FORCED to do an update to the Galaxy Wearable app (it is not recommended to auto-update):
Update like any other app
If everything still works, you don't have to do the following points:
If suddenly it says your device is not compatible or something:
Open root file explorer (give it root rights if you have not already done so)
Go to "data/data/com.samsung.android.app.watchmanager/files" and there open rules.xml
Edit the following lines:
Somewhere you will see: <group name="Gear S4" wearable tye [etc]
Below that line are 3 nearly identical line, all like that: <item supportNonSamsung="false" supportTablet="false" pairingImageName[etc]
In any case, all 6 of them (in 1 line there are 2, as there are 3 lines, that makes 6) should be "true"! If that is not the case, change them accordingly
Save
Start the Galaxy Wearable app again and it should work again
Tested features that work:
Restarting the tablet (on my very first try this triggered some kind of in-app update, but it just repaired and it still works as usual), never had that again later (I repaired/reset the watch several times for testing)
Backup & Restore incl.
Connecting to a Samsung Account (never tested without though, but I see no reason it shouldn't work)
Remote connection (both LTE and Wifi) incl.
Notifications (specifically tested with Gmail and SMS) (both remote and over Bluetooth) and
Calling something (both remote and over Bluetooth)
Automatic Bluetooth reconnect
Widget/App installation & uninstallation (tested with Spotify remote control)
Adding a music track to the watch via Galaxy Wearable and play it
Samsung Health (partially tested, specifically heart rate works)
Calling from the watch, receiving calls to the watch, as standalone or in Tablet range (all 4 are working) (I recommend a Bluetooth headset)
Things that don't work:
Updating / Installing Galaxy Watch apps without doing the guide above
[Sometimes] rules.xml needs to be rechecked after a Galaxy Wearable app [see guide above]
Have fuuuuuuuuuuuun
neuer31 said:
Hi fellas
I got it finally to work, after updating to Android Pie
Time to share how I did it and be aware, I did not test this again in different ways, so there are some uncertainties, I will incorporate them into the places where they belong, so I recommend to first read this guide before doing it, so you are aware of what it requires, what the "risks" are and what restrictions I found so far.
Risks:
No guarantee it works for your devices. I already know from my own testing, it does not work on Android 8.X.
I haven't tested it longterm, so no idea if it will still work in 1 month or if your phone / watch breaks down or Samsung blocks it.
Untested if updating of the watch or Tab S4 breaks this - but in my case I was on newest version of Android, Tizen and the needed apps already.
This is faking the phone's identity to a Galaxy Note 9, this leads to some sideeffects, ie. in my case the navigations button are stuck on the bottom, pin keypad is only usable horizontally, etc.
Specs of my devices:
Samsung Galaxy Tab S4 LTE (SM-T835)
Android 9.0 - ROOT IS REQUIRED and this will void the warranty of your Galaxy Tab S4, as it is breaking Knox and this is not undoable (afaik)!
Here the exact Android version I use - which is meant for my provider (Swisscom), so please use your appropriate provider version! Only posting if someone is wondering (installed via Odin)
Here the guide which I used to root it (I have also some suggestions that should make it more clear)
Samsung Galaxy Watch LTE 46 mm (SM-R805F)
Tizen 4.0.0.1 (R805FXXU1DSB2/R805FOXA1DSB2/R805FXXU1DSB2 - according to Galaxy Wearable)
eSim preactivated on a "compatible" phone (iirc. Galaxy S9) - even doing "Connect to new phone", the watch keeps your eSim info - I could not setup mobile network with this one, but with this "trick" it still works
I tested both, setting it up new and using a backup both work in my case
Things you need to get this working:
Root (see above)
Build Prop Editor app (I used this one), hence the root
Galaxy Wearable app (tested on version 2.2.24.19031361) - If you download it at the beginning you can find it on the Play Store, otherwise you can find it on apkmirror aswell
How to install:
Install the Galaxy Wearable app from the Play Store (or do it later but then you need the .apk)
Open your Build Prop Editor
Change the following stuff to fake your Tab S4 identity to a Galaxy Note 9 (in this case this specific model SM-N960F) - in the app I suggested you can do that by clicking on the pen top right:
ro.product.model=SM-T835 to ro.product.model=SM-N960F (Note: I could very well imagine this works with another model, than the Note 9, aswell, I haven't tested it though)
ro.build.characteristics=phone to ro.build.characteristics=phone (this is essential, otherwise we would need to change some xml file aswell)
ro.config.tima=1 to ro.config.tima=0 (this is to get Samsung Health app to work, I know this app is refusing to work on rooted phones, maybe other Samsung apps are also affected?)
Save the changes (in the app I suggested there is a save symbol top right) and restart the tablet (to apply)
Press "Connect to new phone" on your Galaxy Watch (or if it is brand new, then you should be also in the screen it asks to pair up with a new device) - beware: This "resets" your Galaxy Watch (except eSim), so I suggest to back it up beforehand if you can
If you haven't already: Install the Galaxy Wearable app, but now you need to do with the .apk, you won't find it on the Play Store anymore (I wonder why)
Launch the Galaxy Wearable app
In the main menu of the Galaxy Wearable app, you should now see the Galaxy Watch, then click on it
Now it should pair up without any problems and setup properly (at least for me it did work all 4 times )
As said, the mobile network setup will fail, but it will still work if you setup the eSim beforehand, as written somewhere above
You can restore a backup from here if you chose to, though you still have to setup some of the stuff again - I tried it without and it still worked without problems
If you have an eSim, check your watch if you have connection (go to settings > mobile network > put it on ALWAYS ON just for that test
Afterwards if you want to use it as a standalone outside your Bluetooth tablet range, I suggest AUTO or ALWAYS ON (though ALWAYS ON eats a lot of battery) and set in the Galaxy Wearable under "Account and backup", "Remote Connection" to on
Tested features that work:
Restarting the tablet (on my very first try this triggered some kind of in app update, but it just repaired and it still works as usual), never had that again later (I repaired/resetted the watch several times for testing)
Backup & Restore incl.
Connecting to a Samsung Account (never tested without though, but I see no reason it shouldn't work)
Remote connection (both LTE and Wifi) incl.
Notifications (specifically tested with Gmail and SMS) (both remote and over bluetooth) and
Calling something (both remote and over bluetooth)
Automatic bluetooth reconnect
Widget/App installation & uninstallation (tested with Spotify remote control)
Adding a music track to the watch via Galaxy Wearable and play it
Samsung Health (partially tested, specifically heart rate works)
Untested:
Someone calling me, possibly do tomorrow (once with bluetooth, once without)
Splitscreen on the Tab S4
Things that don't work:
Samsung Dex disappeared for me from the widget bar on the Tab S4 (see in P.s. for a possible fix)
[Possibly] Setting up a new eSim in the Galaxy Wearable app (untested because I didn't want to risk it - if it doesn't work, use workaround by setting it up on another device, then unpair and the eSim profile will be kept)
P.s. !!!
I put back the old model in the prop editor, SM-T835 and it is still working (after a restart of the Tab S4), so maybe it is not needed?
In a further attempt I also edited rules.xml under data/data/com.samsung.android.app.watchmanager/files (you need root for that or someone who is capable to modify the app so that rules.xml is by default with the following changes) and changed all supportTablet="false" to supportTablet="true" between <group name="Gear S4"> and the next </group> and still seems to be working! Maybe, just maybe, a modified .apk could do this without any root necessary, though I had it rooted and tried by only modifying these rules.xml and it didn't work for me. Idk, I am too inexperienced in such things and have no idea of .apk coding.
As for now I keep running with these last changes and set Galaxy Wearable to never update in Play Store. These last changes also fix the Dex and other visual issues, so thats that.
Click to expand...
Click to collapse
Do you by any chance know how to make a rooted Galaxy S7 with with a Pie custom Rom port from Note FE work with a Galaxy Watch 46mm? It is stuck on finishing pairing and that lasts like forever...
Thanks in advance
jazol said:
Do you by any chance know how to make a rooted Galaxy S7 with with a Pie custom Rom port from Note FE work with a Galaxy Watch 46mm? It is stuck on finishing pairing and that lasts like forever...
Thanks in advance
Click to expand...
Click to collapse
That is exactly the problem I had with Android 8, it got stuck at pairing.
Sorry I am not into rooting, I just have enough knowledge to root my own device.
Shouldn't it be compatible on stock?
neuer31 said:
That is exactly the problem I had with Android 8, it got stuck at pairing.
Sorry I am not into rooting, I just have enough knowledge to root my own device.
Shouldn't it be compatible on stock?
Click to expand...
Click to collapse
Yes, it is compatible with stock but the last official Samsung update for S7 is Oreo. If I want to use Pie I need to install a custom rom and that is when the connectivity problems arise. Anyway, thanks for your time...
Wysłane z mojego SM-G930F przy użyciu Tapatalka
jazol said:
Do you by any chance know how to make a rooted Galaxy S7 with with a Pie custom Rom port from Note FE work with a Galaxy Watch 46mm? It is stuck on finishing pairing and that lasts like forever...
Thanks in advance
Click to expand...
Click to collapse
When it is stuck in pairing, try going to Bluetooth setting and manually click on connect button for watch, and come back again on app, may be this will help you, because it helps me when i was stuck on pairing mode
Sent from my Nokia 7 plus using XDA-Developers Legacy app
ca_guri01 said:
When it is stuck in pairing, try going to Bluetooth setting and manually click on connect button for watch, and come back again on app, may be this will help you, because it helps me when i was stuck on pairing mode
Sent from my Nokia 7 plus using XDA-Developers Legacy app
Click to expand...
Click to collapse
Thanks ca_guri01. I'll try it tomorrow.
Wysłane z mojego SM-G930F przy użyciu Tapatalka
jazol said:
Thanks ca_guri01. I'll try it tomorrow.
Wysłane z mojego SM-G930F przy użyciu Tapatalka
Click to expand...
Click to collapse
If you find any solution pls tell me [emoji53]
Sent from my SM-N935F using Tapatalk
fearbit said:
If you find any solution pls tell me [emoji53]
Sent from my SM-N935F using Tapatalk
Click to expand...
Click to collapse
Ok but no luck so far...
jazol said:
Ok but no luck so far...
Click to expand...
Click to collapse
Still looking?? Which rom have you installed?
Στάλθηκε από το SM-N935F μου χρησιμοποιώντας Tapatalk
fearbit said:
Still looking?? Which rom have you installed?
Στάλθηκε από το SM-N935F μου χρησιμοποιώντας Tapatalk
Click to expand...
Click to collapse
I gave it up for the time being. Got back to [TeamExyKings][G930/G935_F/FD][8.0][S9 Port][06-May-2019][v22]LightROM...
So 8 month after I made this guide, this is still working
No issues whatsoever, did multiple watch updates and updates of the app and with a trick even running Samsung Health app
I hope all of you that did this have a similiar good experience
You Sir are a Life Saver!
I had Tab S4 was using as my phone. As it was hard to carry it around I bought the watch. But did not work with S4 but you saved the day!
Thank you.
After editing rules.xml Samsung wear resets and no devices are shown.
Please help
neuer31 said:
So 8 month after I made this guide, this is still working
No issues whatsoever, did multiple watch updates and updates of the app and with a trick even running Samsung Health app
I hope all of you that did this have a similiar good experience
Click to expand...
Click to collapse
Hi, I have a galaxy Tab A (2017 model) and recently bought a Galaxy Watch D346. My tablet shows the watch in bluetooth available devices but can't connect and the samsung wearable app also cant find the watch. Can you please help me with this?
1. I updated the guide with 1 more strongly recommended install, a Magisk module by ianmacd, allowing the rooted Tab S4 to remember Bluetooth connections. It is called: "libsecure_storage companion for rooted Samsung devices"
2. The newest versions of the Samsung Galaxy Wearable app might require an additional modification, which I also implemented in the original post. You have to do it only if it suddenly says that your device is not compatible anymore.
Close the Galaxy Wearable app
Open root file explorer (give it root rights if you have not already done so)
Go to "data/data/com.samsung.android.app.watchmanager/files" and there open rules.xml
Edit the following lines:
Somewhere you will see: <group name="Gear S4" wearable tye [etc]
Below that line are 3 nearly identical line, all like that: <item supportNonSamsung="false" supportTablet="false" pairingImageName[etc]
In any case, all 6 of them (in 1 line there are 2, as there are 3 lines, that makes 6) should be "true"! If that is not the case, change them accordingly
Save
Start the Galaxy Wearable app again and it should be working again
Ashish3640 said:
After editing rules.xml Samsung wear resets and no devices are shown.
Please help
Click to expand...
Click to collapse
Are you using icanmads Magisk Module "libsecure_storage companion for rooted Samsung devices"?
Did you follow the guide?
I assume you did edited rules.xml doing this:
Somewhere you will see: <group name="Gear S4" wearable tye [etc]
Below that line are 3 nearly identical line, all like that: <item supportNonSamsung="false" supportTablet="false" pairingImageName[etc]
In any case, all 6 of them (in 1 line there are 2, as there are 3 lines, that makes 6) should be "true"! If that is not the case, change them accordingly
Zen_K said:
Hi, I have a galaxy Tab A (2017 model) and recently bought a Galaxy Watch D346. My tablet shows the watch in bluetooth available devices but can't connect and the samsung wearable app also cant find the watch. Can you please help me with this?
Click to expand...
Click to collapse
Did you root your device?
If yes, are you using icanmads Magisk Module "libsecure_storage companion for rooted Samsung devices"?
Did you follow the guide?
Hi neuer31, thanks for sharing, I am trying to get galaxy watch3 to connect with Tab S4, I have follow all the steps, in rules.xml in Gear S4 and Watch 3, I change all false to true. Watch 3 show up on wearable, goes through pin numbers authentication and start pairing a minute then shows
Can't open Galaxy wearable
Your version of Android isn't compatible . Check for software update for your phone and try again.
What should I try next ? Thanks
More info,
SM-T835
Android version 10
Baseband version T835XXU4CTI4
Galaxy Wearable 2.2.34.20091461 , I try to load older version but was force to upgraded to this version, I checked rules.xml to be all "true" for Gear s4 and Watch 3
I don't know how to root or tinker a device, scared to screw. Can you help modify the files for Galaxy Tab S2 8.0 please? Or would you be able to share your apks here, so I can try it out on my device??
Hi neuer31, I downgraded to android 9, and got the watch 3 connect to tab s4, I been playing with it for a wk now, so far so good, thanks a lot
My Sprint Samsung Galaxy Note10 Plus can't use the Health Monitor App that is connected to my Samsung Galaxy Active 2 watch. It claims my phone is rooted. I have not rooted a phone since my Samsung Galaxy S4. I have however, been downloading / transferring my info from phone to phone whenever I upgrade. Is it possible their is some error related to my old data? Is it possible my phone could have been rooted without my knowledge? I would like to use this app. I am a bit more concerned with my phone returning an it is rooted error. Anyone have any advice on this? I am running Android 12 with One UI version 4.1. Thanks in advance for any assistance.
Don't use SmartSwitch...
Was it running ok on 11?
12 is a mess.
I'm still and will stay running on Android 9 and 10. Security has not been an issue with only slight user modifications like disabling wifi.
It was not running on 11 either. Don't know why it says that. I have had an S6 Edge, S8 Plus, and now the Note 10 Plus. I have not done anything remotely close to rooting, flashing, or anything else since my S4. I have health issues and so I would really like the convenience of the Health Monitor App. All other features Knox should not allow to work if it was truly tripped work. So, I'm at a loss. Thanks for your reply.
crucian4 said:
It was not running on 11 either. Don't know why it says that. I have had an S6 Edge, S8 Plus, and now the Note 10 Plus. I have not done anything remotely close to rooting, flashing, or anything else since my S4. I have health issues and so I would really like the convenience of the Health Monitor App. All other features Knox should not allow to work if it was truly tripped work. So, I'm at a loss. Thanks for your reply.
Click to expand...
Click to collapse
It's sounds like a solvable issue if the knox efuse isn't tripped.
Make sure the Wearables apps have all their many permissions or it will puke on you.
Any Samsung apps disabled? Dependencies...
Clearing app data or reinstalling maybe. Clear system cache.
Call Samsung tech support, occasionally they do have solutions.
crucian4 said:
My Sprint Samsung Galaxy Note10 Plus can't use the Health Monitor App that is connected to my Samsung Galaxy Active 2 watch. It claims my phone is rooted. I have not rooted a phone since my Samsung Galaxy S4. I have however, been downloading / transferring my info from phone to phone whenever I upgrade. Is it possible their is some error related to my old data? Is it possible my phone could have been rooted without my knowledge? I would like to use this app. I am a bit more concerned with my phone returning an it is rooted error. Anyone have any advice on this? I am running Android 12 with One UI version 4.1. Thanks in advance for any assistance.
Click to expand...
Click to collapse
Try this as a workaround......weird your device thinks its rooted, or once was rooted.
[RESTRICTIONS-REMOVED] Samsung Health Monitor - WearOS - 1.1.3.002 - Root, Age, Country & Device Restriction Removed - 23rd May 2023
Hello Everyone, I hope you all are fine... ~~~ WearOS WATCHES ONLY ~~~ ~~~ FEATURES, BUGS & FUTURE WORKS~~~ FEATURES: Works on Samsung Watch4 and Watch5 (as mentioned Samsung WearOS Watches), Multilanguage, no root detection, no country...
forum.xda-developers.com