After the last system upgrade my Android phone is no longer accesible with MTP. It used to work fine; libmtp seems to be unchanged since october 2018 so the problem could be elsewhere? Either way, the device is unlisted.
The phone is a Cat S30, running Android 5.1
$ mtp-detect
libmtp version: 1.1.16
Listing raw device(s)
Device 0 (VID=04b7 and PID=88b8) is UNKNOWN in libmtp v1.1.16.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
04b7:88b8 @ bus 2, dev 11
Attempting to connect device(s)
error returned by libusb_claim_interface() = -6LIBMTP PANIC: Unable to initialize device
Unable to open raw device 0
$ uname -a
Linux computer 5.1.14-arch1-1-ARCH #1 SMP PREEMPT Sat Jun 22 16:28:48 UTC 2019 x86_64 GNU/Linux
Previously I added this to /etc/udev/rules.d/69-libmtp-extra.rules
#Caterpillar Cat S30
ATTR{idVendor}=="04b7", ATTR{idProduct}=="88b8", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
Attached is an extract of journalctl when the device is plugged in.
Anonymous
NB: the message from Dolphin (the file manager) is: "No storage medium found. Make sure your device is iunlocked and has MTP enabled." (it has...)
we track the S30 as 88b9 ...
can you see if the device has some mode to switch between "charging only" and "file access"?
Modern Android phones pop up a dialog for this.