Thread: Firmware 4.15.12920
View Single Post
Old 07-14-2019, 08:04 PM   #99
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 teapotz View Post
I see the problems only with the Clara HD, everything is normal on my Aura HD. Both are updated with this firmware. I had the same books loaded on both. I had the Clara for about 4 weeks prior to the update and it worked fine, then the update and the problems started.
Can you check the firmware version on the Aura HD? From your description of what you are seeing on the Clara HD, there are only two causes I can think. One is the new problem with firmware 4.15.12920 which is related to the ToC construction. If this is the problem, then you will see it on all devices running this firmware version. I have definitely reproduced it on all of my Kobo devices. And, the differences between the firmware versions on the devices is the kernel and drivers. The application code is identical.

The other way this could happen is with a corrupt database. The factory reset should have fixed that. It should have rebuilt the database on the device which would remove that problem. Then, unless whatever caused the database corruption happened again, it should have the same behaviour. If it is a database problem, you can check the state of the database using any SQLite database manager. Or if you are a calibre user, it is likely to show errors when the device is connected. But, a more thorough check can be done using my Kobo Utilities plugin.
davidfor is offline   Reply With Quote