USB connection issues - Linux OpenSUSE, Onyx Note Pro

[rhizomatic]

I'm having issues getting Calibre to recognize my NotePro. It used to connect, but I have since changed the OS and upgraded the NotePro to Android 11. The calibre log shows an error of some sort.
The device is recognized by the OS and does not auto-mount.


Calibre log.

Spoiler:

calibre 5.35 embedded-python: False is64bit: True
Linux-5.16.4-1-default-x86_64-with-glibc2.34 Linux ('64bit', 'ELF')
('Linux', '5.16.4-1-default', '#1 SMP PREEMPT Sat Jan 29 12:57:02 UTC 2022 (b146677)')
Python 3.8.12
Interface language: None
Successfully initialized third party plugins: Count Pages (1, 11, 1)
USB devices on system:
[['0x26bd', '0x9917', '0x110', '', 'USB DISK 3.0', '0701576160CE6E42'],
['0xbda', '0xb00b', '0x110', 'Realtek', 'Bluetooth Radio', '00e04c000001'],
['0x4ca', '0x708f', '0x10', 'Generic', 'HP IR Camera', '200901010001'],
['0x2207', '0x11', '0x310', 'Onyx', 'NotePro', 'G8ERIQZS5N'],
['0x25a7', '0xfa61', '0x620', 'Compx', '2.4G Receiver', ''],
['0x4ca',
'0x708e',
'0x7',
'DHBUA019IB25JG',
'HP Wide Vision HD Camera',
'200901010001'],
['0xbda', '0x8153', '0x3000', 'Realtek', 'USB 10/100/1000 LAN', '000001'],
['0x2109',
'0x8888',
'0x1',
'VIA Labs, Inc.',
'USB Billboard Device',
'0000000000000001']]

No disabled plugins
Looking for devices of type: MTP_DEVICE
MTP devices connected:
USBDevice(busnum=1, devnum=77, vendor_id=0x2207, product_id=0x0011, bcd=0x0310, manufacturer=Onyx, product=NotePro, serial=G8ERIQZS5N)

