View Single Post
Old 07-02-2018, 03:54 AM   #5
chaley
Grand Sorcerer
chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.chaley ought to be getting tired of karma fortunes by now.
 
Posts: 12,471
Karma: 8025600
Join Date: Jan 2010
Location: Notts, England
Device: Kobo Libra 2
Quote:
Originally Posted by CGF-House View Post
I have the same problem since yesterday. I have 3200 books at my calibre and at my Fire tablet. And yesterday/today the newest 4 books aren't shown in the reading app at the fire. Only at the internal storage of the fire and with green indication at calibre.
I followed every step of the help, I was at the help center of amazon (with the great idea to de/new-register my kindle (which deleted most of my collections... so never do that, when you're not always connected via internet!!), but nothing helps.
So I only have now the problem, that the last 1000 books aren't at collections, collections are deleted AND I CAN'T TRANSFER the books. Neither in AZW3 nor in epub-format or in Mobi. Also not working via email (then it's only in documents, but not in the reading app.)
It seems that Amazon changed "something" in the Fire OS 5.6.1.0 update, making books placed in the "Books" folder in the device no longer appear in the recents or library lists. In some cases the Fire actually deletes azw3 book files! You can see some discussion and debugging of this problem in this thread (ignore that we were using CC to transfer the files). The last two posts are the most important. Quick summary: putting the books into a different folder seems to fix it. See the posts for a discussion of which folder you might choose to use.

I have no idea if this behavior is an Amazon mistake or if they are now purposely attacking side-loaded books.
chaley is offline   Reply With Quote