Editing Fremantle Unsupported Bluetooth profiles

Warning: You are not logged in. Your IP address will be recorded in this page's edit history.

The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.

Learn more about Contributing to the wiki.

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

== 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 ===

<source lang="bash">
sdptool add --channel 1 DUN
while true; do
        rfcomm -S --listen -1 1 /usr/bin/pnatd '{}'
        sleep 1
done
</source>

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 and mice) ==

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

As shown by [[Maemo Summit 2009/Day 2#Hacking officially unsupported Bluetooth profiles to work in Fremantle|Johan Hedberg at the Maemo Summit 2009]]:

Your <code>main.conf</code> should look like:
<pre>
[General]

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

[[root access|As root]] change it to:
<pre>
[General]

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

After saving, do a
<pre>
stop bluetoothd [RETURN]
start bluetoothd [RETURN]
</pre>

Note that editing the bluetooth/main.conf file will conflict with SIXAXIS(TM) Support, the controller will not connect to the device until this is reversed.

=== Bluetooth Keyboard ===

Bluetooth keyboards should pair like any other bluetooth device.

You'll need to complete some extra steps to get the layout working properly. See [[Fremantle Bluetooth Keyboard Layout]].

The new application package "[http://maemo.org/packages/view/extkbd/ extkbd]" (currently in [[Extras-Testing]]) simplifies the usage of external Keyboards. See [http://talk.maemo.org/showthread.php?t=65577 this post] for some usage instructions.

=== Bluetooth Mouse ===

For a bluetooth mouse, extra steps are also required. By default, mouse sensitivity is unusably high. There are some modified versions of the evdev_drv.so driver (and bluetooth.ko module) available in [http://talk.maemo.org/showthread.php?t=57427 this talk.maemo.org thread] that will fix this problem.

Depending on the mouse, you may also need to install the [http://packages.debian.org/lenny-backports/bluez-compat bluez-compat] package from Debian and libxmuu1, then run "hidd --search" in order to pair. See [http://talk.maemo.org/showthread.php?p=737916#post737916 this post] for more details.

Similar to extkbd, the new application package [http://maemo.org/packages/view/extmou/ extmou] (also currently in [[Extras-Testing]]) simplifies this process.

----

== PAN ==

Fremantle comes with the bluetoothd network plugin installed but disabled through <code>/etc/bluetooth/main.conf</code> - 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 ==

[[Category:Users]]
[[Category:Fremantle]]
[[Category:Bluetooth]]
[[Category:Power users]]

Please note that all contributions to maemo.org wiki may be edited, altered, or removed by other contributors. If you do not want your writing to be edited mercilessly, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource (see maemo.org wiki:Copyrights for details). Do not submit copyrighted work without permission!

Summary:

Cancel | Editing help (opens in new window)

Templates used on this page:

Template:Main (view source) (protected)

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

Personal tools

Navigation

Views

Editing Fremantle Unsupported Bluetooth profiles

@@ Line 17: / Line 17: @@
 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.
-Nonetheless, two dimensions of time kind a plane of time, which has no beginning and no end and is not restricted to any single course.  have a look [url=http://www.connoisseurseafood.pl/chocolate-slim--gdzie-kupic-cena-apteka.htm]Chocolate Slim[/url] my blog [url=http://www.rcn-conti.lv/man-pride-cena-lietoana-latvij.htm]Man Pride[/url]
+== HID host (i.e. support for Bluetooth keyboards and mice) ==
+Fremantle comes with the bluetoothd input plugin installed but disabled through <code>/etc/bluetooth/main.conf</code>
+As shown by [[Maemo Summit 2009/Day 2#Hacking officially unsupported Bluetooth profiles to work in Fremantle|Johan Hedberg at the Maemo Summit 2009]]:
+Your <code>main.conf</code> should look like:
+<pre>
+[General]
+#List of plugins that should not be loaded on bluetoothd startup
+DisablePlugins = network,input,hal
+...
+</pre>
+[[root access|As root]] change it to:
+<pre>
+[General]
+#List of plugins that should not be loaded on bluetoothd startup
+DisablePlugins = network,hal
+...
+</pre>
+After saving, do a
+<pre>
+stop bluetoothd [RETURN]
+start bluetoothd [RETURN]
+</pre>
+Note that editing the bluetooth/main.conf file will conflict with SIXAXIS(TM) Support, the controller will not connect to the device until this is reversed.
+=== Bluetooth Keyboard ===
+Bluetooth keyboards should pair like any other bluetooth device.
+You'll need to complete some extra steps to get the layout working properly. See [[Fremantle Bluetooth Keyboard Layout]].
+The new application package "[http://maemo.org/packages/view/extkbd/ extkbd]" (currently in [[Extras-Testing]]) simplifies the usage of external Keyboards. See [http://talk.maemo.org/showthread.php?t=65577 this post] for some usage instructions.
+=== Bluetooth Mouse ===
+For a bluetooth mouse, extra steps are also required. By default, mouse sensitivity is unusably high. There are some modified versions of the evdev_drv.so driver (and bluetooth.ko module) available in [http://talk.maemo.org/showthread.php?t=57427 this talk.maemo.org thread] that will fix this problem.
+Depending on the mouse, you may also need to install the [http://packages.debian.org/lenny-backports/bluez-compat bluez-compat] package from Debian and libxmuu1, then run "hidd --search" in order to pair. See [http://talk.maemo.org/showthread.php?p=737916#post737916 this post] for more details.
+Similar to extkbd, the new application package [http://maemo.org/packages/view/extmou/ extmou] (also currently in [[Extras-Testing]]) simplifies this process.
+----
 == PAN ==