Elipsa: Not accepting converted Kepubs

[Skydog]

Update: Started over with a factory reset. With the problem below cleared up, I was able to send a kepub to device, but it does not appear. The file is indeed on the Elipsa (checked folder) but apparently converted/sideloaded kepubs are not recognized. Any ideas?


After converting several epubs => kepubs, either on-the-fly or before, the same error message appears when attempting to send to device. Any chance this can be resolved in the future?

calibre, version 5.22.1
ERROR: Error: Error communicating with device

'utf-8' codec can't decode bytes in position 14-15: invalid continuation byte

Traceback (most recent call last):
File "calibre\gui2\device.py", line 89, in run
File "calibre\gui2\device.py", line 595, in _upload_books
File "calibre_plugins.kobotouch_extended.device.driver" , line 388, in upload_books
File "configparser.py", line 697, in read
File "configparser.py", line 1017, in _read
File "codecs.py", line 322, in decode
UnicodeDecodeError: 'utf-8' codec can't decode bytes in position 14-15: invalid continuation byte

[PeterT]

This looks like an issue with either the file name or on of the internal files inside the Epub / kepub being sent.

Sent from my Pixel 4a using Tapatalk

[Skydog]

Originally Posted by PeterT

This looks like an issue with either the file name or on of the internal files inside the Epub / kepub being sent.

Sent from my Pixel 4a using Tapatalk

I was just composing an update to my post above when you replied. Performed factory reset, successfully sent kepub BUT... Elipsa does not recognize it, does not appear. (confirmed it is on the device)

[PeterT]

What location on the Kobo are you sending books to?

Sent from my Pixel 4a using Tapatalk

[davidfor]

Originally Posted by Skydog

Update: Started over with a factory reset. With the problem below cleared up, I was able to send a kepub to device, but it does not appear. The file is indeed on the Elipsa (checked folder) but apparently converted/sideloaded kepubs are not recognized. Any ideas?


After converting several epubs => kepubs, either on-the-fly or before, the same error message appears when attempting to send to device. Any chance this can be resolved in the future?

calibre, version 5.22.1
ERROR: Error: Error communicating with device

'utf-8' codec can't decode bytes in position 14-15: invalid continuation byte

Traceback (most recent call last):
File "calibre\gui2\device.py", line 89, in run
File "calibre\gui2\device.py", line 595, in _upload_books
File "calibre_plugins.kobotouch_extended.device.driver" , line 388, in upload_books
File "configparser.py", line 697, in read
File "configparser.py", line 1017, in _read
File "codecs.py", line 322, in decode
UnicodeDecodeError: 'utf-8' codec can't decode bytes in position 14-15: invalid continuation byte

That error is from the driver reading the config file on the device. There was string somewhere in the file that the library being used to read the file does not like. The reset of the device cleared this, but, it could appear again.

There is no error handling for that section of the code. I will look at adding that. Also, it is setting the hidden option for full-book page numbering. That hasn't been valid for a while, so I might add some handling of that. Or just remove it completely. Anyone remember what firmware that was added in and then removed?

[Skydog]

Thank you for the explanation.

Referencing my update to the post, do you have any idea why the kepub (converted via extended driver)transferred successfully but is not seen on the device?

[Skydog]

Originally Posted by PeterT

What location on the Kobo are you sending books to?

Sent from my Pixel 4a using Tapatalk

Presumably, the default assigned by Calibre when "Send to Device" is selected, the root directory of KOBOeReader/. I have not done anything differently from four other Kobo devices and never had a problem. There must be something unique going on in my case since I read one other post from another new Elipsa owner who has converted, sent and read kepubs via the driver.

[davidfor]

Originally Posted by Skydog

Thank you for the explanation.

Referencing my update to the post, do you have any idea why the kepub (converted via extended driver)transferred successfully but is not seen on the device?

Does the importing message show when you eject the device?

My understanding is that there are no differences for the existing function in the Elipsa firmware. And I think someone has mentioned sideloaded kepubs with reference to annotations via the pen. I think that was @Cootey. I am putting it on one of my devices to test. That should be close enough, but, there could be something specific to the new device.

[Skydog]

Originally Posted by davidfor

Does the importing message show when you eject the device?

My understanding is that there are no differences for the existing function in the Elipsa firmware. And I think someone has mentioned sideloaded kepubs with reference to annotations via the pen. I think that was @Cootey. I am putting it on one of my devices to test. That should be close enough, but, there could be something specific to the new device.

