Subject: mount MTP phone

From: Tony Baldwin <[email-masked]>
Date: Sun, 4 Sep 2016 21:13:30 -0400

I'm at a loss, friends:
I have a phone (Motorola Droid Turbo), which functions as an MTP device, 
and auto-mounts on Win7, but not on Debian 8.
AFAIK, I have all the requisite MTP packages installed .
When I plug it in, lsusb doesn't show it at all, however.
I don't know what else to do to try and diagnose or resolve the matter.
Anyone?
I'm running Jessie on AMD64

-- 
http://tonybaldwin.me
all tony, all the time

---

From: Dan Purgert <[email-masked]>
Date: Mon, 5 Sep 2016 10:50:00 -0000 (UTC)

Tony Baldwin wrote:
> [snip]

Is the phone set to "USB for Charge Only"?  Mine ~always~ resets to
that, and I have to change it every time I plug it in and want to use it
as a USB drive.

-- 
|_|O|_| Registered Linux user #585947
|_|_|O| Github: https://github.com/dpurgert
|O|O|O|

---

From: Tony Baldwin <[email-masked]>
Date: Mon, 5 Sep 2016 08:25:07 -0400

> that, and I have to change it every time I plug it in and want to use it
Mine is definitely set to connect as an MTP device.

Thanks,
Tony

-- 
http://tonybaldwin.me
all tony, all the time

---

From: Carl Fink <[email-masked]>
Date: Sun, 4 Sep 2016 21:22:28 -0400

On 09/04/2016 09:13 PM, Tony Baldwin wrote:
> I'm at a loss, friends:
> I have a phone (Motorola Droid Turbo), which functions as an MTP 
> device, and auto-mounts on Win7, but not on Debian 8.
Have you looked at /var/log/syslog for the relevant period?

-- 
Carl Fink
[email-masked]

---

From: Tony Baldwin <[email-masked]>
Date: Sun, 4 Sep 2016 21:30:38 -0400

> Have you looked at /var/log/syslog for the relevant period?

Sorry Carl, you're getting this twice now (it's been a while since I was 
active on lists, I've forgotten how to behave), but

I confess, I had not, until now.

Seems I get a bunch of this:

Sep  4 21:23:47 deathstar kernel: [26533.020450] hub 10-0:1.0: unable to 
enumerate USB device on port 1

-- 
http://tonybaldwin.me
all tony, all the time

---

From: Joe Pfeiffer <[email-masked]>
Date: Tue, 06 Sep 2016 09:19:07 -0600

Tony Baldwin <[email-masked]> writes:

> Sorry Carl, you're getting this twice now (it's been a while since I
> was active on lists, I've forgotten how to behave), but
>
> Sep  4 21:23:47 deathstar kernel: [26533.020450] hub 10-0:1.0: unable
> to enumerate USB device on port 1

That's your problem...  you should be seeing something more like

Sep  6 09:13:02 snowball kernel: [1030652.496395] usb 5-2.1.4: new high-speed USB device number 13 using xhci_hcd
Sep  6 09:13:02 snowball kernel: [1030652.596926] usb 5-2.1.4: New USB device found, idVendor=18d1, idProduct=4ee1
Sep  6 09:13:02 snowball kernel: [1030652.596930] usb 5-2.1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Sep  6 09:13:02 snowball kernel: [1030652.596931] usb 5-2.1.4: Product: Nexus 5
Sep  6 09:13:02 snowball kernel: [1030652.596933] usb 5-2.1.4: Manufacturer: LGE
Sep  6 09:13:02 snowball kernel: [1030652.596934] usb 5-2.1.4: SerialNumber: 039d5ef3437cc5b0

Of course, the strings I'm showing are for a different phone!   Most
commonly when I've seen a device fail to enumerate, the problem has been
the cable (I know, you've already said you've tried multiple cables).
But you need to be enumerating before absolutely anything else will
happen and before anything else is relevant...  you aren't having
trouble with other USB devices?  No chance there's a USB enable/disable
on the phone?  (on mine, things enumerate properly like I showed, but
nothing else happens until I select "USB for file transfers" in a
dropdown on the phone).
-- 
"Erwin, have you seen the cat?" -- Mrs. Shrödinger

---

From: Frédéric Marchal <[email-masked]>
Date: Wed, 07 Sep 2016 08:07:41 +0200

On Tuesday 06 September 2016 09:19:07 Joe Pfeiffer wrote:
> Most commonly when I've seen a device fail to enumerate, the problem has
> been the cable (I know, you've already said you've tried multiple cables).

I second that opinion.

MTP only works with a 24/28 gauge USB cable on my daughter's Android phone. 
That's a cable with thick power wires.

With a standard 28/28 gauge USB cable the MTP device is detected but it 
disconnects within seconds. It continues with a sequence of connect/disconnect 
until Android complains that it can not find any suitable software on the host 
computer to communicate with.

I suspect the OP might have had multiple issues that had to be fixed in the 
right order to solve the problem. The cable being only one of them.

Frederic

---

From: Dutch Ingraham <[email-masked]>
Date: Sun, 4 Sep 2016 21:01:26 -0500

> enumerate USB device on port 1

What do you get with dmesg?  For example, run <sudo dmesg -wH>, then plug the
device in.  What is the complete output?

Also, do you have libmtp installed?

---

From: Anthony Baldwin <[email-masked]>
Date: Sun, 4 Sep 2016 22:52:33 -0400

> Also, do you have libmtp installed?

And, yes, as mentioned earlier, libmtp is installed along with jmtpfs, 
and a handful of other relevant mtp pkgs. I did mention that in my first 
post
Thanks,
Tony

