Re: mount MTP phone

[Lisi Reisz]

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

Re: mount MTP phone

[Joe Pfeiffer]

Ivan Petrov  writes:

> 06.09.2016 22:19, Joe Pfeiffer пишет:
>> Curt Howland  writes:
>>
>>> I've never been able to mount any MTP phone to Linux. Different
>>> phones, different Android versions, different Linux installations,
>>> nada.
>>
>> I've only been able to do it using jmtpfs (I don't have it set up to
>> automount using that).
>>
>
> Why I have this messages, when I'm using it?
>
> $ jmtpfs /media/exfat
> Device 0 (VID=19d2 and PID=ffce) is UNKNOWN.
> Please report this VID/PID and the device model to the libmtp
> development team
> Android device detected, assigning default bug flags

First question:  when you plugged the phone in, did you turn on USB for
file transfers?  Without that I get almost exactly the same behavior you
see:

snowball:501$ jmtpfs /home/joseph/mnt
Device 0 (VID=18d1 and PID=4ee1) is a Google Inc (for LG Electronics/Samsung) 
Nexus 4/5/7/10 (MTP).
Android device detected, assigning default bug flags
snowball:502$ ls mnt
/bin/ls: cannot access 'mnt': Input/output error

If I click the notification on my phone and then select "File transfers"
I get

snowball:507$ jmtpfs /home/joseph/mnt
Device 0 (VID=18d1 and PID=4ee1) is a Google Inc (for LG Electronics/Samsung) 
Nexus 4/5/7/10 (MTP).
Android device detected, assigning default bug flags
snowball:508$ ls mnt
Internal storage/

which is of course what I want.

I'm not sure whether the actual error message you're getting

> Device 0 (VID=19d2 and PID=ffce) is UNKNOWN.
> Please report this VID/PID and the device model to the libmtp
> development team

is relevant; that's telling you that the vendor ID and product ID your
phone is using to identify itself aren't in libmtp's database.  If I
search for them at http://www.the-sz.com/ it tells me the vendor is ZTE
(which looking at the table appears to be a chipset manufacturer, not
the manufacturer of your phone) but it can't find your device.  On the
other hand, jmtpfs is seeing that your device is an Android device, so
it seems to have gotten around that somehow.

Re: mount MTP phone

[Ivan Petrov]

06.09.2016 22:19, Joe Pfeiffer пишет:

Curt Howland  writes:


I've never been able to mount any MTP phone to Linux. Different
phones, different Android versions, different Linux installations,
nada.


I've only been able to do it using jmtpfs (I don't have it set up to
automount using that).



Why I have this messages, when I'm using it?

$ jmtpfs /media/exfat
Device 0 (VID=19d2 and PID=ffce) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp 
development team

Android device detected, assigning default bug flags


?

Re: mount MTP phone

[Frédéric Marchal]

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

Re: mount MTP phone

[Joe Pfeiffer]

Tony Baldwin  writes:

> On 09/04/2016 09:22 PM, Carl Fink wrote:
>> 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.
>>> 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
>> 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

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

Re: mount MTP phone

[Joe Pfeiffer]

Curt Howland  writes:

> I've never been able to mount any MTP phone to Linux. Different 
> phones, different Android versions, different Linux installations, 
> nada.

I've only been able to do it using jmtpfs (I don't have it set up to
automount using that).
-- 
"Erwin, have you seen the cat?" -- Mrs. Shrödinger

Re: mount MTP phone

[Celejar]

On Mon, 5 Sep 2016 17:09:38 +0200
Nicolas George  wrote:

> Le decadi 20 fructidor, an CCXXIV, Curt Howland a écrit :
> > I've never been able to mount any MTP phone to Linux. Different 
> > phones, different Android versions, different Linux installations, 
> > nada.
> 
> I have. With FUSE and gvfs, something like (the computer where I did it and
> kept notes is current shut down):
> 
> gvfs-mount 'mtp://[usb:001,002]'
> 
> You need to have gvfs-fuse already running, then it appears under
> /run/users/$UID/gvfs/.
> 
> libmtp has a few tools to manipulate MTP devices without mounting them, but
> they have 0 documentation. Furthermore, MTP it awfully slow at startup for
> some tasks, so individual commands without a process to keep the library
> open will give awful results. I have started working on a tool with a
> script-friendly FTP-like interface, but not got very far yet due to other
> more pressing projects.

My Android Moto G and E both mount fine with jmtpfs:

~$ jmtpfs ~/mnt

Basic copying and moving files (that's all I have tried) then works
fine.

Umounting works fine with:

~$ fusermount -u ~/mnt

Celejar

Re: mount MTP phone

[Nicolas George]

Le decadi 20 fructidor, an CCXXIV, Tony Baldwin a écrit :
> Something has changed since yesterday (IN which I installeed jmtpfs).
> Now when I do ls usb, I see this:
> Bus 005 Device 012: ID 22b8:2ea4 Motorola PCS
> I'm also seeing possibly relevant (I don't know) stuff in dmesg, such as
> this:
> [quote][75390.506984] hub 5-0:1.0: port 5 disabled by hub (EMI?),
> re-enabling...
> [75390.507000] usb 5-5: USB disconnect, device number 8
> [75406.588441] usb 5-5: new high-speed USB device number 9 using ehci_hcd
> [75406.722345] usb 5-5: New USB device found, idVendor=22b8, idProduct=2ea6
> [75406.722360] usb 5-5: New USB device strings: Mfr=1, Product=2,
> SerialNumber=3
> [75406.722368] usb 5-5: Product: XT1254
> [75406.722374] usb 5-5: Manufacturer: motorola
> [75406.722379] usb 5-5: SerialNumber: ZY2234TGKZ

