Fremantle Unsupported Bluetooth profiles

There are several Bluetooth profiles officially missing/unsupported in Fremantle that are however supported by the upstream BlueZ project or can be made to work with some simple hacks.

Contents

DUN server

There's a tool called pnatd (short for PhoNet AT Daemon) which can act as a proxy between the cellular modem PhoNet interface and a TTY device.

Example script 

sdptool add --channel 1 DUN
while true; do
        rfcomm -S --listen -1 1 /usr/bin/pnatd '{}'
        sleep 1
done

There is one known issue: Most likely due to a bug in the way that the Bluetooth and TTY subsystems in the kernel interact in this use case data can be lost if the DUN client starts immediately sending AT commands when the connection is created. This can e.g. be worked around by adding a 1 second delay to the chat script on the client side.

bad credit loans [url=http://payday100loans24online.com/]payday loan[/url] online loans <a href="http://payday100loans24online.com/"> loans online</a>

PAN

Fremantle comes with the bluetoothd network plugin installed but disabled through /etc/bluetooth/main.conf - to use your N900 as a PAN server for other clients (such as N8x0) just enable this.

If you want to connect to another device over PAN, see Bluetooth PAN for more detailed information.

Phone Book Access Profile (PBAP) and IrMC Sync

Main article: Bluetooth PBAP

Retrieved from "http://wiki.maemo.org/Fremantle_Unsupported_Bluetooth_profiles"