Bluetooth, Linux and a Mobile

You will need the following software:

- Latest 2.4.21 Kernel.
- BlueZ Userland Applications.
- OpenOBEX.
- ObexSERVER.
- ussp-push.

Once again, you have to recompile your kernel. I'm assuming, you know how to do this. If not, there is enough help out there, just google a bit.

Just make sure you're going to enable the following options:

CONFIG_BLUEZ=m
CONFIG_BLUEZ_L2CAP=m
CONFIG_BLUEZ_SCO=m
CONFIG_BLUEZ_RFCOMM=m
CONFIG_BLUEZ_RFCOMM_TTY=y
CONFIG_BLUEZ_BNEP=m
CONFIG_BLUEZ_HCIUSB=m

The Bluetooth option in the USB Menu is not needed. Now add these aliases to your /etc/modules.conf:

alias net-pf-31 bluez
alias bt-proto-0 l2cap
alias bt-proto-2 sco
alias bt-proto-3 rfcomm

Also, you should check if the /dev/rfcomm0 device is existent. If not, do so:

# cd /dev && mknod rfcomm0 c 216 0 && mknod rfcomm1 c 216 1 && mknod ttyU0 c 208 0 && mknod ttyU1 c 208 1

After compiling, lilo'ing and rebooting, we're going to compile some userland apps and stuff. First of all, you will need the BlueZ and OpenOBEX sources.

Uncompress "bluez-1.1.tar.gz bluez-libs-2.4.tar.gz bluez-sdp-1.1.tar.gz bluez-utils-2.3.tar.gz openobex-1.0.0.tar.gz openobex-apps-1.0.0.tar.gz" and complete those two steps for every package:

# ./configure
# make install

Now, you should start hcid and sdpd...

# hcid
# sdpd

and so, we are just one step away from receiving files!

$ cd openobex-apps-1.0.0/src
$ wget http://www.frasunek.com/sources/unix/obexserver.c
$ cc -o obexserver obexserver.c libmisc.a -lopenobex
# chown root.root obexserver && cp obexserver /usr/local/bin
# sdptool add --channel=10 OPUSH
# ./obexserver

Just select some files and choose "Send via Bluetooth" on your phone After receiving, you will be able to find those files in /tmp on your PC.

Okay, now let's send some files to the phone! Get the ussp-push package (link above), uncompress it and edit "obex_main.c". We need to exchange line 221 with the following substitute:

Old line: custfunc.userdata = gt->userdata;
New line: custfunc.customdata = gt->userdata;

Now run 'make' and configure the RfCOMM channel with:

# rfcomm connect 1 "BID" 10 &

The "BID"-tag has to be replaced with your phone's Bluetooth ID. You can retrieve this number (looks like 00:60:57:xx:yy:zz) by executing

# hcitool scan

Now you can send files to your phone by running

# ussp-push /dev/rfcomm0 [local-filename] [remote-filename]

Have fun,

muesli