Connected GPS Pace and Distance is Inaccurate

[DanielMena9]

Went on a run today with my Charge 2 on one wrist and Charge HR on my other wrist. Also had RunKeeper to measure my distance. I started my run with about the same number of steps on both FIT devices. 

After the run, my Charge HR had almost 2K more steps than my Charge 2. In addition, my GPS map on FitBit matched my Runkeeper map which is about a 3.5 mile run BUT FitBit pegged the same route as 1.73 miles >.> 

Why doesn't this device work as advertised? I really like the design and feel of Charge 2 but if it can't do its job accurately, all is for not and I will be shorting FIT as it appears to be a widespread issue (I have maps and photos if someone from FIT wants the data).

Moderator Edit: Edited thread title.

[r.heritage]

I seem to have the latest firmwhere version, but have discovered this morning that my GPS tracked runs are being recorded at about 20% longer distances than actually run...

[Rollerskier]

Welcome to the club .......

[JDGirl]

I have updated everything and my GPS on the Charge 2 says its connected and the map is accurate, but the distance is way off. My daily bike ride is 3 miles but it says 1.8 miles. I'd really like an accurate pace to be calculated, but that requires accurate distance. 

[hawkeye1952]

I am sorry to say. That this is a on going problem. This issue has been talked about, some so called fixes put out. Yet everyone is having the same on going problem. I do not use anything that use this connected GPs. It is still a problem with no solution in sight. Most of the people have said that they will not buy another one

[RLKM]

July, 2017. On a recent Rock n Roll half marathon  my charge 2 had me at over 2 miles more than the 13.1. This weekend, on a  Ragnar race, a 16.3 leg registerd at 17.5.  And, my charge 2 had recently updated per cite instructions. My fitbit is a cherished gift, but I must go  back to my Garmin. Knowing  my pace and distance is too important. Saw more Garmins at the Ragnar on the serious runners. 

Sigh... It makes for a good watch, and heart rate monitor,  though. 

RLKM

[SunsetRunner]

This morning I went for a run together with my husband. He is a more experienced runner and has a Garmin sportswatch. I am starting to run and use my Fitbit Charge 2 (which I love honoustly). Unfortunately in the end our distance was not alike! The Garmin showed only 4,3 km while I tought I had ran 5,7 km according my Charge 2! I was really disappointed 😩. My most recent update has been done yesterday so that cannot be the problem. Is there any solution on this topic availabe? Thank you.

[Colinm39]

