Garmin's testing methods are supreme!
How is it possible to get THIS into public release?!
Garmin's testing methods are supreme!
How is it possible to get THIS into public release?!
Garmin's testing methods are truly special. Release notes for the new software 23.20
In Garmin language this actually mean…
I work as software developer.
I just cant understand how such an obvious bug can go through unnoticed.
Not the first time!
Garmin should fire their testers. Or hire some, may be they have none.
We are aware working on a software fix for this. I will update this thread when there is a resolution. In the mean time I have added you to a ticket we have for this. Thank you for your patience.
even in the newest beta release?
No idea. I don't take part in beta releases
Yes, it is fixed in the beta (which will probably soon roll out as stable):
https://forums.garmin.com/beta-program/forerunner-955-series/f/announcements/414201/public-beta-version-24-04---0
Change Log:
Fix misaligned data on an analog watch face.
And I know, once again I will not make friends with my opinion, but as someone working in software development I understand that Garmin does it like this.
I mean, it is ONE of many watchfaces that is impacted and it is ugly, but it does NOT impact the functionality of this watchface. Or even the basic functionality of the watch.
It should not have happened - agreed.
But it is not an urgent fix. I would have decided the same and put it to the next planned release.
Just to make that more understandable, how to set priorities: Some releases ago, the Garmin Varia functionality (backward radar for biking) broke on FR 955 with the update and did not show the gauge with approaching vehicles (just a short warning). I was also impacted by that.
And as it is obviously a functional loss and also kind of dangerous for people relying on Varia radar, this was fixed with a hotfix in the release cycle kind of two weeks later.