Manually using Bluetooth - Revision history

Gabrys: /* Further reading */

2010-07-24T15:53:21Z

‎Further reading

PaulFertser: /* Prerequisites */ ophoned shouldn't be disabled

2010-04-15T08:51:08Z

‎Prerequisites: ophoned shouldn't be disabled

PaulFertser: /* Pair */ added a link to a simple agent in C

2010-01-24T18:34:01Z

‎Pair: added a link to a simple agent in C

PaulFertser: Whole page amended to remove `pidof bluetoothd` trick that no longer works

2010-01-09T13:17:08Z

Whole page amended to remove `pidof bluetoothd` trick that no longer works

Glenn: /* Further reading */ wiki

2009-12-12T11:55:31Z

‎Further reading: wiki

Martix: /* HID (Human Input Device) */

2009-11-06T19:12:37Z

‎HID (Human Input Device)

PaulFertser: /* HID (Human Input Device) */ experience with external dongle

2009-10-02T08:53:04Z

‎HID (Human Input Device): experience with external dongle

PaulFertser: /* HID (Human Input Device) */ added usage report

2009-09-10T10:15:52Z

‎HID (Human Input Device): added usage report

PaulFertser: /* HID (Human Input Device) */ uinput is unnecessary

2009-08-31T19:28:54Z

‎HID (Human Input Device): uinput is unnecessary

Any Key: /* List of known to work headsets */

2009-08-24T11:00:07Z

‎List of known to work headsets

@@ Line 900: / Line 900: @@
 *http://wiki.bluez.org/wiki/Audio#org.bluez.Audio
 *http://www.gentoo.org/doc/en/bluetooth-guide.xml
 {{Languages|Manually_using_Bluetooth}}
 [[Category:Bluetooth| ]]

← Older revision		Revision as of 08:51, 15 April 2010
Line 758:		Line 758:

	If you're using SHR unstable, you already has a correct state file and rules.yaml, so you can skip to the pairing section.		If you're using SHR unstable, you already has a correct state file and rules.yaml, so you can skip to the pairing section.
		+
		+	'''Some SHR versions have ophoned disabled. Make sure there's no disable=1 in [ophoned] section in /etc/frameworkd.conf'''

	==== State file ====		==== State file ====

@@ Line 58: / Line 58: @@
 '''Bluez4-compatible'''