-- 
http://www.baldwinlinguas.com
translations, localization,
multilingual web development
EN, ES, FR, PT

---

From: Carl Fink <[email-masked]>
Date: Sun, 4 Sep 2016 23:59:14 -0400

On 09/04/2016 10:52 PM, Anthony Baldwin wrote:
> and a handful of other relevant mtp pkgs. I did mention that in my 
> first post
> Thanks,

You didn't enumerate, you just said you had "relevant" packages installed, IIRC.

How about mount.mtpfs?
-- 
Carl Fink
[email-masked]

---

From: "Neal P. Murphy" <[email-masked]>
Date: Sun, 4 Sep 2016 23:50:52 -0400

On Sun, 4 Sep 2016 22:52:33 -0400

> and a handful of other relevant mtp pkgs. I did mention that in my first 

Oh, wait. (Grasping at a straw...) Do you need pkg usb-modeswitch? There are some USB NADs (Network Access Device) for which udev uses usb-modeswitch to switch from the default mode that presents the Windows drivers in a filesystem to a different mode (such as, on a cellular modem, that allows one to use it somewhat like a modem). Windows handles the switch automatically, but Linux needs usb-modeswitch and udev.

---

From: Nate Bargmann <[email-masked]>
Date: Mon, 5 Sep 2016 08:04:33 -0500

* On 2016 04 Sep 22:53 -0500, Neal P. Murphy wrote:
> Oh, wait. (Grasping at a straw...) Do you need pkg usb-modeswitch?
> There are some USB NADs (Network Access Device) for which udev uses
> usb-modeswitch to switch from the default mode that presents the
> Windows drivers in a filesystem to a different mode (such as, on a
> cellular modem, that allows one to use it somewhat like a
> modem). Windows handles the switch automatically, but Linux needs
> usb-modeswitch and udev.

I've yet to try it myself but I do know that my Motorola XT-901
(Electrify M) Android phone will come up as a removable drive under
windows so that one can download and install the Windows software for
accessing the phone's file system.  Running that software permits
switching the phone into an MTP device.

Likewise, plugging the phone into a Linux desktop causes it to be
connected as a USB mass storage device and nothing else.  At least it
used to as I now use the AirDroid app to access the phone over the LAN
with more functionality than MTP offered, as I recall.

- Nate

-- 

"The optimist proclaims that we live in the best of all
possible worlds.  The pessimist fears this is true."

Ham radio, Linux, bikes, and more: http://www.n0nb.us

---

From: Anthony Baldwin <[email-masked]>
Date: Sun, 4 Sep 2016 22:40:30 -0400

On 09/04/2016 10:01 PM, Dutch Ingraham wrote:
> sudo dmesg -wH

Still seeing tonso this:
[  +0.448021] hub 10-0:1.0: unable to enumerate USB device on port 1
[  +0.448006] hub 10-0:1.0: unable to enumerate USB device on port 1
[  +0.447994] hub 10-0:1.0: unable to enumerate USB device on port 1
[  +0.447932] hub 10-0:1.0: unable to enumerate USB device on port 1

same as in /var/log/syslog

./tony

---

From: Carl Fink <[email-masked]>
Date: Sun, 4 Sep 2016 21:35:45 -0400

> enumerate USB device on port 1

Could be hardware. Have you tried the simplest test of all: plugging the
phone into a different USB port?

Can other computers detect it? 

Is the phone unlocked? My own phone is only detected if I unlock it either
before plugging it in, or after doing so.
-- 
Carl Fink                           [email-masked] 

Read my blog at blog.nitpicking.com.  Reviews!  Observations!
Stupid mistakes you can correct!

---

From: Tony Baldwin <[email-masked]>
Date: Sun, 4 Sep 2016 21:40:13 -0400

> before plugging it in, or after doing so.
I've tried two USB ports, three charger chords, screen locked/unlocked.
rebooting both machines in various combos/orders..
The only thing I haven't done is sacrifice a goat first.
./tony

-- 
http://tonybaldwin.me
all tony, all the time

---

From: "Neal P. Murphy" <[email-masked]>
Date: Sun, 4 Sep 2016 22:13:13 -0400

On Sun, 4 Sep 2016 21:40:13 -0400

> The only thing I haven't done is sacrifice a goat first.

Are you using a USB3.0 port? Is the kernel up-to-date? For a while, Jessie's USB3.0 support was basically broken (as it was in most late-model kernels and is still broken in some); some of the recent kernel updates seems to have fixed it.

---

From: Anthony Baldwin <[email-masked]>
Date: Sun, 4 Sep 2016 22:38:39 -0400

> Are you using a USB3.0 port? Is the kernel up-to-date? For a while, Jessie's USB3.0 support was basically broken (as it was in most late-model kernels and is still broken in some); some of the rece…

I don't know what kind any of these USB ports are ( as far as 3.0 or 
whatever), and everything was updated (update-> safe-upgrade) last week.

./tony

---

From: Lisi Reisz <[email-masked]>
Date: Tue, 13 Sep 2016 16:14:56 +0100

On Monday 05 September 2016 03:38:39 Anthony Baldwin wrote:
> I don't know what kind any of these USB ports are

Have a look at the port and/or the plug.  White or black=USB2 and blue=USB3.  
(We can safely ignore USB1).  I have even come across USB2 not working in a 
USB3 port, even though it should in theory.

Lisi

---

From: Carl Fink <[email-masked]>
Date: Sun, 4 Sep 2016 22:04:09 -0400

> The only thing I haven't done is sacrifice a goat first.

I notice you have *not* tried plugging the phone into a different 
computer. At least, you don't mention doing so.

Can your Debian box detect other Android (I'm assuming) devices?

-- 
Carl Fink
[email-masked]