Hey guys,
MTP was working as soon as I got the device, but after I did every available update MTP appears to be broken. Changing the setting in settings->USB state appears to be currently just for show or something as after changing the option, nothing happens and restarting the settings app puts it back to None. Is there a fix coming for this anytime soon?
@fakeshell, sorry I left you hanging on the troubleshooting. I haven't even found the time to play with this some more or work on my old long running projects. I did grab it and test MTP once I saw your above post. It is working as expected now, thank you!
From a usability standpoint it would be nice to have a pop up with a drop down to select the behavior on usb plug
i don't have this issue myself, i was using mtp yesterday actually. maybe you can get in touch with us on telegram or matrix and one of us can diagnose it?
I can replicate this one.
MTP selected either before or after usb plug makes no difference, the computer never sees the FLX1
fakeshell said
i don't have this issue myself, i was using mtp yesterday actually. maybe you can get in touch with us on telegram or matrix and one of us can diagnose it?
If you still need this I would be willing and able to assist
Sword said
fakeshell said
i don't have this issue myself, i was using mtp yesterday actually. maybe you can get in touch with us on telegram or matrix and one of us can diagnose it?
If you still need this I would be willing and able to assist
hey. yes please do message me on telegram or matrix.
fakeshell 22/12/2024 6:54 am
Hey @jakes2me-com can we mark this as solved? It wad fixed up in mtp configfs last week.
I am selecting USB MTB but device is not recognized in Ubuntu with the following error:
jmtpfs Device 0 (VID=2717 and PID=ff20) is UNKNOWN in libmtp v1.1.21. Please report this VID/PID and the device model to the libmtp development team 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 Aborted
CaptainCook 14/02/2025 2:26 am
device identified as:
Bus 016 Device 005: ID 2717:ff20 Xiaomi Inc. FLX1
I also used the following but did not resolve the isse:
*******
mtp, lsusb... use the PCIID to identify the connected devices, in your case VID=18d1 , PID=4ee2 is known as Nexus/Pixel Device (MTP + debug)
To update the PCIID database list use: sudo update-pciids.
Other way to mount your device:
install jmtpfs:
sudo apt install jmtpfs
mkdir devicemnt
sudo chown $USER:$USER devicemnt
jmtpfs -o allow_other devicemnt/
ls devicemnt@captaincook it looks more or less like a client issue. i did all my testing with nautilus which automatically adds the device to the sidebar when mtp is available
@captaincook - I couldn't get MTP working at all in Arch. I tried gvfs-gphoto2, gvfs-mtp, go-mtpfs-git, jmtpfs, simple-mtpfs, mtpfs. android-file-transfer would give me the root dir but this appeared as empty. I even created a udev rule (Arch wiki) but this didn't help. I've now set up ssh (key) so won't be pursuing it further.
Edit: I have used mtpfs in the past with other phones (working) but this was a long time ago.
CaptainCook 14/02/2025 5:06 am
The error "MtpErrorCantOpenDevice" wouldn't that indicate that my desktop computer (client) can communicate with the device, but the device doesn't allow access?
