K5 FW 5.x ScreenSavers Hack

[NiLuJe]

I stopped bundling the sources from the release packages to save space, so, yeah, short of recreating the same full tree at a very specific point in time and setting it up, there's no other way. Hence the snapshot packages, which have the benefit of being (nearly, it's missing the split K3/K5/PW2 binaries) ready-to-go source-wise.

As for the UI, I guess you could also go with WAF, but again, not terribly simple & fast, although it of course depends on how fluent you are in the technologies involved.

[crowned]

Just created this custom screensaver creator for the Touch and Paperwhite 2 (and any other kindle that can use 758 x 1024 or 600 x 800 screensavers). Click the link on the left to toggle between paperwhite and touch.

Select a large jpg or png, and it lets you zoom and crop and convert to black and white, then right-click to save as a black and white PNG.

Everything takes place on the client-side so nothing is uploaded.

Please let me know if you have any feedback or questions.

https://crowned.github.io/kindlesaver/
.
.

[svhs]

@crowned It would be really cool if one could use link as image source!

[crowned]

Originally Posted by svhs

@crowned It would be really cool if one could use link as image source!

Never thought of that. I'll see what I can do (just when I thought I was finished with this sucker!)

[NiLuJe]

@svhs: https://www.mobileread.com/forums/sho...d.php?t=236104?

[svhs]

@NiLuJe Sorry, but I do think it's a totally different thing.
@crowned One more idea: If you could rotate the image, that would be cool too!

[NiLuJe]

@svhs: That's all right, that just means I completely failed to understand what you meant . Please elaborate.

[8bitg33k]

Finally got this installed after some trial and error and it works great!

One question though - it seems that with the default screensaver installed, I would always have to swipe to open after pressing the power button or open the magnetic cover. Why is that? I kinda liked the screen lighting up first before opening it.

[eschwartz]

Finally installed this hack, and enjoying it a lot -- thanks, NiLuJe!

One random question, though. From my limited experimentation, it does not seem to be picking up the covers of my non-Amazon books (all are .azw3) -- unless they have the PDOC field set to EBOK in calibre. Which isn't a problem, as I plan on switching that out anyway, when I get a chance. Just checking that this is known/expected? Unless I have a weird book, of course....

[NiLuJe]

@eschwartz: I can't quite remember how Calibre handles the PDOC thingy, but, yes, the exth cdetype needs to be valid (it filters out everything besides PDOC & EBOK by default, plus MAGZ & NWPR if you enable periodicals support, that's part of the filtering needed to drop dictionaries, Kindlets & co).

TL;DR: Calibre's default conversion settings are sane and work properly. What do you use the PDOC tweak for?

[eschwartz]

To switch from the default PDOC and use EBOK instead. This gets rid of the "personal" banner. But I had an old book which I never resent, which doesn't display the cover. It shows the cover of the book before that.

To be clear, a valid calibre-default azw3 of cdetype=PDOC was not showing the cover. I'll have to try it out with some other old books as well. The newer books, sent after I switched cdetype to EBOK, worked just fine, displaying the cover screeensaver.

[NiLuJe]

@eschwartz: Then it probably didn't have a valid cover in the metadata, the hack handles PDOCs fine .

IIRC, Calibre's default cdetype (after conversion, at least) is EBOK, you only end up with a PDOC if the book you're converting is tagged with the same tag as the one specified in the pdoc tag MOBI output setting.

The whole cover view thing (both cover & personal banner), while related to the cdetype in some aspects, is a bit more complex, but irrelevant for the hack anyway.

[eschwartz]

Originally Posted by NiLuJe

@eschwartz: Then it probably didn't have a valid cover in the metadata, the hack handles PDOCs fine .

IIRC, Calibre's default cdetype (after conversion, at least) is EBOK, you only end up with a PDOC if the book you're converting is tagged with the same tag as the one specified in the pdoc tag MOBI output setting.

Correct. But it's edited on the fly according to the output preferences, as the book is sent-to-device.

The whole cover view thing (both cover & personal banner), while related to the cdetype in some aspects, is a bit more complex, but irrelevant for the hack anyway.

Well, I wouldn't mind an explanation anyway, I love to learn.

In any event, I've checked 4 more old PDOC-sent books, all fail to generate cover view. They were from various sources, and show cover view (in library list) correctly. While that may mean nothing, calibre converted them. 2 more from a single other source showed up correctly -- calibre-converted, and sent with cdetype on output set to EBOK.

If there is a better way to set a cover (besides calibre enforcing it on conversion), I'm all ears.

[NiLuJe]

@eschwartz: Hmm, for those calibre converted ones, I assume you of course had a proper cover set in Calibre at the time? If so, I'd really like to take a look at one of those files .

As for the whole cover view thing:

You get a personal banner if:
• cdetype is PDOC
and/or
• ASIN isn't set

You get a working thumbnail if:
• ASIN is set, and valid, and device is online.
OR
• ASIN is set, not necessarily valid, but with a thumbnail manually and properly side loaded (which is what Calibre does on "Send to Device").
OR
• ASIN is unset (KindleGen produced files, for exemple), in which case it's pulled from the file, and looks tiny on the PW.

All this assumes that the catalog database not be confused and/or using cached info for said book, hence the recommendation to delete stuff on device before updating a book.

(For ref, in calibre, the PDOC cdetype is handled through the pdoc tag thingy, and the inclusion of an ASIN is controlled by the "FB share" checkbox (if it's checked, no ASIN is set). In short, the default settings are sane ).

[eschwartz]

Well, it seems somehow "share_not_sync: true" -- I must've set it a LONG while ago, but I've no idea why.

According to Java Mobi Metadata Editor:
The old book(s) has no exth fields 113, 501, or 504.
The new one(s) has 113:$calibre_uuid, 501:EBOK

I'm not sure why old has no cdetype, (before I touched that setting) nor why the new has an ASIN if that was disabled???

But I can fix the problem books by resending with the new settings or by adding in the cdetype=PDOC/EBOK (either works) using JMME.

So clearly something wrong on my setup.

Thanks for the explanations. Fascinating stuff.

Now excuse me, I need to go tinker with something.