View Single Post
Old 12-26-2017, 09:58 PM   #13
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 Blas View Post
Yeah that's what I see when they are not loaded.
All of my books are saved in my sdCard that is 32GBG. On my Kobo it shows that I have 28.3 GB of 28.8GB avaible on the sdCard.
My database has 56MB.
With that amount of space taken, and that small a database, the books have to be huge. Are we talking comics? Large PDFs? Or lots of books on the card that have not been imported. And if the book or images in them are large, then the time taken to generate the cover image could be noticeable. Especially on the Touch as it has the slowest CPU and least RAM of touch based Kobo devices.

And the card could be exacerbating this. The speed of the card will have an affect. Plus, the device doesn't store the generated images for books on the card. For books on the main memory, the cover images are generated and stored, which makes them faster. But, for the card the covers images are generated. Restarting the device will mean the images are generated each time. The images are cached in memory for a while, but the cache will be limited. If you scroll through the lists, you will see them constantly being generated.

You can use the driver in calibre to generate and send the covers. While the device isn't saving them to the SD card, it does look for them and use them if they exist. The driver has an option to send them. And you can use my Kobo Utilities plugin to send or replace the covers for books already on the device.
Quote:
I always try to wait a bit to see if it will keep frozen, then I just press the home button and it goes to the home screen. It adds the books normally. I never had any problem to load a book to read or change pages.
OK. I get that occasionally. And I think it only happens with a problem book. Though I usually get further than 9%.
Quote:
I will give a try and reinstall this firmware version "4.5.9587" and try to find the book that has an issue. Thx for the advice.

[EDIT]I reinstalled the firmware and the problem persists.



And yes I use this Kobo extension which I think that already covert the epub to Kepub before sending it to the device right.
OK, you are using the KoboTouchExtended driver
Quote:
[EDIT] I think that the problem is that I have a book that has some error which is affecting the importing content. And is affecting the covers loading too.
Quote:
Originally Posted by Blas View Post
Which errors on a book can freeze the "importing content"?
That I don't know. I've never been able to find a consistent cause. I do know that if I clean the books using either the calibre editor or Sigil, or do a conversion in calibre, they rarely fail. The problem should be in the metadata or the ToC. The import on the device reads these and puts them into the database. It doesn't look at other parts of the book, but parts of the internal file structure could cause problems.

Another possibility is if the book is very large, it could cause problems importing the book. The firmware does watch processes in case they hang. Unfortunately, it can't really tell the difference between a process that has truly hung or one that is taking longer than usual. But, I don't think this is the case as the device usually is rebooted when the process watcher kicks in.
davidfor is offline   Reply With Quote