Garmin Forerunner Software 28.05 Rolls Out: What Changed for the 165, 255, 265, 955 and 965 — Fixes, Workout Improvements and Update Guide

Table of Contents

1. Key Highlights:
2. Introduction
3. What Software Version 28.05 Contains — a close reading of the changelog
4. Why these fixes matter: real impact on training and events
5. Model-by-model breakdown: what each Forerunner gains
6. Navigation and maps: the significance of the China OSM and course crash fixes
7. Sensors and accessory pairing: what the Schwinn fix restores
8. Audio prompts and interval training: how completion-time announcements change pacing
9. Run Coach plan synchronization: avoiding training drift
10. Display settings and workout previews: convenience improves consistency
11. How Garmin rolls out firmware: stable, beta and staged distribution
12. How to update: practical instructions and precautions
13. Troubleshooting common problems after installing 28.05
14. Early user reports and community feedback
15. Timing your update: update now or wait?
16. Beyond 28.05: what Garmin might focus on next
17. Practical examples: how 28.05 affects specific user scenarios
18. How Garmin’s fix strategy reflects product maturity
19. Monitoring the rollout and documenting issues
20. FAQ

Key Highlights:

• Garmin has released Software Version 28.05 for five Forerunner models (165, 255, 265, 955, 965), addressing activity upload issues, race event duplication, workout preview and other stability problems; rollout currently at roughly 20% of eligible devices.
• Several model-specific fixes included: crash prevention after course navigation and China OSM map corrections for the 955/965; Schwinn device pairing restored for 255/265/955/965; all models receive targeted improvements to activity and workout handling plus general stability patches.

Introduction

Garmin has issued a stable firmware update — Software Version 28.05 — for a group of its mid-range Forerunner smartwatches. The update follows the earlier stable release 27.09 and a short-lived beta cycle under Version 28.03. This release focuses on reliability: fixes that prevent activities from failing to upload, correct duplicated race events, align Run Coach week numbering between device and Garmin Connect Mobile, and eliminate several workout-related issues that have tripped users in training and racing. Distribution has begun globally but remains limited so far; Garmin reports approximately 20% of eligible units have received the update. The changes vary by model, with the Forerunner 955 and 965 receiving the most patches.

This article examines what the update delivers, why the fixes matter for athletes and everyday users, how the rollout works, and what owners should do before and after installing Version 28.05. Practical troubleshooting steps, real-world scenarios, and guidance on update timing are included for runners, cyclists and multisport athletes who rely on consistent data and device behavior.

What Software Version 28.05 Contains — a close reading of the changelog

Garmin published a grouped changelog for its Forerunner x55 and x65 families with some model-specific items. The update prioritizes fixes to activity handling, workout previews, display settings synchronization, audio prompts, course navigation stability, map display in China, and pairing with certain devices.

Core fixes that apply across all Forerunner x55 and x65 devices:

• Resolved an issue that could cause some activities to fail to upload to Garmin Connect.
• Corrected race event data problems where events could be missing or duplicated after being sent to the device.
• Fixed a discrepancy where the Garmin Run Coach plan's week number on the device differed from Garmin Connect Mobile.
• Addressed problems previewing workouts that had only one step.
• Ensured display settings changed from Garmin Connect Mobile apply correctly on the device.
• Enhanced audio prompts for distance intervals by specifying completion time.
• Various other bug fixes and improvements.

Forerunner 955 and 965 specific:

• Fixed a crash that could occur when saving an activity after following course navigation.
• Corrected issues with China OSM (OpenStreetMap) map data display.

Forerunner 255, 265, 955 and 965:

• Restored pairing functionality with Schwinn devices.

Notice the differences: the 955 and 965 receive two additional fixes (navigation-crash and China maps), while the 255/265 get Schwinn pairing restored, and the 165 receives a reduced set of fixes relative to the other models.

Why these fixes matter: real impact on training and events

A firmware update that primarily lists bug fixes might read like a series of technical bullet points, but these changes have tangible effects for people who train, race and rely on accurate data.

Activity upload failures: Many athletes sync performance data to Garmin Connect, Strava, Final Surge, TrainingPeaks or a coach’s platform. When activities fail to upload reliably, gaps appear in training history, planned workouts can’t be validated, and coaches lose visibility into athlete adherence. For a weekend long run that a coach needs to see, a failed upload can mean missed feedback. Version 28.05 fixes conditions that caused some uploads to fail, reducing the risk of lost training records.

