Difference between revisions of "MTP"

From ArchWiki
Jump to: navigation, search
m (reversed my last change (I'm not sure now if this should be removed))
(simplification and beautification of wikilinks (interactive))
(Tag: wiki-scripts)
 
(168 intermediate revisions by 66 users not shown)
Line 1: Line 1:
[[Category:Sound]]
+
[[Category:Storage]]
MTP is the "Media Transfer Protocol" and is used by many mp3 players (e.g. Creative Zen) and mobile phones (e.g. Android 3+ devices). It is part of the "Windows Media" Framework and has close relationship with Windows Media Player.
+
[[Category:Mobile devices]]
 +
[[fa:MTP]]
 +
[[ja:MTP]]
 +
[[ru:MTP]]
 +
[[zh-hans:MTP]]
 +
{{Related articles start}}
 +
{{Related|USB storage devices}}
 +
{{Related articles end}}
 +
[[Wikipedia:Media_Transfer_Protocol|MTP]], or the ''Media Transfer Protocol'', is a USB device class which is used by many mobile phones (all Windows Phone 7/8/10 devices, most newer Android devices) and media players (e.g. Creative Zen).
  
==Installation==
+
== Installation ==
MTP support is provided by [http://libmtp.sourceforge.net/ libmtp], [[pacman|installable]] with the {{Pkg|libmtp}} package from the [[official repositories]].
 
  
==Usage==
+
=== Functionality ===
After installation, you have several MTP tools available.
 
Upon connecting your MTP device, you use:
 
# mtp-detect
 
to see if your MTP device is detected.
 
  
To connect to your MTP device, you use:
+
Linux MTP support is provided by [[installing]] the {{Pkg|libmtp}} package. It can be installed on its own and used to access devices. However, a number of packages are available that use it as a dependency and add additional convenience (e.g. filemanager) functionalities and compatibility with particular device types - which includes improving transfer access speeds.
# mtp-connect
 
  
If connection is successful, you will be given several switch options in conjunction with {{ic|mtp-connect}} to access data on the device.
+
These packages to choose from all implement a [[Wikipedia:Filesystem in Userspace|Filesystem in Userspace]]:
  
There are also several stand alone commands you can use to access your MTP device such as,
+
* {{Pkg|mtpfs}}
{{Warning | Some commands may be harmful to your MTP device!!! }}
+
* {{AUR|jmtpfs}} - is reported to work well for newer Android 4+ devices
 +
* {{AUR|go-mtpfs-git}} - is reported to work well for newer Android 3+ devices
 +
* {{AUR|simple-mtpfs}}
 +
* {{Pkg|android-file-transfer}} - MTP client with minimalistic UI
  
  mtp-albumart        mtp-emptyfolders    mtp-getplaylist    mtp-reset          mtp-trexist
+
All of them aim at better functionality and performance over {{ic|libmtp}}. Since there are a lot of different USB devices, you might want to research first which one looks most suitable for yours.
  mtp-albums          mtp-files          mtp-hotplug        mtp-sendfile
+
 
  mtp-connect         mtp-folders        mtp-newfolder      mtp-sendtr
+
{{Warning|{{ic|libmtp}} does not handle newer Android devices well - hanging transfers and problems with remote file system browsing are very common, poor performance is expected with most devices. Furthermore, if you have a damaged USB cable, programs utilizing libmtp may crash or hang indefinitely until you disconnect the device. It is recommended to connect your device with the USB Mass Storage (if available), or using [[ADB]] (for example {{aur|adbfs-rootless-git}}) to transfer files, which performs better on most devices and supports additional Android-specific features (like installing APKs, managing packages on the device, backing up data or accessing the device's shell).}}
  mtp-delfile        mtp-format          mtp-newplaylist    mtp-thumb
+
{{Tip|It is recommended to reboot your computer after installing MTP related packages.}}
   mtp-detect         mtp-getfile        mtp-playlists      mtp-tracks
+
 
 +
=== Integration with file managers ===
 +
 
 +
To view the contents of your Android device's storage via MTP in your file manager, install the corresponding plugin:
 +
 
 +
* For file managers that use [[GVFS]] (GNOME Files), install {{Pkg|gvfs-mtp}} for MTP or {{Pkg|gvfs-gphoto2}} for PTP support.
 +
* For file managers that use KIO (KDE's Dolphin), MTP support is included in {{Pkg|kio-extras}} (dependency of dolphin).
 +
 
 +
After installing the required package, the device should show up in the file manager automatically and be accessible via an URL, for example {{ic|mtp://[usb:002,013]/}}.
 +
 
 +
== Usage ==
 +
 
 +
It might be required to create a mount-point directory first. The directory {{ic|~/mnt}} is used as an example below. Also do not forget to unlock your phone's screen before connecting it to the computer.
 +
 
 +
FUSE mounts can generally be unmounted using {{ic|fusermount -u ''mountpoint''}}.
 +
 
 +
=== libmtp ===
 +
 
 +
Run {{ic|mtp-detect}} to detect your device.
 +
 
 +
If an error is returned, make sure your user is in the see {{ic|uucp}} [[group]] and see [[#libmtp 2|troubleshooting libmtp]].
 +
 
 +
You can transfer files using the {{ic|mtp-connect}} command. Run {{ic|pacman -Ql libmtp}} to see the other commands provided by ''libmtp''.
 +
 
 +
=== simple-mtpfs ===
 +
 
 +
Run {{ic|simple-mtpfs -l}} to list detected devices.
 +
 
 +
To mount the first device in the list to {{ic|~/mnt}}, run {{ic|simple-mtpfs --device 1 ~/mnt}}.
 +
 
 +
=== jmtpfs ===
 +
 
 +
Mount device on {{ic|~/mnt}}:
 +
 
 +
$ jmtpfs ~/mnt
 +
 
 +
Make this cohere to the rest of Linux (use regular mount/umount commands) by doing two steps
 +
 
 +
$# ln -s <actual mount command's path/name>  <a name consistent with Linux's mount convention>
 +
$  ln -s /sbin/jmtpfs                        /sbin/mount.jmtpfs
 +
 
 +
add this line to /etc/fstab;
 +
 
 +
  #jmtpfs <mount path>        fuse nodev,allow_other,<other options>                            0    0
 +
  jmtpfs /home/sam/run/motog fuse nodev,allow_other,rw,user,noauto,noatime,uid=1000,gid=1000    0    0
 +
 
 +
Now mount the device and see if the options "took"
 +
 
 +
   $ mount /home/sam/run/motog
 +
  Device 0 (VID=22b8 and PID=2e82) is a Motorola Moto G (ID2).
 +
  Android device detected, assigning default bug flags
 +
  $ mount
 +
  ...
 +
  jmtpfs on /home/sam/run/motog type fuse.jmtpfs (rw,nosuid,nodev,noexec,noatime,user_id=1000,group_id=1000,allow_other,user=sam)
 +
 
 +
=== go-mtpfs ===
 +
 
 +
{{Note|Mounting with {{ic|go-mtpfs}} might fail if an external SD Card is present. If you try to access your device while having an SD card and go-mtpfs complains, try removing the SD card and mounting again.}}
 +
 
 +
Install {{Pkg|android-udev}}, which will allow you to edit {{ic|/etc/udev/rules.d/51-android.rules}} and apply to your {{ic|idVendor}} and {{ic|idProduct}}, which you can see after running ''mtp-detect''. To the end of the line, add your user {{ic|<nowiki>OWNER="<user>"</nowiki>}}.
 +
 
 +
Mount device on {{ic|~/mnt}}:
 +
 
 +
$ go-mtpfs ~/mnt
 +
 
 +
=== mtpfs ===
 +
 
 +
{{Note | The following is likely to not work and you might have to resort to [[Digital_Cameras#libgphoto2|gphoto2]] or a file manager with gvfs support like [[PCManFM]]. }}
 +
 
 +
First edit your {{ic|/etc/fuse.conf}} and uncomment the following line:
 +
user_allow_other
 +
 
 +
Mount your device on {{ic|~/mnt}}:
 +
$ mtpfs -o allow_other ~/mnt
 +
 
 +
=== Android File Transfer ===
 +
 
 +
;FUSE interface
 +
 
 +
Mount your device on {{ic|~/my-device}}:
 +
$ mkdir ~/my-device
 +
$ aft-mtp-mount ~/my-device
 +
 
 +
If you want album art to be displayed, it must be named {{ic|albumart.xxx}} and placed first in the destination folder. Then copy other files. Also, note that fuse could be 7-8 times slower than ui/cli file transfer.
 +
 
 +
;Qt user interface
 +
 
 +
Start the application, choose a destination folder and click any button on the toolbar. Available options are: ''Upload Album'', ''Upload Directory'' and ''Upload Files''. The latter two are self-explanatory. ''Upload album'' searches the source directory for album covers, and sets the best available cover.
 +
 
 +
=== Media players ===
 +
 
 +
You can also use your MTP device in music players such as Amarok. To achieve this, you might have to edit {{ic|/etc/udev/rules.d/51-android.rules}} (the MTP device used in the following example is a Galaxy Nexus).
 +
Run:
  
==Using media players==
 
You can also use your MTP device in music players such as Amarok. To do this you may have to edit {{ic|/etc/udev/rules.d/51-android.rules}} (the MTP device used in the following example is a Galaxy Nexus):
 
To do this run:
 
 
  $ lsusb
 
  $ lsusb
and look for your device, it will be something like:
+
 
 +
Search for your device. It should be something like that:
 
  Bus 003 Device 011: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-P7500 [Galaxy Tab 10.1]
 
  Bus 003 Device 011: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-P7500 [Galaxy Tab 10.1]
in which case the entry would be:
+
 
  SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0666"
+
And entry to {{ic|/etc/udev/rules.d/51-android.rules}} will be this:
Then, reload udev rules:
+
  SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0666", OWNER="[username]"
 +
 
 +
Also reload udev rules:
 
  # udevadm control --reload
 
  # udevadm control --reload
  
{{Note|After installing MTP you may have to reboot for your device to be recognised}}
+
=== gvfs-mtp ===
 +
 
 +
{{Merge|udev}}
 +
 
 +
The {{Pkg|gvfs-mtp}} is available in the official repositories.
 +
 
 +
With {{ic|lsusb}} you can get information about your device where Bus and Device numbers can be used with {{ic|gvfs-mtp}} and device ID for creating of an [[udev]] rule.
 +
Bus '''002''' Device '''018''': ID '''04b7''':'''88a9''' Compal Electronics, Inc.
 +
(...)
  
==mtpfs==
+
To see detected device with enabled MTP
Mtpfs is FUSE filesystem that supports reading and writing from any MTP device. Basically it allows you to mount your device as an external drive.
 
  
Mtpfs can be installed with the packge {{Pkg|mtpfs}}, available from the [[official repositories]].
+
Use ''gvfs-mount'':
*First edit your {{ic|/etc/fuse.conf}} and uncomment the following line:
 
user_allow_other
 
  
*To mount your device
+
{{hc|<NOWIKI>gvfs-mount -li | grep -e ^Volume -e activation_root</NOWIKI>|2=
$ mtpfs -o allow_other /media/YOURMOUNTPOINT
+
Volume(0): MT65xx Android Phone
*To unmount your device
+
  activation_root=mtp://[usb:'''002''','''018''']/
$ fusermount -u /media/YOURMOUNTPOINT
+
}}
*To unmount your device as root
 
# umount /media/YOURMOUNTPOINT
 
  
Also, you can put them into your ~/.bashrc:
+
Use ''lsusb'':
alias android-connect="mtpfs -o allow_other /media/YOURMOUNTPOINT"
 
alias android-disconnect="fusermount -u /media/YOURMOUNTPOINT"
 
Or, with sudo
 
alias android-disconnect="sudo umount -u /media/YOURMOUNTPOINT"
 
{{Note|if you want not be asked for password when using sudo, please refer to [[USB Storage Devices#Mounting USB devices]]}}
 
  
==jmtpfs==
+
{{hc|<NOWIKI>lsusb -v 2> /dev/null | grep -e Bus -e iInterface -e bInterfaceProtocol</NOWIKI>|
[http://research.jacquette.com/jmtpfs-exchanging-files-between-android-devices-and-linux/ jmtpfs] is a FUSE and libmtp based filesystem for accessing MTP (Media Transfer Protocol) devices. It was specifically designed for exchanging files between Linux systems and newer Android devices that support MTP but not USB Mass Storage.
+
(......
jmtpfs is available as {{aur|jmtpfs}} in the [[AUR]].
+
......)
 +
Bus 002 Device 018: ID 04b7:88a9 Compal Electronics, Inc.  
 +
      bInterfaceProtocol      0
 +
      iInterface              5 MTP
 +
(......
 +
......)
 +
}}
  
Use these commands to mount and unmount your device :
+
To mount all available connected MTP devices use inline script
$ jmtpfs ~/mtp
 
  
  $ fusermount -u ~/mtp
+
  gvfs-mount -li | awk -F= '{if(index($2,"mtp") == 1)system("gvfs-mount "$2)}'
  
==go-mtpfs==
+
To mount or dismount from a command with gvfs-mtp use Bus and Device numbers, e.g. to mount {{ic|gvfs-mount mtp://[usb:001,007]/}} and to unmount {{ic|gvfs-mount -u mtp://[usb:001,007]/}}. The mounted device will be available in a directory that begins with ''mtp:host='' and is located under ''/run/user/$UID/gvfs/''.
{{Note|Go-mtpfs gives a better performance while writing files to some devices than mtpfs/jmtpfs. Try it if you have slow speeds.}}
 
If the above instructions don't show any positive results one should try {{aur|go-mtpfs-git}} from the [[AUR]].
 
The following has been tested on a Samsung Galaxy Nexus GSM and Samsung Galaxy S 3 mini.
 
  
If you want do it simpler, install {{Pkg|go}}, {{Pkg|libmtp}} and {{Pkg|git}} from the [[official repositories]]. After that install {{AUR|go-mtpfs-git}} from the [[AUR]].
+
Disable automount of MTP devises with gvfs you will need to change value ''true'' to ''false'' for variable ''AutoMount'' that is located in {{ic|/usr/share/gvfs/mounts/mtp.mount}}.
  
 +
{{Note|The file managers can have own options for automount. On start they checking for all available mountable devices.}}
  
As in the section above install {{aur|android-udev}} which will provide you with "/etc/udev/rules.d/51-android.rules" edit it to apply to
+
If your device isn't showing up in the file manager then the {{Pkg|libmtp}} is missing a native support and is not currently available in the list of the [https://sourceforge.net/p/libmtp/code/ci/HEAD/tree/src/music-players.h supported devices]. If you will try to mount by using command line you may also get an error
your vendorID and productID, which you can see after running mtp-detect. To the end of the line add with a comma OWNER="yourusername". Save the file.
 
  
*Add yourself to the "fuse" group:
+
{{bc|1=Device 0 (VID=''XXXX'' and PID=''XXXX'') is UNKNOWN.
gpasswd -a [user] fuse
+
Please report this VID/PID and the device model to the libmtp development team}}
  
*If the group "fuse" doesn't exist create it with:
+
The workaround to make it shown in the file manager is to write an [[udev]] rule for the device but it is no guaranty that you will be able to mount it with by using MTP connection.
groupadd fuse
 
  
Logout or reboot to apply these changes.  
+
Use ID number that represents by pattern '''vendorId''':'''productID''',e.g. '''04b7''':'''88a9''', and make an udev rule by creating a configuration file
  
*To create a mount point called "Android" issue the following commands:
+
{{hc|/etc/udev/rules.d/51-android.rules|<NOWIKI>
mkdir Android
+
SUBSYSTEM=="usb", ATTR{idVendor}=="04b7", ATTR{idProduct}=="88a9", MODE="0660", GROUP="uucp", ENV{ID_MTP_DEVICE}="1", SYMLINK+="libmtp"</NOWIKI>
 +
}}
 +
Reload the udev rules.
  
*To mount your phone use:
+
  # udevadm control --reload
  go-mtpfs Android
 
  
*To unmount your phone:
+
The file managers with support for [[gvfs]] will be able to show MTP devices and mount them if supported by {{Pkg|libmtp}} but if has no support and cannot be opened then change settings in the phone to PTP and install {{Pkg|gvfs-gphoto2}} for having access at least to the photos, command line mounting of PTP is a little similar to mounting of the MTP devices: {{ic|gvfs-mount gphoto2://[usb:002,019]/}}.
fusermount -u Android
 
  
You can create a .bashrc alias as in the example above for easier use.
+
{{Note|If you getting limited access to the device and cannot use standard commands from command line such as e.g. {{ic|cp}},{{ic|ls}} then look for [[gvfs]] own alternatives, {{ic|ls -1 /usr/bin/gvfs-*}}.}}
  
==gvfs-mtp==
+
== Troubleshooting ==
  
Philip Langdale is has implemented native MTP support for gvfs. The weaknesses of gphoto2 and mtpfs are listed in his [http://intr.overt.org/blog/?p=153 blog post].
+
=== libmtp ===
*The native mtp implementation for gvfs [https://bugzilla.gnome.org/show_bug.cgi?id=666195 has been merged upstream] and has been released in gvfs [http://git.gnome.org/browse/gvfs/commit/?id=d6c8e3a4910ee2c5968886328ebe9456b445796b 1.15.2]. You can grab the stable gvfs-mtp package from extra, when gvfs 1.16 will be released in the stable Arch repos.
 
  
*Devices will have gvfs paths like this
+
==== Unable to enumerate USB device ====
gvfs-ls mtp://[usb:002,013]/
+
{{Deletion|This should be an old kernel bug, and should have been fixed already. There is no bug report to confirm though.}}
 +
{{Merge||Unrelated to MTP, perhaps suited for [[USB storage devices]]}}
  
==simple-mtpfs==
+
If you see a message like this in system log ({{ic|journalctl}})
  
This is another FUSE filesystem for MTP devices. You may find this to be more reliable than {{Pkg|mtpfs}}. {{aur|simple-mtpfs}} is available in the AUR or can be built from source. Remember '''do not''' run the following commands as root.
+
  usb usb4-port2: unable to enumerate USB device
  
* To list MTP devices run
+
You can try following temporary [https://bbs.archlinux.org/viewtopic.php?pid=1087323#p1087323 workaround]
  simple-mtpfs --list-devices
 
  
* To mount a MTP devices (in this example device 0) run
+
  # modprobe -vr uhci_hcd
simple-mtpfs /path/to/your/mount/point
+
  # modprobe -va ohci_hcd
 +
  # modprobe -va uhci_hcd
  
* To un mount run
+
If it works you should create {{ic|/etc/modprobe.d/usb_hci_order.conf}} with following content
  fusermount -u /path/to/your/mount/point
 
  
==KDE MTP KIO Slave==
+
  # create a dependency on ohci for uhci, which fixes problems
There is a MTP KIO Slave built upon libmtp availiable as package {{Pkg|kio-mtp}}.
+
  # with external usb devices not showing up
 +
  #
 +
  softdep uhci_hcd pre: ohci_hcd
  
Using KIO makes file access in KDE seamless, in principle any KDE application would be able read/write files on the device.
+
=== jmtpfs ===
  
===Usage===
+
==== Input/output error upon first access ====
The device will be available under the path mtp:/
 
  
===Workaround if the KDE device actions doesn't work===
+
Symptoms: jmtpfs successfully mounts, but as soon as one attempts to access files on the device (e.g. via {{ic|ls}}), an error is reported:
If you are not able to use the action "Open with File Manager", you may work around this problem by editing the file /usr/share/apps/solid/actions/solid_mtp.desktop
 
  
Change the line
+
  cannot access <mount-point>: Input/output error
Exec=kioclient exec mtp:udi=%i/
 
To
 
Exec=dolphin "mtp:/"
 
  
==GNOME gMTP==
+
This appears to be a security feature: MTP does not work when the phone is locked by the lockscreen.  Unlock the phone and it should work again as long as the cord remains connected.
gMTP is a native Gnome application used for MTP access.
 
  
{{aur|gmtp}} is currently located in the [[AUR]] .
+
=== kio-mtp ===
  
==Workarounds for Android==
+
If you are not able to use the action "Open with File Manager", you may work around this problem by editing the file {{ic|/usr/share/apps/solid/actions/solid_mtp.desktop}}.
MTP is still buggy and may crash despite the best efforts of developers. The following are alternatives:
 
* AirDroid - an Android app to access files via your web browser.
 
* FTP client on Android - If you run a local FTP server on Arch (such as [[Vsftp]]), there are many FTP clients available on the Play Store which will give read/ write access to your device's files.
 
* FTP Server on Android. Note: since FTP client using passive transfer (server connect to client) do not forget to disable firewall or adding rules for allowing FTP server connect to your PC.
 
** Ftp Server (by The Olive Tree) app in Play Store acts as FTP server on Android and allows RW access to pretty much all your storage.
 
*** Pro: Doesn't require root and just works!
 
*** Cons: Doesn't work with tethering network.
 
** FTPServer (by Andreas Liebig) - Just work.
 
* SSH server on Android.
 
** For example, SSHelper, available on the Play Store, just works without requiring root access. Assuming SSHelper is listening on port 20 and the phone's IP address is 192.168.0.20, the following command will synchronise a local directory with the external SD card of the Android device:
 
  rsync --rsh="ssh -p 20" --modify-window=1  ~/local_files  192.168.0.20:/mnt/extSdCard/remote_files
 
Note the {{ic|--modify-window}} option, which is often used when rsyncing to a FAT filesystem (such as the one used by Android devices for their internal memory and external SD cards).
 
* Samba - an Android app to share your SD card as a windows fileshare. Pros: Your desktop apps work as before (since the SD card appears as a windows fileshare). Cons: you need to root your phone.
 
==Security features on android==
 
If you use android 4.x please unlock phone (screen unlock) and then connect phone to USB.
 
  
If you not unlock you have in KDE "No Storages found. Maybe you need to unlock your device?" or error 02fe in console.
+
Change the line {{ic|1=Exec=kioclient exec mtp:udi=%i/}} to {{ic|1=Exec=dolphin "mtp:/"}}.

Latest revision as of 19:30, 7 August 2017

Related articles

MTP, or the Media Transfer Protocol, is a USB device class which is used by many mobile phones (all Windows Phone 7/8/10 devices, most newer Android devices) and media players (e.g. Creative Zen).

Installation

Functionality

Linux MTP support is provided by installing the libmtp package. It can be installed on its own and used to access devices. However, a number of packages are available that use it as a dependency and add additional convenience (e.g. filemanager) functionalities and compatibility with particular device types - which includes improving transfer access speeds.

These packages to choose from all implement a Filesystem in Userspace:

All of them aim at better functionality and performance over libmtp. Since there are a lot of different USB devices, you might want to research first which one looks most suitable for yours.

Warning: libmtp does not handle newer Android devices well - hanging transfers and problems with remote file system browsing are very common, poor performance is expected with most devices. Furthermore, if you have a damaged USB cable, programs utilizing libmtp may crash or hang indefinitely until you disconnect the device. It is recommended to connect your device with the USB Mass Storage (if available), or using ADB (for example adbfs-rootless-gitAUR) to transfer files, which performs better on most devices and supports additional Android-specific features (like installing APKs, managing packages on the device, backing up data or accessing the device's shell).
Tip: It is recommended to reboot your computer after installing MTP related packages.

Integration with file managers

To view the contents of your Android device's storage via MTP in your file manager, install the corresponding plugin:

  • For file managers that use GVFS (GNOME Files), install gvfs-mtp for MTP or gvfs-gphoto2 for PTP support.
  • For file managers that use KIO (KDE's Dolphin), MTP support is included in kio-extras (dependency of dolphin).

After installing the required package, the device should show up in the file manager automatically and be accessible via an URL, for example mtp://[usb:002,013]/.

Usage

It might be required to create a mount-point directory first. The directory ~/mnt is used as an example below. Also do not forget to unlock your phone's screen before connecting it to the computer.

FUSE mounts can generally be unmounted using fusermount -u mountpoint.

libmtp

Run mtp-detect to detect your device.

If an error is returned, make sure your user is in the see uucp group and see troubleshooting libmtp.

You can transfer files using the mtp-connect command. Run pacman -Ql libmtp to see the other commands provided by libmtp.

simple-mtpfs

Run simple-mtpfs -l to list detected devices.

To mount the first device in the list to ~/mnt, run simple-mtpfs --device 1 ~/mnt.

jmtpfs

Mount device on ~/mnt:

$ jmtpfs ~/mnt

Make this cohere to the rest of Linux (use regular mount/umount commands) by doing two steps

$# ln -s <actual mount command's path/name>  <a name consistent with Linux's mount convention>
$  ln -s /sbin/jmtpfs                        /sbin/mount.jmtpfs

add this line to /etc/fstab;

 #jmtpfs <mount path>        fuse nodev,allow_other,<other options>                             0    0
  jmtpfs /home/sam/run/motog fuse nodev,allow_other,rw,user,noauto,noatime,uid=1000,gid=1000    0    0

Now mount the device and see if the options "took"

 $ mount /home/sam/run/motog
 Device 0 (VID=22b8 and PID=2e82) is a Motorola Moto G (ID2).
 Android device detected, assigning default bug flags
 $ mount 
  ...
  jmtpfs on /home/sam/run/motog type fuse.jmtpfs (rw,nosuid,nodev,noexec,noatime,user_id=1000,group_id=1000,allow_other,user=sam)

go-mtpfs

Note: Mounting with go-mtpfs might fail if an external SD Card is present. If you try to access your device while having an SD card and go-mtpfs complains, try removing the SD card and mounting again.

Install android-udev, which will allow you to edit /etc/udev/rules.d/51-android.rules and apply to your idVendor and idProduct, which you can see after running mtp-detect. To the end of the line, add your user OWNER="<user>".

Mount device on ~/mnt:

$ go-mtpfs ~/mnt

mtpfs

Note: The following is likely to not work and you might have to resort to gphoto2 or a file manager with gvfs support like PCManFM.

First edit your /etc/fuse.conf and uncomment the following line:

user_allow_other

Mount your device on ~/mnt:

$ mtpfs -o allow_other ~/mnt

Android File Transfer

FUSE interface

Mount your device on ~/my-device:

$ mkdir ~/my-device
$ aft-mtp-mount ~/my-device

If you want album art to be displayed, it must be named albumart.xxx and placed first in the destination folder. Then copy other files. Also, note that fuse could be 7-8 times slower than ui/cli file transfer.

Qt user interface

Start the application, choose a destination folder and click any button on the toolbar. Available options are: Upload Album, Upload Directory and Upload Files. The latter two are self-explanatory. Upload album searches the source directory for album covers, and sets the best available cover.

Media players

You can also use your MTP device in music players such as Amarok. To achieve this, you might have to edit /etc/udev/rules.d/51-android.rules (the MTP device used in the following example is a Galaxy Nexus). Run:

$ lsusb

Search for your device. It should be something like that:

Bus 003 Device 011: ID 04e8:6860 Samsung Electronics Co., Ltd GT-I9100 Phone [Galaxy S II], GT-P7500 [Galaxy Tab 10.1]

And entry to /etc/udev/rules.d/51-android.rules will be this:

SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0666", OWNER="[username]"

Also reload udev rules:

# udevadm control --reload

gvfs-mtp

Merge-arrows-2.pngThis article or section is a candidate for merging with udev.Merge-arrows-2.png

Notes: please use the second argument of the template to provide more detailed indications. (Discuss in Talk:MTP#)

The gvfs-mtp is available in the official repositories.

With lsusb you can get information about your device where Bus and Device numbers can be used with gvfs-mtp and device ID for creating of an udev rule.

Bus 002 Device 018: ID 04b7:88a9 Compal Electronics, Inc.
(...)

To see detected device with enabled MTP

Use gvfs-mount:

gvfs-mount -li | grep -e ^Volume -e activation_root
Volume(0): MT65xx Android Phone
  activation_root=mtp://[usb:002,018]/

Use lsusb:

lsusb -v 2> /dev/null | grep -e Bus -e iInterface -e bInterfaceProtocol
(......
......)
Bus 002 Device 018: ID 04b7:88a9 Compal Electronics, Inc. 
      bInterfaceProtocol      0 
      iInterface              5 MTP
(......
......)

To mount all available connected MTP devices use inline script

gvfs-mount -li | awk -F= '{if(index($2,"mtp") == 1)system("gvfs-mount "$2)}'

To mount or dismount from a command with gvfs-mtp use Bus and Device numbers, e.g. to mount gvfs-mount mtp://[usb:001,007]/ and to unmount gvfs-mount -u mtp://[usb:001,007]/. The mounted device will be available in a directory that begins with mtp:host= and is located under /run/user/$UID/gvfs/.

Disable automount of MTP devises with gvfs you will need to change value true to false for variable AutoMount that is located in /usr/share/gvfs/mounts/mtp.mount.

Note: The file managers can have own options for automount. On start they checking for all available mountable devices.

If your device isn't showing up in the file manager then the libmtp is missing a native support and is not currently available in the list of the supported devices. If you will try to mount by using command line you may also get an error

Device 0 (VID=XXXX and PID=XXXX) is UNKNOWN.
Please report this VID/PID and the device model to the libmtp development team

The workaround to make it shown in the file manager is to write an udev rule for the device but it is no guaranty that you will be able to mount it with by using MTP connection.

Use ID number that represents by pattern vendorId:productID,e.g. 04b7:88a9, and make an udev rule by creating a configuration file

/etc/udev/rules.d/51-android.rules
SUBSYSTEM=="usb", ATTR{idVendor}=="04b7", ATTR{idProduct}=="88a9", MODE="0660", GROUP="uucp", ENV{ID_MTP_DEVICE}="1", SYMLINK+="libmtp"

Reload the udev rules.

# udevadm control --reload

The file managers with support for gvfs will be able to show MTP devices and mount them if supported by libmtp but if has no support and cannot be opened then change settings in the phone to PTP and install gvfs-gphoto2 for having access at least to the photos, command line mounting of PTP is a little similar to mounting of the MTP devices: gvfs-mount gphoto2://[usb:002,019]/.

Note: If you getting limited access to the device and cannot use standard commands from command line such as e.g. cp,ls then look for gvfs own alternatives, ls -1 /usr/bin/gvfs-*.

Troubleshooting

libmtp

Unable to enumerate USB device

Tango-edit-cut.pngThis section is being considered for removal.Tango-edit-cut.png

Reason: This should be an old kernel bug, and should have been fixed already. There is no bug report to confirm though. (Discuss in Talk:MTP#)

Merge-arrows-2.pngThis article or section is a candidate for merging with [[]].Merge-arrows-2.png

Notes: Unrelated to MTP, perhaps suited for USB storage devices (Discuss in Talk:MTP#)

If you see a message like this in system log (journalctl)

 usb usb4-port2: unable to enumerate USB device

You can try following temporary workaround

 # modprobe -vr uhci_hcd
 # modprobe -va ohci_hcd
 # modprobe -va uhci_hcd

If it works you should create /etc/modprobe.d/usb_hci_order.conf with following content

 # create a dependency on ohci for uhci, which fixes problems
 # with external usb devices not showing up
 #
 softdep uhci_hcd pre: ohci_hcd

jmtpfs

Input/output error upon first access

Symptoms: jmtpfs successfully mounts, but as soon as one attempts to access files on the device (e.g. via ls), an error is reported:

 cannot access <mount-point>: Input/output error

This appears to be a security feature: MTP does not work when the phone is locked by the lockscreen. Unlock the phone and it should work again as long as the cord remains connected.

kio-mtp

If you are not able to use the action "Open with File Manager", you may work around this problem by editing the file /usr/share/apps/solid/actions/solid_mtp.desktop.

Change the line Exec=kioclient exec mtp:udi=%i/ to Exec=dolphin "mtp:/".