GAP isn't work with sw 20.16

GAP with SW 20.16 is not working. It's surprising that you've had information from testers since the beta version that GAP is not working, and you put the same error in the official version. Please fix it. I can understand that you don't put new features into older watches, but why is what used to work not working anymore..."

Top Replies

Garmin-Laurie 4 months ago in reply to gaterobs +0 verified

Hello. I am sorry to hear you are having this issue. I would love to help investigate this further. For this, I will reach out to you via Private Message to collect the details of this experience.
Garmin-Laurie 3 months ago in reply to Amaisa +1 verified

Update March 20, 2025:

Our engineers have indicated this should now be resolved with the latest software version 20.20 and later.
Jiří Svoboda 4 months ago in reply to dxbydy +4

I use GAP as a metric in trail running. In the past, the pace conversion was correct, but now the data is the same as when I'm running on the flat."

Jiří Svoboda said:
I use GAP as a metric in…
gaterobs 4 months ago in reply to druidh +4

druidh said:
it's perfectly possible that it worked in testing.

It's hard to say anything if there's no feedback from Garmin.

Users spend their time beta testing their software, and they can…
Garmin-Laurie 4 months ago in reply to gaterobs +4

Update February 26, 2025:

Our engineers are aware of a potential issue that may cause the GAP pace not calculate correctly. This is software related. So if you are experiencing this, the watch will not…

All Replies

0 dxbydy 4 months ago

Do you mean not working at all or just the random number generator i've always got using GAP?

One of todays mile split example: Average Pace 9.33, GAP Pace 9.23, Accent 2m, Decent 28m

I've never known it to give me any useful info.

0 Jiří Svoboda 4 months ago in reply to dxbydy

I use GAP as a metric in trail running. In the past, the pace conversion was correct, but now the data is the same as when I'm running on the flat."

Jiří Svoboda said:
I use GAP as a metric in trail running. In the past, the pace conversion was correct, but now the data is the same as when I'm running on the flat."

0 honza_81 4 months ago

That can't be true! They broke it during beta cycle and release it as final version. Garmin doesn't stop surprising me.

0 mparker91 4 months ago

also having this issue on my Enduro 2. GAP matches overall pace exactly

0 socorsu 4 months ago

hi you can try this DataFields, the values will be different from Garmin but should be reliable.

https://www.runningwithpower.com/grade-adjusted-pace

https://apps.garmin.com/de-DE/apps/5f650cee-0878-429d-964d-7ca30df1d7eb

I remove it recently, but will reinstall it to track this issue :-(

0 socorsu 4 months ago in reply to honza_81

i did not take care during beta, but you are right the issue were reported

First report --- Jan 20, 2025 ---

https://forums.garmin.com/beta-program/fenix-7-series/public-beta-reports/i/public-beta-20-xx/gap-and-pace-numbers-the-same-no-vo2max-estimated-number

Another one later --- Feb 9, 2025 ---

https://forums.garmin.com/beta-program/fenix-7-series/public-beta-reports/i/public-beta-20-xx/gap-pace-same-as-normal-pace

0 4830662 4 months ago

Same problem here on 20.16, I call garmin Support and they teel me that they don´t have ani report of that haha, but at the same time ask me to send it all the threads of the forum with the problem. Joking

0 socorsu 4 months ago in reply to 4830662

i have the explanation, but you are not ready for it.

Once upon time, Gamrin Laurie explain me that Beta Phase "Ticket" are not shared with Public "Ticket", so Garmin needs to identify and document issue again after Public release !!!

Enjoy :-)

0 honza_81 4 months ago in reply to socorsu

And I still can't get over it. It's such an incomprehensible thing to me that it completely defeats the point of beta testing!

0 druidh 4 months ago

It's working for some folk, if not others. That being the case, it's perfectly possible that it worked in testing.