averageCadence and maxCadence on the va (for running)

I've added the display of currentCadence, averageCadence, and maxCadence to a running app on the vivoactive.

While currentCadence seems correct, averageCadence and maxCadence seems to be 1/2 of what they should be (I'm not using a footpod)

In the doc for cadence in activityInfo talks about revolutions, so could it be that currentCadence when running is steps, but for max and avg, it's still "revolutions" (2 steps?)

Former Member over 10 years ago

I believe this was reported once before and we have a bug report logged.

The cadence metric is stored internally as strides/cycles, but the device shows steps (strides x 2) for running and walking activities. This logic has been included in the cadence metric for ConnectIQ, but was left out of the average and max.

jim_m_58 over 10 years ago

Thanks for the info - for now, I'll just double the numbers for avg and max!