GPS errors on Fitbit Blaze

[MikeG6.5]

So I have been using the Blaze to track my trike riding.  And I've noticed some real issues with the reported GPS track that the blaze then posts on the dashboard.  I use RideWithGPS to also track my riding, but sadly I don't get the heartbeat information when I do this.  But I DO get accurate GPS tracking.

The Fitbit ride has the track jumping all over the place.  If I had actually ridden the track I would have had almost 100 miles in one ride, and had to have flown across bodies of water or ridden through standing forest.  As the ride was on an established MUPs, this was obviously not the case...

Fitbit needs to take a hard look at the usability of the ride portion of the dashboard.  Or needs to get support for RideWithGPS integrated, so heartbeat information can be directly imported to the track it has for a ride.

[Rich_Laue]

Have you tried without any other GPS app running? Has it been ruled out that there is no interferance between the apps.

I find that i need to remove unessasary apps to free up memory.

Does the Blaze show a good GPS signal throughout the ride?

Sorry no answers but only things to look into to help diagnose.

[MikeG6.5]

No, I won't try running on the Blaze as the only tracker on my rides.  I will always run RideWithGPS, although I may be able to run it on my tablet instead of the phone.

When running the Bike app on the watch, it times out and screen goes dark.  Short of constantly turning it on and off again to make sure it's still tracking well, I have no idea if it is losing the GPS signal from the phone or not.  The battery in this device isn't large enough to keep it running all day long while riding...  (I ride 20-50 miles each ride, from 4 to 7 hours duration.)

The errors in the track are typical of the early GPS devices that couldn't clean up a massive jump in coordinates.  Obviously if I'm riding or walking along at a certain pace, there's no physical way the next location plotted is going to be 3 or 5 miles further down the track, then jump to a location 100 feet from the starting point...  Yet this is exactly what is happening many times during a ride.

One of my rides had me going over 100 miles of bouncing around all over the county, when I actually rode just 29 miles.  Yet the Blaze reported that I had ridden only 23 miles.  (I exported the ride out, imported it into RideWithGPS and followed the track and the reported miles there. With both rides side by side, what a difference the two devices reported...)