/[gentoo]/xml/htdocs/doc/en/bluetooth-guide.xml
Gentoo

Contents of /xml/htdocs/doc/en/bluetooth-guide.xml

Parent Directory Parent Directory | Revision Log Revision Log


Revision 1.11 - (show annotations) (download) (as text)
Tue Mar 13 00:40:27 2007 UTC (7 years, 5 months ago) by nightmorph
Branch: MAIN
Changes since 1.10: +4 -14 lines
File MIME type: application/xml
Remove all references to coldplug, bug 170679. All hail the udev-only era, for as long as it lasts. Don't like udev? Complain to greg_kh! udev is now The Gentoo Way(tm)

1 <?xml version='1.0' encoding="UTF-8"?>
2
3 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4 <!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml,v 1.10 2007/01/14 12:36:10 nightmorph Exp $ -->
5
6 <guide link="/doc/en/bluetooth-guide.xml">
7 <title>Gentoo Linux Bluetooth Guide</title>
8
9 <author title="Author">
10 <mail link="deathwing00@gentoo.org">Ioannis Aslanidis</mail>
11 </author>
12 <author title="Contributor">
13 <mail link="puggy@gentoo.org">Douglas Russell</mail>
14 </author>
15 <author title="Contributor">
16 <mail link="marcel@holtmann.org">Marcel Holtmann</mail>
17 </author>
18 <author title="Author">
19 <mail link="fox2mike@gentoo.org">Shyam Mani</mail>
20 </author>
21 <author title="Editor">
22 <mail link="rane@gentoo.org">Ɓukasz Damentko</mail>
23 </author>
24
25 <abstract>
26 This guide will explain how to successfully install a host Bluetooth device,
27 configure the kernel properly, explain all the possibilities that the Bluetooth
28 interconnection offers and how to have some fun with Bluetooth.
29 </abstract>
30
31 <!-- The content of this document is licensed under the CC-BY-SA license -->
32 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
33 <license/>
34
35 <version>1.7</version>
36 <date>2007-01-14</date>
37
38 <chapter id="introduction">
39 <title>Introduction</title>
40 <section>
41 <title>What is Bluetooth?</title>
42 <body>
43
44 <p>
45 Bluetooth is an industrial specification that provides users a way to connect
46 and exchange information between devices like personal computers, PDAs or
47 mobile phones. Using the Bluetooth technology, users can achieve wireless voice
48 and data transmission between devices at a low cost. Bluetooth also offers the
49 possibility to create small wireless LANs and to synchronize devices.
50 </p>
51
52 </body>
53 </section>
54 <section>
55 <title>About the content of this guide</title>
56 <body>
57
58 <p>
59 The first part of this guide is to identify qualified and non-qualified devices
60 that support the Bluetooth technology. This way, users can purchase Bluetooth
61 devices that are known to work. After that, the guide explains how to configure
62 the system kernel, identify the Bluetooth devices installed on the system and
63 detected by the kernel and install the necessary basic Bluetooth tools.
64 </p>
65
66 <p>
67 The second part covers how to detect remote devices and how to establish a
68 connection from or to them by either setting up radio frequency communication
69 (RFCOMM) or by setting up a personal area network (PAN).
70 </p>
71
72 <p>
73 The last part of the guide lists in detail applications that can take
74 advantage of all the possibilities offered by the Bluetooth technology.
75 </p>
76
77 </body>
78 </section>
79 </chapter>
80
81 <chapter id="devices">
82 <title>Supported Devices</title>
83 <section>
84 <title>Qualified and non-qualified devices that support Bluetooth</title>
85 <body>
86
87 <impo>
88 These products might work even though some are not qualified Bluetooth
89 products. Gentoo does not support them in any way, they might just work.
90 </impo>
91
92 <p>
93 A list of the currently supported devices can be found at: <uri
94 link="http://www.holtmann.org/linux/bluetooth/features.html">Bluetooth device
95 features and revision information by Marcel Holtmann</uri>.
96 </p>
97
98 </body>
99 </section>
100 </chapter>
101
102 <chapter id="kernel">
103 <title>Configuring the system</title>
104 <section>
105 <title>Kernel Configuration</title>
106 <body>
107
108 <p>
109 As the latest Linux stable kernel is 2.6, the configuration will be done for
110 these series of the kernel. Most Bluetooth devices are connected to a USB port,
111 so USB will be enabled too. If you want, you can use hotplugging in case you
112 want to use modules instead of compiling support built into the kernel. Please,
113 refer to the <uri link="/doc/en/usb-guide.xml"> Gentoo Linux USB Guide</uri>.
114 </p>
115
116 <pre caption="Configuration for 2.6 kernels">
117 Networking ---&gt;
118
119 &lt;*&gt; Bluetooth subsystem support ---&gt;
120
121 --- Bluetooth subsystem support
122 &lt;M&gt; L2CAP protocol support
123 &lt;M&gt; SCO links support
124 &lt;M&gt; RFCOMM protocol support
125 [*] RFCOMM TTY support
126 &lt;M&gt; BNEP protocol support
127 [*] Multicast filter support
128 [*] Protocol filter support
129 &lt;M&gt; HIDP protocol support
130
131 Bluetooth device drivers ---&gt;
132 &lt;M&gt; HCI USB driver
133 [*] SCO (voice) support
134 &lt;M&gt; HCI UART driver
135 [*] UART (H4) protocol support
136 [*] BCSP protocol support
137 [*] Transmit CRC with every BCSP packet
138 &lt;M&gt; HCI BCM203x USB driver
139 &lt;M&gt; HCI BPA10x USB driver
140 &lt;M&gt; HCI BlueFRITZ! USB driver
141 <comment>(The four drivers below are for PCMCIA Bluetooth devices and will only
142 show up if you have also selected PCMCIA support in your kernel.)</comment>
143 &lt;M&gt; HCI DTL1 (PC Card) driver
144 &lt;M&gt; HCI BT3C (PC Card) driver
145 &lt;M&gt; HCI BlueCard (PC Card) driver
146 &lt;M&gt; HCI UART (PC Card) device driver
147 <comment>(The driver below is intended for HCI Emulation software.)</comment>
148 &lt;M&gt; HCI VHCI (Virtual HCI device) driver
149
150 <comment>(Move back three levels to Device Drives and then check if USB is
151 enabled. This is required if you use a Bluetooth dongle, which are mostly USB
152 based.)</comment>
153 USB support ---&gt;
154
155 &lt;*&gt; Support for Host-side USB
156 --- USB Host Controller Drivers
157 &lt;M&gt; EHCI HCD (USB 2.0) support
158 [ ] Full speed ISO transactions (EXPERIMENTAL)
159 [ ] Root Hub Transaction Translators (EXPERIMENTAL)
160 &lt;*&gt; OHCI HCD support
161 &lt;*&gt; UHCI HCD (most Intel and VIA) support
162 &lt; &gt; SL811HS HCD support
163 </pre>
164
165 <p>
166 Now we'll reboot with our new kernel. If everything went fine, we will have a
167 system that is Bluetooth ready.
168 </p>
169
170 <impo>
171 Your USB device may have two modes the default of which may not be HCI, but HID.
172 If this is your case, use <c>hid2hci</c> to switch to HCI mode. Your system
173 will not remember this change when you next reboot.
174 </impo>
175
176 <pre caption="Checking the Bluetooth devices">
177 <comment>(One way to check for the device)</comment>
178 # <i>cat /proc/bus/usb/devices | grep -e^[TPD] | grep -e Cls=e0 -B1 -A1</i>
179 <comment>(The Cls=e0(unk. ) identifies the Bluetooth adapter.)</comment>
180 T: Bus=02 Lev=02 Prnt=03 Port=00 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
181 D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
182 P: Vendor=0a12 ProdID=0001 Rev= 5.25
183 <comment>(Some might show up on lsusb from sys-apps/usbutils)</comment>
184 # <i>lsusb</i>
185 Bus 003 Device 002: ID 046d:c00e Logitech, Inc. Optical Mouse
186 Bus 003 Device 001: ID 0000:0000
187 Bus 002 Device 002: ID 0db0:1967 Micro Star International Bluetooth Dongle
188 </pre>
189
190 </body>
191 </section>
192 </chapter>
193
194 <chapter id="bluez">
195 <title>BlueZ - The Bluetooth Stack</title>
196 <section>
197 <title>Installing BlueZ</title>
198 <body>
199
200 <p>
201 Now that the device is detected by the kernel, we need a layer that lets
202 applications communicate with the Bluetooth device. BlueZ provides the official
203 Linux Bluetooth stack. The ebuilds that provide what we need are
204 <c>bluez-libs</c> and <c>bluez-utils</c>. Devices that need Broadcom firmware
205 files or the like may need <c>bluez-firmware</c>.
206 </p>
207
208 <pre caption="Installing bluez-libs and bluez-utils">
209 # <i>emerge net-wireless/bluez-libs net-wireless/bluez-utils</i>
210 </pre>
211
212 <warn>
213 Do not emerge <c>bluez-sdp</c> as it will break <c>bluez-utils</c>!
214 </warn>
215
216 <p>
217 Additionally, as we have compiled the Bluetooth subsystem as modules, we will
218 need hotplug, which is explained in the <uri
219 link="http://www.gentoo.org/doc/en/usb-guide.xml#doc_chap4_sect2">Gentoo Linux
220 USB Guide</uri>.
221 </p>
222
223 <pre caption="Emerging hotplug">
224 # <i>emerge hotplug</i>
225 </pre>
226
227 </body>
228 </section>
229 <section>
230 <title>BlueZ configuration and PIN pairing</title>
231 <body>
232
233 <p>
234 Now it's time to see if the Bluetooth device is being picked up correctly by the
235 system. We start up the required Bluetooth services first.
236 </p>
237
238 <pre caption="Running hciconfig">
239 <comment>(Start up Bluetooth)</comment>
240 # <i>/etc/init.d/bluetooth start</i>
241 * Starting Bluetooth ...
242 * Starting hcid ... [ ok ]
243 * Starting sdpd ... [ ok ]
244 * Starting rfcomm ... [ ok ]
245
246 # <i>hciconfig</i>
247 hci0: Type: USB
248 BD Address: 00:01:02:03:04:05 ACL MTU: 192:8 SCO MTU: 64:8
249 DOWN
250 RX bytes:131 acl:0 sco:0 events:18 errors:0
251 TX bytes:565 acl:0 sco:0 commands:17 errors:0
252 </pre>
253
254 <p>
255 This shows that the Bluetooth device has been recognised. As you might have
256 noticed the device is <e>DOWN</e>. Let's configure it so that we can bring it
257 up. The configuration file is at <path>/etc/bluetooth/hcid.conf</path>. The
258 required changes to the config file are shown below. For additional details
259 please refer to <c>man hcid.conf</c>.
260 </p>
261
262 <pre caption="Editing /etc/bluetooth/hcid.conf">
263 <comment>(Recommended changes to be made to the file are shown)</comment>
264
265 # HCId options
266 options {
267 # Automatically initialize new devices
268 autoinit yes;
269
270 <comment>(Change security to "auto")</comment>
271 # Security Manager mode
272 # none - Security manager disabled
273 # auto - Use local PIN for incoming connections
274 # user - Always ask user for a PIN
275 #
276 security auto;
277
278 # Pairing mode
279 pairing multi;
280
281 <comment>(Change pin_helper to use /etc/bluetooth/pin-helper)</comment>
282 # PIN helper
283 pin_helper /etc/bluetooth/pin-helper;
284 }
285
286 # Default settings for HCI devices
287 device {
288 <comment>(Set your device name here, you can call it anything you want)</comment>
289 # Local device name
290 # %d - device id
291 # %h - host name
292 name "BlueZ at %h (%d)";
293
294 # Local device class
295 class 0x3e0100;
296
297 # Inquiry and Page scan
298 iscan enable; pscan enable;
299
300 # Default link mode
301 lm accept;
302
303 # Default link policy
304 lp rswitch,hold,sniff,park;
305
306 <comment>(Leave as is, if you don't know what exactly these do)</comment>
307 # Authentication and Encryption (Security Mode 3)
308 #auth enable;
309 #encrypt enable;
310 }
311 </pre>
312
313 <p>
314 After that, we have to configure the Bluetooth device PIN. That will help in
315 pairing this device with another one.
316 </p>
317
318 <note>
319 You can choose from different pin helpers, depending on what you want to use.
320 Available pin helpers are: <c>/usr/lib/kdebluetooth/kbluepin</c>
321 (net-wireless/kdebluetooth), <c>/usr/bin/bluepin</c> or
322 <c>/etc/bluetooth/pin-helper</c> among others.
323 </note>
324
325 <pre caption="Editing /etc/bluetooth/pin">
326 <comment>(Change 123456 with your desired pin number.)</comment>
327 123456
328 </pre>
329
330 <impo>
331 This number (of your choice) must be the same in all your hosts with Bluetooth
332 devices so they can be paired. This number must also be kept secret since anyone
333 with knowledge of this number can essentially establish connections with your
334 devices.
335 </impo>
336
337 </body>
338 </section>
339 <section>
340 <title>Services configuration</title>
341 <body>
342
343 <p>
344 Now that we have concluded with the configuration of BlueZ, it's time to restart
345 the necessary services.
346 </p>
347
348 <pre caption="Starting the Bluetooth daemons">
349 # <i>/etc/init.d/bluetooth restart</i>
350 <comment>(We can also add it to the default runlevel.)</comment>
351 # <i>rc-update add bluetooth default</i>
352 * bluetooth added to runlevel default
353 * rc-update complete.
354 </pre>
355
356 <p>
357 Let's be sure that the Bluetooth daemons started correctly. If we can see that
358 both <c>hcid</c> and <c>sdpd</c> are running, then we configured Bluetooth the
359 right way. After that, we can see if the devices are now up and running with
360 the configured options.
361 </p>
362
363 <pre caption="Checking whether Bluetooth daemons started correctly">
364 <comment>(Check to see if the services are running)</comment>
365 # <i>ps -ae | grep hcid</i>
366 26050 ? 00:00:00 hcid
367 # <i>ps -ae | grep sdpd</i>
368 26054 ? 00:00:00 sdpd
369
370 # <i>hciconfig -a</i>
371 hci0: Type: USB
372 BD Address: 00:0A:0B:0C:0D:0E ACL MTU: 192:8 SCO MTU: 64:8
373 UP RUNNING PSCAN ISCAN
374 RX bytes:125 acl:0 sco:0 events:17 errors:0
375 TX bytes:565 acl:0 sco:0 commands:17 errors:0
376 Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
377 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
378 Link policy: RSWITCH HOLD SNIFF PARK
379 Link mode: SLAVE ACCEPT
380 Name: 'BlueZ at bluehat (0)'
381 Class: 0x3e0100
382 Service Classes: Networking, Rendering, Capturing, Object Transfer,
383 Audio
384 Device Class: Computer, Uncategorized
385 HCI Ver: 1.1 (0x1) HCI Rev: 0x1e7 LMP Ver: 1.1 (0x1) LMP Subver: 0x1e7
386 Manufacturer: Cambridge Silicon Radio (10)
387 </pre>
388
389 </body>
390 </section>
391 </chapter>
392
393 <chapter id="detect">
394 <title>Detecting and Connecting to Remote Devices</title>
395 <section>
396 <title>Detecting Bluetooth devices in other hosts</title>
397 <body>
398
399 <p>
400 At this point we are now ready to detect Bluetooth devices installed in other
401 machines. This is independent of the host Operating System. We will make use of
402 the <c>hcitool</c> command for the same.
403 </p>
404
405 <pre caption="Checking for local devices">
406 # <i>hcitool dev</i>
407 Devices:
408 hci0 00:01:02:03:04:05
409 </pre>
410
411 <pre caption="Scanning for remote devices">
412 # <i>hcitool scan</i>
413 Scanning ...
414 00:0A:0B:0C:0D:0E Grayhat
415 </pre>
416
417 <pre caption="Inquiring remote devices">
418 # <i>hcitool inq</i>
419 Inquiring ...
420 00:0A:0B:0C:0D:0E clock offset: 0x5579 class: 0x72010c
421 </pre>
422
423 <p>
424 Now that we know the MAC address of the remote Bluetooth devices, we can check
425 if we paired them correctly.
426 </p>
427
428 <pre caption="Running l2ping">
429 # <i>l2ping 00:0A:0B:0C:0D:0E</i>
430 Ping: 00:0A:0B:0C:0D:0E from 00:01:02:03:04:05 (data size 20) ...
431 20 bytes from 00:0A:0B:0C:0D:0E id 200 time 69.85ms
432 20 bytes from 00:0A:0B:0C:0D:0E id 201 time 9.97ms
433 20 bytes from 00:0A:0B:0C:0D:0E id 202 time 56.86ms
434 20 bytes from 00:0A:0B:0C:0D:0E id 203 time 39.92ms
435 4 sent, 4 received, 0% loss
436 </pre>
437
438 </body>
439 </section>
440 <section>
441 <title>Setting up Radio Frequency Communication (RFCOMM)</title>
442 <body>
443
444 <note>
445 Please note that setting up radio frequency communication is optional.
446 </note>
447
448 <p>
449 We can establish a radio frequency connection to another Bluetooth device using
450 the <c>rfcomm</c> command. To make things a little easier especially for users
451 with multiple devices that support Bluetooth, it is advisable to make a few
452 changes to the default rfcomm config at <path>/etc/bluetooth/rfcomm.conf</path>.
453 </p>
454
455 <p>
456 The whole segment of the config starting from <c>rfcomm0 {</c> and ending with
457 <c>}</c> is the config for the device that will establish a connection at
458 <path>/dev/rfcomm0</path>. In this case, we will only show one example, rfcomm0.
459 You can add more devices as you see fit.
460 </p>
461
462 <pre caption="Editing /etc/bluetooth/rfcomm.conf">
463 <comment>(Only changes that might be needed are shown)</comment>
464 rfcomm0 {
465 # Automatically bind the device at startup
466 <comment>(Creates the device node, /dev/rfcomm0 at start up)</comment>
467 bind yes;
468
469 # Bluetooth address of the device
470 <comment>(Enter the address of the device you want to connect to)</comment>
471 device 00:0A:0B:0C:0D:0E;
472
473 }
474 </pre>
475
476 <p>
477 After configuring RFCOMM, we can connect to any device. Since we've made the
478 required settings to the <path>/etc/bluetooth/rfcomm.conf</path> file, we just
479 issue the command shown below. In case you've not made changes to the config
480 file, an alternative method is also shown in the code listing that follows
481 </p>
482
483 <pre caption="Establishing an RFCOMM connection">
484 <comment>(The 0 refers to the rfcomm0 in the config file)</comment>
485 # <i>rfcomm connect 0 </i>
486 Connected /dev/rfcomm0 to 00:0A:0B:0C:0D:0E on channel 1
487 Press CTRL-C for hangup
488
489 <comment>(If you did not edit /etc/bluetooth/rfcomm.conf)</comment>
490 # <i>rfcomm connect 0 00:0A:0B:0C:0D:0E 1</i>
491 Connected /dev/rfcomm0 to 00:0F:DE:69:50:24 on channel 1
492 Press CTRL-C for hangup
493 </pre>
494
495 <p>
496 The first parameter after the connect command is the RFCOMM TTY device node
497 that will be used (usually 0). The second parameter is the MAC address of the
498 remote device. The third parameter is optional and specifies the channel to be
499 used. Please, note that in order to connect to a device, that device must be
500 listening for incoming connections. To do that, we have to explicitly tell it
501 to listen. We can cancel the communication at any moment by just hitting
502 CTRL+C.
503 </p>
504
505 <pre caption="Listening for incoming RFCOMM connections">
506 # <i>rfcomm listen 0 1</i>
507 Waiting for connection on channel 1
508 </pre>
509
510 <p>
511 In a similar way to the connect command, the listen command can receive two
512 parameters. The first one explicits the RFCOMM TTY device node (usually 0) that
513 will be used to accept a connection, while the second is the channel that will
514 be used.
515 </p>
516
517 <p>
518 Each time you call the <c>rfcomm</c> command, you can also specify the physical
519 device you want to use. Below you can see a small example specifiying the
520 physical device on the above two commands.
521 </p>
522
523 <pre caption="RFCOMM connections specifying physical device">
524 # <i>rfcomm -i hci0 listen 0 1</i>
525 Waiting for connection on channel 1
526 <comment>(To listen to a determined device) </comment>
527 # <i>rfcomm -i hci0 connect 0 00:0A:0B:0C:0D:0E 1</i>
528 <comment>(To use a determined device when connecting to another one)</comment>
529 </pre>
530
531 </body>
532 </section>
533 <section>
534 <title>Setting up a Personal Area Network (PAN)</title>
535 <body>
536
537 <note>
538 Please note that setting up a Personal Area Network is optional. This section
539 describes how to set up and connect to a Network Access Point, though setting
540 up a Group Ad-Hoc Network follows a similar way.
541 </note>
542
543 <p>
544 First of all, we need the <c>bnep</c> module loaded. And probably we want it
545 loaded each time the computer starts.
546 </p>
547
548 <pre caption="Loading the bnep module">
549 # <i>modprobe bnep</i>
550 # <i>echo "bnep" &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>
551 </pre>
552
553 <p>
554 We have to start the <c>pand</c> daemon in the host that will provide the NAP.
555 We'll have to specify that we want to provide a NAP service and that this host
556 will be the master, thus the other hosts that connect to it, the slaves.
557 Another possible service is GN (Group ad-hoc Network).
558 </p>
559
560 <pre caption="Running the pand daemon">
561 # <i>pand --listen --role NAP --master --autozap</i>
562 </pre>
563
564 <p>
565 After doing that, we have a host listening, so the rest of hosts just have to
566 connect to that one.
567 </p>
568
569 <pre caption="Connecting to the Network Access Point">
570 # <i>pand --connect 00:0A:0B:0C:0D:0E --service NAP --autozap</i>
571 </pre>
572
573 <p>
574 If everything went fine, we can now configure the IP addresses of our hosts.
575 </p>
576
577 <pre caption="bnep IP address configuration">
578 host0 #<i> ifconfig bnep0 192.168.2.1</i>
579 host1 #<i> ifconfig bnep0 192.168.2.2</i>
580
581 host0 #<i> ifconfig bnep0</i>
582 bnep0 Link encap:Ethernet HWaddr 00:0A:0B:0C:0D:0E
583 inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0
584 inet6 addr: fe80::210:60ff:fea3:cb41/64 Scope:Link
585 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
586 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
587 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
588 collisions:0 txqueuelen:1000
589 RX bytes:208 (208.0 b) TX bytes:188 (188.0 b)
590
591 host1 #<i> ifconfig bnep0</i>
592 bnep0 Link encap:Ethernet HWaddr 00:01:02:03:04:05
593 inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
594 inet6 addr: fe80::210:60ff:fea2:dd2a/64 Scope:Link
595 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
596 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
597 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
598 collisions:0 txqueuelen:1000
599 RX bytes:208 (208.0 b) TX bytes:188 (188.0 b)
600 </pre>
601
602 <p>
603 Finally, we can do a simple test to see that the network is working fine.
604 </p>
605
606 <pre caption="IP ping between bnep interfaces">
607 host1 #<i> ping 192.168.2.1</i>
608 PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
609 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=34.0 ms
610 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=37.3 ms
611
612 --- 192.168.2.1 ping statistics ---
613 2 packets transmitted, 2 received, 0% packet loss, time 1000ms
614 rtt min/avg/max/mdev = 34.045/35.690/37.336/1.656 ms
615 </pre>
616
617 </body>
618 </section>
619 </chapter>
620
621 <chapter id="apps">
622 <title>Desktop Applications for Bluetooth</title>
623 <section>
624 <title>Introduction</title>
625 <body>
626
627 <p>
628 We have quite a few Bluetooth applications that run on the desktop and this
629 chapter has been divided into 3 parts, one each for Gnome, KDE and Miscellaneous
630 applications.
631 </p>
632
633 </body>
634 </section>
635 <section>
636 <title>For Gnome</title>
637 <body>
638
639 <p>
640 If you are a gnome user, you will most probably go with <c>gnome-bluetooth</c>.
641 It provides the most basic yet most used functionalities, as you can see below.
642 </p>
643
644 <ul>
645 <li><c>gnome-bluetooth-manager</c>: To manage Bluetooth remote devices.</li>
646 <li><c>gnome-obex-send</c>: To send files to other devices.</li>
647 <li><c>gnome-obex-server</c>: To receive files.</li>
648 </ul>
649
650 <pre caption="Installing gnome-bluetooth">
651 # <i>emerge gnome-bluetooth</i>
652 </pre>
653
654 <p>
655 This adds menu entries under Applications &gt; System Tools from where you can
656 easily start up the manager or File sharing to transfer files between devices.
657 </p>
658
659 <p>
660 To transfer files (the easy way):
661 </p>
662
663 <ul>
664 <li>
665 From the Phone to the Computer - Send the file from the phone via Bluetooth
666 and it will be picked up and saved to your <path>/home</path> always.
667 </li>
668 <!--FIXME : Doesn't work on Nautilus 2.10.x. Bug #103464 for details -->
669 <!--
670 <li>
671 From the Computer to the Phone - Fire up <c>nautilus</c> and select the
672 file you want to send and right click on it. Select the Send via Bluetooth
673 option and ask your phone to accept the file.
674 </li>
675 -->
676 </ul>
677
678 <p>
679 <c>gnome-phone-manager</c> is a nifty app that you can use to send and receive
680 messages to and from your phone, using only your system. You do not have to
681 touch your phone to read or send messages since all that happens through the
682 application. You are also notified of a new message on your screen if the option
683 is enabled under Preferences. Installation is a breeze as always.
684 </p>
685
686 <pre caption="Installing gnome-phone-manager">
687 # <i>emerge gnome-phone-manager</i>
688 </pre>
689
690 </body>
691 </section>
692 <section>
693 <title>For KDE</title>
694 <body>
695
696 <p>
697 KDE makes use of <c>kdebluetooth</c> and provides more utilities than its Gnome
698 counterpart as seen below.
699 </p>
700
701 <ul>
702 <li><c>kbluetoothd</c>: Bluetooth Meta Server.</li>
703 <li><c>kbtsearch</c>: Bluetooth device/service search utility.</li>
704 <li><c>khciconfig</c>: KDE Bluetooth Monitor.</li>
705 <li><c>kioclient</c>: KIO command line client.</li>
706 <li><c>qobexclient</c>: Swiss army knife for obex testing/development.</li>
707 <li><c>kbtobexclient</c>: A KDE Bluetooth Framework Application.</li>
708 <li><c>kioobex_start</c></li>
709 <li><c>kbtserialchat</c></li>
710 <li><c>kbemusedsrv</c>: KDE Bemused Server.</li>
711 <li><c>kbtobexsrv</c>: KDE OBEX Push Server for Bluetooth.</li>
712 <li><c>kbluepin</c>: A KDE KPart Application.</li>
713 <li>
714 <c>auth-helper</c>: A helper program for kbtobexsrv that sends an
715 authentication request for a given ACL link.
716 </li>
717 </ul>
718
719 <pre caption="Installing kdebluetooth">
720 # <i>emerge kdebluetooth</i>
721 </pre>
722
723 </body>
724 </section>
725 <section>
726 <title>Other Interesting Applications</title>
727 <body>
728
729 <ul>
730 <li>
731 <c>app-mobilephone/obexftp</c>: File transfer over OBEX for mobile phones
732 </li>
733 <li>
734 <c>app-mobilephone/bemused</c>: Bemused is a system which allows you to
735 control your music collection from your phone, using Bluetooth.
736 </li>
737 <li>
738 <c>app-pda/multisync</c>: Multisync allows you to sync contacts, calendar
739 entries and notes from your mobile phone with your computer, over a
740 Bluetooth connection (amongst other things). It includes such features as
741 backing up this information and restoring it later, and syncing with the
742 Evolution e-mail client. You will need the <c>irmc</c> USE flag set to
743 ensure that <c>multisync</c> has Bluetooth support.
744 </li>
745 <li>
746 <c>net-wireless/opd</c> and <c>net-wireless/ussp-push</c> are command line
747 tools (server and client) that can be used to send files to your mobile
748 phone.
749 </li>
750 </ul>
751
752 </body>
753 </section>
754 </chapter>
755
756 <chapter>
757 <title>Acknowledgements</title>
758 <section>
759 <body>
760
761 <p>
762 Special thanks to <mail link="marcel@holtmann.org">Marcel Holtmann</mail>
763 for his time and dedication to the Bluetooth development and for reviewing this
764 guide. And big thanks to <mail link="puggy@gentoo.org">Douglas Russell</mail>
765 for performing additional hardware tests and improving this guide.
766 </p>
767
768 </body>
769 </section>
770 </chapter>
771 </guide>

  ViewVC Help
Powered by ViewVC 1.1.20