07-29-2018 15:38
07-29-2018 15:38
Hey Everyone,
Some help would be appreciated. I have the Fitbit Versa and over the last week its been having serious connection issues, it cant keep track of runs during GPS tracking, often losing several KM along the way. The device has a lot of problems tracking notifications - especially phone calls which I might get 20% of the time, but I can overlook at as this is more of a sports tracker. But run tracking should be something this device does 100%.
Fitibt told me my device isn't actually supported - Pixel 2 XL - so pretty much I'm on my own to solve this. Anyone have any ideas?
Answered! Go to the Best Answer.
07-29-2018 19:54
07-29-2018 19:54
Hi, @VincentAM! I've heard some speculation from people on the forums that there are some issues with the GPS tracking on 2.75, the latest version. I haven't updated to it myself, since my thoughts are "if it ain't broke..." Maybe this is what you're seeing, too? I think it may have rolled out on Tuesday last.
MakMak | Community Council
If you find a response useful, please mark it as a solution to help others.
Check out the Lifestyle Forums for ways to get more active!
07-29-2018 19:54
07-29-2018 19:54
Hi, @VincentAM! I've heard some speculation from people on the forums that there are some issues with the GPS tracking on 2.75, the latest version. I haven't updated to it myself, since my thoughts are "if it ain't broke..." Maybe this is what you're seeing, too? I think it may have rolled out on Tuesday last.
MakMak | Community Council
If you find a response useful, please mark it as a solution to help others.
Check out the Lifestyle Forums for ways to get more active!
07-30-2018 04:46
07-30-2018 04:46
Interesting, thanks for the insight. I'll try reloading the previous version of the app to see if that helps and respond here afterwards.
07-30-2018 17:24
07-30-2018 17:24
I removed version 2.75 and reinstalled version 2.74.2 and tried tonight, the GPS functioned as normal with no interruptions.I can only assume since the 2 runs I had that were messed up happened after the 2.75 update, that the software is at fault.
Thanks @MakMak for the info.