Ubuntu

Samsung Galaxy S / S2 / S3 detected but cannot be connected to

Reported by David Nielsen on 2011-01-01
76
This bug affects 14 people
Affects Status Importance Assigned to Milestone
Banshee
Invalid
Undecided
Unassigned
libmtp
Unknown
Unknown
libmtp (Ubuntu)
Undecided
Unassigned

Bug Description

On x86_64 Natty when I plug in my Samsung Galaxy S it is detected by both USB and by libmtp, but it doesn't show up in Banshee or Nautilus.

running mtp-detect I get:

libmtp version: 1.0.3

Listing raw device(s)
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
   Found 1 device(s):
   Samsung: Galaxy S GT-I9000 (04e8:6877) @ bus 1, dev 9
Attempting to connect device(s)
ignoring usb_claim_interface = -110PTP_ERROR_IO: Trying again after re-initializing USB interface
inep: usb_get_endpoint_status(): Connection timed out
outep: usb_get_endpoint_status(): Connection timed out
usb_clear_halt() on IN endpoint: Connection timed out
usb_clear_halt() on OUT endpoint: Connection timed out
usb_clear_halt() on INTERRUPT endpoint: Connection timed out
LIBMTP PANIC: Could not open session! (Return code 767)
  Try to reset the device.
Unable to open raw device 0
OK.

I have tried rebooting both the machine and the device but the connection never seem able to be established.

It seems like this would be fixed with an update to the just released libmtp 1.0.4

I compiled the latest libmtp from git and now the device shows up in Nautilus but mtp-detect still gives errors.

david@sagan:~/Projekter/libmtp$ mtp-detect
libmtp version: 1.0.4

Listing raw device(s)
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
   Found 1 device(s):
   Samsung: Vibrant SGH-T959 (04e8:68a9) @ bus 1, dev 8
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.

The device should be a Samsung Galaxy S GT-I9000 but now it is detected as a different model.. odd

same problem with the builds in Natty

Changed in banshee:
importance: Unknown → Medium
status: Unknown → Confirmed
Chow Loong Jin (hyperair) wrote :

One of those bugs should be marked a duplicate of the other, I guess.

Alessio Treglia (quadrispro) wrote :

Please, could you try to reproduce this with the latest release of libmtp on Natty?

Changed in libmtp (Ubuntu):
status: New → Incomplete

On Ocelot (same libmtp):

Banshee:
[1 Warn 00:40:56.444] Failed to load media-player-info file for 1
[1 Warn 00:40:56.469] Failed to load media-player-info file for 1
[1 Debug 00:40:56.919] U1MS: Url Loaded: - http://stores.7digital.com/default.aspx?shop=436&partner=983
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
[1 Warn 00:40:58.695] Failed to load media-player-info file for 1
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
[12 Debug 00:41:17.463] Failed to connect to mtp device. Trying 4 more times...
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
[12 Debug 00:41:39.524] Failed to connect to mtp device. Trying 3 more times...
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
[12 Debug 00:42:01.583] Failed to connect to mtp device. Trying 2 more times...
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
[12 Debug 00:42:23.644] Failed to connect to mtp device. Trying 1 more times...
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
[12 Debug 00:42:45.703] Failed to connect to mtp device. Trying 0 more times...
[1 Warn 00:42:47.706] Failed to load media-player-info file for 1

mtp-detect:
david@sagan:~$ mtp-detect
libmtp version: 1.0.6

Listing raw device(s)
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
   Found 1 device(s):
   Samsung: Vibrant SGH-T959 (04e8:68a9) @ bus 1, dev 10
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
inep: usb_get_endpoint_status(): Device or resource busy
outep: usb_get_endpoint_status(): Device or resource busy
usb_clear_halt() on IN endpoint: Device or resource busy
usb_clear_halt() on OUT endpoint: Device or resource busy
usb_clear_halt() on INTERRUPT endpoint: Device or resource busy
LIBMTP libusb: Attempt to reset device
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.

The device is also still wrongly detected as a Vibrant, this is a Galaxy S i9000

bigbrovar (bigbrovar) wrote :