Race event duplication/missing events: Race integrations are used to push course files and event details to devices ahead of competition. Duplicated or missing race events can cause confusion on race day: athletes might believe they’ve loaded a course that isn’t present, or worse, follow an incorrect course file. Clearing duplication and missing-event bugs ensures that events sent from organizers or apps arrive consistently and correctly.

Run Coach week-number sync: Garmin’s Run Coach adjusts weekly load and sessions over a training plan. If the device shows a different week number than Garmin Connect Mobile, training progress can get misaligned. Imagine a coach and athlete who assume they are both looking at Week 6 of a build but the device thinks it’s Week 5 — workouts and recovery days could be mistimed. The synchronization fix prevents this mismatch.

Workout preview and single-step workouts: Previewing workouts matters when users build a custom session with a warmup, a single interval set, and cooldown. Previously, workouts with only one step could fail to preview, causing users to doubt whether a complex custom session would run as programmed. This fix reduces pre-workout anxiety and improves confidence in structured sessions.

Display settings not applying: Many athletes manage device display preferences from Garmin Connect Mobile for convenience. When a watch didn’t apply those settings, users had to reconfigure from the device, wasting time and introducing inconsistency. The patch aligns mobile-to-device display behavior.

Audio prompt specificity for distance intervals: The update now specifies completion time in audio prompts for distance intervals. For interval training where pacing and split goals are critical, hearing a prompt that announces not just the interval name but the projected or completed time helps maintain rhythm and adjust effort.

Course navigation crash: The 955 and 965 received a fix to prevent crashes when saving an activity after course navigation. Course navigation is central to long routes, trail races and complex urban courses. A crash that prevents saving the activity can destroy precious training or race data; fixing this stabilizes post-activity data handling.

China OSM map fix: Map display errors in China can affect navigation reliability. Ensuring maps render correctly in region-specific datasets restores confidence for users who travel or live there.

Schwinn device pairing: Indoor cycling trainers and smart bikes from manufacturers like Schwinn are often paired with watches for power, cadence and cadence smoothing. Restoring pairing prevents broken indoor training sessions and missed sensor data.

These fixes restore reliability across scenarios that range from daily workouts to high-stakes racing.

Model-by-model breakdown: what each Forerunner gains

Although many fixes apply across the range, differences matter for owners of each model. Here’s a closer look at what to expect for each device.

Forerunner 165

• Receives seven changes relative to 27.09. The 165 benefits from the cross-device fixes: activity upload reliability, race event handling, Run Coach synchronization, workout preview fix, display settings application, audio prompt specificity, and general bug fixes. The 165 receives fewer individual patches than the higher models, reflecting the hardware and feature set differences.

Forerunner 255 and 265

• Receive eight changes. Both 255 and 265 inherit the cross-device fixes plus restoration of pairing to Schwinn devices. Owners running indoor cycling workouts or connecting to smart trainers should see pairing restore, which re-enables sensor-based indoor training metrics.

Forerunner 955 and 965

• Receive the full set of up to ten changes. In addition to the shared fixes and Schwinn pairing, these two models fix a crash related to saving activities after navigation and correct China OSM map display behavior. The 955 and 965, positioned at the top of the Forerunner lineup, support advanced navigation features and more complex map data, so stability improvements here have outsized importance for endurance and multi-sport athletes.

Understanding why the 955/965 get extra fixes: these models include more advanced navigation and mapping features and typically handle larger activity datasets. They also attract heavy use from multisport athletes on long navigation-heavy outings. Fixes targeted at these models reduce the likelihood of a high-impact failure during navigation and afterwards during data preservation.

Navigation and maps: the significance of the China OSM and course crash fixes

Maps and routing are a core component for many Forerunner users. The China OSM maps fix and the crash-after-navigation patch address two separate but related areas.

China OSM maps

• Map datasets for China often rely on either region-specific tiles or adjusted OSM datasets due to local mapping and regulatory constraints. If OSM tiles render incorrectly or contain misaligned data, turn-by-turn instructions, elevation profiles or even route snapping can become unreliable. Users relying on a device for route following within China or for routes that cross into the region benefit from corrected map rendering.

