In light of the recent software rollout, it’s clear that a significant portion of our community is facing some frustrating technical hurdles. I’ve been monitoring the reports, and it seems that owners of several Forerunner models are dealing with bugs that directly impact the core athletic metrics we rely on most.
Software Version 27.09 Under Fire
The source of the current friction appears to be firmware version 27.09. While software updates are usually intended to refine performance, this particular version has been linked to a dip in reliability for several popular mid-range and high-end devices. The models most frequently mentioned in these reports include:
-
Forerunner 255 and 265
-
Forerunner 955 and 965
While not every user is experiencing these glitches, the volume of reports on platforms like Reddit has grown loud enough to catch the attention of the wider tech community.
Inaccurate Biometrics and Elevation Data
The primary grievance involves the optical heart rate sensor. For many athletes, real-time heart rate data is the foundation of their training zones and effort management. Users have reported that the sensors are becoming unreliable during active sessions—a problem that is much harder to fix after the fact than a simple GPS wandering issue.
In addition to biometric concerns, there are reports of strange behavior regarding elevation tracking. Some users have noted that their watches are logging significant climbs during workouts conducted on completely flat terrain. Because these issues have reportedly persisted for some since earlier this year, the frustration is mounting regarding the speed of a potential fix.
Community Response and Next Steps
The reaction from the user base has been mixed, with some calling for more transparency from the manufacturer. While many units continue to function perfectly, those stuck with erratic data are finding it difficult to rely on their devices for serious training.
If you are noticing similar discrepancies with your heart rate or altimeter readings on the latest firmware, the best course of action is to document the instances and reach out to support. Consistent feedback from the community is often the fastest way to ensure these bugs are prioritized in the next beta or public software cycle.
Also Read: The Garmin Forerunner 970 is Here, But I’m Still Wearing the 965—Here’s Why!
