View Single Post
Old 12-14-2012, 09:00 PM   #7
jusmee
Wizard
jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.jusmee ought to be getting tired of karma fortunes by now.
 
Posts: 1,047
Karma: 203682
Join Date: Oct 2009
Device: Libre 2
Quote:
Originally Posted by davidfor View Post
I'm curious about what happened just before you lost the reading status. From my experience, this happens only when something goes wrong. Or using the old calibre driver.

The previous calibre driver set the reading status based on values in the tags column if the automatic metadata management was used. The current one doesn't for the Touch, Glo and Mini.
What/where do I check to see if this is the case? The only I remember doing was to add one new book using Calibre (0.8.51). Does that have the old driver?

Quote:
Originally Posted by davidfor View Post
Another time you will lose the reading status is with a factory reset. There is nothing that stores the status for books other than kepubs, so the status can't be restored.

Another way to lose the status is if the database on the device gets corrupted. In that case, the device might rebuild the database after reprocessing the books on the device. The only times this has happened to me was been because I unplugged from the PC without ejecting it. The fix has always been to replace the database from a backup or do a factory reset. Logging off the device and back in again probably would have fixed it as well.

Logging off is another way to cause this. I believe this simply replaces the existing with an empty copy.

From the above, one way to reduce the problem is to take a backup of the database. This in ".kobo\KoboReader.sqlite". Then if it gets corrupted, restore the latest version. Then you only lose the changes since the backup was taken.

No resets or crashes of any kind recently. I will look at ways to back up the database. Actually, it would be nice if that was a task Calibre could automate.
jusmee is offline   Reply With Quote