Fremantle Unsupported Bluetooth profiles
m (spelling)
Line 15: Line 15:
</pre>
</pre>
-
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 imediately 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.
+
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.
=== HID host (i.e. support for Bluetooth keyboards) ===
=== HID host (i.e. support for Bluetooth keyboards) ===
Line 21: Line 21:
Fremantle comes with the bluetoothd input plugin installed but disabled through /etc/bluetooth/main.conf
Fremantle comes with the bluetoothd input plugin installed but disabled through /etc/bluetooth/main.conf
-
As shown by Johan Hedberg at the maemo summit 2009:
+
As shown by Johan Hedberg at the Maemo Summit 2009:
Your main.conf should look like:
Your main.conf should look like:

Revision as of 22:02, 23 November 2009

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.

HID host (i.e. support for Bluetooth keyboards)

Fremantle comes with the bluetoothd input plugin installed but disabled through /etc/bluetooth/main.conf

As shown by Johan Hedberg at the Maemo Summit 2009:

Your main.conf should look like: 

[General]

#List of plugins that should not be loaded on bluetoothd startup
DisablePlugins = network,input,hal
...

With root rights change it to 

[General]

#List of plugins that should not be loaded on bluetoothd startup
DisablePlugins = network,hal
...

After saving, do a 

stop bluetoothd [RETURN]
start bluetoothd [RETURN]

Then go to the bluetooth section pair the keyboard like any other bluetooth device and connect it.

PAN

Fremantle comes with the bluetoothd network plugin installed but disabled through /etc/bluetooth/main.conf

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