Enhancement-Kindle fire HD 8

Bug #1797890 reported by John G
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
calibre
Invalid
Undecided
Unassigned
calibre (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Calibre recently came out with the eighth generation kindle in early October and Calibre does not pick up the new device. It shows in the computer but they do not talk to each other. Have tried all the steps recommended but still no success. Thank you

Revision history for this message
Kovid Goyal (kovid) wrote : Re: calibre bug 1797890

See https://manual.calibre-ebook.com/faq.html#my-device-is-not-being-detected-by-calibre

If those do not work, then post the debug log as described there.

 status incomplete

Changed in calibre:
status: New → Incomplete
Revision history for this message
John G (apd27) wrote :
Download full text (3.5 KiB)

Linked to Bug #1797992

Device connected.
Windows Version: 10.0.10011.16384
Calibre 3.32
No SD card and only device attached
"Fire" showing in File Explorer
When clicked on states file is empty
Under ignored devices nothing there
Both computer and device restarted separately and restarted again attached via USB unsuccessfully

Brand new device (8th generation) updated and attached to computer via USB

calibre 3.32 embedded-python: True is64bit: False
Windows-10-10.0.17134-SP0 Windows ('32bit', 'WindowsPE')
32bit process running on 64bit windows
('Windows', '10', '10.0.17134')
Python 2.7.12+
Windows: ('10', '10.0.17134', 'SP0', u'Multiprocessor Free')
Interface language: None
Successfully initialized third party plugins: Gather KFX-ZIP (from KFX Input) (1, 9, 0) && Package KFX (from KFX Input) (1, 9, 0) && KFX metadata reader (from KFX Input) (1, 9, 0) && KFX Input (1, 9, 0) && KindleUnpack - The Plugin (0, 81, 5) && Set KFX metadata (from KFX Output) (1, 23, 0) && KFX Output (1, 23, 0) && Kindle hi-res covers (0, 4, 0) && Kindle Collections (1, 7, 21)
USB devices on system:
(USBDevice(vendor_id=0x8087 product_id=0x24 bcd=0x0 devid=usb\vid_8087&pid_0024&rev_0000 devinst=2),
 USBDevice(vendor_id=0x45e product_id=0x745 bcd=0x252 devid=usb\vid_045e&pid_0745&rev_0252&mi_01 devinst=3),
 USBDevice(vendor_id=0x45e product_id=0x745 bcd=0x252 devid=usb\vid_045e&pid_0745&rev_0252&mi_02 devinst=4),
 USBDevice(vendor_id=None product_id=None bcd=None devid=usb\root_hub20&vid8086&pid1e26&rev0004 devinst=5),
 USBDevice(vendor_id=0x45e product_id=0x745 bcd=0x252 devid=usb\vid_045e&pid_0745&rev_0252 devinst=6),
 USBDevice(vendor_id=0x64e product_id=0x812e bcd=0x2709 devid=usb\vid_064e&pid_812e&rev_2709&mi_00 devinst=7),
 USBDevice(vendor_id=None product_id=None bcd=None devid=usb\root_hub20&vid8086&pid1e2d&rev0004 devinst=8),
 USBDevice(vendor_id=0x8087 product_id=0x24 bcd=0x0 devid=usb\vid_8087&pid_0024&rev_0000 devinst=9),
 USBDevice(vendor_id=0x64e product_id=0x812e bcd=0x2709 devid=usb\vid_064e&pid_812e&rev_2709 devinst=10),
 USBDevice(vendor_id=0x8087 product_id=0x7da bcd=0x7869 devid=usb\vid_8087&pid_07da&rev_7869 devinst=11),
 USBDevice(vendor_id=None product_id=None bcd=None devid=usb\vid_1949&pid_0331&rev_???? devinst=1),
 USBDevice(vendor_id=0xbda product_id=0x129 bcd=0x3960 devid=usb\vid_0bda&pid_0129&rev_3960 devinst=12),
 USBDevice(vendor_id=0x45e product_id=0x745 bcd=0x252 devid=usb\vid_045e&pid_0745&rev_0252&mi_00 devinst=13),
 USBDevice(vendor_id=None product_id=None bcd=None devid=usb\root_hub30&vid8086&pid1e31&rev0004 devinst=14))

No disabled plugins
Looking for devices of type: MTP_DEVICE
List of WPD PNP ids:
[u'\\\\?\\usb#vid_1949&pid_0331#g0w0t9058277f7mv#{6ac27878-a6fa-4155-ba85-f98f491d4f33}']
MTP device: \\?\usb#vid_1949&pid_0331#g0w0t9058277f7mv#{6ac27878-a6fa-4155-ba85-f98f491d4f33}
{'device_version': u'1.0',
 'friendly_name': u'',
 'has_bulk_properties': True,
 'has_storage': True,
 'manufacturer_name': u'Amazon',
 'model_name': u'Fire',
 'protocol': u'MTP: 1.00',
 'serial_number': u'G0W0T9058277F7MV',
 'storage': [],
 'type': 'media player'}
Not a suitable MTP device, ignoring

No suitable MTP devices found

Looking for devi...

Read more...

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

Your device is still reporting empty sotrage, if rebooting does not fix
it, your remaining options are:

1) Reset the device
2) Use a wireless conenction methods, as described here:
https://manual.calibre-ebook.com/faq.html#how-do-i-use-calibre-with-my-android-phone-tablet-or-kindle-fire-hd
3) Get a replacement from amazon

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for calibre because there has been no activity for 60 days.]