Course navigation crash and post-navigation saving

• The sequence — follow a course, finish, then save — is fundamental. A crash that prevents the activity from saving destroys the corresponding data record locally and complicates upload attempts. The 28.05 fix prevents that crash, making it safer to trust the watch during navigation-heavy activities. Endurance athletes who log long events with navigation should see fewer abandoned or lost activity files.

Practical example: an ultra-runner navigates a 50-km course using a Forerunner 955. Previously, an unexpected crash on save after the navigation leg could wipe the only record of their pacing and splits. Version 28.05 removes that critical failure mode and ensures the activity file persists.

Sensors and accessory pairing: what the Schwinn fix restores

Schwinn-branded equipment often appears in home training environments: smart bikes and trainers used with Entities like Zwift, Peloton alternatives, and structured indoor workouts. These devices communicate heart rate, cadence, speed, and power via Bluetooth or ANT+. Watches that can pair to these trainers allow athletes to keep a single consolidated record and view real-time metrics on wrist during sessions.

Symptoms before the fix:

• Inability to pair or sudden disconnections visible on device pairing lists.
• Trainer data not appearing in workout summaries.
• Inconsistent cadence or power readings during structured indoor workouts.

Impact of the fix:

• Restored connectivity enables consistent indoor training sessions with accurate capture of power/cadence data and smoother integration into multi-sensor training setups. Cyclists and triathletes who depend on a single device for both outdoor GPS and indoor trainer metrics should find their sessions more reliable.

Note on standards: Garmin watches support BLE (Bluetooth Low Energy) and ANT+ sensor profiles. Successful pairing depends on device firmware compatibility as well as the trainer's firmware and Bluetooth/ANT settings. While the update restores pairing in many reported cases, users should ensure their Schwinn device firmware is up to date and that pairing modes are correctly set on both devices.

Audio prompts and interval training: how completion-time announcements change pacing

One item in the update might seem small but has meaningful training consequences: specifying completion time in audio prompts for distance intervals. Here’s how that plays out.

Before the change: Users received generic audio prompts like “Interval complete” or “Halfway through interval,” which required glancing at the screen or relying on pace alone to know time targets.

After the change: The watch can announce the completion time for a distance interval as part of the audio prompt. In practice, that might sound like “400 meters complete — 1 minute 23 seconds,” giving immediate numeric feedback for pacing.

Why that matters:

• Maintains focus: Audio completion times let athletes stay mentally in the session without breaking stride to look at the wrist.
• Immediate correction: Hearing a completion time allows athletes to speed up or ease off during the next interval based on actual performance.
• Coaching clarity: When a coach or training plan prescribes specific interval time targets, instant audio feedback provides confirmation that the athlete met or missed the goal.

Real-world scenario: A track athlete runs a set of 8x400m intervals targeting 1:20 each. With completion-time audio prompts, after the first repeat finishes the athlete hears “400 meters complete — 1 minute 18 seconds” and adjusts pace for the next lap to hit the planned session load.

Run Coach plan synchronization: avoiding training drift

Garmin's Run Coach plan is designed to prescribe a structured weekly progression. Discrepancies between device-week numbering and Garmin Connect Mobile can produce duplicate or skipped sessions and confusion about which workouts to perform.

If a user believes they are on Week 4 but the device shows Week 3, they may inadvertently perform an easier session, undermining periodization and planned loading. The fix aligns the week numbers so the plan progression matches between mobile and device. For athletes following a formal plan — a marathon training block, for instance — consistency matters for long-term adaptation and fatigue management.

Display settings and workout previews: convenience improves consistency

Two additional fixes improve day-to-day usability.

Display settings from Garmin Connect Mobile: Many users prefer configuring screens, data fields and widgets from the larger mobile interface. When settings changed on the phone failed to apply to the watch, users wasted time reconfiguring on wrist. This update restores the intended workflow and reduces friction.

Workout previews for single-step workouts: Some sessions are intentionally minimal — a single interval step or a single pace target. Previously, previewing such workouts could fail, leaving doubt whether the session was correctly set. The patch guarantees that even single-step workouts display and run as intended.

These fixes may not be headline-grabbing features, but they increase confidence in routine interactions with the device and reduce small sources of frustration that accumulate over weeks of training.

