Connected GPS vs Fitbit app GPS accuracy

[jwebb72]

I, like others, am having accuracy problems with connected GPS exercises. One thing I noticed is the map with the plotted route, using the GPS through the Fitbit app, the plotted line is nice and smooth and looks correct to the path I took. The connected GPS plotted line is very ragged and not straight and smooth. My walk was straight down the road for .25 mile and back. I'm consistently seeing the connected GPS reading .1 miles over every mile.
I did the 2 tests back to back, I even did it as a bike ride and same results, ragged route and over on distance. My phone is the Motorola Moto E running 5.0 lollipop and my Blaze has the most current firmware. Does anyone know if this issue is being worked on?

[SunsetRunner]

I have the same problem, using my Nexux 6P running Android 6.0.1 with my Blaze.  My Blaze using Connected GPS is off all the time.  Sometimes off by as much as 1/2 a kilometer, most time about 100 - 200 meter (about 110 - 230 feet) for a 4.38 km walk.  And my FitBit Mobile Track works perfect, just the Blaze.  I contacted Fitbit and after they tried some things, they send me are placement Blaze and the new Blaze does the same thing.  The problem has to be in the FitBit app or Blaze Firmware.  I am very unhappy with the Blaze and FitBit customer service, they deny there is a problem.

[MikeS1971]

I've noticed the same thing recently and have narrowed it down to the Blaze loosing is connected GPS connection with the phone.

[picasso66]

With the recent Fitbit App update, I notice there's now a stride length option that says the stride length is automatically adjustered every time I go on a run [walk].  I thought the stride length is to calculate the steps. What I've noticed is the distance is way off since this update.  I walked 3.1 miles with connected GPS turned on and it measued 2.49 miles.  MapMyWalk and Google Maps are 3.1. Excuse my ignorance here but shouldn't they all be the same if it's using GPS???  The mapped route on Fitbit shows the same picture of the map as Google Maps and MapMyWalk.  Confused in Florida...

[Rich_Laue]

The auto stride length takes the miles measured, and divides it by the steps, to caome up with your side.

Outside of restarting the Blaze, Phone, making sure the phone is set for GPS only, deleting then re-installing the app. I'm not sure of what else to do, there have been several posts on things people did that fixed this.

[jwebb72]

I agree @MikeS1971 I've ruled out the phone lossing GPS, must be a communication problem between the phone and the Blaze. Sometimes I do get the right distance once in a while and it shows on the map, nice smooth plotted route line, not a jagged line like when it's inaccurate.

[ehansen1212]

I too am being cheated on distance and steps with the Blaze when comparing their connected GPS to MapMyWalk and even my car. This morning I tracked what Fitbit connected GPS said was a mile on their map and got approximately 1.5 miles on my car. Very significant discrepancy which is unacceptable. Had the Blaze for 1 week now and love its look and features, but doesn'the seem to do the basics. Upsetting for sure.

[annenoe]

Glad to see it's not just me. I use MapMyWalk and have just started using the Blaze. I bought it primarily to monitor heart rate but am a bit disappointed in the mileage estimate. It's consistently short, by .25 to .5 miles over a 5+ mile walk. When I look at the map from MapMyWalk, I can see it is *extremely* accurate in terms of the route, e.g, shows me crossing back and forth on the street, walking into/around a neighborhood park. I like the Blaze for heart rate and being able to manage my music, but will continue to carry my iphone to make sure I'm getting in my 5 miles a day.

[RodrigoFitbit]

@jwebb72 @SunsetRunner @MikeS1971 @picasso66 @Rich_Laue @ehansen1212 @annenoe Guys I found something that might be of help for this particular case about distance tracker with GPS on this post.