Fremantle Unsupported Bluetooth profiles
m (Protected "Fremantle Unsupported Bluetooth profiles": Excessive vandalism ([edit=autoconfirmed] (expires 18:49, 16 December 2018 (UTC)) [move=autoconfirmed] (expires 18:49, 16 December 2018 (UTC))))
 
(35 intermediate revisions not shown)
Line 1: Line 1:
-
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.  
+
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 ===
+
== 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.
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 ====
+
=== Example script ===
-
<pre>
+
<source lang="bash">
sdptool add --channel 1 DUN
sdptool add --channel 1 DUN
while true; do
while true; do
-
         rfcomm -S -- listen -1 1 /usr/bin/pnatd '{}'
+
         rfcomm -S --listen -1 1 /usr/bin/pnatd '{}'
         sleep 1
         sleep 1
done
done
-
</pre>
+
</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 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) ===
+
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]
-
Fremantle comes with the bluetoothd input plugin installed but disabled through /etc/bluetooth/main.conf
+
== PAN ==
-
As shown by Johan Hedberg at the maemo summit 2009:
+
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.
-
Your main.conf should look like:
+
If you want to connect to another device over PAN, see [[Bluetooth PAN]] for more detailed information.
-
<pre>
+
-
[General]
+
-
#List of plugins that should not be loaded on bluetoothd startup
+
== Phone Book Access Profile (PBAP) and IrMC Sync ==
-
DisablePlugins = network,input,hal
+
-
...
+
-
</pre>
+
-
With root rights change it to
+
{{main|Bluetooth PBAP}}
-
<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>
+
-
 
+
-
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
+
[[Category:Users]]
[[Category:Users]]
[[Category:Fremantle]]
[[Category:Fremantle]]
[[Category:Bluetooth]]
[[Category:Bluetooth]]
 +
[[Category:Power users]]

Latest revision as of 18:49, 16 December 2017

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

[edit] 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.

[edit] 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.

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]

[edit] 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.

[edit] Phone Book Access Profile (PBAP) and IrMC Sync

Main article: Bluetooth PBAP

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