RESOLVED: Distance travelled does not match distance logged

[DerrickS]

Fitbit Update 03/09/17

Hi everyone -- Some good news to share! This issue should now be resolved!

If you were previously experiencing this issue on iOS, please try it again as our team has pushed out a fix. Feel free to give me some feedback about your post-fix experience. Thank you for your patience as we worked to get you all back on track.

---

Fitbit Update 2/28/17
It was recently brought to our attention that some iOS users are experiencing their mile splits for GPS workouts don’t add up to the total distance of their workout. Our team is aware of this issue and is currently working towards a fix.

[Redwalker84]

Just wanted to post that my Fitbit issue has also been resolved. Thanks to all who helped. 

[DerrickS]

@Nancy07 For your husband's Blaze, I would recommend verifying that he's inputted his personal information like his height, weight, and age correctly. Personal information like this is used when tracking fitness stats and having the wrong information could be affecting his accuracy.

I'd also recommend setting his stride length to "Auto" or that he follows the instructions listed here to input a custom stride length.

Lastly, I'd also recommend that your husbands wrist settings matches the wrist that he wears his tracker on.

@JamesW123 This problem should be fixed the next time that you sync your tracker. The fix was implemented on the back end, so a sync is required for the changes to take effect.

[Redwalker84]

That happens to me all the time. The second map is always correct but the first one is wrong. The first map seems to remember where I walk, so it has the same route for a while. I don't think it's a big deal though as long as the mileage is correct. 

[JNagano]

That's been happening to me, too. The map that shows up on the activity screen is different from the one that shows my actual GPS-tracked run.

Sent from my iPad

[Pjd1300]

---

@Nancy07 wrote:

Yes I have exactly the same problem. The map is from a few days ago but when I tap on it the correct map then appears to be right. There are gremlins in this App at the moment. Needs sorting and updating please Fitbit

---

@Nancy07 @JNagano @Redwalker84 @jrfromm

This particular gremlin has been taunting me for the longest time, since at least summer, 2016.   However, aside from this issue being off-topic, it doesn't appear to affect the functionality of the Fitbit or the app in any way.

[spike290166]

Hi, Not fixed for me on my Blaze, but my fault is slightly different, my distance on the app is always 2 miles above my Wife's Charge 2 HR on a 5 mile walk, and the watch is 1 Mile higher over the same distance, so the app and the watch do not match and is 20% and 40% different

[Clicker75]

I have not seen any change with my Alta yet. I have done all the updates as far as I can tell, but the problem is still there. The Fitbit app logs steps correctly, but the miles are about 30 percent higher.

[kelsigle]

My correlation between mile splits and overall mileage since Thursday has been accurate. The previous 2 weeks where it was incorrect has not been corrected. As long as it has been corrected going forward I am OK. Now I am having a problem with the part of the app that recognizes the 250+ steps an hour. Even when I am reaching this goal the app is not recognizing it and logging it on the app. Seems to be worse if I get to the goal in the last 10 minutes of the hour. Very frustrating to have my Blaze say yeah 11/11 hours but the app is only registering 9/11!

Kelly
Sent from my iPad

[Nancy07]

Tried again today. Have logged out of App shut iPhone down, restarted downloaded new App and still same. There were two of us walkers with more or less identical stats today on Fitbit. But my husband's Blaze says his pace is faster and that he has walked one mile when we both had walked 0.8. At the end of five mile walk this adds up to a lot of extra mileage. His height and weight and stride are all accurate. Seems to be a problem since getting upgrade to iPhone 7 (which is obviously running latest software). Fitbit and iPhone 7 are incompatible. Or else this Blaze is faulty. Waiting for a response from Fitbit as emailed them today.

Sent from my iPhone

[Kobalto]

Now this is working fine for me! Previous records were also corrected, so now total distance = splits. Thanks!

[ScottMom4]

I am concerned that mine is still functioning incorrectly. Last Wednesday I ran 5 miles. My app told me each mile and my average pace. When I was done...what was logged on my dashboard was completely different. I then ran again on Saturday. My app was not working and told me I was on pace for a 17 minute mile...which I know was inaccurate. I turned it off and continued to run. I am training for a half-marathon so I ran close to 11 miles. I was given the steps but no log of a run. 

[Cindy49]

Having same problem. Been happening 3-4 weeks. Was trying to reset my Fitbit now my steps are not showing on phone.  Synced and powered down phone

