Quote:
Originally Posted by crane3
I think something is forgotten here. From what I have been reading, only books purchased from Kobo is considered "non sideloaded", like Amazon & Kindle. Books loaded using Calibre is considered "sideloaded" if none of the books were from Kobo. Collections can be made using Calibre to create collections.
My KA1 had a collection list that had books in each collection after sideloaded from Calibre.
Okay. The books I have on the KA1 LE were all 'sideloaded" from Calibre & collections were created & populated with books.
The original problem is that the collections were "de-populated" after I did a power off for about 1 day & power on. Was the collection listing display done from ram where data disappear after being powered off? Does the database need to be "re-synced" after turning the KA1 off? Is the database really in "temporary" storage & need to be synced when the KA1 is turned off?
I see what people are saying, but no one addressed the issue of the collections listing of books being set to 0 books just because the reader was turned off. Looks like the collections listing is just a temporary list?
|
That was covered by my "depending on exactly what went wrong in the first place" statement. The answer is we don't know. The most likely reason is a corrupt database. If that is the case, then the recommended fix would be the signout/signin steps. About the only other thing I can think of is that the clock on the device was wrong. And during the sync, the timestamps on the collection records were such that the the sync decided they had been deleted. I'm not sure if that can happen, it would depend on exactly what checks were done. Another possibility is with multiple devices or the Kobo apps logged into the same account. There have been some problems with the syncing across all of them. I haven't noticed any recently, but, I haven't been looking to hard.
Unfortunately, this is one of those things that by the time you notice it, it is to late to work out what happened. If you see it and find the database is corrupted, then that is the answer. For the other possibilities I mentioned, it can be harder to prove.