Random Screensaver Image

[Bean_There]

Wow that's great to hear Frostschutz.



If you need any testing done on a GLo HD let me know, more than happy to do it.

Cheers

[kobayashi]

Originally Posted by frostschutz

I'm planning to update this mod, perhaps this weekend. Well, remind me if I don't.

The tool I use to display images (pngshow) is a dirty hack I wrote myself. It doesn't hold a candle to NiLuJe's so much better fbink tool. It has better compatibility with Kobo devices and it's also lightyears faster to bring the image to the screen. And with fbink it will also be possible to display debug messages on screen - that alone should help to understand what the heck is going on.

What that doesn't fix is the scanline approach itself. I still haven't found a more reliable way to detect that the reader is going into standby (or going to shut off power).

Great news. Have a KA1 now and will have a Forma soon to test on.

[frostschutz]

This uses fbink instead of pngshow to display scanline and image. (No fancy debugging yet - sorry.)

You have to re-detect scanline for this version. Remove old scanline value from screensaver.cfg, then let the device drop into standby, and from standby into poweroff. (Wait some time between those steps. Scanline detection takes a few seconds, and if you just rebooted, some seconds before the mod is even active.)

My H2O is using 4.8.11073 firmware, and detected these scanlines:

#
# Standby scanline autodetected Sat Oct 27 18:18:56 CEST 2018
#   If this value does not work, remove it so it will be re-detected.
#
standby=1231:ffffff000000c2c2c2ffffff949494000000fdfdfdfffffff4f4f4000000c6c6c6fffffffcfcfc8383833333330b0b0b0000001e1e1e616161c7c7c7fffffffcfcfc8383833333330b0b0b0000001e1e1e616161c7c7c7ffffffedededc9c9c9a4a4a48080805c5c5c373737131313000000cececeffffff9d9d9d4141410505050000000707072e2e2e787878f0f0f0ffffffe5e5e5c2c2c29f9f9f7b7b7b585858353535121212000000c6c6c6fffffff5f5f5cfcfcfaaaaaa8585856060603a3a3a151515000000c5c5c5ffffff9999993737370000001515156b6b6bd6d6d6ffffffa7a7a74848481010100000001a1a1a666666c2c2c2f7f7f7ffffff


#
# Poweroff scanline autodetected [1] Sat Oct 27 18:19:17 CEST 2018
#   If this value does not work, remove it so it will be re-detected.
#
poweroff=1231:0000000b0b0bffffffe2e2e20000001b1b1bffffff7a7a7a0000005050509f9f9fe9e9e9ffffffdfdfdfb8b8b84f4f4f0000000909090000000909090000000909090000000303037c7c7cccccccf4f4f4ffffffe1e1e19e9e9e3838380000000a0a0a3030305555557a7a7aa0a0a0c5c5c5eaeaeaffffff393939000000313131979797edededfffffff8f8f89191910000000303037c7c7cccccccf4f4f4ffffffe1e1e19e9e9e383838000000282828969696d5d5d5fbfbfbfffffff6f6f6d2d2d2a8a8a8434343191919ffffff3434340000005050509f9f9fe9e9e9ffffffdfdfdfb8b8b84f4f4f0000000909090b0b0bffffff3939390909090b0b0bffffff393939090909000000

[MGlitch]

No joy on my forma running 4.11.11911
fbset.txt has this:

mode "1440x1920-0"
# D: 0.006 MHz, H: 0.004 kHz, V: 0.002 Hz
geometry 1440 1920 1440 3840 16
timings 160000000 36 248 4 8 52 1
accel false
rgba 5/11,6/5,5/0,0/0
endmode

screensaver.example.cfg

appears unchanged with:

# ScreenSaver config

#
# uninstall (Default: 0)
# Set to 1 if you want to uninstall ScreenSaver after the next run.
#
uninstall=0

#
# standby / poweroff (Default: unset)
# Scanline offset and pattern to look for when standby/poweroff.
# This will be detected automagically and appended below.
#


this was after

1) installing the mod
2) unplugging forma
3) setting sleep/power off to 5/10 mins respectively
4) allowing the device to sleep/power off

I had tried installing previous versions, but ran the uninstall for them. I also went as far as to remove the screensaver folder within .addons which was reinstalled by installing the fbink experiment.

[frostschutz]

