Garmin Forerunner 570 & 970 Public Beta 16.37: Headphone and HIIT Crash Fixes, Better Course Planner Performance

Table of Contents

1. Key Highlights:
2. Introduction
3. What Public Beta Version 16.37 Contains
4. Why the Headphone Crash Fix Matters
5. HIIT Activity Crash: What Happened and Why This Fix Is Important
6. Course Planner Improvements — Real-World Effects
7. Fixes to Goal Alerts, Translations and Other Minor Bugs
8. How Garmin Distributes Firmware: Beta vs Stable and What v16.xx Means
9. How to Install Public Beta 16.37 — Step-by-Step and Safety Checklist
10. Who Should Install the Public Beta — A Practical Decision
11. Practical Tips: Avoiding Update-Related Problems
12. How These Fixes Translate to Everyday Training
13. What This Release Suggests About Garmin’s Current Priorities
14. Real-World Scenarios: How Athletes Will Use These Fixes
15. How to Report Bugs Effectively to Help Garmin
16. Compatibility and Broader Ecosystem Notes
17. What to Watch for After Installing 16.37
18. FAQ

Key Highlights:

• Garmin has released Public Beta Version 16.37 for the Forerunner 570 and Forerunner 970, addressing several stability issues including crashes when using headphones and during HIIT activities.
• The update improves course planner performance, fixes goal alert behavior and other minor bugs, and delivers updated translations.
• Users can trigger the update manually via the watch (Menu → Settings → System → Software Update → Check for Updates) or enroll through Garmin’s Beta Program; weigh the benefits of early fixes against the risks of running beta software.

Introduction

A small firmware revision can mean the difference between a flawless training session and lost workout data. Garmin’s latest public beta for the Forerunner 570 and Forerunner 970 — Public Beta Version 16.37 — targets several stability pain points reported by users over recent weeks. Rather than introducing headline-grabbing new features, this release focuses on reliability: eliminating crashes tied to Bluetooth headphones and the HIIT activity mode, restoring consistent goal alerts, and smoothing performance in the built-in course planner.

That practical approach carries immediate value for athletes who depend on their watch for interval training, guided workouts, and navigation. The update arrives after a prior stable release more than a month ago, and Garmin’s choice to continue v16.xx development through public beta signals a push to tighten the platform’s day-to-day stability before rolling out further major revisions. The details below explain what changed, why it matters, and how athletes and everyday users should approach installation and testing.

What Public Beta Version 16.37 Contains

Garmin’s changelog for the jump between v16.28 and v16.37 lists focused fixes rather than new capabilities. The update notes:

• Fixes a potential crash when using headphones.
• Fixes a potential crash when using the HIIT activity.
• Fixes an issue where only one goal alert is shown per day.
• Fixes other minor bugs.
• Improves course planner performance.
• Updates translations.

Each line in the log points to an area where user experience could be interrupted. The headphone and HIIT crash fixes are the most consequential for athletes who perform interval sessions with earbuds or rely on coached HIIT workouts. The course planner changes will matter to users who create complex routes or navigate unfamiliar terrain. Correct translations and additional minor fixes round out an incremental but pragmatic release.

Most users will notice no new screens, menus, or major UI changes. Instead, the update is about fewer interruptions and more predictable behavior across commonly used features.

Why the Headphone Crash Fix Matters

Bluetooth headphones are now standard equipment for many runners, cyclists, and gym-goers. Watches that play music, stream audio prompts, or control playback must handle audio streaming while concurrently tracking sensors, GPS signals, and timers. A crash triggered by a headphone pair may look like a brief freeze on the display, a sudden reboot, or an outright loss of an activity file — all of which undermine training and safety.

What the fix likely addresses

• Race conditions between the audio stack and activity tracking routines.
• Unexpected Bluetooth disconnects or malformed metadata from certain headphone firmware.
• Concurrent CPU bursts when decoding audio or handling playback controls during an active exercise session.

Symptoms users reported (generalized)

• Watch restarts when a headphone connects or when playback starts.
• Music continues on the headphone but the watch is unresponsive.
• An active workout stops recording, and the file fails to save.

Practical implications

• For interval-heavy sessions, losing data from a single workout can obscure progress tracking and skew training load calculations.
• Reboots mid-activity can also erase heart rate, GPS, and lap data that athletes rely on for pacing and analysis.
• Some users pair multiple devices (phone + headphones) and rely on the watch to act as the primary media controller; instability there affects the whole ecosystem.

Workarounds before installing the beta

