Quote:
Originally Posted by kovidgoyal
@Cinderela: Since you seem to be in contact with amazon, tell them that their issues are all caused by a bug in their software. Whenever a MOBI file has the 113 field in the EXTH header with a value that amazon's servers don't know about, the following misbehavior happens:
1) For *some* MOBI files, the Kindle Fire opens then immediately closes the file, presumably because last read position syncing failed. There is absolutely no reason why the Fire should not be able to handle this situation gracefully.
2) In K4PC and on *some* kindle devices the cover thumbnail from the book is not used, instead, the software tries (and fails) to download the thumbnail from amazon's servers, and so displays a generic cover. Instead, it should fallback to using the thumbnail from the file when one cannot be downloaded from the cloud.
|
Thank you so much for your speedy response, Kovid! When all else failed, I did contact KF support and they were *no* help! The experts here were all more knowledgeable about the KF than the support "experts" at Amazon itself, but there are tons of Amazon forum threads about these issues and I can certainly copy & paste your comments there - I, personally, do not write code, so I can't re-phrase your observation.
Perhaps it's not a "bug" at all - just another way to try to bully us into only reading files that have gone through their servers.
UPDATE: After the software update, I got TWO WHOLE HOURS with everything the way it SHOULD be! Covers restored and all files opening as they should. After a couple of hours, the files were right back to "maybe open, maybe not".