Is there an always on display basic example anywhere?

But the 10% luminance can be reasoned also by battery saving, so we can't know if AMOLED displays can burn-in or not.

flocsy🤠 said:

we can't know if AMOLED displays can burn-in or not.

I realize this is just a poor choice of words, but there’s no such thing as an AMOLED display that can’t burn in (even the newest AMOLED displays have a chance of burning in). I think what you mean to say is that perhaps burn in is not a practical problem with the latest displays that Garmin uses (regardless of how the display is used), meaning that Garmin’s burn-in restrictions are no longer necessary (at least, not to prevent burn-in). Personally, I would highly doubt that, but I could be wrong. (It doesn’t matter either way - see below)

On a side note, if burn-in is not a problem on the latest AMOLED Garmins, why does Garmin employ pixel shifting on activity screens, causing the data field dividers (among other things) to constantly move around? More than one dev has noticed the pixel shifting and filed a bug report (erroneously assuming it's not intended behavior.)

Obviously Garmin thinks that burn-in is a valid concern.

flocsy🤠 said:

But the 10% luminance can be reasoned also by battery saving, so we can't know if AMOLED displays can burn-in or not.

But it doesn’t matter whether the 10% luminance restriction is “actually” due to burn-in concerns, battery life concerns, or both. As you like to say, you’re missing the point here. If you read the comment you replied to carefully, I never explicitly said anything about whether the latest devices would burn in or not. I said that Garmin’s new burn-in restriction will be applied to the latest devices.

My point is that Garmin enforces the 10% luminance rule regardless of the rationale behind it, and whether or not it is really necessary. 

This was in response to FlyFrosty’s comment: “I have burn in protection included for all, even though (in theory) the AMOLED displays no longer require it.”

(To be fair, I did say "I think they do", implying I think the displays themselves require it, but I followed up by clarifying that Garmin's burn-in restriction will be applied.)

Again, if you are simulating a CIQ 5 device and you enable Always on Mode in the simulator, if your app violates the 10% luminance restriction, the simulator will immediately tell you that the screen will turn off due to violating the rule.

The exact message is:

Warning!

Screen update will be shutoff due to display luminance exceeding 10% of maximum display luminance in low power mode. See Screen Heat Map for more details.

The heat map (which is automatically opened at this point), displays the following status indicators:

- Power Mode: OFF
(if you cycle the mode to “Always-On” using the Toggle Power Mode button, for a split second, this value is displayed as “Always-On” before it automatically changes to “OFF”)

- Screen Protection: ON

- Burn-in State: YES
(regardless of whether it’s “really” because of burn-in concerns, battery life concerns, or both, Garmin chooses to present it as a burn-in issue, and again it really doesn’t matter since Garmin will enforce the rule regardless of the real reason behind it.)

- Luminance Usage: (some number greater than 10%)

I was able to recreate this easily by modifying the AnimationWatchface sample so it supports fr965, running it in the sim and setting the display mode to Always On.