After 9.24 update, third party watch faces don't return to AOD display after notification, they go blank

This happens to two different third party watch faces that I have installed, "Quartz" and "Futura". This does not happen with the stock Garmin watch faces.

When I receive a notification on my watch, I typically will just glance at it when it lights up the screen (I have Gesture = Off, Always On = On) and then ignore it and let it time out and go away on its own. When I do this, instead of returning to the third party watch face and then going into the AOD mode, the screen just goes blank.

This worked correctly before the latest Garmin update; I've changed nothing on my end like AOD settings on the watch or within the watch faces.

Anyone else seeing this?

Top Replies

All Replies

0 Al P 7 months ago

Any updates on this? I am thinking of upgrading from the 2 plus to the 3 but this is a showstopper issue for me.

0 4536956 7 months ago in reply to Al P

Nope, none. Only got an automatically generated E-Mail by garmin that I will be notified if they need further information or if there is a solution.

If I sold a watch and it would stop showing the time, I'd be all over it to get this fixed. Not a priority for garmin apparently... So embarassing...

0 Al P 7 months ago in reply to 4536956

. The email is because you also generated a ticket in addition to posting here?

0 4536956 7 months ago in reply to Al P

No, was generated for me by the garmin admin surveying this post... At least they did that X-)...

0 8838280 7 months ago

Same issue still with custom watchfaces in Venu 3 beta version 10.08.

AOD on, raise wrist off. Custom 3rd party watch faces still returning to blank (black) sceen or remain in high-energy mode (with second-hand moving) after notification creating battery drain and probable screen burn in.

0 Scott 7 months ago

Joining this thread since my report weas in a different one that's been locked

Garmin-Inder

Do we have permission to email you? Yes
Do we have permission to look into your Connect account? Yes
What country are you located in? USA

0 Garmin-Inder 7 months ago in reply to Scott

Thanks, we've gathered enough reports on this and will update this post once there is a solution.

0 BippityBoppity 7 months ago in reply to Garmin-Inder

It goes blank, and you can see that many other people are having this problem too. This happens to two different third party watch faces by different developers. I did reach out to the developer and they have no idea why it would suddenly be happening on a watch face that worked fine until the latest update.

0 4536956 7 months ago in reply to BippityBoppity

Totally agree with bippityboppity. It has been a month now since this issue came up - I tested way more watch faces than just two. Most of third party watch faces show the issue - allthough some exceptions seem to work. A bit of a mess.

Sorry, Garmin-Inder - but as far as I am concerned this moves on way too slowly. In the meantime there already has been a software update which didn't address the issue at all. It seems our only way to get you software developpers moving ist to repeatedly keep this thread actice so hopefully new customers will read about this and wait with a purchase. And it's not like this is the only funcionality issue with your software. It's just the most annoying one.

0 3094365 7 months ago

I've got same problem too... Venu3.. get me crazy.