Quote:
Originally Posted by moorekom
@Question Mark: I have had the same experience as you. Epub to kepub mostly downsizes it. Maybe because of the reason @rashkae has mentioned. And it was working on the old one without any issue.
@rashkae: Maybe you are right. I've never been bothered by the image quality as kepub offers the choice to double click on the image to zoom. But as you mentioned, the file reduction might be because of it and the issue here can not have been caused by it.
|
And because of the zoom, you want the best quality image you can get. Then you can zoom in for details.
Quote:
@davidfor: I think you might have just hit it on the head. Being a textbook, it does have a lot of TOC. I believe book 1 had 50 pages in TOC. I'll try to check the trace logs. How do I open these log files you've mentioned?
I'm adding the link to the actual book download site. I believe there is some device limit for the books but as far as I know, there doesn't seem to be any drm involved. If you want me to send you a copy of the book, let me know. Or we can also try some other torrent/pirate site to study this issue. But I'm not sure what your stance on the latter is, so let me know what you most comfortable with.
http://www.ciscopress.com/store/ccna...-9780134441009
http://www.ciscopress.com/store/ccen...-9780134440972
|
I've had a look, but at that price, I can't buy one. And it seems to much like work

And, as I keep telling the people I work with, I'm an application developer, not a network engineer.
I did find the first book in the Kobo store and downloaded the preview. This has the full ToC of 566 entries. With that number of ToC entries, it might be a sickel reboot. When a kepub is first opened, it does a page count for all the chapters and adds this to the ToC entries in the database. If that isn't reporting updates, then sickel might see the process as hung and restart the device.
Quote:
Originally Posted by moorekom
@davidfor: Found the stack files as you mentioned. There are stack_00 through stack_09. I copied the 09 and pasting it here.
|
That looks like an error in the WebKit. Which I would think is more likely to be a display issue. That goes against my thought of the page count. But, that might not be the right file. You need to look for one with a timestamp that matches the crash as the firmware cycles through them.