GPS accuracy during exercise

[wrebble]

Picture says more than thousand words so... picture first.

How can it be that the same lap is measured THAT wrong. It is 1,27 km difference which is BAD. Both lines run on the same road so it can not be just "difference". Step count is the same and also the time. Which one can I trust at all? It isn't the first time it has happened (at least once more). 

FitBit app is up to date. My Versa 2 is up to date.

I started my run the same way: opened exercise - choose "run" - wait FitBit to connect with "connected GPS" - start!

Also the settings are the same when I start the run. I activate "do not disturb" and "always on display".

Am I doing something wrong? Is the app so bad that it does not know how to calculate distance? Is it problem with my watch? I looked into it and it seems this problem has been with you for 3.5 years. Is there seriously no fix?

Anyways, I posted this in "App" section because it seems to be problem with an app. If not let me know.

Moderator edit: Subject for clarity 

[Bart_NL]

I have now tried a couple of runs with a rebooted phone (not versa, just the phone) and it seems that the distance is measured correctly.

I restart my phone, let it start all apps and services and then go out for a run. 

So could you guys try this as well? 

[jackski]

I have tried restarting my phone! A few times! Thanks for the suggestion.

Moderator Edit: Personal info removed

[SammyP123]

I am returning my watch and have bought a Garmin instead. I advise people do the same if they can.

Really poor from Fitbit. 

[jackski]

I am really hoping they can get this figured out.  Has ANYONE had this accuracy issue and HAD IT RESOLVED?  It has to be something not quite right in the watch...and yet there are some that work correctly.  My friend's is spot on for distance.  

[MaryG-P]

The post by Recovery Runner actually worked for me! I did all the things suggested and now it’s working! In the end I:
- force shut the app and reopened it
- turned Bluetooth off and back on
- turned my iPhone off and back on

Worked yesterday for the first time in ages.

Sent from my iPhone

[MaryG-P]

I did that too on your advice and now working! Thanks!!

Sent from my iPhone

[Hadeur]

Using the Fitbit App directly to track a run instead of connected GPS was never a problem in my case. No need to reboot the phone.

It just happens when you use the Versa and I guess this is because the step length is used to calculate the displayed distance instead of the GPS track.

[Brettski55]

Spoiler

Spoiler

Followed those steps a couple times and didn't do anything. 

[wrebble]

So a few notes that I have noticed in the course of four months. I do not know why I did not mention them before.

• Distance seems to be more incorrect in "running / walking" situation. When I've ran all the way with almost the same pace the distance is more accurate, but still off.
• When running at very slow speed (very small steps, ca 10cm long), watch is registering it as your normal running pace. That means it will still use stride length even though GPS signal is there. You can only fool the watch with it around a minute or two.

@Bart_NL But the distance measurements are done in the watch not in the phone? Phone is only responsible for boosting GPS data (GPS is accurate). Still, I will try it tomorrow.

Also try to upload your TCX file to another app (Strava or something) and check if the distance is actually correct. The "seems to be correct" is very iffy.

@Hadeur Same here. Also I wouldn't mind using the Fitbit app for tracking. The sad part about using the app is that you can't see your speed / distance / etc on your watch and also it won't save the HR data to the exercise.

[Brettski55]

Contacted Fitbit on twitter as that's the only other option I have for customer service for some reason. After three days of waiting they simply said that my stride length must be off as that's how distance is calculated. That has nothing to do with the gps. The customer service is horrible. Why is it so hard to have someone contact me so I can get rid of this faulty watch?

[Jbp1954]

I have the same issue when biking. 

If I wait for the watch to connect, which takes way too long, usually the map, when viewed later in the app, is correct.

But, distance varies wildly.

I'm about to return this thing. Have had numerous conversations with Fitbit but not resolved.

Samsung Galaxy S10+. Android.

FIX THIS PROBLEM ALREADY!!!!!!!

[SunsetRunner]

I had a similar experience with customer service through Twitter! They said it was probably poor GPS signal!!!!! I had already explained what was happening and even included a link to this thread. Useless!

(This is in reply to Bretski55 btw)

[busterandwoody]

