Was this useful and you were satisfied with the outcome...?


  • Total voters
    538
Search This thread

arjaykumar1

Member
Nov 1, 2020
29
2
Calmly read what I said,
Samsung made a mess and changed their server URL to the wrong one...

So no one can create certificates at all, you're not alone, there are thousands others waiting...
Bro all process is done and I also got a certificate but I unable to flash it if flash the this type of error showing

See the photos

And tell me what I do next
 

Attachments

  • IMG20220621214553.jpg
    IMG20220621214553.jpg
    3.7 MB · Views: 73
  • IMG20220621214558.jpg
    IMG20220621214558.jpg
    4.1 MB · Views: 70
  • IMG20220621212130.jpg
    IMG20220621212130.jpg
    3.9 MB · Views: 74
Bro all process is done and I also got a certificate but I unable to flash it if flash the this type of error showing

See the photos

And tell me what I do next
Oh, forgive me, thought you were still referring to the 408 error...

The issue you're having now is completely different, nothing is signed because of either your username having space or long path, it's a windows limitation, hence why I focus on saying keep path simple and short by placing Fit2Installer directly on your C drive or any drive and save yourself from a headache... once you run the command, you won't see the error "the system can't find the path specified"...

Windows will execute the command but it won't do anything, just skip through the lines to generate the output file being unsigned (if it actually even manage to do that)...

So move Fit2Installer to C drive, run it again and all should be fine...
 
Hello, got the cert in tizen studio.. but when I go on with the others steps.. I ran into a problem :
this is what fit2installer is saying.. but I did sign first successfully with the password..

__return_cb req_id[1] pkg_type[tpk] pkgid[com.samsung.health.sams.bp] key[start] val[install]
__return_cb req_id[1] pkg_type[tpk] pkgid[com.samsung.health.sams.bp] key[install_percent] val[12]
__return_cb req_id[1] pkg_type[tpk] pkgid[com.samsung.health.sams.bp] key[install_percent] val[15]
__return_cb req_id[1] pkg_type[tpk] pkgid[com.samsung.health.sams.bp] key[install_percent] val[18]
__return_cb req_id[1] pkg_type[tpk] pkgid[com.samsung.health.sams.bp] key[install_percent] val[21]
__return_cb req_id[1] pkg_type[tpk] pkgid[com.samsung.health.sams.bp] key[install_percent] val[25]
__return_cb req_id[1] pkg_type[tpk] pkgid[com.samsung.health.sams.bp] key[install_percent] val[28]
__return_cb req_id[1] pkg_type[tpk] pkgid[com.samsung.health.sams.bp] key[error] val[-12] error message: :Invalid signature. Signed with wrong key, changed signature file or changed package file.:<-4>
__return_cb req_id[1] pkg_type[tpk] pkgid[com.samsung.health.sams.bp] key[end] val[fail]
processing result : Check certificate error [-12] failed
spend time for pkgcmd is [3055]ms
* The version of SDB client (2.3.0) is not same with that of SDB server (4.2.16).
It may cause version compatibility problems.
It is recommended to use SDB server with version 2.3.0. *

any idea ?
Screenshot is better than copy and pasting... I'm assuming you're trying to push the mod to your watch but it got rejected...? Because I see two things that might be an issue, either you can't push Because of 2 sdb running or you are installing the unsigned shm mod (you grabbed it from sign_me instead of install_me)...

So which problem are you facing...?
 

arjaykumar1

Member
Nov 1, 2020
29
2
Oh, forgive me, thought you were still referring to the 408 error...

The issue you're having now is completely different, nothing is signed because of either your username having space or long path, it's a windows limitation, hence why I focus on saying keep path simple and short by placing Fit2Installer directly on your C drive or any drive and save yourself from a headache... once you run the command, you won't see the error "the system can't find the path specified"...

Windows will execute the command but it won't do anything, just skip through the lines to generate the output file being unsigned (if it actually even manage to do that)...

So move Fit2Installer to C drive, run it again and all should be fine...
thanks for helping me i enjoy talking to you.
and you are a very nice person
Have a grate day BRO
 
  • Love
Reactions: Dante63

pabowens