• Avoid pairing headphones during structured activities until the update is applied.
• Use the watch’s vibration/tone alerts instead of audio prompts.
• Keep headphones firmware up to date; some interaction problems originate in the earbud rather than the watch.
• If a crash occurs, power-cycle the watch, confirm the activity file saved to Garmin Connect, and export any partial data for backup when possible.

The headphone crash fix restores a critical interaction pathway. For anyone pairing Bluetooth audio devices with their Forerunner during workouts, the update should reduce unexpected interruptions.

HIIT Activity Crash: What Happened and Why This Fix Is Important

High-intensity interval training (HIIT) is a configuration where the watch must rapidly switch between work and rest intervals, trigger alerts, log heart-rate zones, and pace both time and effort. The watch handles numerous timers and event-driven tasks during these sessions, and a failure in the HIIT activity handler can result in a crash that terminates the workout.

How a HIIT crash affects training

• Loss of interval timestamps, heart rate history, and distance data.
• Inability to resume the same structured session, requiring manual reconstruction of the workout.
• Frustration for users relying on guided workouts or for athletes tracking interval compliance.

What the patch addresses

• Race conditions in the HIIT timer or interval transition logic.
• Exceptions thrown by secondary features invoked during intervals (audio prompts, screen transitions, automatic lap markers).
• Corner cases where unexpected user input (pause/resume) during a rapid interval change triggered an unhandled state.

Best practices for interval training before updating

• Use a manual timer outside the watch to ensure interval pacing is maintained if you suspect instability.
• Export key workouts immediately after completion to prevent data loss.
• Consider using a simple “Run” or “Indoor Run” profile with manual lap marking as a temporary workaround.

After 16.37, athletes should find their HIIT sessions complete and intact, with interval markers, heart-rate traces, and elapsed times preserved. That restores trust in the watch as a training tool rather than a liability during intense sessions.

Course Planner Improvements — Real-World Effects

Garmin’s course planner lets users create, edit and follow routes directly from the watch or via Garmin Connect. Improvements to course planner performance on the Forerunner 570 and 970 will benefit users who create multi-kilometer routes, navigate unfamiliar roads, or structure long rides and runs with exacting turn-by-turn guidance.

What to expect from improved course planner performance

• Faster load times for complex routes and GPX files.
• Quicker recalculation when you deviate from a route.
• Smoother handling of multiple waypoints and route segments.
• Lower CPU and memory overhead during navigation, reducing the chance of slowdowns during long activities.

Practical examples

• A road cyclist setting a 120 km loop with multiple turn points will see quicker route validation and fewer pauses when the watch must recompute a new path after an unscheduled detour.
• Trail runners who import GPX files with detailed elevation changes should notice speedier rendering of the route and more responsive notifications for upcoming turns.
• Triathletes using the watch for bike-course navigation between swim, transition and run legs will benefit from predictable route behavior across stages.

Course planner performance ties directly into the utility of the watch for navigation. Improvements reduce the friction of route creation and increase the reliability of turn-by-turn directions during crucial moments.

Fixes to Goal Alerts, Translations and Other Minor Bugs

Small bugs can produce outsized frustration. One reported issue caused the watch to show only one goal alert per day. Goal alerts — move reminders, step targets, calorie notifications — form the backbone of daily motivation and behavior nudges. Reinstituting the expected alert cadence means users receive consistent feedback on progress toward daily objectives.

Updated translations matter beyond cosmetic concerns. Accurate, localized copy removes ambiguity and reduces user error when interpreting on-device prompts, especially in critical contexts such as system warnings or workout cues. Other minor bug fixes, though unspecified individually, generally improve UI responsiveness, reduce rare freezes, and stabilize background services.

Cumulatively, these fixes polish the everyday experience of the watch. They reduce the small, repetitive annoyances that erode user confidence long before a headline bug appears.

How Garmin Distributes Firmware: Beta vs Stable and What v16.xx Means

Garmin typically issues two types of software releases: stable updates that reach the broad consumer base after testing, and beta updates distributed to enrolled testers. Beta programs allow Garmin to expose changes to a controlled audience, collect crash reports, and iterate quickly.

What happened in this cycle

• Garmin released a stable update to the Forerunner 570/970 more than a month prior.
• Instead of immediately proceeding to a major new stable revision, Garmin continued v16.xx development in the Beta Program.
• Public Beta Version 16.37 was rolled out to eligible units, meaning the company considered these fixes ready for wider testing but not yet part of the general stable channel.

Understanding versioning

• The “v16.xx” notation signals a series of revisions within the same major release generation. Incremental point releases (e.g., v16.28 → v16.37) typically include bug fixes, performance improvements, and translation updates rather than feature overhauls that would warrant a jump to v17.0.
• Public beta indicates the release has moved beyond closed internal testing but remains a pre-release candidate until it is promoted to stable.

