04-20-2018 17:15
04-20-2018 17:15
I've been using the Strava app on my Galaxy S6 to log my MTB rides for several years. My local loop has always registered as 10.5 to 10.7 miles, over dozens of rides. Yesterday I ran Strava on my phone and the Versa bike app simultaneously during this same ride. Strava reported 10.7 miles. Fitbit reported 8.7miles. Both apps synched rides to my Strava feed. The maps are identical and smooth, but Fitbit's mileage is off.
Today I rode a slightly longer route than yesterday, with just the Versa running. Fitbit only reports 9.3miles when Strava has always reported this route at >11 miles.
Anyone else having similar issues?
04-20-2018 20:20
04-20-2018 20:20
Yes, but with running. See me thread here:
https://community.fitbit.com/t5/Versa/Connected-GPS-Run-Inaccurate-Distance-Screenshots/m-p/2658906
I have since switched back to my blaze full time which doesn't have this issue.
04-21-2018 12:00 - edited 04-21-2018 12:02
04-21-2018 12:00 - edited 04-21-2018 12:02
I agree. I had a ride tracked on my Apple Watch, Google Fit via my Google Pixel in my Pocket and my Versa. The difference between the Apple Watch and Versa was 5.12 miles.
Screenshots Below (Apple Watch 16.35 miles, Google Fit 15.49 miles, Versa 11.23 miles)
Apple Watch
Google Fit
Versa