02-26-2019 13:14
02-26-2019 13:14
Whatever happened in the 2.88 update seems like the right direction, as my OnePlus 6T (Pie/9) phone and my Versa with connected GPS seems better. Usually during walks or bike rides, I'll see "connecting..." occur shortly into the exercise, and then I'd receive no new notifications from phone to versa for a while. After stopping the exercise, I'd then have problems connecting to my phone for 10-30 minutes. Whatever was changed in 2.88 seems like it was a step in the right direction, as I'm not noticing this occurring anymore. Kudos to the software engineers, I think?
02-26-2019 14:10
02-26-2019 14:10
Do you see the map of your walk now?
02-26-2019 14:18
02-26-2019 14:18
My post was specific to my versa initiating the connected gps walk, and I never had a problem with one not showing up as a map before. My GPS aways recorded the walk as a map, albeit sometimes a bit wonky and sometimes slow to update in the app. When initiating it as a walk from the app itself previously, I've had them being logged as runs instead, but I'm unsure if this aspect is fixed or not.
02-26-2019 14:24
02-26-2019 14:24
I took my first hike today with 2.88 and the map is gone, as is the elevation chart in the Dashboard.
02-26-2019 14:46 - edited 02-26-2019 14:49
02-26-2019 14:46 - edited 02-26-2019 14:49
Hmm. Either there was a temporary GPS problem on your phone, or a new app problem was introduced for your phone hardware or OS version. I'd reboot the phone and experiment some with a few more test excercises before assuming is is an app bug. If it doesn't go away, then update the post and open a case with Fitbit.
Also, make sure you are initiating the hike from the Versa and not hoping it is detected as a hike.
02-26-2019 14:52
02-26-2019 14:52
I manually started and ended the hike from my tracker and I received a notification on my phone that my tracker was connected to my GPS.