Thread: Firmware 4.17.13694
View Single Post
Old 09-22-2019, 06:54 PM   #73
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 compurandom View Post
I've got a large library on my kobo, and it took quite a while for the upgrade to finish. It probably had to examine every book and update the database for each one, so it just took a while, but not as long as reimporting everything. I left it plugged into the USB (but ejected) and just let it think for a while.
Kobo changed the way the reading position is stored for epubs. This meant an update for each epub in the database during the first boot after the update. The more books you have, the longer it would have taken.
Quote:
Probably by turning it off and on in the middle of the scan you corrupted the database, which is why a factory reset was needed. It was really hard for me to not bother it too. :->
Yes, turning the device off in the middle of the update would have been a bad idea.
davidfor is offline   Reply With Quote