The nickel binary is 5M, so if you replace it with a shell script and then make a firmware update (bye your shellscript), you've wasted 5M of the internal memory. Now, there is ~100M free internally which seems like a lot, but... and then you still have the issue that all mods have to cooperate on this somehow.
It might still come to that, depending on which ways Kobo decides to break this mod in the future.
Quote:
|
Yes to all: Aura H2O, 3.18.0, English, scanline mode, kobo sleep screen is plain "Sleeping" displayed on white background.
|
If the screensaver is displayed _before_ the Kobo ever displayed "Sleeping" then you have the wrong signature. With scanline mode there should be no race as it's supposed to react only after Kobo already displayed "Sleeping". [And as far as I'm aware Kobo does not display "Sleeping" twice]. If the screensaver is not displayed at all, then it could be either wrong signature or wrong delay.
I'm still hoping to find a way to improve the scanline method, right now it's impossible to tell what the signature stands for, so it's easy to pick the wrong one.
As for delay, smaller delays work better for scanline mode, so try delay=0.1 0.1 0.1 0.1 0.1