Trying to open: USBDevice(busnum=1, devnum=77, vendor_id=0x2207, product_id=0x0011, bcd=0x0310, manufacturer=Onyx, product=NotePro, serial=G8ERIQZS5N)
Opening device failed:
Traceback (most recent call last):
File "/usr/lib64/calibre/calibre/devices/mtp/unix/driver.py", line 213, in open
self.dev = self.create_device(connected_device)
File "/usr/lib64/calibre/calibre/devices/mtp/base.py", line 23, in synchronizer
return func(self, *args, **kwargs)
File "/usr/lib64/calibre/calibre/devices/mtp/unix/driver.py", line 165, 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=77, tried 1 such devices

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/lib64/calibre/calibre/devices/mtp/unix/driver.py", line 143, in debug_managed_device_detection
self.open(d, 'debug')
File "/usr/lib64/calibre/calibre/devices/mtp/driver.py", line 126, in open
BASE.open(self, device, library_uuid)
File "/usr/lib64/calibre/calibre/devices/mtp/base.py", line 23, in synchronizer
return func(self, *args, **kwargs)
File "/usr/lib64/calibre/calibre/devices/mtp/unix/driver.py", line 216, in open
raise OpenFailed('Failed to open %s: Error: %s'%(
calibre.devices.errors.OpenFailed: Failed to open USBDevice(busnum=1, devnum=77, vendor_id=0x2207, product_id=0x0011, bcd=0x0310, manufacturer=Onyx, product=NotePro, serial=G8ERIQZS5N): Error: Unable to open MTP device with busnum=1 and devnum=77, tried 1 such devices


Looking for devices of type: SMART_DEVICE_APP
All IP addresses {'lo': [{'addr': '127.0.0.1', 'netmask': '255.0.0.0', 'peer': '127.0.0.1'}], 'wlo1': [{'addr': '192.168.0.3', 'netmask': '255.255.255.0', 'broadcast': '192.168.0.255'}], 'enp4s0f3u1u3': [{'addr': '192.168.0.2', 'netmask': '255.255.255.0', 'broadcast': '192.168.0.255'}]}
No device is connected

Looking for devices...

Devices possibly connected: None

dmesg

Spoiler:

[10701.058220] usb 1-1.3.4: new high-speed USB device number 76 using xhci_hcd
[10701.160991] usb 1-1.3.4: New USB device found, idVendor=2207, idProduct=0011, bcdDevice= 3.10
[10701.161001] usb 1-1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[10701.161005] usb 1-1.3.4: Product: NotePro
[10701.161008] usb 1-1.3.4: Manufacturer: Onyx
[10701.161010] usb 1-1.3.4: SerialNumber: G8ERIQZS5N
[10709.022382] usb 1-1.3.4: USB disconnect, device number 76
[10712.070205] usb 1-1.3.4: new high-speed USB device number 77 using xhci_hcd
[10712.176739] usb 1-1.3.4: New USB device found, idVendor=2207, idProduct=0011, bcdDevice= 3.10
[10712.176751] usb 1-1.3.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[10712.176755] usb 1-1.3.4: Product: NotePro
[10712.176758] usb 1-1.3.4: Manufacturer: Onyx
[10712.176760] usb 1-1.3.4: SerialNumber: G8ERIQZS5N

[Renate]

On your Linux, how about the relevant section of "lsusb -v".
On the Note, how about [adb shell] "getprop|grep usb".

[rhizomatic]

There's something funky going on with my USB. This morning it refused to recognize all usb peripherals with lsusb hanging. The issue disappeared when I did a full distro update. Now the NotePro is not recognized by the system at all if I connect it directly to a USB port, but is recognized if I connect if to a hub I have running via my USB-C port.

I've installed adb tools and was about to run it, when Calibre recognized the device (tried this a few times, and sometimes it recognizes it, sometimes it doesn't). The toolbar changes, but it gives a an error popup

Spoiler:

Failed to create folder named Document in ('Internal shared storage',) with error: 2:PTP Layer error 2009: LIBMTP_Create_Folder: Could not send object info.
2:Error 2009: PTP Invalid Object Handle

Traceback (most recent call last):
File "/usr/lib64/calibre/calibre/gui2/device.py", line 87, in run
self.result = self.func(*self.args, **self.kwargs)
File "/usr/lib64/calibre/calibre/gui2/device.py", line 512, in _books
mainlist = self.device.books(oncard=None, end_session=False)
File "/usr/lib64/calibre/calibre/devices/mtp/driver.py", line 218, in books
self.get_driveinfo() # Ensure driveinfo is loaded
File "/usr/lib64/calibre/calibre/devices/mtp/driver.py", line 190, in get_driveinfo
self._update_drive_info(self.filesystem_cache.stor age(sid), location_code)
File "/usr/lib64/calibre/calibre/devices/mtp/driver.py", line 180, in _update_drive_info
self.put_calibre_file(storage, 'driveinfo', BytesIO(raw), len(raw))
File "/usr/lib64/calibre/calibre/devices/mtp/driver.py", line 150, in put_calibre_file
parent = self.ensure_parent(storage, path)
File "/usr/lib64/calibre/calibre/devices/mtp/driver.py", line 403, in ensure_parent
parent = self.create_folder(parent, name)
File "/usr/lib64/calibre/calibre/devices/mtp/base.py", line 23, in synchronizer
return func(self, *args, **kwargs)
File "/usr/lib64/calibre/calibre/devices/mtp/unix/driver.py", line 374, in create_folder
raise DeviceError(
calibre.devices.errors.DeviceError: Failed to create folder named Document in ('Internal shared storage',) with error: 2:PTP Layer error 2009: LIBMTP_Create_Folder: Could not send object info.
2:Error 2009: PTP Invalid Object Handle

and somewhat works. I can send a file, it arrives on the device, but Calibre doesn't recognize that it is on the device on the main screen (the green check mark is missing).

The sending format is Books/{author_sort}/{title} - {authors}, I don't know why it is attempting to create a Document folder.

lsusb -v

Spoiler:

Bus 001 Device 037: ID 2207:0011 Fuzhou Rockchip Electronics Company SmartTab
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x2207 Fuzhou Rockchip Electronics Company
idProduct 0x0011 SmartTab
bcdDevice 3.10
iManufacturer 1 Onyx
iProduct 2 NotePro
iSerial 3 G8ERIQZS5N
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 0x003e
bNumInterfaces 2
bConfigurationValue 1
iConfiguration 4
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 255 Vendor Specific Subclass
bInterfaceProtocol 0
iInterface 5 MTP
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x81 EP 1 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x02 EP 2 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x001c 1x 28 bytes
bInterval 6
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 66
bInterfaceProtocol 1
iInterface 6 ADB Interface
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
bNumConfigurations 1
Device Status: 0x0001
Self Powered

getprop|grep usb

Spoiler:

NotePro:/ $ getprop|grep usb
[init.svc.usbd]: [stopped]
[persist.sys.usb.config]: [adb]
[ro.boottime.usbd]: [32186824403]
[ro.product.usbfactory]: [rockchip_usb]
[sys.usb.config]: [mtp,adb]
[sys.usb.configfs]: [1]
[sys.usb.controller]: [ff580000.usb]
[sys.usb.diag.config]: [0]
[sys.usb.ffs.ready]: [1]
[sys.usb.state]: [mtp,adb]

[Renate]

Yeah, that lsusb sure is a strain on your eyes formatted like that.
I think that your Calibre can't make up its mind if that's PTP or MTP.

Mostly that's because of the stupid descriptors.
I really don't know why anybody uses ff:ff:00 (instead of 06:01:01)
I modified my kernel to fix that and I don't even use MTP.

Have you tried turning off ADB (in Developer Options) as a test?
Check in dmesg for -110 timeouts and general USB thrashing.

[rhizomatic]

My mistake, I assumed that you were looking for a specific event and wouldn't mind. Here's a pastebin link to the same output. https://pastebin.com/bn6iN1LM

The first thing I've tried was toggling the developer option on and off.

I've also tried modifying /etc/usb_modeswitch.conf according to this
https://forums.opensuse.org/showthre...nsfer-with-MTP

Dmseg still presents the same messages, without any indication of a failure to connect (now all USB ports recognize it)

I've also tried installing mtp-tools and simple-mtfs without change. Not sure what else I could try on that front

Spoiler:

❯ zy se mtp
Loading repository data...
Reading installed packages...

S | Name | Summary | Type
---+-----------------------------+------------------------------------------------------------------------+-----------
| ghc-smtp-mail | Simple email sending via SMTP | package
| ghc-smtp-mail-devel | Haskell smtp-mail library development files | package
i | ksmtp | Job-based library to send email through an SMTP server | package
| ksmtp-devel | Development files for KSMTP | package
i | ksmtp-lang | Translations for package ksmtp | package
| leechcraft-lmp-mtpsync | LeechCraft MtpSync Module | package
i | libKPimSMTP5 | Job-based library to send email through an SMTP server | package
| libesmtp-devel | A Library for Posting Electronic Mail | package
i | libesmtp6 | A Library for Posting Electronic Mail | package
| libmtp-devel | Development files for access to MTP Player library | package
i | libmtp-udev | Udev rules for accessing MTP devices | package
i | libmtp9 | Library for accessing MTP Players | package
| libosmo-mtp-1_5_0 | Osmocom Message Transfer Part library | package
| libosmo-mtp-devel | Development files for the Osmocom MTP library | package
| monitoring-plugins-smtp | Check SMTP connections | package
| msmtp | Lightweight SMTP Client | package
| msmtp-doc | Documentation for msmtp | package
| msmtp-lang | Translations for package msmtp | package
| msmtp-mta | MTA based on msmtp | package
i+ | mtp-tools | Commandline utilities for access to MTP Players | package
| mtpaint | Painting program for creating icons and pixel-based artwork | package
| mtpaint-handbook | Handbook for the mtpaint painting application | package
| mtpaint-lang | Translations for package mtpaint | package
| mtpfs | FUSE filesystem that supports MTP devices | package
| mtpfs | FUSE filesystem that supports MTP devices | srcpackage
| mtpfs-debuginfo | Debug information for package mtpfs | package
| mtpfs-debugsource | Debug sources for package mtpfs | package
| perl-Net-SMTP-SSL | SSL support for Net::SMTP | package
| php-pear-Net_SMTP | An implementation of the SMTP protocol | package
| prelude-manager-smtp-plugin | SMTP alert plugin for Prelude Manager | package
| python310-aiosmtpd | SMTP server based on asyncio | package
| python310-aiosmtplib | Python asyncio SMTP client | package
| python38-aiosmtpd | SMTP server based on asyncio | package
| python38-aiosmtplib | Python asyncio SMTP client | package
| python39-aiosmtpd | SMTP server based on asyncio | package
| python39-aiosmtplib | Python asyncio SMTP client | package
i+ | simple-mtpfs | Simple MTP fuse filesystem driver | package
| smtpping | A tool for measuring SMTP server delay, delay variation and throughput | package
| syslog-ng-smtp | SMTP output support for syslog-ng | package

[Renate]

I don't know. We've drifted from pure USB to Calibre which I don't really know. I think that your Calibre is wanting to use "Documents" as your root directoy and that you need to configure that somewhere in the Calibre preferences.

[rhizomatic]

It works. I uninstalled the zypper provided Calibre, downloaded the binary Calibre from the official site, and again did a full update of my system

[rhizomatic]

Jinxed, it worked only once.

[salamanderjuice]

What desktop environment are you using? (if any). Is it auto-mounting it in your file manager by default? I can't access my Boox devices through Calibre if it's mounted in my file manager and I can't access it in the file manager if it's mounted in Calibre. Perhaps something somewhere is mounting it before Calibre gets a chance?

[rhizomatic]

Originally Posted by salamanderjuice

What desktop environment are you using? (if any). Is it auto-mounting it in your file manager by default? I can't access my Boox devices through Calibre if it's mounted in my file manager and I can't access it in the file manager if it's mounted in Calibre. Perhaps something somewhere is mounting it before Calibre gets a chance?

That's the first thing I've checked, and no, it's not auto-mounting. I'm using the latest KDE.

Actually, it does work sometimes now. If I connect Onyx as soon as the system boots, Calibre will recognize it, but it will stop recognizing after a few connects/disconnects. Then I will have to reboot to have it recognize it again. It's a strange bug, but at least it's consistent now.

[Markismus]

Originally Posted by rhizomatic

... upgraded the NotePro to Android 11.

How did you do that, I saw a Note Pro upgrade from 6 to 9. However, I never saw an upgrade to 11. Could you explain?

[rhizomatic]

Originally Posted by Markismus

How did you do that, I saw a Note Pro upgrade from 6 to 9. However, I never saw an upgrade to 11. Could you explain?

I tried googling a bit but couldn't find the tutorial I used. There was an unofficial official post someplace with instructions. Basically you flash it on your own. I managed to do it with Windows VM on Linux.

This post references the original instructions, but doesn't link to it
https://help.boox.com/hc/en-us/commu...age=1#comments