Pace (mile splits) has not tracked accurately

[Mgilp]

On Fitbit app, pace or 1 mile splits has not been accurate since Sept 2024. Seems to be a systems problem that is being ignored. WHEN will this be fixed?

[KatherineNY]

@Mgilp How do you know this? What did you notice as wrong, specifically, about it?

I would also like to add that the same route I jog or walk show different miles (distance).  When I jog it, tells me I covered more miles than if I walked it.  I enable the GPS for both types of exercises. The same 2 laps around my local park. And I don't know why.

[JenBanner]

I have the same problem as well. I can go for a 3 mile run and it shows that I’ve done six laps.

[Wanch]

@JenBanner -

Here's some things to try.

Restart the Device: Restarting your Fitbit Charge 6 can often resolve many issues. To do this, press and hold the button (or the back and bottom buttons) for 10 seconds until you see the Fitbit logo on the screen, then release the button. Your Fitbit will restart and show your clock face once complete.

Check Laps Setting: Ensure that the laps setting is enabled in your Fitbit app. Go to the section with "exercise shortcuts" and click on run, walk, or hike. You should see "laps on" or "off." Switch it back on for all exercises.

Verify Stride Length: Sometimes, incorrect stride length settings can cause tracking issues. Check and adjust your stride length in the Fitbit app settings.

Update Firmware: Make sure your Fitbit Charge 6 is running the latest firmware. Sync your device with the Fitbit app to ensure it has the latest updates.

Sync with App: Sync your Fitbit Charge 6 with the Fitbit app to save your device's data and ensure everything is up to date.

[JenBanner]

Hello

I did both of these things. This time it got the number of laps right (3 miles, 3 laps) but it said that I ran them at 7 min pace. Not quite. My average mile was 11 min and my run was about 33 min.

So a try still not resolved.

-Jen

[David_FBC]

I am glad someone else is complaining about this, because I find it incredibly frustrating.  @Wanch - do you work for Fitbit?  Does anyone have the ability to bring up the following issues with the developer/engineering teams?

1. Why not display the full duration of the activity?  Why is it rounded to the nearest minute?

- I don't care that my run today was close to 9 minutes - I would like to know exactly how long it was.  There is plenty of space in this UI to display the seconds, and even tenths or hundredths of a second.  Surely the data is available, so why not display it.

2. The laps/pacing information is simply wrong - it is definitely a bug.  I have seen this multiple times, and it is always frustrating.

- I have a loop that I like to run, which is just a little bit more than a mile.

- When I finish a run, what I really want to know is:  How long did it take me to run the first mile?  This drives me crazy - this must be the most basic feature for any kind of exercise app.  If you are traveling any kind of distance broken into units (like miles), the user probably wants to know how long they spent on each of those units.

- Yet, in my run, which was 1.02 miles long, and took a total of "about" 9 minutes, somehow, I am shown that I was running the first mile at a pace of 5'28"???

- This is obviously wrong, and it also leaves out the key information I want to know.  Pace is a nice extra-stat, but the most basic question here is: How long did it take me to run the 1st mile???

- I have tried all of the update, restart, sync, etc. steps, but each time I go for a run, this problem is always the same.  The pace is WRONG and the information about the actual time it took me for each unit is MISSING.

- Sorry, but I am trying to train for a triathlon now, and I got this Fitbit for Christmas, and I am just really, really frustrated that I can't see any of the data that I actually care about when I do something.  I don't understand how you can have a fitness app that doesn't display some of the most basic information like "how long was I running?".  What do I need to do in order for this complaint to become a bug-ticket with the devs?

[SomchaiArron]

Really 😏

[Wanch]

I do not work for FitBit. 

I'm just another in the long list of frustrated, long time FitBit end users that searches for fixes to issues with their equipment.