From ArchWiki
Jump to navigation Jump to search

ObexFTP implements the OBEX protocol, used to transfer files. OBEX was adopted by Bluetooth and Android supports it since version 2.1.


Install the obexftpAUR package.

For a Tcl/Tk front-end install obextoolAUR.

For a GVFS client install gnome-vfs-obexftpAUR[broken link: package not found].


Obex Object Push

To send a file, find out the channel of the OBEX Push service:

$ sdptool search --bdaddr MAC_address OPUSH

Then send the file to that channel using the following command from [1]:

$ obexftp --nopath --noconn --uuid none --bluetooth MAC_address --channel channel --put file

Alternatively you could use ussp-pushAUR. To receive OBEX Pushes, there is ObexPushD, which however is no longer packaged for Arch.


If your device supports the Obex FTP service but you do not wish to mount the device you can transfer files to and from the device using the obexftp command.

To send a file to a device run the command:

$ obexftp -b MAC_address -p /path/to/file

To retrieve a file from a device run the command:

$ obexftp -b MAC_address -g filename
Note: Ensure that the file you are retrieving is in the device's exchange folder. If the file is in a subfolder of the exchange folder then provide the correct path in the command.


Another option, rather than using KDE or Gnome Bluetooth packages, is ObexFS which allows for the mounting of phones which are treated like any other filesystem.

Note: To use ObexFS, one needs a device that provides an ObexFTP service.

Mount supported phones by running:

$ obexfs -b MAC_address mountpoint

Once you have finished, to unmount the device use the command:

$ fusermount -u mountpoint

For more mounting options see http://dev.zuckschwerdt.org/openobex/wiki/ObexFs

Note: Ensure that the bluetooth device you are mounting is not set to mount read-only. You should be able to do this from the device's settings. If the device is mounted read-only you may encounter a permissions error when trying to transfer files to the device.