Split pace

[Juho_U]

Hello!

I'm having problem with spilt pace cues.

I have set app to give voice cues after every km (Distance, Time, Average pace, Split pace), but split pace is always same as average pace.

Below is screenshot about splits I had on my latest run. I did run slow first and then picked up pace to make sure there really is an issue and I'm not just hearing voice cues wrong or running steady pace.

Ps. I'm using app version 2.10. Should I update, does the latest version have fix for this?

[SunsetRunner]

The current version is 2.10.1. By all means update the app before reaching out to support.

[Juho_U]

"Don't fix what is not broken"

No reason to update if it doesn't offer solution for my problem.

By all the means could you please tell me whether or not 2.10.1 is fix for split pace voice cues?

[gdio53]

---

@Juho_U wrote:

"Don't fix what is not broken"

No reason to update if it doesn't offer solution for my problem.

By all the means could you please tell me whether or not 2.10.1 is fix for split pace voice cues?

---

I can confirm that 2.10.1 announces average pace and split time the same, so not fixed.

[brutet]

2.18.2 and still not fixed

[aaccss]

I moved to an iphone two year ago, and found that splits worked properly with their IOS app.  Last week I moved back to Android and was disappointed to see that they still haven't fixed this.  This is simple math.  How hard can it be to get it right after three years?  I'm now in version 2.58.  

[Charly22]

How difficult is this to fix? 3 years old post and it works properly on IOS...

[SunsetRunner]

The problem is still there on Android.

[SunsetRunner]

The specific feature even works on a Lumia 640 (Windows 10 Phone)! Unfortunately, during my test yesterday the app crashed half way through my 10 mile (~16 Km) easy run.

Due to the fact that Fitbit doesn't allow the import of session files (GPX, TCX, ...) I had to resort to enter manually the data taken by an alternative app (Runtastic).

[SunsetRunner]

Tested again on the Lumia 640 after a factory reset (OS build 10.0.15063.1631 ) and the update of the Fitbit app to the latest version compatible with that version of the operating  system.

The app performed as expected in my 14 Km workout (~ 9.5 miles).

That means that, in my case, you earned time to fix the app on Android until the end of 2019, when Microsoft will cease any kind of support for Windows 10 Mobile. 

[adytom]

September 2019 and this still isn't fixed. I think fitbit never tests their software in anger! How can it be that after 4 years basic and annoying bugs like these are still not fixed? Instead of fixing basic functionality needed for sports like voice split times or topographical elevation and heart rates  recorded for runs, they seem more interested in adding useless gimmicks like sleep scores...

[Cmurchie]

Hiiiiiii it's August 2021.  Not fixed.