06-29-2020 05:21
06-29-2020 05:21
Hi,
Recently got my Versa 2. Went for 2 runs, 2 laps around my neighbourhood which strava says is about 2.4km (1.22km/lap) Some might argue that it's Strava that has inaccurate data but I verified with multiple sources (bicycle tachometer, bicycle GPS, multiple phone GPS, google earth ruler)
First run, recorded 2.03km for 2 laps. That's already a pretty sizable error (~20%)
Second run, recorded 4.60km for 3 laps. Bigger error now and in the totally opposite direction, instead of underestimating by ~20% now its overestimating by ~25%
I understand that Versa 2 uses the phone's onboard GPS. But other apps work with my phone's GPS just fine, why the discrepancy? It's so disappointing to get a new device to work this poorly. Please advice.
Versa 2 Firmware 35.70.8.0
Fitbit App Version 3.23 (Location permission allowed all the time, Google Location Accuracy On)
Google Pixel 4XL Android Version 10 Build Number QQ3A.200605.001
Also no response on Fitbit in related post here:
https://community.fitbit.com/t5/Versa-Smartwatches/Versa-s-distance-tracking-way-off/td-p/4095035