Menu

#1737 Doesn't mount Motorola Z Play detecting a Moto G as well.-

1.1.13
pending
None
1
2018-03-25
2017-10-28
Anonymous
No

Motorola Z Play with Debian Testing.-

$ mtp-detect
libmtp version: 1.1.13

Listing raw device(s)
Device 0 (VID=22b8 and PID=2e76) is a Motorola Moto G (ID1).
Found 1 device(s):
Motorola: Moto G (ID1) (22b8:2e76) @ bus 4, 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.


BTW, it gives 2 PID's depending on ADB is active in Options or not. Disabling it gives 2e82 like a Motorola G type and activating it 2e76.

Thanks.

Greetings.

Discussion

  • Marcus Meissner

    Marcus Meissner - 2017-11-04
    • status: open --> pending
    • assigned_to: Marcus Meissner
     
  • Marcus Meissner

    Marcus Meissner - 2017-11-04

    looks like a permission issue. is this the debian package or self-built?

    if self-built, you need to install the udev or hwdb ruleset same as debian does.

    you can cross check that by running mtp-detect as root, if that works its a permission issue.

     
  • Marcus Meissner

    Marcus Meissner - 2017-11-04
    • Group: unknown release (please set) --> 1.1.13
     
  • Anonymous

    Anonymous - 2017-11-04

    First of all, thanks for your answer.

    It's debian package.

    As root, the problem persists:

    mtp-detect
    libmtp version: 1.1.13

    Listing raw device(s)
    Device 0 (VID=22b8 and PID=2e76) is a Motorola Moto G (ID1).
    Found 1 device(s):
    Motorola: Moto G (ID1) (22b8:2e76) @ bus 4, dev 3

    Greetings.

     
  • Anonymous

    Anonymous - 2018-03-24

    Same issue here with Moto Z2 Play.
    It's not a permission issue, running mtp-detect as root:
    # mtp-detect
    libmtp version: 1.1.13

    Listing raw device(s)
    Device 0 (VID=22b8 and PID=2e82) is a Motorola Moto G (ID2).
    Found 1 device(s):
    Motorola: Moto G (ID2) (22b8:2e82) @ bus 1, dev 10
    Attempting to connect device(s)
    libusb_get_active_config_descriptor(1) failed: No data available
    no active configuration, trying to set configuration
    libusb_set_configuration() failed, continuing anyway...: Protocol error
    libusb_get_active_config_descriptor(2) failed: Protocol error
    LIBMTP PANIC: Unable to initialize device
    Unable to open raw device 0
    OK.

    openSUSE Leap 42.3. Kinda makes mtp on Linux useless...

    simple-mtpfs and mtpfs don't work either, probably for the same reason:
    # simple-mtpfs /tmp/f
    LIBMTP PANIC: Trying to dump the error stack of a NULL device!
    Exit 1
    # mtpfs /tmp/f
    Listing raw device(s)
    Device 0 (VID=22b8 and PID=2e82) is a Motorola Moto G (ID2).
    Found 1 device(s):
    Motorola: Moto G (ID2) (22b8:2e82) @ bus 1, dev 10
    Attempting to connect device
    libusb_get_active_config_descriptor(1) failed: No data available
    no active configuration, trying to set configuration
    libusb_set_configuration() failed, continuing anyway...: Protocol error
    libusb_get_active_config_descriptor(2) failed: Protocol error
    LIBMTP PANIC: Unable to initialize device
    Unable to open raw device 0
    Exit 1

    The device screen is NOT locked! And the device is a Motorola Moto Z2 Play, android 7.1.1.

     
  • Marcus Meissner

    Marcus Meissner - 2018-03-25

    one thing that could be is that gvfs *GNOME virtual fileysstem is blocking the device for usage in Nautilus

     

Anonymous
Anonymous

Add attachments
Cancel