Garmin Forerunner 570 and 970 Beta v16.28: Custom Golf Targets, Cycling and Ski Fixes, and Translation Updates

Table of Contents

1. Key Highlights
2. Introduction
3. What v16.28 Introduces: Feature-by-feature breakdown
4. Why saved custom golf targets matter to golfers
5. Preserving structured repeats: why interval training becomes less brittle
6. How the Garmin Coach cycling workout load fix affects cyclists
7. Backcountry Ski summary fix: why max speed and mileage return matters
8. Translation updates and global usability
9. How to download and install v16.28
10. Best practices and precautions for beta firmware users
11. Risk assessment: possible side effects and how to mitigate them
12. How v16.28 fits in Garmin’s 16.xx beta cycle and update history
13. Real-world scenarios: how these fixes change outcomes for athletes
14. Community response and the role of Garmin’s forums
15. How these fixes affect data-driven coaching and analytics
16. Comparisons: how this update positions Garmin among competitors
17. Predicting the public release timeline and what to expect next
18. How to provide useful feedback as a beta tester
19. The value of incremental updates over feature-laden releases
20. What this update signals about Garmin’s product priorities
21. Troubleshooting common issues after updating
22. Long-term training implications: why accuracy and persistence matter
23. Tips for athletes who depend on watch data for racing or safety
24. The business and product management perspective
25. Final observations on v16.28’s value proposition
26. FAQ

Key Highlights

• Garmin has released beta firmware v16.28 for the Forerunner 570 and Forerunner 970, introducing saved custom golf course targets, preserved structured-repeat settings between interval sessions, fixes to Garmin Coach cycling workout loading, and refreshed translations.
• The Forerunner 970 receives an additional Backcountry Ski bug fix restoring maximum speed and mileage to post-activity summaries; the update is available through the watch Software Update path for enrolled beta users.

Introduction

Garmin continues incremental testing on its flagship Forerunner wearables. The latest public beta, version 16.28, threads new small-but-practical features with targeted bug repairs aimed at athletes who depend on precise activity data. The headline additions — saved custom golf targets and persistent structured-repeat changes — respond to everyday frustrations that crop up during multi-sport training and recreational play. Repairs to Garmin Coach, cycling workouts, and backcountry ski summaries restore data fidelity for performance analysis. These changes arrive as part of the broader 16.xx beta cycle, and they reflect a pattern: Garmin refining usability and data integrity rather than introducing sweeping new hardware features.

The rest of this article explains each change, why it matters to users, how to install the beta safely, the risks and best practices for testing pre-release firmware, and what the update signals about Garmin’s development priorities going forward.

What v16.28 Introduces: Feature-by-feature breakdown

Version 16.28 consolidates several targeted improvements and bug fixes for the Forerunner 570 and Forerunner 970. The public notes describe over 20 items in the changelog, but five changes are new to this release cycle:

• Saved custom targets on golf courses: When users set custom targets (for example, preferred landing zones or pin locations), those targets persist on the course for future rounds.
• Persisted structured repeats for interval workouts: Adjustments made to structured-repeat elements remain saved so the next interval session starts with the same modified settings.
• Garmin Coach cycling workout loading fix: The issue causing the wrong Garmin Coach cycling workout to load has been resolved.
• Translation updates: Localization and translation strings on the Forerunner 570 and 970 have been updated.
• Backcountry Ski post-activity data restored (Forerunner 970 only): Maximum speed and total mileage now show correctly on the activity summary page after Backcountry Ski workouts.

These items reflect an emphasis on user workflow continuity — keeping user-configured settings intact across sessions — and on restoring accurate activity metrics, which are essential for training evaluation and safety.

Why saved custom golf targets matter to golfers

Golfers using GPS-enabled watches treat each hole like a small, repeatable experiment. Course layouts are fixed, but conditions and strategy change hole-to-hole and round-to-round. Being able to save a custom target transforms the watch from a reactive distance tool into a lightweight course-management aid.

How this plays out in practice:

• Pin placement tracking: If a player sets a custom target for a particular pin location on a par 3 or a reachable par 5, that saved target speeds up club selection on subsequent visits to the same hole. Instead of re-measuring, the golfer gains immediate reference data from the watch.
• Hazard strategy: Players can mark landing zones to avoid hazards and reuse those targets when wind or course setup repeats.
• Coaching and practice: Coaches working with swing mechanics can mark targets representing optimal approach zones and use the saved targets across practice sessions to assess consistency.