[NJA753]

1. What type of iOS device are you using?  iphone 6  

2. What iOS version is your device running (ie iOS 10.2, iOS 8 ,etc)?   ios 10.2.1

3. Were you using the Apps GPS, Surge's built-in GPS, or Charge 2/Blaze's Connected GPS to track your workout?   Using Charge HR.    Fitbit is NOT listed under Location services.   It's not listed under the app itself either.

4. Does force quitting and reopening the App help?  No.

Distance is not accurate:

Day 1:  Walked 6 miles, Fitbit logged 4 miles.

Day 2: Walked 3.4 miles.   Fitbit logged 2.4 miles.

Day 3:  Walked 3.4 miles. Exact same path as Day 2.  Fitbit logged 2.17 miles.

[DerrickS]

@spike290166 @Nancy07 It's hard to say what's exactly going on without more context, but I think that the suggestions below should help:

• Verify that both your wife's phone and your phone are able to track GPS when your phones' screens are locked. 
• Your phone can identify your location and can track your location when you're not using Wi-Fi. You can find more information here.
• That you've both selected workouts from the exercise menu that support Connected GPS.
• Tried the troubleshooting steps mentioned here.

@kelsigle This discrepancy between distance and miles/km splits should be resolved moving forward. 

In regard to you not receiving reminders to move, I would recommend the following:

• Make sure that you have notifications turned "On" on your Charge 2. You can verify this by holding Charge 2's button for 2-3 seconds when it is displaying its clock face.
• Make sure that you keep these three tips in mind when wearing your Charge 2 to maximize your heart rate readings accuracy.
• Verify that you have Reminders To Move turned on in your settings. Click here for instructions.

@Cindy49 I'd recommend re-pairing your Charge 2 to your account by using the replacement setup instructions mentioned here.

[JNagano]

Has the Moderator noted this issue as RESOLVED??? It isn't resolved. My running stats from Feb. 23 are all incorrect as described. Distance run and total average time is off. 

---

---

[Nancy07]

Don't know why it's now shown as resolved but the problem persists. Through determination and self diagnosis we can confirm that the fault is with the IPhone 7 Fitbit app. The Blaze distance travelled is correct when using different handset (Samsung galaxy). The data for distance and pace match other users doing same walk. Switch back to iPhone 7 and then pace stays way too fast and distance recorded is 20 percent too high. This is not a problem with gps on the iPhone as other distance and pace app works perfectly. The problem is with Fitbit app on iPhone 7. But I doubt anyone from Fitbit will admit there is a problem!  

[Nancy07]

Don't know why it's now shown as resolved but the problem persists. Through determination and self diagnosis we can confirm that the fault is with the IPhone 7 Fitbit app. The Blaze distance travelled is correct when using different handset (Samsung galaxy). The data for distance and pace match other users doing same walk. Switch back to iPhone 7 and then pace stays way too fast and distance recorded is 20 percent too high. This is not a problem with gps on the iPhone as other distance and pace app works perfectly. The problem is with Fitbit app on iPhone 7. But I doubt anyone from Fitbit will admit there is a problem!  

[stevethompson49]

I've had my Charge 2 for about a month.

Using the connected GPS, it has always over-estimated the distance walked. I've kept records over the last week and it's consistently showing around 17% longer distance than actually walked. That also affects the calculation of pace and calories.

The distance reported is more accurate the faster I go. If I drive the same course, at about 60kph, the distance reported is quite accurate. When I walk the course, at around 4.5 to 4.9kph, the distance reported is overstated by about 17%.

I suspect that the FitBit app accumulates the distance between each successive GPS position recorded. Because the satellites are constantly moving, every calculation of position can be up to a few metres off. This leads to a zig-zag course being recorded, the total distance of which is longer than the actual distance walked. I suggest that the app needs to smooth the course recorded, or maybe to reduce the sample rate for lower speed exercise.

[ScottMom4]

I have been using my Fitbit and Fitbit app to train for a half-marathon. I am quite nervous now that I haven't been running the distances needed and that my pace isn't what I thought. I was feeling confident and now I am terrified!!

[stevethompson49]

If you've been running, your distance recorded will be more accurate, because at the faster speed the GPS trace will be less zig-zag, more straight.

You could use your car or Google Maps to measure out the required distance, and record your running time. FitBit's are accurate recording time, but not distance.