How to obtain a beta update

• Enroll in Garmin’s Beta Program via Garmin’s official beta portal and register the device you want to test.
• Beta builds generally arrive over-the-air (OTA) to enrolled devices. If a device doesn’t receive an automatic prompt, manually check for updates on the watch: Menu → Settings → System → Software Update → Check for Updates.
• Some users prefer to download beta images via Garmin Express on a PC, though the most straightforward path is OTA.

Why Garmin uses public betas

• Field-testing across a wide range of hardware configurations and paired accessories (phones, headphones, sensors) surfaces edge-case failures that internal labs do not.
• Rapid telemetry and user feedback from real-world conditions speeds identification and repair of regressions.

How to Install Public Beta 16.37 — Step-by-Step and Safety Checklist

Installing a public beta requires caution. Follow these steps and checks to reduce the likelihood of trouble.

Pre-install checklist

• Charge the watch to at least 50%, preferably to 80–100%. Firmware changes can fail if power drops mid-install.
• Sync your watch with Garmin Connect to ensure recent activities and settings are backed up.
• Note any third-party data or settings that matter (custom sensors, structured workouts, watch faces).
• Have your phone and Wi-Fi available if your watch downloads updates via the phone’s connection or a paired Wi-Fi network.

Installation options

1. Manual update on the watch:
   • From the watch, go to Menu → Settings → System → Software Update → Check for Updates.
   • If Public Beta Version 16.37 is available, follow on-screen prompts to download and install.
   • Do not interrupt the update; let the watch complete its reboot cycle.
2. via Garmin Beta Program:
   • Enroll on Garmin’s beta website using your Garmin account and accept terms.
   • Register the applicable Forerunner device to receive OTA beta builds automatically.
   • Wait for the notification on your watch, or check manually as above.
3. Garmin Connect / Garmin Express:
   • Occasionally, beta channels require explicit distribution through Garmin Express. Confirm instructions on the beta portal.

Post-install steps

• Pair headphones and other sensors. Verify basic functions: heart rate monitoring, GPS lock, music playback, and notifications.
• Run a short test workout to confirm there are no immediate crashes or stability issues.
• If you rely on guided workouts for a key training session soon, delay installing the beta until you’ve validated stability with a few short sessions.

Rollback considerations

• Rolling back from a beta to the stable channel may require reinstalling the stable firmware via Garmin Express or waiting for Garmin to distribute a stable replacement. Back up settings and exported activities before moving between channels.
• If severe instability occurs, contact Garmin Support and provide detailed reproduction steps, device logs if requested, and your firmware version.

Who Should Install the Public Beta — A Practical Decision

Installing a public beta is a balance between wanting fixes now and maintaining absolute stability. Consider the following profiles:

Good candidates for the beta

• Tech-savvy users comfortable diagnosing issues and reporting bugs.
• Users experiencing the exact issues the beta addresses (headphone crashes, HIIT crashes) and willing to test the fix.
• Enthusiasts who want early access to improvements and can tolerate occasional regressions.

Users who should wait

• Athletes preparing for an imminent race, event, or competition. Race day is not the time to run pre-release firmware.
• Professionals who rely on their watch for guaranteed data capture and who cannot accept even a minor risk of data loss.
• Users with limited technical knowledge who prefer a stable, support-backed experience.

Risk mitigation

• Delay the update until after a key event.
• Install the beta on a secondary device if you own multiple wearables.
• Read user feedback from initial beta adopters on forums and social platforms for early signals about stability.

Practical Tips: Avoiding Update-Related Problems

A few habits reduce the chance that an update will disrupt training.

Timing and environment

• Update at home when you can monitor the device and re-pair accessories if necessary.
• Avoid updates immediately before long outdoor workouts, flights, or races.

Connectivity and power

• Use a trusted Wi-Fi network if your watch downloads firmware directly.
• Keep the watch on charger during large firmware installations.
• Keep the phone close if the update is routed via Garmin Connect.

Pairing and accessories

• After update, re-pair and test headphones, external HR straps, cadence sensors, and any third-party watch faces.
• Check that music playback and voice prompts function as expected.

Data hygiene

• Sync Garmin Connect immediately post-update and verify that past workouts are intact.
• Export critical training files (FIT or TCX) for archival storage if you are concerned about data loss.

What to do if something goes wrong

• Reboot the watch and re-run the update check.
• Clear the Bluetooth cache on the phone and re-pair devices.
• If the watch becomes unstable, contact Garmin Support with time-stamped logs and detailed reproduction steps. Beta participants typically have to provide more diagnostic information.

