Feature Request: Woxter Scriba 190 support

Bug #1317892 reported by Zup
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
calibre
Fix Released
Undecided
Unassigned

Bug Description

Using Debian jessie/sid with standard calibre package (1.25.0), the device is detected as an Aluratek Color (that makes no sense, since that is a TFT device and this one is an e-Ink device). Using Windows, the device is not detected.

I guess the problem begind with drive mounting: in Linux the internal memory is shown BEFORE the SD slot, but in Windows the SD slot is shown before. My list of features:

E-book formats supported (as stated in box):
- pdf (to a surprisingly good level)
- epub
- fb2
- txt
- mobi
- html
- pdb
- rtf
- djvu
- chm
- prc
- doc (it DOES open MS Office docs, but don't format them correctly).

Image formats supported:
- jpeg
- bmp
- gif
- png

Screen type:
- Resolution 600x800
- 16 gray levels
- 6 inch e-ink pearl

Other features:
- It has a micro SD slot.
- It DOES NOT require the books to be placed in an specific directory.
- It DOES allow subdirectories and multiple level subdirectories.
- It DOES support Adobe DRM.

Some other (strange) features:
- It contains a manual, but it's placed in a hidden partition (so it's not displayed in the book list nor in the drives shown in computer).
- When connected on Windows, the device shows the SD slot BEFORE the internal memory (on my Windows 7, H: is the SD slot and I: is the internal memory).
- When connected on Linux, the device shows SD slot AFTER the internal memory (on my Debian, /dev/sdc is the internal memory and /dev/sdd the SD slot).
- On Linux (Debian Jessie/Sid using calibre 1.25.0+dfsg-1), the device is recognized as an Aluratek Color, but on Windows 7 Pro 64 with calibre 1.36.0 64 bit, it is not detected.

The attached file contains this list of features and the logs from calibre 1.36.0 with the device attached and disconnected.

Revision history for this message
Zup (rubenatch) wrote :
Revision history for this message
Kovid Goyal (kovid) wrote : Re: calibre bug 1317892

That device shares usb ids with the aluratek color, which is why it will
be recognized as such. The vendor and product strings for windows have
to be added to the aluratek driver, to enable detection on windows.

Revision history for this message
Kovid Goyal (kovid) wrote : Fixed in master

Fixed in branch master. The fix will be in the next release. calibre is usually released every Friday.

 status fixreleased

Changed in calibre:
status: New → Fix Released
Revision history for this message
Kovid Goyal (kovid) wrote : Re: calibre bug 1317892

As for the drives being swapped, that is a firmware bug and you should
report it to the device manufacturer. It will cause calibre to detect
the sd card as the main memory and vice versa, but that is
harmless.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.