Fremantle Unsupported Bluetooth profiles

(use <code> and <source>, links)
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))))
 
(24 intermediate revisions not shown)
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.
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) ==
+
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 <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>
+
-
 
+
-
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]].
+
-
 
+
-
You can use the same instructions for a bluetooth mouse. The trackwheel will only zoom in & out for the browser (Firefox). Mouse sensitivity is too high, xorg.conf modifications should make it work properly.
+
-
 
+
-
Note that this will conflict with SIXAXIS(TM) Support, the controller will not connect to the device until this is reversed.
+
== PAN ==
== PAN ==
Line 61: Line 25:
If you want to connect to another device over PAN, see [[Bluetooth PAN]] for more detailed information.
If you want to connect to another device over PAN, see [[Bluetooth PAN]] for more detailed information.
-
== Phone Book Access Profile (PBAP) ==
+
== Phone Book Access Profile (PBAP) and IrMC Sync ==
-
 
+
-
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 <code>/usr/share/dbus-1/services/obexd.service</code>. If this is not enough, the ebook driver might need some tweaking for Fremantle.
+
 +
{{main|Bluetooth PBAP}}
[[Category:Users]]
[[Category: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"