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.

[HeWilliams]

I have an i phone too and have this problem

[Emallen1974]

Juan, I’m having the same issue. This problem first arose with my Fitbit charge. I thought it might be due to the device being a little too old, so I just upgraded to a Versa. Today I tried it on a run and have the same problem. Showing 1 lap of 9.76 miles even though the gps worked fine and my average pace is accurate. I want to see the pace per mile, which used to display just fine at the bottom of all the stats. 

[kvog983]

Just adding to the other replies here. The incorrect lap units on the app still persist after 3-4 months. I originally posted in the iOS form but my post was closed and I was directed here for updates, even though this is the Android forum. This is incredibly frustrating that this many bugs are allowed to be deployed and not rolled back or fixed. If it weren’t for the sync to Strava I wouldn’t really know my lap pace (I shouldn’t have to do the km to miles conversion on my own). 

original post: https://community.fitbit.com/t5/iOS-App/Lap-split-units-are-incorrect/m-p/5695879#M179267

[JuanFitbit]

Hi everyone! Thank you for your messages and feedback. 

We appreciate when you post, new symptoms and the troubleshooting steps that you have tried. This helps our team with their investigation. 

I've merged the posts/thread in the iOS thread and the Android threads here,as the issue affects both systems and so that everyone gets the updates at the same time. This helps us reach out to you all, keep the Community in order and keep track of the new developments. 

Our team is still looking into this. Hopefully it gets solved soon. 

[Seanjkl]

It seems there was another update pushed to the app in an attempt to address this issue. Unfortunately, this feels like the furthest misstep yet, as my 8-mile run was recorded as four laps:

• Laps 1–3: Measured in kilometers but labeled as miles.

• Lap 4: Labeled as 9.96 kilometers at a 6-minute pace.

To clarify the timeline on this bug so far:

• September 7, 2024: The issue was initially reported and acknowledged as a bug where laps didn’t function at all (e.g., a 6-mile run recorded as one lap of 6 miles).

• Early December: A fix was released, resulting in laps being tracked in kilometers but mislabeled as miles.

• Today’s Update: Now, three-quarters of the distance are tracked in kilometers but labeled as miles, while the remaining distance is lumped into the fourth lap with seemingly incoherent lap data.

As someone who works in software development, I’m genuinely baffled by how such a seemingly straightforward issue has spiraled so far out of control across multiple updates. This isn’t an edge case—it’s core functionality that users rely on and a fundamental selling point of the product.

At this point, I have little confidence that this issue will be resolved, and I can’t imagine how others could either. With an upcoming marathon and an extremely inadequate resolution timeline, I’ll have no choice but to purchase a competitors device. The level of product support from Fitbit since the Google acquisition has been deeply disappointing.

[mhouse]

Same here. Tracked activities are correct when finished.  However, once the activity is closed and the "other stats" are calculated pace/splits are converted to km but showing miles and it also changes calories burned and zone minutes are also incorrect (1 min/zone min regardless of zone - this is a problem for all activities).  So even if you don't care about absolute values and look at trends, the data is completely unreliable and useless for making decisions to improve fitness.

[JuanFitbit]

@mhouse @Seanjkl , Thank you for your messages and the info/screenshots shared. 
I'll pass your findings to our team, so that they know about the changes and take them into consideration while they work on a solution.

We appreciate that you both share the findings and changes. 

We will updating the thread as soon as we receive further info. 

[mgockel2003]

@JuanFitbit  - I have been checking this string for months and still have the issue with the 1.61 showing even though my IOS phone app and sense are set to miles.   Seems hard to believe this isn't fixed with so many people with this issue.   Can you please confirm it is not resolved yet?   Any guess on timeline for this fix?

[Slow_Steady]

Is there a solution to this issue yet? It is frustrating to have the pace calculated by 1.61mi rather ran by 1mi that is in the settings. 

[HBT06]

No fix yet. Still won’t give me an accurate pace per mile. 5 months now with no fix. 

[HeWilliams]

No fix here either still giving incorrect mile splits I you say 5 months now and not fixed

Moderator Edit: Personal info removed

[SeanTSanDiego]

I see this is still happening as of 1/19/2025 and I see the 0.50 mile splits showing 0.81 miles and the 1.00 Mile Splits showing 1.62 , has there been a solution on this yet? 

[StacieRuns]

Any updates to this? Looks like it’s been a few months since your post here. I have a Sense 2. The mile pace times are accurate on my watch but showing way faster mile pace times in the app. How can I fix this?

[monopear]

Is this solved? Mine's still doing it. 

[JuanFitbit]

Hi everybody! Thank you for your messages and info. 
Our team is still working on this. Hopefully this gets solved soon. 

We will update the thread as soon as we receive further info . 

[Justanotherguy7]

Not fixed in 4.35 for iOS. 

[JuanFitbit]

@Justanotherguy7 , Thank you for your message and confirmation. 

I'll pass the info to our team so that they are aware of this. We appreciate your collaboration. 

Hope this gets fixed soon. 

[DLK1868]

Please stop these meaningless responses. Bring this entire thread to a
close.

[JenBanner]

Has this been answered? I'm having this issue. 

[EmilyJS]

This issue is ongoing. When will it be fixed?