Pace display switch to exact values instead of rounded values ?

I doubt it. I think Garmin's rationale is that instant pace is not very accurate, so even though it's shown in Connect after fact with 1s granularity, Garmin chooses to display it in real time on the watch with 5s granularity. (A very long time ago, Garmin used to show pace with 1s granularity, so it's clear they made this change in response to *something* - maybe users were complaining that instant pace fluctuates too wildly.)

You can always use a 3rd party Connect IQ data field which shows exact pace, like this: Exact Pace Datafield (1 second steps)

Btw, even if Garmin were to show pace with 1s granularity, that's not truly *exact* pace, to be pedantic.

Consider that:

- 1s / km is not the same granularity as 1s / mile, so your choice of display units affects the granularity of your pace, and any arbitrary pace won't be *exact* in both of the situations where it's expressed as min:sec / km and min:sec / mi, except maybe for a few edge cases.

- activity speed is internally stored and recorded as floating-point (decimal) values units of m/s (so the underlying value is more granular than what's displayed). For example, if your current speed is internally represented as 3.056324 m/s, then it's unlikely that this can be exactly converted to a pace in min:ss / km without either rounding the result to the nearest second or displaying decimals.

Otoh, Garmin could be even "more" "exact" than 1s / km (or mi) by displaying decimals, such as 5:00.28/km. But ofc very few people would want that, because it doesn't give them any more useful information than 5:00/km.

By the same logic, Garmin doesn't think that 5:02/km (for example) gives any more useful infomation than 5:00/km, in terms of instant pace.

So really, all users are ok with Garmin rounding pace, it's just that they disagree whether it should be rounded to 1s or 5s.