03-26-2019
07:18
- last edited on
03-28-2019
07:36
by
MarcoGFitbit
03-26-2019
07:18
- last edited on
03-28-2019
07:36
by
MarcoGFitbit
Over the past couple of weeks I've found that whilst running or cycling my route is not being logged correctly, so when it syncs with Strava the route is inaccurate. The route will be correct for a while and then just show as a straight line between two points on the map.
This is happening in areas that has until recently recorded correctly so I don't think its a lack of GPS coverage. Also I've been with friends who's phones or watches have tracked correctly.
This also seems to be messing up the time on splits as my times are totally different to those I've run alongside, even though the total end distance is the same.
Moderator Edit: Clarified Subject.
03-28-2019 07:39
03-28-2019 07:39
Hello @Colin5250 thanks for joining the Fitbit Community, it's great to have you on board.
I appreciate your participation in the Forums and for sharing your experience with us. Tell me, when the activities get recorded by your Versa, are they getting automatically detected or do you start the activities from the Exercise app? Have you restarted your Versa already by pressing and holding the Back and Select buttons (left and bottom right) until you see the Fitbit logo on the screen? If so, would it be possible for you to reply to us with a screenshot of how the activities are showing in the app after you sync them?
This will be very helpful for us to check this further.
Thanks for your patience and understanding, we'll be waiting to hear from you.
03-28-2019 08:29
03-28-2019 08:29
Hi Marco
I always start the exercise from the app, rather than auto detect. I haven't tried restarting the Versa, but will give that a try later.
Attached are screen shots from Strava. The first shows how a run tracked for me showing the straight lines, the second is from a friend whom I ran alongside showing the actual route. There is also quite a large difference in split times despite the fact we ran side by side (though I'm assuming this is due to gps tracking not being accurate.)
Many thanks.