Is the Onyx Note Pro even *supposed* to be supported?
Here's the output of the device detection debugging, as (subtly) requested:
Code:
calibre 3.44 embedded-python: False is64bit: True
Linux-4.19.0-5-amd64-x86_64-with-debian-10.0 Linux ('64bit', 'ELF')
('Linux', '4.19.0-5-amd64', '#1 SMP Debian 4.19.37-3 (2019-05-15)')
Python 2.7.16
Linux: ('debian', '10.0', '')
Interface language: None
Successfully initialized third party plugins: Obok DeDRM (6, 5, 4)
USB devices on system:
[['0x2207', '0xd', '0x310', u'Onyx', u'NotePro', u'0123456789ABCDEF'],
['0x8087', '0xa2b', '0x1', u'', u'', u'']]]
No disabled plugins
Looking for devices of type: MTP_DEVICE
Unknown device USBDevice(busnum=1, devnum=6, vendor_id=0x2207, product_id=0x000d, bcd=0x0310, manufacturer=Onyx, product=NotePro, serial=0123456789ABCDEF) claims to be an MTP device
No MTP devices connected to system
Looking for devices of type: SMART_DEVICE_APP
[...]
No device is connected
Looking for devices...
Devices possibly connected: None
How do I actually make sure that:
Quote:
|
If you are on Linux and the device is an MTP device, make sure it is not automounted by the OS/file manager as only one program can access an MTP device at a time.
|
I don't run a file manager on session startup here, so I don't think anything is grabbing the MTP device. The device is not "ignored" and there's no "plugin" for the device either that can be enabled (hence the first question).
I was told in
this other thread that I can use "adb" to see all files on the device. So far I'm stuck with treating it like a digital camera and it kind of sucks..
Update: I found out how to fix this. It turns out the udev database doesn't cover for the device just yet, so the following needs to be added to (say)
/etc/udev/rules.d/51-android.rules:
Code:
# Onyx Note https://www.mobileread.com/forums/showthread.php?t=296401
ATTR{idVendor}=="2207", ATTR{idProduct}=="0001", MODE="0664", GROUP="plugdev"
# Onyx Note Pro
ATTR{idVendor}=="2207", ATTR{idProduct}=="000d", MODE="0664", GROUP="plugdev"
I found the former in
this thread, the latter is an adaptation. Once that's done, you can either replug the device or re-fire udev with:
Code:
sudo udevadm trigger
Now the question is: where should this file be shipped from?