This is rather promising.

> [81479.602219] usb 5-5: USB disconnect, device number 9
> [81479.876441] usb 5-5: new high-speed USB device number 10 using ehci_hcd

> [81483.946880] usb 5-5: USB disconnect, device number 10
> [81484.220444] usb 5-5: new high-speed USB device number 11 using ehci_hcd

This is less promising: disconnect and then immediate reconnect. Could be a
faulty contact in the cable.

> [81484.399977] usb 5-5: USB disconnect, device number 11
> [81508.968204] usb 5-5: new high-speed USB device number 12 using ehci_hcd

This one was longer. Maybe you remember if you did something with the phone
at the time. /var/log/kernel.log or `journalctl -kb` would have readable
timestamps.

I would also suggest dmesg -w to see the messages in realtime.

> is your work in a github repo, sourceforge project, or similar, where others
> could have a look, and, perhaps, contribute, Nicolas?

It is way too early for that: no doc, no build system. I just added a quick
comment with a copyright notice and the build command and uploaded to my web
page (so 1990's!):

http://nsup.org/~george/comp/misc/mtpop.c

I can make no promise about a timeline, or even reacting to contributions,
except it will be long (fixing libavfilter has uttermost priority for me
right now). But this is the only place I have publicly spoken of it, so if
someone wants to completely take over, just reply to this mail and everybody
will be informed.

Regards,

-- 
  Nicolas George

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature

Re: mount MTP phone

[Tony Baldwin]

On 09/05/2016 11:09 AM, Nicolas George wrote:

Le decadi 20 fructidor, an CCXXIV, Curt Howland a écrit :

I've never been able to mount any MTP phone to Linux. Different
phones, different Android versions, different Linux installations,
nada.


I have. With FUSE and gvfs, something like (the computer where I did it and
kept notes is current shut down):

gvfs-mount 'mtp://[usb:001,002]'

You need to have gvfs-fuse already running, then it appears under
/run/users/$UID/gvfs/.

libmtp has a few tools to manipulate MTP devices without mounting them, but
they have 0 documentation. Furthermore, MTP it awfully slow at startup for
some tasks, so individual commands without a process to keep the library
open will give awful results. I have started working on a tool with a
script-friendly FTP-like interface, but not got very far yet due to other
more pressing projects.

Regards,



Something has changed since yesterday (IN which I installeed jmtpfs).
Now when I do ls usb, I see this:
Bus 005 Device 012: ID 22b8:2ea4 Motorola PCS
I'm also seeing possibly relevant (I don't know) stuff in dmesg, such as 
this:
[quote][75390.506984] hub 5-0:1.0: port 5 disabled by hub (EMI?), 
re-enabling...

[75390.507000] usb 5-5: USB disconnect, device number 8
[75406.588441] usb 5-5: new high-speed USB device number 9 using ehci_hcd
[75406.722345] usb 5-5: New USB device found, idVendor=22b8, idProduct=2ea6
[75406.722360] usb 5-5: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3

[75406.722368] usb 5-5: Product: XT1254
[75406.722374] usb 5-5: Manufacturer: motorola
[75406.722379] usb 5-5: SerialNumber: ZY2234TGKZ
[81479.602219] usb 5-5: USB disconnect, device number 9
[81479.876441] usb 5-5: new high-speed USB device number 10 using ehci_hcd
[81480.010291] usb 5-5: New USB device found, idVendor=22b8, idProduct=2ea6
[81480.010305] usb 5-5: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3

[81480.010314] usb 5-5: Product: XT1254
[81480.010319] usb 5-5: Manufacturer: motorola
[81480.010325] usb 5-5: SerialNumber: ZY2234TGKZ
[81483.946880] usb 5-5: USB disconnect, device number 10
[81484.220444] usb 5-5: new high-speed USB device number 11 using ehci_hcd
[81484.354763] usb 5-5: New USB device found, idVendor=22b8, idProduct=2ea6
[81484.354778] usb 5-5: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3

[81484.354786] usb 5-5: Product: XT1254
[81484.354792] usb 5-5: Manufacturer: motorola
[81484.354797] usb 5-5: SerialNumber: ZY2234TGKZ
[81484.399977] usb 5-5: USB disconnect, device number 11
[81508.968204] usb 5-5: new high-speed USB device number 12 using ehci_hcd
[81509.102613] usb 5-5: New USB device found, idVendor=22b8, idProduct=2ea4
[81509.102627] usb 5-5: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3

[81509.102635] usb 5-5: Product: XT1254
[81509.102641] usb 5-5: Manufacturer: motorola
[81509.102647] usb 5-5: SerialNumber: ZY2234TGKZ
[/quote]


