Quote:
Originally Posted by davidfor
I had a very quick test last night and calibre doesn't really support individual images or sending them to a device. That makes doing anything there a bit more complicated.
But, I was thinking more that part of the fmon install process would be to generate the covers images and put them in place. Thinking about it now, they could just be copied from a working system. The cover images have names that are derived from from the book and its location and is used as a id in the database.
|
This is certainly an alternative to the current install process. Even thought, it seems a little uncomfortable to me.
I wonder why on devices where KSM has been installed at some point and was running for some time without problems, all of a sudden fmon is triggered without the user accessing the relevant PNGs. If I remember correctly, reports of this happening were often related to installing a new FW. And usually (I think there was one exception) visiting the PNGs in the library and opening them, brought everything back to normal.
My attempt to explain this was to assume that under circumstances unknown to me some FWs recreate on some models the covers anew. I was however not able to verify this. On my devices I did not see any covers recreated after a FW update. The most recent file date of an fmon related cover on any of my devices is from February 2015.
There are of course other possible explanations. The user never did the install process completely, but by chance nothing happened for some time. Or the user signed out without afterwards repeating the necessary steps related to fmon. Deleting and adding the PNGs at a later time might also have some effect (I never checked whether nickel removes the covers of deleted books).