Quote:
Originally Posted by torishu
Paperbackstash, similar "ghost files" have been showing up for me for the last many firmware revisions, usually when I accept an updated book on "My Content and Devices." I can always tell because I will have two of the book or the book will be missing the three dots in the corner in cover view.
Trying to delete the book will make the screen flash and nothing happens.
I had reset my Kindles many times over the past year or so over this problem. Even deleting the files after connecting the Kindles to the computer doesn't always fix it.
One thing that does seem to consistently work, however, and has kept me from having to reset and reload my Kindles for a couple months now has been to remove the book in question from a collection, delete it, then re-download and re-add it to the collection.
(All my books are in collections, however I think adding a book to a dummy collection and removing might work. I would, of course, try to delete the book at every step, not just after adding and then removing.)
Hope this helps, or at least helps others who have been experiencing similar. This is happening on all three of my current Kindles (two 2019 Oases and a Paperwhite) so I know it's not just a unit quirk.
Between this and the TTF custom font issue, these firmware revisions seem to be getting a bit worse.
(I now convert all my custom-loaded fonts to OTF because TTF files are squashed at smaller sizes and won't accept bolding if the book contains a publisher font. This is with direct-from-Amazon books, not sideloaded. It's been an issue the past few firmware revisions along with the above issue.)
|
How odd!
Your problem sounds even worse than mine, but then again it sounds like yours has existed longer.
I don't have any of the ghost files in collections - I sometimes use collections but not much any longer. The one I have now that is empty just shows an empty cover with book and author name, but there are no bars or any way to manually delete this. I know it's no longer on the device. I wonder if they have been experimenting with Kindle Unlimited permissions or something and that's causing a glitch.