Random Screensaver Image

[Limalimlim]

ok, thank you. I'll try that :>

[stevenam]

I just successfully installed this mod on KA1. I think the trick after step 3 is directly delete all code in the config file, then do step 4 and 5. It will save time.

[kobayashi]

The screensaver hack is broken in the new firmware update. I can get the scanlines but no screensaver.

[frostschutz]

It still works for me...

[kobayashi]

Originally Posted by frostschutz

It still works for me...

I've tried resetting the hack multiple times and it produces scanlines and saves them but the image never shows.

I'll try resetting the values again and report back.

EDIT: OMG, it finally worked. I tried deleting the scanline settings and redetecting them but that didn't work. I then uninstalled and reinstalled but it still didn't work. I then uninstalled and reinstalled a second time and the screensavers worked. Each time I went to standby and poweroff 3 times to be sure that the values were stored. FWIW, I'm using XP and EditPad Lite 7.

[MGlitch]

This doesn't seem to work on the newest firmware for the ka1 (4.2.8283). I'd had a previous version installed and that displayed duplicate images in the top two quarters of the screen. I reinstalled the mod and now it just doesn't display anything.

Any chance of an update?

[frostschutz]

Is this on the H2O (as in your profile) or do you have a KA1? 4.2.8283 comes with a kernel/framebuffer pixel format change, which pngshow won't know how to handle so you either get no images or glitched images. But as far as I'm aware this kernel/firmware doesn't run on the H2O so I can't test it myself. I don't have a KA1 and no plans to buy one.

[MGlitch]

I'm using a KA1, just been too lazy to update the profile. I'm willing to test, but I'm essentially limited to 'it didn't work' or 'it did work'. If the scanline mode in the autodetect works like it did when we controlled it, the line appears to be in the opposite corner from where it should be.

To make that clear it should be in the lower left corner, but I'm seeing a brief line in the upper right corner.

If it would help I could post what's in the config file.

[frostschutz]

Hmmm. Okay. I'm flying blind here, but there you go. Let me know what happens. (remove previously detected standby/poweroff from .addons/screensaver/screensaver.cfg & then let it re-detect those).

[kobayashi]

Originally Posted by frostschutz

Hmmm. Okay. I'm flying blind here, but there you go. Let me know what happens. (remove previously detected standby/poweroff from .addons/screensaver/screensaver.cfg & then let it re-detect those).

On my KA1, the standby and poweroff were finally detected after a few tries at each but the screensaver never loads.

Is this working for anyone else with the new firmware?

[frostschutz]

@kobayashi: So the scanline showed up properly? What's in your .addons/screensaver/screensaver.cfg?

If scanline works properly but images don't show, that'd be pngshow not working properly. It has to work partially though, otherwise scanline wouldn't show either. Hmmm.

[kobayashi]

Originally Posted by frostschutz

@kobayashi: So the scanline showed up properly? What's in your .addons/screensaver/screensaver.cfg?

Yes:

#
# Poweroff scanline autodetected Tue Jan 24 09:22:12 EST 2017
# If this value does not work, remove it so it will be re-detected.
#
poweroff=1672:ff000000*ff929292ffffffff*fff5f5f5ff 000000*ff5b5b5bffffffff*ffe0e0e0ff000000*ff565656f fb0b0b0fff8f8f8ffffffff*ffb4b4b4ff5d5d5dff000000*f f4d4d4dffadadadffffffff*ff949494ff000000*ffd5d5d5f fecececffffffff*fff5f5f5ff000000*ff3f3f3fffe4e4e4f fffffff*ffa2a2a2ff000000*ff020202ff616161ffc1c1c1f ffdfdfdffffffff*fffcfcfcffa3a3a3ff4b4b4bff000000*f f242424ff7d7d7dffd7d7d7ffffffff*ffefefefff6e6e6eff 000000*ff5d5d5dffe8e8e8ffffffff*ffd0d0d0ff323232ff 000000*ff020202ff616161ffc1c1c1fffdfdfdffffffff*ff fcfcfcffa3a3a3ff4b4b4bff000000*ff5a5a5affbebebefff dfdfdffffffff*ffe5e5e5ffa5a5a5ff474747ff000000*ffe eeeeeffffffff*ff000000*ff565656ffb0b0b0fff8f8f8fff fffff*ffb4b4b4ff5d5d5dff000000*ff6c6c6cffffffff*ff 3c3c3cff000000*ff6c6c6cffffffff*ff3c3c3cff000000*


#
# Standby scanline autodetected Tue Jan 24 09:31:12 EST 2017
# If this value does not work, remove it so it will be re-detected.
#
standby=1672:ffffffff*ff818181ff000000*ffcfcfcffff fffff*ff979797ff000000*ff5f5f5fffffffff*ff989898ff 000000*ffdcdcdcffffffff*fffdfdfdff9e9e9eff3e3e3eff 020202ff000000*ff030303ff5c5c5cffb4b4b4ffffffff*ff fdfdfdff9e9e9eff3e3e3eff020202ff000000*ff030303ff5 c5c5cffb4b4b4ffffffff*ffe8e8e8ff8c8c8cff2f2f2fff00 0000*ff1b1b1bffc7c7c7ffffffff*ffcfcfcfff5c5c5cff02 0202ff000000*ff0d0d0dff6e6e6effddddddffffffff*ffcd cdcdff717171ff161616ff000000*ff131313ffb4b4b4fffff fff*ffdbdbdbff828282ff282828ff000000*ff1d1d1dffb2b 2b2ffffffff*ff8e8e8eff1d1d1dff000000*ff373737ffaba babffffffff*ffb6b6b6ff535353ff090909ff000000*ff141 414ff373737ff7c7c7cffd4d4d4ffffffff*fffafafaffa5a5 a5ff515151ff000000ff454545ffffffff*

[frostschutz]

RGBA but A is the first byte? Okay. I hate byte order issues.

Does this change anything?

This experiment2 should also create a .addons/screensaver/fbset.txt, please post it.

If you have a shell, you can try this directly:

# fbset
# /usr/local/ScreenSaver/pngshow /mnt/onboard/someimage.png
# echo $?

Thanks for testing.

[kobayashi]

Screensaver not working with ex2 file. Not sure what a shell is but here is the fbset.txt:

mode "1404x1872-45"
# D: 133.404 MHz, H: 84.380 kHz, V: 44.835 Hz
geometry 1404 1872 1408 3840 32
timings 7496 44 89 4 5 44 1
accel false
rgba 8/16,8/8,8/0,8/24
endmode

[frostschutz]

Hmmm, no big surprise there. Not sure what else to try right now, sorry.