Well I have tried all the suggested fixes for my runs and Versa still wildly under on distance with connected GPS. Google maps tracks my run too and is fine so nothing to do with my phone. So frustrating. Been with Fitbit for years but their obvious lack of testing updates is starting to really annoy me! 

[SammyP123]

As I have mentioned, I have returned (being collected by DPD on Tuesday) mine and purchased a Garmin (arriving today) but got an email from Fitbit today which is more frustration.

From the email, it would seem they are admitting that the most accurate way is to use the exercise tile on the mobile app. In that case, it seems redundant to buy a watch on the first place. 

I must add that I tried this last Thursday and the results were still wildly different from other applications. 

They've given a very vague answer by saying that this is due to different algorithms but are failing to see that these are all from the same GPS signal. 

I really can't understand why they aren't seeing our issue. 

It isn't my problem now as I have left fitbit but I would be very interested to see if the issue is resolved for others and will continue to help where possible. 

 

 

 

 

[patsfan123]

 

 

So the battery dies in a day and it can't even calc distance correctly when using GPS sync

 

[Jbp1954]

I can tell you flat out that this will not work.

I bike.

When I'm about to start a ride, I go to Exercise on my Versa 2 watch (one of the two methods they suggested in your post), tap on "Bike", then wait, sometimes for a LONG time, for it to "Connect".

Today, I didn't wait and it took over 5 minutes to connect, making my map and distance completely useless.

But, when I DO wait, then make sure it's actually started, and then start my ride, my distances are all over the place for the same, or very similar routes.

I also track my rides using a bike computer, which is mechanical - a sensor on the wheel, wired to the unit, counts revolutions of the wheel, multiplies that by the circumference I've programmed into the computer. 

While I don't know if the computer is "accurate", it IS consistent. The Versa 2 is FAR from consistent. Sometimes it's higher, sometimes lower.

I cannot depend on it AT ALL, other than to show me a map of my route (IF it connected properly) and the time/duration of my ride (which DOES match that of my bike computer within seconds).

I have done all the troubleshooting steps Fitbit has told me to do, reloaded the app, restarted the device several times, and find that if it's not connecting, if I go to my phone and force a sync, it connects.

There's no rhyme or reason to it, honestly.

They simply have a problem, either with hardware, software, or firmware. At this point, I don't care which. I'm just frustrated, since the main reason I bought this device was for biking and it's useless for it.

[Jbp1954]

PS - I have the exact same issue if I use it under Exercise-Walk.

In addition, I forgot to mention, I've had numerous occasions when the tracking stopped in the middle of a ride or walk. 

Useless.

[wrebble]

If your watch does not connect within less than a minute then move to another position (few meters). When you are in home or near some structures then yeah, it will take time to connect. Also use "mobile data" as connectivity boost.
- - - - - - - - - - - - - - - 

@MarreFitbit Are there any news yet? Don't you need out TCX files to get help for pinpointing the problem and solution?

As I get it the watch is supposed to calculate distance/pace via GPS (Fitbit website says that). When the GPS is not present, it will use stride length.

So by opening the TCX file in MS Excel, you can see the GPS coordinates are accurately registered, which means the GPS is WORKING. Somehow in "DistanceMeters" the distance is still wrong. And it is wrong from the very first second!

So there are 2 possible answers why this happens

1. Fitbit watch is stupid enough that it can not measure distance via coordinates
2. Fitbit watch is dumb enough that it ignores GPS data and still keeps calculating distance via stride length (I vote for this)

How can I pinpoint these and you can not? How long time does it take for a professional team (who have learned this and are with years of experience) to fix this. You are not building a new watch - you are fixing a code.

- - - - - - - - - - - - - - - 

Also your website says "Real-Time Pace & Distance - Keep an eye on your speed and milage by connecting to your phone's GPS". If you Fitbit mods are saying one more thing about "stride length" then I can assume your statement on website is false (false advertisement).

[DawnH1]

The runs I have been out on since last posting have varied wildly. Sometimes under, sometimes over and sometimes the distance is about accurate. 

Someone in this thread mentioned that Fitbit told them they use their own algorithm. Well there is probably a very good reason why other trackers use a different one- it is accurate. Honestly 🙄

[2015Health]

That is exactly what is happening to me. 4 weeks ago it worked perfectly.
Something has changed. I have had this Fitbit only 6 weeks.