Thread: [Device Plugin] Kobo Touch Extended Driver
View Single Post
Old 06-21-2020, 09:04 AM   #2218
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 jxall View Post
After updating to this build the very same bug that I experienced with v3.2.10 and Calibre 4.18 is back: newly-synced books can't be found anywhere on the device. Only that this time I am using v3.2.11 with Calibre 4.19.

The processing of the books (that occurs when you eject and unplug the device from the PC) is suspiciously fast (as if just one book has been synced instead of a dozen) and none of the new books is either searchable or listed within the My Books section.

On a sidenote, I can confirm that this build has corrected the spacing issue that I was experiencing with v3.2.10 and Calibre 4.19 (kepubs are now displayed correctly at least on Calibre Viewer - of course I can't speak for the Kobo Clara as I am unable to find the books).
Are the books definitely on the device? Can you see them on the device before you eject? Are you sending new books, or replacing exiting copies?

The quick import could be because the first book failed to be processed correctly. That blocks the rest from being imported. And, if this was happening before, it might be a leftover from a previously sideloaded batch. You will probably need to remove these books, work out which are triggering the problem, fix it and send them again. Unfortunately, the only way I know to do this, is send the books in small batches until you find the problem book.
davidfor is offline   Reply With Quote