libmtp clarification about android-file-transfer-linux HOT 8 CLOSED

concretely, without libmtp:

$ groups dkwo 
dkwo : dkwo wheel audio plugdev users _seatd socklog
$ aft-mtp-mount ~/mnt 
connect failed: no MTP device found

while it mounts fine with it.

from android-file-transfer-linux.

No, AFTL has its own MTP implementation and does not use libmtp. My wild guess is that it contains udev rules to allow MTP devices to be readable by anyone or plugdev.

Try passing -v to aft-mtp-mount and check which devices it tries to open

from android-file-transfer-linux.

I see. Without libmtp:

$ lsusb | grep Pixel 
Bus 001 Device 015: ID 18d1:4ee1 Google Inc. Nexus/Pixel Device (MTP)
$ aft-mtp-mount -v mnt 
connect failed: no MTP device found
$ ls -lt /dev/bus/usb/001                                                
total 0
crw-rw-r-- 1 root root 189, 14 Dec 12 15:06 015
...(similar entries)

from android-file-transfer-linux.

ouch, probably not the best way of fixing that - try extract udev rules into separate package (and call it plugdev for instance).

Then the package will provide user group plugdev and register udev rules. Normally different udev/rules.d could have duplicated code (in case you have plugdev + libmtp installed together), it should just work

from android-file-transfer-linux.

by extract, you mean from libmtp? as I don't see any udev rules in aftl..

if so, then i'd split a subpackage libmtp-tools (containing the binaries) from libmtp (leaving here only usr/lib and udev rules) and make aftl depend on the latter?

from android-file-transfer-linux.

(the libmtp and libmtp-ng should not conflict anyway..)

from android-file-transfer-linux.

I only meant that this set of udev rules would be useful even without AFTL or libmtp. It's just sane to have an access to your pluggable usb device

from android-file-transfer-linux.

thanks for the clarifications. i'll try to split a subpkg of libmtp with just udev rules, and make aftl depend on this.

from android-file-transfer-linux.