I'm on 7.2 and after a period of not moving my wrist, the display turns completely off (this is after the expected dimming) even though I have Always On selected. I hope this is a bug and not one of the ways it gets the 6 days of battery life.
I'm on 7.2 and after a period of not moving my wrist, the display turns completely off (this is after the expected dimming) even though I have Always On selected. I hope this is a bug and not one of the ways it gets the 6 days of battery life.
Updated October 18th, 2022:
If your display was turning off despite your settings, the v9.37 software update has fixed the issue.
This picture will help and the Support Center article…
Thanks, Chris. Yes, that does help but given those specifications there isn’t really an option for a display that is always on so “Always on Display” is misleading (and now it makes sense how Epix is able…
I hope the 7 works out better for you. I’ll never be able to go back to that muted screen after having the Epix for a week.
To reiterate my experience, AOD on, gestures off, and I literally never…
"The watch face app can write anything on the screen in AOD mode, but there are restrictions - it must use less than 10% of pixels and not have same pixel on for more than 3 minutes (to avoid burn-in). If the app violates any of these conditions, the system turns off the display, so no AOD at all.
Using all data on the screen in AOD might bring it over 10%, that is why I limit it to what you see on the 3rd screen."(from the developer of one watchface)
Looks like the AOD goes completely off if the watch face is not following the requirements for the AOD.
On Venu 2 the difference between the active watchface and the AOD is the brightness and the amount of details(normally, seconds get removed and other background details)...i guess it's to make it below that 10% of pixels.
I find it strange that with Garmin's watchfaces the screen goes completely black on the Epix 2 or maybe i misunderstood some other posts.
Can't wait to test it personally but looks like i'll need to wait a lot
"So, we can now at least state that Garmin's doing this not for the sake of battery life but to not have to deal with burn in devices."
It's either battery life and/or burn in. But what makes you say it's burn in? I would think pixel shifting and brightness would solve that.
The requirements put on third party developers explicitly states it's for the risk of burn in.
I guess that the requirment of "10% of pixels" is making easier the pixel shifting but it's also to reduce the battery consumption(looks logic that more pixels are on and more battery you use).
That's of course a consequence of the requirement but I cannot see it to be the reason.
If they are stating 6 days with AOD with max 10% of pixels and a watchface is using more, and consuming more power, then people would complain about the duration of the battery.
Pixel burn-in is more serious, for sure, but pixel shifting should be possible also with 20% or 30% of pixels used, right?(not an expert...just suppositions). If they are limiting it at 10% then it's more for the battery, imo.
They could limit it to 20% and state 4days of battery life with AOD but they chose something that looks more appealing i guess.
You're probably right that that's one of the reasons.
It would be interesting to see a comparison between the stock faces in bright and dimmed mode. To see what's missing. I personally always have liked the stock faces but if they, in dimmed state, are quite different from what they look like in a bright state then I'm not sure I'm very fond of that solution.
In most cases they are exactly the same or just the second hand stops for example.
That's good to know.