My role is complete...
I told you what you might be expecting from what you did...
It's up to you what you wish to do with the watch now...
Keep it, replace it, sell it, etc...
your call...
My role is complete...
Thanks bro is there any way i can brick this watch?My role is complete...
I told you what you might be expecting from what you did...
It's up to you what you wish to do with the watch now...
Keep it, replace it, sell it, etc...
your call...
Bro can i get indian firmware link my friend flashed stock CSC again in his watch 3, i also want to flash it in my watch 4 (wifi)My role is complete...
I told you what you might be expecting from what you did...
It's up to you what you wish to do with the watch now...
Keep it, replace it, sell it, etc...
your call...
Thanks bro is there any way i can brick this watch?
Then i will claim replacement
There is a big chance samsung will reject bricked Watch saying it was abused and they will need proof of how it bricked...Bro can i get indian firmware link my friend flashed stock CSC again in his watch 3, i also want to flash it in my watch 4 (wifi)
Ok i will visit service centre and will check what they will tell meThere is a big chance samsung will reject bricked Watch saying it was abused and they will need proof of how it bricked...
And no, WearOS was never released to public yet, so no flashing avaliable...
Did some changed with the latest watchupdates regarding wifi debugging
I can connect to my watch, but it always stays offline
Dunno, post your number of update and will see
You probably were slow to allow / grant access from your PC.Did some changed with the latest watchupdates regarding wifi debugging
I can connect to my watch, but it always stays offline
adb disconnect <IP:port>
adb connect <IP:port>
adb kill-server
adb connect <ip:port>
It's called soft color + on facer but since facer battery drain, I decided to recreate the watchface, you can find it on Playstore, look for geminiman watchfaces case, install the app and find the face from thereHi Dante do you remember what's the name of that wallpaper on the watch? thank you
Thank you sirIt's called soft color + on facer but since facer battery drain, I decided to recreate the watchface, you can find it on Playstore, look for geminiman watchfaces case, install the app and find the face from there
If you're talking about the shm mod companion, just set check updates to never...Thank you very much for this adapted app version @Dante63 ! It works very well.
As another user had asked before, I was wondering if it would be possible to allow/enable toggling on/off the background activity of the Wear OS app. I understand that you said it uses around 1% of battery but I think toggling background off could help save battery. I hope it's possible to implement this.
Thanks again!
SH BP sync, as in Samsung Health BP sync, thus, Samsung Health app, don't mix between Samsung Health and Samsung Health Monitor, two different apps...Hello, trying to go through the instructions and have tried searching the thread, but have gotten stuck on enabling "set features" within the Samsung Health Monitor app. I've been tapping on the version # for a while now (I included a screenshot and circled where I'm tapping), but nothing pops up. I've tried installing the companion app and had it successfully Enable SetFeatures. I've also tried force stopping app, clearing cache, and restarting phone, but I can never get "set features" to show up. Not sure what I'm doing wrong?
I'm using a Pixel 6 Pro running 13.
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!
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)
pm disable-user --user 0 com.samsung.android.shealthmonitor
and exiting the shell and disconnecting... instructions updated...