MobileRead Forums - View Single Post

davidfor · 03-09-2020, 08:36 PM

Sorry, I don't see a solution in your post. Effectively you have said to get the IT gods to corrupt a book and things will be fixed when you try to open it. I'm not sure if that is a practical solution

Or are you asking for help to know what happened to fix things?

If so, it would help to know what was going on if you had posted the error message you saw. The "error communicating with device" is a fairly generic error, and the detail will tell more about what is happening. And it depends on when the error happened. Was it during the initial connect, when updating metadata or sending a book?

For a Kobo device, the most common reason is a that the firmware has been updated but the calibre version hasn't been updated to match. The next most common is a corrupt database on the device. To fix that, you usually need to log out of the Kobo account on the device, or restore a backup of the database. Issues with individual books are usually because or DRM or errors in the book. The latter will happen if you are using the extended driver to send books as kepubs.

The "Kobo had a fit" doesn't say much. If it meant the device restarted and redid the setup, then that would suggest a corrupt database. The setup process creates a new database and reimports the sideloaded books. That would fix a lot of errors.

03-09-2020, 08:36 PM	#2
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	Sorry, I don't see a solution in your post. Effectively you have said to get the IT gods to corrupt a book and things will be fixed when you try to open it. I'm not sure if that is a practical solution Or are you asking for help to know what happened to fix things? If so, it would help to know what was going on if you had posted the error message you saw. The "error communicating with device" is a fairly generic error, and the detail will tell more about what is happening. And it depends on when the error happened. Was it during the initial connect, when updating metadata or sending a book? For a Kobo device, the most common reason is a that the firmware has been updated but the calibre version hasn't been updated to match. The next most common is a corrupt database on the device. To fix that, you usually need to log out of the Kobo account on the device, or restore a backup of the database. Issues with individual books are usually because or DRM or errors in the book. The latter will happen if you are using the extended driver to send books as kepubs. The "Kobo had a fit" doesn't say much. If it meant the device restarted and redid the setup, then that would suggest a corrupt database. The setup process creates a new database and reimports the sideloaded books. That would fix a lot of errors.