So does 2.68 fix the map and Gps issues from 2.66?

[foofarley]

Does 2.68 fix the jagged map, incorrect distances, and syncing issues present in 2.66?

[BamIAm]

Tried my Surge with 2.66 last weekend.  Got exactly the problems you described, very jaggy tracking, and one really off GPS lock at the start.  Was blaming it on the tracker and not the app.

Will have to try the Surge with my legacy 2.42 to see if it works better.  MobileRun definitely works right with the old version.

[Gandalf2Grey]

2.67 fixed it, at least for me.  I did learn that I have to turn on both "Always connected" and "Keep-Alive widget" to maintain the GPS lock for tracking.  If I do not have the "keep-Alive Widget" enabled, my charge 2 frequently loses the link to phone GPS and my ended biking map looks like ###.  

Upgraded to 2.68 yesterday and experienced the old GPS issue.  Found that the update somehow turned off the "Keep-Alive Widget".  Hope that turning it back on will solve the issue.   

[Jessica_orf]

Hello, I have been having a lot of trouble with the map and stats when I go on my runs. I just went on a 3 mile run, my gps was on and working fine, then when I pressed finish my map and stats did not appear. This is very frustrating to me because it has happened multiple times now. I have already restarted my phone twice, and logged in and out of Fitbit, and the map and my stats have still not appeared. What can I do to fix this problem? 

[Goosse1962]

@Jessica_orf,

This sounds familiar. Some of us have it fixed, and I think one phone type still has the Oreo/GPS issue.

If you provide the tracker type with the phone model, Android version, and Fitbit app version, we (the user community) will have a better chance at providing help. (I use a Blaze, Pixel 2 running 8.1.0, app version 2.68. The issue was fixed for me after several updates to both the Fitbit app and some Android related service apps.)

Alternatively, you can call Fitbit support. They can walk you through some options that may fix it, or tell you if there is still an outstanding issue for your phone model.

Good luck and have a Terrific day!

[Goosse1962]

@Gandalf2Grey, I found the same issue with the keep alive widget getting turned off. lost connection when I crossed the street.

Thanks to all of the issues I experience from when Oreo was pushed to me, I was able to locate the issue and restart my walk in less than 30 seconds. I can see this frustrating many users that haven't worked through the frustration earlier in the Android/Fitbit update cycles.

Have a Terrific day!

[Rich_Laue]

@BamIAm the Surge has its own built in GPS and does not need the phone to be with you to record the path. Your jagged lines are with the Surge, not the app .

@Jessica_orf and @Goosse1962 I'm not sure if your using connected GPS with the tracker or the tracking function built into the app. If using the app and the walk was paused then resumed, the map could be lost. The work around is to not resume after hitting pause .

[BamIAm]

@Rich_Laue, when you sync a Surge to the app, the results are filtered by it.  I've seen enough strangeness with Fitbit's app's interpretation corrected by uploading the .tcx file to Strava.  Fitbit's app definitely puts its own touch on the raw data from the Surge.