Bug: 24/7 heart rate misses readings while recording an activity

Former Member
Former Member
When the HR sensor is enabled during an activity, it captures a detailed HR history that is written to the FIT file. After that, in 24/7 HR stats however, I find that almost all peaks that were recorded during the session are missing. As a result, the min/max stats are also wrong.

So if you workout like hell and push your limits, you'll never see that in the 24/7 and health stats. This kind of defeats the purpose of the device. IMHO this is a bug.

I understand the default 24/7 HR readings have a low sample rate in order to save battery life. But when there's more detailed information available anyway, e.g. during activity recording, that information should not be silently dropped.
  • Post to device relevant forum
  • Former Member
    Former Member over 7 years ago
    I don't think it's device specific. Looks more like a firmware issue.
  • Firmware is device model specific. It has nothing to do with Garmin Connect.
  • Different devices has different versions of the oHrm sensor and that sample rate can differ. Newer devices have the ability to sample every second 24/7. Don't get confused about when it sample vs what data gets sent to GC in 24/7 mode, where that is far fewer readings than you can see on the watch. On a watch with SensorHistory, that saves a sample every couple minutes, but on many (with the latest sensor), in code, you can use Activity.getActivityInfo().currentHeartrate, and see the HR every second. That's how watchfaces can display the HR at basically 1hz with onPartialUpdate.

    Here's an example of a WF showing that (on watches that allows it.) Simple Heart
  • Former Member
    Former Member over 7 years ago
    This behavior is not related to the Connect IQ API, but I will forward your feedback to the device teams.
  • Former Member
    Former Member over 7 years ago
    Thanks, Brian. I wasn't aware the API and firmware developers were in different departments.

    Earlier in the day, I posted this issue also on the Vivoactive HR forum.