Menu

#1593 LIBMTP ERROR: couldn't parse extension samsung.com/devicestatus:0

1.1.10
closed
None
1
2021-05-23
2016-08-15
No

When I am connecting my Samsung Galaxy J7 (2016) I have the following error :

$ mtp-connect 
libmtp version: 1.1.10

Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
LIBMTP ERROR: couldnt parse extension samsung.com/devicestatus:0

The device is not showing up in my Thunar file manager also (probably because of the error above).

Discussion

  • Anonymous

    Anonymous - 2016-09-02

    I am getting the same error with Samsung Galaxy Note 4. Using Thunar on Debian Stretch (Debian Testing as of this writing). Also unable to use jmtpfs to mount it (I imagine it uses libmtp, hence the same error).

     
  • Marcus Meissner

    Marcus Meissner - 2016-09-04

    The expecation is that number is in MAJOR.MINOR format, just MAJOR seems invalid.

    The standard says "dewey decimal number", although i dont know dewey decimal format and googling did not help :/

    that error is harmless however, and should not hinder operation.

     
  • Anonymous

    Anonymous - 2016-09-04

    I am getting the same error on my Samsung Galaxy S6 on Arch Linux x64.

    libmtp version: 1.1.12

    Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
    LIBMTP ERROR: couldnt parse extension samsung.com/devicestatus:0

     
  • Anonymous

    Anonymous - 2016-09-05

    I am also getting this with my galaxy note 7.
    This same setup has been working perfectly with the galaxy note 5.

     
  • Marcus Meissner

    Marcus Meissner - 2016-09-05

    The ERROR should only be this line, it should work fine otherwise?

     
  • ross tyler

    ross tyler - 2016-10-15

    I am getting the same/similar on my Samsung Galaxy 6

    mtp-folders
    Attempting to connect device(s)
    Device 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
    mtp-folders: Successfully connected
    LIBMTP ERROR: couldnt parse extension samsung.com/devicestatus:1
    Friendly name: (NULL)
    Error 1: Get Storage information failed.
    Error 2: PTP Layer error 02ff: get_handles_recursively(): could not get object handles.
    Error 2: Error 02ff: PTP: I/O error
    Error 7: Found a bad handle, trying to ignore it.
    ... ^ ditto x ~100
    Error 2: PTP Layer error 02ff: Error getting friendlyname.
    Error 2: Error 02ff: PTP: I/O error
    LIBMTP_Get_Storage()
    : No such device
    OK.

    Running on Fedora 24 with latest from official repos

    rpm -qa | grep libmtp
    libmtp-examples-1.1.11-1.fc24.x86_64
    libmtp-devel-1.1.11-1.fc24.x86_64
    libmtp-1.1.11-1.fc24.x86_64

    I don't know what to expect from the libmtp-examples (e.g. mtp-folders) but this seems wrong.
    I first noticed the problem shortly after a phone update from AT&T.
    My simple-mtpfs usage stopped working.
    I created a simple-mtpfs issue:

    https://github.com/phatina/simple-mtpfs/issues/48

    I downloaded the simple-mtpfs code and stepped through it until

    https://github.com/phatina/simple-mtpfs/blob/master/src/simple-mtpfs-mtp-device.cpp#L158

    which returns 0 after complaining

    LIBMTP ERROR: couldnt parse extension samsung.com/devicestatus:1

     
  • Anonymous

    Anonymous - 2016-10-23

    I also have this problem, but only with Galaxy S7 (SM-G930F). On the same machine, using the same USB cable plugged to the same port I cannot mount S7 via simple-mtpfs, whereas completly the same procedure works with old S4.
    Only plugging the S7 (without any command) gives the following error:

    gvfsd[1813]: PTP: reading event an error 0x02ff occurredDevice 0 (VID=04e8 and PID=6860) is a Samsung Galaxy models (MTP).
    gvfsd[1813]: LIBMTP ERROR: couldnt parse extension samsung.com/devicestatus:0
    

    My configuration:

    Galaxy S7 (SM-G930F), Android 6.0.1, kernel 3.18.14-8888212
    
    # uname -r
    4.7.9-200.fc24.x86_64
    
    # rpm -qa | grep mtp
    libmtp-1.1.11-1.fc24.x86_64
    simple-mtpfs-0.2-6.fc24.x86_64
    gvfs-mtp-1.28.3-1.fc24.x86_64
    
    # rpm -qa | grep fuse
    glusterfs-fuse-3.8.5-1.fc24.x86_64
    gvfs-fuse-1.28.3-1.fc24.x86_64
    fuse-2.9.7-1.fc24.x86_64
    fuse-libs-2.9.7-1.fc24.x86_64
    

    By the way, apart from this porblem while mounting phone to folder, I can easily access its data via file browser, because it's visible in Nautilius.

    The more detailed description of my attempts could be found at the following two stackexchange questions:

    http://unix.stackexchange.com/questions/317694/mount-samsung-galaxy-s7-using-simple-mtpfs

    http://android.stackexchange.com/questions/160439/cannot-mount-galaxy-s7-with-simple-mtpfs-with-s4-it-used-to-work-fine

    Adam Przedniczek

     
  • Anonymous

    Anonymous - 2016-10-24

    I get this with my Samsung S7 Edge.

     
  • Marcus Meissner

    Marcus Meissner - 2016-10-24

    is the mtp access enabled on the S7? (did you confirm the dialog that pops up on the device)?

     
  • ross tyler

    ross tyler - 2016-10-24
     
  • Marcus Meissner

    Marcus Meissner - 2016-10-24
    • status: open --> closed
    • assigned_to: Marcus Meissner
     
  • Marcus Meissner

    Marcus Meissner - 2016-10-24

    i rewrote the logic a bit for next release 1.1.13, it will not display this useless error.

     
  • Anonymous

    Anonymous - 2017-02-06

    The message has indeed disappeared, but I'm still getting Input/output errors after attempting to mount with jmtpfs (which uses libmtp @ 0e78a1e

     
  • Anonymous

    Anonymous - 2017-03-15

    any solution? same error and YES I did click 'Allow' on pop up phone message (S7)

     
  • Anonymous

    Anonymous - 2017-03-28

    Marcus, do you have a forecast release data for 1.1.13?

     
  • Anonymous

    Anonymous - 2017-03-30

    Maybe you didnt add your regular user to the uucp group? My system arch linux, libmtp version 1.1.12
    then try: # mtp-detect

     

Anonymous
Anonymous

Add attachments
Cancel