Changed in calibre:
status: Incomplete → Expired
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in calibre (Ubuntu):
status: New → Confirmed
Revision history for this message
James Cuzella (trinitronx) wrote :
Download full text (3.3 KiB)

Same issue observed in calibre 4.99.4+dfsg+really4.12.0-1build1
on Focal 20.04 LTS
with Kindle Fire HD 8 plus (10th generation)

Following the guide here seems to help: https://manual.calibre-ebook.com/faq.html#android-usb

If you miss or can't find the USB notification by swiping down:

- Swipe down from top of the device's screen
- Swipe down again to expand the system control widgets (WiFi, Bluetooth, etc...)
- Tap the Gear icon in the lower right to open Settings (OR just tap "Settings" icon from the device's homescreen)
- Tap "Connected Devices"
- Tap "USB"
- Under "Use USB for", tap "File Transfer"

Note: When trying to switch "USB controlled by" to "Connected device", it did not seem to work and just says "Couldn't switch".

After enabling File Transfer mode, the device was mounted under an unusual path (when compared to most standard USB mass storage devices):

    /run/user/1000/gvfs/mtp:host=Amazon_XXXXXX_XXXXXXXXXXXXXXXX/Internal storage

The device's product ID and serial number should be listed in place of the X's.

After doing this, I opened up Calibre via the command line. It threw this exception error:

Device 0 (VID=1949 and PID=0581) is UNKNOWN in libmtp v1.1.17.
Please report this VID/PID and the device model to the libmtp development team
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device
Error while trying to open MTPDevice(busnum=1, devnum=35, vendor_id=6473, product_id=1409, bcd=547, serial='XXXXXXXXXXXXXXXX', manufacturer='Amazon', product='XXXXXX') (Driver: <calibre.devices.mtp.driver.MTP_DEVICE object at 0x7f294280d880>)
Traceback (most recent call last):
  File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 218, in open
    self.dev = self.create_device(connected_device)
  File "/usr/lib/calibre/calibre/devices/mtp/base.py", line 25, in synchronizer
    return func(self, *args, **kwargs)
  File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 171, in create_device
    return self.libmtp.Device(d.busnum, d.devnum, d.vendor_id,
libmtp.MTPError: Unable to open MTP device with busnum=1 and devnum=35, tried 1 such devices

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/calibre/calibre/gui2/device.py", line 297, in detect_device
    dev.open(cd, self.current_library_uuid)
  File "/usr/lib/calibre/calibre/devices/mtp/driver.py", line 125, in open
    BASE.open(self, device, library_uuid)
  File "/usr/lib/calibre/calibre/devices/mtp/base.py", line 25, in synchronizer
    return func(self, *args, **kwargs)
  File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 221, in open
    raise OpenFailed('Failed to open %s: Error: %s'%(
calibre.devices.errors.OpenFailed: Failed to open MTPDevice(busnum=1, devnum=35, vendor_id=6473, product_id=1409, bcd=547, serial='XXXXXXXXXXXXXXXX', manufacturer='Amazon', product='XXXXXX'): Error: Unable to open MTP device with busnum=1 and devnum=35, tried 1 such devices

So in this case it appears to be an error caused by an unrecognizable device in the current version of libmtp:

    Device 0 (VID=1949 and PID=0581) is UNKNOWN in libmtp v1.1.17.

T...

Read more...

Changed in calibre:
status: Expired → Confirmed
Revision history for this message
Kovid Goyal (kovid) wrote :

That error means your device is being opened by the desktop environmnet/file manager. Prevent it from being auto-mounted and you will be fine. On Linux, only one program can talk to an MTP based device at a time.

Changed in calibre:
status: Confirmed → Invalid
Revision history for this message
James Cuzella (trinitronx) wrote :
Download full text (4.2 KiB)

After testing out the newer version of libmtp v1.1.18, I was able to get even the current version of Calibre working (as long as I unmounted the device from Nautilus / GVFS first!)

Here is the initial error if the device is already automounted by GVFS:

Device 0 (VID=1949 and PID=0581) is a Amazon Kindle Fire HD8 Plus.
libusb_claim_interface() reports device is busy, likely in use by GVFS or KDE MTP device handling alreadyLIBMTP PANIC: Unable to initialize device
Error while trying to open MTPDevice(busnum=1, devnum=36, vendor_id=6473, product_id=1409, bcd=547, serial='XXXXXXXXXXXXXXXX', manufacturer='Amazon', product='XXXXXX') (Driver: <calibre.devices.mtp.driver.MTP_DEVICE object at 0x7f8353368880>)
Traceback (most recent call last):
  File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 218, in open
    self.dev = self.create_device(connected_device)
  File "/usr/lib/calibre/calibre/devices/mtp/base.py", line 25, in synchronizer
    return func(self, *args, **kwargs)
  File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 171, in create_device
    return self.libmtp.Device(d.busnum, d.devnum, d.vendor_id,
libmtp.MTPError: Unable to open MTP device with busnum=1 and devnum=36, tried 1 such devices

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/calibre/calibre/gui2/device.py", line 297, in detect_device
    dev.open(cd, self.current_library_uuid)
  File "/usr/lib/calibre/calibre/devices/mtp/driver.py", line 125, in open
    BASE.open(self, device, library_uuid)
  File "/usr/lib/calibre/calibre/devices/mtp/base.py", line 25, in synchronizer
    return func(self, *args, **kwargs)
  File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 221, in open
    raise OpenFailed('Failed to open %s: Error: %s'%(
calibre.devices.errors.OpenFailed: Failed to open MTPDevice(busnum=1, devnum=36, vendor_id=6473, product_id=1409, bcd=547, serial='XXXXXXXXXXXXXXXX', manufacturer='Amazon', product='XXXXXX'): Error: Unable to open MTP device with busnum=1 and devnum=36, tried 1 such devices
Device 0 (VID=1949 and PID=0581) is a Amazon Kindle Fire HD8 Plus.
libusb_claim_interface() reports device is busy, likely in use by GVFS or KDE MTP device handling alreadyLIBMTP PANIC: Unable to initialize device
Error while trying to open MTPDevice(busnum=1, devnum=37, vendor_id=6473, product_id=1409, bcd=547, serial='XXXXXXXXXXXXXXXX', manufacturer='Amazon', product='XXXXXX') (Driver: <calibre.devices.mtp.driver.MTP_DEVICE object at 0x7f8353368880>)
Traceback (most recent call last):
  File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 218, in open
    self.dev = self.create_device(connected_device)
  File "/usr/lib/calibre/calibre/devices/mtp/base.py", line 25, in synchronizer
    return func(self, *args, **kwargs)
  File "/usr/lib/calibre/calibre/devices/mtp/unix/driver.py", line 171, in create_device
    return self.libmtp.Device(d.busnum, d.devnum, d.vendor_id,
libmtp.MTPError: Unable to open MTP device with busnum=1 and devnum=37, tried 1 such devices

During handling of the above exception, another exception occurred:

Traceback (most recent call ...

Read more...

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.