Random Screensaver Image

[mobilemoxie]

Ok. I see from the earliest posts in this thread the size is quite a bit larger than what I was using.

Also, any way to get rid of the "sleeping" and "powered off" words that appear on screen so only the images appear?

[frostschutz]

if your image is large enough and not transparent in that area, the image will replace it

[mobilemoxie]

Thank you!

Best image size as you specified way back on page 1 of this thread is:

1080 x 1440

And here's one of the screensaver images on my Kobo

[leonmoonen]

Just wanted to report another successful install of KoboRoot-ScreenSaver-20181216.zip on a Kobo Forma with firmware 4.12.12111 (and some patches)


Some things that may help other people in getting it to work:
- it took me a great number of sleep and power-off cycles (I'm guessing 8-10) before both modes were successfully scanned, i.e. don't give up/uninstall, just use your reader and it may start to work after a while
- especially the power-off scanline took a long time to register after the actual power-off event (I probably was too impatient on the initial cycles)
- sleep and power-off via the timed events (in settings) seemed to work better than via power button presses, I used sleep after 5 mins, power-off after 10.
- for the Forma, full screen images should be 1440x1920

My scanlines, for possible reuse (I checked and these are the same as the ones posted by @MGlitch for his Forma, so reusability seems likely, esp on the same firmware):

Spoiler:

standby=1649:ffffff000000ffffff000000fffffff5f5f5000000636363ffffffd5d5d57878781b1b1b0000002a2a2a7e7e7edadadaffffffd5d5d57878781b1b1b0000002a2a2a7e7e7edadadaffffffecececcbcbcbaaaaaa898989686868474747262626050505000000777777fffffff5f5f58585851515150000002a2a2a989898ffffffe2e2e2c2c2c2a2a2a2838383636363434343232323030303000000686868fffffff5f5f5d3d3d3b1b1b18f8f8f6e6e6e4c4c4c2a2a2a080808000000636363fffffff2f2f2767676222222000000030303656565e5e5e5ffffffb8b8b8505050050505000000020202535353a4a4a4f6f6f6f9f9f9ffffff

poweroff=1649:0000000a0a0affffff5555550000001c1c1cffffff202020000000575757b5b5b5ffffffcacaca6d6d6d1010100000000707070000000707070000002a2a2a878787e4e4e4ffffffd5d5d58181812525250000000a0a0a2c2c2c4e4e4e707070919191b3b3b3d5d5d5f7f7f7ffffff9c9c9c000000141414888888f4f4f4ffffffc1c1c11919190000002a2a2a878787e4e4e4ffffffd5d5d58181812525250000005a5a5ab5b5b5ffffffebebebacacac494949000000202020ffffff919191000000575757b5b5b5ffffffcacaca6d6d6d1010100000000707070a0a0affffff9797970707070000000707070a0a0affffff979797070707000000

Finally, @frostschutz: when the scanline for sleep/standby was already registered in screensaver.cfg but the one for power-off wasn't detected yet, I still got scanlines when the device went into sleep mode (before going into power-off). This is not a big problem but it was unexpected, so I thought it might point at something special in the Forma context? Although I saw the scanline on the screen, the actual code for standby in screensaver.cfg was not changed/added (at least the time-stamp in the corresponding comment wasn't).

[frostschutz]

Originally Posted by leonmoonen

Finally, @frostschutz: when the scanline for sleep/standby was already registered in screensaver.cfg but the one for power-off wasn't detected yet, I still got scanlines when the device went into sleep mode (before going into power-off). This is not a big problem but it was unexpected, so I thought it might point at something special in the Forma context? Although I saw the scanline on the screen, the actual code for standby in screensaver.cfg was not changed/added (at least the time-stamp in the corresponding comment wasn't).

The thing is, I simply don't have a reliable method to detect standby/poweroff anymore. Not without going deeper into the rabbit hole, anyway, i.e. without LD_PRELOAD or outright patching of things. Which I want to avoid, since it would make the mod very firmware dependent (patches have to be re-done all the time).

So, screensaver addon doesn't KNOW AT ALL you're going into standby, or poweroff, or what. That's why the roundabout method of using a scanline in the first place. I have to look at the screen contents in order to be able to tell what is happening.