How Garmin rolls out firmware: stable, beta and staged distribution

Garmin distributes updates through a staged mechanism. Typically:

• Beta channel: Early releases for testing that may address particular issues or trial new behaviors. Beta versions are often limited to users who opt in.
• Stable channel: Public releases intended for production use after testing.

Version 27.09 was a stable release several months prior. Garmin then pushed a 28.xx beta (28.03), likely to test certain fixes and collect user feedback. With those learnings, the company published 28.05 as a stable rollout.

Staged distribution explanation:

• Garmin rarely releases updates to all eligible devices at once. A staged rollout gradually increases the percentage of updated units, allowing the company to monitor telemetry and user reports for any unforeseen regressions.
• Approximately 20% of eligible watches had received the 28.05 update at the initial rollout status. That percentage typically increases over days to weeks.

Why staged rollouts matter:

• They limit the blast radius of potential regressions.
• They allow Garmin to halt or patch quickly if a severe issue appears.

Owners can expect the update to reach more devices as Garmin observes stability metrics.

How to update: practical instructions and precautions

Updating a wearable is straightforward but should be done with care to avoid mid-update disruptions or data gaps.

Recommended pre-update steps:

1. Charge the watch: Ensure at least 50% battery; 80-100% is preferable to avoid the device powering down mid-update.
2. Back up preferences if you rely on custom configurations. While most settings persist, noting key display and data field arrangements reduces time to restore in unlikely cases.
3. Finish or sync ongoing activities: Sync any unsent activity files to Garmin Connect because firmware updates can affect storage and sometimes require a restart.
4. Update companion apps: Make sure Garmin Connect Mobile and Garmin Express (on desktop) are on the latest version. Companion app updates often accompany device firmware and fix pairing or transfer issues.

Update methods:

• Over-the-air (OTA) via Garmin Connect Mobile: When a staged update reaches your device, the watch typically receives a notification in the Garmin Connect Mobile app. Tap the device entry and follow the prompts to install.
• Garmin Express (desktop): Connect your watch to a computer and open Garmin Express. If the update is available to your device and in the Garmin Express channel, the software will present the option to install.
• Manual push: Some advanced users force-check for updates in Garmin Connect Mobile by going to device settings and using the “Check for Updates” option. Because of staged rollouts, forcing an update may not show the new firmware until Garmin expands the distribution.

Post-update checks:

• Confirm that your common sensors (heart rate straps, power meters, cadence sensors, smart trainers) still pair and provide data.
• Run a short test activity (5–10 minutes) to ensure GPS locks, data fields populate and uploads occur.
• Verify that previously reported issues are resolved: try previewing a single-step workout; check Run Coach week number consistency; pair a Schwinn device if applicable.

If the update fails:

• Restart both the watch and the companion device (phone or PC).
• Reattempt via Garmin Express if OTA fails.
• Remove and re-add the watch in Garmin Connect Mobile as a last resort (note: re-adding may require re-pairing sensors and re-downloading maps or courses).

Troubleshooting common problems after installing 28.05

Although 28.05 aims to increase stability, no rollout is entirely free of issues. Here are troubleshooting steps for plausible problems.

Update stuck or failed:

• Force restart the watch (model-specific hold-button combinations detailed in Garmin support).
• Try installing via Garmin Express instead of OTA.
• Ensure the watch has adequate storage; remove large offline maps or old activities if storage is near capacity.

Sensor pairing loss:

• Reboot the watch and the accessory.
• Unpair and re-pair the device within Sensors & Accessories settings.
• Update the accessory’s firmware if possible.

Activity upload still failing:

• Confirm the watch is connected to your phone and Garmin Connect Mobile.
• Manually sync via the app.
• Use Garmin Express and connect via USB for a manual upload route.
• If uploads failed for multiple users before 28.05 and persist, gather activity files and contact Garmin Support with logs.

Navigation crash persists on 955/965:

• If issues continue after 28.05, avoid immediately removing course navigation mid-activity. Instead, stop the activity and save without navigating after a trial run to produce diagnostic logs for Garmin Support.

Map display issues in China:

• Verify that you have the correct regional maps installed.
• Ensure the watch’s map configuration and language/region settings match Garmin Connect Mobile.

Schwinn pairing fails:

