04-04-2018
11:07
- last edited on
04-05-2018
09:32
by
RobertoME
04-04-2018
11:07
- last edited on
04-05-2018
09:32
by
RobertoME
I used the app yesterday to track my hike for the first time which is a hike I've done before as a total of 5.6 Miles. For some reason on the Fitbit app the hike was tracked as 3.41 Miles. I've tracked this hike plenty of times using my phone app and never had an issue. Not sure if I somehow didn't set it correctly. Idk if anyone else has had this problem before. It's just a little frustrating that it didn't track the actual progress.
Moderator Edit: Format
04-09-2018 08:51
04-09-2018 08:51
Hello @kalba, nice to have you as a new member of the Fitbit Community! I was reading your hike distance was not recorded correctly. My apologies for the late response and I'm wondering how it goes so far? Is the issue still happening or it was only in that occasion?
If you're still having difficulty, try these troubleshooting steps:
Make sure the Fitbit app is allowed to run in the background on your phone and the Fitbit app is open on your phone or running in the background. Do not force quit the Fitbit app.
If the issue persist:
See you around and stay tuned if you need additional help.
"Great things are done by a series of small things brought together.” What's Cooking?
09-28-2019 02:41
09-28-2019 02:41
For a very long time Fitbit distance has never been correct for me during a run or hike. It has been cutting the actual distance in half. I track on map my run as well and mapmyrun says 5.5 miles, and fit bit says 2.8 miles. It also will stop the work out on it's own at exactly .5 miles (but only sometimes) . Side note, on runs it starts out pretty accurate for about the first .25 - .5 miles then starts to drop off dramatically.
The fixes you posted make no difference and never had.
I have a versa 2 with a galaxy s9
Brian