Garmin pushed two distinct beta firmware builds for its Fenix 8 family within a single calendar day on October 30 — a concentration of releases unusual enough in the company’s Fenix beta history to signal something beyond routine iteration. Together, versions 24.13 and 24.14 cleared 28 bugs, with the most consequential fixes targeting failures that blocked the watch during active outdoor use: a crash whenever a user tapped the map page mid-activity, a Bluetooth heart rate broadcast that cut out after toggling connections, and a reboot that fired exactly when the watch should have been saving a completed workout.

Both builds shipped as automatic over-the-air downloads to participants in Garmin’s Beta Software Program. The double release arrives as the v24 development track — roughly two weeks old, having debuted with a feature-heavy initial build — enters an aggressive cleanup phase ahead of what Garmin’s historical patterns suggest will be a stable promotion in late November or early December, well within the holiday shopping window.

The builds cover the entire Fenix 8 family: the Fenix 8 AMOLED (43 mm, 47 mm, and 51 mm), Fenix 8 Solar (47 mm and 51 mm), Fenix 8 Pro (47 mm, 51 mm, and MicroLED), Enduro 3, Fenix E, Tactix 8 Solar, Tactix 8 AMOLED (47 mm and 51 mm), and Quatix 8. ECG and Dive capabilities remain disabled across all v24.x beta builds.

Version 24.13 Addresses Eighteen Bugs, Led by Map Crash and HR Broadcast Failure

The first of Thursday’s two builds, v24.13, replaces v24.12 with a changelog of 18 corrections and no new features.

The highest-impact fix addresses a crash that fired whenever a user selected the map page during an activity. For a navigation watch used by trail runners, hikers, and cyclists, this was a hard blocker: tapping the map mid-route caused an immediate crash rather than displaying position. A related fix resolved devices becoming completely unresponsive after extended USB connections, trapping users in a frozen update or sync state.

The heart rate broadcast failure carries significance for athletes who pair their Garmin to a cycling computer, rowing machine, or gym cardio equipment over Bluetooth. The bug caused HR transmission to stop whenever Bluetooth was toggled off — a routine connection-management step on watches juggling multiple Bluetooth devices — breaking HR data delivery to external equipment for the remainder of the session. This fix is paired with a correction for heart rate graphs that sometimes failed to populate in post-activity summaries, restoring accurate visual review of cardiovascular data for completed workouts.

Track runners benefit from the repair of occasional crashes during track run activities, which likely involved the watch’s lap-counting and GPS geometry logic in track mode. Audio quality improves with a fix for distorted alarm and notification tone playback.

Several more targeted issues also close in v24.13: a screen blackout when saving a point of interest, an incorrect menu opened by the “Display Settings” shortcut, streak alerts overriding step-goal alerts mid-workout, a non-functional magnifier in address search, unresponsive NTN “try again” buttons, move alerts sticking in the notification center after dismissal, a decimal picker appearing incorrectly when editing pack weight on unsupported devices, missing data fields on the “Iron Portal” watch face, inaccurate entry and exit points for individual and apnea dives, a grade-adjusted average pace field that failed to populate for trail runners, and coordinate display appearing incorrectly on map pages.

Full v24.13 changelog (18 items):

• Fixes “Display Settings” shortcut opening the wrong menu
• Fixes “Iron Portal” watch face missing some data fields
• Fixes map theme failing to change when requested
• Fixes average grade-adjusted pace field not populating
• Fixes coordinate information appearing incorrectly on map pages
• Fixes decimal picker displaying during pack weight editing when decimals are not supported
• Fixes device crashing when selecting the map page
• Fixes devices becoming unresponsive after extended USB connections
• Fixes distorted alarm and notification audio playback
• Fixes entry and exit points displaying inaccurately for individual dives and apnea dives
• Fixes heart rate broadcasting stopping after Bluetooth is disabled
• Fixes heart rate graphs sometimes not populating correctly in activity summaries
• Fixes move alert not being cleared from the notification center
• Fixes NTN “try again” screen buttons not responding
• Fixes occasional crashes during track run activities
• Fixes screen going black when saving a point of interest
• Fixes streak alerts replacing goal alerts during activities
• Fixes magnifier in address search not working

