K5 FW 5.x ScreenSavers Hack

[NiLuJe]

You only need Python for KFX support in *cover* mode, and that's Python 2, not 3 (i.e., filename is Update_python_*.bin).

And, of course, you need the actual ScreenSavers hack itself, not just Python.

[Hundebub]

Ok, thank you!
How do I completly uninstall the Python 3 from my kindle? The uninstall.bin only doesn't work on Python 3 (only on 2)?
I would like to fresh install Python 2 again and then the ScreenSavershack itself, maybe that helps.

[NiLuJe]

The uninstall package will uninstall both. Keeping both version installed is completely harmless, though.

A fresh install of the ScreenSavers hack *is* a good idea, though. Do uninstall it and *then* manually remove the linkss folder to achieve that.

[russbus64]

Just made an account just to let you know this hack is great! I have a PW2 and I finally decided to get the Special Offers removed, jailbreak the thing, and add this hack. I'm a little jealous of the newer Kindles with a similar feature and this will help tide me over until there's a semi-decent reason to upgrade to a newer model.

I actually misread the instructions at first and didn't install Python. Thankfully it worked after installation and being patient for a few moments after opening a book.

[NiLuJe]

Yeah, Python is only necessary for KFX support these days .

[dream_state]

Hi,
So I've hacked my PW4 with Kindlebreak but I'm unable to install packages through KAUL. So instead I put the screensaver hack in mrpackages and installed it using ;log mrpi. I get the new screensaver saying "you've successfully installed the hack" but when I go to change the settings in KAUL to either cover or last screen nothing happens. Is it my KAUL install or screensaver hack causing the issue? ��

[mergen3107]

cover mode requires python package as well. You can find it in the NiLuJe’s Snapshots

[dream_state]

Originally Posted by mergen3107

cover mode requires python package as well. You can find it in the NiLuJe’s Snapshots

I have installed python already

[NiLuJe]

Possibly incomplete JB. Hard to say without logs.

[LostOnTheLine]

What's the latest version of the Screensaver hack? I've seen newer pages online saying to use "kindle-linkss-0.24.N-r13390.tar" & older ones saying to use "kindle-linkss-0.24.N-r14393.tar" & "kindle-linkss-0.25.N-r18509.tar" & Somewhere else that says "kindle-2.5-screensaver-hack-0.4.zip" The page that says it has the most updated things links to "kindle-linkss-0.24.N-r14393.tar". I'm re-doing my PW1 because KoReader stopped opening ePubs, & I can't figure out which is the current best one. Help please

[NiLuJe]

Don't trust third-party documentation to tell you anything accurate or up-to-date, and always use the links from the Snapshots thread.

[Jorvik]

Amazing hack and so simple to implement. Anyway to get the screensaver to automatically load a different image after X amount of time? (e.g. every hour) Sorry if I've missed this in the comments. Thanks

[NiLuJe]

Nope, because the device is asleep.

[AlanHK]

I have PW3 running 5.10.3 Installed KUAL and screensaver.

I've had this problem a few times:

Originally Posted by NiLuJe

Q. Get the last thing shown on screen (or a blank screen on FW 2/3/4) in cycle mode, either straight-away or after a few working custom images?

Saw your answer:

Originally Posted by NiLuJe

A. One of the files in your screensaver pool upset the Kindle firmware . That rarely happens on FW 2/3/4 (you're much more likely to see a corrupted image, rather than breaking the whole thing, which is what happens on FW 5.x: once it fails in this way, only a reboot will make the framework try again, even if the next file in the cycle is okay, the framework just appears to give up on screensavers), but on FW 5.x, that means checking the size, format, resolution of each and every file in your pool, to see if it matches the device, and really is a PNG8 (256c) (optionally properly dithered down to 16 colors, but not indexed to 16c), without any embedded ICC profile.

That may diagnose it, but doesn't tell me what to do about it.
It means a cover image in the cache is bad?

I used the Screensaver "Clear cover cache" and rebooted.
Opened some of the same books, same problem, just showing last screen, not covers.
Cleared cache and rebooted: same problem. Cleared and rebooted: now it seems fixed????

Why are there bad images? How can they be (apparently, touch wood) good now?

[NiLuJe]

Originally Posted by AlanHK

That may diagnose it, but doesn't tell me what to do about it.

It kinda does: either remove it, or re-encode it properly.

The cache only applies to Cover mode. Cover mode will *never* generate broken images. That excerpt applies to user-provided content in cycle mode .