01-06-2019
01:46
- last edited on
10-19-2021
18:13
by
DavideFitbit
01-06-2019
01:46
- last edited on
10-19-2021
18:13
by
DavideFitbit
Fitbit Versa 32.33.1.30
Fitbit App on Android 2.84 (20213341)
Fitbit app on Windows 10 - latest version. Win 10 completely up to date.
Sony Xperia X Android 8 completely up to date. I know this is an unsupported phone but it has been 6 months since I bought the Versa now...
I had completely given up on connected GPS, but recently upgraded my Versa firmware, so had high hopes.
2 bike rides later and it is just as it was before. I logged 0.4m for a 5 mile ride and today I have just logged 0.49 miles for a 9 mile ride. It showed "connected" within 10s of me starting the ride and I didn't check it until I got back home.
Also, swim tracking does not seem as good now. It never missed a lap on my 40 length swims, but now I am always 1 or 2 lengths short.
Also, connectivity on my Android phone for syncing is now very hit and miss.
Also, every time I start up Win10, I have to manually remove the Versa from the paired devices (in Win10) and then add it again before launching the Fitbit App otherwise it will not connect.
Moderator edit: format
01-06-2019 06:03
01-06-2019 06:03
Yes, my connected GPS works fine once it connects (Samsung S8). I dont bother with it though as I know where I went!
Helen | Western Australia
Want to discuss ways to increase your activity? Visit Get Moving in the Lifestyle Discussion Forum.
01-06-2019 08:02
01-06-2019 08:02
I'm not so much interested in where I went, I am more interested in matching the heart rate, speed and terrain metrics. But when you say you don't bother with it, how do you know it works consistently? 🙂
Unfortunately, the ride always syncs with Strava (which I've told it to do) but according to Fitbit, my 9 mile ride this morning took 28 minutes and I only travelled 0.49m so as you can imagine, my average speed made for interesting reading on Strava...