Tag Info

New answers tagged

0

As far as I know, MTP works fine in Trusty. You can try this: Uncomment #user_allow_other in /etc/fuse.conf. Run lsusb and see your device's vendor ID. It will be something like 1d6b:0002. Add the following line to /lib/udev/rules.d/69-libmtp.rules. ATTR{idVendor}=="1d6b", ATTR{idProduct}=="0002", SYMLINK+="libmtp-%k", ENV{ID_MTP_DEVICE}="1", ...


0

Adding the following entries to /lib/udev/rules.d/69-libmtp.rules did the trick ATTR{idVendor}=="05c6", ATTR{idProduct}=="6764", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1", TAG+="uaccess" ATTR{idVendor}=="05c6", ATTR{idProduct}=="6765", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ...


0

You might want to try to install the following sudo apt-get install mtp-tools mtpfs Also I have read that plugging it into a usb 3.0 (blue) port is better.


1

There is a particular name property provided by the device through MTP, and this is the value you are seeing here. On a nexus device, it's always empty - so you see Unnamed Device. For other kinds of Android device, you may see a meaningful value here (I think Samsung set it). It's actually possible to set from the PC side using MTP but there's no way to ...


1

Setup this sudo apt-get install mtpfs sudo mkdir /media/onex sudo chmod 775 /media/onex sudo mtpfs -o allow_other /media/onex gedit /etc/udev/rules.d/51-android.rules and add the following line: SUBSYSTEM=="usb", SYSFS{idVendor}=="0bb4", MODE="0666" and then: sudo service udev restart Then add a user to the "disk" group (or whatever You want) make a ...


0

I realize that this is an old question, but I found it when I was searching for a method to use for 4.4.2 KitKat, so others may as well. The methods above worked great prior to Android KitKat 4.4.2. However, with the restriction on writing to the SD card by non-system apps, starting with KitKat, you're out of luck if you use an external SD card for your ...



Top 50 recent answers are included