-Pairing is nothing special, do it with simple-agent [http://git.kernel.org/?p=bluetooth/bluez.git;a=blob_plain;f=test/simple-agent;hb=HEAD] as described here or with any other agent you like as described in that agent's documentation.
+Pairing is nothing special, do it with simple-agent [http://git.kernel.org/?p=bluetooth/bluez.git;a=blob_plain;f=test/simple-agent;hb=HEAD] as described here or with any other agent you like as described in that agent's documentation. Bluez also comes with a simple command-line agent written in C, you can grab the source from [http://git.kernel.org/?p=bluetooth/bluez.git;a=blob_plain;f=test/agent.c;hb=HEAD] .
 Make sure the bluetooth chip is powered up (see below) and that bluetoothd is running.

@@ Line 33: / Line 33: @@
 '''Bluez4-compatible'''
-You can do it with [[OpenmokoFramework/mdbus]] or with <code>dbus-send</code>. To introspect with dbus-send you can employ something like this:
+You can do it with [[OpenmokoFramework/mdbus]] or with
-  dbus-send --system --dest=org.bluez --print-reply /org/bluez/`pidof bluetoothd`/hci0 org.freedesktop.DBus.Introspectable.Introspect
+<code>dbus-send</code>.
 The next example is how to make your device discoverable:
-  dbus-send --system --dest=org.bluez --print-reply /org/bluez/`pidof bluetoothd`/hci0 org.bluez.Adapter.SetProperty string:Discoverable variant:boolean:true
+  dbus-send --system --dest=org.bluez --print-reply $BTADAPTER org.bluez.Adapter.SetProperty string:Discoverable variant:boolean:true
 == Scanning for bluetooth devices ==
@@ Line 65: / Line 74: @@
 Then do
-  dbus-send --system --dest=org.bluez --print-reply /org/bluez/`pidof bluetoothd`/hci0/dev_00_18_00_00_C2_37 org.bluez.Input.Connect
+  dbus-send --system --dest=org.bluez --print-reply $BTADAPTER/dev_00_18_00_00_C2_37 org.bluez.Input.Connect
 Where <code>00_18_00_00_C2_37</code> is the address of your HID device. You can query for the device address with:
-  dbus-send --system --dest=org.bluez --print-reply /org/bluez/`pidof bluetoothd`/hci0 org.bluez.Adapter.ListDevices
+  dbus-send --system --dest=org.bluez --print-reply $BTADAPTER org.bluez.Adapter.ListDevices
 Enjoy.
@@ Line 355: / Line 364: @@
 You can enable or disable various roles by setting <code>Enable</code> property to true/false. Example for GN:
-  dbus-send --system --dest=org.bluez --print-reply /org/bluez/`pidof bluetoothd`/hci0 org.bluez.NetworkHub.SetProperty string:Enabled variant:boolean:true
+  dbus-send --system --dest=org.bluez --print-reply $BTADAPTER org.bluez.NetworkHub.SetProperty string:Enabled variant:boolean:true
 For PANU use org.bluez.NetworkPeer interface and for NAP use org.bluez.NetworkRouter.
 You might want to know UUID of GN for later use, so you need to read its properties:
-  dbus-send --system --dest=org.bluez --print-reply /org/bluez/`pidof bluetoothd`/hci0 org.bluez.NetworkHub.GetProperties
+  dbus-send --system --dest=org.bluez --print-reply $BTADAPTER org.bluez.NetworkHub.GetProperties
 To use NAP you'll need to create bridge device manually with
@@ Line 373: / Line 382: @@
 ==== Trust ====
 On GN/NAP role you need to ''trust'' the PANU peer:
-  dbus-send --system --dest=org.bluez --print-reply /org/bluez/`pidof bluetoothd`/hci0/dev_00_06_6E_17_27_E0 org.bluez.Device.SetProperty string:Trusted variant:boolean:true
+  dbus-send --system --dest=org.bluez --print-reply $BTADAPTER/dev_00_06_6E_17_27_E0 org.bluez.Device.SetProperty string:Trusted variant:boolean:true
 Where <code>00_06_6E_17_27_E0</code> is the MAC of peer.
@@ Line 388: / Line 397: @@
 bus = dbus.SystemBus()
 network = dbus.Interface(bus.get_object("org.bluez",
-                 "/org/bluez/"+sys.argv[1]+"/hci0/"+sys.argv[2]),
+                 sys.argv[1]),
                  "org.bluez.Network")
@@ Line 398: / Line 407: @@
 Then you do:
-  ./panu.py `pidof bluetoothd` dev_00_06_6E_17_27_E0
+  ./panu.py $BTADAPTER/dev_00_06_6E_17_27_E0
 Where <code>00_16_CE_E4_44_D5</code> is MAC of GN/NAP.
@@ Line 853: / Line 862: @@
 You might need to get the bluetooth headset connected manually on the beggining and also after suspend:
-  mdbus -s org.bluez /org/bluez/`pidof bluetoothd`/hci0/dev_xx_xx_xx_xx_xx_xx org.bluez.Headset.Connect
+  mdbus -s org.bluez $BTADAPTER/dev_xx_xx_xx_xx_xx_xx org.bluez.Headset.Connect
 where xx_xx_xx_xx_xx_xx is address of the device, for example:
-  mdbus -s org.bluez /org/bluez/`pidof bluetoothd`/hci0/dev_00_09_DD_31_92_98 org.bluez.Headset.Connect
+  mdbus -s org.bluez $BTADAPTER/dev_00_09_DD_31_92_98 org.bluez.Headset.Connect
 Hopefully, your bluetooth headset now works. Good luck!

@@ Line 886: / Line 886: @@
 == Further reading ==
-http://www.holtmann.org/papers/bluetooth/ols2006_slides.pdf
+*http://www.holtmann.org/papers/bluetooth/ols2006_slides.pdf
-http://wiki.bluez.org/wiki/Audio#org.bluez.Audio
+*http://wiki.bluez.org/wiki/Audio#org.bluez.Audio
-http://www.gentoo.org/doc/en/bluetooth-guide.xml
+*http://www.gentoo.org/doc/en/bluetooth-guide.xml
 {{Languages|Manually_using_Bluetooth}}
 [[Category:Bluetooth| ]]

← Older revision		Revision as of 19:12, 6 November 2009
Line 132:		Line 132:

	(See also [[Freedom_Slim_Keyboard]] for fso scripts which work with bluez4.)		(See also [[Freedom_Slim_Keyboard]] for fso scripts which work with bluez4.)
		+
		+	==== Mouse ====
		+	Edit /etc/X11/Xserver and replace ''tslib'' with ''/dev/input/mice''.
		+	<pre>
		+	"GTA02")
		+	if [ `screen_width` -gt 330 ] ; then
		+	DPI=285
		+	else
		+	DPI=140
		+	fi
		+	ARGS="$ARGS -dpi ${DPI} -screen ${SCREEN_SIZE} -mouse /dev/input/mice -root-ppm /usr/share/pixmaps/xsplash-vga.ppm vt1"
		+	XSERVER=/usr/bin/Xglamo
		+	;;
		+	</pre>

	==== Acting as HID device ====		==== Acting as HID device ====