How These Fixes Translate to Everyday Training

The practical benefits of these targeted fixes show up in everyday training routines.

Interval sessions

• Stable HIIT mode ensures that a 10 x (30/30) interval workout will be recorded without missing intervals or losing session logs. That feeds accurate training load and recovery recommendations into training plans.

Long routes and navigation

• Quicker course planner performance reduces pre-ride preparation time and the annoyance of watching a slow-loading route screen. Recalculation that keeps pace with your deviation from a planned path keeps navigation helpful rather than distracting.

Motivation and behavior

• Restored goal alerts deliver consistent nudges; step and move notifications are the small, repeated interactions that sustain long-term behavior change.

Hands-free audio

• Fixing headphone crashes means runners and cyclists who rely on audio coaching or motivational playlists can run without the fear of the watch rebooting mid-interval or mid-loop.

Combined, these fixes reduce cognitive load. Instead of watching for software quirks, users can concentrate on pace, technique and recovery.

What This Release Suggests About Garmin’s Current Priorities

A sequence of small, stability-focused beta updates reflects a development approach that prioritizes reliability over feature expansion in the short term. Garmin’s continued work on the v16.xx stream shows attention to:

• Addressing regression bugs that affect multiple device models.
• Strengthening the foundation before introducing larger changes.
• Using public beta distribution to test fixes across a variety of real-world pairings and usage patterns.

For users, this indicates that Garmin listens to field reports and opts for iterative refinement. For the broader smartwatch ecosystem, it demonstrates a balance between introducing capabilities and maintaining the baseline usability that athletes expect.

Real-World Scenarios: How Athletes Will Use These Fixes

Narrative examples show how small changes matter in practice.

Scenario 1 — The interval-minded runner Emma trains six days a week and relies on HIIT sessions to build VO2 max. Last month she experienced a sudden device reboot during a crucial ladder workout, losing heart-rate and interval data. After installing Public Beta 16.37, Emma runs a 30-minute HIIT session with consistent interval markers, accurate HR zones and no unexpected reboots. She uploads the workout, and the training load metrics correctly reflect the effort.

Scenario 2 — The cyclist on a long tour Miguel maps a 120 km route with complex turns and waypoints. Previously, the watch took several minutes to render the full route and occasionally lagged when recalculating off-route. With the course planner improvements, the route loads rapidly and recalculates smoothly when he needs a detour. The watch’s navigation becomes a reliable partner rather than a source of frustration.

Scenario 3 — The runner who trains with audio cues Nia uses Bluetooth earbuds and a coaching app to get audio cues during tempo runs. Before the update, connectivity sometimes caused the watch to stall mid-run. After applying the beta, Nia can start playback without the device crashing, and the workout files save correctly to Garmin Connect for later analysis.

These scenarios highlight the functional impact: clearer data, smoother navigation and uninterrupted audio — all practical improvements that enhance training fidelity.

How to Report Bugs Effectively to Help Garmin

If you encounter a reproducible problem while running the beta, quality bug reports help Garmin diagnose and fix issues faster. A useful report contains:

• Device model and serial number (where applicable).
• Exact firmware version (e.g., v16.37).
• Steps to reproduce the issue in numbered sequence.
• Frequency: always, often, sometimes, rare.
• Expected behavior and actual behavior.
• Time and date of the occurrence and any relevant environmental factors (indoor vs outdoor, paired accessories).
• Screenshots, video captures, or exported FIT files showing the problem.
• Whether the device was paired with a phone and the phone model and OS version.
• Paired accessories: headphones, sensors and their firmware versions.

Submit this information via the Garmin Beta Program feedback channels or official support. Logs gathered by the device are often invaluable—follow instructions from Garmin when they request device logs to attach to your case.

Compatibility and Broader Ecosystem Notes

Public Beta 16.37 specifically targets the Forerunner 570 and 970. While some fixes may also appear in betas for other Garmin models, distribution is device-specific. Users of other Forerunner series or Garmin watches should monitor their own firmware channels for similar updates.

Third-party apps and complications

• Third-party apps that integrate with Garmin’s platform occasionally need updates to align with firmware changes. If a companion app misbehaves after a firmware update, check for app updates on the phone and confirm compatibility with the new firmware build.

Accessory firmware

• When troubleshooting headphone-related issues, check for firmware updates for earbuds, chest straps, and cycling power meters. A chain is only as strong as its weakest link; cross-device incompatibilities often surface as crashes.

Warranty and support

