Menu

#1680 HTC 10 Android 7 unsupported

1.1.13
closed
htc10 (1)
1
2017-06-03
2017-04-09
deviousway
No

incorrect name HTC One instead HTC10
and can't connect via mtp
stucked on

deviousway ~ $ mtp-detect 
libmtp version: 1.1.13

Listing raw device(s)
Device 0 (VID=0bb4 and PID=0f87) is a HTC HTC One (MTP+ADB+?).
   Found 1 device(s):
   HTC: HTC One (MTP+ADB+?) (0bb4:0f87) @ bus 3, dev 66
Attempting to connect device(s)
deviousway ~ $ mtp-connect 
libmtp version: 1.1.13

Device 0 (VID=0bb4 and PID=0f87) is a HTC HTC One (MTP+ADB+?).
deviousway ~ $ jmtpfs Media/mounts/mtp 
Device 0 (VID=0bb4 and PID=0f87) is a HTC HTC One (MTP+ADB+?).
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
terminate called after throwing an instance of 'MtpErrorCantOpenDevice'
  what():  Can't open device

sometime this output

deviousway ~ $ mtp-detect 
libmtp version: 1.1.13

Listing raw device(s)
Device 0 (VID=0bb4 and PID=0f87) is a HTC HTC One (MTP+ADB+?).
   Found 1 device(s):
   HTC: HTC One (MTP+ADB+?) (0bb4:0f87) @ bus 3, dev 68
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

Discussion

  • deviousway

    deviousway - 2017-04-09

    Also i tried to update
    /usr/lib/udev/rules.d/69-libmtp.rules

    ATTR{idVendor}=="0fce", ATTR{idProduct}=="0c93", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
    ATTR{idVendor}=="0fce", ATTR{idProduct}=="0f87", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
    ATTR{idVendor}=="0fce", ATTR{idProduct}=="0f86", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
    

    and

    /usr/lib/udev/rules.d/51-android.rules
    ATTR{idProduct}=="0c93", MODE="0660", GROUP="uucp", ENV{ID_MTP_DEVICE}="1", SYMLINK+="libmtp"
    ATTR{idProduct}=="0f87", MODE="0660", GROUP="uucp", ENV{ID_MTP_DEVICE}="1", SYMLINK+="libmtp"
    ATTR{idProduct}=="0f86", MODE="0660", GROUP="uucp", ENV{ID_MTP_DEVICE}="1", SYMLINK+="libmtp"

     

    Last edit: deviousway 2017-04-09
  • deviousway

    deviousway - 2017-04-09

    finally it works with custom

    /usr/lib/udev/rules.d/69-libmtp.rules
    /usr/lib/udev/rules.d/51-android.rules
    

    (The post above)
    i just forgot restart
    rules

    udevadm control --reload
    

    and unit

    systemctl restart  systemd-udevd
    

    So i think need to update some rules in next version

     
  • Marcus Meissner

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

    Marcus Meissner - 2017-04-10

    The device seems to be detected fine (the name is not so relevant, the USB id is).

    The libmtp udev rules should have been refreshed by the packager of your libmtp (your distribution).

    The android rules are catch-all vendor rules and not from libmtp.

    So who installed libmtp 1.1.13 also needed to install either udev rules or the hwdb files correctly

     
  • deviousway

    deviousway - 2017-04-10

    ok, got it , thank you for reply

     

    Last edit: deviousway 2017-04-10
  • Anonymous

    Anonymous - 2017-05-06

    Hi

    Same here. My HTC 10 gets detected as a HTC One.

    Bye

     
  • Anonymous

    Anonymous - 2017-05-06

    Here is the output of "mtp-detect".

     
  • Marcus Meissner

    Marcus Meissner - 2017-06-03
    • status: pending --> closed
     
  • Marcus Meissner

    Marcus Meissner - 2017-06-03

    I think it good.,

     

Anonymous
Anonymous

Add attachments
Cancel





Auth0 Logo