I am having same issue with my Galaxy S I9000. when I run mtp-detect I get the following error

libmtp version: 1.0.6

Listing raw device(s)
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
   Found 1 device(s):
   Samsung: Vibrant SGH-T959 (04e8:68a9) @ bus 2, dev 16
Attempting to connect device(s)
LIBMTP PANIC: Unable to find interface & endpoints of device
Unable to open raw device 0
OK.
 I was trying to figure out why neither amarok nor banshee is able to sync with the galaxy S.

Alessio Treglia (quadrispro) wrote :

Please give a try with libmtp 1.1.0 now available in Oneiric.

bigbrovar can you test this, I am currently stuck on OS X till such a time as correct installation of Linux on an EFI powered Mac Mini 2011 is possible (timeframe for this should be ca. F16 Beta, or roughly 2 months).

Timothy Arceri (t-fridey) wrote :

Still not working:

timothy@timothy-1005P:/usr/bin$ mtp-detect
libmtp version: 1.1.0

Listing raw device(s)
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
   Found 1 device(s):
   Samsung: Galaxy S GT-I9000 (04e8:6877) @ 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.

Timothy Arceri (t-fridey) wrote :

It seems if I plug my device into usb then quickly run mtp-detect it will
detect my device.

However if I wait even a few seconds then it will fail this would point to
some sort of locking issue I would have thought. What other applications
might be interfering with libmtp???

Timothy Arceri (t-fridey) wrote :

Running device-drivers gives me:

T: Bus=01 Lev=01 Prnt=01 Port=06 Cnt=01 Dev#= 34 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=02(commc) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=04e8 ProdID=6877 Rev=04.00
S: Manufacturer=SAMSUNG
S: Product=SAMSUNG_Android
S: SerialNumber=1000b4332e7e
C: #Ifs= 3 Cfg#= 4 Atr=c0 MxPwr=96mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm
I: If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm
I: If#= 2 Alt= 0 #EPs= 3 Cls=06(still) Sub=01 Prot=01 Driver=(none)

Timothy Arceri (t-fridey) wrote :

My wifes Samsung Nexus S works with banshee, nautilus etc but comes up as:

T: Bus=01 Lev=01 Prnt=01 Port=06 Cnt=01 Dev#= 42 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=18d1 ProdID=4e21 Rev=02.27
S: Manufacturer=Samsung
S: Product=Nexus S
S: SerialNumber=XXXXXXXXXXXXXX
C: #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=500mA
I: If#= 0 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage

Timothy Arceri (t-fridey) wrote :

Hmmm, ok if I turn on USB development in my phones settings and then enable USB mass storage drumroll.........it works!! Banshee etc connect and detect the phone.

And a storage device is added to the usb devices:

T: Bus=01 Lev=01 Prnt=01 Port=06 Cnt=01 Dev#= 44 Spd=480 MxCh= 0
D: Ver= 2.00 Cls=02(commc) Sub=00 Prot=00 MxPS=64 #Cfgs= 1
P: Vendor=04e8 ProdID=681c Rev=04.00
S: Manufacturer=SAMSUNG
S: Product=SAMSUNG_Android
S: SerialNumber=XXXXXXXXXXX
C: #Ifs= 4 Cfg#= 3 Atr=c0 MxPwr=96mA
I: If#= 0 Alt= 0 #EPs= 1 Cls=02(commc) Sub=02 Prot=01 Driver=cdc_acm
I: If#= 1 Alt= 0 #EPs= 2 Cls=0a(data ) Sub=00 Prot=00 Driver=cdc_acm
I: If#= 2 Alt= 0 #EPs= 2 Cls=08(stor.) Sub=06 Prot=50 Driver=usb-storage
I: If#= 3 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=42 Prot=01 Driver=(none)

I guess now someone smarter than me has to work out how to get access to the usb-storage without having to enable usb debugging.

Timothy Arceri (t-fridey) wrote :

Please ignore my last comment wtp does not work when you do that. The
storage device just become accessible.

Timothy Arceri (t-fridey) wrote :

