You are not logged in.
Hey guys Im using KDE Ive been running into a lot of issues this past day or so trying to mount my android usb storage to a directory. When I run mtp-detect It returns
libmtp version: 1.1.18
Listing raw device(s)
Device 0 (VID=19d2 and PID=0307) is a ZTE V880E.
Found 1 device(s):
ZTE: V880E (19d2:0307) @ bus 3, dev 9
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
OK.So I tried running lsof for that bus and device and it seems the process keeping it busy is kiod5. Now Ive seen on a few posts here that kiod5 was the culprit and the fix was to just kill the process. I've tried this and it works (as in mtp-detect lists my device correctly) for about a second, and then just restarts with a new pid. Ive tried quickly mounting it with simple-mtpfs in this window before it restarts again and it does work for a few seconds and then kiod5 starts up and messes up the folder Im mounting.
I guess my question is, do I need kiod5 for anything else, and how can I keep it from interfering with mounting it in simple-mtpfs or disable the kiod5 process. Thanks.
Offline
Have you looked at android file transfer?
Offline
Have you looked at android file transfer?
I have, the same problem happens where it won't connect unless kiod5 is killed, but since it just starts up again its the same issue. Also it doesnt seem to have an option to mount to a directory when I got it to work for a second when kiod5 was disabled, Im trying to do that so I can access the folder in a wine program. But thanks for the suggestion.
Offline