BUG - Average Speed

Activity.info's "averageSpeed" registers about 1 million MPH, if you START the activity, and then, a few seconds later, begin simulating data.

No biggie.... just an entertaining bug.
  • Hey DaveBrillhart,

    I've got a ticket made to address this. It was really easy to reproduce. Thanks for the heads up.

    -Coleman
  • Sure. I have two more bugs.....

    1. Upon an activity DISCARD and restart a new activity without rebooting the device... all counter based metrics shiould be zeroed out. Obviously. Avg Speed, Total Ascent, Avg Power, Moving and Elapsed Time, Distance, etc. Except CALORIES is not reset to zero.

    2. Elapsed Time is still broken. Easy to demonstrate. Setup a CIQ variable that is a calculated Elapsed Time, which is simply NOW - STARTTIME. That is accurate. But the built in ElapsedTime is wrong under the following use case.... Start an activity... after some time. STOP it. Then hold the power button for a few seconds and you get the option to either Power it off or Put it to Sleep. At least on the newer Edge devices like the 820. Select SLEEP. In a bit, hit the power button to wake it back up. And RESUME the activity. The built in Elapsed Time will be wrong - short by maybe a minute or so. Interestingly, if you do the same use case again, but instead select Power Off instead of Sleep... then then wake it back up and resume... the built in Elapsed Time is often back on track or at least within a few seconds of the correct elapsed time (NOW - START TIME).

  • DaveBrillhart,

    1) Which device is this on specifically? I can run it by the device team, but I think they probably have a reason for that.

    2) I've created a ticket on the Edge 820 - they can port that fix over to other devices as we discover the extent of the issue.

    Tag: STARK-2507

  • 1) Which device is this on specifically? I can run it by the device team, but I think they probably have a reason for that.

    2) I've created a ticket on the Edge 820 - they can port that fix over to other devices as we discover the extent of the issue.

    Tag: STARK-2507


    Thanks for creating the ticket for the Elapsed Time bug. I confirmed that bug exists on the device.

    For the lack of a calorie reset - I can't imagine why that would be desired, as the activity is discarded and starting a NEW activity should not carry over the old calorie counter. But anyway, was detected in the simulator. I'm not sure that is also a problem on the actual device. You should be able to recreate the issue likely with any device in the simulator.