/[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.12 - (show annotations) (download) (as text)
Tue Apr 10 06:48:59 2007 UTC (7 years, 6 months ago) by nightmorph
Branch: MAIN
Changes since 1.11: +5 -17 lines
File MIME type: application/xml
DIE HOTPLUG DIE. by request of cardoe.

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

  ViewVC Help
Powered by ViewVC 1.1.20