Before v16.28, some users needed to re-enter targets each round or lost custom markers between sessions. That friction cost time and introduced opportunities for human error. Saving custom targets removes those steps and ensures the watch reflects an evolving plan across a season.

Preserving structured repeats: why interval training becomes less brittle

Structured repeats form the backbone of interval training sessions: warm-up, repeated efforts at specific power, pace, or cadence, rest intervals, and cool-down. Athletes file small modifications during a workout all the time — adjusting recovery length, increasing the number of repeats, or tweaking target intensity based on perceived exertion.

With v16.28, changes made to structured repeats are now preserved for the next interval session. The practical consequences:

• Faster session setup: Athletes who progressively increase repetitions or modify repeat lengths during training no longer have to reconfigure the same changes before their next interval session.
• Training consistency: Coaches using repeated weekly interval templates for athletes will find it easier to maintain an athlete’s incremental progression without manually re-entering mid-session adjustments.
• Reduced errors: Manual re-entry invites mistakes — a wrong repetition count or an incorrectly set recovery value can skew an entire workout. Persisted settings reduce that risk.

For triathletes and runners who chain multiple structured workouts across a training block, saved repeats shave minutes off warm-up routines and promote adherence to planned progressions.

How the Garmin Coach cycling workout load fix affects cyclists

Garmin Coach supplies adaptive training plans and individual workouts tailored to goals and recent performance. When the platform delivers the wrong cycling workout to a watch, the mismatch can undermine a session or require on-the-fly adjustments that defeat the purpose of coached sessions.

Restoring the correct Garmin Coach cycling workout addresses multiple problems:

• Training fidelity: Riders complete the intended effort profile, ensuring progression based on the coach’s algorithm.
• Safety and pacing: Incorrect workouts can cause over- or under-prescribing of intensity, leading to fatigue or missed stimulus.
• Data continuity: Correct workout logs ensure training analytics, fatigue modeling, and adaptive plan adjustments (which rely on accurate historical workouts) remain valid.

Cyclists using power meters and head units that sync with the watch depend on precise workout instructions. This fix reduces the friction between plan and execution.

Backcountry Ski summary fix: why max speed and mileage return matters

Backcountry skiing is an activity where metrics carry utility beyond performance analysis. Maximum speed can indicate risk-taking behavior on descents, while mileage and elevation metrics help reconstruct routes post-tour for safety review or for insurance/incident reporting. Losing maximum speed and mileage from the post-activity summary complicates debriefs and erodes trust in recorded metrics.

Restoring these values on the Forerunner 970 accomplishes:

• Better session review: Athletes and guides can review speed traces and total distance to evaluate route choice and efficiency.
• Safety records: Credible logs assist in incident analysis and provide clear records of activity extent.
• Data consistency: Third-party apps that ingest Garmin summaries expect certain fields; missing values create gaps in downstream analytics.

For backcountry skiers who rely on the watch as the primary tracking device during remote tours, preserving these metrics improves both everyday usefulness and longer-term record keeping.

Translation updates and global usability

Translation changes may seem minor compared to activity fixes, but accurate localization plays a significant role in usability and in reducing errors caused by misinterpreted menu items or prompts.

Key impacts:

• Clear instructions reduce setup mistakes for non-English users.
• Better translations improve adoption in international markets where Garmin competes heavily.
• Localization updates are particularly relevant in sport-specific pages where terminology must remain precise (e.g., "structured repeats" vs. "intervals" or course-specific golf prompts).

Small translation improvements ripple through user support, forum troubleshooting, and community adoption.

How to download and install v16.28

Garmin makes beta firmware available through its community beta program for enrolled users. For devices enrolled in the beta testing track or those receiving the build via over-the-air distribution, follow this path on the watch to trigger a check:

Main menu > Settings > System > Software Update > Check For Updates

Best practices for installing:

• Charge the device to at least 50% or place it on the charger to prevent power loss during installation.
• Back up workout data by syncing the watch to Garmin Connect prior to updating.
• Install beta updates when you have a clear window to test — preferably not immediately before a critical race or multi-day expedition.
• If you rely on third-party sensors or apps, sync them and ensure pairing is intact after the update.

If you aren’t enrolled in the beta program but want access, visit Garmin’s official forums and join the beta program thread for your model. Participation often requires agreeing to test terms and providing feedback through forum threads or internal reporting channels.

Best practices and precautions for beta firmware users