Looking at the Galaxy Tab bug report: http://sourceforge.net/tracker/?func=detail&aid=3372454&group_id=158745&atid=809061

It looks like the issue is Samsung implements Microsoft DRM, and there is no easy fix to get around this.

Jonas Norlander (jonorland) wrote :

I also have a Samsung Galaxy S / GT-I9000
And like above it's miss detected on my Kubuntu 11.10

jonas@tor:~$ sudo mtp-detect
libmtp version: 1.1.0

Listing raw device(s)
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
   Found 1 device(s):
   Samsung: Vibrant SGH-T959 (04e8:68a9) @ bus 1, dev 8
Attempting to connect device(s)
LIBMTP PANIC: Unable to find interface & endpoints of device
Unable to open raw device 0
OK.

Changed in banshee:
status: Confirmed → Unknown
Linus Walleij (triad) wrote :

The MTP stack found in these Samsungs seems to be the Microsoft
one, with a lot of quirks to the USB level of things.

I need to work hands-on with a device to progress on this... Else
I rely 100% on users to hack with libmtp to get it working :-/

fmo (fmo) wrote :

I believe this is the same problem as Bug #815055 and #903422.

This bug seems to have been fixed in the newly released libmtp 1.1.3 see here http://sourceforge.net/projects/libmtp/files/libmtp/1.1.3/

I think it would probably also be a good idea to upgrade mtpfs to 1.1 http://www.adebenham.com/mtpfs/ (current version is 0.9-3)

Not sure where to go from here but I hope it helps.

Changed in libmtp (Ubuntu):
status: Incomplete → Confirmed
Andre (ajx) wrote :

@fmo: Bug #903422 is not a duplicate of this one. This bug here deals with Samsung related problems which are exisiting on pre-ICS versions. Bug #903422 deals with ICS (Android 4) on all kinds of devices.

summary: - Samsung Galaxy S detected but cannot be connected to
+ Samsung Galaxy S / SII detected but cannot be connected to

Thank you for taking the time to report this bug and helping to make Ubuntu better.
Could anyone try to reproduce this with the latest release available in Quantal?

Changed in libmtp (Ubuntu):
status: Confirmed → Incomplete
Jonathan Kamens (jik) wrote :

I am using Fedora, but I suspect this is equally applicable to both Ubuntu and Fedora...

If I (a) ensure that nothing else, e.g., gvfs-gphoto2, mounts my Galaxy S III, and (b) connect to it using libmtp _within about three seconds of when I plug it in_, then the connection is successful.

If, however, something else has already connected to it, e.g., gvfs2-gphoto2-volume-monitor mounts it and then I eject it, OR if I wait three seconds or more after plugging it in before trying to connect to it via libmtp, then the connection fails as shown above.

hoover (uwe-schuerkamp) wrote :

As mentioned above, the device is detected if mtp-detect runs within 3 seconds after pluggging in usb, but then I get a segmentation fault:

$ sleep 5; mtp-detect
libmtp version: 1.1.3

Listing raw device(s)
Device 0 (VID=04e8 and PID=6865) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
   Found 1 device(s):
   04e8:6865 @ bus 2, dev 8
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 WARNING: no MTP vendor extension on device 8 on bus 2LIBMTP WARNING: VendorExtensionID: 00000000LIBMTP WARNING: VendorExtensionDesc: (null)LIBMTP WARNING: this typically means the device is PTP (i.e. a camera) but not an MTP device at all. Trying to continue anyway.Speicherzugriffsfehler (Speicherabzug geschrieben)

dmesg output:
[ 3733.464041] usb 2-6: reset high-speed USB device number 8 using ehci_hcd
[ 3733.596795] usb 2-6: usbfs: process 9182 (mtp-detect) did not claim interface 0 before use
[ 3733.596845] usb 2-6: usbfs: process 5616 (gvfs-gphoto2-vo) did not claim interface 0 before use
[ 3733.596879] usb 2-6: usbfs: process 5616 (gvfs-gphoto2-vo) did not claim interface 0 before use
[ 3733.596891] usb 2-6: usbfs: process 5616 (gvfs-gphoto2-vo) did not claim interface 0 before use
[ 3733.596906] usb 2-6: usbfs: process 5616 (gvfs-gphoto2-vo) did not claim interface 0 before use
[ 3733.596916] usb 2-6: usbfs: process 5616 (gvfs-gphoto2-vo) did not claim interface 0 before use
[ 3734.668356] mtp-detect[9182]: segfault at 8 ip b7644616 sp bfef6c74 error 4 in libc-2.15.so[b75c2000+19f000]

