Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 03 Jan 2013 15:31:41 -0500
From:      Lowell Gilbert <Lgfbsd@be-well.ilk.org>
To:        Hans Petter Selasky <hselasky@c2i.net>
Cc:        freebsd-usb@freebsd.org
Subject:   Re: Android device problems with MTP ID
Message-ID:  <44sj6iqa8i.fsf@lowell-desk.lan>
In-Reply-To: <201301032104.54225.hselasky@c2i.net> (Hans Petter Selasky's message of "Thu, 3 Jan 2013 21:04:54 %2B0100")
References:  <44d2xmrrfp.fsf@lowell-desk.lan> <201301032039.16448.hselasky@c2i.net> <448v8arqco.fsf@lowell-desk.lan> <201301032104.54225.hselasky@c2i.net>

next in thread | previous in thread | raw e-mail | index | archive | help
Hans Petter Selasky <hselasky@c2i.net> writes:

> On Thursday 03 January 2013 20:58:15 Lowell Gilbert wrote:
>> Hans Petter Selasky <hselasky@c2i.net> writes:
>> > On Thursday 03 January 2013 20:34:50 Lowell Gilbert wrote:
>> >> On my (updated to Android 4.1.1) phone, MTP only works if the phone's
>> >> USB debugging option is enabled. If it is, usbconfig(8) sees a ugen(4)
>> >> interface of MTP type; but otherwise it just shows up as a CD device.
>> > 
>> > Try to use cdcontrol to eject the CD.
>> 
>> Thanks! That works! [And I can see the logic behind it, even, from a
>> firmware point of view.]
>> 
>> I should be able to automate the eject command through devd, I think.
>> It would be nice to put something in the tree that would do that, but
>> being sure not to catch cases you'd want such a feature would be
>> error-prone.
>> 
>> I'll move forward on making MTP more convenient on FreeBSD. A lot of
>> devices are starting to force it on us, and it keeps the device usable
>> while the computer is accessing its files.
>> 
>> Thanks again!
>> 
>> Be well.
>>         Lowell
>
> There might be a quirk for that.
>
> See usbconfig, and send a patch for that if you figure it out :-)

This is going to apply to a *lot* of devices, so adding adding all of
the devices individually seems like it would be a losing battle.  If I'm
wrong, or if it's worth doing anyway, I'd certainly be willing to do the
code. There might be a way to tell that this needs to be done from the
usbconfig info, or even from the contents of the ISO, but I don't see
it. Maybe if I look deeper into the USB descriptor encodings I'll find
something. I'd be happy to accept advice.

At the very least, I'll document whatever I do so other people can
imitate it.

Be well.
        Lowell



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44sj6iqa8i.fsf>