• Update trainer firmware.
• Ensure the trainer is discoverable and not connected to another device (some trainers only allow one active connection).
• Toggle Bluetooth/ANT settings on both devices and re-pair.

When to contact Garmin Support:

• If an activity file is missing or corrupted post-update.
• If a critical function (e.g., navigation or sensor pairing) is unusable after recommended troubleshooting.

Early user reports and community feedback

Rollouts produce forum threads, social posts and support tickets. Initial community feedback for 28.05 is likely to focus on:

• Whether activity uploads that previously failed now complete reliably.
• Stability of course navigation and whether reported crashes are resolved.
• Successful reconnection to Schwinn devices.
• Any unexpected regressions introduced by 28.05 (battery impact, UI responsiveness, new pairing issues).

Historical pattern: Garmin’s patches that address specific customer-facing issues generally receive positive immediate response when they resolve long-standing problems. Staged rollouts let early adopters provide data to Garmin and the broader community, improving the larger deployment.

Owners who depend on their devices for coaching, racing or multi-sport transitions should monitor relevant community threads (Garmin forums, Reddit’s r/Garmin, sport-specific forums) for firsthand reports from users of the same model.

Timing your update: update now or wait?

Whether to update immediately depends on usage patterns and risk tolerance.

Reasons to update now:

• You have experienced any of the fixed issues (upload failures, duplicated race events, Run Coach misalignment, navigation-related crashes, Schwinn pairing problems).
• You rely on consistent activity uploads and accurate navigation data.
• You use a 955 or 965 and have encountered navigation or China map issues.

Reasons to wait:

• You are in the middle of a major training block or have an imminent race and cannot afford even a low-probability regression.
• You rely on a heavily customized workflow (third-party apps, complex sensor setups) and prefer to see initial community feedback.
• You have multiple devices in a team environment where a staged adoption minimizes risk.

A prudent approach:

• For most users the update is low-risk and beneficial. If you elect to wait, monitor community reports for 48–72 hours after the update gains broader distribution. If your device is mission-critical for an impending event, postpone updates until after the event unless the update fixes a problem you are currently experiencing.

Beyond 28.05: what Garmin might focus on next

Garmin’s releases typically alternate between targeted bug fixes and broader feature updates. After stabilizing known issues in 28.05, likely areas for future attention include:

• Further navigation refinements, particularly around multi-leg courses and turn prompts.
• Expanded smartwatch features, possibly in watch face performance, widget responsiveness, or health metric refinement.
• Continued pairing improvements with third-party smart trainers and gym equipment.
• Enhanced cloud-sync features and coach integrations to reduce plan mismatches.

Users interested in new features should watch Garmin’s beta programs and public release notes for the v28.xx cycle, which may include feature additions beyond the stability patches seen in 28.05.

Practical examples: how 28.05 affects specific user scenarios

Scenario 1 — Weekend long run with navigation and post-run upload: A trail runner follows a 30-km preloaded course on a Forerunner 965. Previously, on long navigations, the device had a chance to crash at save time, risking activity loss. With 28.05, the runner completes the course, saves the file without crash, and observes a successful upload to Garmin Connect, preserving route and elevation data for coach analysis.

Scenario 2 — Interval session on track: A competitor runs 10x800m intervals. With the new audio prompt behavior, each interval completion announces the exact time, enabling the runner to modulate effort without constantly looking at wrist. The Run Coach week number alignment ensures the athlete is on the prescribed week and performs the correct workout intensity.

Scenario 3 — Indoor cycling on a Schwinn smart bike: A triathlete uses a Forerunner 265 to record indoor trainer sessions paired to a Schwinn device. After updating to 28.05, pairing is reliable, cadence and power metrics appear in activity summaries, and the athlete’s indoor workouts upload to Garmin Connect for training load calculations.

Scenario 4 — Race organizer handling course uploads: An event organizer sends courses to participants’ devices. After 28.05, participants report fewer duplicated or missing race events, simplifying day-of coordination.

These examples show the update’s practical benefits across disciplines.

How Garmin’s fix strategy reflects product maturity

A mature fitness platform reaches a stage where incremental stability improvements and edge-case bug fixes are more valuable than headline feature rollouts. Version 28.05 reinforces that pattern: the updates focus on reliability, data integrity and consistent integration with companion apps and external devices. For athletes who treat their watch as a primary data logger and navigation tool, solving these edge cases matters more than adding cosmetic features.

