Register Guidelines E-Books Search Today's Posts Mark Forums Read

Go Back   MobileRead Forums > E-Book Software > Calibre > Devices

Notices

Reply
 
Thread Tools Search this Thread
Old 06-21-2022, 08:02 AM   #1
iandol
Enthusiast
iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.
 
iandol's Avatar
 
Posts: 33
Karma: 216612
Join Date: Feb 2022
Device: Kobo Nia
Exclamation [kobo] Making sure Calibre remembers which books have been sent to device?

I have a Kobo Nia, and the latest version of Calibre with Kobo Utilities using the extended driver. I connect via USB, sometimes connecting while using Nickel, and sometimes when running KOReader. Once connected Calibre shows green tick marks on books it knows it has "Sent to device". I send EPubs and do not convert them to Kepub.

The problem I have is that (since around April 9th) this has stopped showing on books that were sent to device. New books I send to device show the green mark when first sent, but when I disconnect and reconnect the green mark disappears even though the book is present on the device and had been previously sent there by Calibre.

How can I "force" Calibre to recognise that this book is already on the device? I've tried running "Refresh the list of books on the device" from the plugin menu to no effect. I've "checked" the database is ok, and it is.

Last edited by iandol; 06-21-2022 at 08:04 AM.
iandol is offline   Reply With Quote
Old 06-21-2022, 11:21 AM   #2
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,908
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
The first thing that comes to mind, as you sometimes connect from KOReader, is that you are not letting the Kobo software, called nickel, import the books. The driver reads the database for books on the device. This is populated when you eject the device and nickel looks for new books and imports them into the database. If you only connect from KOReader, that will not happen. I don't think exiting from KOReader back to nickel would trigger the import. There are other ways to do it, but, connecting while running nickel is the best.

The next likely thing is that the database on the device is corrupt. The device may import the books, but, the database does not get updated properly and hence, the next time you connect, the books are not seen. But, if this was the case, I would expect that you would see errors when connecting to calibre and the databases is read. Exactly what you see does depend on how the database is corrupt, so sometimes it calibre does not see the error. But, you can run a full database check with the Kobo Utilities

The last thought is, with the timing of when this happened, it could also be related to issues with firmware version 4.32. That had issues with presenting the book partition to the PC when connecting. These meant that the partition would be loaded read-only when you eject. And that caused a lot of problems, such as what you are seeing. Firmware 4.33 was released earlier in the month and that fixes these problems.

Also, as you are not sending books to the device as kepubs, why are you using the KoboTouchExtended driver? The purpose of this is to transform books to kepubs. There is almost no reason to use it if you are not using kepubs. The built-in KoboTouch driver should be enough.
davidfor is offline   Reply With Quote
Advert
Old 06-21-2022, 08:34 PM   #3
iandol
Enthusiast
iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.iandol ought to be getting tired of karma fortunes by now.
 
iandol's Avatar
 
Posts: 33
Karma: 216612
Join Date: Feb 2022
Device: Kobo Nia
Dear David, I think a combination of your first point regarding KOReader alongside some issues with 4.32 may have been at fault. I have manually cleaned up my storage then forced a full rescan with NickelMenu's commands, and you are indeed correct that now Calibre "recognises" the books I had added.

I used the extended driver as I initially was using the kepub conversion for reading using the kobo software, but I realised I preferred some typography things with epubs and then spent more time in KOReader and Plato. Is there a downside to use the extended driver if one doesn't convert to kepub?

Finally, thank you for a comprehensive and helpful reply!
iandol is offline   Reply With Quote
Old 06-22-2022, 12:29 AM   #4
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,908
Karma: 47303748
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
It's always good to hear one of my guesses was right

As to the extended driver, there isn't any real issue with using it and turning off the kepub options. For me, the biggest issue would be remembering why I had it in six months time. And part of the reason I asked is that there are some people out there that say you must install the extended driver and say it in such a way that implies calibre will not work with Kobo device without it.
davidfor is offline   Reply With Quote
Reply

Tags
calibre, kobo, kobo utilities

Thread Tools Search this Thread
Search this Thread:

Advanced Search

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
[Kobo] calibre does not find books in subsubfolders of device avv Devices 15 08-02-2021 12:37 AM
books from Kobo device into Calibre catsknit Library Management 2 10-07-2019 11:21 PM
[KOBO] books on the device that are not recognised by calibre anacreon Devices 8 06-25-2019 04:05 AM
How does Calibre recognise books on device / Kobo Kepub-Epub (not) linked Mrs_Often Devices 12 06-08-2018 08:00 AM
Suddenly Calibre doesn't mark some books on a Kobo Glo device bernard.ryefield Devices 34 05-10-2018 09:12 PM


All times are GMT -4. The time now is 06:52 PM.


MobileRead.com is a privately owned, operated and funded community.