MTP and perhaps USB connection broken?

Added by Zrab Zrab over 5 years ago


some days ago, i realised that MTP on my S3 didn't want to work (GNOME Shell showed me the corresponding icon for 0.1s). I supposed it was due to some bad karma, so I just waited. Now, the problem still remains and I used directly some commandline tools to try to test everything. I also realised then that USB-Network neither works.
Now, it looks like there is some sort of issue with the USB-stack.
  1. lsusb (with usbnetworking on)
    Bus 001 Device 008: ID 04e8:6863 Samsung Electronics Co., Ltd GT-I9500 [Galaxy S4] / GT-I9250 [Galaxy Nexus] (network tethering)
  1. lsusb (without usbnetworking on)
    Samsung Electronics Co., Ltd GT-I9250 Phone [Galaxy Nexus] (Mass storage mode)
  1. mtp-detect
    Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.6

Listing raw device(s)
Device 0 (VID=04e8 and PID=685c) is a Samsung Galaxy models (MTP+ADB).
Found 1 device(s):
Samsung: Galaxy models (MTP+ADB) (04e8:685c) @ bus 1, dev 9
Attempting to connect device(s)
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0

The lsusb stuff looks quite weird. It it may be helpfull, I could lauch some test on 2 other phones (S2, S4; no custom ROM/OS) and post the results here.

Well, I hope it's just me or perhaps my cable, but who knows ...


Replies (2)

RE: MTP and perhaps USB connection broken? - Added by Paul Kocialkowski over 5 years ago

MTP support is not complete on GNU/Linux distros that don't use the very latest versions of the packages. I got it to work on Debian unstable as well as Fedora 20 and Trisquel 7 (not released yet) while it is broken on earlier versions of these systems.

RE: MTP and perhaps USB connection broken? - Added by Zrab Zrab over 5 years ago

Well, I suppose that I should have the "very latest versions of the packages" with Parabola (aka Arch-libre). Aparently, it's a problem with gvfs-mtp. After removing the package, everything seems to work fine (eventhough the classic mtp interface isn't as easy to use as gvfs-mtp). I'm going to look for details.