Distance Calculations for Tracked Run Activities With Phone GPS Off Are Using Walking Stride Length

[SunsetRunner]

Normally I have phone GPS turned on for tracked run activities. But this week, I've done a number of runs with it turned off so that I could leave the phone at home. Even though the activity is being tracked as a run, the Fitbit HR is using the walking stride length (85cm) instead of the running stride length (100cm) to estimate distance.

Fitbit was rebooted and hard reset after I noticed this yesterday. That didn't resolve the issue as distance for two runs I did today were also estimated using the walking stride length.

[JohnnyRow]

Are you using the 'Run' option in the Exercise App on tracker itself?  That's definitely worth a try if you were relying on auto-recognition.  If that's not the issue, it's worth checking your stride length again.

[SunsetRunner]

I'm using the run option in the Exercise App on the tracker itself. I disabled auto-recognition months ago after the Fitbit repeatedly started auto-recognized activities while a manually started activity was already active (i.e. if I did a five minute cooldown walk at the end of a manually started run activity, the Fitbit would start an overlapping auto-recognized walking activity).

I checked the stride lengths on both the Android App and on Fitbit.com before posting. Both identify manually entered walking and running stride lengths to be 85cm and 100cm, respectively.

A workaround I found a few minutes ago is to select the Treadmill exercise option instead of the Run option. Distance appears to be estimated based on the running stride length for the Treadmill activity.

[JohnnyRow]

What I meant by checking your stride length again was to actually re-measure, but if you've found a solution that works for you, that's good.

I have never actually done test to verify 'Run' uses running stride length - just assumed it would.  Maybe you have found a bug.