Ticket Created
over 3 years ago

WERETECH-9599

This is a known issue that should be addressed in a future SDK.

problem with SpO2

4.1.3/eclipse/win

1. Due to the problem with battery draining I've switched off SpO2 on watch but

ACT.getActivityInfo().currentOxygenSaturation

still returns value - it's probably the latest reading but it can named "current" - I can see value last is 24h old.

But when sensor is off currentOxygenSaturation should be rather simple null.

2. I don't when something change but now there is additional problem with getNewestSampleTime().value() from SpO2 sensor iterator

- on sim it is rather ok

- on device f6p 21.80 - returns rather not newest sample timestmap but timestamp of attempting reading value (I can't see the same value like in widget but usually can see value very close to now())

_psx_
  • over 3 years ago

    This is a known issue that should be addressed in a future SDK.

    The strange thing is that everything was good on f6p but changed with new firmware - it means bugged functionality from one device was implemented to other.

    BTW, still exist bug (unhandled exception) on f6s (on sim I don't know if it happens on device) then calling:

    SHI.getOxygenSaturationHistory(null);

  • over 3 years ago

    samples in sensor SpO2 history after conversion (Sample0.data ? Sample0.data.toFloat().format("%.1f") : "---") now looks like

    9999999999999999893774739473192.0

    iterator.getMin()  =>  0
    iterator.getMax()  => 2147483647

    I've check others SDK to 3.25 an the same effect so it has to be problem with new firmware but how to report it?