01-09-2020
00:58
- last edited on
01-20-2020
11:47
by
RicardoFitbit
01-09-2020
00:58
- last edited on
01-20-2020
11:47
by
RicardoFitbit
A couple of days ago I let my Fitbit Blaze die completely, so resorted to using Mobile Track during the day. Steps and distance were measured as expected, as I was walking routes I know the distance of. Since then, when tracking routes on the Fitbit Blaze, the distance is way off - to the tune of a 2.8 mile walk reduced to 2.1 miles, and a 3.5 mile run reduced to 2.5 miles.
GPS in both instances came from Pixel 3XL - so it was using the same GPS service, only one on the mobile track, one on the Blaze
To check I was not going insane I used MapMyRun and Strava to create route maps of the affected routes, and sure enough, the Fitbit app was shown to be off. I have used the Average Stride length now for several years, so I'm fairly certain that should be reasonably accurate.
I have checked for firmware updates and there are none available.
Any suggestions on how to remedy this?
Moderator edit: Subject for clarity
01-20-2020 11:45
01-20-2020 11:45
Hi @ViscountGrey, welcome to the Community Forums! Sorry for the delayed reply.
Thanks for bringing this to my attention and the details that were shared in your post. To better assist you with this, can you please let me know if this is affecting a specific activity or all of them? When was the first time you experienced this GPS issue and how many times since then? If you haven't already done so, I recommend you to restart your Blaze following the steps that are specified on this help article and then check: Why isn't GPS working on my Fitbit device? for more troubleshooting steps.
Keep me posted and let me know if you have any additional questions.