is your work in a github repo, sourceforge project, or similar, where 
others could have a look, and, perhaps, contribute, Nicolas?


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

Re: mount MTP phone

[Nicolas George]

Le decadi 20 fructidor, an CCXXIV, Curt Howland a écrit :
> I've never been able to mount any MTP phone to Linux. Different 
> phones, different Android versions, different Linux installations, 
> nada.

I have. With FUSE and gvfs, something like (the computer where I did it and
kept notes is current shut down):

gvfs-mount 'mtp://[usb:001,002]'

You need to have gvfs-fuse already running, then it appears under
/run/users/$UID/gvfs/.

libmtp has a few tools to manipulate MTP devices without mounting them, but
they have 0 documentation. Furthermore, MTP it awfully slow at startup for
some tasks, so individual commands without a process to keep the library
open will give awful results. I have started working on a tool with a
script-friendly FTP-like interface, but not got very far yet due to other
more pressing projects.

Regards,

-- 
  Nicolas George


signature.asc
Description: Digital signature

Re: mount MTP phone

[Curt Howland]

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256


I've never been able to mount any MTP phone to Linux. Different 
phones, different Android versions, different Linux installations, 
nada.


- -- 
You may my glories and my state dispose,
But not my griefs; still am I king of those.
 --- William Shakespeare, "Richard II"

-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iF4EAREIAAYFAlfNhdkACgkQtk9X6NaR4amjowEAxDqk/armeNDM4p/bu+x75eG7
ErHTs5wRK2oF3T0Ne+QBAOkZh46FTak4Y+b4SW6q5JnGBzNBGbQTOFKo+rJDwKEr
=WSpF
-END PGP SIGNATURE-

Re: mount MTP phone

[Nate Bargmann]

* 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

Re: mount MTP phone

[Tony Baldwin]

On 09/05/2016 06:50 AM, Dan Purgert wrote:

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.
[snip]
I don't know what else to do to try and diagnose or resolve the matter.
Anyone?


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.



Mine is definitely set to connect as an MTP device.

Thanks,
Tony

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

Re: mount MTP phone

[Dan Purgert]

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.
> [snip]
> I don't know what else to do to try and diagnose or resolve the matter.
> Anyone?

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| 

Re: mount MTP phone

[Carl Fink]

On 09/04/2016 10:52 PM, Anthony Baldwin wrote:
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,


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

How about mount.mtpfs?
--
Carl Fink
c...@finknetwork.com

Re: mount MTP phone

[Neal P. Murphy]

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

> On 09/04/2016 10:01 PM, Dutch Ingraham wrote:
> > On Sun, Sep 04, 2016 at 09:30:38PM -0400, Tony Baldwin wrote:
> >> On 09/04/2016 09:22 PM, Carl Fink wrote:
> >>> 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.
>  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
> >>> 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
> >
> > What do you get with dmesg?  For example, run , then plug 
> > the
> > device in.  What is the complete output?
> >
> > 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

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.

Re: mount MTP phone

[Anthony Baldwin]

On 09/04/2016 10:01 PM, Dutch Ingraham wrote:

On Sun, Sep 04, 2016 at 09:30:38PM -0400, Tony Baldwin wrote:

On 09/04/2016 09:22 PM, Carl Fink wrote:

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.
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

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


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

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

Re: mount MTP phone

[Anthony Baldwin]

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

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

Re: mount MTP phone

[Anthony Baldwin]

On 09/04/2016 10:13 PM, Neal P. Murphy wrote:

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


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



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.



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

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

Re: mount MTP phone

[Neal P. Murphy]

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

> 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
> 

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.

Re: mount MTP phone

[Carl Fink]

On 09/04/2016 09:40 PM, Tony Baldwin wrote:

On 09/04/2016 09:35 PM, Carl Fink wrote:

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.


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


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
c...@finknetwork.com

Re: mount MTP phone

[Dutch Ingraham]

On Sun, Sep 04, 2016 at 09:30:38PM -0400, Tony Baldwin wrote:
> On 09/04/2016 09:22 PM, Carl Fink wrote:
> > 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.
> > > 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
> > 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

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

Also, do you have libmtp installed?

Re: mount MTP phone

[Tony Baldwin]

On 09/04/2016 09:35 PM, Carl Fink wrote:

On Sun, Sep 04, 2016 at 09:30:38PM -0400, Tony Baldwin wrote:

On 09/04/2016 09:22 PM, Carl Fink wrote:

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.
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

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


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.


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

Re: mount MTP phone

[Carl Fink]

On Sun, Sep 04, 2016 at 09:30:38PM -0400, Tony Baldwin wrote:
> On 09/04/2016 09:22 PM, Carl Fink wrote:
> > 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.
> > > 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
> > 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

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   nitpick...@nitpicking.com 

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

Re: mount MTP phone

[Tony Baldwin]

On 09/04/2016 09:22 PM, Carl Fink wrote:

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.

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

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

Re: mount MTP phone

[Carl Fink]

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.

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

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

--
Carl Fink
c...@finknetwork.com