Thread: Aura HD KEPUB problems: Books won't load more than once
View Single Post
Old 10-03-2013, 10:51 PM   #25
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 Cosmic View Post
I am brand new to these forums as I am a very recent owner of my first e-reader, a Kobo Aura HD.

I am experiencing the same problem as the TS. Navigating from an ebook to the home screen and then back again to the ebook, causes a freeze and a message of the bottom of the screen saying something like "page x is loading ...".

I am also using the KoboTouchExtended-plugin.

I have made a debug log as proposed above. I would like some help as I do want to keep on using the Kepub-format (love those statistics!) and my own shelves.
Nothing in the debug log suggests any problem. The request to neil74 was because calibre appeared to be sending kepubs to the device even though the extended driver had been removed or disabled. That shouldn't happen, so I needed to see why it was.

The problem you describe sounds like the same as the OP. And as I replied it sounds like a known bug in 2.8.1 with kepubs that use embedded fonts. But, the times I have seen this, I was able to get the text displayed by bring up the menu and then dismissing it. It probably means there is something in the book that makes it not respond.

A difference I can think of is adding "FullBookPageNumbers=true" to the config file. Maybe this is causing a hang when calculating the page numbers.

If what you are seeing is related to the embedded font bug, then there is something you can try. My Kobo Utilities plugin has a way to change the font to be used for a book. Use this to set the font to something other than "Document default". If that doesn't allow the books to be opened, then it is a different problem than what I thought.
davidfor is offline   Reply With Quote