Ubuntu does not work with Samsung Galaxy phones (Unable to open raw device 0)

Status changed to 'Confirmed' because the bug affects multiple users.

That isn't true that "Android 4 will not support anymore usb mass-storage protocol" it is up to device maker to provide sdcard slots or "internal sdcard". In that case mass storage will be available.

But more devices do not have sdcard support or sdcard like internal memory. So, those are only accessible using the MTP protocol which needs to be implemented in GVFS to automatically mount in .gvfs users folders.

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

I've created an upstream bug report: https://bugzilla.gnome.org/show_bug.cgi?id=666195

I'm on Ubuntu 11.10, using a Samsung Galaxy Nexus with Android 4/ICS.

What I observe is that connecting the GN in ptp mode behaves almost exactly as it if it was connect as a USB mass storage device, i.e., automount, icon (camera) appearing in the Launcher & Nautilus, possibility to create/move/delete any kind of files/folders, etc. Even with Banshee (and Rhythmbox I presume), if you put an ".is_audio_player" at the root, the GN will me recognized as a Media/Audio player!

Anyway, I guess that if the mtp connection was providing the same kind of access as ptp (by default, GN is set to connect as mtp device), it would be easier for novice users to have their GN phone works with Ubuntu.

The only problem (limit) with ptp so far is that, strangely, it appears to limit the space access to +/-1,5 GB, as there is +/- 13 GB available (free) on the phone...

We'd need to add a udev rule to allow users to access these devices. I figure we don't want to collect a whole lot of vendor/product IDs, is there a way to tell that an USB device is an Android one?

Can you please run

  udevadm info --export-db > /tmp/udev-db.txt

in a terminal and attach /tmp/udev-db.txt here, with the phone connected?

Here are the requested log files, one when the phone is connected in mtp mode, the other in ptp mode.

I don't think (I may be wrong) that there is a magic way to detect all Android devices, as there are so many manufacturers and products... Anyway, most Android phones will continue to rely on USB mass storage, as Android 4/ICS still support this mode when there is an SD card inserted in the phone (which is usually the case). Up to now, Galaxy Nexus is an exception, with very few others so far.

Other file.

I'm using Ubuntu 11.10, with a Samsung Galaxy Nexus with Android 4.0.2

I cannot get USB support to work with either Media Device (MTP) which gives no response at all, or Camera (PTP) which will trigger a camera icon. When clicking "open" on the icon, I get a window with a "Galaxy" title in Nautilus, follwed by a long pause, and the eventual message, "The folder contents cannot be displayed. Sorry, could not display all the contents of "Galaxy": DBus error org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."

Thus, I am forced to use "Airdroid" rather than accessing the device in the normal manner.

Here is a copy of the tmp/udev-db.txt that corresponds to my prior posting.

@traverlaw Did you try to follow the tutorial at "OMG! Ubuntu" which is linked in the bug description?

Andre asked, "@traverlaw Did you try to follow the tutorial at "OMG! Ubuntu" which is linked in the bug description?"

Yes I did try it, several times, in many different versions as found on the web, and it does not work. I also upgraded via compiling to libmtp-1.1.1 and it still did not work. File access to a Galaxy Nexus via Linux should be an easy plug-in-the-phone treat, not requiring hours of searching the web, compiling new packages, editing files, and manually mounting and unmouting. When finally able to get to the files with the new lebmtp, they could be seen, but not accessed. Picutres would not show, music would not play. It was, from the user perspective, a wild goose chase that led to nothing. Android, it appears, is leaving Linux behind, and that is a very bad thing for Linux.

Once again, just to put the story straight: Android 4/ICS is ***still*** supporting USB mass storage (UMS). The only thing is that some devices (such as Galaxy Nexus) have only one partition (i.e. without SD card) and thus, can't rely on UMS since this would lockup the whole system. These devices have to rely on other widely known protocol like mtp and ptp which are usually supported under Linux for years. On this explanation, see: http://www.engadget.com/2011/11/21/ice-cream-sandwich-supports-usb-mass-storage-after-all-galaxy-n/

So basically, the only thing to resolve here IMHO, is to have the Galaxy Nexus well recognized by Ubuntu as a mtp/ptp device (and, if possible, to provide complete file access with these protocols).

