Lap pace alert first lap always 0:00 since 10.78 / 11.10

For the first lap I always get a 0:00 lap-pace on the alert-screen - no change if it is an auto lap or i hit the lap button.

From lap 2 everything is ok, in GC the data for the first lap is also ok... (6x Sapphire). Anyone else with this problem?

For the 1km autolap it helps to use the lap time (it is the same, so no calculation neccessary), but if i manually hit the button after 2,583km i would like to have the pace instead of the time...

Before 10.78 everything was OK.

0 alexander_mai over 4 years ago

#metoo

0 Former Member over 4 years ago

Same exact problem with 245 Music. I apologize for responding in the fenix 6 forum, but I can't find anyone talking about this elsewhere.

0 roc7241 over 4 years ago

me,too.

0 Tycho over 4 years ago

Resetting the "running settings" to factory solved the issue (and some problems with data fields which had not been visible on any page) for me.

0 Former Member over 4 years ago in reply to Tycho

Thanks. I thought I had tried that, but maybe not. If so, won't hurt to try again.

0 roc7241 over 4 years ago in reply to Tycho

Update V12.2, and resetting the "running settings", but still the same. why?

0 Brunoff1987 over 4 years ago in reply to roc7241

I have exactly the same problem with garmin 245 after last update... Pace for lap that pops up is always 0:00... For every lap

0 PSHINNYC over 3 years ago

Same issue but with Lap Power. I noticed during interval ride where I was going hard for one interval and then easy. It seemed that all the laps where off "by 1", meaning instead of giving me lap power the lap just finished, it was giving me the lap before that. Which explains why the 1st lap is always "0" since there is no lap before the first lap. Still doesn't explain why or how to fix it.

0 eezytiger over 3 years ago in reply to PSHINNYC

This is also true when following workouts on the bike with a power meter. Lap (interval) heart rate is always appropriate. Lap power lags by one lap on each interval. I haven't reported it, but I really should.

0 alexander_mai over 2 years ago in reply to alexander_mai

solved for me since V 23.00