• Running public beta software does not void hardware warranties in most cases, but it may complicate support when issues are tied specifically to pre-release firmware. Keep records of any changes you make and be prepared to provide them if you contact support.

What to Watch for After Installing 16.37

Monitor these elements in the days following installation:

• Activity integrity: Confirm that a variety of workouts (HIIT, runs, rides) save completely and include accurate heart-rate and GPS traces.
• Headphone behavior: Test pairing, playback, and media control during active and paused workouts.
• Course navigation: Load routes of various sizes and traverse a short segment to observe recalculation responsiveness.
• General stability: Note any freezes, reboots, or abnormal battery drain.

If you detect new regressions, document them carefully and report them through the Beta Program channels. Early, specific reports reduce the time between identification and fix.

FAQ

Q: How do I trigger the update manually on my Forerunner 570 or 970? A: On the watch, go to Menu → Settings → System → Software Update → Check for Updates. If Public Beta 16.37 is available for your device and you are enrolled in the Beta Program, the watch should offer to download and install it.

Q: How can I join Garmin’s Beta Program to receive this update? A: Sign in to Garmin’s official Beta Program portal with your Garmin account. Enroll the device you wish to test and accept the beta terms. Once enrolled, beta builds are generally provided over-the-air to your watch.

Q: Will this update be pushed to all devices automatically? A: Public betas are typically distributed to enrolled testers only. Stable releases are rolled out to the broader user base after sufficient testing. If you are not enrolled, check the watch manually or wait for the stable release.

Q: What happens if the watch crashes during an activity after installing the beta? A: Reboot the watch and check Garmin Connect for whether the activity saved. If the file is incomplete, export any available data for backup. Report the crash through the beta feedback channels, including steps to reproduce and any available logs or FIT files.

Q: Can I revert from the beta to the previous stable firmware? A: Reverting may require reinstalling the stable firmware via Garmin Express or waiting for Garmin to push the stable build. Back up settings and export any critical workouts before moving between channels. Contact Garmin Support for assistance with rollback if needed.

Q: Should I install Public Beta 16.37 before an important race? A: No. Avoid pre-release firmware before races or any event where guaranteed data capture is essential. Install and validate the update well in advance of competitions.

Q: Will this fix battery drain issues I’ve seen after previous updates? A: The changelog for v16.37 does not specifically mention battery optimizations. If you experience new battery problems after the update, report them with detailed usage patterns. Garmin may address such issues in subsequent builds.

Q: Which issues are fixed by this update? A: The update addresses a potential crash when using headphones, a potential crash when using the HIIT activity, a goal alert issue where only one alert was shown per day, other minor bugs, course planner performance, and updated translations.

Q: Does Public Beta 16.37 affect other Forerunner models? A: This release was announced for the Forerunner 570 and 970. Similar fixes may be released for other models on their own update schedules.

Q: How can I provide the most helpful feedback if I encounter a bug? A: Provide device model, firmware version, exact reproduction steps, frequency, screenshots or video, timestamps, paired accessories and their firmware versions, and any exported FIT files. This information accelerates triage and fixes.

Q: Will fixing headphone crashes fix all Bluetooth audio issues? A: The update addresses specific crash conditions causing the watch to reboot or freeze when using headphones. Some Bluetooth audio problems can originate with the headphone firmware or the phone; keep all devices updated and check compatibility if problems persist.

Q: What is the best way to validate the update after installation? A: Run a short HIIT session, a GPS run or ride with audio prompts enabled, and navigate a short pre-planned route. Verify that activities save, that audio and media controls work, and that navigation recalculates smoothly when you go off-route.

Q: How quickly should I expect the stable channel to pick up these fixes? A: Timing varies; Garmin promotes public beta fixes to stable channels after sufficient testing. The cadence depends on the volume of beta feedback, bug severity, and the company’s release schedule.

Q: Will installing the beta affect my training history? A: Installing firmware does not delete historical data. Sync the watch with Garmin Connect before and after the update to ensure all files are backed up. Export critical workouts if you are concerned about data integrity.

Q: Are translations updated for all supported languages? A: The update includes translation updates, though the changelog does not list specific languages. Users in localized regions should verify that on-device text reads correctly and report any remaining translation errors.

Public Beta Version 16.37 represents a focused effort to restore reliability across features many athletes rely on daily: audio playback, HIIT tracking, navigation and daily goal alerts. Users who experience the addressed issues will find this update particularly meaningful. Those who prioritize absolute stability should test the beta in low-stakes conditions and await the stable channel if preparations for competition are imminent. Carefully applied, the update reduces interruptions, preserves training data and makes the Forerunner 570 and 970 more dependable partners for sport and fitness.