Beta firmware can provide early access to bug fixes and enhanced functionality, but it carries caveats. Professional athletes, coaches, and guides should weigh the benefit against potential instability.

Recommended checklist before installing:

• Schedule the update outside critical training cycles or events.
• Create backups and ensure Garmin Connect has synced all recent activities and settings.
• Read the changelog carefully to understand fixed and known issues.
• Keep a recovery plan: record serial numbers, access to Garmin support, and steps to revert to a public build if needed. Garmin sometimes requires device support to re-flash stable firmware.
• Test essential functions immediately after update: GPS recording, sensor connectivity (HR straps, power meters), notification behavior, and battery life under a representative activity.
• Report bugs promptly and clearly on the Garmin forum thread with timestamps, activity files (FIT files), and steps to reproduce the issue.

Beta testers should treat their role as part of Garmin’s quality assurance: provide concise reproduction steps, attach logs or activity files, and test across multiple scenarios to accelerate fixes.

Risk assessment: possible side effects and how to mitigate them

Potential issues with beta firmware include:

• Data loss or corrupted activity files.
• Reduced battery life due to inefficient firmware processes.
• Connectivity problems with sensors, headphones, or head units.
• Regression of previously working features.

Mitigation steps:

• Keep sufficient battery and avoid updating immediately before extended trips.
• Sync activities to Garmin Connect Cloud and download local copies of crucial FIT files.
• Pair critical sensors and run a short test activity to confirm operation before a full workout.
• If encountering severe issues, document them and contact Garmin support; restore to stable firmware may require technician intervention.

Professional users should maintain a secondary device or backup logging method when experimenting with beta builds.

How v16.28 fits in Garmin’s 16.xx beta cycle and update history

The 16.xx cycle has centered on iterative stability improvements and small feature rollouts across multiple Forerunner models. Previous releases — such as beta 16.17 — introduced a range of bug fixes. The pattern shows Garmin focusing on real-world pain points raised by users: data accuracy, workout playback fidelity, and workflow persistence.

Why this matters:

• Incremental updates reduce the chance of introducing systemic regressions compared with large feature pushes.
• Concentrating on usability fixes aligns with the demands of athletes who require consistent day-to-day performance from their devices.
• The volume of early-stage fixes suggests Garmin is responding directly to community bug reports and telemetry collected from beta participants.

Expect subsequent 16.xx updates to continue this trend: resolving fragmentation across devices, fine-tuning sensor behavior, and addressing edge-case activity types like backcountry skiing or golf-specific workflows.

Real-world scenarios: how these fixes change outcomes for athletes

Concrete examples illustrate why these modest updates matter.

Case 1: A competitive amateur golfer preparing for a local qualifier

• Before v16.28: The golfer marks a preferred layup zone on the 3rd hole but loses the marker after the next round, requiring re-measurement and distracting from course strategy.
• After v16.28: The saved target appears every time the watch loads the course, allowing the golfer to focus on execution and club selection rather than reconfiguration.

Case 2: A cycling coach prescribing weekly interval progression through Garmin Coach

• Before v16.28: An athlete’s watch sometimes loads an incorrect cycling workout, causing an unintended training stimulus and creating confusion in coach-athlete feedback.
• After v16.28: The correct workout loads consistently. The coach can rely on logged data for adaptive adjustments, and the athlete follows the prescribed intensities without guesswork.

Case 3: A backcountry skier logging a remote tour

• Before v16.28: Maximum speed and total mileage vanish from the post-activity summary, complicating reports and analysis of descent dynamics.
• After v16.28: Those values return, enabling accurate debriefs and contributing to safety-oriented reviews after a tour.

Case 4: A runner who modifies structured repeats mid-session

• Before v16.28: Adjustments are forgotten for the next session, forcing manual re-entry or risking training drift.
• After v16.28: The adjusted repeat settings persist, preserving training progression across sessions and reducing setup time.

These examples show the update’s practical value: small improvements that compound into more reliable training and less administrative overhead for athletes and coaches.

Community response and the role of Garmin’s forums

Garmin’s beta program relies on community feedback. Forum threads accompanying each beta build collect bug reports, reproduction steps, and user-supplied FIT files that help Garmin engineers isolate issues.

What successful beta participation looks like:

• Clear, concise reports that include device model, software version, steps to reproduce, and attached activity files.
• Refraining from anecdotal claims without evidence; include timestamps and screenshots where relevant.
• Verifying issues after performing a factory reset or fresh pairing to rule out peripheral causes.