Ah... I just noticed that now when trying another book. No importing message with the progress bar - it acted like a reset, i.e. blank, then the three black progressive dots.

P.S. I thought @Cootey was working with Kobo kepubs as he mentioned syncing. But I've read so many posts I may be confused. ;-)

It appears I am an isolated case. From someone's post yesterday: I noticed though that the stylus's markup functionality doesn't seem to work for any kepubs converted by the Kobo Touch Extended driver (or kepubify). Works fine for original epubs though. Does anyone have ideas for a workaround there? I'd be sad to go back to regular epubs on the Elipsa.

[davidfor]

Originally Posted by Skydog

Ah... I just noticed that now when trying another book. No importing message with the progress bar - it acted like a reset, i.e. blank, then the three black progressive dots.

I just put several kepubs on my Glo HD with firmware version 4.28.17826 on it. They were all imported and I was able to open them.

That sounds like the device was rebooted. Which could be a problem with a book. I would recommend removing all the books that have not been imported and trying the in smaller groups or singly. I would check any suspect books in the calibre editor to make sure that shows no errors.

[DNSB]

Originally Posted by Skydog

Presumably, the default assigned by Calibre when "Send to Device" is selected, the root directory of KOBOeReader/. I have not done anything differently from four other Kobo devices and never had a problem. There must be something unique going on in my case since I read one other post from another new Elipsa owner who has converted, sent and read kepubs via the driver.

I would suggest not using the root directory to place your ebooks. Create a directory called Books or whatever name you prefer and use that instead.

[Skydog]

Originally Posted by davidfor

I just put several kepubs on my Glo HD with firmware version 4.28.17826 on it. They were all imported and I was able to open them.

That sounds like the device was rebooted. Which could be a problem with a book. I would recommend removing all the books that have not been imported and trying the in smaller groups or singly. I would check any suspect books in the calibre editor to make sure that shows no errors.

That is precisely what I have been doing. I've only sideloaded a total of six books until I resolve the problem. They were all removed, one factory reset was performed and I have attempted to resend/convert a different, single book one at a time all with the same result. I will check all those that have failed but it seems odd that every single one would have errors.

I haven't sideloaded converted kepubs to my other Kobos since the 5.xx upgrade. Guess I should test those too.

[Skydog]

Originally Posted by DNSB

I would suggest not using the root directory to place your ebooks. Create a directory called Books or whatever name you prefer and use that instead.

Good idea. Which begs a question.

Without realizing Calibre's capabilities many years ago, my earlier Kobo readers had their books dumped in the default root folder. Ironically, it's not how I manage my computers. That said, is it possible to create a new folder, move books to that folder, edit the template for that device, without sc***ing up the entire library, database and communication with Calibre? What would the best method (least risky) to accomplish the task?

[Skydog]

I've checked five random books for errors, none reported. Sent to device via KTE driver, only one book each time. Same result, they are physically on the device but do not import or appear in My Books. I have also tried converting prior to sending. Same thing converting from azw3 or epub to kepub.

Also, I've tested with the Forma with the same result and suspect it will be no different with the Libra. The last successful conversion and importing was in v4.23.

After spending four hours fiddling with this I'm burned out.

[Quoth]

I've Sony PRS350, Sony 4.3" Android 4.x phone (Aldiko Basic), Palm Z1 PDA, Alcatel 6" phone Android, Android 6.x 7" tablet, Android 10" 8.x tablet (Lithium), Kindles DGX, KK3, PW3, Kobo Original Aura 6.8" H2O, Kobo Libra and Boyue Likebook Mars. All work Calibre 5.21 on Linux. Also had an iRiver Cover Story, Kobo Touch and Nook Simple touch and various LCD Binatone ereaders. ALL worked at the time. Been using Calibre since XP and with an old Kindle Basic.

I did have trouble with the MTP driver especially with the Likebook Mars. On the other Android MTP devices simply ejecting the phone/tablet and then starting Calibre worked.
The universal solution for Linux Mint with Mate is to "stop" (not kill) "gvfs-mtp-volume-monitor and only "continue" it if file browser access is needed. On Cinnamon disabling automount works for MTP

But all the Kobos and Kindles I've seen, and the Sony PRS-350, use USB Mass storage. If you can see the files in Explorer/File-managers then Calibre can. Maybe you have the required device plug in disabled? Or your Kobo Touch or Kobo Touch Extended is out of date and/or hasn't got "try to work with newer firmware" ticked, which is usually OK unless the plugin is prehistoric.

Perhaps you didn't update plugins after 4.23?