Toybox.SensorHistory.getOxygenSaturationHistory strange samples

I am getting really strange results reading the Toybox.SensorHistory.getOxygenSaturationHistory. Although it seems to work fine in the simulator, on the Fenix 6X pro I get extreme high e.g.55311017190201917345628160.000000 and extremely low e.g. -14393159110885376.000000 results among results around the 29 which is also very deadly when it would be an accurate spO2 reading. Also the values returned by the iterator may differ between subsequent calls. Is this a bug in the recently released 3.2 SDK? is anyone else also experiencing this issue?

Evosys

TheMagician over 4 years ago in reply to Bastos65

Bug is still valid for latest beta firmware of the f6x series v11.75
- Cancel
- Up 0 Down
- More
- Cancel
Bastos65 over 4 years ago in reply to TheMagician

Will try it, thank for the tip.
- Cancel
- Up 0 Down
- More
- Cancel

TheMagician over 4 years ago in reply to Bastos65

To get the last available spo2 value you can use this:

var ActivityInfo = Activity.getActivityInfo();
var oxygenSaturation = ActivityInfo != null and ActivityInfo has :currentOxygenSaturation ? ActivityInfo.currentOxygenSaturation : null;
if (oxygenSaturation != null) {
    dc.drawText(x, y, font, oxygenSaturation, alignment);
}

Works perfectly e.g. with the F6X series.

Bastos65 over 4 years ago

Ok, thank.

I guess we only can use history in watchfaces.

Then I will wait firmwares fix to add function in my watchfaces.

Regards.
- Cancel
- Up 0 Down
- More
- Cancel
jim_m_58 over 4 years ago in reply to Bastos65

The 945 and 245 are impacted, but I'll bet it's any device with a 3.2 VM, so things like the va4 and venu too. So anything with getOxygenSaturationHistory.

Sensor.getInfo().oxygenSaturation works, but that's only the current reading where a reading occurs once an hour. The history is also only saved every hour too.
- Cancel
- Up 0 Down
- More
- Cancel