Monitoring the rollout and documenting issues

Owners who want to track rollout progress or submit feedback should:

• Check Garmin’s release notes in the device settings in Garmin Connect Mobile.
• Monitor Garmin Support Twitter/X and official forums for notices.
• Use community forums to share reproduction steps and any diagnostic logs if a persistent issue emerges. When reporting, include device model, firmware version before and after update, and a concise description of the failure with replication steps.

Garmin often requests logs for complex issues: capturing these early helps accelerate investigations.

FAQ

Q: Which Forerunner models are eligible for Software Version 28.05? A: The update targets the Forerunner 165, Forerunner 255, Forerunner 265, Forerunner 955 and Forerunner 965.

Q: How many changes does 28.05 include? A: Changes vary by model. All eligible models received a set of shared fixes (activity uploads, race events, Run Coach week numbering, single-step workout previews, display setting sync, audio prompt improvements, and general bug fixes). The 255/265/955/965 also received a fix to restore pairing with Schwinn devices. The 955 and 965 receive two additional fixes to address a post-navigation crash and China OSM map issues. Overall, the 955/965 see up to ten changes, the 255/265 about eight, and the 165 around seven relative to Software Version 27.09.

Q: How widespread is the rollout? A: Garmin reported that approximately 20% of eligible devices had received the update at the initial reporting time. Rollouts are staged, so distribution typically increases over subsequent days.

Q: How do I update my watch to 28.05? A: Use Garmin Connect Mobile when the update appears in notifications for your device, or connect the watch to a computer and open Garmin Express. Ensure the watch has sufficient battery before updating. If the update is not yet available to you, it will likely appear as Garmin expands the staged rollout.

Q: Should I update immediately? A: Update if you are affected by the fixed issues (upload failures, race event duplication, navigation crashes, Schwinn pairing problems, etc.). If you are in a critical training cycle or have an upcoming race and no current problem is being fixed by 28.05, you may prefer to wait a short period and monitor community feedback.

Q: What if the update fails or something breaks? A: Restart both devices (watch and phone/PC), attempt the update via Garmin Express if OTA fails, and re-pair sensors if needed. If problems persist, gather logs and contact Garmin Support. For missing or corrupted activity files, reach out directly to Garmin Support as soon as possible.

Q: Will this update affect third-party apps like Strava, TrainingPeaks, or coach platforms? A: The update’s primary intent is to fix device-side issues. Successful uploads to Garmin Connect should continue to propagate to third-party services as before. If you see post-update disruptions in third-party sync, verify Garmin Connect upload success and then check third-party service settings.

Q: Does 28.05 change battery life or performance? A: The changelog does not list battery or performance regressions as planned changes. Staged rollouts are used in part to detect any unanticipated regressions; if users report battery or performance issues, Garmin may address them in subsequent patches.

Q: Can I downgrade to a previous firmware if I encounter problems? A: Garmin does not provide an official downgrade path for most users. If you encounter severe issues post-update, contact Garmin Support to discuss possible remediation.

Q: Are non-Forerunner Garmin devices affected? A: 28.05 specifically targets the listed Forerunner models. Other Garmin devices receive separate firmware releases and have their own changelogs.

Q: Where can I see the official changelog? A: The official changelog is typically published in Garmin Connect Mobile under device settings and may be posted to Garmin’s support pages or community release notes.

Q: What should coaches know about this update? A: Coaches should note that Run Coach week-number inconsistencies between device and Garmin Connect Mobile are addressed, which reduces the risk of athletes training off-plan due to a mismatch. Encourage athletes to update if they experienced week-number issues, and confirm successful uploads of recent workouts before adjusting plans.

Q: Is there any security-specific content in the update? A: The changelog focuses on functional and stability issues. Security-related changes are typically called out explicitly when present.

This update underscores Garmin’s continued emphasis on reliability for its training-focused devices. For owners of the affected Forerunner models, 28.05 restores several important behaviors that athletes and coaches rely on daily. Apply the update when convenient, follow pre-update precautions, and run verification checks afterward — particularly if you use advanced navigation, rely on indoor trainer pairing, or follow structured training plans.