Thread: Kobo Firmware 3.11.0
View Single Post
Old 11-10-2014, 08:50 PM   #356
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 Ebri View Post
PeterT: Thank you, I will check them.

Yesterday I also had to use a backup of my database to recover (removing the corrupt parts had some vital side-effects), and I did only highlighting on EPUBs, but if highlighting didn't happen while I have read all the page, I made the device (Aura HD) sleep and wake, which made it responsive again, but I am unsure whether it also killed the database. Do you have such experience? Especially does anyone have a cure, that would make highlighting faster? (I read quickly, but reading a page takes some time still.)
I haven't noticed it much recently, but I was having a problem like this. Occasionally when I tried to highlight something, the device would hang. But, putting it to sleep and waking it would get it going. And highlighting would work. I never worked out pattern, but I felt like it was more likely to happen if I started from the right edge and swiped left. Of course, when I deliberately did this, it always worked.

But, I would have said this went away with 3.11.0. I put some of the blame on something in the database. When certain things are done, an entry is added or updated in the Events table. For highlighting, eventid 9 is used to count them. Up to 3.11.0, this was done incorrectly and a row could be added to the database for each highlight and the count updated on all of them. After a while, there could be a lot of rows. I found about 3000 one time I looked. Deleting these sped up the highlighting and dictionary lookup a lot.

As of 3.11.0, the count has been changed to a per book count. But, it's possible the old rows are still there. That would have a performance hit due to the size of the table.
davidfor is offline   Reply With Quote