Menu

#455 Samsung Galaxy S2 - GT-I9100

GIT version
open
5
2015-03-27
2011-08-02
Anonymous
No

Hi,

Here you can find the information provided by the latest version of Libmtp (through VirtualBox) with my Samsung Galaxy S2

libmtp version: 1.1.0

Listing raw device(s)
Device 0 (VID=04e8 and PID=6860) is a Samsung GT-P7510/Galaxy Tab 10.1.
Found 1 device(s):
Samsung: GT-P7510/Galaxy Tab 10.1 (04e8:6860) @ bus 1, dev 3
Attempting to connect device(s)
ignoring usb_claim_interface = -110PTP_ERROR_IO: failed to open session, trying again after resetting USB interface
LIBMTP libusb: Attempt to reset device
inep: usb_get_endpoint_status(): No such device
outep: usb_get_endpoint_status(): No such device
usb_clear_halt() on IN endpoint: No such device
usb_clear_halt() on OUT endpoint: No such device
usb_clear_halt() on INTERRUPT endpoint: No such device
ignoring usb_claim_interface = -9ignoring usb_claim_interface = -22LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.

And the lsusb -v result :

Bus 001 Device 004: ID 04e8:6860 Samsung Electronics Co., Ltd
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 1.10
bDeviceClass 239 Miscellaneous Device
bDeviceSubClass 2 ?
bDeviceProtocol 1 Interface Association
bMaxPacketSize0 64
idVendor 0x04e8 Samsung Electronics Co., Ltd
idProduct 0x6860
bcdDevice 4.00
iManufacturer 1
iProduct 2
iSerial 3
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 105
bNumInterfaces 3
bConfigurationValue 1
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 11
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x8e EP 14 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 0x0d EP 13 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 0x89 EP 9 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 14
Interface Association:
bLength 8
bDescriptorType 11
bFirstInterface 1
bInterfaceCount 2
bFunctionClass 2 Communications
bFunctionSubClass 2 Abstract (modem)
bFunctionProtocol 0 None
iFunction 7
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 1
bAlternateSetting 0
bNumEndpoints 1
bInterfaceClass 2 Communications
bInterfaceSubClass 2 Abstract (modem)
bInterfaceProtocol 1 AT-commands (v.25ter)
iInterface 5
CDC Header:
bcdCDC 1.10
CDC Call Management:
bmCapabilities 0x00
bDataInterface 2
CDC ACM:
bmCapabilities 0x02
line coding and serial state
CDC Union:
bMasterInterface 1
bSlaveInterface 2
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x000a 1x 10 bytes
bInterval 9
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 2
bAlternateSetting 0
bNumEndpoints 2
bInterfaceClass 10 CDC Data
bInterfaceSubClass 0 Unused
bInterfaceProtocol 0
iInterface 6
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x85 EP 5 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 0x04 EP 4 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
cannot read device status, Connection timed out (110)

Regards Nico

