Thread: Clara HD Error Communicating With Device
View Single Post
Old 09-06-2020, 10:12 AM   #12
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 codychan View Post
I don't know if there is something wrong with two recent released firmwares, my Kobo Forma goes wrong from time to time since the firmware 4.23.15505, such as

1. highlight some sentences when reading, but the highlights parts are not shown in the highlight collection list on the right color of the screen
There is a filter to control what is shown in the annotations list. Is this set to "All?
Quote:
2. the database got corrupted, it has been corrupted twice since I installed 4.23.15505, I have to restore it from the backup database file made by Calibre
3. the Send to device function in Calibre doesn't work from time to time, sometimes one book or two are not sent to the device, sometime it works when I tried it again
If you are using the KoboTouchExtended driver, if the changes to make an epub a kepub fail, it can silently not send books. That depends on the options chosen. Calibre should always send a book if there is a suitable format. And if there isn't it should do a conversion, or tell you.

But, how do you know the book wasn't sent? Did you look in the file system on the device? Or did it not appear in the book list? If he latter, did the device show the importing screen after you ejected the device? If it did, and the book wasn't shown, it generally means there was a problem with the book so that the device could not import it. And this will mean other books in the same batch won't be imported.

Those are the things I can think of. If calibre isn't actually putting the book on the device, I would need to see a debug log from calibre when it happens to try and work out what was wrong.
Quote:
4. The reading position is not synced into Calibre, and the reading position restore to the old position in the book after I unplugged.
The latter is usually a sign that the database is corrupt. The status isn't successfully written to the database, and then when it is read again, the last successfully written position us found. But, there is something different in how or when the reading position is stored, that might mean it might not be seen when connecting to calibre. I don't have a good idea of what has changed, just that something has changed.

The reading position not being retrieved can also be caused by the file "driveinfo.calibre" being regenerated (by being deleted or a factory reset). If you have a profile for your device configured in the Kobo Utilities plugin, this is identified by the contents of the "driveinfo.calibre" file. If that get regenerated, then the plugin does not know it is the same device. If you only have one Kobo device, using "* Any device" for the configuration is generally better. Or if you don't want to differentiate between the devices. Otherwise, you need to add the device again in the Device tab of the configuration.
davidfor is offline   Reply With Quote