#1269 Device 0 (VID=2717 and PID=0360) is UNKNOWN.

[Anonymous]

Device 0 (VID=2717 and PID=0360) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team
Found 1 device(s):
2717:0360 @ bus 1, dev 6
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
ignoring libusb_claim_interface() = -6LIBMTP PANIC: failed to open session on second attempt
Unable to open raw device 0
OK.

its Xaomi Mi3w

[Marcus Meissner]

added to git, thanks!

[Ritesh Raj Sarraf]

Hi.. I have the same phone and I ran into some problem. Since I stumbled across this bug report, I'm hoping to ask you some questions. If you think I should create a new bug report, please let me know and I'll do so.

A couple of questions

• How does libmtp work? From the Linux namespace, when I monitor IO, I notice reads on the host machine, but no writes. That's because nothing is mounted on the host machine. So what all components are involved in MPT's IO Operation ?

• When doing large (2 GiB single file) I/O, things fall apart. It'd fail (and USB reset) half way through, which further would mean that one would have to redo the entire operation, because it is not allowing partial copy.

There's not much info on the host machine apart from the USB reset messages.

[Marcus Meissner]

1. libmtp talks via libusb to the Linux kernel usb interfaces , there is no filesystem in the middle.
   if you know windows, libusb would be talking to usbd.sys via DeviceIoControl

2. large file io failing ... it might timeout or not work, hard to say what the exact reason is here.

(but basically it is better to open a new bug or support ticket for new issues)