New member
May 12, 2009
4
2
Thanks for a detailed guide. This works for my galaxy watch 3. The only problem I have is the Blood Oxygen is still missing. Is there any way I can add it in my watch as well?
@Dante63 I hope all is well. I am in a similar boat. The difference was I watched another video that had me flash firmware R840XXU1ATF3 and since after that I lost blood oxygen. I was hoping you have another firmware that has blood oxygen? I followed a video that had me pull the csc file from the watch, change it and add it back. Not sure if it was that or FW. I went under common and changed the region from us to gb. I appreciate your help in advance.
 
  • Like
Reactions: Dante63

pabowens

New member
May 12, 2009
4
2
@Dante63 I hope all is well. I am in a similar boat. The difference was I watched another video that had me flash firmware R840XXU1ATF3 and since after that I lost blood oxygen. I was hoping you have another firmware that has blood oxygen? I followed a video that had me pull the csc file from the watch, change it and add it back. Not sure if it was that or FW. I went under common and changed the region from us to gb. I appreciate your help in advance.
I forgot to add when I check for update it says I'm up to date version R840XXU1ATF9. So I am not sure how blood oxygen disappeared if I have the latest fw version.
 
I forgot to add when I check for update it says I'm up to date version R840XXU1ATF9. So I am not sure how blood oxygen disappeared if I have the latest fw version.
Unfortunately I'm not familiar with changing watch CSC, those enquiries should be posted in the threads relevant to CSC changing...

I do hope you can get it back...
 

arjaykumar1

Member
Nov 1, 2020
29
2
Oh, forgive me, thought you were still referring to the 408 error...

The issue you're having now is completely different, nothing is signed because of either your username having space or long path, it's a windows limitation, hence why I focus on saying keep path simple and short by placing Fit2Installer directly on your C drive or any drive and save yourself from a headache... once you run the command, you won't see the error "the system can't find the path specified"...

Windows will execute the command but it won't do anything, just skip through the lines to generate the output file being unsigned (if it actually even manage to do that)...

So move Fit2Installer to C drive, run it again and all should be fine...
Bro
Tpk/Wgt sign problem was now solved
But then a new problem has come i unable to push/install tpk or Wgt file
And i also try to install from tizen device manager but they show me -1 error

See the photos

Bro i don't know what to do next I'm so upset I try every day and every day I'm disappointed

Please tell me what I do next 😔
Thanks you for your reply
(Again) please reply as soon as possible
I can't wait because I am at the last point of getting SHM feature
don't get me wrong I am only curious to install SHM mode
(Agani) thanks you
 

Attachments

  • IMG20220622192845.jpg
    IMG20220622192845.jpg
    3.6 MB · Views: 32
  • IMG20220622193711.jpg
    IMG20220622193711.jpg
    4.2 MB · Views: 33
Bro
Tpk/Wgt sign problem was now solved
But then a new problem has come i unable to push/install tpk or Wgt file
And i also try to install from tizen device manager but they show me -1 error

See the photos

Bro i don't know what to do next I'm so upset I try every day and every day I'm disappointed

Please tell me what I do next 😔
Thanks you for your reply
(Again) please reply as soon as possible
I can't wait because I am at the last point of getting SHM feature
don't get me wrong I am only curious to install SHM mode
(Agani) thanks you
Open task manager, look for all sdb.exe and end them... run Fit2Installer again and hit install option...

This error happens due to having tizen studio sdb and Fit2Installer sdb running side by side in background, only one should be running...
 
  • Like
Reactions: arjaykumar1

arjaykumar1

Member
Nov 1, 2020
29
2
Open task manager, look for all sdb.exe and end them... run Fit2Installer again and hit install option...

This error happens due to having tizen studio sdb and Fit2Installer sdb running side by side in background, only one should be running...
Bro
Still not installing giving error😥
See a photo
 

Attachments

  • IMG20220622213846.jpg
    IMG20220622213846.jpg
    5.9 MB · Views: 47

pabowens

New member
May 12, 2009
4
2
Unfortunately I'm not familiar with changing watch CSC, those enquiries should be posted in the threads relevant to CSC changing...

I do hope you can get it back...
Hello Dante63, I appreciate the response. I apologize if I was in the wrong thread. I got it working. I was able to flash fw R840XXU1BTG6 and got it back. Best of all everything I did for bp and ecg still works. I appreciate you going the extra step making the app and the step by step videos and responding to everyone.
 
  • Like
Reactions: Dante63
Hello Dante63, I appreciate the response. I apologize if I was in the wrong thread. I got it working. I was able to flash fw R840XXU1BTG6 and got it back. Best of all everything I did for bp and ecg still works. I appreciate you going the extra step making the app and the step by step videos and responding to everyone.
Glad it hear you got things working again, and no problem 😊
 

