Version 12:38: What fixes and improvements?

Hello everyone, I saw that firmware version 12.38 was recently released. However, the updates or fixes included are not specified.

I noticed that the beta version has reached 13.24, which is significantly ahead of this 12.38. I was wondering what the purpose of an update is if it still lags so far behind the beta versions, and what changes have actually been made.

Top Replies

6805874-Micha 4 months ago +2 suggested

forums.garmin.com/.../fenix-8-system-software-12-38
6805874-Micha 4 months ago in reply to Ludovico84 +2

So when you click there you should see they fixed a GPS issue
8299722 4 months ago +1

I was noticing longer GPS lock times in the last week. The 12.38 brought back a fast lock. This seems more of a “hotfix” to the 12.X firmware iteration while the 13.X is polished up on the beta channel…

All Replies

0 6805874-Micha 4 months ago

forums.garmin.com/.../fenix-8-system-software-12-38

0 Ludovico84 4 months ago in reply to 6805874-Micha

So, where would be the detailed description of the improvements?

0 6805874-Micha 4 months ago in reply to Ludovico84

So when you click there you should see they fixed a GPS issue

0 Ludovico84 4 months ago in reply to 6805874-Micha

I prefer to wait if the update is for a single issue. In the beta versions they added and fixed many more things. I hope the official version comes out soon.

0 8299722 4 months ago

I was noticing longer GPS lock times in the last week. The 12.38 brought back a fast lock. This seems more of a “hotfix” to the 12.X firmware iteration while the 13.X is polished up on the beta channel.

0 iba55 4 months ago in reply to 6805874-Micha

This link is for Fenix 8, not for Enduro 3. Is correct?

0 6805874-Micha 4 months ago in reply to iba55

That's correct. However I guess the changes are the same

0 gerzson 4 months ago

One thing that was fixed seem to be this: https://forums.garmin.com/outdoor-recreation/outdoor-recreation/f/enduro-3/387182/overnight-hrv-avg-calculation-error. At least for me on 12.35 the issue was there. On 12.38 the calculated avg. is more in line with the graph.