09-02-2019
15:50
- last edited on
09-08-2020
13:04
by
MatthewFitbit
09-02-2019
15:50
- last edited on
09-08-2020
13:04
by
MatthewFitbit
I cycled the weekend, 31 mile round trip. Before setting off I manually started my Charge 2 to record the activity. The app shows the activity, with correct duration. It also displays a map of the complete route taken, with no missing sections apparent. But it records the distance as 8.9 miles which is clearly wrong. Even the distance between the furthest points on the map is greater than this! And average speed is calculated as 4.4mph. Again totally wrong (I'm not THAT slow!). Any ideas what is going wrong? How does Fitbit calculate distance for cycling with Connected GPS?
09-02-2019 16:18
09-02-2019 16:18
Replying to my own thread, but having searched on previous posts relating to Connected GPS and wildly inaccurate distances. I realised that Fitbit promised they were aware and investigating 2 years ago. With this, and the lack of commitment to support the latest Samsung devices, I have realised that Fitbit are very unlikely to fix any of the issues I have encountered. EVER. First Fitbit = last Fitbit.