Forum threads also surface regional issues (e.g., language-specific translation errors) and rare activity-type problems. The 16.28 changelog’s translation updates likely originated from such localized reports.

How these fixes affect data-driven coaching and analytics

Modern training programs depend on reliable metrics: pace, power, cadence, heart rate, elevation, and derived metrics such as training load, TSS (Training Stress Score), or HRV trends. Corrupted or missing fields undermine the models coaches and platforms use to adapt plans.

Restore and preserve the following:

• Accurate post-activity summaries: Needed for manual coaching reviews and for automatic ingestion into platforms like TrainingPeaks, Strava, or GoldenCheetah.
• Workout consistency: Prefabricated workouts that load correctly ensure data continuity for adaptive algorithms.
• Course-specific settings: Saved golf targets and preserved structured repeats maintain the integrity of specific training templates.

Metadata integrity matters, too. An incorrect workout label or missing field can cause a finished session to be miscategorized, affecting long-term analytics.

Comparisons: how this update positions Garmin among competitors

Garmin sits within a crowded wearable market that includes players like Polar, Suunto, COROS, and consumer-focused devices such as the Apple Watch. Each vendor has differing priorities: some emphasize raw sensor accuracy, others focus on ecosystem services, and others optimize battery life. v16.28 does not change Garmin’s placement but strengthens its core offering.

Comparative points:

• Ecosystem depth: Garmin’s extensive activity modes (golf, backcountry ski, triathlon, etc.) remain a differentiator. Fixes that restore specific mode functions keep that edge intact.
• Athlete workflows: Preservation of settings and fix-driven fidelity reduce user friction and keep Garmin devices favorable for serious athletes compared to simpler consumer wearables.
• Beta responsiveness: Vendor responsiveness to community-reported issues influences trust. Rapid iteration within the 16.xx cycle positions Garmin as attentive to field-reported problems.

Rivals also deploy beta programs; what separates success is the speed and completeness of fixes and how well vendors communicate known issues and workarounds.

Predicting the public release timeline and what to expect next

Garmin typically graduates stable beta builds to public releases once testing confirms fixes and does not introduce regressions across the device family. Given that v16.28 follows earlier 16.xx updates focused on bug patches, public release could arrive within a few weeks after sufficient beta user validation, though exact timing depends on aggregated feedback.

Likely next steps:

• Additional targeted fixes for remaining edge-case activity types.
• Broader rollouts of translation updates across additional devices where localization was inconsistent.
• Possible refinement of saved-setting behaviors — for example, expanding persistence beyond structured repeats to other user-defined workout templates.

Garmin’s public release process will prioritize minimizing disruption to everyday athletes and ensuring backward compatibility for third-party integrations.

How to provide useful feedback as a beta tester

Effective bug reports accelerate resolution. Follow these guidelines when reporting issues in Garmin’s beta forum:

• Title: Summarize the problem succinctly (e.g., “Forerunner 970: Backcountry Ski post-summary missing max speed after v16.28”).
• Device details: Include model, firmware version, and any paired sensors.
• Steps to reproduce: List each action taken prior to the failure in numbered steps; reproduce the issue if possible and note reproducibility frequency.
• Attach data: Provide the FIT file or a screenshot of the issue. Include timestamps, activity file names, and brief notes on conditions (GPS reception, temperature, paired devices).
• Expected vs. actual result: State clearly what you expected the device to do and what it did instead.
• Environment: Note mobile app version, phone OS version, and whether the update was applied via the watch or through connected software.

Concise, evidence-rich reports help Garmin prioritize and replicate problems.

The value of incremental updates over feature-laden releases

Large updates with sweeping changes can be disruptive. Incremental changes like those in v16.28 deliver practical improvements without destabilizing the ecosystem. Advantages include:

• Reduced risk of regressions: Smaller patches are easier to test across varied hardware and use cases.
• Faster feedback cycle: Beta testers validate focused fixes quickly, shortening the time to public release.
• User-centric improvements: Fixes often address narrow but high-impact usability annoyances that affect daily workflows.

Users focused on reliable performance often prefer stability and measured enhancements over headline features that create new issues.

What this update signals about Garmin’s product priorities

Garmin’s priorities manifest through the focus of its patches: data integrity, workout fidelity, and user-defined persistence. These priorities indicate a company orienting toward:

