View Single Post
Old 05-20-2020, 11:17 PM   #51
kovidgoyal
creator of calibre
kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.kovidgoyal ought to be getting tired of karma fortunes by now.
 
kovidgoyal's Avatar
 
Posts: 44,017
Karma: 22669822
Join Date: Oct 2006
Location: Mumbai, India
Device: Various
It seems fairly clear that the kindle firmware tries to update covers for "newly" uploaded books, exactly once. Before the change to amazon's servers, the firmware would do it, and fail and keep the calibre generated thumbnail. After the update, it does it and replaces the thumbnail with its spurious "no cover available" image.

So this will affect any book that the firmware thinks is "newly added" on a date after the amazon server was changed.

Assuming amazon refuses to fix their firmware/servers to do the sensible thing, the best possible workaround seems to be for calibre to restore changed thumbnails on subsequent reconnects. This means to send a book to the kindle, with cover, you have to send, disconnect, wait for the Kindle to destroy the cover, then re-connect and have calibre restore the cover.
kovidgoyal is offline   Reply With Quote