SpO2 TPK

Search This thread
By:
Advanced…
S

sixtybi

Member
Dec 14, 2011
33
1
adfree said:
Code: 
sdb root on

sdb shell mount -vo remount,rw /opt/system/csc/



sdb push SW_Configuration.xml /opt/system/csc/mps/CSC/

sdb push home_default_items.xml /opt/system/csc/preconfig/DEF/usr/homescreen/

First attempt...

Changed 1 Byte to prevent CTI4 FOTA...


@betterl8thannvr

Your Model Name is what?

Because I've play with my SM-R820...

Best Regards
Click to expand...
Click to collapse

What do I need to change in SW_Configuration.xml to prevent FOTA updates?
 
A

adfree

Senior Member
Jun 14, 2008
10,619
6,175
Samsung Galaxy Watch 4
Samsung Galaxy S22
@sixtybi

Check this:
https://xdaforums.com/showpost.php?p=83828175&postcount=976

You can use 7Zip Tool to extract...

I have changed CTI4 into TEST...

Only change MAXIMUM 4 Bytes...

Because many scripted s h it inside... to prevent "funny" sideeffects...

It would be enough if you change 1 Byte:
Code: 
CTI4
into
Code: 
CT[COLOR="Red"][B]l[/B][/COLOR]4

L insted I

Then database request for FOTA not find valid text string... :cowboy:

Best Regards
 
S

sixtybi

Member
Dec 14, 2011
33
1
adfree said:
@sixtybi

Check this:
https://xdaforums.com/showpost.php?p=83828175&postcount=976

You can use 7Zip Tool to extract...

I have changed CTI4 into TEST...

Only change MAXIMUM 4 Bytes...

Because many scripted s h it inside... to prevent "funny" sideeffects...

It would be enough if you change 1 Byte:
Code: 
CTI4
into
Code: 
CT[COLOR="Red"][B]l[/B][/COLOR]4

L insted I

Then database request for FOTA not find valid text string... :cowboy:

Best Regards
Click to expand...
Click to collapse

And do you know how can I remove the notification on the phone? FOTA disabled with this method has applied only after I have been notified about new firmware. And I can't remove this notification.I have reset the watch, the android app, everything, it is still there. Removed the delta.tar on the watch on fota folder.
Thanks!
 
G

gauravinvouge

Senior Member
Mar 3, 2009
226
11
adfree said:
All files are extracted from CTI4 Firmware (SM-R820).



Code: 
sdb root on

sdb shell mount -vo remount,rw /

sdb push shealth-measure /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth-service /usr/apps/com.samsung.shealth_gear/bin

sdb push w-home /usr/apps/com.samsung.w-home/bin/

Only working with ROOT...

And only for preinstalled Version of SHEALTH...
Code: 
package="com.samsung.shealth_gear" version="[B]4.10.10100[/B]"

Best Regards

Edit 1.
Sorry, v2 worked only for SM-R820. :eek:

Added v3... hopefully work now on both:
SM-R820 and SM-R830
Click to expand...
Click to collapse

hi adfree thanks in advance as based on your directions i ws able to run ecg and bp on my active watch 2 with one plus 6 on tizen 5.5.0.1

pls now guide me how to go about what you've explained above in a bit detail.
rgds
 
A

adfree

Senior Member
Jun 14, 2008
10,619
6,175
Samsung Galaxy Watch 4
Samsung Galaxy S22
Progress in Research. :good: :cool:

But no final solution... for GWA2...

Here some infos about status and problem(s)...

If somebody have ideas or solution. Feel free to post or to PM me.

Best Regards

These are NOT my findings... I am posting only part from our conversation...

...they have identical sensors but difference access path ...

SM-R840

