Quote:
Originally Posted by davidfor
That does suggest it was that book causing the all problems. It's a pity you couldn't have tried open the Awards or stats after reading a different book.
I'll try creating a nice big kepub to see if I can break it. But, as this was a kepub from Kobo, can you send me a link. I haven't been in the mood for Peter F Hamilton lately, but I'll look at the preview and pass it on to Kobo.
|
I can still test it. Although I have patched sickel I can still tell when the original sickel would have rebooted by the amount of time the reading stats takes to open.
The time the reading stats tile takes to open after a device restart does seem to be related to the current read. I guess it doesn't keep the stats as running totals but has to trawl through the database to compute them from the individual reading session data for the book. So if you have a large book that has taken a long time to read (i.e. many sessions over many days) then it will take much longer to open the tile than for a book which hasn't had many reading sessions. So perhaps not directly related to the size of the epub itself, but to how complicated the reading history for that book is.
I guess some of the reading stats have to be computed when you open the book for the first time after a device restart too, so it can compute and display the time to finish.
The book was
this one, it has the problem where the publisher has put more than one chapter in a file, and it has an incomplete TOC so the KePub synced from Kobo has some automatically-generated TOC entries titled "Untitled chapter". Unfortunately that is not altogether uncommon for backlist books. Stats say it took me 31.1 hours to read at an average 42 minutes per session, but I took a break and read another book part way through so it was spread out over a week, and I might have opened the book a few times back around the time I bought it which was a few months (and firmware versions) ago.
Edit: Another factor is probably that I keep all the books I have finished on the device, and it has been a long time since I did a factory reset, so to compute the stats for total hours read is always going to be slow the first time if no running total is kept. Even with a newly opened book as current read, the stats tile takes a long time to open the first time after the device starts.
My database probably has a fair bit of cruft, but this is just a consequence of the hardware and firmware being so solid and reliable, I've never had a corrupt database and so never needed to do a factory reset (although I did do one by accident last year sometime.)