Cannot connect Android phone, MTP support not working in 13.1

English Hardware
1

I’m considering moving from Xubuntu to openSUSE. So far, I love this OS, really nice! I just can’t seem to get MTP working no matter what I do. I have installed:

whitebox:/home/scottbomb # zypper se -i mtp
Loading repository data...
Reading installed packages...

S | Name      | Summary                                         | Type   
--+-----------+-------------------------------------------------+--------
i | go-mtpfs  | Mount MTP devices over FUSE                     | package
i | kio_mtp   | Access MTP devices in KDE                       | package
i | libesmtp  | A Library for Posting Electronic Mail           | package
i | libmtp9   | Library for accessing MTP Players               | package
i | mtp-tools | Commandline utilities for access to MTP Players | package
i | mtpfs     | FUSE filesystem that supports MTP devices       | package

Yet it still won’t mount. This is what Dolphin gives:

 An error occurred while accessing 'Home', the system responded: The requested operation has failed: Error mounting /dev/fd0 at /run/media/scottbomb/disk: Command-line `mount -t "auto" -o "uhelper=udisks2,nodev,nosuid" "/dev/fd0" "/run/media/scottbomb/disk"' exited with non-zero exit status 32: mount: /dev/fd0 is not a valid block device

This is a deal-breaker as I do connect my phone and transfer files daily. Can anyone suggest a real fix?

2

MTP devices do not behave as block devices, so do not get mounted as such. However, KDE has kio-mtp which is supposed to provide file access for MTP devices that makes such a device appear as if it is mounted. There are a lot of threads and bug reports around that suggest that it is not working for some hardware, so you might want to search online first. BTW, the device node (/dev/fd0) is usually associated with floppy disk hardware, so I’m not sure why that message is being reported. In any case, it might pay to examine the kernel messages reported upon attaching your phone

sudo failf /var/log/messages

Maybe that will yield some useful info.

3

If you wish to experiment with this a little further, the following Arch Wiki page is a good place to start

https://wiki.archlinux.org/index.php/MTP

4

Here’s what I get for tail /var/log/messages:

2013-11-27T16:15:32.648550-06:00 whitebox kernel:  4042.909034] usb 2-5: device descriptor read/64, error -62
2013-11-27T16:15:32.913569-06:00 whitebox kernel:  4043.174046] usb 2-5: device descriptor read/64, error -62
2013-11-27T16:15:33.171575-06:00 whitebox kernel:  4043.432057] usb 2-5: new full-speed USB device number 12 using ohci-pci
2013-11-27T16:15:33.335564-06:00 whitebox kernel:  4043.596053] usb 2-5: device descriptor read/64, error -62
2013-11-27T16:15:33.600565-06:00 whitebox kernel:  4043.861046] usb 2-5: device descriptor read/64, error -62
2013-11-27T16:15:33.858581-06:00 whitebox kernel:  4044.119061] usb 2-5: new full-speed USB device number 13 using ohci-pci
2013-11-27T16:15:34.262565-06:00 whitebox kernel:  4044.523037] usb 2-5: device not accepting address 13, error -62
2013-11-27T16:15:34.419563-06:00 whitebox kernel:  4044.680047] usb 2-5: new full-speed USB device number 14 using ohci-pci
2013-11-27T16:15:34.823589-06:00 whitebox kernel:  4045.084048] usb 2-5: device not accepting address 14, error -62
2013-11-27T16:15:34.823627-06:00 whitebox kernel:  4045.084083] hub 2-0:1.0: unable to enumerate USB device on port 5

Running lsusb … not even detected. However, it is charging. Strange. I’ll check out the Arch page too and post any results if I can get it to work.

5

Are you using old hardware? (Full speed communication usually associated with USB1 hardware.)

2013-11-27T16:15:33.171575-06:00 whitebox kernel:  4043.432057] usb 2-5: new full-speed USB device number 12 using ohci-pci

Without wishing to confuse, I have read that USB hubs (inside computer) use a transaction translator to determine OHCI and EHCI connected devices - usually one for each port, but sometimes one shared for all ports on the internal hub. When the latter is the case, one USB 1 device connected is enough to force all ports to the lower speed. Anyway, USB 2 is far more common, so I had to ask…you can use ‘lsusb’ to report your USB hardware

6

Running lsusb … not even detected. However, it is charging. Strange. I’ll check out the Arch page too and post any results if I can get it to work.

No, I don’t think you’ll succeed until you get the USB communication sorted… do other USB devices report and work ok?

7

On 2013-11-28 00:26, deano ferrari wrote:
>
>> Running lsusb … not even detected. However, it is charging. Strange.
>> I’ll check out the Arch page too and post any results if I can get it to
>> work.
> No, I don’t think you’ll succeed until you get the USB communication
> sorted… do other USB devices report and work ok?

Weird. My Android phone connects to the computer without MTP, as a disk.
Two disks actually, one for the memory card, another for the internal
space. I have to tell the phone that I want to connect, though. It is a
Samsung.

I can also connect using bluetooth, but that fails a lot.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

8

The mouse is USB and it’s detected. I plugged in a joystick and it was also detected. From lsusb:

Bus 001 Device 002: ID 1a40:0101 Terminus Technology Inc. 4-Port HUB
Bus 002 Device 002: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse
Bus 002 Device 027: ID 046d:c215 Logitech, Inc. Extreme 3D Pro
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

I unplugged the USB hub and plugged in the phone. Still nothing.

9

It used to connect as a disk, until Google screwed that up a few months ago with an “update”. I believe it was with the Jellybean release.

10

Yes, I think some Android devices offer block storage access and some only provide MTP communication. Lots of threads about that, but the OP explicitly mentioned MTP connectivity…

11

Yes, I recall that affected many users… the only problem seems to be variable degrees of MTP support within a Linux environment :frowning:

12

What android device are you trying to connect to?

Have you tried gmtp? This work’s with my Droid Ultra. Though since switching to 13.1, I’ve had no issuse with my MTP device.

13

It’s an HTC One with Android ver. 4.1.1. I Googled gmtp and found it on SourceForge. While it may work, it’s not my ideal solution as I’d like to be able to access the phone in Dolphin like I do on the Xubuntu machines. I downloaded it anyway but found that it’s in .pkg (?) format as opposed to RPM. I may some day learn how to build my own .deb or .rpm packages but that’s quite the undertaking that I simply don’t have time for right now, especially as I’m just testing out this distro.

14

I totally understand. Forgive me, as my last device was a Moto Droid Razr, which now has Android 4.1.2. I did find this link, and decided to post it, just to double check thing’s on the phone, as you say, you own the HTC One.

How to connect Android to PC with USB Mass Storage Mode |

I see you have a USB hub. I take that being external. Have you tried unplugging everything besides keyboard, and mouse, and see if it works straight to the PC. Also, have you checked your cable? Just going down the check list.

I also found this, but please, check with the more experienced people before hand, as I’m also new to the system. I’d hate to be more cause to the problem, than the solution.

http://www.rpmseek.com/rpm-pl/gmtp.html?hl=com&cx=0::

15

First place to look for openSUSE RPM packages is

software.opensuse.org:

but I totally understand your preference for to use kio-mtp /Dolphin. When comparing performance with other distros, only the KDE and libmtp versions should play a part here. So, it would be good to know what your Xubuntu machines have installed.

16

On 2013-11-28 01:36, scottbomb wrote:
>
> robin_listas;2602924 Wrote:
>> On 2013-11-28 00:26, deano ferrari wrote:
>> Weird. My Android phone connects to the computer without MTP, as a disk.
>> Two disks actually, one for the memory card, another for the internal
>> space. I have to tell the phone that I want to connect, though. It is a
>> Samsung.
>
> It used to connect as a disk, until Google screwed that up a few months
> ago with an “update”. I believe it was with the Jellybean release.

Oh. I’m fortunate, then, my phone uses version 2.3.6 :slight_smile:

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

17

I downloaded and installed that package, thanks. Unfortunately it’s still not working. Tail of dmesg:

  154.085046] usb 2-6: new full-speed USB device number 3 using ohci-pci
  154.250069] usb 2-6: device descriptor read/64, error -62
  154.516064] usb 2-6: device descriptor read/64, error -62
  154.774042] usb 2-6: new full-speed USB device number 4 using ohci-pci
  154.939035] usb 2-6: device descriptor read/64, error -62
  155.205050] usb 2-6: device descriptor read/64, error -62
  155.463050] usb 2-6: new full-speed USB device number 5 using ohci-pci
  155.867038] usb 2-6: device not accepting address 5, error -62
  156.024046] usb 2-6: new full-speed USB device number 6 using ohci-pci
  156.428044] usb 2-6: device not accepting address 6, error -62
  156.428082] hub 2-0:1.0: unable to enumerate USB device on port 6

MTP support was built into Xubuntu 13.10 and I think it was added during 13.04. Nevertheless, it works there natively with Thunar and Dolphin. I’m going to try out Fedora too and see what their KDE experience is like. I’m hoping to get my hands dirty with the Red Hat commands and learn the Red Hat way of doing stuff I know how to do in Xubuntu.

I like and prefer to use KDE but Kubuntu is very buggy, especially with graphics drivers lately. I am very impressed with how openSUSE is built. No problems (yet) with that bug-infested Google Earth (Kubuntu chokes on it). I will continue to experiment with it but it won’t replace Xubuntu on my other machines unless I can get it to work on this one. I like other aspects of the OS too, especially Yast and the ease with which I can customize things. I am hopeful!

18

On 2013-11-28 02:06, deano ferrari wrote:

> Yes, I think some Android devices offer block storage access and some
> only provide MTP communication. Lots of threads about that, but the OP
> explicitly mentioned MTP connectivity…

I see. I thought that the OP might be able to activate block storage
instead, seems more reliable.

–
Cheers / Saludos,

Carlos E. R.
(from 12.3 x86_64 “Dartmouth” at Telcontar)

19

Are you plugging the phone into the hub or direct to a USB port? Have you tried connecting to another port on the computer? (One is USB 1.1, one is USB 2)

20

Simply installing a package like that will not help as I mentioned previously. (I only explained how to find openSUSE RPMs.) You need to get to the bottom of the USB error messages, which is why I asked if the phone is being attached via a hub, or directly to the computer’s USB ports.