I/SYSLOG_KERN(P 0, T 0): [SSP] initialize_variable_iio start
I/SYSLOG_KERN(P 0, T 0): [SSP] initialize_variable_iio end
I/SYSLOG_KERN(P 0, T 0): input: accelerometer_sensor as /devices/virtual/input/input2
I/SYSLOG_KERN(P 0, T 0): input: accelerometer_32gsensor as /devices/virtual/input/input3
I/SYSLOG_KERN(P 0, T 0): input: gyro_sensor as /devices/virtual/input/input4
I/SYSLOG_KERN(P 0, T 0): input: uncal_gyro_sensor as /devices/virtual/input/input5
I/SYSLOG_KERN(P 0, T 0): input: pressure_sensor as /devices/virtual/input/input6
I/SYSLOG_KERN(P 0, T 0): input: light_sensor as /devices/virtual/input/input7
I/SYSLOG_KERN(P 0, T 0): input: ecg_fac_sensor as /devices/virtual/input/input8
I/SYSLOG_KERN(P 0, T 0): input: ecg_lib_sensor as /devices/virtual/input/input9
I/SYSLOG_KERN(P 0, T 0): input: LPM_MOTION as /devices/virtual/input/input10
I/SYSLOG_KERN(P 0, T 0): input: hrm_raw_sensor as /devices/virtual/input/input11
I/SYSLOG_KERN(P 0, T 0): input: hrm_lib_sensor as /devices/virtual/input/input12
I/SYSLOG_KERN(P 0, T 0): input: ssp_context as /devices/virtual/input/input13
I/SYSLOG_KERN(P 0, T 0): [SSP]: sensor_motor_callback result : 0
I/SYSLOG_KERN(P 0, T 0): [SSP]: ssp_probe - probe success!
I/SYSLOG_KERN(P 0, T 0): input: pressure_sensor1 as /devices/virtual/input/input14

SM-R830

I/SYSLOG_KERN(P 0, T 0): [SSP] initialize_variable_iio start
I/SYSLOG_KERN(P 0, T 0): [SSP] initialize_variable_iio end
I/SYSLOG_KERN(P 0, T 0): input: accelerometer_sensor as /devices/virtual/input/input3
I/SYSLOG_KERN(P 0, T 0): input: accelerometer_32gsensor as /devices/virtual/input/input4
I/SYSLOG_KERN(P 0, T 0): input: gyro_sensor as /devices/virtual/input/input5
I/SYSLOG_KERN(P 0, T 0): input: uncal_gyro_sensor as /devices/virtual/input/input6
I/SYSLOG_KERN(P 0, T 0): input: pressure_sensor as /devices/virtual/input/input7
I/SYSLOG_KERN(P 0, T 0): input: light_sensor as /devices/virtual/input/input8
I/SYSLOG_KERN(P 0, T 0): input: ecg_fac_sensor as /devices/virtual/input/input9
I/SYSLOG_KERN(P 0, T 0): input: ecg_lib_sensor as /devices/virtual/input/input10
I/SYSLOG_KERN(P 0, T 0): input: LPM_MOTION as /devices/virtual/input/input11
I/SYSLOG_KERN(P 0, T 0): input: hrm_raw_sensor as /devices/virtual/input/input12
I/SYSLOG_KERN(P 0, T 0): input: hrm_lib_sensor as /devices/virtual/input/input13
I/SYSLOG_KERN(P 0, T 0): input: ssp_context as /devices/virtual/input/input14
I/SYSLOG_KERN(P 0, T 0): [SSP] ssp_enable, enable = 1, old enable = 1
I/SYSLOG_KERN(P 0, T 0): [SSP]: sensor_motor_callback result : 0
I/SYSLOG_KERN(P 0, T 0): [SSP]: ssp_probe - probe success!
I/SYSLOG_KERN(P 0, T 0): input: pressure_sensor1 as /devices/virtual/input/input15
Click to expand...
Click to collapse




Found the Error Message for SpO2 Activation on R830 -- Missing Library with wrong Lookup 0x41 ? Hmmm what library is that ?

These commands are actually part of the ADD LIBRARY COMMAND of SENSORHUB. Not sure which library is that. Need some research ...


SM-R840


I/SYSLOG_KERN(P 0, T 0): [SSP]: ssp_sensorhub_write - 55, 41, 1, 0 (4) ;SPO2_START, ADD LIBRARY
I/SYSLOG_KERN(P 0, T 0): [SSP]: send_instruction - Inst = 0x37, Sensor Type = 0x29, data = 1
I/SYSLOG_KERN(P 0, T 0): [SSP]: ssp_sensorhub_write - 53, 54, 1, 0 (4)
I/SYSLOG_KERN(P 0, T 0): [SSP]: send_instruction - Inst = 0x35, Sensor Type = 0x36, data = 1
I/SYSLOG_KERN(P 0, T 0): sensorhub_stat: sensorhub_stat_update_wear: 1 1
I/SYSLOG_KERN(P 0, T 0): sensorhub_stat: sensorhub_stat_update_wear: 1 1 0 71141 0
I/SYSLOG_KERN(P 0, T 0): [SSP]: ssp_sensorhub_list - 1, 1, 54, 1, 1, 1, 1, 41, 1, 0, 0, 1, 0, 64, 85, 21, 0, 64, 85, 21, 0, 109, 13, -97, 7, 24, 3, -80, -1, 0, 0, 0, 0 (33)
I/SYSLOG_KERN(P 0, T 0): [SSP]: print_mcu_debug : iLength: 255, LibraryState: 4ec16d0040d687a


