+1 for this feature. For some reason it doesn't connect properly (appears in RhythmBox as unknown device with 0bytes storage - mtp-detect doesn't given any joy either).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Also, just to mention that my numbers are a bit different. lsusb gives
Bus 001 Device 003: ID 04e8:68a9 Samsung Electronics Co., Ltd
mtp-detect gives
libmtp version: 1.0.2
Listing raw device(s)
Device 0 (VID=04e8 and PID=68a9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
04e8:68a9 @ bus 1, dev 3
Attempting to connect device(s)
ignoring usb_claim_interface = -16ignoring usb_claim_interface = -22PTP_ERROR_IO: Trying again after re-initializing 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 PANIC: Could not open session! (Return code 767)
Try to reset the device.
Unable to open raw device 0
OK.
Hope that's helpful. I'd really love to see this work!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Listing raw device(s)
Device 0 (VID=04e8 and PID=68a9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
04e8:68a9 @ bus 1, dev 4
Attempting to connect device(s)
PTP_ERROR_IO: Trying again after re-initializing USB interface
inep: usb_get_endpoint_status(): Broken pipe
outep: usb_get_endpoint_status(): Broken pipe
libmtpLIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Unable to open raw device 0
OK.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Output from lsusb:
Bus 002 Device 072: ID 04e8:6877 Samsung Electronics Co., Ltd
Output from mtp-detect:
libmtp version: 1.0.2
Listing raw device(s)
Device 0 (VID=04e8 and PID=6877) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
04e8:6877 @ bus 2, dev 72
Attempting to connect device(s)
PTP_ERROR_IO: Trying again after re-initializing USB interface
inep: usb_get_endpoint_status(): Broken pipe
outep: usb_get_endpoint_status(): Broken pipe
LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Unable to open raw device 0
OK.
I hope this helps, let me know if you need someone to run any tests or provide more info.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a slightly different PID value. Since USB hacking is a mystery, I'm not sure if this matters one bit or not, so I'll post my mtp-detect output:
Listing raw device(s)
Device 0 (VID=04e8 and PID=68a9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
04e8:68a9 @ bus 1, dev 12
Attempting to connect device(s)
PTP_ERROR_IO: Trying again after re-initializing USB interface
inep: usb_get_endpoint_status(): Broken pipe
outep: usb_get_endpoint_status(): Broken pipe
LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Unable to open raw device 0
OK.
My device is the Galaxy S as rebranded by T-Mobile (called the Vibrant, model number SGH-T959.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Device 0 (VID=04e8 and PID=68a9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Device 0 (VID=04e8 and PID=68a9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
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
ignoring usb_claim_interface = -9ignoring usb_claim_interface = -22LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Device 0 (VID=04e8 and PID=68a9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
PTP_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
ignoring usb_claim_interface = -9ignoring usb_claim_interface = -22LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Device 0 (VID=04e8 and PID=68a9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Device 0 (VID=04e8 and PID=68a9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
PTP_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
ignoring usb_claim_interface = -9ignoring usb_claim_interface = -22LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Device 0 (VID=04e8 and PID=68a9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
PTP_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
lsusb says:
Bus 002 Device 002: ID 04e8:68a9 Samsung Electronics Co., Ltd
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 1
bMaxPacketSize0 64
idVendor 0x04e8 Samsung Electronics Co., Ltd
idProduct 0x68a9
bcdDevice 4.00
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 5
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 96mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 6 Imaging
bInterfaceSubClass 1 Still Image Capture
bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470)
iInterface 8
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8c EP 12 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 0x0a EP 10 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 14
can't get device qualifier: Connection timed out
can't get debug descriptor: Connection timed out
cannot read device status, Connection timed out (110)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Has this ever gotten fixed? I have a Samsung Captivate, same issue.
USB Mode: Media Player mtp-device output:
libmtp version: 1.0.3
Listing raw device(s)
Device 0 (VID=04e8 and PID=68a9) is a Samsung Captivate.
Found 1 device(s):
Samsung: Captivate (04e8:68a9) @ bus 2, dev 8
Attempting to connect device(s)
PTP_ERROR_IO: Trying again after re-initializing USB interface
inep: usb_get_endpoint_status(): Broken pipe
outep: usb_get_endpoint_status(): Broken pipe
LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Unable to open raw device 0
OK.
Usb Mode Samsung Kies mtp-device output:
libmtp version: 1.0.3
Listing raw device(s)
Device 0 (VID=04e8 and PID=6877) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
04e8:6877 @ bus 2, dev 9
Attempting to connect device(s)
PTP_ERROR_IO: Trying again after re-initializing USB interface
inep: usb_get_endpoint_status(): Broken pipe
outep: usb_get_endpoint_status(): Broken pipe
LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Unable to open raw device 0
OK.
I grabbed the cvs of libmtp and attempted to add it to media_players.h but I'm thinking it's a little more involved then proper device detection.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Added with both IDs. The error messages indicate that it
probably needs DEVICE_FLAG_NO_ZERO_READS, please
help debugging and testing this on the CVS version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You can further help us with libmtp by identifying if this device
needs some futher special device flags. If a device has "siblings"
in the database (similar devices from same manufacturer) we
often add default bug flags like its closest siblings, and sometimes
this is right, sometimes bugs have been fixed so it's wrong.
I checked out and installed the latest version. My Samsung is now detected and correctly identified, but there are problems with connecting. This is the output of running examples/detect:
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 2, dev 7
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 think the reason my device has a different ProductId from what others are reporting is that I have the European version. It's the same as the USA version with 8 GiB, except it does not have a built-in gyroscope, just an accelerometer.
If I can help by running more tests, please let me know.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
terrigan@Ichigo:~$ rhythmbox
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
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.
Samsung Kies mode:
terrigan@Ichigo:~$ rhythmbox
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
PTP_ERROR_IO: Trying again after re-initializing USB interface
inep: usb_get_endpoint_status(): Broken pipe
outep: usb_get_endpoint_status(): Broken pipe
LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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???
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
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.
Looking at the raw contents of that dump I can see it's not an Android
MTP implementation but rather some heavily DRM:ed Microsoft
version, supporting all of their special extensions.
This might require some authentication etc to work properly, and
maybe DEVICE_FLAG_ALWAYS_PROBE_DESCRIPTOR
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I do have Samsung Galaxy S III, GT-I9300
I have downloaded latest libmtp 1.1.3 from GIT and compiled.
When I am lucky, I do have correct MTP connection to my phone. By "lucky" - I mean that from 10 trials, only 1 is successful.
Here is output:
virnik@cyborg:~/Work/libmtp$ 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/I9070/I9100/I9300 Galaxy Tab 7.7/10.1/S2/S3/Nexus/Note/Y.
Found 1 device(s):
Samsung: GT P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab 7.7/10.1/S2/S3/Nexus/Note/Y (04e8:6860) @ bus 1, dev 20
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): Protocol error
outep: usb_get_endpoint_status(): Protocol error
usb_clear_halt() on IN endpoint: Protocol error
usb_clear_halt() on OUT endpoint: Protocol error
usb_clear_halt() on INTERRUPT endpoint: Protocol error
ignoring usb_claim_interface = -71LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
Running Kubuntu 12.04, x64
Virnik
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Does the luck coincide with the screen being unlocked?
Pls check the following advice from README:
mtp-* tools doesn't work because someone else is already hogging
the device
This is a common problem, the most common case could be that
gphoto2 (which can also talk PTP/MTP) is taking over the device
as soon as it's plugged in. Some distributions are configured that
way. Counter it like this:
gvfs-mount -s gphoto2
Then re-attach the device.
Sometimes the "gvfs-gphoto2-volume-monitor" is running on the
system and hogging the device, try something like:
pkill gfvs-gphoto2-volume-monitor && mtp-detect
to figure out if this may be the case.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
+1 for this feature. For some reason it doesn't connect properly (appears in RhythmBox as unknown device with 0bytes storage - mtp-detect doesn't given any joy either).
Also, just to mention that my numbers are a bit different. lsusb gives
Bus 001 Device 003: ID 04e8:68a9 Samsung Electronics Co., Ltd
mtp-detect gives
libmtp version: 1.0.2
Listing raw device(s)
Device 0 (VID=04e8 and PID=68a9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
04e8:68a9 @ bus 1, dev 3
Attempting to connect device(s)
ignoring usb_claim_interface = -16ignoring usb_claim_interface = -22PTP_ERROR_IO: Trying again after re-initializing 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 PANIC: Could not open session! (Return code 767)
Try to reset the device.
Unable to open raw device 0
OK.
Hope that's helpful. I'd really love to see this work!
libmtp version: 1.0.2
Listing raw device(s)
Device 0 (VID=04e8 and PID=68a9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
04e8:68a9 @ bus 1, dev 4
Attempting to connect device(s)
PTP_ERROR_IO: Trying again after re-initializing USB interface
inep: usb_get_endpoint_status(): Broken pipe
outep: usb_get_endpoint_status(): Broken pipe
libmtpLIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Unable to open raw device 0
OK.
I'll try to get around to hacking on it tomorrow it should be pretty standard as an android phone (heres hoping!)
Output from lsusb:
Bus 002 Device 072: ID 04e8:6877 Samsung Electronics Co., Ltd
Output from mtp-detect:
libmtp version: 1.0.2
Listing raw device(s)
Device 0 (VID=04e8 and PID=6877) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
04e8:6877 @ bus 2, dev 72
Attempting to connect device(s)
PTP_ERROR_IO: Trying again after re-initializing USB interface
inep: usb_get_endpoint_status(): Broken pipe
outep: usb_get_endpoint_status(): Broken pipe
LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Unable to open raw device 0
OK.
I hope this helps, let me know if you need someone to run any tests or provide more info.
I have a slightly different PID value. Since USB hacking is a mystery, I'm not sure if this matters one bit or not, so I'll post my mtp-detect output:
Listing raw device(s)
Device 0 (VID=04e8 and PID=68a9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
04e8:68a9 @ bus 1, dev 12
Attempting to connect device(s)
PTP_ERROR_IO: Trying again after re-initializing USB interface
inep: usb_get_endpoint_status(): Broken pipe
outep: usb_get_endpoint_status(): Broken pipe
LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Unable to open raw device 0
OK.
My device is the Galaxy S as rebranded by T-Mobile (called the Vibrant, model number SGH-T959.
+1 here too - I have the same device, would be nice to see it work...
I get the following libmtp output, via rhythmbox:
Device 0 (VID=04e8 and PID=68a9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Device 0 (VID=04e8 and PID=68a9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
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
ignoring usb_claim_interface = -9ignoring usb_claim_interface = -22LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Device 0 (VID=04e8 and PID=68a9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
PTP_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
ignoring usb_claim_interface = -9ignoring usb_claim_interface = -22LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Device 0 (VID=04e8 and PID=68a9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Device 0 (VID=04e8 and PID=68a9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
PTP_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
ignoring usb_claim_interface = -9ignoring usb_claim_interface = -22LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Device 0 (VID=04e8 and PID=68a9) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
PTP_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
lsusb says:
Bus 002 Device 002: ID 04e8:68a9 Samsung Electronics Co., Ltd
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 0 (Defined at Interface level)
bDeviceSubClass 0
bDeviceProtocol 1
bMaxPacketSize0 64
idVendor 0x04e8 Samsung Electronics Co., Ltd
idProduct 0x68a9
bcdDevice 4.00
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 39
bNumInterfaces 1
bConfigurationValue 5
iConfiguration 0
bmAttributes 0xc0
Self Powered
MaxPower 96mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 3
bInterfaceClass 6 Imaging
bInterfaceSubClass 1 Still Image Capture
bInterfaceProtocol 1 Picture Transfer Protocol (PIMA 15470)
iInterface 8
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8c EP 12 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 0x0a EP 10 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x86 EP 6 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 14
can't get device qualifier: Connection timed out
can't get debug descriptor: Connection timed out
cannot read device status, Connection timed out (110)
Has this ever gotten fixed? I have a Samsung Captivate, same issue.
USB Mode: Media Player mtp-device output:
libmtp version: 1.0.3
Listing raw device(s)
Device 0 (VID=04e8 and PID=68a9) is a Samsung Captivate.
Found 1 device(s):
Samsung: Captivate (04e8:68a9) @ bus 2, dev 8
Attempting to connect device(s)
PTP_ERROR_IO: Trying again after re-initializing USB interface
inep: usb_get_endpoint_status(): Broken pipe
outep: usb_get_endpoint_status(): Broken pipe
LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Unable to open raw device 0
OK.
Usb Mode Samsung Kies mtp-device output:
libmtp version: 1.0.3
Listing raw device(s)
Device 0 (VID=04e8 and PID=6877) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
04e8:6877 @ bus 2, dev 9
Attempting to connect device(s)
PTP_ERROR_IO: Trying again after re-initializing USB interface
inep: usb_get_endpoint_status(): Broken pipe
outep: usb_get_endpoint_status(): Broken pipe
LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
Unable to open raw device 0
OK.
I grabbed the cvs of libmtp and attempted to add it to media_players.h but I'm thinking it's a little more involved then proper device detection.
Added with both IDs. The error messages indicate that it
probably needs DEVICE_FLAG_NO_ZERO_READS, please
help debugging and testing this on the CVS version.
This device has been added to the libmtp database in CVS.
You can verify it by browsing the database here:
http://libmtp.cvs.sourceforge.net/viewvc/libmtp/libmtp/src/music-players.h?view=markup
If you want to test your device with the new support added in
CVS, refer to making a CVS check-out:
https://sourceforge.net/cvs/?group_id=158745
You can further help us with libmtp by identifying if this device
needs some futher special device flags. If a device has "siblings"
in the database (similar devices from same manufacturer) we
often add default bug flags like its closest siblings, and sometimes
this is right, sometimes bugs have been fixed so it's wrong.
If you have special problems, refer to the README file:
http://libmtp.cvs.sourceforge.net/viewvc/checkout/libmtp/libmtp/README
If you have problems installing and linking the library refer to the INSTALL file:
http://libmtp.cvs.sourceforge.net/viewvc/checkout/libmtp/libmtp/INSTALL
I checked out and installed the latest version. My Samsung is now detected and correctly identified, but there are problems with connecting. This is the output of running examples/detect:
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 2, dev 7
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 think the reason my device has a different ProductId from what others are reporting is that I have the European version. It's the same as the USA version with 8 GiB, except it does not have a built-in gyroscope, just an accelerometer.
If I can help by running more tests, please let me know.
Grabbed CVS version and hooked up my Captivate.
Media player mode:
terrigan@Ichigo:~$ rhythmbox
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
Device 0 (VID=04e8 and PID=68a9) is a Samsung Vibrant SGH-T959.
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.
Samsung Kies mode:
terrigan@Ichigo:~$ rhythmbox
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
Device 0 (VID=04e8 and PID=6877) is a Samsung Galaxy S GT-I9000.
PTP_ERROR_IO: Trying again after re-initializing USB interface
inep: usb_get_endpoint_status(): Broken pipe
outep: usb_get_endpoint_status(): Broken pipe
LIBMTP PANIC: Could not open session! (Return code 767)
Try to reset the device.
No clue on how to proceed on this, I've just been guessing...
Need developes who can test the device and probe it, myself
I don't have it :-/
In dmesg I find this:
[48159.680156] usb 1-2: usbfs: USBDEVFS_CONTROL failed cmd lt-detect rqt 130 rq 0 len 2 ret -110
Is there anyhow we can assist with probing the device?
Resolution is marked 'fixed' but it doesn't work for me!
I've tested with the latest CVS checkout as repackaged and compiled on Debian/Sid against my Galaxy handset.
The results are interesting if disappointing.
The full test typescript is available here: https://docs.google.com/leaf?id=0B-r0kOumKPg2NDlkZmI3MzctMzkyMS00MWQ5LThkZjgtNjI4NDg5YjY3NjI1&sort=name&layout=list&num=50
A summary follows, with the hope this can clue the core developers.
I've tried 2 setting in music-players.h:
{ "Samsung", 0x04e8, "GalaxyS MTP x3", 0x68a9,
// DEVICE_FLAG_UNLOAD_DRIVER |
// DEVICE_FLAG_PLAYLIST_SPL_V1 |
// DEVICE_FLAG_NO_ZERO_READS
DEVICE_FLAG_NONE },{ "Samsung", 0x04e8, "GalaxyS MTP x4", 0x68a9,
DEVICE_FLAG_UNLOAD_DRIVER | DEVICE_FLAG_PLAYLIST_SPL_V1 | DEVICE_FLAG_NO_ZERO_READS// DEVICE_FLAG_NONE
In one instance 'mtp-detect -d' successfully completes. Other times, not so much.
A good session begins like:
t61p:/home/candlish/src/libmtp# mtp-detect -d
LIBMTP_Set_Debug: Setting debugging level to 9 (on)
libmtp version: 1.0.3
Listing raw device(s)
LIBMTP LIBMTP_Detect_Raw_Devices[581]: Device 0 (VID=04e8 and PID=68a9) is a Samsung GalaxyS MTP x3.
Found 1 device(s):
Samsung: GalaxyS MTP x3 (04e8:68a9) @ bus 1, dev 19
Attempting to connect device(s)
PTP: Opening session 0000: 1000 0000 0100 0210 0000 0000 0100 0000 ................
a bad session begins like this:
t61p:/home/candlish/src/libmtp# mtp-detect -d
LIBMTP_Set_Debug: Setting debugging level to 9 (on)
libmtp version: 1.0.3
Listing raw device(s)
LIBMTP LIBMTP_Detect_Raw_Devices[581]: Device 0 (VID=04e8 and PID=68a9) is a Samsung GalaxyS MTP x3.
Found 1 device(s):
Samsung: GalaxyS MTP x3 (04e8:68a9) @ bus 1, dev 17
Attempting to connect device(s)
ignoring usb_claim_interface = -110PTP: Opening session 0000: 1000 0000 0100 0210 0000 0000 0100 0000 ................
Thanx
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???
Running usb-devices 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)
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.
Please ignore my last comment wtp does not work when you do that. The storage device just become accessible.
Looking at the raw contents of that dump I can see it's not an Android
MTP implementation but rather some heavily DRM:ed Microsoft
version, supporting all of their special extensions.
This might require some authentication etc to work properly, and
maybe DEVICE_FLAG_ALWAYS_PROBE_DESCRIPTOR
Please test this with libmtp 1.1.3.
I have 1.1.3 on Ubuntu 12.04 and the Galaxy S3 still doesn't work.
Hello,
I do have Samsung Galaxy S III, GT-I9300
I have downloaded latest libmtp 1.1.3 from GIT and compiled.
When I am lucky, I do have correct MTP connection to my phone. By "lucky" - I mean that from 10 trials, only 1 is successful.
Here is output:
virnik@cyborg:~/Work/libmtp$ 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/I9070/I9100/I9300 Galaxy Tab 7.7/10.1/S2/S3/Nexus/Note/Y.
Found 1 device(s):
Samsung: GT P7310/P7510/N7000/I9070/I9100/I9300 Galaxy Tab 7.7/10.1/S2/S3/Nexus/Note/Y (04e8:6860) @ bus 1, dev 20
Attempting to connect device(s)
PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): Protocol error
outep: usb_get_endpoint_status(): Protocol error
usb_clear_halt() on IN endpoint: Protocol error
usb_clear_halt() on OUT endpoint: Protocol error
usb_clear_halt() on INTERRUPT endpoint: Protocol error
ignoring usb_claim_interface = -71LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.
Running Kubuntu 12.04, x64
Virnik
Does the luck coincide with the screen being unlocked?
Pls check the following advice from README:
the device
This is a common problem, the most common case could be that
gphoto2 (which can also talk PTP/MTP) is taking over the device
as soon as it's plugged in. Some distributions are configured that
way. Counter it like this:
gvfs-mount -s gphoto2
Then re-attach the device.
Sometimes the "gvfs-gphoto2-volume-monitor" is running on the
system and hogging the device, try something like:
pkill gfvs-gphoto2-volume-monitor && mtp-detect
to figure out if this may be the case.