@SunsetRunner  If your are getting those variations you maybe experiencing what some of us in the Southern Hemisphere have reported, see this link.  The Charge 2 and the Blaze gain 30cm (12")/second in an East/West direction. I compared it against my Surge which is accurate and when I go from a North/South direction into an East/West direction the Blaze, immediately the pace goes about 2 minutes/km faster. Swing back to North/South and it drops that extra pace.

When I just use the App (MobileRun) it is accurate.

---

@SunsetRunner wrote:

This morning I went for a run together with my husband. He is a more experienced runner and has a Garmin sportswatch. I am starting to run and use my Fitbit Charge 2 (which I love honoustly). Unfortunately in the end our distance was not alike! The Garmin showed only 4,3 km while I tought I had ran 5,7 km according my Charge 2! I was really disappointed 😩. My most recent update has been done yesterday so that cannot be the problem. Is there any solution on this topic availabe? Thank you.

---

[Annabel_b]

Hi 

Fitbit have marked this thread as solved, despite the fact that the problem continues and was never solved, so no one from Fitbit will be monitoring any of the messages added to it. I suggest that you log the problem with Fitbit Support or start a new discussion thread. This has been a problem for at least 9 months now and Fitbit either will not or cannot fix it. 

[hawkeye1952]

I sorry to report that there is no fix. Fitbit as the other person stated. Has marked this fix. Yet  the problem is still there. 

[Annabel_b]

Hi @Colinm39

Just curious, but why do you have a Blaze as well as a Surge? I'm thinking of replacing my inaccurate Charge 2 with a Surge and am interested in your opinion of the Surge.

Cheers

Annabel

[Rollerskier]

Fitbit sent out a firmware update for Charge2 this week.  I installed it yesterday but has not tested it out yet. Latest version is 22.54.6. According to Fitbit several minor bug fixes? 

VERSION 22.54.6

This release includes several minor bug fixes.

Has it solved some of our issues?  Very wrong GPS distance in the southern hemisphere?

Inaccurate GPS distance in general?  Inaccurate heart rate? Slow reaction to changing heart rate during interval training.  Not reacting to heart rate peak levels?

What’s your experience with the latest Firmware? Any good news?

[Annabel_b]

@Rollerskiersadly no. After installing the update my Charge 2 with Connected GPS recorded an 8.6km run as 10.32km so if anything, the problem is worse 😒

[SunsetRunner]

I have also read the problem might have something to do with iphone7. Seems with other types of smartphones Fitbit works OK. So I have done there an update as well. Just in case... Are you all using iphone7? Or is the problem on Fitbit side only?

[Annabel_b]

@SunsetRunnerI'm using an iPhone 6. Also, I am comparing the distance recorded by the Charge 2 with Runkeeper running on the same phone so using exactly the same GPS input. I have also tried my Charge 2 with an iPhone 5s with the same result. The problem is definitely with the Charge 2 and only when moving West-East or East-West. 

[Rollerskier]

I am using both iphone7 and iphone6plus with Charge2.  My Iphone6plus is giving much better results on distance than iphone7 with the Fitbit App.  Fitbit App with iphone7 measures also small distances when I am not moving.  However, with the NikeRun Club app iphone7 and iphone6plus give both very accurate distances.

Fitbit app with Iphone7 is very inaccurate when walking(5-6 km/h).  When roller skiing 20-30 km/hour its much better on distance as long as I not stop for a short break.

I will try out the new Firmware this weekend to find out if something has changed regarding distance.

[hawkeye1952]

This is a on going problem. I have a android phone and have the same problems. They do not have a fix for the problem

[bolivar]

charge 2 with recent firmware update threw my known stats by a decrease of approx 9%. I have been using a charge up until a few days ago and have been doing the same distance for a long time. i have my distances memorised and also use map my walk app. the FIX needs fixing.

[Colinm39]

@Annabel_bThe Surge... Very accurate for me but I can't wear it 24/7 because I have large wrists and there is no breathing where the "hard" band rests on the side of the wrist bones and I get irritation immediately...  I use the Surge and MapMyRun to prove the East/West inaccuracy on the Blaze Connected GPS.

Like many I'm awaiting the release of the Blaze 2, and others the Charge 3 in the US 2018.. The Blaze 2 will have inbuilt GPS and hopefully have the accuracy of the Surge. See this link and See this link

---

@Annabel_b wrote:

Hi @Colinm39

Just curious, but why do you have a Blaze as well as a Surge? I'm thinking of replacing my inaccurate Charge 2 with a Surge and am interested in your opinion of the Surge.

Cheers

Annabel

---

[Annabel_b]

Thanks for the info @Colinm39. Interesting about the Blaze 2. I wonder if Fitbit are planning on completely phasing out Connected GPS. That would explain the reluctance to spend any money or effort in fixing it. Sounds like built in GPS is the way to go. Still, it's pretty dodgy that the Charge 2 is still on the shelves.

[Rollerskier]

Start up, breaks and shut downs of a run.

I mentioned previously that Fitbit records distance when you are not moving as well.

I have attached a run were you can study this(zoomed in on a section of the track).  Anybody else has this problem?

You can see the horisontal lines in a wobbling pattern.  These represents distance that is not real.  Point 9.80 km represents the time were I stopped the recording.  Open circles represents the time when started the run.  Both these placed are geographical wrong.  I started and stopped in the middle of the vertical lines.  The vertical lines represents different laps on a round trip track. The overall distance roller skiing is not that wrong when the speed is around 20-30 km/hour.  However, if I stop for a break (without pausing the recording) in an interval training the distance continue to record in this wobbling pattern.