Gurv69

New member
Jun 15, 2022
3
1
Hello, got the cert in tizen studio.. but when I go on with the others steps.. I ran into a problem :
this is what fit2installer is saying.. but I did sign first successfully with the password..

__return_cb req_id[1] pkg_type[tpk] pkgid[com.samsung.health.sams.bp] key[start] val[install]
__return_cb req_id[1] pkg_type[tpk] pkgid[com.samsung.health.sams.bp] key[install_percent] val[12]
__return_cb req_id[1] pkg_type[tpk] pkgid[com.samsung.health.sams.bp] key[install_percent] val[15]
__return_cb req_id[1] pkg_type[tpk] pkgid[com.samsung.health.sams.bp] key[install_percent] val[18]
__return_cb req_id[1] pkg_type[tpk] pkgid[com.samsung.health.sams.bp] key[install_percent] val[21]
__return_cb req_id[1] pkg_type[tpk] pkgid[com.samsung.health.sams.bp] key[install_percent] val[25]
__return_cb req_id[1] pkg_type[tpk] pkgid[com.samsung.health.sams.bp] key[install_percent] val[28]
__return_cb req_id[1] pkg_type[tpk] pkgid[com.samsung.health.sams.bp] key[error] val[-12] error message: :Invalid signature. Signed with wrong key, changed signature file or changed package file.:<-4>
__return_cb req_id[1] pkg_type[tpk] pkgid[com.samsung.health.sams.bp] key[end] val[fail]
processing result : Check certificate error [-12] failed
spend time for pkgcmd is [3055]ms
* The version of SDB client (2.3.0) is not same with that of SDB server (4.2.16).
It may cause version compatibility problems.
It is recommended to use SDB server with version 2.3.0. *

any idea ?
all works now thanks again for your time and expertise :)
 
  • Like
Reactions: Dante63

sohebq

Senior Member
Aug 20, 2011
3,438
604
RAWALPINDI
For last 3 days i am trying best to install through tizen studio but it is frustrating. I managed to make ecg work but not bp. Any easy way out?
 

Zotyoo

Member
Jul 11, 2015
43
11
Dear Dante63! I have been using SHM MOD for a long time, which works perfectly. He wrote a Companion program that is available in version 1.2.0. It works on your phone. There was a Watch menu, the essence of which would be to be able to install or update the SHM MOD program from the phone using the application up to the hour. It works on the phone, but there would also be a version 1.1.0 of the Companion app for the watch that you can’t put on. It displays the following error message: "There was a problem parsing the package". I downloaded the app for the watch, but it doesn’t allow me to install it either over the phone or using Easy Fire Tools. Do you have any idea why Companion will not be installed on the watch? This has not been the case so far and I put SHM MOD in Sideload and it works. This program would make it easier to keep your applications up to date. Especially if you could be notified when a new version is available. For now, it would also be good to be able to put on the clock somehow, for which you throw a mistake for some reason. Thank you for your answer in advance!
Phone: Samsung S10 rooted
Watch: Samsung Galaxy Watch 4 (SM-R875F)
 
Dear Dante63! I have been using SHM MOD for a long time, which works perfectly. He wrote a Companion program that is available in version 1.2.0. It works on your phone. There was a Watch menu, the essence of which would be to be able to install or update the SHM MOD program from the phone using the application up to the hour. It works on the phone, but there would also be a version 1.1.0 of the Companion app for the watch that you can’t put on. It displays the following error message: "There was a problem parsing the package". I downloaded the app for the watch, but it doesn’t allow me to install it either over the phone or using Easy Fire Tools. Do you have any idea why Companion will not be installed on the watch? This has not been the case so far and I put SHM MOD in Sideload and it works. This program would make it easier to keep your applications up to date. Especially if you could be notified when a new version is available. For now, it would also be good to be able to put on the clock somehow, for which you throw a mistake for some reason. Thank you for your answer in advance!
Phone: Samsung S10 rooted
Watch: Samsung Galaxy Watch 4 (SM-R875F)
You're in the wrong thread but no problem...
Seems to me the package you downloaded is corrupted, try downloading it again using a different browser and make sure no antivirus on your phone is scanning it, antivirus tend to break the manifest as it extracts and compress the apk, the companion should be installed normally like the watch shm mod...
 

