Minor 16.22 bug on Aviator Gen 2

Tux 1 month ago

Hi,

there is a minor bug in SW version 16.22: on the standard Aviator watchface the sunset time is shown as „Dec. 31st“.

Nothing serious but if you could please consider it for the next bugfix release.

Thank you.

Top Replies

Garmin-Laurie 10 days ago in reply to 3014301 +6 verified

Update April 17, 2024

Our engineers have been able to reproduce this concern. This appears to only impact the Home Airport Weather location on the watch face. Our aviation team is investigating a software…
Garmin-Laurie 1 month ago in reply to 4389125 +5 verified

I have reported this concern to our engineers. If there are any updates or solutions, I will update you here. Thank you for taking the time to report this.
Peter 1 month ago +4

Suppose that's the price of the small, calculated risk of not allowing interested Aviator users to participate in the beta test :-)

All Replies

0 gaijin 1 month ago

Just a thought-

This sounds like the kind of glitch that could be solved by a hard reset - holding down the top left button until the watch completely shuts down, waiting 30 seconds, then turning the watch back on. No data are lost when doing this, unlike a complete factory reset.

HTH

0 visitor29 1 month ago

i have same on my aviator, even after full reset it sows me "SET 31 Dec"

0 mcbit 1 month ago

Just checked mine is the same if I switch to standard watch-face

0 Tux 1 month ago in reply to visitor29

Correct. I also tried a hard reset before highlighting this topic here.

0 gaijin 1 month ago

Yup. I get the same thing.

0 Peter 1 month ago

Same here...

0 Peter 1 month ago

Suppose that's the price of the small, calculated risk of not allowing interested Aviator users to participate in the beta test :-)

0 visitor29 1 month ago in reply to Peter

In my years of experience with Garmin, starting from the Fenix 3, I've consistently noticed that whenever they release firmware to the public, it often contains bugs. Whether labeled as beta or public release, the outcome remains the same.

0 4389125 1 month ago

Same bug here.

+1 Garmin-Laurie 1 month ago in reply to 4389125

I have reported this concern to our engineers. If there are any updates or solutions, I will update you here. Thank you for taking the time to report this.