1. What is DUID?1. Your certificates have the watch DUID...?
2. Did you use the mod wgt or original...?
3. Did you see any error when you signed the wgt...?
2. Used the mod
3. No errors at all
1. What is DUID?1. Your certificates have the watch DUID...?
2. Did you use the mod wgt or original...?
3. Did you see any error when you signed the wgt...?
How did you create your certificates?
1. Not sure what you're trying to say but the watch can pair to one device at a time, changing device means watch reset...Please note getting the following error while pairing my Active 2 watch with Tizen Studio device manager. Please note following :-
1) This watch was successfully paired to another phone using your tutorial. Now I am trying to pair it with another phone. The watch has already been reset.
2) I confirm Developer option is On, Debugging is turned On, both PC and Watch are connected to same network, WIFI is "Always On", IP address is correct, JDK15 installed.
Can't help you without you telling me what you've done...
Hmm, maybe I missed checking the DUID. Let me try installing once more from scratch.How did you create your certificates?
Look at the video at 11:00
Tizen watch accepts 2 sideloads, Samsung signed apps and self-signed apps that contain watch DUID, anything else the watch will reject it...Hmm, maybe I missed checking the DUID. Let me try installing once more from scratch.
I have installed SHM - 1.1.1.191 and followed the instructions, but SHM is not pairing with watch 3
Does the watch have shm on it?I have installed SHM - 1.1.1.191 and followed the instructions, but SHM is not pairing with watch 3
I can't see it
That's the problem then, shm can't work on its own, it needs a watch with shm as well
Shouldn't be a problem, just use the official installer with stock shm on your phone, your phone will push it to your watch and install it...
I have removed the SHM mod and reinstalled the official version, but the watch still doesn't have SHMShouldn't be a problem, just use the official installer with stock shm on your phone, your phone will push it to your watch and install it...
No no, for the tizen watch, there is official watch shm and mod shm, you install the mod when you can't install the official or the official has missing features (no BP)I have removed the SHM mod and reinstalled the official version, but the watch still doesn't have SHM
Ok, I fixed it
View attachment 5617289
I installed APK4TPK Installer attempt APK and it was successfulNo no, for the tizen watch, there is official watch shm and mod shm, you install the mod when you can't install the official or the official has missing features (no BP)
Did the entire process from scratch, everything works fine now. Thanks!Tizen watch accepts 2 sideloads, Samsung signed apps and self-signed apps that contain watch DUID, anything else the watch will reject it...
You can updateDid the entire process from scratch, everything works fine now. Thanks!
Just wanted to know if Tizen updates would break the functionality (GW3)?
Facer -> soft color+which watch face you are using on your watch3 shown in new tutorial.
Everything should be in the Google drive!
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://xdaforums.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...
Here is what I observed on phone SHM 1.2.4.003:
GUI:
- assets has country code IN - india with both BP and ECG documents, this is a clear indicator of support...
- plenty of permissions removed, this will probably solve the issue of SHM being flagged by TotalVirus (I already checked, this apk is safe)...
- Diagnostic added (might be for Samsung Members aka Samsung devices only)
- backup service updated (this might be backup and restore logic activated)
- Samsung India address added...
- I can see Sleep duration strings, not sure what this is, I will know when I look at the code...
CODE:
- CSCUtil confirms India got ECG and BP but not IHRN...
- I can confirm sleep layout and sleep tracking added but I do not see it being used anywhere nor even called - I can confirm sleep is not active from the manifest, probably future implementation...