How Two Builds Reached Watches in a Single Day — and What That Cadence Signals

The mechanics of how Garmin delivers beta firmware to enrolled devices explain how a same-day double release is operationally possible. Beta participants receive updates through two paths: an automatic over-the-air push, which Garmin initiates from its servers and which installs when the watch syncs with the Garmin Connect app, and a manual pull via Settings → System → Software Update → Check for Updates on the watch itself.

Both v24.13 and v24.14 shipped via the OTA push path rather than manual-only delivery. That choice carries a quality signal: Garmin uses the automatic push route when it has sufficient internal confidence in a build’s stability to deploy it without requiring the user to opt in manually. Shipping two builds OTA in the same day suggests the company had both builds staged and validated before releasing either, rather than discovering issues in v24.13 post-release and scrambling an emergency follow-up.

OTA firmware delivery to wearables uses a delta-update approach — only the changed components of the firmware package travel over the connection, not a complete firmware image. This is why rapid successive builds are practical on a device with limited bandwidth and battery capacity: the second download (v24.14) is a patch on top of v24.13 rather than another full install.

The two-week-old v24 track debuted with dozens of changes including new features compared to the previous v23.xx stable baseline. Versions 24.13 and 24.14 have added 28 further corrections on top of that, all of them bug fixes. This pattern — a feature-heavy initial version followed by rapid, fix-only iterations — is characteristic of Garmin’s early-in-cycle cleanup behavior across prior beta tracks on the Fenix 8 platform, including v21, v22, and v23 cycles, each of which included similar stability iterations after the first feature-bearing release.

Version 24.14 Closes Ten More Bugs, Including Activity-Save Reboot and Swim Overcounting

Hours after v24.13, Garmin pushed v24.14 with ten additional fixes focused on activity save reliability, in-workout navigation stability, and sport-mode regressions.

The most significant fix addresses a full watch restart triggered by saving a completed activity. The moment of save — when the watch transitions from active recording to confirmed storage — is precisely when users expect feedback that their workout data is safely captured. An unexpected reboot at that moment creates genuine uncertainty: the screen goes dark and the watch restarts just as it should be confirming the save. The uncertainty is not trivial for athletes who rely on continuous training logs. A companion fix addresses the watch freezing or crashing during in-workout navigation and point-of-interest route calculation, completing coverage of the full workout-with-navigation lifecycle.

Swimmers using pool modes benefit from a fix that prevented an extra phantom swim length from appending to the total after stopping an activity. The bug could have inflated cumulative distance figures and made it appear a set had been completed when it had not. The fix is particularly relevant for athletes tracking specific distance targets in Garmin Connect.

A crash occurring immediately after a factory reset — specifically when users selected the “Learn the basics of your watch?” onboarding option — is also patched. While most relevant to new owners or users who reset their devices, crashes in first-run initialization flows can indicate broader state management fragility in device configuration code.

Audio and display corrections round out v24.14. Timer completion tones that failed to play when audio alerts were enabled — breaking a key feedback mechanism for interval training and countdowns — are restored. The music controls page now again shows song title and playback duration rather than displaying only transport controls with no track context. A solid blue screen that appeared when the display dimmed during “Free” meditation sessions is resolved. The snowboard activity profile’s data screen regains the ability to set a custom background color. An interface element — the “change search area” icon on prefecture searches — is disabled as an intentional behavior correction. A watch face data field clipped in Czech language layout is fixed.

Full v24.14 changelog (10 items):

• Disables “change search area” icon in prefecture search
• Fixes full blue screen appearing when display dims during “Free” meditation activities
• Fixes a watch face data field being clipped in Czech language settings
• Fixes an issue that could add an extra swim length after stopping an activity
• Fixes device freezing during in-workout navigation or route calculation via a point of interest
• Fixes device restarting when saving a completed activity
• Fixes crash occurring after factory reset when selecting “Learn the basics of your watch?”
• Fixes inability to set background color on the snowboard activity data screen
• Fixes song title and playback duration disappearing from the music controls page
• Fixes timer completion tones not sounding when audio alerts are enabled