Interesting to see that the Kobo Forma is using RGB565 again, when they switched from RGB565 to RGBA for H2O and other models. I'd have to downgrade firmware to test if RGB565 works with fbink... (I guess it would, but I don't know)

Thanks for testing in any case, even if it didn't work. So I have to add debugging to know what's going on, no way around it. Sorry I didn't make it for this version.

[MGlitch]

No worries about not adding debugging. I’m just glad this mod is getting looked at again.

[MGlitch]

I have to correct myself. I have this working now.

The only thing I can think of is that I power cycled it again, then forced it into sleep and again power off.

Happy day callooh callay!

Now I just need to tweak the image I want as a screensaver to properly display (the dimensions are off so it's a bit funky).

Thanks again for your work on this mod!

[frostschutz]

Great to hear.

Does it still work after connecting to PC? Currently the mod is designed to just quit on PC connection, and then later re-start itself on disconnect - and perhaps this is not working on other models.

The mod would be inactive for ~15s after disconnecting from PC, so if you go to sleep right after pulling the USB plug, it would be "normal" for no image to show up (yet)

Also out of interest, post the cfg entry it generated.

[MGlitch]

As near as I can figure yes. Initial install was followed by disconnect from USB then >5mins to natural sleep, followed by natural power off.

After that I'd left it for a tick, and noticed it was drawing the scanline when I forced it to sleep. Then it drew a bit of one of the images, so I tried waking > forced sleep again and it drew all of another.

Then I forced power down, it drew scanline and drew one of the power off images.

I have not tested the 15 second thing, but it continues to work after I replaced the image file for both sleep and power off.

I have not tested if it'll display when it naturally falls asleep or powers off post getting this to work. I can do that if you want, but my suspicion is that it will work.

[NiLuJe]

*Wilhelm scream*

Nooooo, not RGB565 again :'(.

Unless that's caught during an image drawn by pickel, because pickel does drop back to 16bpp. Can't remember what's actually drawn via pickel, though... -_-".

Kidding (almost) aside, the only thing I'm not sure won't horribly blow up on the Forma is rotation, it entirely depends on how they implemented that on the Forma.

If you have shell access, see this post for more details .

[MGlitch]

Originally Posted by NiLuJe

*Wilhelm scream*

Nooooo, not RGB565 again :'(.

Unless that's caught during an image drawn by pickel, because pickel does drop back to 16bpp. Can't remember what's actually drawn via pickel, though... -_-".

Kidding (almost) aside, the only thing I'm not sure won't horribly blow up on the Forma is rotation, it entirely depends on how they implemented that on the Forma.

If you have shell access, see this post for more details .

No shell access

But it respects the rotation for portrait mode displaying right side up for whichever way the Forma was before going to sleep. I’ve not tested landscape since I don’t intend to ever use landscape.

[frostschutz]

Originally Posted by NiLuJe

Unless that's caught during an image drawn by pickel,

it waits for nickel to start, then it waits another 5 seconds for good measure, then it waits for nickel to put its feelers into affiliate.conf (that's how it detects sleep/poweroff), and only then it grabs the fbset.

So ... no it's not from early bootup. And I assume the standby/poweroff screen isn't displayed by pickel, or that would be a so much better way to hook into things than the stuff I'm doing right now

@MGlitch: does landscape mode extend to the sleep/poweroff screen? scanline would not detect for different rotations then... same if it rotates screen 180° unless the rotation is transparent to /dev/fb0 ...

[NiLuJe]

@frostschutz: I can't remember the exact timing, but I seem to remember Nickel actually changing the modeset fairly late, so there may be a chance that's still the pickel modeset from the three dots progress bar (he said, wildly hoping they didn't switch back to a crappy pixel format) ;D.

EDIT: Whee, I completely misread that. Yeah, probably not pickel's modeset :/.

Looking at the FS, only the progress bar, update, reboot & factory reset screens are drawn by pickel...

EDIT²: You could log fbink's stderr, that'll contain the modeset it detected .

@MGlitch: Eh, that's a good start (& news), thanks .

[frostschutz]

well if you have any doubts you can delete fbset.txt while connected to pc and then unplug, standby, replug and grab the new fbset.txt (check file date to see it was new created) but I doubt the contents would change :-)

[NiLuJe]

Yeah, previous message edited, I, err, misinterpreted most of what you said, oops .