/[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.7 - (show annotations) (download) (as text)
Tue Sep 19 10:24:53 2006 UTC (8 years ago) by jkt
Branch: MAIN
Changes since 1.6: +4 -5 lines
File MIME type: application/xml
#132600, bluez-kernel was removed from the tree

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.6 2006/03/02 23:59:29 neysx 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.4</version>
36 <date>2006-09-19</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 and coldplug, which are 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 and coldplug">
224 # <i>emerge hotplug coldplug</i>
225 # <i>rc-update add coldplug boot</i>
226 </pre>
227
228 </body>
229 </section>
230 <section>
231 <title>BlueZ configuration and PIN pairing</title>
232 <body>
233
234 <p>
235 Now it's time to see if the Bluetooth device is being picked up correctly by the
236 system. We start up the required Bluetooth services first.
237 </p>
238
239 <pre caption="Running hciconfig">
240 <comment>(Start up Bluetooth)</comment>
241 # <i>/etc/init.d/bluetooth start</i>
242 * Starting Bluetooth ...
243 * Starting hcid ... [ ok ]
244 * Starting sdpd ... [ ok ]
245 * Starting rfcomm ... [ ok ]
246
247 # <i>hciconfig</i>
248 hci0: Type: USB
249 BD Address: 00:01:02:03:04:05 ACL MTU: 192:8 SCO MTU: 64:8
250 DOWN
251 RX bytes:131 acl:0 sco:0 events:18 errors:0
252 TX bytes:565 acl:0 sco:0 commands:17 errors:0
253 </pre>
254
255 <p>
256 This shows that the Bluetooth device has been recognised. As you might have
257 noticed the device is <e>DOWN</e>. Let's configure it so that we can bring it
258 up. The configuration file is at <path>/etc/bluetooth/hcid.conf</path>. The
259 required changes to the config file are shown below. For additional details
260 please refer to <c>man hcid.conf</c>.
261 </p>
262
263 <pre caption="Editing /etc/bluetooth/hcid.conf">
264 <comment>(Recommended changes to be made to the file are shown)</comment>
265
266 # HCId options
267 options {
268 # Automatically initialize new devices
269 autoinit yes;
270
271 <comment>(Change security to "auto")</comment>
272 # Security Manager mode
273 # none - Security manager disabled
274 # auto - Use local PIN for incoming connections
275 # user - Always ask user for a PIN
276 #
277 security auto;
278
279 # Pairing mode
280 pairing multi;
281
282 <comment>(Change pin_helper to use /etc/bluetooth/pin-helper)</comment>
283 # PIN helper
284 pin_helper /etc/bluetooth/pin-helper;
285 }
286
287 # Default settings for HCI devices
288 device {
289 <comment>(Set your device name here, you can call it anything you want)</comment>
290 # Local device name
291 # %d - device id
292 # %h - host name
293 name "BlueZ at %h (%d)";
294
295 # Local device class
296 class 0x3e0100;
297
298 # Inquiry and Page scan
299 iscan enable; pscan enable;
300
301 # Default link mode
302 lm accept;
303
304 # Default link policy
305 lp rswitch,hold,sniff,park;
306
307 <comment>(Leave as is, if you don't know what exactly these do)</comment>
308 # Authentication and Encryption (Security Mode 3)
309 #auth enable;
310 #encrypt enable;
311 }
312 </pre>
313
314 <p>
315 After that, we have to configure the Bluetooth device PIN. That will help in
316 pairing this device with another one.
317 </p>
318
319 <note>
320 You can choose from different pin helpers, depending on what you want to use.
321 Available pin helpers are: <c>/usr/lib/kdebluetooth/kbluepin</c>
322 (net-wireless/kdebluetooth), <c>/usr/bin/bluepin</c> or
323 <c>/etc/bluetooth/pin-helper</c> among others.
324 </note>
325
326 <pre caption="Editing /etc/bluetooth/pin">
327 <comment>(Change 123456 with your desired pin number.)</comment>
328 123456
329 </pre>
330
331 <impo>
332 This number (of your choice) must be the same in all your hosts with Bluetooth
333 devices so they can be paired. This number must also be kept secret since anyone
334 with knowledge of this number can essentially establish connections with your
335 devices.
336 </impo>
337
338 </body>
339 </section>
340 <section>
341 <title>Services configuration</title>
342 <body>
343
344 <p>
345 Now that we have concluded with the configuration of BlueZ, it's time to restart
346 the necessary services.
347 </p>
348
349 <pre caption="Starting the Bluetooth daemons">
350 # <i>/etc/init.d/bluetooth restart</i>
351 <comment>(We can also add it to the default runlevel.)</comment>
352 # <i>rc-update add bluetooth default</i>
353 * bluetooth added to runlevel default
354 * rc-update complete.
355 </pre>
356
357 <p>
358 Let's be sure that the Bluetooth daemons started correctly. If we can see that
359 both <c>hcid</c> and <c>sdpd</c> are running, then we configured Bluetooth the
360 right way. After that, we can see if the devices are now up and running with
361 the configured options.
362 </p>
363
364 <pre caption="Checking whether Bluetooth daemons started correctly">
365 <comment>(Check to see if the services are running)</comment>
366 # <i>ps -ae | grep hcid</i>
367 26050 ? 00:00:00 hcid
368 # <i>ps -ae | grep sdpd</i>
369 26054 ? 00:00:00 sdpd
370
371 # <i>hciconfig -a</i>
372 hci0: Type: USB
373 BD Address: 00:0A:0B:0C:0D:0E ACL MTU: 192:8 SCO MTU: 64:8
374 UP RUNNING PSCAN ISCAN
375 RX bytes:125 acl:0 sco:0 events:17 errors:0
376 TX bytes:565 acl:0 sco:0 commands:17 errors:0
377 Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
378 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
379 Link policy: RSWITCH HOLD SNIFF PARK
380 Link mode: SLAVE ACCEPT
381 Name: 'BlueZ at bluehat (0)'
382 Class: 0x3e0100
383 Service Classes: Networking, Rendering, Capturing, Object Transfer,
384 Audio
385 Device Class: Computer, Uncategorized
386 HCI Ver: 1.1 (0x1) HCI Rev: 0x1e7 LMP Ver: 1.1 (0x1) LMP Subver: 0x1e7
387 Manufacturer: Cambridge Silicon Radio (10)
388 </pre>
389
390 </body>
391 </section>
392 </chapter>
393
394 <chapter id="detect">
395 <title>Detecting and Connecting to Remote Devices</title>
396 <section>
397 <title>Detecting Bluetooth devices in other hosts</title>
398 <body>
399
400 <p>
401 At this point we are now ready to detect Bluetooth devices installed in other
402 machines. This is independent of the host Operating System. We will make use of
403 the <c>hcitool</c> command for the same.
404 </p>
405
406 <pre caption="Checking for local devices">
407 # <i>hcitool dev</i>
408 Devices:
409 hci0 00:01:02:03:04:05
410 </pre>
411
412 <pre caption="Scanning for remote devices">
413 # <i>hcitool scan</i>
414 Scanning ...
415 00:0A:0B:0C:0D:0E Grayhat
416 </pre>
417
418 <pre caption="Inquiring remote devices">
419 # <i>hcitool inq</i>
420 Inquiring ...
421 00:0A:0B:0C:0D:0E clock offset: 0x5579 class: 0x72010c
422 </pre>
423
424 <p>
425 Now that we know the MAC address of the remote Bluetooth devices, we can check
426 if we paired them correctly.
427 </p>
428
429 <pre caption="Running l2ping">
430 # <i>l2ping 00:0A:0B:0C:0D:0E</i>
431 Ping: 00:0A:0B:0C:0D:0E from 00:01:02:03:04:05 (data size 20) ...
432 20 bytes from 00:0A:0B:0C:0D:0E id 200 time 69.85ms
433 20 bytes from 00:0A:0B:0C:0D:0E id 201 time 9.97ms
434 20 bytes from 00:0A:0B:0C:0D:0E id 202 time 56.86ms
435 20 bytes from 00:0A:0B:0C:0D:0E id 203 time 39.92ms
436 4 sent, 4 received, 0% loss
437 </pre>
438
439 </body>
440 </section>
441 <section>
442 <title>Setting up Radio Frequency Communication (RFCOMM)</title>
443 <body>
444
445 <note>
446 Please note that setting up radio frequency communication is optional.
447 </note>
448
449 <p>
450 We can establish a radio frequency connection to another Bluetooth device using
451 the <c>rfcomm</c> command. To make things a little easier especially for users
452 with multiple devices that support Bluetooth, it is advisable to make a few
453 changes to the default rfcomm config at <path>/etc/bluetooth/rfcomm.conf</path>.
454 </p>
455
456 <p>
457 The whole segment of the config starting from <c>rfcomm0 {</c> and ending with
458 <c>}</c> is the config for the device that will establish a connection at
459 <path>/dev/rfcomm0</path>. In this case, we will only show one example, rfcomm0.
460 You can add more devices as you see fit.
461 </p>
462
463 <pre caption="Editing /etc/bluetooth/rfcomm.conf">
464 <comment>(Only changes that might be needed are shown)</comment>
465 rfcomm0 {
466 # Automatically bind the device at startup
467 <comment>(Creates the device node, /dev/rfcomm0 at start up)</comment>
468 bind yes;
469
470 # Bluetooth address of the device
471 <comment>(Enter the address of the device you want to connect to)</comment>
472 device 00:0A:0B:0C:0D:0E;
473
474 }
475 </pre>
476
477 <p>
478 After configuring RFCOMM, we can connect to any device. Since we've made the
479 required settings to the <path>/etc/bluetooth/rfcomm.conf</path> file, we just
480 issue the command shown below. In case you've not made changes to the config
481 file, an alternative method is also shown in the code listing that follows
482 </p>
483
484 <pre caption="Establishing an RFCOMM connection">
485 <comment>(The 0 refers to the rfcomm0 in the config file)</comment>
486 # <i>rfcomm connect 0 </i>
487 Connected /dev/rfcomm0 to 00:0A:0B:0C:0D:0E on channel 1
488 Press CTRL-C for hangup
489
490 <comment>(If you did not edit /etc/bluetooth/rfcomm.conf)</comment>
491 # <i>rfcomm connect 0 00:0A:0B:0C:0D:0E 1</i>
492 Connected /dev/rfcomm0 to 00:0F:DE:69:50:24 on channel 1
493 Press CTRL-C for hangup
494 </pre>
495
496 <p>
497 The first parameter after the connect command is the RFCOMM TTY device node
498 that will be used (usually 0). The second parameter is the MAC address of the
499 remote device. The third parameter is optional and specifies the channel to be
500 used. Please, note that in order to connect to a device, that device must be
501 listening for incoming connections. To do that, we have to explicitly tell it
502 to listen. We can cancel the communication at any moment by just hitting
503 CTRL+C.
504 </p>
505
506 <pre caption="Listening for incoming RFCOMM connections">
507 # <i>rfcomm listen 0 1</i>
508 Waiting for connection on channel 1
509 </pre>
510
511 <p>
512 In a similar way to the connect command, the listen command can receive two
513 parameters. The first one explicits the RFCOMM TTY device node (usually 0) that
514 will be used to accept a connection, while the second is the channel that will
515 be used.
516 </p>
517
518 <p>
519 Each time you call the <c>rfcomm</c> command, you can also specify the physical
520 device you want to use. Below you can see a small example specifiying the
521 physical device on the above two commands.
522 </p>
523
524 <pre caption="RFCOMM connections specifying physical device">
525 # <i>rfcomm -i hci0 listen 0 1</i>
526 Waiting for connection on channel 1
527 <comment>(To listen to a determined device) </comment>
528 # <i>rfcomm -i hci0 connect 0 00:0A:0B:0C:0D:0E 1</i>
529 <comment>(To use a determined device when connecting to another one)</comment>
530 </pre>
531
532 </body>
533 </section>
534 <section>
535 <title>Setting up a Personal Area Network (PAN)</title>
536 <body>
537
538 <note>
539 Please note that setting up a Personal Area Network is optional. This section
540 describes how to set up and connect to a Network Access Point, though setting
541 up a Group Ad-Hoc Network follows a similar way.
542 </note>
543
544 <p>
545 First of all, we need the <c>bnep</c> module loaded. And probably we want it
546 loaded each time the computer starts.
547 </p>
548
549 <pre caption="Loading the bnep module">
550 # <i>modprobe bnep</i>
551 # <i>echo "bnep" &gt;&gt; /etc/modules.autoload.d/kernel-2.6</i>
552 </pre>
553
554 <p>
555 We have to start the <c>pand</c> daemon in the host that will provide the NAP.
556 We'll have to specify that we want to provide a NAP service and that this host
557 will be the master, thus the other hosts that connect to it, the slaves.
558 Another possible service is GN (Group ad-hoc Network).
559 </p>
560
561 <pre caption="Running the pand daemon">
562 # <i>pand --listen --role NAP --master --autozap</i>
563 </pre>
564
565 <p>
566 After doing that, we have a host listening, so the rest of hosts just have to
567 connect to that one.
568 </p>
569
570 <pre caption="Connecting to the Network Access Point">
571 # <i>pand --connect 00:0A:0B:0C:0D:0E --service NAP --autozap</i>
572 </pre>
573
574 <p>
575 If everything went fine, we can now configure the IP addresses of our hosts.
576 </p>
577
578 <pre caption="bnep IP address configuration">
579 host0 #<i> ifconfig bnep0 192.168.2.1</i>
580 host1 #<i> ifconfig bnep0 192.168.2.2</i>
581
582 host0 #<i> ifconfig bnep0</i>
583 bnep0 Link encap:Ethernet HWaddr 00:0A:0B:0C:0D:0E
584 inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0
585 inet6 addr: fe80::210:60ff:fea3:cb41/64 Scope:Link
586 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
587 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
588 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
589 collisions:0 txqueuelen:1000
590 RX bytes:208 (208.0 b) TX bytes:188 (188.0 b)
591
592 host1 #<i> ifconfig bnep0</i>
593 bnep0 Link encap:Ethernet HWaddr 00:01:02:03:04:05
594 inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
595 inet6 addr: fe80::210:60ff:fea2:dd2a/64 Scope:Link
596 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
597 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
598 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
599 collisions:0 txqueuelen:1000
600 RX bytes:208 (208.0 b) TX bytes:188 (188.0 b)
601 </pre>
602
603 <p>
604 Finally, we can do a simple test to see that the network is working fine.
605 </p>
606
607 <pre caption="IP ping between bnep interfaces">
608 host1 #<i> ping 192.168.2.1</i>
609 PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
610 64 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=34.0 ms
611 64 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=37.3 ms
612
613 --- 192.168.2.1 ping statistics ---
614 2 packets transmitted, 2 received, 0% packet loss, time 1000ms
615 rtt min/avg/max/mdev = 34.045/35.690/37.336/1.656 ms
616 </pre>
617
618 </body>
619 </section>
620 </chapter>
621
622 <chapter id="apps">
623 <title>Desktop Applications for Bluetooth</title>
624 <section>
625 <title>Introduction</title>
626 <body>
627
628 <p>
629 We have quite a few Bluetooth applications that run on the desktop and this
630 chapter has been divided into 3 parts, one each for Gnome, KDE and Miscellaneous
631 applications.
632 </p>
633
634 </body>
635 </section>
636 <section>
637 <title>For Gnome</title>
638 <body>
639
640 <p>
641 If you are a gnome user, you will most probably go with <c>gnome-bluetooth</c>.
642 It provides the most basic yet most used functionalities, as you can see below.
643 </p>
644
645 <ul>
646 <li><c>gnome-bluetooth-manager</c>: To manage Bluetooth remote devices.</li>
647 <li><c>gnome-obex-send</c>: To send files to other devices.</li>
648 <li><c>gnome-obex-server</c>: To receive files.</li>
649 </ul>
650
651 <pre caption="Installing gnome-bluetooth">
652 # <i>emerge gnome-bluetooth</i>
653 </pre>
654
655 <p>
656 This adds menu entries under Applications &gt; System Tools from where you can
657 easily start up the manager or File sharing to transfer files between devices.
658 </p>
659
660 <p>
661 To transfer files (the easy way):
662 </p>
663
664 <ul>
665 <li>
666 From the Phone to the Computer - Send the file from the phone via Bluetooth
667 and it will be picked up and saved to your <path>/home</path> always.
668 </li>
669 <!--FIXME : Doesn't work on Nautilus 2.10.x. Bug #103464 for details -->
670 <!--
671 <li>
672 From the Computer to the Phone - Fire up <c>nautilus</c> and select the
673 file you want to send and right click on it. Select the Send via Bluetooth
674 option and ask your phone to accept the file.
675 </li>
676 -->
677 </ul>
678
679 <p>
680 <c>gnome-phone-manager</c> is a nifty app that you can use to send and receive
681 messages to and from your phone, using only your system. You do not have to
682 touch your phone to read or send messages since all that happens through the
683 application. You are also notified of a new message on your screen if the option
684 is enabled under Preferences. Installation is a breeze as always.
685 </p>
686
687 <pre caption="Installing gnome-phone-manager">
688 # <i>emerge gnome-phone-manager</i>
689 </pre>
690
691 </body>
692 </section>
693 <section>
694 <title>For KDE</title>
695 <body>
696
697 <p>
698 KDE makes use of <c>kdebluetooth</c> and provides more utilities than its Gnome
699 counterpart as seen below.
700 </p>
701
702 <ul>
703 <li><c>kbluetoothd</c>: Bluetooth Meta Server.</li>
704 <li><c>kbtsearch</c>: Bluetooth device/service search utility.</li>
705 <li><c>khciconfig</c>: KDE Bluetooth Monitor.</li>
706 <li><c>kioclient</c>: KIO command line client.</li>
707 <li><c>qobexclient</c>: Swiss army knife for obex testing/development.</li>
708 <li><c>kbtobexclient</c>: A KDE Bluetooth Framework Application.</li>
709 <li><c>kioobex_start</c></li>
710 <li><c>kbtserialchat</c></li>
711 <li><c>kbemusedsrv</c>: KDE Bemused Server.</li>
712 <li><c>kbtobexsrv</c>: KDE OBEX Push Server for Bluetooth.</li>
713 <li><c>kbluepin</c>: A KDE KPart Application.</li>
714 <li>
715 <c>auth-helper</c>: A helper program for kbtobexsrv that sends an
716 authentication request for a given ACL link.
717 </li>
718 </ul>
719
720 <pre caption="Installing kdebluetooth">
721 # <i>emerge kdebluetooth</i>
722 </pre>
723
724 </body>
725 </section>
726 <section>
727 <title>Other Interesting Applications</title>
728 <body>
729
730 <ul>
731 <li>
732 <c>app-mobilephone/obexftp</c>: File transfer over OBEX for mobile phones
733 </li>
734 <li>
735 <c>app-mobilephone/bemused</c>: Bemused is a system which allows you to
736 control your music collection from your phone, using Bluetooth.
737 </li>
738 <li>
739 <c>app-pda/multisync</c>: Multisync allows you to sync contacts, calendar
740 entries and notes from your mobile phone with your computer, over a
741 Bluetooth connection (amongst other things). It includes such features as
742 backing up this information and restoring it later, and syncing with the
743 Evolution e-mail client. You will need the <c>irmc</c> USE flag set to
744 ensure that <c>multisync</c> has Bluetooth support.
745 </li>
746 <li>
747 <c>media-plugins/xmms-btexmms</c>: Btexmms is an XMMS plugin that allows
748 you to use your Bluetooth-enabled (Sony) Ericsson mobile phone as a remote
749 control for XMMS.
750 </li>
751 </ul>
752
753 </body>
754 </section>
755 </chapter>
756
757 <chapter>
758 <title>Acknowledgements</title>
759 <section>
760 <body>
761
762 <p>
763 Special thanks to <mail link="marcel@holtmann.org">Marcel Holtmann</mail>
764 for his time and dedication to the Bluetooth development and for reviewing this
765 guide. And big thanks to <mail link="puggy@gentoo.org">Douglas Russell</mail>
766 for performing additional hardware tests and improving this guide.
767 </p>
768
769 </body>
770 </section>
771 </chapter>
772 </guide>

  ViewVC Help
Powered by ViewVC 1.1.20