ECG and Dive Stay Gated — Why Beta Builds Can’t Ship These Features

One standing caveat accompanies the v24.x beta cycle for all covered models: ECG and full Dive functionality remain disabled. The reason is procedural rather than technical. ECG on consumer smartwatches falls under FDA oversight as a Class II medical device feature; software versions that implement it must meet specific quality and documentation requirements under FDA clearance. Beta builds are not validated under that clearance framework, which means shipping ECG in an unvalidated beta would put it outside its cleared use context. The same logic applies to Dive functionality, which involves safety-relevant calculations including decompression limits — a domain where unvalidated beta code carries elevated risk.

Both features will return in a validated stable release once their implementations pass the separate qualification cycle required for that build.

Who Can Install These Builds and How to Get Them

These builds are available only to Fenix 8 family owners enrolled in Garmin’s Beta Software Program. Enrollment is free and takes roughly a minute: sign in to Garmin Connect (connect.garmin.com), click the watch icon in the top-right, select your device, and click “Join Beta Software program.” Once enrolled, builds arrive via the OTA push automatically when the watch syncs with Garmin Connect, though timing varies. Users can also pull the update manually: navigate to Settings → System → Software Update → Check for Updates on the watch.

Participants who prefer stable firmware over early bug access can leave the beta program from the same Garmin Connect device page and wait for the stable v24.x release. Based on Garmin’s established beta cadence for the Fenix 8 — typically 30 to 40 days between a beta build and the corresponding stable promotion — the stable v24.x release for non-beta Fenix 8 owners is likely to arrive in late November or early December 2026.

Frequently Asked Questions

How do I join Garmin’s Beta Software Program for the Fenix 8?

Sign in to Garmin Connect at connect.garmin.com, click the watch icon in the top-right corner, select your device from the list, and click “Join Beta Software program.” Beta builds will begin arriving via automatic OTA sync shortly after enrollment. You can leave the program the same way — from your device page in Garmin Connect — which will return you to stable firmware updates on Garmin’s standard release schedule.

Is it safe to install Garmin beta firmware on my Fenix 8?

Garmin beta builds are tested internally before release, but they carry a higher probability of containing bugs than stable releases — that is the trade-off of early access. The v24.13 and v24.14 builds address bugs that existed in v24.12, and v24.14 itself may have introduced others not yet discovered. Enrolled users report issues through the Garmin Beta Program forum, where Garmin engineers respond. If you depend on your Fenix 8 for navigation in remote terrain or as your primary fitness-tracking device, the conservative choice is to wait for the stable release. If you are specifically affected by one of the 28 bugs cleared in these builds — particularly the map-page crash, HR broadcast dropout, or activity-save reboot — the beta offers immediate bug fix access.

When will non-beta Fenix 8 owners receive the v24 firmware update?

Beta participants receive updates 30 to 40 days before the corresponding stable release reaches the general public. With v24.13 and v24.14 shipping on October 30, the stable v24.x release for all Fenix 8 owners is likely to arrive in late November or early December 2026 — positioning it to reach users who receive a Fenix 8 as a holiday gift or purchase one during seasonal sales. Garmin does not publish fixed timelines for stable promotions, but the company has historically accelerated the schedule when critical regressions affecting core functionality are cleared, which describes the map crash and HR dropout fixes in the current builds.

Why do ECG and Dive remain disabled across all Fenix 8 beta builds?

ECG on consumer smartwatches operates under FDA oversight as a Class II medical device feature. Beta firmware builds are not validated under the FDA clearance documentation framework, which means activating ECG in a beta build would place it outside its cleared use context. Dive functionality involves safety-relevant decompression calculations that carry similar validation requirements. Both features are gated until a stable build that has completed the separate qualification cycle required for those capabilities is released. They are present in the hardware across all covered Fenix 8 models; their gating is a software validation boundary, not a hardware limitation.