Bad maps since Saturday

[JenRuns]

This past Saturday (9/23), I went for a walk, then looked at the map afterward, and it was awful. It looked like the GPS only recorded my location a handful of times and drew straight lines between those few pings. It did it again this morning when I went for a run. Unlike with Runkeeper, I can't manually fix the map (please let me know if I'm wrong), so the distance is all wrong, and now it's probably making bad assumptions about my stride length. I also can't figure out how to tell my device to ping GPS more often. Did something update recently that changed GPS settings? I'm on an Android device, if that helps. Thanks!

[LZeeW]

@JenRuns  I moved your post to the Android forum.  I think this is more of an android issue and not a tracker issue.  I also noticed that the android app was updated on 9/25.  Do you have the current version of the app?

Also, maps cannot be edited, as in Runkeeper.

[shipo]

---

@JenRuns wrote:

This past Saturday (9/23), I went for a walk, then looked at the map afterward, and it was awful. It looked like the GPS only recorded my location a handful of times and drew straight lines between those few pings. It did it again this morning when I went for a run. Unlike with Runkeeper, I can't manually fix the map (please let me know if I'm wrong), so the distance is all wrong, and now it's probably making bad assumptions about my stride length. I also can't figure out how to tell my device to ping GPS more often. Did something update recently that changed GPS settings? I'm on an Android device, if that helps. Thanks!

---

What kind of Fitbit device do you have?  I'm assuming you don't have a Surge and you're using one of the other trackers which uses Connected GPS; yes, no?  If "Yes", which version of the Android Fitbit app do you have?

[JenRuns]

Sorry I didn't reply sooner -- the website was throwing SSL errors every time I tried. I have a Charge 2, and my phone updated the app this morning. I'll give it another shot either tomorrow or Saturday and see if that fixed anything.

[JenRuns]

I still haven't been able to test this. I went for a run on Sunday, and when my Charge 2 said it couldn't see my phone, I didn't feel like spending 5 minutes arguing with it and just ran without a map. It seems to be getting harder and harder for my Charge to find my phone. I was hoping the firmware update it installed on Sunday would help, but it did not. 

[JenRuns]

My phone app is up to date on my Pixel, my Charge 2 went through a firmware update, and the maps are still terrible. See this lovely route it thinks I just took. The wavy gray line is the actual river path. The red line is the route it thinks I took. It's like it's only pinging the GPS every few minutes and drawing straight lines between the pings.

[CherylChilders]

At least you get a map, albeit a wrong map.  I walk a 4 mile route every morning and cannot get a map of my walk.  It usually tells me I did aerobic or elliptical and only for about 20 minutes.  Love my fitbit but the app is driving me out of my mind.

[JenRuns]

The maps were excellent until recently. I switched over from Runkeeper to Fitbit for the improved mapping. I've been searching my phone settings to see if there's a way to have to ping the GPS more often, but if it's an option, I can't find it.