SM-R830

I/SYSLOG_KERN(P 0, T 0): [SSP]: ssp_sensorhub_write - 55, 41, 1, 0 (4) ; SPO2_START ADD LIBRARY
I/SYSLOG_KERN(P 0, T 0): [SSP]: send_instruction - Inst = 0x37, Sensor Type = 0x29, data = 1
I/SYSLOG_KERN(P 0, T 0): [SSP]: ssp_sensorhub_write - 53, 54, 1, 0 (4)
I/SYSLOG_KERN(P 0, T 0): [SSP]: send_instruction - Inst = 0x35, Sensor Type = 0x36, data = 1
I/SYSLOG_KERN(P 0, T 0): [SSP]: ssp_sensorhub_write - 53, 3, 1, 0 (4)
I/SYSLOG_KERN(P 0, T 0): [SSP]: send_instruction - Inst = 0x35, Sensor Type = 0x3, data = 1
I/SYSLOG_KERN(P 0, T 0): [SSP]: MSG From MCU -
I/SYSLOG_KERN(P 0, T 0): [SSP]: ssp_sensorhub_list - 1, 1, 3, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0 (18)
I/SYSLOG_KERN(P 0, T 0): [SSP]: print_mcu_debug : iLength: 255, LibraryState: 4ec1460040d687a
I/SYSLOG_KERN(P 0, T 0): [SSP]: MSG From MCU - library_add : Wrong LookUp No. 41\x0a
I/SYSLOG_KERN(P 0, T 0): sensorhub_stat: sensorhub_stat_update_wear: 1 1
I/SYSLOG_KERN(P 0, T 0): sensorhub_stat: sensorhub_stat_update_wear: 1 1 0 40537 0
I/SYSLOG_KERN(P 0, T 0): [SSP]: ssp_sensorhub_list - 1, 1, 54, 1, 1 (5)
Click to expand...
Click to collapse



Current findings show that the message "Wrong LookUp No." came from "sensorhub.fw" a virtual sensor library found under /usr/apps/com.apps.samsung-watch-system-update/res/sensorhub/sensorhub.fw

If you execute the update program under /usr/apps/com.apps.samsung-watch-system-update/bin, it loads the resource file sensorhub.fw and is installed on the kernel as an extension library... hmmmmm

I am guessing that this is loaded as a sub library for the kernel. This is where the library program for AFE4920 is located based on HEX view scan. But looking at R820, R830, R840 firmware rootfs files, they all have identical sensorhub.fw . Maybe GW3 with Spo2 has a different version of sensorhub.fw ? This because R840 is using AFE4930 ? Or maybe the same with other watches but its looking for other library files if installed on GW3 ?
Click to expand...
Click to collapse
 
  • Like
Reactions: woof123
hamid.seyedani

hamid.seyedani

Senior Member
Oct 7, 2013
52
17
Tehran
adfree said:
Progress in Research. :good: :cool:

But no final solution... for GWA2...

Here some infos about status and problem(s)...

If somebody have ideas or solution. Feel free to post or to PM me.

Best Regards

These are NOT my findings... I am posting only part from our conversation...
Click to expand...
Click to collapse

Should we be disappointed or is it too early?
 
A

adfree

