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

MobileDriveway over 2 years ago

Any updates on this? I'm testing getOxygenSaturationHistory in my app on Fenix 6X, and results are all over the place - from extremely high (like in the original post) to 0 and everything in between (got 12 for example).
- Cancel
- Up 0 Down
- More
- Cancel
Makkas-CIQ over 2 years ago

Travis.ConnectIQ Hello. Any news here from Garmin? This post is 9 months old and it seems that getOxygenSaturationHistory is still pretty much bugged. Wrong order, weird samples...

Thanks.
- Cancel
- Up 0 Down
- More
- Cancel
jim_m_58 over 3 years ago in reply to 9517925

Still messed up with the latest FW on a 945 as of this morning. The readings look ok, but still oldest to newest when they should be newest to oldest.
- Cancel
- Up 0 Down
- More
- Cancel
9517925 over 3 years ago

has it been fixed now ? I still have the issue with SDK 3.2.5
- Cancel
- Up 0 Down
- More
- Cancel
TheMagician over 3 years ago in reply to TheMagician

Bug is still valid for latest beta firmwares of the f6x pro v11.77 and v12.10.

Please fix, thanks.
- Cancel
- Up 0 Down
- More
- Cancel