To reproduce the bug, select Run, Training, Race Yourself, From History, go to a previous activity, press START.
Symptoms: the estimated finish time minutes & seconds are calculated incorrectly. Specifically, if you slowly increase your running speed you will see a progression in finish times similar to this:
44:55, 44:54, 44:53, 44:52, 44:51, 44:50, 43:49, 43:48, 43:47, 43:46, 43:45, 42:44, 42:43, 42:42, 42:41, 42:40, 41:39, 41:38, and so on.
notice how the seconds are steadily decreasing, but only drop by about 5 before the minutes drop by 1. Note that you will never see an intermediate time such as 43:22 in the above example - it will jump between 42:44 and 43:45. Can someone at Garmin with access to the source code have a look at this calculation? It is seriously screwed up. It looks like an integer rounding error or similar.
Also, I consistently find that at about 100m to the finish line the estimated finish time displays as --:--:-- for perhaps 20m before displaying again. Also, the estimated finish time can jitter up and down by +/-1 minute when there is only 20m to go to the finish, when running at a constant pace.
Add to this the other problems with race an activity, such as when racing activities more than about a month old, a large offset can be added to the time ahead/behind. E.g., you can be over an hour behind on an activity that is only 30 minutes long. Note that the "ahead/behind" display is correct, but the time ahead/behind has a large offset from zero. This bug has affected the Fenix watches for at least 4 years, and Epix 2 since they came out, and has been reported many times.
It would be really nice if the next firmware release could address these serious bugs in a very useful feature of the watch, rather than adding new activities such as "underwater pickelball" or "croquet"!
Regards,
Michael