pairing the watch , thank you.Ok, by not able to connect, you're talking about shm or pairing the watch? I should've asked that question first
pairing the watch , thank you.Ok, by not able to connect, you're talking about shm or pairing the watch? I should've asked that question first
Changelog few posts backNew Samsung Health Monitor update (1.1.1.227)
https://www.apkmirror.com/apk/samsu...2/samsung-health-monitor-2-1-1-1-227-release/
Does this need any rooted device or does Root in the title mean it simply works on rooted devices? confused
How about reading F.A.Q and Features on first post... it's very clear...Does it work if I have a Samsung Galaxy S20 phone? I read a comment on a Reddit thread saying it only works if you have a non Samsung phone.
That's why there is an app for Tizen and App for WearOS... Tizen mod will hold data of active2 and WearOS will hold data of watch4...I apologize in advance if this was already answered or explained, but I am wondering if it is possible to use both the WearOS and Tizen MODs with the same phone.
My WearOS (Watch4) has the mod and works as expected.
On my Active 2 I have the mod on the watch and as expected it says Calibration required, when I click to continue on the phone nothing happens.
When I open the SHM App on the phone, the same one I use for Blood Pressure with Watch 4 WearOS, It does not recognize the device.
I thought maybe there are two different APKs for the Phone, one that works with Tizen and one that works with WearOS but when I tried to install the APK from the download it says Update indicating it is already installed.
Any ideas what I am missing? Or is it just that I can't have both the WearOS and Tizen Mods simultaneously?
1. Wrong thread, mod here is for watch3 and active2, so go to the WearOS thread...I was able to download the Samsung health monitor App with my One Plus Smartphone.
Thanks a lot to make that work, but as soon as I open the app I have to accept the terms, and when I klick on that button, the App is closing.
Tried that quit a few times but i can't get over that problem.
I would love to get help what I have to do, really want to use the features for my galaxy watch 5
Thanks Dante,That's why there is an app for Tizen and App for WearOS... Tizen mod will hold data of active2 and WearOS will hold data of watch4...
But Tizen mod will have a conflict with stock shm... so you need to uninstall stock shm on your phone...
1. Wrong thread, mod here is for watch3 and active2, so go to the WearOS thread...
2. What app did you install?
Don't say that about yourself, you just didn't pay attention to what you were suppose to click... we're human beings and we tend to make mistakes, it's fine really, happens a lot and to most of us...Samsung Health app 6.23.0.063
SMH 1.1.1.227
Got a new Galaxy s22 Ultra and was able to unlock the restrictions of health monitor (my country doesnt have them available) but when trying to sync BP I can't, the set features button never appears on the samsung health app even after checking that the FeatureManager file is set correctly and clicking 10 times.
Also I noticed that on the health monitor app when I try to add the permissions for Samsung Health the button is locked, it may be because of the set features issue above but still.
Could anyone help me?
Edit: I was being dumb, I was supposed to click the version number, not the "Samsung Health" so the set features appeared.
Thanks for the answer !That's why there is an app for Tizen and App for WearOS... Tizen mod will hold data of active2 and WearOS will hold data of watch4...
But Tizen mod will have a conflict with stock shm... so you need to uninstall stock shm on your phone...
1. Wrong thread, mod here is for watch3 and active2, so go to the WearOS thread...
2. What app did you install?
Pairing requires a device, unfortunately, not emulator and you can't use shm with iPhone because there is no shm for iPhone...hey dante, thanks so much for you great work.
I just have a quick question: im an iphone user, got a watch3 bc of the health features. Its cheaper than any apple watch and apple watches cant be modified to enable health features if they are not supported.
Is there any way to enable healt features without an android device? I dont care if i cant pair the watch to my phone, i just want to be able to access health features. Is it possible to load the modified SHM in an android emulator and enable healt features? or the watch needs to be paired to the android device where the SHM app is installed ?
btw i temporarily paired the watch to my brother's android device just to be able to set it up.
First I want to say to article authors, thank you for your efforts to publish an article on this, but please do not copy and paste into your article as content may change and please provide link to the thread so people can get help and ask questions...
Ok, now let's begin:
- Tizen SHM MOD and WearOS SHM MOD...?
The watch4 original SHM can't communicate with the phone MOD, and it's not possible to completly remove the original SHM from the watch4, so I had to create WearOS MOD and rename the previous MOD to Tizen MOD...- Do I need root...?
No root is required...- Does this void my warranty?
No it does not void the warrenty or trip the know or damage the watch or the phone...- OTA effect on MOD & MOD effects on OTA.
No Effects, the MOD is independant...- Run_me.bat Java "main" errors and JDK15.
Open CMD and type 'Java --version', if it doesn't say Java 15, then you will struggle with such error, uninstall any JDK and reinstall JDK 15, run the command again, you should see Java 15...- Connecting to the watch isn't working.
Firewall, antivirus, defender, anything that filters the internet can block the connection of the watch, so make sure to disable all internet security, if it doesn't connect yet, reboot the pc and the watch and try again...
Please use the Knox Patch Module:
Samsung Health Security PropsRemoves "sakv2" from ro.security.keystore.keytype to help make Samsung Health run on rooted devices. This doesnt mean its a universal "fix" and works on every device every time, so ymmv....
Disclaimer: The changes made by this module may have ramifications/consequences beyond what you may be using it for (Samsung Health). I have tested it for several days and havent found any personally, but this doesnt mean they dont exist. You use this at your own risk
This module:
looks for /vendor/build.propif found, it copies the ro.security.keystore.keytype line (in case not everyone has the same keytypes in the line - i hate using static files, i write modules to use whats on each device) to a new system.prop file in the modules folderremoves sakv2 from the line in system.prop (it will remove sakv2 from the line (hopefully) wherever it exists, beginning, end or middle)I had planned to test this new "fix" for a while before releasing the module to stop people from manually editing the existing file, as using magisk is preferable as its easily reversible, but once i saw posts on XDA about it, i figured id release this now
As mentioned above, there may be side effects to this "fix", ymmv
Note: You still need to make sure you have Samsung Health added to Magisk's Deny List, ideally with Shamiko installed (if using Shamiko dont forget to disable Enforce Deny List)
Thanks to the following members for sharing their solutions about the Java "main" exception error solution: @FckSamsung, @little_blaine, @uoY_redruM and @gogega ...
BIG THANKS TO @evildog1 for the APK Easy Tool and @LeJay for the Fit2Installer that I found on his Thread...
Thanks to @caravana for sharing version 175, found at Samsung Health Monitor - 1.1.0.175.mod4.Caravana and on XDA Samsung Health Monitor v1.1.0.167 by @JonGarrett is how I found the link...
Thanks to @adfree for providing me SHM 1.1.0.181, SHM watch 1.1.0037 and SHM watch 1.1.0039...
Thanks to @vadu71 for providing me the updated version of SHM 183...
Big thanks to member @l0nax for the great catch of finding the device detection and lowering age restriction found in here...
Thanks to @jmdomini as despite BP was hidden and inaccessible, he was able to use the BP by calling the activity through a third-party app which tells me that the restrictions were only view related and not functionality, his findings helped me dig in the right place and fix SHM...
Thanks to @warpjavier for sharing his thread
https://forum.xda-developers.com/t/working-bp-tpk-for-non-samsung-phones.4184729/
I have followed his steps and generated unsigned TPKs, you just need to sign it...
After signing it with Tizen studio, you either push it sdb or you can use the TPK installer which you decompile, place the tpk in assets and compile it again...
Thanks for this Guide by @xxstd (download 1 to 3, don't use 4 or 5, use mine and proceed with the rest) for how to sign TPKs
Thanks to Mr. @m2carbine as on the journey of trying to make this work, thanks to him I found the root cause why BP failed to install...