01-29-2020
01:40
- last edited on
01-30-2020
20:20
by
RicardoFitbit
01-29-2020
01:40
- last edited on
01-30-2020
20:20
by
RicardoFitbit
Hi, I've been having issues with my distance measurements when going for runs. On my phone GPS fitbit app, this morning it says at the top of the screen that I did 8.44k (which is showed on the recording screen when I stopped the tracker) but the map on the same screen states it 6k, and my actual fitbit on my wrist which is connected to my phone says 4k. Which is correct and why are they
all different? I'm pretty sure the 8.44k is right and I've done that run quite a few times but just starting to doubt my fitbits accuracy ☹️
Have attached screenshots so you can see what I mean. My phone is a Huawei p20 if that makes any difference and I have the latest updates for the fitbit app.
Kind regards Emma
Moderator edit: Subject for clarity
01-30-2020 20:20
01-30-2020 20:20
Hi @EmmaT1980, it's nice to see you again participating here in the Community Forums, welcome back!
Thanks for bringing this to my attention and the details that were shared in your post, the screenshots that were attached in your post were really helpful for me to understand this situation in a better way. To move forward, can you please let me know which Fitbit device are you using? This way, I'll be able to determine if you're using connected GPS or if your device has a built-in GPS chip. Also, can you please let me know when was the first time you experienced this issue and how many times since then? In the meantime I receive your answers, please check the information that's specified on our help article: How accurate is my GPS data? and Why isn't GPS working on my Fitbit device?
Looking forward to your reply.
01-30-2020 23:10
01-30-2020 23:10
Hi there, many thanks for your reply. I have a Charge 2 and it was connected by GPS to my Huawei phone. I have since mapped allot of my runs on mapometer website and most of them are all overestimated by about 1.5 to 2 km which I'm gutted about. My fitbit app has been giving me 3 different readings for months now but have only recently had time to properly investigate it. From googling the issue it appears that there is a big between fitbits and android phone so expect the issue lies here a doing everything else all the help articles say to do ☹️ seems as though the issue has been about for over a year but not seen any soloutions or fixes?
Any help greatly received, seriously thinking of getting a Garmin that has inbuilt and more accurate GPS as can't rely on my fitbit anymore which is such a shame ☹️
01-31-2020 07:52
01-31-2020 07:52
Thought I'd give you another update. Did a run this morning and used fitbit again and also the runkeeper app. Fitbit was out by 2k again but runkeeper was spot on so shows not an issue with my phones GPS. Must be a bug in the fitbit app ☹️