Quote:
Originally Posted by BobC
I'm pretty sure that on the occasion the log refers to the error displayed was something like "Error Communicating with Device". The error has occurred a different stages from time to time, both on initial connect and on later interaction. It is only with 2.8.1 that I started looking more closely at the logs and noticed that the error seems to occur during/after the "Update Metadata" phase. I can still get it to happen, although not every time, if I delete a book on the device from Device View. To date though an eject and re-connect has always got things going again.
|
The fact the error happens during the "Update Metadata" phase makes sense. That is when updates are made to the database. The earlier phase is read only. Sending a book writes to the drive and updates the database.
Quote:
|
Do you want the full debug log ? - I trimmed it down rather than posting the whole 10Kb.
|
Yes please. Post it or send it in a PM.
Quote:
|
I haven't been able to interest Kobo in the problem because it only seems to happen when the database is being manipulated and that isn't a supported activity (perhaps the desktop app does it but I don't use that as it's no good for loading the books I have). Simple book/file copying using File Manager doesn't trigger the issue.
|
I'm not surprised. Kobo accepts that calibre exists. But, they don't officially support using it. If we could reproduce the problem with the desktop app, that would be a different matter. The desktop app does update the database, but probably not as many as the calibre driver can. That might be the issue.