Blaze underestimates distance during run

[ro_s]

Hello,

My Blaze underestimates distance covered during runs. Earlier, a run measured at 6.7 km on Google Maps and Runtastic only measured at 6km. 

I didn't have this problem on my old phone (the distance was exactly right) : this has only started happening since I got a new phone in March. However, the new phone GPS works fine on apps such as Google Maps.

Also, the map of my run on the Fitbit app is exactly correct (shows the correct path, etc...) but the problem is with the distance. The problem isn't with steps counted because the distance is measured fine when running without GPS (by entering my own stride length)

Thank you!

[AlejandraFitbit]

A warm welcome to the Community @ro_s. Keep in mind that when you're tracking an activity with GPS, Fitbit calculates your distance using GPS data rather than steps. If you are having problems with the GPS, I recommend following the instructions provided in the My Blaze GPS is not working post.

Let me know how it goes.