@@ Line 73: / Line 73: @@
 Enjoy.
-''I've tested this with a BT mouse (no issues) and with SE cellphones that can pretend to be a mouse and keyboard. Both cellphones work without issues with my laptop using exactly the same procedure. The first phone seemed to work for a couple of seconds with FR too, after that the connection was lost. The second didn't work with FR at all. I'm going to try with an external BT dongle soon -- PaulFertser''
+''I've tested this with a BT mouse (no issues) and with SE cellphones that can pretend to be a mouse and keyboard. Both cellphones work without issues with my laptop using exactly the same procedure. The first phone seemed to work for a couple of seconds with FR too, after that the connection was lost. The second didn't work with FR at all.
 ==== Being able to use HID devices ====

← Older revision		Revision as of 10:15, 10 September 2009
Line 72:		Line 72:

	Enjoy.		Enjoy.
		+
		+	''I've tested this with a BT mouse (no issues) and with SE cellphones that can pretend to be a mouse and keyboard. Both cellphones work without issues with my laptop using exactly the same procedure. The first phone seemed to work for a couple of seconds with FR too, after that the connection was lost. The second didn't work with FR at all. I'm going to try with an external BT dongle soon -- PaulFertser''

	==== Being able to use HID devices ====		==== Being able to use HID devices ====

← Older revision		Revision as of 19:28, 31 August 2009
Line 70:		Line 70:

	dbus-send --system --dest=org.bluez --print-reply /org/bluez/`pidof bluetoothd`/hci0 org.bluez.Adapter.ListDevices		dbus-send --system --dest=org.bluez --print-reply /org/bluez/`pidof bluetoothd`/hci0 org.bluez.Adapter.ListDevices
−
−	~~Then modprobe the <code>uinput</code> kernel module:~~
−	~~modprobe uinput~~

	Enjoy.		Enjoy.

@@ Line 720: / Line 720: @@
 === List of known to work headsets ===
-no-name "Jabra", discovered as "Bluetooth headset" -- PaulFertser
+Moved to [[List_of_bluetooth_headsets]]
-−
-'''Plantronics Voyager 855''' -- DigitalPioneer
-−
-no-name '''BT Headset-12''' -- Vanous
-−
-'''Plantronics Explorer 220''' -- Vendion
-−
-'''Insmat (HS200?), a real cheap one''' -- Rakshasa
-−
-'''[http://www.qstarz.com/Products/Bluetooth%20Products/BH-Q360.html qstarz BT-Q360]''' -- Martin JaMa Jansa
-−
-'''Sony Ericsson HBH-300''' using SHR-U -- ChristW
-−
-'''Jabra BT125''' using FSO 5.5 -- Stargrave
 === List of non-working headsets ===