Senior Member
Jun 14, 2008
10,619
6,175
Samsung Galaxy Watch 4
Samsung Galaxy S22
Still NO final solution... :(

But still heavy Investigation from our user. :good: :good:
Thank you very much. :cowboy: :cool:

Leads to Kernel Action... dzImage...

https://opensource.samsung.com/uploadSearch?searchValue=SM-R

Later more... now only this...

Kernel Action leads to Knox dripped... :eek: :crying:

Best Regards
 

Attachments

  • sensorHubbytabbieDo_v1.jpg
    sensorHubbytabbieDo_v1.jpg
    254.8 KB · Views: 183
  • Like
Reactions: hamid.seyedani
M.Noury

M.Noury

Senior Member
Oct 19, 2007
496
125
Jeddah
I just got the GW3

Did you get what you need or shall I share it with you.

adfree said:
Still "we" stuck...

Without help of Galaxy Watch 3 user(s) maybe impossible... :eek:


Request is IMHO not toooo tough.


Code: 
sdb shell tail -f /var/log/dlog/system>bloodyOxy_v1.txt

During Blood Oxygen Measure...

You can write Private Mail to me.

Thanx in advance.


Best Regards
Click to expand...
Click to collapse
 
  • Like
Reactions: hamid.seyedani
You must log in or register to reply here.

Similar threads

nique0201
sPo2
Replies
38
Views
6K
T
Tribux
H
Galaxy Watch 3 Spo2 Problem
Replies
22
Views
7K
D
defeat2
V
[TPK Request] Spotify 2.5.40
Replies
1
Views
3K
N
niff2005
H
where to download .tpk or .wgt apps/files?
Replies
2
Views
4K
Santelite
Santelite
N
New GW3, latest software, missing (or can't find) SpO2
Replies
9
Views
4K
A
adfree

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 7
    A
    adfree
    Samsung not add Blood Oxygen in Tizen 5.5.0.2 for GWA2...
    😭

    But I will check our older findings... with SM-R820 DUA3...

    Test checklist...

    A
    This still work... so red LED not deactivated fully...

    B
    My Rooting is still working. So I have Root access in DUA3...


    C
    Maybe mistake... w-home trick seems not work... to enable BloodOxy Widget...
    Will check later again with open eyes...

    D
    Hmmm...
    sdb push w-manager-service /usr/apps/com.samsung.w-manager-service/bin/

    No luck yet to make the Widget visible like before...

    E
    sh-3.2# launch_app com.samsung.shealth.measure
    ... successfully launched

    Shows same "not avaliable"...

    Will proceed with SH mods...

    F
    Code: 
    usr\lib\libsensor-genuine.so.4.1.27
usr\lib\sensor\libsensor-hal.so


    Still 2 hits for search text string:
    SPO2_MONITOR_SENSOR
    View
    6
    A
    adfree
    Old method was to replace text string SM-R820 with SM-R840...

    In my tests with DUA3 SM-R820 I realized this is not "Driver switch"... but kind of blacklist...

    So my "new" method is:

    A
    Code: 
    sdb root on

sdb shell mount -vo remount,rw /

sdb push shealth-measure /usr/apps/com.samsung.shealth_gear/bin

    Only changed text string SM-R820 into SM-R821...


    B
    To start Blood Oxy I send Command:
    Code: 
    sdb shell launch_app com.samsung.shealth.measure


    This means only progress like before... but with less modified files...


    Now will try to do more text string changes... because SH TPK contain in every Binary Model Name text strings...
    Will check if blacklist stuff or something else...

    Best Regards
    View
    6
    A
    adfree
    Simple edit of manifest.xml allow me now to start Blood Oxygen in 3 wayS...

    Code: 
    D:\SDB\SDB260>sdb shell launch_app com.samsung.shealth.measure
... successfully launched

D:\SDB\SDB260>sdb shell launch_app com.samsung.shealth
... successfully launched

    2 Commands because I have simple replaced shealth with shealth-measure...

    And this allows me also by clicking the Icon...

    Now next changes... rename... to run also where SH is installed...
    I have Root and ways to deinstall...

    I am trying to simplify also for others...

    Best Regards
    View
    6
    D
    DamnFog
    I will be receiving a GW3 sometime next week. Not sure if I will keep it yet as it is probably to big for my skinny wrists :D.
    But I would be up to do the necessary testing for you @adfree
    View
    5
    A
    adfree
    Attempt 1.

    With changed text string inside 20 files from SH bin folder...

    Code: 
    sdb root on

sdb shell mount -vo remount,rw /

sdb push notification-service /usr/apps/com.samsung.shealth_gear/bin

sdb push scp-service /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth-alert-viewer /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth-breathe /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth-debug-menu /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth-exercise /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth-exercising-viewer /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth-health-data-permission /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth-heartrate-measure /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth-measure /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth-mindfulness /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth-multiworkout-widgetsetting /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth-sa-service /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth-sdk-data-service /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth-service /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth-stress-measure /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth-together-viewer /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth-whitelist-sync-service /usr/apps/com.samsung.shealth_gear/bin

sdb push shealth-widget /usr/apps/com.samsung.shealth_gear/bin

    Need then time to check if still working and to maybe find differences...

    Best Regards
    View

New posts