Comment 55 for bug 1314556

I have a bit more info here. I have Ubuntu 14.04 (15.04 all the same) running on HP Envy m6 laptop + Android YotaPhone1 and have all listed problems with MTP/ADB here: the connection is unreliable (works 1 of 10 or does not work at all). None of the suggested solutions (using mtp tools or killing gvfs processes) helps.

Same phone connects just fine (MTP/ADB) on Windows 8 on same laptop and on some 2year-old OpenSUSE on another comp.

What I have noted is that lsusb hangs (even when the phone and other devices are disconnected) for a couple of minutes before showing the result (mtp-detect also hangs rather than shows error), so it gave me an idea that this might be a hardware problem and I have made some tests.

I take 2 laptops HP Envy m6 and Sony Vaio and 2 live CDs Ubuntu 14.04 (15.04 all the same results) and OpenSUSE 13.2 live with gnome.

1) HP Envy+Ubuntu 14.04 (15.04) - both live and installed:
- lsusb hangs (shows result after few minutes)
- MTP/ADB extremely unreliable

2) HP Envy+OpenSUSE 13.2 gnome live:
- lsusb shows immediately
- MTP works just fine (most likely ADB would work too, but it is not installed on live system)

3) Sony Vaio+Ubuntu 14.04 (15.04):
- lsusb shows immediately
- MTP works just fine

So, I have one laptop where Ubuntu 14.04 (15.04)+MTP/ADB does NOT work and OpenSUSE 13.2+MTP DOES work and another laptop where Ubuntu 14.04 (15.04)+MTP DOES work. The MTP/ADB software problem 100% correlates with problem with lsusb.

This is most likely (definitely) hardware+software combination problem. And this problem most likely not on GVFS/MTP layer, but on lower layer with lsusb/kernel.

I will run more tests and make more investigations on my hardware, if someone points me further what I should do.

Attach some system output from OpenSUSE 13.2 gnome live (MTP works):
uname -a
lsmod
after connecting the phone:
dmesg
lsusb
lsusb -t
lsusb -v
lsusb -D /dev/bus/usb/003/003