Asking again: is anyone from Ubuntu looking at this issue at all?
Unfortunately there's rather a complex interplay of subsystems here: It
seems the top end is Nautilus, and the bottom end might be libmtp. In
the middle GVFS, GIO, FUSE and all sorts of stuff might lurk.
If only some expert that kn
mtpfs, go-mtpfs, gmtp, mtp-detect and nautilus (gvfs, or gio, or
whatever) all use the same libmtp library. It seems that the common way
to query MTP devices used to be "pull a list of all objects", "push and
pull individual objects". A lot of old, legacy devices actually seem to
*expect* that kind
Sorry, I meant Canonical people. I forgot that Ubuntu is supposedly a
"community distribution", except when it's not :-p
Where's "upstream"? Is there a bug tracker for the gvfs people anywhere?
Please understand, the reason this is a confusing issue is that it's not
immediately apparent from any s
*sigh* It's what I've come to expect from Ubuntu: remember, Shuttleworth
says it's better to have users than a stable product!
As a workaround, you can set the Galaxy Nexus to use PTP. (Drag down on
the notifications bar, and click the "Connected as media device/Touch
for other USB options" notifi
Which update was that? I'm up to date and it's still broken. The only
updates I got that might be relevant was for glib (and libtasn1), and
neither fixed the issue.
I've tried using Cinnamon, GNOME fallback and Unity, and now it seems
like hit-or-miss that MTP even gets recognized. If that happens
I've tried something different:
http://ohheyitslou.blogspot.com/2011/12/galaxy-nexus-enable-mtp-file-
transfer.html
Precise is up-to-date with the latest stable libmtp. BUT, it seems that
mtpfs pulls down the entire tree from the phone before allowing access
to the FS. If this is because libmtp o