• Athlete reliability: Ensuring metrics and workouts function as expected across sports.
• Usability refinement: Removing small friction points that accumulate in daily use.
• Community engagement: Leveraging forum-sourced bug reports and region-specific translation fixes.

This approach benefits serious athletes, coaches, and professionals who require predictable device behavior.

Troubleshooting common issues after updating

If you install v16.28 and encounter problems, these steps address the most common scenarios:

1. Missing activity fields or corrupted summaries
   • Sync the device with Garmin Connect and download the raw FIT file from your device to check if the issue exists in the local file.
   • Reboot the watch. If the problem persists, report it to the beta thread attaching the FIT file.
2. Connectivity problems with sensors
   • Unpair and re-pair the sensor after the update.
   • Test with a short activity to confirm data stream integrity.
3. Increased battery drain
   • Allow the device to complete a couple of full charge cycles; some background indexing processes can temporarily increase consumption.
   • If drain persists, perform a factory reset after backing up data and re-test.
4. UI or translation glitches
   • Provide screenshots and exact menu paths to the forum. Localization issues are often quickly addressed once reproducible examples are available.
5. Wrong workouts loading
   • Re-sync with the Garmin Connect mobile app and verify the intended workout exists in the watch’s workout library.
   • If Garmin Coach still loads incorrectly, include the workout ID and session timestamps in your report.

Document each troubleshooting step when filing a report; partial or unstructured reports slow diagnosis.

Long-term training implications: why accuracy and persistence matter

Training is cumulative. A runner builds fitness through small, measured increases over months; a cyclist’s season unfolds through planned interventions. Errors in logging, missing data fields, or unintended workout substitutions distort periodization, recovery calculations, and performance predictions.

Consistent device behavior is foundational:

• Accurate logs feed adaptive plans that depend on past performance.
• Saved settings eliminate administrative overhead and preserve prescribed progressions.
• Post-activity metrics enable coaches to calibrate next steps with confidence.

v16.28 may not dramatically change training theory, but it preserves the integrity of the data pipeline athletes use to train efficiently.

Tips for athletes who depend on watch data for racing or safety

Athletes who use their watch for navigation, live tracking, or as a primary safety device should adopt redundancy when testing betas:

• Carry a secondary tracking method: a backup GPS device, phone-based live tracking, or a PLB/EPIRB for critical expeditions.
• Validate critical functions: navigation routes, breadcrumb trails, and live tracking on a short test route before relying on them in the field.
• Share route plans with a trusted contact and keep check-in times if you’re in remote terrain.

Bugs that affect navigation or telemetry can be rare, but the consequences in remote or high-risk environments justify extra caution.

The business and product management perspective

From a product standpoint, v16.28 exemplifies an iterative maintenance approach. Engineering teams often prioritize:

• High-frequency, low-impact improvements that reduce support tickets.
• Localization fixes to improve market penetration.
• Targeted repairs for niche activities where metrics hold functional importance beyond fitness metrics (e.g., backcountry skiing).

Investing in these areas stabilizes the platform and reduces churn among serious users who demand reliability.

Final observations on v16.28’s value proposition

Version 16.28 does not reinvent the Forerunner experience. It refines it. The update addresses retention of user-specified settings, restores essential post-activity metrics, and reconciles discrepancies between intended and delivered workouts. Those changes enhance daily workflows for golfers, runners, cyclists, and backcountry athletes. For beta participants, the update offers tangible improvements that justify testing and reporting. For the broader user base, v16.28 signals steady progress toward a more predictable, dependable wearable platform.

FAQ

Q: Which devices receive beta v16.28? A: The release notes specifically target the Garmin Forerunner 570 and Forerunner 970. The changelog references both models and a model-specific fix for the Forerunner 970’s Backcountry Ski activity summary.

Q: How do I install the beta on my Forerunner? A: If you are enrolled in Garmin’s beta program for your device, check for the update on the watch: Main menu > Settings > System > Software Update > Check For Updates. Alternatively, follow the beta program instructions posted on Garmin’s official forums to enroll and receive the build.

Q: Is this a public stable release or a beta build? A: This is a public beta release (v16.28). Beta builds are distributed to participants for testing and feedback before a stable public rollout.

Q: Will the update erase my workouts or settings? A: Beta installs do not typically erase workouts or settings, but best practice requires you to sync all data with Garmin Connect and back up any critical files before updating. If you rely on specific settings or custom workouts, verify them post-update.