Discussion

  • Anonymous

    Anonymous - 2011-08-26

    I think that this could be solved by adding support for the Samsung Galaxy Tab 10.1, since their device IDs are identical. Discussion about that is going on in tracker issue 3372454.

     
  • Anonymous

    Anonymous - 2011-09-10

    I can provide a USB capture from USBlyzer if you want, just ask me if you want it

     
  • Anonymous

    Anonymous - 2011-09-10

    I need more info to classify and possibly add this device.

    • What does "mtp-detect" (maybe run as root) produce?
    • What does lsusb -vv display for this device?
     
  • frapell

    frapell - 2011-09-11

    I'm having these exact issues with my Samsung Galaxy S2.

    As per Issue #3372454 i tried running mtp-detect as soon as i plugged in the device and i got some useful output, but then i got errors for every time i tried it afterwards.

    I also have some verbose output from lsusb.

    mtp-detect : http://pastebin.lugmen.org.ar/6789 (Serial number hidden by me)
    lsusb: http://pastebin.lugmen.org.ar/6790

    PS: Any idea on how can i attach a file directly here instead of using pastebin ?

     
  • Anonymous

    Anonymous - 2012-01-05

    galaxy s2 running cyanogenmod 9 heres the ptp mode output

    $ mtp-detect
    libmtp version: 1.1.1

    Listing raw device(s)
    Device 0 (VID=04e8 and PID=6866) is UNKNOWN.
    Please report this VID/PID and the device model to the libmtp development team
    Found 1 device(s):
    04e8:6866 @ bus 2, dev 14
    Attempting to connect device(s)
    ignoring usb_claim_interface = -16ignoring usb_claim_interface = -22PTP_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 mtp mode:

    sudo mtp-detect
    libmtp version: 1.1.1

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

     
  • Linus Walleij

    Linus Walleij - 2012-01-12

    So this bug may be a duplicate of the Galaxy Tab 10.2?

    Is this in Android 3 (Gingerbread) or Android 4 (Ice Cream Sandwich)?

    I have a vague idea that Androids MTP stack is used from 4.0 forth and Samsung
    used their own stack (with these issues) prior to that.

     
  • Linus Walleij

    Linus Walleij - 2012-01-12

    bongmaster: when you runt it in PTP mode, have you tried it with gPhoto2 without libmtp?

     
  • Anonymous

    Anonymous - 2012-03-31

    I got these results using Ubuntu 12.04 and a Samsung Galaxy S2 (GT-I9100) running the latest official Samsung 4.0.3 (ICS) Firmware:

    CONNECTING VIA MTP:

    coversnail@Keith-Lenovo-B570:~$ mtp-detect
    libmtp version: 1.1.2

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

    CONNECTING VIA PTP:

    coversnail@Keith-Lenovo-B570:~$ mtp-detect
    libmtp version: 1.1.2

    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 1, dev 10
    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.

     
  • Linus Walleij

    Linus Walleij - 2012-04-02

    We have a few fixes in the git for this device since last week or so, can you
    please check if it solves your problems?

     
  • botusj

    botusj - 2012-04-12

    Same sort of issues with the latest libmtp.
    This took a long time to finish, maybe an hour or more.

    $ sudo 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 11
    Attempting to connect device(s)
    ignoring usb_claim_interface = -99^C[jochem@jochem-desktop ~]$ ^C
    [jochem@jochem-desktop ~]$ sudo 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 12
    Attempting to connect device(s)
    ignoring usb_claim_interface = -99Android device detected, assigning default bug flags
    USB low-level info:
    Interface has a kernel driver attached.
    bcdUSB: 512
    bDeviceClass: 0
    bDeviceSubClass: 0
    bDeviceProtocol: 0
    idVendor: 04e8
    idProduct: 6860
    IN endpoint maxpacket: 512 bytes
    OUT endpoint maxpacket: 512 bytes
    Raw device info:
    Bus location: 1
    Device number: 12
    Device entry info:
    Vendor: Samsung
    Vendor id: 0x04e8
    Product: GT-P7310/P7510/N7000/I9100/Galaxy Tab 7.7/10.1/S2/Nexus/Note
    Vendor id: 0x6860
    Device flags: 0x48008107
    Device info:
    Manufacturer: samsung
    Model: GT-I9100
    Device version: 1.0
    Serial number: ????????
    Vendor extension ID: 0x00000006
    Vendor extension description: microsoft.com: 1.0; android.com: 1.0;
    Detected object size: 64 bits
    Extensions:
    microsoft.com: 1.0
    android.com: 1.0
    Supported operations:
    1001: get device info
    1002: Open session
    1003: Close session
    1004: Get storage IDs
    1005: Get storage info
    1006: Get number of objects
    1007: Get object handles
    1008: Get object info
    1009: Get object
    100a: Get thumbnail
    100b: Delete object
    100c: Send object info
    100d: Send object
    1014: Get device property description
    1015: Get device property value
    1016: Set device property value
    1017: Reset device property value
    101b: Get partial object
    9801: Get object properties supported
    9802: Get object property description
    9803: Get object property value
    9804: Set object property value
    9805: Get object property list
    9810: Get object references
    9811: Set object references
    95c1: Unknown (95c1)
    95c2: Unknown (95c2)
    95c3: Unknown (95c3)
    95c4: Unknown (95c4)
    95c5: Unknown (95c5)
    Events supported:
    0x4002
    0x4003
    0x4004
    0x4005
    Device Properties Supported:
    0xd401: Synchronization Partner
    0xd402: Friendly Device Name
    0x5003: Image Size
    Playable File (Object) Types and Object Properties Supported:
    3000: Undefined Type
    3001: Association/Directory
    3004: Text
    3005: HTML
    3008: MS Wave
    3009: MP3
    300b: MPEG
    3801: JPEG
    3802: TIFF EP
    3807: GIF
    3808: JFIF
    380b: PNG
    380d: TIFF
    b901: WMA
    b902: OGG
    b903: AAC
    b982: MP4
    b983: MP2
    b984: 3GP
    ba05: Abstract Audio Video Playlist
    ba10: WPL Playlist
    ba11: M3U Playlist
    ba14: PLS Playlist
    ba82: XMLDocument
    b906: FLAC
    Storage Devices:
    StorageID: 0x00010001
    StorageType: 0x0003 fixed RAM storage
    FilesystemType: 0x0002 generic hierarchical
    AccessCapability: 0x0000 read/write
    MaxCapacity: 12332314624
    FreeSpaceInBytes: 9372131328
    FreeSpaceInObjects: 1073741824
    StorageDescription: Interne opslag
    VolumeIdentifier: (null)
    Special directories:
    Default music folder: 0x00001a95
    Default playlist folder: 0xffffffff
    Default picture folder: 0x00001a9d
    Default video folder: 0xffffffff
    Default organizer folder: 0xffffffff
    Default zencast folder: 0xffffffff
    Default album folder: 0xffffffff
    Default text folder: 0xffffffff
    MTP-specific device properties:
    Friendly name: (NULL)
    Synchronization partner: (NULL)
    libmtp supported (playable) filetypes:
    Folder
    Text file
    HTML file
    RIFF WAVE file
    ISO MPEG-1 Audio Layer 3
    MPEG video stream
    JPEG file
    GIF bitmap file
    JFIF file
    Portable Network Graphics
    TIFF bitmap file
    Microsoft Windows Media Audio
    Ogg container format
    Advanced Audio Coding (AAC)/MPEG-2 Part 7/MPEG-4 Part 3
    MPEG-4 Part 14 Container Format (Audio+Video Emphasis)
    ISO MPEG-1 Audio Layer 2
    Abstract Playlist file
    XML file
    Free Lossless Audio Codec (FLAC)
    ERROR: Could not close session!
    inep: usb_get_endpoint_status(): No such file or directory
    outep: usb_get_endpoint_status(): No such file or directory
    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
    OK.

    $sudo lsusb -vd 04e8:6860

    Bus 001 Device 012: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II]
    Device Descriptor:
    bLength 18
    bDescriptorType 1
    bcdUSB 2.00
    bDeviceClass 0 (Defined at Interface level)
    bDeviceSubClass 0
    bDeviceProtocol 0
    bMaxPacketSize0 64
    idVendor 0x04e8 Samsung Electronics Co., Ltd
    idProduct 0x6860 GT-I9100 Phone [Galaxy S II]
    bcdDevice 2.26
    iManufacturer 2
    iProduct 3
    iSerial 4
    bNumConfigurations 1
    Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 62
    bNumInterfaces 2
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xc0
    Self Powered
    MaxPower 96mA
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 0
    bAlternateSetting 0
    bNumEndpoints 3
    bInterfaceClass 255 Vendor Specific Class
    bInterfaceSubClass 255 Vendor Specific Subclass
    bInterfaceProtocol 0
    iInterface 1
    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 0x04 EP 4 OUT
    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 0x83 EP 3 IN
    bmAttributes 3
    Transfer Type Interrupt
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x001c 1x 28 bytes
    bInterval 6
    Interface Descriptor:
    bLength 9
    bDescriptorType 4
    bInterfaceNumber 1
    bAlternateSetting 0
    bNumEndpoints 2
    bInterfaceClass 255 Vendor Specific Class
    bInterfaceSubClass 66
    bInterfaceProtocol 1
    iInterface 0
    Endpoint Descriptor:
    bLength 7
    bDescriptorType 5
    bEndpointAddress 0x85 EP 5 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 0x07 EP 7 OUT
    bmAttributes 2
    Transfer Type Bulk
    Synch Type None
    Usage Type Data
    wMaxPacketSize 0x0200 1x 512 bytes
    bInterval 0
    Device Status: 0x0000
    (Bus Powered)

     
  • Linus Walleij

    Linus Walleij - 2012-05-02

    Hm. have you tried this with the example program
    mtp-filetree that access the device in the way that Android
    devices prefer to be rubbed?

     
  • Aleksander Adamowski

    Hi! I think it's not necessary to wait a full hour to finish it (I suppose it's some libmtp's timeout).

    I've discovered that mtp-detect seems to output the same information when you physically disconnect the device some seconds after launching mtp-detect.

    botusj, Nico, could you verify that you get exactly the same info when simply disconnecting the device (no stuff missing from the output)?

    I also suspect that this issue is the same as described in this bug:

    https://sourceforge.net/tracker/?func=detail&aid=3372454&group_id=158745&atid=809061#

    that is, it's a problem with handling of Samsung's extensions to Android MTP stack (like the darned Microsoft DRM).

    Maybe you can capture some USB traffic logs on Windows how it communicates with your device (using this: http://blogs.msdn.com/b/usbcoreblog/archive/2009/12/04/etw-in-the-windows-7-usb-core-stack.aspx or this: http://code.google.com/p/busdog/ )?

     
  • Aleksander Adamowski

    BTW, I've tested using libmtp compiled from Git master today and the behaviour is the same. Verified using strace that mtp-detect and mtp-filetree actually link with the Git version of the library. They both hang after printing out "Attempting to connect device(s)".

     
  • Linus Walleij

    Linus Walleij - 2012-06-28

    no response from poster so closing

     
  • Dietmar Hofer

    Dietmar Hofer - 2012-12-31

    I have the same issue on Ubuntu 12.04, S2 with Samsung ICS.
    Trying with libmtp 1.1.5 (git f97c48f1f):

    ~/src/libmtp/examples$ ./mtp-connect 
    libmtp version: 1.1.5
    
    Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
    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
    No devices.
    

    I captured USB communication with usbmon, see attachment.

    Please let me know how else I can help.

    (update: sry, can't delete the duplicate attachment, seems to be a sf bug)

     

    Last edit: Dietmar Hofer 2012-12-31
  • Linus Walleij

    Linus Walleij - 2013-01-01
    • status: closed --> open
    • milestone: --> GIT version
     
  • Anonymous

    Anonymous - 2013-03-08

    On fedora 18 with 1.1.5 the files can be browsed but not transfered.

    mtp-detect

    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 7
    Attempting to connect device(s)
    libusb_detach_kernel_driver() failed, continuing anyway...: Success
    ignoring libusb_claim_interface() = -6PTP_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.

    lsusb

    Bus 001 Device 010: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-I9300 Phone [Galaxy S III], GT-P7500 [Galaxy Tab 10.1]

     
  • Anonymous

    Anonymous - 2014-08-27

    Same bug here. i9100, ubuntu 13.10
    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 62
    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
    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
    ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt
    Unable to open raw device 0
    OK.

     

Anonymous
Anonymous

Add attachments
Cancel