Question about file transfer to Android device
Šarūnas Burdulis
sarunas at math.dartmouth.edu
Mon Sep 22 19:33:15 UTC 2025
On 2025-09-22 1:54 PM, Bret Busby wrote:
> ...
> 2025-09-23 01:49:38 bret at bret-Precision-Tower-5810:~ > mtp-detect
> libmtp version: 1.1.19
>
> Listing raw device(s)
> Device 0 (VID=1f3a and PID=4ee1) is UNKNOWN in libmtp v1.1.19.
> Please report this VID/PID and the device model to the libmtp
> development team
> Found 1 device(s):
> 1f3a:4ee1 @ bus 3, dev 31
> Attempting to connect device(s)
> libusb_claim_interface() reports device is busy, likely in use by GVFS
> or KDE MTP device handling alreadyLIBMTP PANIC: Unable to initialize device
> Unable to open raw device 0
In README of libmtp (https://github.com/libmtp/libmtp) there is this,
which might be relevant in your case (among other information):
* mtp-* tools doesn't work because someone else is already hogging
the device
This is a common problem, the most common case could be that
gphoto2 (which can also talk PTP/MTP) is taking over the device
as soon as it's plugged in. Some distributions are configured that
way. Counter it like this:
gvfs-mount -s gphoto2
Then re-attach the device.
Sometimes some gvfs daemons are running on the
system and hogging the device, try stopping them
with something like these commands:
killall gvfs-mtp-volume-monitor
killall gvfs-gphoto2-volume-monitor
Then plug in the device and issue "mtp-detect" to figure out if
this may be the case.
--
Šarūnas Burdulis
Dartmouth Mathematics
https://math.dartmouth.edu/~sarunas
· https://useplaintext.email ·
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20250922/cbe3bbce/attachment.sig>
More information about the ubuntu-users
mailing list