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.

[SonNamedIt]

Update: This brought the lap breakout by mile back. However, the pace is still inaccurate. Unfortunately it is still not working.

Saw something out on the web and it worked for me. I’m using an iPhone. Go into your Fitbit settings > select exercise under preferences > scroll to the bottom > select cues > make sure split pace (since last cue) is selected > click exercise at top left to return to last page > select frequency > choose what you want for your split length.

Hope this works for you too.

[Lynn975]

I appreciate the information. However, after many months of being
frustrated with my Fitbit not working correctly, I purchased an Apple
Watch. Each has its pros and cons. I wish Google had never purchased
Fitbit.

[SunsetRunner]

Thank you for the advise. I did what you said and went for a run. The lap pace is still not recording properly in the app. For example: Lap-6'14"/mi-1.61 mi

[SonNamedIt]

You are correct. I got too excited when I was able to see multiple laps broken out instead of the one lap. However, the pace per mile is still incorrect. Hopefully that can be fixed soon.

[Lynn975]

Me too!

[mattjohnsontv]

Same problem here. I’m training for a marathon, just had to buy a new Fitbit charge 6 because my charge 5 stopped working and Fitbit would not replace it. Now since Google took over not all activities show up anymore and splits are off on runs even though laps are set on watch. Why am I getting pace per 1.61 miles like everyone else. Fitbit needs to prioritize getting this fixed now - two months since this post and no answers and no updates? I want my money back or the app to work properly. ASAP. Bad look guys. 

--------

Found this helpful link to convert - it appears Fitbit is tracking minutes per KM and 1 KM = 1.61 miles even though it shows in the app as minutes/mile. This helps convert so you can get a sense for your actual splits. Why do you need to make it so hard Fitbit?!? Still doesn’t solve missing activities not showing up. Come on Fitbit time for a fix! This needs to be escalated. 

https://www.runnorthwest.co.uk/pages/race-pace-conversion-chart 

[ToddDerrick]

I've had the same problem for months. Today,  I figured out what they have done. Sadly, it makes the failure to fix this simple  problem all the more frustrating....

The pace shows "miles per minute" but it is actually "kilometers per minute."

1 mile = 1.61 kilometers

2 miles = 3.2 kilometers 

5 miles = 8 kilometers 

 (approximately)

I use these three distances because I assume these are common distances for most folks who walk or run. 

1 kilometer = 0.6 miles (approximately)

In my case, for example, I usually walk 5 miles. My pace is between 18 and 20 minutes per mile. 

So here is a typical display once this problem started:

I walked 5 miles, not 8. 

8 (kilometers) X 0.6 = 5 (miles)

A 12 minute pace (as shown in kilometers)x 1.6 = 19.3 minutes per mile. 

THIS WOULD SEEM TO BE A VERY EASY FIX..... if Fitbit really mattered to Google. I'm now convinced it does not. (I can't post the link, but you can  Google "Google killing  Fitbit")

[JuanFitbit]

Hi everyone! Thank you for your messages, feedback and screenshots shared.

I've informed our team and shared your updates so that they are aware of the new symptoms. 
They are looking into this, and will work a solution for it. 

Hopefully it will be solved soon. I'll update the thread as soon as I receive further infos. 

[mattjohnsontv]

Thanks for the update Juan. Unfortunately this is the same answer you gave us four months ago that it was being worked on. We need a timeline of when this will be fixed or we’re going to have to purchase different devices. Please advise as soon as possible. This is unacceptable.

[DLK1868]

Agree. I’ve been in Juan’s position of the customer facing role, and
unable to give the specific details due to proprietary info, but could work
with the team enough to say whether a root cause had been identified etc.
this answer continues to be too ‘pat’ and does not give me confidence that
Juan, or his direct manager, is on the resolution team communication.
Starting to give extra credibility to those articles about Google not
supporting FitBit. Shame. The battery life is longer than an Apple Watch,
the old simplicity was superior….I don’t need, or really want, all of the
functionality of an Apple Watch , but apparently Google will only support a
platform that does.

[sees]

App mixes miles and kilometers.  1 mi = 1.61 kilometers.

[HAN254]

When I first posted in this thread my app was showing one “lap” with my total mileage and a wildly inaccurate pace. Now it’s showing multiple “laps” (too many) and a wildly inaccurate pace. 

Original - 

 Updated - 

 

[HAN254]

I forgot to include that the stats above that show I ran 2.26 miles at an 11’35”/mile. 

[JuanFitbit]

Hi everybody ! Thank you for your comments and pictures. 
I have passed the info to our team so that they are aware of the changes. 
They are still looking into this. 

Hopefully it gets solved soon. 

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

[Concerneduser57]

That makes sense. Thank you for pointing that out. The time of my pace on all of my runs however are still wildly inaccurate. I know for a fact I have never run a 7 minute mile for example, but the app was saying I was making this pace in my splits.  That said, the pace on my most recent run was finally accurate even if it was showing it measured for a 1.61mile/ or one kilometer. So there is hope that my split paces will begin making sense again! 

[Yogamomtx]

What is the update on this?  I am

still having this problem.  

[SunsetRunner]

None of the updates have changed this problem. Many of us are very disappointed with Fitbit/google.

[JuanFitbit]

@SunsetRunner @Yogamomtx @Concerneduser57 , Thank you for your messages. 

The update I mentioned above was the v4.32 app update.

We appreciate that you confirmed that the issue was not solved with it, so that I can inform our team, and they' ll continue working on this. They are working had to bring you all back on track as soon as possible. 

[jjfeigal]

I am still having this problem with my Fitbit Charge 5. My Fitbit app is version 4.32 for my iPhone 14 Pro.

The pace feature used to work a while ago, but hasn’t worked for a while now.

This is a software bug that should be easy to fix given that the Charge 5 seems to be tracking time and distance correctly although I am no longer provided voice mile times as was previously provided by my Fitbit Charge 3.

[RiekoC]

Hello @jjfeigal 

I noticed that you mention you have the iPhone 14 Pro. You posted in the Android app forum. Please submit your issue in the iOS app forum (<-- click link) so that the iOS developers have your information.