Screwed up data first km in v23.00?

This happened several activities in a row now. Directly after start, my Fenix 6x autolaps for 1 km after 1 second. The time shows up absurd in the log. After 1km of actual running, the watch blips for auto lap 2 km with a km-time that is longer than I have been out. Something seems very screwed up here, right? Anybody else having similar problems?

0 tmk2 over 3 years ago

Did a couple of runs on 23.00. No issues whatsoever. Are you sure you had a good GPS lock before staring the activity?

0 DALI02 over 3 years ago in reply to tmk2

Yes, gps was green before start. And the track looks perfectly fine. I got the precise same error on my last 3 runs.

0 Tisztul_A_Visztula over 3 years ago in reply to DALI02

Maybe some of them helps:

1. Manually delete CPE.bin from the watch, sync again to get the file again.

2. Acquiring gps signals for 15-20 minutes (I guess it is called soaking) tbefore the activity. Certainly with open sky.
Normally one soaking is enough, it makes no sense to do it before eqch activity

3. Long push power off. It is not a reset during which you lose any data or settings.

Let us know whether any of them helped you.

0 Former Member over 3 years ago

Former Member already posted some helpful pointers, hope you get it sorted. This looks very interesting, if I were a Garmin developer I would want to investigate. Perhaps you can contact Support and ask them if they want to have a look at this activity?

0 5996474 over 3 years ago

Similar type of thing here. Garmin recorded the first lap as 10:00mins (correct) distance was 12650 metres!! Av pace 0:47min/Km. Even Kipchoge won’t manage that!

I’ve done a few runs on v23.00 with everything ok. Had a decent amount of gps green time before the start. I was however using a structured workout that does the laps for me. This discrepancy was in the first lap of 10mins warm up but was as you described.

I really wish Garmin would sort themselves out. Constant race prediction errors, Vo2max, training load errors, training effect category and now this.
It’s the same story with every software update. More things broken than fixed from the previous version. Very disheartening when we’re all working so hard, no wonder the likes of Coros and Apple Watch are gaining such a following. I personally know 3 Garmin users that have gone that route and seem very happy. I may not be far behind them.

0 Tisztul_A_Visztula over 3 years ago in reply to tmk2

It came to my mind that maybe this phenomenon is related to the “Lap pace is 0:00 in case of of first lap” bug. Why? Garmin had a fix in alpha/beta of 22.xx, which was finally eliminated from the changelog of 23.00, but my experience is that Garmin modified something, because yesterday I got not 0:00 for the pace of the first lap.

reference: forums.garmin.com/.../1490654

0 DALI02 over 3 years ago

Thanks all, a factory reset seems to have fixed the issue for me. Have no idea what cased it. But works fully normal first run now after reset.