Pace/Lap display in Exercise

[Jdmcb66]

I have a Charge 6 and Iphone and within the past few days my laps/pace on my exercise details page has gone crazy.  I walked tonight, 2.23 Miles at average 19' pace.  The detail at the bottom says Lap 1 - 11'41"/mi = 3.63 miles.  I know my laps are set at 1.0 mi. I have gone back and earlier exercises that had lap1, lap 2, etc... now have similar one lap with ludicrous distances and no individual laps.  This makes me nuts, as a runner I want to know what my lap times are for training and improvement.

Anyone that can help would make me very happy.

[kvog983]

6 months later and the incorrect lap unit measurements are still occurring. This is a core feature of the app and it does not work.

[profet]

I am also now seeing this issue.

I use fitbit primarily to track my exercise. If it can't do that, it's useless. 

---

@JuanFitbit 

Any updates on this? This is a core feature of this application.

It's pretty obvious that it's just a unit conversion issue.

[JuanFitbit]

Hi everyone! Thank you for your messages and patience. 

Our team informed us that the issue with the split rounds/laps and pace should be solved by now. Please update the Fitbit app to the latest update available (4.38 or higher) to receive the fix. 

Please confirm over here, if this got solved for you or if any of you are still having this issue, let us know over here. 

[profet]

@JuanFitbit 
I am using version 4.38 on android and the issue is still happening.

Here is an example. Both screen shots are of the exact same work out. The app seems to randomly convert the distance and pace incorrectly. The Pace Laps are ALWAYS incorrect:

CorrectIncorrect

[mhouse]

You’re kidding, right?  If you mean converting 1 km to 1.6 mi and calling it solved then I guess you’re right.

I have the latest update 4.39 and even deleted and reinstalled the app (iOS) a still incorrect pace.

 

[Khukuri]

I agree.

I upgraded my app in iPhone to 4.39 and i am still seeing the issue.

The issue is not resolved yet.

[willswords]

So are you saying that the pace/lap issue isn't specific to the Fitbit devices, but also happens with Pixel watches?

[mhouse]

It's an issue with the app, not the device. This used to work just fine -
they apparently forgot how to do unit conversions when they "upgraded" a
while ago.

[Nattyem]

I also have the latest version of the iOS app and it still isn’t resolved.

[profet]

@willswords The watch works fine, but when the data is viewed in the app, they are doing incorrect unit conversions. See my post above with the two screen shots. It randomly messes up the distance and the average pace, and ALWAYS messes up the laps.

[JuanFitbit]

Hi everybody! Thank you for your messages. 

I've informed our team so that they are aware that some of you are still having the issue, so that they continue work on this. 

We appreciate your feedback and information.

[willswords]

Has anyone on this thread confirmed that the issue has been fixed for them? I tend to believe it hasn't been fixed for anyone unless someone actually confirms it has been fixed. I think you probably should remove the "Best Answer" tag until someone actually confirms it works.

[jjfeigal]

I just completed a walk after updating the Fitbit app to 4.39 and the pace/lap data is still not correct.

I worked in software development and software support for 40 years, and while I acknowledge an error was occasionally introduced unintentionally, it never took us 8 months to fix the problem. Also, unit testing and quality control testing were meant to insure basic functions were working properly before a fix was released to the customer base.

I’m at a loss to understand how what seems to be a straightforward conversion issue cannot be resolved by Google. There’s got to be a senior software engineer with experience that could solve this issue in a short period of time.

[HBT06]

No, this is still not fixed. My one mile laps are still showing 1.61 miles. 

[Fredlausier]

I think I see what the programmers did wrong.  They are measuring the laps in kilometers, but labeling them as miles.  1 kilometer is 0.621 miles.  1 mile is 1.61 kilometers (1 / 0.621 = 1.61). That is where that number is coming from.

[profet]

@Fredlausier Yep... we've been saying this for a while. Apparently it's too difficult to fix for FitBit/Google.

Bumping this thread to the top again until this is fixed.

[abrownMike]

Let's not place so much harsh assumptions on the team. I strongly doubt it's a matter of it being too difficult. We don't know what goes on behind the scenes. I don't think it's fair to do that. Let's just continue providing the feedback the team needs to get this fixed. 

[LFortier]

Has this problem not been fixed yet? I can see my run distance as 5.25 miles on the dashboard screen, but when I open the run it says it was only 3.27miles. The average pace is wrong. The lap pace looks like it is right, but when I export it to look at the map on google maps the  markers all move to laps of .62 miles which is not helpful. This still looks like a conversation issue. Why is it not fixed?

[abrownMike]

Looks like Fitbit app has been updated to 4.39.2.fitbit-mobile. Check for it and see if it provided the fix. 

[Priestyworld]

On Wednesday, following an update to the app, my walk showed the correct lap stats, i.e showing 1.0 miles:

The next day and ever since, it's back to showing 1.61 miles:

How did they manage that ??