[Samsung Galaxy S10 Themes, Apps, and Mods] Chainfire:
Not right now, no. Currently I would have to wake the CPU to do this, unless we blink only once per minute, which kind of defeats the purpose. I do have a lead on possibly making this work, but that's future stuff. First things first.

(also [MENTION=5710513]Duncan1982[/MENTION] )

One can never receive enough praise :)

I am however not planning on doing any more root development. I keep some of my apps somewhat updated (but not extensively so) and I support my open source root libraries just out of interest, but the development of root itself is extremely time-consuming. Don't underestimate the effort John has put in just for the S10, it was certainly not a trivial task, and even if the outcome is not ideal one should respect his effort. I have not kept up with the details on the internal workings (and my knowledge on this subject is very quickly becoming obsolete), but assuming I can do a better job at it or that a better implementation is even possible on the S10 is just that, an assumption.

As I no longer really root my daily drivers (which the S10 is) it also wouldn't bring me anything. I did develop SuperSU originally both out of interest and because I wanted to fix issues with my other apps that used root, but eventually it just turned into a job. A job I no longer have, or wish to have, as my excitement for the subject matter has dwindled (and I no longer have a lot of root apps that I wan't to push that need it). That and the pressure of demanding users, which tends to cause me to overwork myself (I know that's a me problem, but it is what it is). Yes, I am annoyed with the lack of access on unrooted Android, but no longer to the point that I will work to fix it. Root has lost significant marketshare over the years too, and I feel we've pretty much lost the battle for device control for the masses.

And even if I did have interest to do something like that again, note that I don't have any legal rights to SuperSU any more, so I'd have to go from scratch, and then it'd still be a questionable affair legally.

In short, the chance of me doing anything like that again is essentially zero.

Keep in mind that this app is free and open source precisely because I do not want to feel responsible for its continued operation too. Once I'm done implementing the basic feature-set and it works, then it's done, and people who want more will have to send me pull requests.

See below.

Also see my reply here: https://xdaforums.com/showpost.php?p=79313160&postcount=425

The % battery use seen there is only relevant if measured solely when the screen is on. When the screen is off, that measurement stops making sense as other factors (such CPU or screen having power at all) come into play. Actions that Holey Light performs may influence other system components that would otherwise have a different footprint. The only correct way to measure is running for many hours with, and without, Holey Light, and measuring the difference in battery use, charging to 100% in between (as different levels degrade at different rates due to how batteries work and the % not being truly linear).

As for point (2), I don't think the electrical current used to light up the screen is actually counted here, only the CPU. And even then, it is imprecise.

And (3), Holey Light actually never wakes up Android from deep sleep. It runs in the cycles that the system/AOD has already woken up the CPU for. But to nuance that, if using anything but the "Unholey Light" animation style, it may keep the system awake using indirect methods. It may specifically wake the system up to respect AOD/DND/custom schedules, but that would be a few seconds per hour, and wouldn't be noticeable in any charts.

Note that AOD wakes the CPU for a few seconds at least once per minute. Which gives us ample time to process events.

Other than helping me test if your use-case still works without issue, no. I would upgrade to the next Play-release, though.

With the screen off ? 0.66% battery use per hour for AOD is fine/expected.

The option is there still, and will continue to be there going forward. v0.55 is mostly a test release to see if the implementation of that ring works right for everyone.