Yeah i Installed for wear OS too. But the app dont find my compatible watch 4For WearOS watch, use the WearOS SHM MOD, you'll find the link in the thread
Yeah i Installed for wear OS too. But the app dont find my compatible watch 4For WearOS watch, use the WearOS SHM MOD, you'll find the link in the thread
If the phone app is crashing and can't get past profile creation, then even if you carry on installing the mod on your watch, you won't be able to use it because phone shk mod should be functional...Bare with me, my knowledge in this area is limited. I installed the shm on my phone by downloading the file to my PC, plugging my phone into the PC and copied the files over. But how do I get the shm on my watch? Is it the same downloaded I installed on my phone?
Watch has shm mod installed..?Yeah i Installed for wear OS too. But the app dont find my compatible watch 4
Yes it's installed SHM mod. Yes it's show no compatible watch.If the phone app is crashing and can't get past profile creation, then even if you carry on installing the mod on your watch, you won't be able to use it because phone shk mod should be functional...
But let's say you want to install the watch app regardless, the watch shm mod is located in the watch folder the name of the apk has "watch" in it...
Watch has shm mod installed..?
Does it open the phone shm mod and still show no compatible watch found...?
If yes, restart phone and watch and they will detect each other on next boot...
Could you please share a screenshot of the app icons for watch and phone just to confirm you have the right appsYes it's installed SHM mod. Yes it's show no compatible watch.
I've restarted several times today but it is the same problem
Could you please share a screenshot of the app icons for watch and phone just to confirm you have the right apps
And the watch app icon ?
Few posts back you said the mod is installed on watch (as an answer to my question)...
sorry I meant the original app is on the watch. my mistake. Thanks for the tip, I'll take a look and report back, sirFew posts back you said the mod is installed on watch (as an answer to my question)...
Nevertheless, there is a ReadME document in Google drive in the watch folder...
You can also install the shm mod companion, watch section has a question mark that explains what you need to do and sideload the apk...
Alternatively, watch the YouTube video...
No worries, I hope it's straightforward and easy for you to install...sorry I meant the original app is on the watch. my mistake. Thanks for the tip, I'll take a look and report back, sir
Hi Dante, I have the watch.SHM.MOD on my computer and I copied it to my phone.If the phone app is crashing and can't get past profile creation, then even if you carry on installing the mod on your watch, you won't be able to use it because phone shk mod should be functional...
But let's say you want to install the watch app regardless, the watch shm mod is located in the watch folder the name of the apk has "watch" in it...
Watch has shm mod installed..?
Does it open the phone shm mod and still show no compatible watch found...?
If yes, restart phone and watch and they will detect each other on next boot...
Yes, you'll turn on debugging and debug over Wi-Fi, kindly read the instructions or watch the video or wait few hours, I will release a new tutorial video to show simple PC way or using phone only (which I will highlight that this is easier)Hi Dante, I have the watch.SHM.MOD on my computer and I copied it to my phone.
How do I transfer it to my watch?
View attachment 5777279
Once I have it on my watch do I need to turn on ADB debugging on my watch before installing?
That would be awesome! I look forward to the new tutorial video (for those challenged like me)Yes, you'll turn on debugging and debug over Wi-Fi, kindly read the instructions or watch the video or wait few hours, I will release a new tutorial video to show simple PC way or using phone only (which I will highlight that this is easier)
Might take a day or so, just thought I'd tell you if you don't want to waitThat would be awesome! I look forward to the new tutorial video (for those challenged like me)![]()
Have you found a solution to that? My watch disconnects once a week and only a factory reset of the watch + Apps brings it back to live.Once is disconnected seems to be unpaired from Bluetooth also. Even I'm trying to reconnect it via Bluetooth and is successfully connected, still the Galaxy app can't reconnect back to watch.
Much appreciated! I watched/read the how too again and I think I have it figured out. If not I'll wait. UPDATE: Still no luck :-(Might take a day or so, just thought I'd tell you if you don't want to wait
Have you found a solution to that? My watch disconnects once a week and only a factory reset of the watch + Apps brings it back to live.
Thanks a lot!It can be one of two things
1) Just a known bug that isnt yet fixed that causes random disconnections
or
2) If you have a rooted Samsung of certain models, once rooted on stock ROM they can lose bluetooth pairing and need to be patched to prevent this, my previous device the S20+ was one such device
see the thread here if you have a Samsung device and want to check if youre possibly affected:
![]()
BluetoothLibraryPatcher - Fix bluetooth pairings loss [Android 13/12/11/10/Pie/Oreo/Nougat]
Bluetooth Library Patcher • Description : This patch attends to avoid losing bluetooth pairings after reboot or airplane mode switch on rooted samsung devices. It patches on the fly the bluetooth library and should support most of samsung...forum.xda-developers.com
p.s. Dont ask me.....
Thanks a lot!
Do you have more information or a link to get more details on the this bug?
I'm using a Huawei P30 Pro
Thank you so muchI have just started looking into phone shm (version 227) and here is what I observed on UI:
* Malaysia & Thailand having BP & ECG enabled...
* Luxembourg & Philippines both having privacy policy and terms of use but nothing obvious about BP or ECG...
* more works on the icon to support shadows and so (and dropping static round icon)...
* polishing to UI code (removing useless elements from elements) and seems BP & ECG ISO have their own container...
* Added 2 Descriptions for BP & ECG (not sure where it will be visible till I patch and make it runnable):
"""Samsung Health Monitor Model Blood Pressure App is a mobile medical application operating on a compatible Samsung Galaxy phone and Samsung Galaxy Watch that can transfer the measurements to the app on the Galaxy phone, allowing the user to view blood pressure data and trends."""
"""Samsung Health Monitor Model ECG App is a mobile medical application operating on a compatible Samsung Galaxy Watch (ECG-Tizen/WearOS) and Samsung Galaxy phone (ECG-Android). This app captures bioelectric signals from the user. It's used to measure ECG, and data can be transferred to the Samsung Galaxy phone, allowing users to store and share PDF data with healthcare professionals."""
* Samsung has an address in Thailand...
* Malaysia language is English, they did not translate the app...
As for the functionality (Code), here is what I observed:
* Message handler that was absent before, failed to sync to watch try again later (I think this is where the layout seems to spinning forever and after a restart, the app connects to the watch)...
* New countries visible in CSCUtil, Macao (MO), Malaysia (MY), Thailand (TH), Philippines (PH), Norfolk Island (NF), Malta (MT), Luxembourg (LU)...
OK so,
NF is checked as isAUModel (Australia)
MO is checked alongsiide HK in a new method called isHongKongRegion (China)
TH has its own method isTHModel
Nothing about the PH or MT or LU but it is possible to say they got partial support if not fully...
what next:
* they are changing font programmatically ("sec-roboto-light")...
* BP and ECG results may look different as I spotted method fromHtml (used to add styling to text, such as color, bold, etc) in a TextView...
* BP History Compare...? worth checking this one out...
* BP is heavily modified (Code gone poof lol and new code replacing it or nothing at all)
* ECG is modified same as BP...
* I don't think there is a significant change in the UI (at least by just looking at the code)...
And that's all...
I don't see any change that is worrying me, so I should be able to apply the latest patch of 221 and it should work fine...
I will try my best to patch and release this version whenever I get the time to work on...
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...- Do I need to install both phone and watch MODs?
Yes, you need both, keep in mind, the apk with word phone is for phone and the watch4 is for the watch...- Where is the IP Address?
You can find it inside the developer options after you enable the ADB Wi-Fi, it takes time though, alternativly, you can go to connections -> wifi -> the wifi you are connected to -> scroll down and you'll find your IP...- Can I do this from my phone?
Yes, you can use Bugjeager if you don't like to type commands or Remote ADB Shell if you want to type the commands...- How do I update?
Just install it again and it will update, whether you install the phone app or the watch app...- Do I need Samsung Health MOD, is there even such thing...?
There is no Samsung Health MOD, Samsung Health is a core application, modding it will break many services, using official Samsung Health works fine...
Now here is an update of mine if the above does not work and Galaxy Wearables keeps disconnecting from the watch4
Initially it was Huawei devices but this solution works for other devices as well...
This fix is done by Reddit u/Relative_Comparison2 & u/MelodicMaintenance
You need Galaxy Wearables & Watch4 Plugin installed, now do the following steps:
- Download Samsung Health.
- start Samsung health then go to accessories and search for your watch (scan).
- Samsung Health will call Galaxy Wearables to set up the connection and a normal setup is performed.
It was Explained that you need to have the following apps installed:
Galaxy Wearable & Watch 4 plug-in
Give all permissions to Galaxy Wearables and the Watch4 plugin by going app info, scroll down, permission and grant all...
Now Clear the data of the following applications:
The phone will start acting up, that's normal, so restart your phone to allow system app to rebuild itself, when the phone starts, do not configure your google account yet, first try connecting to the Watch4 again through Samsung Health and it should work, after that you can do whatever you want for google...
- Google Play Services
- Google Play Framework
- Google Play Store
- HwWifiproBqeService (For Huawei devices only, skip if you are not Huawei)
One last note, disable any battery optimization, some phones have aggressive optimization, they will kill background services, this will stop the watch4 from pairing, if you can't disable it, then whitelist galaxy wearble and the watch4 plugin!
Samsung Health Security Props
Removes "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:
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
- looks for /vendor/build.prop
- if 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 folder
- removes sakv2 from the line in system.prop (it will remove sakv2 from the line (hopefully) wherever it exists, beginning, end or middle)
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)
pm disable-user --user 0 com.samsung.android.shealthmonitor
and exiting the shell and disconnecting... instructions updated...