I am using Ubunto 10.04 LTS. I followed the instructions in the referenced document. However, when I execute the mtp-detect | grep idVendor or mtp-detect | grep idProduct commands I get no output. It just returns to the cursur.

I have recently bought a Asus Transformer Prime which gives no feedback on my Kubuntu 11.10 laptop when I hook it up in MTP mode. Mass storage does not seem to be one of the options for USB though that might be because I did not have any external memory hooked up when I connected it. Using the instructions a OMG ubuntu I was able to mount the system quite quickly.

I also own a Samsung Galaxy S. Though this still has mass storage support for the built-in memory, I tried hooking it up in MTP mode for a change. Something actually did pop-up and seemed to give some access to the phone. It seems however that I did not have access to all the files as I do seem to have on Windows.

I do hope that this can be included in the next release of (K)Ubuntu because a lot of people will be running into this now. If Ubuntu truly wants to remain a distro for the not-so-technical users things like this should really be picked up early.

@w-troop: you might have to install the package mtp-tools (i.e. execute 'sudo apt-get install mtp-tools' ). Though I would still except some output even if it is not installed. You could try executing just 'mtp-detect' and see if you can find the values yourself.

I'm using Cyanogenmod 9 with my Motorola Droid *with an SD card*, and I still cannot connect via USB. Also there is no option to change to MTP in the notification drawer like OMG! Ubuntu suggests so I cannot even fix it that way ):

@Zaiger:

Currently, under Cyanogenmod 9 (still in early development), USB mass storage works with some devices (http://forum.xda-developers.com/showthread.php?t=1374497), but not (or not so well) for others. It's a Cyanogenmod 9 development issue. Again, ICS is built to supports USB mass storage when the device has more than one partition. For devices that don't, we need good mtp/ptp support under Ubuntu.

libmtp is involved in MTP support because udev rules and protocol implementation are provided by that package, so bundling a recent one is required.
There are a few open Android 4 related bugs in its bug tracker (I can't link to them in this bug's meta because LaunchPad think that the bug tracker is at LaunchPad and refuses to monitor SourceForge ones):
http://sourceforge.net/tracker/?func=detail&aid=3489472&group_id=158745&atid=809061
Some are recently fixed (January):
http://sourceforge.net/tracker/?func=detail&aid=3456722&group_id=158745&atid=809061

When pluging in an MTP device nautilus should show the device content like with any mass storage device, no matter how, this is the behavior poeple are especting.

See this bug about mtpfs crashing in 12.04: https://bugs.launchpad.net/ubuntu/+source/mtpfs/+bug/948615

Just update my galaxy s 2 with ICS and following everystep in here http://www.omgubuntu.co.uk/2011/12/how-to-connect-your-android-ice-cream-sandwich-phone-to-ubuntu-for-file-access/ but no working :(

I'm using ubuntu 11.10 64 bit.

I cannot make this to work either. I have a Galaxy S2 with ICS 4.0.3 and Precise. No luck till so far...

This bug should be fixed by the latest release uploaded to Precise.
Could anyone confirm that?

it works for me now. it automounts in nautilus through gphoto2 mtp backend.

handset is samsung galaxy s2 with latest cyanogenmod 9 ( ICS 4.0.4)

Good! Closing for now.

still on 11.10, can't test if fix works (but looking forward to this in a couple of days time)

for the record; i'm on a samsung galaxy sII with official samsung ICS ROM and although I do have a external sd-card, I don't have the option to mount it as USB mass storage, only choices are between MTP and PTP.

I have a Sony Xperia Neo V which I recently upgraded to ICS and I have upgraded my Kubuntu installation to Precise. If it is true that the problem has been "fixed by the latest release uploaded to Precise" as per comment #24 please tell me from a vanilla installation what packages should I install to enable Precise to read my SD card via MTP protocol. The curious thing is that Ubuntu has always read my MP3 player (also on MTP) without my needed to install any specific packages, so I wonder why I have to install now only?

@jamadagni: I don't know precisely what package is needed, but in my case, I have libmtp9, libmtp-common and libmtp-runtime installed (by default) on my Ubuntu 12.04 machine and I'm able to mount my Galaxy Nexus 4.1 ICS phone. However, when I plug the phone, nothing happens, i.e. no automount; I have to switch phone to ptp mode (or if it is already to ptp switch to mtp), to have the phone mount with one or this mode. Hope this helps.

I've a Galaxy tablet 10.1 and 12.04 does not recognize it!

I have a Samsung Galaxy Note and 12.04 does not recognize it!

Galaxy S2 with ICS

Galaxy Nexus with ICS 4.0.4 . Aparently, everthing works, but when I try to copy music to the phone, or it copies to root folder or gives an error

Nexus-S_4G with Android 4.0.4 can be mounted as easy as it has been with 2.3.x. Vanilla Android seems to work great.

@Jesueldo: You might want to try it with a .is_audio_player file which allows to specify the location of your music files on the device when using software like Rhythmbox or Banshee: http://almost-a-technocrat.blogspot.com/2010/11/isaudioplayer.html

When I tried to use rhythmbox to acess a samsung table 10.1:
"Unable to open the Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note device"

The same problem with Samsung Galaxy SII...

The best would be to be able to access it using Nautilus since it is not only photos and music, there are videos, ebooks and any other type of file that we may want to transfer between the devices!

Importance: Wishlist ?! WHY??
That is BAD! You are downgrading something that millions of user would like to integrate, linux with any android device in an EASY way! Please!

I cannot connect my stock Galaxy SII (ICS). Nothing happens. gMTP doesn't work either.

How can this be fixed if people are still experiencing issues?

Precise with latest updates.

No way is it fixed for me, Galaxy S2 with official ICS, Ubuntu 12.04 updated. Neither MTP or camera or debug modes. In MTP, it does automount in nautilus and shows the files and folders on the root of the phone, but all folders say 0 items inside them, and going into any folder shows no files or folders inside (when I know there are).

Uploading a file to the root or inside a folder shows as if its transferring, completes, but doesn't actually go on the phone's storage.

Same is true for me: Galaxy SIII, Ubuntu 12.04. When i plug in the phone, two nautilus windows (vie gphoto2) open for the internal and the external sd-card. In MTP mode i get the content and even may read files from the external sd, but only in the root-folder. Aall other folders i may browse, but they appear empty.

I may also create a file, that somehow may be changed on the card. When i plug of and on, the file can`t be read anymore, just be deleted.

I have a Samsung Galaxy Tab 10.1 and despite a fully up to date Precise system, MTP support is not working.

AfC

Mio,

USB3 would be a kernel bug. You should look for unhappy messages in dmesg output.

Moving files: There are two answers to this one. It is physically possible to implement a "fake" file move in the backend, although if that's the path you want to go down it should be done in gvfs core code and not in each backend (the ptp backend has this fake move logic in it, but no one else can use it). But the most robust implementation would be in nautilus, because then it would understand what's really going on and could keep track of the file as it moves around the system and minimize the chance of data loss. It would also be able to give feedback to the user that two copy operations are taking place.

As described in bug #696301 the problem still exists in precise.
I also tested it with backported version from raring for libmtp (1.1.5) and mtpfs (1.1.2)
( --> https://launchpad.net/~dirk-computer42/+archive/c42-edge )

$ mtp-detect
Error: Unable to open ~/.mtpz-data for reading.
libmtp version: 1.1.5

Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
   Found 1 device(s):
   Samsung: Galaxy models (MTP) (04e8:6860) @ bus 1, dev 5
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.

Problem is not resolved with the most current libmtp 1.1.5 (see http://sourceforge.net/projects/libmtp/files/libmtp/)

Dirk, As discussed above, mtpfs will never work with an Android 4.x device due to how it uses libmtp. No updates to libmtp will ever change that.

As for your mtp-detect error, that's likely due to another application already talking MTP to the device (eg: if you'd attempted to mount with mtpfs, or if gvfs ptp was trying to communicate with it - which will happen automatically if you have a default Unity desktop, or if gvfs mtp is communicating with it, if you're using my version of gvfs). The MTP protocol only supports one application communicating with the device at a time, so if another one tries to do connection initialization, the device gets confused and can respond in fairly unpredictable ways.

Philip, thanks for all your work on this. With your PPA nautilus sees my i9300 allright but upon mounting it I only managed once to actually see any contents. In all other cases there was no visual error and the device appeared mounted, but there was just no content and I could not create anything as well.

Is there any way to debug this?

I also noticed that even though your solution is using gvfs, it is limited to nautilus, ie. other gvfs aware file managers such as thunar can't be used. I know this is exactly as announced by yoursefl, but our of curiosity: is this something to be fixable on your end or is it a limitation on those other file managers part?

2 working workaround solutions:

- jmtpfs: http://research.jacquette.com/jmtpfs-exchanging-files-between-android-devices-and-linux/
- go-mtpfs: http://www.webupd8.org/2012/12/how-to-mount-android-40-ubuntu-go-mtpfs.html

Marius,

Are you making sure the phone is unlocked when you plug it in? If the phone is locked, then you'll see an empty nautilus window. Once you unlock it, press F5 to refresh the window (My quantal builds are against libmtp 1.1.4 which has no event notification support - if built and run against 1.1.5, it will auto refresh when you unlock), and you should see some content.

As for Thunar, I'm slightly surprised it doesn't work. I haven't tried it so I have no idea what it does but my work should be transparent to anything that uses gvfs 'normally'. It's possible that Thunar handles some of the backend registration differently from Nautilus and may need explicit code changes to know that the mtp backend is available.

There are ONE POINT THREE million devices activated each day that are not "plug and play" with Ubuntu!

I have been frustrated with the lack of Android 4+ (MTP) plug and play for some time and I have tried gmtp and go-mtpfs but none have been stable. I handle my family's 7 android devices and the proposed workarounds works now and then for some of the devices. Last time that I needed to offload 9 GB of pictures from a Galaxy SII phone I had to revert to a virtual Windows 7:(

I propose to make MTP "Plug & Play" in Ubuntu, current LTS and future releases.

@Mio, H.-Dirk Schmitt

Please test the latest version of libmtp and gvfs from Philips PPA.

https://launchpad.net/~langdalepl/+archive/gvfs-mtp

It runs fine with my Nexus7 and Samsung Galaxy S3. It supports the basic functions:

- mount
- file transfer
- make new dir
- rename dir (press F5 after rename)

I've been watching the thread for a while now as I still can't find a solution to get any files to/from my mobile devices (HTC One X and Acer A500) but by using ssh (either installing ssd on mobile devices or connection to my laptop/desktop). Both my laptop and desktop are running Ubuntu, usually the last stable one, so now it is Quantal.

First of all I would like to thank the ones working on the solution to this problem as it is a shame that Ubuntu does not support the andriod devices out of box (I've tried to use them since Oneiric with no success).

I've tried the gcfs-mtp solution mentioned above almost with out success. It allowed me to browse folders and open PDF files (only !) on my devices, but I could neither copy or move any files nor open image files.

Now I've udated to the newer version and got even worse results: I still can open a pdf in the root folder of my HTC, but when I try to enter the DCIM folder nautilus closes with "Connection closed" error (I see a localized message in hungarian but if it is important I can check the message the original message). Also I've got
 pool[26210] general protection ip:7f95b802a69c sp:7f95aeffcc28 error:0 in libgobject-2.0.so.0.3400.1[7f95b7ff9000+4d000]
error in my kern.log.

When using my Acer A500 the same thing happens if I try to open the root folder of the device...

Can I do anything to help solving these problems? SHould I post any logs or try anything?

> but when I try to enter the DCIM folder nautilus closes with "Connection closed" error

I got this message often with the old version of gvfs and libmtp. Have done a restart after updating?

I'm using a Galaxy Tab2 7.0 and have had similar problems. I cannot access the device at all using any of the known mtp tools (mtpfs, go-mtpfs, or jmptfs). I supposed that maybe upgrading to libmtp-1.1.5 will help.

I downloaded the libmtp-1.1.5 tarball, dropped in the debian/ directory from the previous version's deb src, changed debian/changelog and built a new deb containing the various packages for version 1.1.5.

mtp-detect succeeds. go-mtpfs and jmptfs work. Sometimes "fusermount -u foobar" will fail because the system thinks I'm still doing something in foobar. Regular mtpfs works unacceptably. It seems that it does a union mount of the internal sdcard on top of the external sdcard and sets all the permissions to 777.

I hope this helps.

broken on xoom.

gvfs changes are now merged upstream.

For the record, support for a proper MTP backend just landed in upstream gvfs. Once raring gets glib 2.35.x, we can package this.

Worked for me http://www.webupd8.org/2012/12/how-to-mount-android-40-ubuntu-go-mtpfs.html

@Mio, H.-Dirk Schmitt

Please test the latest version of libmtp and gvfs from Philips PPA.

https://launchpad.net/~langdalepl/+archive/gvfs-mtp

Also on my Galaxy S3 and Nexus 7 these (Natty packages) work great!

I would really suggest to get these packages to Natty-backports since the amount of Android devices using MTP in this world is enormous. The current user experience is horrible and hard to explain (like: yes Android is linux-based but it doesn't work with your Ubuntu linux... :-S) while with these new packages the user experience is great (just plug it in, file-manager opens, and there are nice icons for Internal Storage and SD storage).

Every day more and more Android devices are sold, most of them by now having Android OS 4.x+ and only MTP...

@Myself #149, dumb me. Not Natty, but Quantal packages... :P don't know what I was thinking...

Works flawlessly with Samsung Galaxy Nexus GSM, even with (sometimes flawed) Nautilus file copying. Thanks for the much needed fix and the PPA!

Works fine without noticeable issues with Galaxy SIII. Will test with a
couple of my Android development tablets (Galaxy Tab, Lepan, etc.) and
report back.

Great work getting this one wrestled down and fixed. Be nice to have
the Ubuntu maintainers push this out to the rest of the world, as 90% of
the people using Ubuntu never put enough effort in to find out how to
fix things.

Agreed, this needs to be backported, otherwise we are losing users :)

This bug was fixed in the package gvfs - 1.15.2-0ubuntu1

---------------
gvfs (1.15.2-0ubuntu1) raring; urgency=low

  * debian/watch: Look for development releases, too.
  * New upstream release:
    - Add new MTP backend. In particular this can access Android 4.0 devices
      which do not support the USB Mass Storage interface any more.
      (LP: #903422)
    - See NEWS for other changes.
  * Bump build depends and add libmtp-dev according to upstream configure.ac.
  * debian/gvfs-backends.install: Install new MTP monitor.
  * Drop debian/tests/gvfs-test, it has been accepted upstream. Update
    debian/tests/integration to use tests/gvfs-test instead.
  * Add 00git_fix_archivemounter_tests.patch: Fix ArchiveMounter tests.
 -- Martin Pitt <email address hidden> Fri, 18 Jan 2013 12:42:41 +0100

The langedalepl ppa is not helpful on Quantal. No joy. Galaxy Nexus
won't let me see pix or mount device with mtp or ptp chosen on the phone.

The langedalepl ppa works well for me. No issues so far.
I've got Quantal with a Galaxy Nexus.

Unfortunately the langedalepl ppa does not work for me on Xubuntu 12.10 (I did reboot). Phone is a Motorola XT890 running ICS. I've tried multiple USB ports, unlocking the phone's screen and switching between MTP and PTP. Further things to try would be welcome.

$ mtp-detect
Error: Unable to open ~/.mtpz-data for reading.
libmtp version: 1.1.5

Listing raw device(s)
   No raw devices found.
$ lsusb
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 003: ID 06a3:8021 Saitek PLC Eclipse II Keyboard
Bus 002 Device 004: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
Bus 002 Device 005: ID 0424:2514 Standard Microsystems Corp. USB 2.0 Hub
Bus 002 Device 018: ID 22b8:710f Motorola PCS
Bus 002 Device 007: ID 0cf3:3005 Atheros Communications, Inc. AR3011 Bluetooth
$ cat /etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", MODE="0666"
SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", MODE="0666"

It is now well over a month since this bug has been marked as fixed. Is this ever going into precise and/or quantal, or will this version of gvfs only be available from raring onwards?

Well, if it's going to happen, an SRU has to be filled out, and it will
have to meet the criteria for that. Now, whether this qualifies or not, I'm
not sure, but I'm sure something useful will be on the Ubuntu wiki about
that.

Sincerely,
kroq-gar78
On Feb 26, 2013 1:05 PM, "Stefan Brozinski" <email address hidden>
wrote:

> It is now well over a month since this bug has been marked as fixed. Is
> this ever going into precise and/or quantal, or will this version of
> gvfs only be available from raring onwards?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/903422
>
> Title:
> Ubuntu does not work with Samsung Galaxy phones ( Unable to open raw
> device 0)
>
> Status in GVFS:
> Fix Released
> Status in “gmtp” package in Ubuntu:
> Invalid
> Status in “gvfs” package in Ubuntu:
> Fix Released
> Status in “udev” package in Ubuntu:
> Invalid
> Status in “gmtp” source package in Precise:
> Invalid
> Status in “gvfs” source package in Precise:
> Confirmed
> Status in “udev” source package in Precise:
> Invalid
> Status in “gmtp” source package in Quantal:
> Invalid
> Status in “gvfs” source package in Quantal:
> Confirmed
> Status in “udev” source package in Quantal:
> Invalid
>
> Bug description:
> If your device is not supported please open a new bug specifying:
> * device in question (make / model / release)
> * output of `mtp-detect` when the device is attached
> * output of `lsusb` when the device is attached
>
> This bug will be a catch all for recent Samsung Nexus & Nexus 7, or
> please comment what other recent Andorid 4.x devices are affected.
>
> Yes there is a lag in providing support for the most recent devices.
> As soon as the fixes are available, SRUs will follow.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/gvfs/+bug/903422/+subscriptions
>

Stefan Brozinski [2013-02-26 18:57 -0000]:
> It is now well over a month since this bug has been marked as fixed. Is
> this ever going into precise and/or quantal, or will this version of
> gvfs only be available from raring onwards?

My gut feeling is "Raring onwards", as it's quite an intrusive change
which by far doesn't meet the usual SRU criteria.

Dave,

Unfortunately, these newer Motorola devices appear as... wait for it... a CDROM drive.

The CD image contains the installer for some windows software that they want you to run, which will send a magic USB packet to the phone to switch it into MTP mode. That's really what's going on. I haven't found any useful information about this online, so it doesn't appear anyone's reverse engineered the magic packet. Sad sad sad.

Philip Langdale [2013-03-06 4:57 -0000]:
> Unfortunately, these newer Motorola devices appear as... wait for it...
> a CDROM drive.

That's quite common indeed; there is usb-modeswitch to get devices
from this useless fake CD-ROM to "real" UMS/MTP mode, so perhaps
usb-modeswitch-data needs to be updated for your model? It might help
to file a bug against usb-modeswitch-data, anyway.

I encounter this bug also with my Intel Orange phone with Android 4.0 and Ubuntu 12.04
(Device 0 (VID=8087 and PID=09fc))

This is a very BIG regression, because it used to work normaly (at fast speed) on my computer since last week where I have let ubuntu proceed to updates.

connecting and browsing with nautilus is fine with my HTC. Copy Camera-Pictures to Linux works fine too.
But now copied files onto that phone from a WinXP and when wanting to copy those files towards Linux I get the error:

"Error getting file: -6: Not Supported"

The file size is 368MB

output of mtp-detect:

libmtp version: 1.1.3

Listing raw device(s)
Device 0 (VID=0bb4 and PID=0df9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
   Found 1 device(s):
   0bb4:0df9 @ bus 2, dev 16
Attempting to connect device(s)
ignoring usb_claim_interface = -6ignoring usb_claim_interface = -5PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.

and lsusb:

lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 0a5c:2110 Broadcom Corp. Bluetooth Controller
Bus 003 Device 003: ID 0483:2016 SGS Thomson Microelectronics Fingerprint Reader
Bus 002 Device 016: ID 0bb4:0df9 High Tech Computer Corp.

actually it now works for me when adding this ppa:

sudo add-apt-repository ppa:langdalepl/gvfs-mtp
sudo apt-get update

apply all updates and restart computer. found the info here: http://www.webupd8.org/2013/01/upgrade-to-gvfs-with-mtp-support-in.html

With Ringtail-13.04 I can access Android 4.2.2 data on my Galaxy Nexus .
Does not show up like a USB device on my desktop but File Manager shows it
and can mount/unmount and copy data to it.
A big advantage for 13.04 over 12.10. Thanks to all the folks who made this work again.

I've been too lazy to try go-mtpfs, up until now.
It just works flawlessly with Galaxy Nexus / Android 4.2.2, unlike libmtp and its ecosystem (gmtp, rhythmbox, nautilus).

There was recently a change to the adb tool. It now does authentication; the user is prompted to "allow" a new computer when the phone is connected to it. The old adb is not compatible.

This change is probably why it fails, even though MTP on the Samsung Galaxy Nexus previously worked.

I used the new adb (with the authentication) to manually push files. That worked fine. Trying the other forum posts (like changing the udev rules) did not work for me.

It was very aggravating to get the cool new phone (Nexus 4) and then not be able to transfer files to it.

(This comment reposted from duplicate bug 1092621.)

Nexus S
Android 4.1.2
Build JZO54K

Ubuntu 13.04

Error:
     Unable to Mount Nexus S
     Unable to open MTP device '[usb:001,005]'

$ gmtp
Device 0 (VID=18d1 and PID=4e21) is a Google Inc (for Samsung) Nexus S.
LIBMTP PANIC: Unable to find interface & endpoints of device
Detect: Unable to open raw device?
LIBMTP PANIC: Trying to dump the error stack of a NULL device!
LIBMTP PANIC: Trying to clear the error stack of a NULL device!

$ mtp-detect
Unable to open ~/.mtpz-data for reading, MTPZ disabled.libmtp version: 1.1.5

Listing raw device(s)
Device 0 (VID=18d1 and PID=4e21) is a Google Inc (for Samsung) Nexus S.
   Found 1 device(s):
   Google Inc (for Samsung): Nexus S (18d1:4e21) @ bus 1, dev 5
Attempting to connect device(s)
LIBMTP PANIC: Unable to find interface & endpoints of device
Unable to open raw device 0
OK.

$ lsusb -vs 001:006
Bus 001 Device 006: ID 18d1:4e21 Google Inc. Nexus S
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x18d1 Google Inc.
  idProduct 0x4e21 Nexus S
  bcdDevice 2.31
  iManufacturer 2 samsung
  iProduct 3 Nexus S
  iSerial 4 37351D????????
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 32
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0x80
      (Bus Powered)
    MaxPower 500mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 8 Mass Storage
      bInterfaceSubClass 6 SCSI
      bInterfaceProtocol 80 Bulk-Only
      iInterface 1 Mass Storage
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x01 EP 1 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 1
Device Qualifier (for other device speed):
  bLength 10
  bDescriptorType 6
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  bNumConfigurations 1
Device Status: 0x0001
  Self Powered

quantal has seen the end of its life and is no longer receiving any updates. Marking the quantal task for this ticket as "Won't Fix".

Seems like this bug still occurs on:

`
patben@patben-amd:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
patben@patben-amd:~$ mtp-detect
libmtp version: 1.1.13

Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
   Found 1 device(s):
   Samsung: Galaxy models (MTP) (04e8:6860) @ bus 5, dev 6
Attempting to connect device(s)
ignoring libusb_claim_interface() = -6PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
patben@patben-amd:~$ lsusb
Bus 006 Device 002: ID 0424:5734 Standard Microsystems Corp.
Bus 006 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 005 Device 003: ID 04b3:3025 IBM Corp. NetVista Full Width Keyboard
Bus 005 Device 004: ID 0424:274c Standard Microsystems Corp.
Bus 005 Device 006: ID 04e8:6860 Samsung Electronics Co., Ltd Galaxy (MTP)
Bus 005 Device 002: ID 0424:2734 Standard Microsystems Corp.
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 05e3:0723 Genesys Logic, Inc. GL827L SD/MMC/MS Flash Card Reader
Bus 001 Device 003: ID 2516:0051
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
`

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release