Q: I depend on my Forerunner for race-day tracking. Should I install v16.28? A: Avoid installing beta firmware immediately before important races or critical expeditions. If you must, ensure you have a fallback option (secondary device, phone-based tracking) and test the watch thoroughly after update.

Q: How do I join the Garmin beta program to receive updates like v16.28? A: Visit Garmin’s official forums and look for the beta program thread corresponding to your device model. Follow the enrollment instructions; note that participation may require agreeing to beta testing terms and providing feedback.

Q: What should I do if the update causes problems? A: Sync and back up your activities, reboot the watch, and perform initial troubleshooting steps such as unpairing and re-pairing sensors. If issues persist, post a detailed bug report in the Garmin beta forum including device model, firmware version, reproduction steps, and attached activity (FIT) files. For severe problems, contact Garmin Support for assistance with re-flashing stable firmware.

Q: Does v16.28 change battery life or performance? A: The changelog does not list battery life changes. Beta firmware can temporarily affect battery usage due to background processes or indexing. Monitor battery behavior after the update and report anomalies to the beta thread.

Q: Are the golf and structured-repeat changes permanent? A: The update makes saved custom targets and persisted structured-repeat changes available in this beta. If testing confirms stability, these changes will likely be included in a subsequent public firmware release.

Q: Will this update affect third-party apps or integrations? A: Changes that restore or modify activity fields can affect third-party ingestion. Most compatible apps that read standard FIT fields should see improved data consistency, especially where values were previously missing. If you use third-party tools, verify post-update that syncing flows remain intact.

Q: How quickly will Garmin release these fixes to the general public? A: The timeline depends on beta feedback and any additional regressions discovered during testing. Minor, verified fixes can move to public releases within weeks; broader or more complex issues may take longer.

Q: Where can I find the full changelog for v16.28? A: The full change log is posted in the respective beta threads on Garmin’s official forums for the Forerunner 570 and Forerunner 970. The watch’s Software Update screen will also indicate available builds when enrolled.

Q: Does v16.28 include other fixes beyond the five highlighted changes? A: Yes. The release notes list more than 20 items, though many were introduced in earlier 16.xx updates. The five items highlighted are newly introduced in this build.

Q: Will translations improve menus in my language? A: Translation updates refine localized strings and are intended to improve clarity across supported languages. If you encounter language-specific issues after the update, report them with screenshots and the exact menu paths so they can be corrected in a subsequent patch.

Q: Can I revert to a previous firmware if I don’t like the beta? A: Reverting may require assistance from Garmin Support or re-flashing stable firmware, depending on the device and the nature of the beta. Back up your data prior to updating and document the firmware version you had previously to facilitate any rollback.

Q: Who authored the v16.28 changelog and official notes? A: Garmin posts beta announcements and changelogs on its official forums. The public notice for v16.28 appears on Garmin’s beta forum pages for the Forerunner 570 and 970.

Q: Does this update affect the Forerunner 970 flashlight or other hardware accessories? A: The v16.28 notes do not indicate hardware accessory changes. If you experience accessory behavior changes, test and report them in the beta forum.

Q: Where can I get help interpreting activity files or attaching them to a bug report? A: The Garmin beta forum community and Garmin Support can advise. When reporting bugs, attach the raw FIT file and include the activity start time and duration. Third-party analysis tools sometimes help isolate problems in recorded data.

Q: Are there known issues I should be aware of before installing? A: Check the beta thread for posted “known issues” and user reports. Beta threads often list issues confirmed by testers and any recommended workarounds.

Q: How does Garmin prioritize which bugs to fix? A: Garmin considers user impact, severity, frequency, and the importance of the feature area. Safety-critical items and widely reported bugs typically receive higher priority.

Q: Will my training metrics like Training Load and recovery updates be affected? A: Restored metrics and corrected workout loading improve the upstream data feeding these analytics. If your workouts log accurately after the update, derived metrics will reflect that accuracy as well.

Q: How can I help accelerate fixes for issues I encounter? A: Provide clear, reproducible bug reports with attached FIT files, timestamps, device model, and firmware version. Prompt responses to follow-up questions from engineers or community members also help.

This update continues Garmin’s work to refine the Forerunner user experience by patching real-world pain points. The v16.28 beta prioritizes persistent user settings and accurate post-activity metrics — changes that matter to athletes and coaches who rely on predictable, reliable device behavior. Testers should proceed with standard beta precautions: back up data, validate critical functions before important outings, and report issues with clear evidence to aid swift resolution.