12-13-2020
12:53
- last edited on
12-13-2020
18:23
by
RicardoFitbit
12-13-2020
12:53
- last edited on
12-13-2020
18:23
by
RicardoFitbit
I have had lots of issues with my Fitbit not tracking maps properly. I have done a full factory reset as previously advised. It tracks fine if I track using the Fitbit phone app, but will not track if I use the Fitbit itself.
Moderator Edit: Clarified subject
12-13-2020 18:22
12-13-2020 18:22
Hi @Tigore, welcome to the Community Forums.
Thanks for bringing this to our attention and for trying some troubleshooting steps before posting over here. To better assist you with this situation and for a better understand of your issue, can you please elaborate more? Are you using MobileTrack on your phone and also your Versa 2? When was the first time you experienced this situation and how many times since then? Is this affecting a specific exercise or all of them? Lastly but not less important, which phone are you using with your Fitbit?
Looking forward to your reply.
12-13-2020 22:35
12-13-2020 22:35
Hello
This only started happening in October, it worked fine up until then. It happens every time I try to use the Fitbit to track. I have Motorola G7 power, the same phone I’ve had throughout. I only really use the Fitbit to track walking. I prefer to track using the the Fitbit itself, with the phone app open just to provide gps. I ensure it says it is connected on the Fitbit itself before starting the walk, however, it keeps losing the gps connection. I know it is tracking the number of steps, rough distance, calories burned etc okay for the entire walk, but will not show a correct map of the route. If I only use the phone Fitbit app to track a route, and not the Fitbit itself, it will track fine so I know I do have constant gps signal on the phone. I have been trying to sort the issue by walking the same three mile route to tell if it is working properly. All location permissions are set correctly.