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.

[CTT2615]

Okay - here on the equator in Singapore, 1.5 degrees N, a 5km Parkrun measured 5.0km on Strava, and 4.95km on connected gps. 

[Rollerskier]

I have done 2 more tests today comparing iphone6+ and iphone7.

The first showed 2,79 km for iPhone6+ vs. 2,74 km for iphone7 - deviation (50m, 1,8%) and the second iphone6+ 2,14 km vs. iPhone7 2,13 km - deviation (10m, 0,5%).

I can see that there are some minor deviations between the 2 paths drawn on the map that explains the deviation in meters. 

I think I can conclude after 4 tests that my iphone7 GPS distance has improved a lot.  The iphone6+ was ok previously also. Iphone7 showed earlier always the longest distance that is not longer the case.  Iphone7 has been a problem since I bought it 1 year ago. Perhaps it is improved due to Apple and the new firmware for iphone7 included in the iOS11.0.2 update - not the latest Fitbit charge2 firmware ver. 22.55.2?

Based on your feedback it looks like at least the iPhone users on the Northern Hemisphere get a better GPS distance accuracy with the latest setup.  And that Fitbit unfortunately still has a few bugs to sort out. 

Do you have some more examples with the latest setup that you would like to share with us?

[SunsetRunner]

I tested it as well today and according to me there is an improvent! My fitbit with connected GPS IPhone 7 said I ran 5,14 km while Runtastic was saying it was 5,12 km. Only 200 metres difference which is acceptabele to me. In the past it used to be 500 m and more! A positive progress if you ask me!

[SunsetRunner]

Hi everyone,

It's been really interesting to read your posts on this topic.

I must say I have not seen any improvement since the latest updates to the App and firmware.

My Charge 2 still seems to be logging more steps and miles than my other device and the App on my mobile. The Connected GPS function still does not map my track correctly.

If anyone has a suggestion on how to improve the function of the device / app please let me know.

FAILED TRACK

[Rich_Laue]

I find freeing some memory always helps, but im on Android, i don't know which of the 3 apps your running.

[SunsetRunner]

Hi Rich_Laue

I'm also on Android, but I am not sure what exactly you mean by "which of the 3 apps you're running"

I use the Fitbit app version 2.59 on my mobile and I also use the Viewranger app to track my route, as it is more accurate.

I also carry a Omron Walking Style IV 3 axis pedometer to cross check my steps and distance.

The attached pic shows the track recorded by the viewranger app which proves to me that my mobile phones GPS is working correctly.

[CTT2615]

Unfortunately my planned 'northern hemisphere' test in Hong Kong didn't come off - amongst other things, I wasn't able to get away from Central and all the skyscrapers, so GPS was useless. There are a couple of tests from others that suggest that all in fine in the North.

Now back in the southern hemisphere in Canberra (35.28 S), I just did a quick walk at lunchtime with both Strava and Fitbit connected GPS running: Strava = 2.9km, Fitbit = 2.88km. The (huge!) inaccuracy that I was seeing prior to this last update is gone and so, from these tests at least, I think it is safe to say that the problem has been fixed for both hemispheres. The path I followed was a closed path (end point same as start point).

Note that these tests have only been about the differences previously seen between 'connected GPS total distance' (the total distance reported measured when you trigger an activity on the Charge 2 device itself - and hence the derived figures of pace and the fitness score), and the distances measured by an independent app running on the same phone that supplies the GPS to the Charge 2. Its not going to pick up issues with the performance of the phone GPS itself, nor step counting issues, nor altitude/elevation issues.

Conveniently, this now means that the activities pulled over from fitbit by the Strava app, with the heart rate data, should be accurate - or at least accurate enough - and thats a win!

For the record, I'm using an iPhone 6S and Fitbit Charge 2 running 22.55.2 

[Rollerskier]

So it seems at least for the iPhone users that GPS distance tracking started from both the Fitbit app and started connected from Charge 2 have improved ( iphone6s, iphone6+ and iphone7 ).

((It took me 1 year to get accurate results with iphone7 so I probably should keep a safe distance to iphone8 or iPhone X until somebody can confirm that they work accurate with Fitbit as well.))

Just for the record have you updated your phone to iOS11 as well?

It could be that the Fitbit App running on the iOS11 vs iOS10 might be the main reason for more accurate results. Androide users have not reported any improvements with the the latest Charge 2 firmware.

However, strange that CTT2615(Canberra) and Cobalto(Santiago) are getting different results for connected GPS both using iphone6s on the same Charge2 firmware?

Anybody else in Australia that has tested the connected GPS from Charge 2?

[CTT2615]

Actually I am still on iOS 10.3.3... so it's not an iOS 11 improvement.

