Thread: [GUI Plugin] Kobo Utilities
View Single Post
Old 07-19-2015, 11:05 PM   #975
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 JimmXinu View Post
Sorry for quoting an old post, but I want to check if this is still how it works--it certainly matches the behavior I'm seeing.

I just bought a Kobo Glo HD that I want to use with fanfiction books from FanFicFare. My use pattern is to frequently add new chapters (and TOC entries) to existing books and then update them on the device. Often several times a day.

The post I quoted says that the device driver deliberately fudges the file size in the Kobo's DB to prevent it from reprocessing updated books--which pretty much prevents me from reading new chapters as they don't appear in the TOC and the Kobo crashes if I page into them and then try to view the TOC.

Alternatively, it sounds like even if I patched my copy of the driver to not fudge the file size, the Kobo would discard the reading position and any bookmarks when it reprocessed the book.

Am I missing anything that may help me here?
No, you are not missing anything. The behaviour of either the Kobo devices or the driver has not changed. The driver fiddling with the file size in the database is a compromise and I think fits most scenarios for resending a book. Unfortunately, the one scenario it is a bad fit for is fanfiction.

But, the way the device would handle this is just as bad. You can get around this by having the utilities store the book progress, send the updated version, disconnect and let the device process the book and then reconnect and restore the progress. This will work, but is a pain.

I suppose what I should really do is clean up and release some code I have to fix the ToC in this type of book. It compares the ToCs the different places (the book in the calibre library, in the device and in the database) and reports the count of entries in each place. Then it can add the extra entries if they are missing from the database. It is fairly dumb, simply comparing counts and assumes the extra entries are at the end of the ToC. But, it works with the FanFicFare downloaded books I have tried. And before anyone asks, it only works for epubs.

Oh, the crash is something new. In the past, this would all work except that the ToC wouldn't match the book. But, it has been a while since I tried opening the ToC in this situation. I'll have a try later, but could you look and see if there are any logs on the device? These will be in the ".kobo" directory with the name "stack_xx.log". They contain a stack dump and can help Kobo debug problems like this. I should get one when I reproduce this and I'll report it via the beta list, but a report from another user is good.

And completely off topic, the stats on my Glo HD shows me as having read for 999.0 hours!
davidfor is offline