Thread: Aura H2O Light bug in 4.4.9344
View Single Post
Old 07-14-2017, 08:52 PM   #37
robko
Wizard
robko ought to be getting tired of karma fortunes by now.robko ought to be getting tired of karma fortunes by now.robko ought to be getting tired of karma fortunes by now.robko ought to be getting tired of karma fortunes by now.robko ought to be getting tired of karma fortunes by now.robko ought to be getting tired of karma fortunes by now.robko ought to be getting tired of karma fortunes by now.robko ought to be getting tired of karma fortunes by now.robko ought to be getting tired of karma fortunes by now.robko ought to be getting tired of karma fortunes by now.robko ought to be getting tired of karma fortunes by now.
 
Posts: 2,454
Karma: 5469320
Join Date: Jul 2010
Device: Kobo
Quote:
Originally Posted by msegt View Post
It doesn't have to do with my Kobo account either. I'll probably try to play around with the reader in the summer to try to fix the issues, but it's definitely been caused by the update, and it's very annoying that it's not an isolated case and nobody at Kobo seems to care..
You're right: your Kobo account is fine. HOWEVER what David was suggesting is that you SIGN OUT of your account ON THE DEVICE and sign back in to it. That completely clears the database on the device and resets it to factory conditions. The specific symptoms of bookmark not updating/stuck at an older point you described have been traced back to a database corruption in 99% of the cases reported here and signing out/in will almost always solve it. It could be something happened during the update that caused something to get out of whack in your database, or maybe it was coincidence that it happened around that time.
You may have a high level of database knowledge, but IMHO Davidfor probably has the best understanding of how the Kobo database and how the device uses it of anyone short of developers themselves so I wouldn't assume that he's wrong until you can prove a different cause.

The light issue is a different thing and that is a firmware bug that should be fixed in the next version.
robko is offline   Reply With Quote