cm-t arudy (cm-t) wrote :

* nautilus/rythmbox launched
* connect my SII via USB, to my Ubuntu 12.04.1 LTS, in mode storage (not camera) (phone is power ON if ever)
* lsusb → Bus 002 Device 015: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II]
* ls /media → ./ ../
* sudo apt-get install mtp-detect
* mtp-detect
libmtp version: 1.1.3

Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note.
   Found 1 device(s):
   Samsung: GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note (04e8:6860) @ bus 2, dev 18
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
usb_clear_halt() on IN endpoint: Device or resource busy
usb_clear_halt() on OUT endpoint: Device or resource busy
usb_clear_halt() on INTERRUPT endpoint: Device or resource busy
LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.

* Just after unplug/plugin:
 mtp-detect
libmtp version: 1.1.3

Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note.
   Found 1 device(s):
   Samsung: GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note (04e8:6860) @ bus 2, dev 19
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.

cm-t arudy (cm-t) wrote :

+ Sometime I can see in nautilus like if it was mounted and able to see folders, no file into these folders (expeted result: show files r-w-x) and action possible; visible in rythmbox but nothing inside. This popup happend in this case (If I seen it well).

Changed in banshee:
importance: Medium → Undecided
status: Unknown → New
status: New → Invalid
Geoffrey Pursell (geoffp) wrote :

This comment on the upstream libmtp bug has indicated that this could be a distro config issue:
http://sourceforge.net/p/libmtp/bugs/354/?limit=10&page=2#6dae

Unfortunately, it has also been closed due to lack of activity, despite there being many Galaxy S3 owners with no ability to interact with the media on their devices on Linux. I will try to test the given workaround if I can find the time.

summary: - Samsung Galaxy S / SII detected but cannot be connected to
+ Samsung Galaxy S / S2 / S3 detected but cannot be connected to

Run in this issue on 12.04.1 with a Samsung Galaxy S 2 (GT-I9100)

Dec 24 15:28:24 dilbert kern.info kernel [] -- [ 1426.002289] usb 1-4.1: new high-speed USB device number 8 using ehci_hcd
Dec 24 15:28:25 dilbert kern.info kernel [] -- [ 1426.097890] usb 1-4.1: New USB device found, idVendor=04e8, idProduct=6860
Dec 24 15:28:25 dilbert kern.info kernel [] -- [ 1426.097901] usb 1-4.1: New USB device strings: Mfr=2, Product=3, SerialNumber=4
Dec 24 15:28:25 dilbert kern.info kernel [] -- [ 1426.097908] usb 1-4.1: Product: SAMSUNG_Android
Dec 24 15:28:25 dilbert kern.info kernel [] -- [ 1426.097913] usb 1-4.1: Manufacturer: SAMSUNG
Dec 24 15:28:25 dilbert kern.info kernel [] -- [ 1426.097918] usb 1-4.1: SerialNumber: 000e33f34c22af

 $ mtp-detect
libmtp version: 1.1.3

Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note.
   Found 1 device(s):
   Samsung: GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note (04e8:6860) @ bus 1, dev 7
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.

Changed in libmtp (Ubuntu):
status: Incomplete → Confirmed
tags: added: precise
Changed in libmtp (Ubuntu):
status: Confirmed → New
Changed in libmtp (Ubuntu):
status: New → Confirmed

Problem also with backported (raring) libmtp ( --> 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.

Also used backported mptfs 1.1.2 (see https://bugs.launchpad.net/ubuntu/+source/libmtp/+bug/815055/comments/6) from raring.
 ( --> https://launchpad.net/~dirk-computer42/+archive/c42-edge )

Problem is not resolved.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.