This has been fixed in sw version 16.19, which is currently at 10% rollout. If you are experiencing this same issue after 16.19, please start a new thread.
But apparently that was a misstatement and 16.19 was only ever coming out for 255.
The 16.19 software release fixed an issue specific to the Forerunner 255 Series. At this time, we do not have an estimate on when the next software release will be for the Forerunner 265 Series, Forerunner 965, or the Forerunner 955 Series watches.
I believe 965, 955, 265 and 255 all share a similar code base, which is why their firmware releases are all similar with similar change logs. When there are bugs, they are replicated across all 4 devices. I think they are simply rolling out 16.19 to 255 first to make sure there are no major issues before rolling out to the other 3 devices.
I believe 965, 955, 265 and 255 all share a similar code base, which is why their firmware releases are all similar with similar change logs. When there are bugs, they are replicated across all 4 devices.
Good point and I agree. I just wanted to add the context (for anyone else reading the thread) about:
- why people specifically believe that 16.19 should be available for 955 right now
- what changed regarding 16.19's status
Maybe I worded my comment a bit too strongly when I said "16.19 was only ever coming out for 955". I'll just let the comments by Garmin-Sierra speak for themselves. Maybe 16.19 will come out for 955 eventually, but it isn't out now. It's possible that 16.19 will be released for 955 (and the other watches) in the future, or maybe the next version for the 955 (and the other watches) will be 16.20, who knows.
