Thread: Aura One Wackiness
View Single Post
Old 10-05-2016, 06:59 AM   #4
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by NightGoat View Post
The sideloaded book I was reading kept reverting back to a the same previous location after coming out of sleep, none of the highlights beyond that particular location were being saved.

I decide to power off (holding the button) and when I turn it back on, all of the book covers on the main page are blank and inaccessible. Then it reboots on its own, and goes through the setup again.
I'm thinking I'm getting an update. Not the case.
The books are all back now but all of my highlights have disappeared.

This is my first Kobo reader; is this how it's going to be with Kobo?
The symptoms suggest that the database on the device was corrupted. The database is used to store details of the books, reading status and annotations as well as the users details. Depending on exactly what is wrong with the database, the device can continue OK, or, in the extreme case, need to reset and start again.

How this happened, I don't really know. The only way that I know can do it is not safely ejecting the device from the PC. One problem is that it can take a while to see the effects. The device will run using date in memory, and keep running but not successfully updating the database. Then, at a restart, the database is read and it is either an old copy of the data, or bad enough to trigger the setup.

Is it going to be like this? I don't think so. Across my four devices, I've seen a corrupt database twice this year. And I know what I did both times. I do take backups of the database just in case, but I have rarely needed to use them.
davidfor is offline   Reply With Quote