Distance discrepancies

[Nadirian]

Hello!

I've had this problem lately with my ionic, i can't say when it started or if it has been there all the time, but when i go for a run in my 2.5km track, the ionic starts to drift.

In:

2.5km actual result is 2.44km

5km actual result is 4.51km

10km actual result is 9.3km .

When i compared the 10km run with Runkeeper, Runkeeper stuck at 10.18km on a 10km run, which is a bit better.

This is unbearable for me now, I've tried all solutions i could find here, should i return it?

Moderator edit: Subject for clarity 

[RicardoFitbit]

Hello @Nadirian, welcome to the Community Forums!

I appreciate all the information and details that were shared in your post, totally understand how frustrating this matter can be for you. To better assist you with this, can you please let me know when was the first time you experiencing this and how many times since then? 

Let me share with you that Fitbit devices calculate distance by multiplying your walking steps by your walking stride length and multiplying your running steps by your running stride length. We estimate your stride lengths using your height and sex. If your Fitbit device uses GPS and you track 1 or more runs using on-board or connected GPS, we evaluate that data to automatically update your running stride length. For best results, run at a comfortable pace for at least 10 minutes.

If you prefer to measure your walking and running stride lengths yourself and enter them manually, see How do I measure and adjust my stride length?

Note that when you're tracking an activity with GPS, Fitbit calculates your distance using GPS data rather than steps. If you begin moving before you get a GPS signal, the tracker will calculate distance using steps and stride length as described above until a GPS signal is found.

Let me know if you have any additional questions.

[Nadirian]

@RicardoFitbit 

I have experienced this since the day i bought it.

I went from an Alta HR to the Ionic in late April for my birthday.

My colleague had an Alta HR, and when we ran together with our Altas, there were very very small to no difference in distance.

When we ran together with my Ionic and her Alta HR, my Ionic were always drifting later... When her fitbit ticked 1km, my was at 0.98, and when hers were at 2km, mine was at 1.94 or something. Always behind.

I always use the GPS, and i never ever start my run or walk before my Ionic has aquired signal from the GPS service. When it says "connected" and vibrates, i press the "start" button and start my excercise.

Ill share with you, two images of my 10km run.

https://imgur.com/a/6n8hfJw

(I ran this track 4 times, as said. Its a 2.5km run)

The first image shows a stride that is completely off... according to fitbit this is a stride in about 100-150meter.

The second image, shows two other strides that are also a bit far off the map... I am sure this affects the data in the end.

I will look into the stride-length guide. But i wish there were less complicated than this.

My stridelength is not consistent, when i run fast i take longer steps, when i getting more tired, the steps are closer and slower...

[JPinFL]

I've noticed this issue since I recently received a replacement Ionic. That said..I was not comparing the Ionic to anything prior, so I may have just been blissfully unaware.

When my Ionic (purchased in November) recently died, I installed the Pacer app & Nike Run Club app. After I received my replacement Ionic, I continue to use the Nike Run Club as I liked the voice cues and had connected with some friends on the app. Every day the Nike Run Club app has show a longer distance for the same time. I do wait for the Ionic to show it's connected to GPS before I start my run activity and the Nike app at the same time.

Today on my morning run...the Ionic only showed 3.11 miles and the Nike Run Club showed 3.23 miles. I thought the Ionic had it's own GPS..and had felt it was accurate - now however I'm seeing it's not as the other two apps are using the GPS on my phone. 

This is distressing..as the Ionic is not a cheap tracker and obviously is not working for the purpose intended. I found message threads dated over 18 months ago, so it appears this has been a reported issue for some time.