[Rollerskier]

Well, thats interesting to know.  At least something has been changed so the improvements on my iphone7 is very significant while iPhone 6+ is minimal where I operate in Norway.  Unfortunately I did not do any test between the IOS11 update and Fitbit firmware update.

[Kobalto]

Hi @CTT2615,

It's great that it is working well for you, is it possible that you share with me the downloaded TCX file? I can run an analysis in Excel, as I've I done with other tracks in https://community.fitbit.com/t5/Charge-2/Connected-GPS-is-Inaccurate-in-Southern-Hemisphere/m-p/2232...

[CTT2615]

Happy to do so - but at the moment, the fitbit website is giving an error when I try to download the TCX file. Will check over the weekend, and will either post here or PM to you.

[Kobalto]

I had the same issue today, but only when using Microsoft Edge, I tried Chrome and it worked.

Today I ran again using both IPhone tracking and Connected GPS. Still incorrect measurement from Connected GPS. Analyzing the TCX file, it still asumes that there are 111,200 Km per long degree (which is right if you are in the equator), instead of ~93,000 Km for my latitude. Can't believe they can't solve something this simple! 

 

[Kobalto]

Today I switched to IPhone 7. I did the same test again, and guess what? Same results, Connected GPS keeps measuring distance incorrectly 

Upper image is Connected GPS, lower is direct track with IPhone

[hawkeye1952]

First I keep my phone in a case on my belt. Here is what I have found out since the last update. If I open the fit bit app and use it by it self. Then it almost right on. If I use the app with another program running like endomondo. Then the app can not measure correctly. I found it to be off by as much as.50 miles. It can not find it self.

[Rollerskier]

The internal life of Fitbit is a black box.

I only run one App using GPS at the time on the same phone.  I use always 2 phones to check and compare the results simultaneously.

"Kobalto" - Are you using 1 or 2 phones when you compare the results done simultaneously?

You mentioned you have changed to iphone7 lately but do you still have your iphone6s around to check this out with 2 phones simultaneously?

Previously I had 2 Fitbit trackers set up at the same phone. This was also a mess if both where active connected at the same time( the other tracker in the same room ). I was also trying to compare the HR with 1 tracker on each wrist connected to the same phone...did not work out too.

[Colinm39]

@RollerskierI'm currently testing my HR after having the Ionic for 11 days. Comparing the Ionic V's Blaze.. The type of tests follow and I always keep my Fitbit One on me 16/7. I have also started comparing the Ionic GPS with the Surge.

1. A 24/7 day, one on LH and the other RH wrists. That also tests my sleep.

2. Next day I swapped the wrists for another 24/7

3. Every time I do this, my Fitbit One is with me 24/7bathroom spikes at the the same time.

Results..

BMR is 3 bpm higher on the Ionic, so I will let that settle a little longer

Cardio Finess down from 43-47 to 42-46... Expected

Steps on the Blaze and Ionic were with 1%

Steps comparing the One to both devices , the One was higher by about 9%. Typical

GPS Ionic appears consistent on distance checking against MapMyRun

Both the Blaze and Iconic had me at 56bpm over 7 hours sleep, my bathroom spikes were at the same time.

The sleep graphs were close enough on comparison couple of breaks in the awake time but consistent over the two 24/7 tests.

But, I have just emailed @Kobalto and would like to take up his offer of sending TCX files to examine a walk I did today. I had odd issues with pace even though my steps were 123-124 each minute, reasonable consistent. I was suspicious because I had spurts of 2min/km faster in the East/West direction and the minute I turned the corner to North/South it was back at my normal pace of around 12:30min/km walk pace.(I'm Southern Hemisphere).

I have kept this post here because that is where the action is on checking the GPS.

The one good thing today on the two walks, the GPS connected immediately on the Ionic.  Other days it has lagged about 2 minutes.  That is when my GPS Status App has immediate connection.

[hawkeye1952]

Went for my morning walk today. Weather heavy, overcast, light drizzle. Check the gps satellites strength and found that I had 5 very strong signals. results as follows. Endomondo was 1.61 miles and fitbit 1.46 miles. Even the heart rate was off

[SunsetRunner]

Hi everyone,

I have been doing my own tests and have been posting on

https://community.fitbit.com/t5/Windows-10-App/GPS-Tracking-unreliable/m-p/2230144#M12364

I hope you manage to find a solution.

CliveP.

[Rollerskier]

If we could get a Fitbit moderator involved so perhaps we could get an update on the status solving these issues.  The southern hemisphere problem should not be that difficult to debug for Fitbit. I would in general assume that Fitbit monitors the activity on the community but on this tread there is no response....