K5 FW 5.x ScreenSavers Hack

[kalyy]

I tried last image, cover and cycle mode and they all work. But random mode doesn't work, it just stays in cycle mode. Should it work on fw 5.7.2? Thanks!

[knc1]

Originally Posted by kalyy

I tried last image, cover and cycle mode and they all work. But random mode doesn't work, it just stays in cycle mode. Should it work on fw 5.7.2? Thanks!

Do you restart the framework after changing modes?

[NiLuJe]

@Mike_73: You're possibly reading KFX titles, in which case, use the snapshot version of the hack.

@kalyy: As @knc1 mentioned, the shuffling process is done when the hack starts up (which normally is at boot, or during a framework restart triggered from KUAL).

[kalyy]

Yes I did a framework restart and also a device restart.
I just try it again kual->Screen savers->Restart framework now
And configurations->Restart
Whith the device restart I see the "S randomizing screensavers..." message and when I did the framework restart it showed a message in white letters for less than a second.

[NiLuJe]

@kalyy: The you misunderstood the behavior of the hack. it simply reshuffles the order in which the images will be shown, but it's still a cycle from 0 to 100, it's just that 'n' might not point to the same picture between two different boots.

[XXCoder]

;dm gonna try that.

Wonder if you could add "custom picture" that has picture # and reason it failed? and cache THAT so screensaver cycle stays working?

I will check into usbnetwork too, thanks.

[NiLuJe]

@XXCoder: Not feasible. Can't (easily) predict how the framework will handle some files .

At best you could play with parsing identify's output to look for common issues, but, again, the best place to do that is outside the Kindle .

[Yolina]

Is there a size limit after which the PW3 isn't happy? I resized my previously-used-on-PW2 images to the larger PW3 resolution and for some reason the PW3 doesn't like one of them - at the new res, it's 1.93MB whilst all the others (working fine) are between 300KB and 1.6MB

[knc1]

Any chance the conversion made other changes?
Such as from PNG8 to indexed grayscale - or any other such 'invisible' internal changes.

[Yolina]

I don't think so - I did exactly the same for all the images, and it's just this one the PW3 isn't happy with. I'll try the resize again later today just in case and see what happens.

[knc1]

Are the PW-2 and PW-3 both running the same firmware version?

Why?
During the lifetime of the PW-2 there was a png library version change, which may or may not be the problem here.
The PW-3 has only used the new(er) png library.

Otherwise -
You may have just discovered a limitation of the ss display.

[Yolina]

The PW2 is still on 5.4.5.1; PW3 on 5.7.2.

All the other images I was using on the PW2 work fine on the PW3 at the new res

[knc1]

Originally Posted by Yolina

The PW2 is still on 5.4.5.1; PW3 on 5.7.2.

All the other images I was using on the PW2 work fine on the PW3 at the new res

and size?

Your PW-2 uses the old libpng, your PW-3 is using the new libpng.
That is one certain difference.
But if it is the cause of this inablity to handle the large file, I can't say.

[Yolina]

I've resized again from the original, and same problem.
That image was obviously smaller on the PW2, around 1MB.

Ah well, one of those things I guess.

[knc1]

Originally Posted by Yolina

I've resized again from the original, and same problem.
That image was obviously smaller on the PW2, around 1MB.

Ah well, one of those things I guess.

You could try reducing the shades of gray - that should make the file smaller.
If it works, then it is indeed the file size that is the problem on the PW-3.