08-13-2020 09:32
08-13-2020 09:32
I’ve had my Versa 2 for a couple of months, I do the same 5km run most days which is 2.5km each way. However, this week when connecting to my phones GPS, as soon as I lock my phone it says ‘connecting.’ It was usually always connected even with my phone locked. Also, the GPS isn’t accurate anymore. Today, when I got to my usual 2.5km, it showed I had only done 2km. So I ran further, but by the time I got home it was 5.24km meaning I’d done more distance coming back. I’ve compared with other apps and think Fitbit is somehow now under reading my distance. Any ideas why or how to fix?
10-13-2020 12:51
10-13-2020 12:51
This affects me also... Same walk records different distances each time but never the correct distance! Also the longer I walk for, the bigger the gap gets to the correct distance! So frustrating!!
10-14-2020 03:52
10-14-2020 03:52
I have the same problem. It just started about 2 weeks ago (Oct ‘20). Before that, my Fitbit was spot-on since I purchased it in April ‘20. Same 3.5 mile walk I’ve been doing at a 18 mph pace for months is now giving me a 21 mph pace and only tracking 2.8-3.2 miles! I am beyond frustrated. Fitbit staff/moderator: can we get some help?
10-14-2020 11:48
10-14-2020 11:48
@VL33 @Lauren1990 @Jamie39142 -
This has been an on-and-off issue all year, depending on the mobile app release number. In the past, the GPS connection would drop within 10 seconds of either locking the screen or sometimes even just placing the app in the background. Bringing the app back up to the foreground normally would case the connection to reestablish itself within 5 seconds.
I am currently on iOS version 3.30 and am not experiencing the issue, but have noticed that version 3.32 is available in the App Store.
The issue may very well have come back a-g-a-i-n with a newer release.
Which version are you three running and what platform - iOS or Android?