K5 FW 5.x ScreenSavers Hack

[NiLuJe]

Yup, PW1.

So you were indeed the wrong file, which explains everything .

EDIT: *insert favorite "evil laugh" track here* ;p.

[GoSharks]

Originally Posted by ManyManyBooks

It is:

BO24

Yep...PW1 wifi. Use the other PW install .bin file.


edit - *grumble, grumble* What NiLuJe said (again!)

[ManyManyBooks]

Originally Posted by GoSharks

Yep...PW1 wifi. Use the other PW install .bin file.


edit - *grumble, grumble* What NiLuJe said (again!)

Oops...


Will do.

[ManyManyBooks]

*sheepishly* That worked.

Thanks, NiLuJe!

[PeterBr]

Hi.

I have one book where linkss gives me the wrong cover as the screensaver.


I removed the photo cacche, emptied screensavers/ and uninstalled and reinstalled the hack itself.

Didn't open the “wrong” book since then.

Still the same problem.

Other books work fine.

I assume that this is some kind of ID thingie, but I have no idea where to look.

I use calibre to put un-DRMed AZW and mobi files on my Kindle Paperwhite 1st gen.

Edit:

Okay, the filename's apparently based on the Ids field as shown on calibre. But when I overwrite the file with another image, linkss chooses yet another image. I'm... confused.

[knc1]

Originally Posted by PeterBr

I use calibre to put un-DRMed AZW and mobi files on my Kindle Paperwhite 1st gen.

What does show as the screensaver?
**STOLEN BOOK** ??

[PeterBr]

Originally Posted by knc1

What does show as the screensaver?
**STOLEN BOOK** ??

I hope not, since I bought these books. However, I have no qualms about removing DRM when I need to read them on another device or want to fix the typesetting.

[knc1]

Originally Posted by PeterBr

I hope not, since I bought these books. However, I have no qualms about removing DRM when I need to read them on another device or want to fix the typesetting.

I am trying to get you to clarify the:

I have one book where linkss gives me the wrong cover as the screensaver.

Cover from wrong book?
Wrong choice of two or more covers in the book?
Other?

We can't do much with: "It's broke" reports.

[NiLuJe]

@PeterBr: By wrong, do you mean random or the next-to-last opened book?

if (apparently) random: you have a date/time issue.
if next-to-last: the issue lies in the book itself (ID clashes *shouldn't* happen, and if it did, I'm guessing there'd be way more weird issues ;D).

Check the logs (;dm in the searchbar).

[PeterBr]

Originally Posted by knc1

I am trying to get you to clarify the:


Cover from wrong book?
Wrong choice of two or more covers in the book?
Other?

We can't do much with: "It's broke" reports.

Oh sorry, in my mind I had typed this:

When I open Book A and turn on the Kindle after a while, linkss chooses the cover of a totally unrelated Book B as the screensaver cover. This doesn't happen for Book C or Book D, which do get there respective covers as screensaver images.

Since un- and reinstalled links and deleted everything from cover_cache and the images in screensaver, I only opened Book A , C and D.

I just checked with another book E, for which linkss will also generate a correct screensaver image.

However, another book F got a wrong one, possibly because I turned of the kindle to early.

I gave it some more time with book G, which promptly got the correct cover as screensaver image.

I opened book A again and now it shows book's G cover.

I think I saw this behaviour before, i.e. that book A simply gets the last valid cover.

I also checked: Book A's cover original is largish, gets to 500 KB when I turn it into a grayscale png of 758x1024 and compress it with tinypng.

[NiLuJe]

See my previous answer. If it's indeed case n°2, PM me the affected books and I'll investigate, see if something can be done .

[PeterBr]

Originally Posted by NiLuJe

@PeterBr: By wrong, do you mean random or the next-to-last opened book?

I got it down to last opened book.

Originally Posted by NiLuJe

if next-to-last: the issue lies in the book itself (ID clashes *shouldn't* happen, and if it did, I'm guessing there'd be way more weird issues ;D).

Check the logs (;dm in the searchbar).

Doesn't do anything. I assume I can find them on the device, when I mount it?

I guess I'll use calibe to convert the book to mobi and see what happens.

It's not that different frrom other books. I bought it from amazon, I de-drmed in on my Mac and then used calibe to transfer it to the kindle.

[NiLuJe]

The logs probably won't tell much if you got it down to the next-to-last case, but FYI, because it might come in handy: from the Homescreen, launch a Search for the string ;dm, instead of showing you the search result page, it'll churn for a while, and four txt files will pop in the documents folder (and thus on your homescreen too). The larger one (all_system_logs or something like that IIRC) is the one we usually care about.

As for the books, a lot of People/Publishing House still handle metadata like crap, so I'm not terribly surprised. PM me one of them and I'll try to pinpoint the issue, see if it can be worked around in the hack or not.

[Canis Lupus]

Hi everyone,

I followed the instructions in the first post for my new Kindle Paperwhite touch. Its recently jailbroken. However, I've run into a problem.

When I tap the button to put my kindle into sleep mode (and thus enable the screensaver), the screen flickers, flashes black, and then it shows the same screen that I was on when I hit the sleep button. When I click the sleep button again, I am prompted to enter my password, as if I was looking at a screensaver.

I have already tried to reinstall the files, and it didn't make a difference. What am I doing wrong?

[eschwartz]

You are either in "last" mode (and everything is working exactly as it should), or you have hit the errors mentioned in the FAQ spoiler in the first post.

* In cycle mode (ie. not cover or last):

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?
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 (optionally properly dithered down to 16 colors).

Another likely way to trigger that issue is to boot (which also means restart, which is what happens right at the end of an update on FW 5.x) while the device is plugged to something (especially a computer: a wall charger should be fine, but just in case...) . I'm guessing this also impacts the last mode, but the cover mode should be fine (although you're still exposing yourself to all the vanilla things that can go wrong when you boot a Kindle like this ).
TL;DR: Unplug your device.