Top Liked Posts

  • There are no posts matching your filters.
  • 188
    Hello Everyone,
    I hope you all are fine...


    Tizen-Lockup-On-Light-RGB.png


    ~~~ TIZEN WATCHES ONLY ~~~
    20220106_171450.jpg20220106_202449.png
    ~~~ FEATURES, BUGS & FUTURE WORKS~~~
    • FEATURES: Works on Active2 and Watch3 (as mentioned, Samsung Tizen Watches), Multilanguage, no root detection, no country restriction, no device restriction, age limit lowered from 22 to 16, no lock screen restriction, No Force update to latest version) for phone, as for the watch, SHM multilanguage 1.1.00453...
    • BUGS: None...
    • BP SYNC between SHM and SH: There is an Entire Section that explains it in detail, don't miss it if you want this to work...
    • About ECG in SH: ECG has never synced to Samsung Cloud, since the first release of SHM, the ECG tile has no use other than being a shortcut to open SHM at ECG tab...
    • SHM ChangeLog: see Post #2
    • CRASHING?: few devices crash at application start and few others crash after completing the profile, logs showed each device has a different problem, I'm not considering this as a bug but you can ask me and I'll try to help...
    • IMPORTANT NOTE ABOUT POSTING: Please search the thread first before posting your problem, provide details, screenshot, videos if possible, do not just say "it's not working" or "it's crashing", details are important if you want me to help you and to get it fast...
    • FUTURE WORKS: none...
    • NOTE FOR SAMSUNG ROOT USERS: Device encryption will play a big role if you leave it, you most likely will end up with error ERR_INTEGRITY which makes shm refuse to communicate with the watch... the solution would be flashing encryption disabled - you also need knox patched...

    • IMPORTANT NOTE ABOUT POSTING: Please read the F.A.Q and search the thread first before posting your problem, PROVIDE DETAILS, SCREENSHOT, VIDEOS IF POSSIBLE, DO NOT JUST SAY "IT'S NOT WORKING" OR "IT'S CRASHING", details are important if you want me to help you and to get it fast...

    If you are confused on XDA, here is a brief view on Github:

    ~~~ FOR WearOS (Watch4 And Above), LINK BELOW~~~


    ~~~ SHM MOD F.A.Q ~~~
    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:

    1. 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...
    2. Do I need root...?
      No root is required...
    3. Does this void my warranty?
      No it does not void the warrenty or trip the know or damage the watch or the phone...
    4. OTA effect on MOD & MOD effects on OTA.
      No Effects, the MOD is independant...
    5. 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...
    6. 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...

    ~~~ REPORTING AN ISSUE WITH SHM MOD ~~~

    Tell me your device type and Android version, provide me a screenshot or video of where it happened and how, a logcat is appreciated, these details will help me re-create the environment and try to get the issue you have so I can trace it and fix it...

    ~~~ Tizen - Active2 & Watch3 - How to install SHM MOD - Tutorial - XDA - Dante63 ~~~

    If you can't see the YouTube video, visit the YouTube link: https://youtu.be/6foHp4LDVd0

    ~~~ FILES and Description ~~~
    Here is the link to the files I am using:
    I believe the folders describe themselves, the APK at the root is to be installed on your phone...

    ~~~ SHM MOD Companion ~~~
    ~~~ Get updates, Enable BP Sync and Much More ~~~

    If you can't see the YouTube video, visit the YouTube link: https://youtu.be/QzYjqrgnKU0


    ~~~ ENABLING BP SYNC BETWEEN SHM & SH ~~~
    If you can't see the YouTube video, visit the YouTube link: https://youtu.be/-4eetNuHFco

    ~~~ Using latest Samsung Health on Rooted Device ~~~
    Thanks to XDA @73sydney , quoting the solution for bypassing Samsung Health root detection, no more using Samsung Health MOD...

    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:

    • 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)
    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)
    Please use the Knox Patch Module:
    Thanks to XDA @BlackMesa123
    You can also find a thread here:
    XDA - Knox Patch

    ~~~ Special Thanks ~~~
    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...
    ~~~ ABOUT THE ORIGINAL SHM ~~~
    According to Samsung, The Samsung Health Monitor app requires a Galaxy Watch Active2 or Galaxy Watch3 and later models, alongside having Android version 7.0 and above...

    SHM has device detection, country restriction and spoof location detection, the following countries were listed in the country restriction checking, I believe if you live in those countries, SHM should Work, otherwise, it wouldn't, SHM checks your GeoLocation, Sim Card, and Device CSC (if no sim or location provided)

    List of Country Codes Alpha-2:
    EU_CSC (Total 35):
    "AT"
    "BE"
    "BG"
    "CZ"
    "DE"
    "DK"
    "EE"
    "ES"
    "FI"
    "FR"
    "GR"
    "HR"
    "HU"
    "IE"
    "IT"
    "LT"
    "LV"
    "NL"
    "PL"
    "PT"
    "RO"
    "SE"
    "SI"
    "SK"
    "CY"
    "LU"
    "MT"
    "GB"
    "CH"
    "IS"
    "NO"
    "LI"
    "TR"
    "RS"
    "CY"
    EU_MNC (Total 29):
    "AT"
    "BE"
    "BG"
    "CH"
    "CZ"
    "DE"
    "DK"
    "EE"
    "ES"
    "FI"
    "FR"
    "GB"
    "GR"
    "HR"
    "HU"
    "IE"
    "IS"
    "IT"
    "LT"
    "LV"
    "NL"
    "NO"
    "PL"
    "PT"
    "RO"
    "SE"
    "SI"
    "SK"
    "CY"
    NON-EU (Total 14):
    "KR"
    "US"
    "BR"
    "CL"
    "AE"
    "ID"
    "HK"
    "RU"
    "SG"
    "AZ"
    "GE"
    "PY"
    "AU"
    "TW"

    SHM will work only if the following is not detected on your Samsung Device:
    Paths:
    "/data/local/"
    "/data/local/bin/"
    "/data/local/xbin/"
    "/sbin/"
    "/su/bin/"
    "/system/bin/"
    "/system/bin/.ext/"
    "/system/bin/failsafe/"
    "/system/sd/xbin/"
    "/system/usr/we-need-root/"
    "/system/xbin/"
    "/system/app/Superuser.apk"
    "/cache"
    "/data"
    "/dev"
    Apps:
    "com.noshufou.android.su"
    "com.noshufou.android.su.elite"
    "eu.chainfire.supersu"
    "com.koushikdutta.superuser"
    "com.thirdparty.superuser"
    "com.yellowes.su"
    "com.devadvance.rootcloak"
    "com.devadvance.rootcloakplus"
    "de.robv.android.xposed.installer"
    "com.saurik.substrate"
    "com.zachspong.temprootremovejb"
    "com.amphoras.hidemyroot"
    "com.amphoras.hidemyrootadfree"
    "com.formyhm.hiderootPremium"
    "com.formyhm.hideroot"
    "com.koushikdutta.rommanager"
    "com.koushikdutta.rommanager.license"
    "com.dimonvideo.luckypatcher"
    "com.chelpus.lackypatch"
    "com.ramdroid.appquarantine"
    "com.ramdroid.appquarantinepro"
    Binary:
    "su"
    "busybox"
    SU:
    "/system/xbin/which"
    "su"
    Test-Keys:
    "test-keys"
    ~~~ Don't forget to ~~~
    Don't forget to smash the (y)THANKS (y)
    PS. if you are super happy and want to thank me, It is highly appreciated if you'd consider supporting me through my Patreon Page ❤️ 😊monthly or one time through PayPal ...


    You can also support me through Google Play by installing:
    Sadly, the Watchfaces you see are only for WearOS, not Tizen, and I do not make Tizen Watchfaces...

    ✯ XDA: https://xdaforums.com/m/dante63.7047928/
    ✯ Reddit: https://www.reddit.com/user/XDA-Dante63/
    ✯ Telegram: https://t.me/xda_dante63
    36
    What's New:
    Latest Changes:

    SHM MOD Companion Phone 4.6.0
    • Paid CDN servers for hosting files for Companion to use...
    Phone (TIZEN & WEAROS) SHM MOD 1.2.4.003 (Android 9 and above)
    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...

    TIZEN WATCH SHM END OF LIFE - 1.1.0053 is the last version released...
    No version will be released after this according to Samsung Galaxy Store:

    1699706953615.png

    Enjoy...

    Previous Release:
    Changelog History Moved to Github:
    21
    Download SHM MOD Companion from here if Google Drive reaches its limit...
    13
    Update update update, a wonderful amazing update for all watch4 owners and those who ordered it
    SHM works on watch4,
    Still going through heavy tests to ensure it is at its best form and most features active...
    I will release it in 1-2 days...
    8
    I am going to start organizing the Thread for Watch4 *Excitement* lol