[Samsung Galaxy S10 Themes, Apps, and Mods] Chainfire:
It does complicate the code quite a bit. Nevertheless, I am looking into solution to make what you're all asking for possible.

Holey Light tries to create/remove its overlay as quickly as possible. However, as others have also noticed, sometimes there is a small delay. I myself only see this delay when I turn the screen on, which isn't exactly prize winning visually and I am looking into improving that, but I personally never experienced it when I turn the phone back on.

The 75%/25% is due to Holey Light only blacking out 75% of the screen, so charging information - and the fingerprint icon - is still visible.

Delays in the overlay disappearing can be caused by many things. First off, we currently depend on Android informing the app that the screen has turned on. If you have multiple apps listening for this event (and it is certainly not uncommon to), these callbacks are executed serially. If Holey Light is not first in line and another app is being slow, you will notice this exactly as the behavior described. (That is not to say this is the cause, just that if this situation presented itself, it would also look exactly like this)

I am trying to improve this behavior, I suggest you keep upgrading as new versions come out, and report back if things have improved. It is hard for me to test as I myself do not have this issue.

Hmm, this implies a logic issue! Interesting! Can you take a picture of what your AOD screen looks like exactly?

Also [MENTION=5338421]BuckyRocks[/MENTION] and [MENTION=4351783]mixxxk[/MENTION]

That is might be tricky indeed. For this to work correctly, you will definitely need (an updated) AOD helper.

These pixels may indeed burn-in. This is why the "Unholey Light" option is better for your screen too. Future scheduling/timeout options will further help with this.

I understand the mode may be desirable, but I'm not sure whether the assumption above is correct. The screen still has some power as it detects your taps, I'm not sure whether the difference between these modes is big enough to be relevant. (I mean it might be, I'm not saying it isn't, but I wouldn't just assume so)

Working on the show/hide delay.

Not sure why some of you are seeing AOD switching to landscape mode yet. Does it happen after a couple of screen taps by any chance? There is a hidden button to switch between portrait and landscape, but it requires three taps to activate.

This is in fact intentional. Do you want it to *not* show this?

You're the only person to report this as of yet.

If no black-ish notifications show up in the Colors screen in the active section, that is indeed weird. If they do, you probably have one of them set to "pretty much black but not completely black".

Not currently no. It is on my list to investigate. I'm not sure *if* the proximity sensor can be used in this mode (it wouldn't work in my first simple test), but what is your purpose for this? It might actually take more power to use the proximity sensor than it takes to keep the AOD image visible.

In tap to wake mode, the notification will only be visible when you tap to wake.

This is being investigated for possibilities.