GPS route inaccuracy

[danikat]

I am having trouble with the GPS accuracy as the map/route is completely all over the place. The top image below is the route as mapped by my Blaze. The bottom image is the same route mapped previously by Runkeeper.

I've ran the route twice with my Blaze and both times the route has me jumping all over the place. I have walked another route 3 times this week. The GPS worked once (on the second attempt) but has not worked any other time. I haven't done anything different between those attempts.

Has anyone else experience this problem and know a way to fix it?

[Salpal23]

Is this an issue with just the Blaze? If you can, try walking that same route using just your phone and another mapping app that utlizes GPS and see if you get similar results.

I only ask because the Blaze doesnt have built in GPS and, instead, it connects to your phone and uses that GPS. Your map looks very similar to what Ive seen before on my own walks years ago when I would lose GPS signal on my phone and it would throw me all around the map.

[cactusjack]

I have only tracked one route so far with the Blaze and it was pretty much spot on with previous runs using map my run. Will be interested to see if i can duplicate your problem and will look forward to hearing how you fare on future runs.

[danikat]

It is just an issue with the Blaze. The image attached to the original post was a run tracked with the blaze vs a run tracked using Runkeeper using my phone gps 🙂

[Salpal23]

---

@danikat wrote:
It is just an issue with the Blaze. The image attached to the original post was a run tracked with the blaze vs a run tracked using Runkeeper using my phone gps 🙂

---

Lol. I see it now. Sorry.

I wish I could be of more help but Im stumped.

[danikat]

That's okay! Thanks for trying! 🙂

[cactusjack]

Seems odd that there is such a difference since the Blaze also uses the phones GPS for tracking

[Visualtps]

I had the same problem that you are having.  The cause is that you are losing the GPS signal or you are starting the run before you have a good signal.  I use the Galaxy S3.  What I did to solve the problem was the following:

1.  I went to settings on my phone and went to location and then Mode.  The S-3 has three GPS modes, high accuracy (uses GPS, Wi-Fi and mobile networks), Power Saving (uses Wi-Fi and moble networks) and GPS only.  I changed my setting to GPS mode only.

2.  I downloaded the GPS Test app.

3.  When I went on my walk the last two days I first called up the GPS test app and waited until I had a good GPS signal and then started the exercise.  The map of my walk was then perfect. 

Hope this helps

[premiump]

Hi, are you initiating the run from the Blaze, through the exercise feature, or using MobileRun from the app?

I have found MobileRun to be absolutely terrible for GPS, but using the GPS Connect feature in the Exercise section of my Blaze was perfect.

I have a Nexus 6.

[AuntBB]

Visualtps,
I've been experiencing mapping + pace inaccuracy problems. Avg Pace is up to 34s slow with Connected GPS. That's nuts. My S3 had issues getting a GPS fix a year ago, so I would run the GPS Status app to provide a solution for that with Runkeeper. It didn't seem to offer improvement with Blaze and Connected GPS. I'm going to try your suggestions tomorrow. Thanks.
I've also noticed Connected GPS doesn't correct itself when there's GPS interference, lost signal, etc. It can't seem to extrapolate. All the other GPS tracking apps have this ability. Puzzling that fitbit would forget about this.