What I do know is when the reader was rebooted (due to service restart, time discrepancy, etc.). So what the addon does for the poweroff scanline is... keep detecting scanlines. And after reboot, simply use the last scanline that was done and assume it happened just before poweroff. So that's the poweroff scanline for you, and that's why it keeps on doing the scanline thing, it's just waiting for that poweroff to actually happen at some point.

It's a hack, a very roundabout method to do things, but - once the correct values are found - it works. Yay

Thanks for your feedback

so reusability seems likely, esp on the same firmware

Same firmware (sometimes across firmwares if they didn't change the sleep screen any), same language, and if there are any patches regarding borders, system font (sizes), etc. If it changes a single pixel in the scanline row, you need new values unfortunately...

[Mingyar]

Hello all,

Someone could give the config file for the Aura One and firmware 4.12.12111 ?

Thanks in advance.

Finally, I got it by myself, after so many sleep/awake, turn off/on.

If it can help,
For Mini in 4.12.12111

#
# Standby scanline autodetected Sat Feb  2 04:14:26 CET 2019
#   If this value does not work, remove it so it will be re-detected.
#
standby=677:ffffffd1d1d19b9b9b2525250000007070709c9c9ca7a7a7abababa0a0a08585854a4a4a000000ffffffececec7b7b7b000000808080e6e6e6ffffffeeeeee7b7b7b000000848484dcdcdcffffff171717000000ffffff3d3d3d000000030303040404000000333333ffffffebebeb7a7a7a0000007a7a7ad7d7d7ffffffe5e5e5696969000000747474d4d4d4ffffffe5e5e5696969000000747474d4d4d4ffffff3d3d3d000000030303040404000000333333ffffff


#
# Poweroff scanline autodetected [1] Sat Feb  2 14:54:42 CET 2019
#   If this value does not work, remove it so it will be re-detected.
#
poweroff=677:0000002e2e2e646464dadadaffffff8f8f8f6363635858585454545f5f5f7a7a7ab5b5b5ffffff000000e3e3e3ffffff090909000000c2c2c2fffffffcfcfcfbfbfbffffffcccccc000000141414858585ffffff858585282828000000131313848484ffffff7f7f7f191919000000111111848484ffffff7b7b7b232323000000e3e3e3ffffff090909000000

For H2O original in 4.12.12111

#
# Standby scanline autodetected Sat Feb  2 03:40:28 CET 2019
#   If this value does not work, remove it so it will be re-detected.
#
standby=1231:fffffff4f4f40000001d1d1dffffff030303000000f6f6f6fffffff5f5f5cfcfcfaaaaaa8585856060603a3a3a151515000000c5c5c5ffffff9999993737370000001515156b6b6bd6d6d6fffffff6f6f6fffffff6f6f6fffffffcfcfc8383833333330b0b0b0000001e1e1e616161c7c7c7ffffffe5e5e5c2c2c29f9f9f7b7b7b585858353535121212000000c6c6c6fffffff4f4f4000000c6c6c6fffffff4f4f4000000c6c6c6fffffffcfcfc8383833333330b0b0b0000001e1e1e616161c7c7c7ffffff


#
# Poweroff scanline autodetected [1] Sat Feb  2 03:47:10 CET 2019
#   If this value does not work, remove it so it will be re-detected.
#
poweroff=1231:0000000b0b0bffffffe2e2e2000000fcfcfcffffff090909000000090909ffffff3a3a3a0909090000000303037c7c7cccccccf4f4f4ffffffe1e1e19e9e9e3838380000001a1a1a3d3d3d606060848484a7a7a7cacacaedededffffff3939390000000a0a0a3030305555557a7a7a9f9f9fc5c5c5eaeaeaffffff3a3a3a000000666666c8c8c8ffffffeaeaea949494292929000000090909ffffff3a3a3a090909000000

For Aura One (LE) in 4.12.12111

#
# Standby scanline autodetected Sat Feb  2 05:47:56 CET 2019
#   If this value does not work, remove it so it will be re-detected.
#
standby=1604:fffffff5f5f5000000aaaaaaffffffe5e5e5000000f8f8f8ffffffe3e3e39797970c0c0c000000636363d7d7d70000001616164040403e3e3e030303000000d9d9d9fffffffdfdfdadadad2f2f2f0000005c5c5ca8a8a8d8d8d8ffffffe2e2e28f8f8f1111110000001d1d1d8f8f8fffffff7272720000006f6f6fffffff7e7e7e000000bebebeffffffe8e8e8adadad656565000000686868fffffff5f5f5000000636363fffffff5f5f5000000636363ffffff7272720000006f6f6fffffff7e7e7e000000bebebeffffff


#
# Poweroff scanline autodetected [1] Sat Feb  2 14:12:01 CET 2019
#   If this value does not work, remove it so it will be re-detected.
#
poweroff=1604:0000000a0a0affffff5555550000001c1c1cffffff070707000000515151fffffffdfdfd0000008d8d8dffffff909090000000818181ffffff4141410000001717175252529a9a9affffff9797970000001c1c1c686868f3f3f3ffffff9c9c9c282828ffffffe9e9e9bfbfbfc1c1c1fcfcfcffffff262626000000515151fffffffdfdfd000000

[Mingyar]

For thoose who like the same kind of images than me, here are some links.
49 pictures. The poweroff version is the same than standby version but textured.
The links will be destroyed after one month without any download.
H2O_1080_1430.zip
Mini_600_800.zip
One_1404_1872.zip

[Mingyar]

Hi frostschutz, I use the screensaver with a great pleasure.

May I suggest an evolution ?
I use a pin code to activate my Kobo.
When I turn it on or awake it, I have to type my code. If I decide to go back to sleep before I type all the code, the screen turn to blank but not to an image.

Do you think you can adapt your script ?
Hope I'm clear ...

[frostschutz]

Originally Posted by Mingyar

When I turn it on or awake it, I have to type my code. If I decide to go back to sleep before I type all the code, the screen turn to blank but not to an image.

I've never used the pin code before... unfortunately, at first glance there does not seem to be an easy fix for this.

[Mingyar]

Thanks for your quick answer.
If you can do something one day, it will be good, but don't worry about it.

[IanScuffling]

I just acquired an Aura HD this week and was happy to find this excellent thread. But I can't get it to work.

I've turned off the book cover as screensaver, downloaded the 12-18-2018 package, placed the KoboRoot-ScreenSaver-20181216.tgz file in Kobo/.Kobo, ejected the device, and gone through multiple sleep and power off cycles. I see the .addons folder with the png files, but they don't display.

I've then set the screensaver cfg file to uninstall, and redone the entire process.

I'll keep doing the sleep and power off things and see if the images appear, but I'd welcome any suggestions.

Edit: Am running firmware 4.12.12111.

Matt

[spoonm]

Originally Posted by IanScuffling

I just acquired an Aura HD this week and was happy to find this excellent thread. But I can't get it to work.

I've turned off the book cover as screensaver, downloaded the 12-18-2018 package, placed the KoboRoot-ScreenSaver-20181216.tgz file in Kobo/.Kobo, ejected the device, and gone through multiple sleep and power off cycles.

Just to be sure: you did rename the file to KoboRoot.tgz inside the .kobo directory, right? Also, set the device to sleep/poweroff on timeouts, it seems to be more effective than putting it to sleep/powering it off manually. If you see the line, that'd mean it's working.

[IanScuffling]

Originally Posted by spoonm

Just to be sure: you did rename the file to KoboRoot.tgz inside the .kobo directory, right? Also, set the device to sleep/poweroff on timeouts, it seems to be more effective than putting it to sleep/powering it off manually. If you see the line, that'd mean it's working.

Yes, I renamed the file to KoboRoot.tgz inside the .kobo directory. Sorry I didn't make that clear.

And I let the device go to sleep and then power off. I have not seen the line. Weird. Will give it more thought.

[Mingyar]

If it helps, for my 3 Kobo readers, I almost lost patience before I finally had the expected success. I didn't count the sleep and stop times before the images finally appeared.

Originally Posted by Mingyar

If it helps, for my 3 Kobo readers, I almost lost patience before I finally had the expected success. I didn't count the sleep and stop times before the images finally appeared.

Agreed... I went spastic reinstalling, redoing, trying everything. Took untold number of sleep/power cycles to start working, but eventually did, and now does so reliably, so I'm very grateful for this hack. Have the Clara HD, and the only weird thing is that my 'line' is diagonal across the left upper corner area, but the picture then fills and looks great. It is possible, as stated above, that the best thing is to set a 5min timeout, and just let it keep cycling naturally.