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.
Latest revision Your text
Line 1: Line 1:
-
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.  
+
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.  
-
== 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 ====
-
<source lang="bash">
+
<pre>
sdptool add --channel 1 DUN
sdptool add --channel 1 DUN
while true; do
while true; do
Line 13: Line 13:
         sleep 1
         sleep 1
done
done
-
</source>
+
</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 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.
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) ===
-
== PAN ==
+
Fremantle comes with the bluetoothd input plugin installed but disabled through /etc/bluetooth/main.conf
-
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.
+
As shown by Johan Hedberg at the Maemo Summit 2009:
-
If you want to connect to another device over PAN, see [[Bluetooth PAN]] for more detailed information.
+
Your main.conf should look like:
 +
<pre>
 +
[General]
-
== Phone Book Access Profile (PBAP) and IrMC Sync ==
+
#List of plugins that should not be loaded on bluetoothd startup
 +
DisablePlugins = network,input,hal
 +
...
 +
</pre>
 +
 
 +
With root rights 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>
 +
 
 +
Then go to the bluetooth section pair the keyboard like any other bluetooth device and connect it.
 +
 
 +
You'll need to complete some extra steps to get the layout working properly.  See [[Fremantle Bluetooth Keyboard Layout]].
 +
 
 +
=== PAN ===
 +
 
 +
Fremantle comes with the bluetoothd network plugin installed but disabled through /etc/bluetooth/main.conf
 +
 
 +
=== Phone Book Access Profile (PBAP) ===
 +
 
 +
Since Fremantle has Evolution Data Server as its contacts backend it might be possible to get some PBAP functionality by enabling PBAB support with the ebook driver in obexd. The obexd package might need to be recompiled for this (not 100% sure) and the --pbap commandline switch will need to be added to /usr/share/dbus-1/services/obexd.service. If this is not enough, the ebook driver might need some tweaking for Fremantle.
-
{{main|Bluetooth PBAP}}
 
[[Category:Users]]
[[Category:Users]]

Learn more about Contributing to the wiki.


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!


Cancel | Editing help (opens in new window)

Templates used on this page:

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