Blaze not tracking distance correctly

[theotherdaveg]

Since the last firmware update I have noticed that the distance accuracy on the Blaze is off.  I am pairing to a Galaxy S5, and also using the Strava App.  For a while I had the Strava/FitBit sync enabled, but i disabled it this week.  Each day I do the same run in my neighborhood.  It is a loop of ~1.1 miles.  I usually do 5 laps, so ~5.5 miles.  So far this week, FitBit has me completing distances (miles) of 5.43, 5.68. 5.16 and 3.86 (today was only 4 laps).  Strava has me completing distances (miles) of 5.4, 5.7, 5.8, and 4.8.  So the first two were close, but the last to were off by ~.7 and 1.0 miles.  Both are using the phones GPS, so what is happening to the FitBit?

[FerdinandFitbit]

Hi there @theotherdaveg. Good to see you in the Fitbit Community! 🙂

That's very strange. Something that may affect the GPS distance is the signal reception on your phone. If you're running somewhere full of trees or where you can find tall buildings, this could cause the distance not to be accurate.

I can also suggest restarting your tracker by pressing and holding the left and lower right buttons for 10-12 seconds and this should restart your tracker and after that, you can try it out and see if this makes any difference.

Let me know how it goes!

[theotherdaveg]

@FerdinandFitbit, thank you for the reply.  Two very good points.  The area is treed, but I would expect the Strava app to be affected as well, since it is relying on the phone GPS signal.  I have restarted the Blaze, but have been unable to test since then do to travel.  I am also planning on brining it to a track and confirm.

Regards,

Dave

[FerdinandFitbit]

No worries @theotherdaveg. As soon as you can test it, you can see if that made a difference.

Keep me updated! 🙂