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

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

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

Revision 1.2 Revision 1.14
1<?xml version='1.0' encoding="UTF-8"?> 1<?xml version='1.0' encoding="UTF-8"?>
2 2
3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> 3<!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
4<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml,v 1.2 2005/08/27 09:19:30 swift Exp $ --> 4<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/bluetooth-guide.xml,v 1.14 2007/10/22 05:27:37 nightmorph Exp $ -->
5 5
6<guide link="/doc/en/bluetooth-guide.xml"> 6<guide link="/doc/en/bluetooth-guide.xml">
7<title>Gentoo Linux Bluetooth Guide</title> 7<title>Gentoo Linux Bluetooth Guide</title>
8 8
9<author title="Author"> 9<author title="Author">
13 <mail link="puggy@gentoo.org">Douglas Russell</mail> 13 <mail link="puggy@gentoo.org">Douglas Russell</mail>
14</author> 14</author>
15<author title="Contributor"> 15<author title="Contributor">
16 <mail link="marcel@holtmann.org">Marcel Holtmann</mail> 16 <mail link="marcel@holtmann.org">Marcel Holtmann</mail>
17</author> 17</author>
18<author title="Author/Editor"> 18<author title="Author">
19 <mail link="fox2mike@gentoo.org">Shyam Mani</mail> 19 <mail link="fox2mike@gentoo.org">Shyam Mani</mail>
20</author> 20</author>
21<author title="Editor"> 21<author title="Editor">
22 <mail link="rane@gentoo.org">Łukasz Damentko</mail> 22 <mail link="rane@gentoo.org">Łukasz Damentko</mail>
23</author> 23</author>
24 24
25<abstract> 25<abstract>
26This guide will explain how to successfully install a host Bluetooth device, 26This guide will explain how to successfully install a host Bluetooth device,
27configure the kernel properly, explain all the possibilities that the Bluetooth 27configure the kernel properly, explain all the possibilities that the Bluetooth
28interconnection offers and how to have some fun with Bluetooth. 28interconnection offers and how to have some fun with Bluetooth.
29</abstract> 29</abstract>
30 30
31<!-- The content of this document is licensed under the CC-BY-SA license --> 31<!-- The content of this document is licensed under the CC-BY-SA license -->
32<!-- See http://creativecommons.org/licenses/by-sa/2.5 --> 32<!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
33<license/> 33<license/>
34 34
35<version>1.0</version> 35<version>1.10</version>
36<date>2005-08-25</date> 36<date>2007-10-21</date>
37 37
38<chapter id="introduction"> 38<chapter id="introduction">
39<title>Introduction</title> 39<title>Introduction</title>
40<section> 40<section>
41<title>What is Bluetooth?</title> 41<title>What is Bluetooth?</title>
106<body> 106<body>
107 107
108<p> 108<p>
109As the latest Linux stable kernel is 2.6, the configuration will be done for 109As the latest Linux stable kernel is 2.6, the configuration will be done for
110these series of the kernel. Most Bluetooth devices are connected to a USB port, 110these series of the kernel. Most Bluetooth devices are connected to a USB port,
111so USB will be enabled too. If you want, you can use hotplugging in case you 111so USB will be enabled too. Please refer to the <uri
112want to use modules instead of compiling support built into the kernel. Please,
113refer to the <uri link="/doc/en/usb-guide.xml"> Gentoo Linux USB Guide</uri>. 112link="/doc/en/usb-guide.xml"> Gentoo Linux USB Guide</uri>.
114</p> 113</p>
115 114
116<pre caption="Configuration for 2.6 kernels"> 115<pre caption="Configuration for 2.6 kernels">
117Device Drivers ---&gt;
118 Networking Support ---&gt; 116Networking ---&gt;
119 117
120&lt;*&gt; Bluetooth subsystem support ---&gt; 118&lt;*&gt; Bluetooth subsystem support ---&gt;
121 119
122--- Bluetooth subsystem support 120--- Bluetooth subsystem support
123&lt;M&gt; L2CAP protocol support 121&lt;M&gt; L2CAP protocol support
142<comment>(The four drivers below are for PCMCIA Bluetooth devices and will only 140<comment>(The four drivers below are for PCMCIA Bluetooth devices and will only
143show up if you have also selected PCMCIA support in your kernel.)</comment> 141show up if you have also selected PCMCIA support in your kernel.)</comment>
144&lt;M&gt; HCI DTL1 (PC Card) driver 142&lt;M&gt; HCI DTL1 (PC Card) driver
145&lt;M&gt; HCI BT3C (PC Card) driver 143&lt;M&gt; HCI BT3C (PC Card) driver
146&lt;M&gt; HCI BlueCard (PC Card) driver 144&lt;M&gt; HCI BlueCard (PC Card) driver
147&lt;M&gt; HCI UART (PC Card) device driver 145&lt;M&gt; HCI UART (PC Card) device driver
148<comment>(The driver below is intended for HCI Emulation software.)</comment> 146<comment>(The driver below is intended for HCI Emulation software.)</comment>
149&lt;M&gt; HCI VHCI (Virtual HCI device) driver 147&lt;M&gt; HCI VHCI (Virtual HCI device) driver
150 148
151<comment>(Move back three levels to Device Drives and then check if USB is 149<comment>(Move back three levels to Device Drives and then check if USB is
152enabled. This is required if you use a Bluetooth dongle, which are mostly USB 150enabled. This is required if you use a Bluetooth dongle, which are mostly USB
178<comment>(One way to check for the device)</comment> 176<comment>(One way to check for the device)</comment>
179# <i>cat /proc/bus/usb/devices | grep -e^[TPD] | grep -e Cls=e0 -B1 -A1</i> 177# <i>cat /proc/bus/usb/devices | grep -e^[TPD] | grep -e Cls=e0 -B1 -A1</i>
180<comment>(The Cls=e0(unk. ) identifies the Bluetooth adapter.)</comment> 178<comment>(The Cls=e0(unk. ) identifies the Bluetooth adapter.)</comment>
181T: Bus=02 Lev=02 Prnt=03 Port=00 Cnt=01 Dev#= 4 Spd=12 MxCh= 0 179T: Bus=02 Lev=02 Prnt=03 Port=00 Cnt=01 Dev#= 4 Spd=12 MxCh= 0
182D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1 180D: Ver= 1.10 Cls=e0(unk. ) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
183P: Vendor=0a12 ProdID=0001 Rev= 5.25 181P: Vendor=0a12 ProdID=0001 Rev= 5.25
184<comment>(Some might show up on lsusb from sys-apps/usbutils)</comment> 182<comment>(Some might show up on lsusb from sys-apps/usbutils)</comment>
185# <i>lsusb</i> 183# <i>lsusb</i>
186Bus 003 Device 002: ID 046d:c00e Logitech, Inc. Optical Mouse 184Bus 003 Device 002: ID 046d:c00e Logitech, Inc. Optical Mouse
187Bus 003 Device 001: ID 0000:0000 185Bus 003 Device 001: ID 0000:0000
188Bus 002 Device 002: ID 0db0:1967 Micro Star International Bluetooth Dongle 186Bus 002 Device 002: ID 0db0:1967 Micro Star International Bluetooth Dongle
206files or the like may need <c>bluez-firmware</c>. 204files or the like may need <c>bluez-firmware</c>.
207</p> 205</p>
208 206
209<pre caption="Installing bluez-libs and bluez-utils"> 207<pre caption="Installing bluez-libs and bluez-utils">
210# <i>emerge net-wireless/bluez-libs net-wireless/bluez-utils</i> 208# <i>emerge net-wireless/bluez-libs net-wireless/bluez-utils</i>
211</pre>
212
213<warn>
214Do not emerge <c>bluez-kernel</c> or <c>bluez-sdp</c> as they will break
215<c>bluez-utils</c>!
216</warn>
217
218<p>
219Additionally, as we have compiled the Bluetooth subsystem as modules, we will
220need hotplug and coldplug, which are explained in the <uri
221link="http://www.gentoo.org/doc/en/usb-guide.xml#doc_chap4_sect2">Gentoo Linux
222USB Guide</uri>.
223</p>
224
225<pre caption="Emerging hotplug and coldplug">
226# <i>emerge hotplug coldplug</i>
227# <i>rc-update add coldplug boot</i>
228</pre> 209</pre>
229 210
230</body> 211</body>
231</section> 212</section>
232<section> 213<section>
249# <i>hciconfig</i> 230# <i>hciconfig</i>
250hci0: Type: USB 231hci0: Type: USB
251 BD Address: 00:01:02:03:04:05 ACL MTU: 192:8 SCO MTU: 64:8 232 BD Address: 00:01:02:03:04:05 ACL MTU: 192:8 SCO MTU: 64:8
252 DOWN 233 DOWN
253 RX bytes:131 acl:0 sco:0 events:18 errors:0 234 RX bytes:131 acl:0 sco:0 events:18 errors:0
254 TX bytes:565 acl:0 sco:0 commands:17 errors:0 235 TX bytes:565 acl:0 sco:0 commands:17 errors:0
255</pre> 236</pre>
256 237
257<p> 238<p>
258This shows that the Bluetooth device has been recognised. As you might have 239This shows that the Bluetooth device has been recognised. As you might have
259noticed the device is <e>DOWN</e>. Let's configure it so that we can bring it 240noticed the device is <e>DOWN</e>. Let's configure it so that we can bring it
262please refer to <c>man hcid.conf</c>. 243please refer to <c>man hcid.conf</c>.
263</p> 244</p>
264 245
265<pre caption="Editing /etc/bluetooth/hcid.conf"> 246<pre caption="Editing /etc/bluetooth/hcid.conf">
266<comment>(Recommended changes to be made to the file are shown)</comment> 247<comment>(Recommended changes to be made to the file are shown)</comment>
248
249# HCId options
250options {
251 # Automatically initialize new devices
252 autoinit yes;
267 253
268<comment>(Change security to "auto")</comment> 254<comment>(Change security to "auto")</comment>
269 # Security Manager mode 255 # Security Manager mode
270 # none - Security manager disabled 256 # none - Security manager disabled
271 # auto - Use local PIN for incoming connections 257 # auto - Use local PIN for incoming connections
272 # user - Always ask user for a PIN 258 # user - Always ask user for a PIN
273 # 259 #
274 security auto; 260 security auto;
275 261
262 # Pairing mode
263 pairing multi;
264
265<comment>(You only need a pin helper if you are using &lt;=bluez-libs-2.x and &lt;=bluez-utils-2.x)
276<comment>(Change pin_helper to use /etc/bluetooth/pin-helper)</comment> 266(Change pin_helper to use /etc/bluetooth/pin-helper)</comment>
277 # PIN helper 267 # PIN helper
278 pin_helper /etc/bluetooth/pin-helper; 268 pin_helper /etc/bluetooth/pin-helper;
269}
279 270
271# Default settings for HCI devices
272device {
280<comment>(Set your device name here, you can call it anything you want)</comment> 273<comment>(Set your device name here, you can call it anything you want)</comment>
281 # Local device name 274 # Local device name
282 # %d - device id 275 # %d - device id
283 # %h - host name 276 # %h - host name
284 name "BlueZ at %h (%d)"; 277 name "BlueZ at %h (%d)";
285 278
279 # Local device class
280 class 0x3e0100;
281
282 # Inquiry and Page scan
283 iscan enable; pscan enable;
284
285 # Default link mode
286 lm accept;
287
288 # Default link policy
289 lp rswitch,hold,sniff,park;
290
286<comment>(Leave as is, if you don't know what exactly these do)</comment> 291<comment>(Leave as is, if you don't know what exactly these do)</comment>
287 # Authentication and Encryption (Security Mode 3) 292 # Authentication and Encryption (Security Mode 3)
288 #auth enable; 293 #auth enable;
289 #encrypt enable; 294 #encrypt enable;
290} 295}
293<p> 298<p>
294After that, we have to configure the Bluetooth device PIN. That will help in 299After that, we have to configure the Bluetooth device PIN. That will help in
295pairing this device with another one. 300pairing this device with another one.
296</p> 301</p>
297 302
298<note>
299You can choose from different pin helpers, depending on what you want to use.
300Available pin helpers are: <c>/usr/lib/kdebluetooth/kbluepin</c>
301(net-wireless/kdebluetooth), <c>/usr/bin/bluepin</c> or
302<c>/etc/bluetooth/pin-helper</c> among others.
303</note>
304
305<pre caption="Editing /etc/bluetooth/pin"> 303<pre caption="Editing /etc/bluetooth/pin">
306<comment>(Change 123456 with your desired pin number.)</comment> 304<comment>(Replace 123456 with your desired pin number.)</comment>
307123456 305123456
308</pre> 306</pre>
309 307
310<impo> 308<impo>
311This number (of your choice) must be the same in all your hosts with Bluetooth 309This number (of your choice) must be the same in all your hosts with Bluetooth
312devices so they can be paired. This number must also be kept secret since anyone 310devices so they can be paired. This number must also be kept secret since anyone
313with knowledge of this number can essentially establish connections with your 311with knowledge of this number can essentially establish connections with your
314devices. 312devices.
315</impo> 313</impo>
316 314
315<note>
316If you are using <c>&lt;=bluez-libs-2.x</c> and <c>&lt;=bluez-utils-2.x</c> you
317can choose from different pin helpers, depending on what you want to use.
318Available pin helpers are: <c>/usr/lib/kdebluetooth/kbluepin</c>
319(net-wireless/kdebluetooth), <c>/usr/bin/bluepin</c> or
320<c>/etc/bluetooth/pin-helper</c> among others.
321</note>
322
323<note>
324Beginning with <c>>=bluez-libs-3.x</c> and <c>>=bluez-utils-3.x</c>, pin helpers
325have been replaced by passkey agents. There are a few different graphical
326passkey agents available to help manage your PIN, such as <c>bluez-gnome</c> and
327<c>kdebluetooth</c>. You can also use <c>passkey-agent</c> (found in
328<c>bluez-utils</c>) from the command line.
329</note>
330
317</body> 331</body>
318</section> 332</section>
319<section> 333<section>
320<title>Services configuration</title> 334<title>Services configuration</title>
321<body> 335<body>
334</pre> 348</pre>
335 349
336<p> 350<p>
337Let's be sure that the Bluetooth daemons started correctly. If we can see that 351Let's be sure that the Bluetooth daemons started correctly. If we can see that
338both <c>hcid</c> and <c>sdpd</c> are running, then we configured Bluetooth the 352both <c>hcid</c> and <c>sdpd</c> are running, then we configured Bluetooth the
339right way. After that, we can see if the decices are now up and running with 353right way. After that, we can see if the devices are now up and running with
340the configured options. 354the configured options.
341</p> 355</p>
342 356
343<pre caption="Checking whether Bluetooth daemons started correctly"> 357<pre caption="Checking whether Bluetooth daemons started correctly">
344<comment>(Check to see if the services are running)</comment> 358<comment>(Check to see if the services are running)</comment>
34826054 ? 00:00:00 sdpd 36226054 ? 00:00:00 sdpd
349 363
350# <i>hciconfig -a</i> 364# <i>hciconfig -a</i>
351hci0: Type: USB 365hci0: Type: USB
352 BD Address: 00:0A:0B:0C:0D:0E ACL MTU: 192:8 SCO MTU: 64:8 366 BD Address: 00:0A:0B:0C:0D:0E ACL MTU: 192:8 SCO MTU: 64:8
353 UP RUNNING PSCAN ISCAN AUTH ENCRYPT 367 UP RUNNING PSCAN ISCAN
354 RX bytes:125 acl:0 sco:0 events:17 errors:0 368 RX bytes:125 acl:0 sco:0 events:17 errors:0
355 TX bytes:565 acl:0 sco:0 commands:17 errors:0 369 TX bytes:565 acl:0 sco:0 commands:17 errors:0
356 Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00 370 Features: 0xff 0xff 0x0f 0x00 0x00 0x00 0x00 0x00
357 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 371 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
358 Link policy: RSWITCH HOLD SNIFF PARK 372 Link policy: RSWITCH HOLD SNIFF PARK
389</pre> 403</pre>
390 404
391<pre caption="Scanning for remote devices"> 405<pre caption="Scanning for remote devices">
392# <i>hcitool scan</i> 406# <i>hcitool scan</i>
393Scanning ... 407Scanning ...
394 00:0A:0B:0C:0D:0E Grayhat 408 00:0A:0B:0C:0D:0E Grayhat
395</pre> 409</pre>
396 410
397<pre caption="Inquiring remote devices"> 411<pre caption="Inquiring remote devices">
398# <i>hcitool inq</i> 412# <i>hcitool inq</i>
399Inquiring ... 413Inquiring ...
400 00:0A:0B:0C:0D:0E clock offset: 0x5579 class: 0x72010c 414 00:0A:0B:0C:0D:0E clock offset: 0x5579 class: 0x72010c
401</pre> 415</pre>
402 416
403<p> 417<p>
404Now that we now the MAC address of the remote Bluetooth devices, we can check 418Now that we know the MAC address of the remote Bluetooth devices, we can check
405if we paired them correctly. 419if we paired them correctly.
406</p> 420</p>
407 421
408<pre caption="Running l2ping"> 422<pre caption="Running l2ping">
409# <i>l2ping 00:0A:0B:0C:0D:0E</i> 423# <i>l2ping 00:0A:0B:0C:0D:0E</i>
410Ping: 00:0A:0B:0C:0D:0E from 00:01:02:03:04:05 (data size 20) ... 424Ping: 00:0A:0B:0C:0D:0E from 00:01:02:03:04:05 (data size 20) ...
41120 bytes from 00:0A:0B:0C:0D:0E id 200 time 69.85ms 42520 bytes from 00:0A:0B:0C:0D:0E id 200 time 69.85ms
41220 bytes from 00:0A:0B:0C:0D:0E id 201 time 9.97ms 42620 bytes from 00:0A:0B:0C:0D:0E id 201 time 9.97ms
41320 bytes from 00:0A:0B:0C:0D:0E id 202 time 56.86ms 42720 bytes from 00:0A:0B:0C:0D:0E id 202 time 56.86ms
41420 bytes from 00:0A:0B:0C:0D:0E id 203 time 39.92ms 42820 bytes from 00:0A:0B:0C:0D:0E id 203 time 39.92ms
4154 sent, 4 received, 0% loss 4294 sent, 4 received, 0% loss
416</pre> 430</pre>
417 431
418</body> 432</body>
419</section> 433</section>
420<section> 434<section>
448 462
449 # Bluetooth address of the device 463 # Bluetooth address of the device
450 <comment>(Enter the address of the device you want to connect to)</comment> 464 <comment>(Enter the address of the device you want to connect to)</comment>
451 device 00:0A:0B:0C:0D:0E; 465 device 00:0A:0B:0C:0D:0E;
452 466
453} 467}
454</pre> 468</pre>
455 469
456<p> 470<p>
457After configuring RFCOMM, we can connect to any device. Since we've made the 471After configuring RFCOMM, we can connect to any device. Since we've made the
458required settings to the <path>/etc/bluetooth/rfcomm.conf</path> file, we just 472required settings to the <path>/etc/bluetooth/rfcomm.conf</path> file, we just
482CTRL+C. 496CTRL+C.
483</p> 497</p>
484 498
485<pre caption="Listening for incoming RFCOMM connections"> 499<pre caption="Listening for incoming RFCOMM connections">
486# <i>rfcomm listen 0 1</i> 500# <i>rfcomm listen 0 1</i>
487Waiting for connection on channel 1 501Waiting for connection on channel 1
488</pre> 502</pre>
489 503
490<p> 504<p>
491In a similar way to the connect command, the listen command can receive two 505In a similar way to the connect command, the listen command can receive two
492parameters. The first one explicits the RFCOMM TTY device node (usually 0) that 506parameters. The first one explicits the RFCOMM TTY device node (usually 0) that
493will be used to accept a connection, while the second is the channel that will 507will be used to accept a connection, while the second is the channel that will
494be used. 508be used.
495</p> 509</p>
496 510
497<p> 511<p>
498Each time you call the <c>rfcomm</c> command, you can also specify the physical 512Each time you call the <c>rfcomm</c> command, you can also specify the physical
499device you want to use. Below you can see a small example specifiying the 513device you want to use. Below you can see a small example specifiying the
557<pre caption="bnep IP address configuration"> 571<pre caption="bnep IP address configuration">
558host0 #<i> ifconfig bnep0 192.168.2.1</i> 572host0 #<i> ifconfig bnep0 192.168.2.1</i>
559host1 #<i> ifconfig bnep0 192.168.2.2</i> 573host1 #<i> ifconfig bnep0 192.168.2.2</i>
560 574
561host0 #<i> ifconfig bnep0</i> 575host0 #<i> ifconfig bnep0</i>
562bnep0 Link encap:Ethernet HWaddr 00:0A:0B:0C:0D:0E 576bnep0 Link encap:Ethernet HWaddr 00:0A:0B:0C:0D:0E
563 inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0 577 inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0
564 inet6 addr: fe80::210:60ff:fea3:cb41/64 Scope:Link 578 inet6 addr: fe80::210:60ff:fea3:cb41/64 Scope:Link
565 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 579 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
566 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 580 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
567 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 581 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
568 collisions:0 txqueuelen:1000 582 collisions:0 txqueuelen:1000
569 RX bytes:208 (208.0 b) TX bytes:188 (188.0 b) 583 RX bytes:208 (208.0 b) TX bytes:188 (188.0 b)
570 584
571host1 #<i> ifconfig bnep0</i> 585host1 #<i> ifconfig bnep0</i>
572bnep0 Link encap:Ethernet HWaddr 00:01:02:03:04:05 586bnep0 Link encap:Ethernet HWaddr 00:01:02:03:04:05
573 inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0 587 inet addr:192.168.2.2 Bcast:192.168.2.255 Mask:255.255.255.0
574 inet6 addr: fe80::210:60ff:fea2:dd2a/64 Scope:Link 588 inet6 addr: fe80::210:60ff:fea2:dd2a/64 Scope:Link
575 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 589 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
576 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 590 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
577 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0 591 TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
58964 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=34.0 ms 60364 bytes from 192.168.2.1: icmp_seq=1 ttl=64 time=34.0 ms
59064 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=37.3 ms 60464 bytes from 192.168.2.1: icmp_seq=2 ttl=64 time=37.3 ms
591 605
592--- 192.168.2.1 ping statistics --- 606--- 192.168.2.1 ping statistics ---
5932 packets transmitted, 2 received, 0% packet loss, time 1000ms 6072 packets transmitted, 2 received, 0% packet loss, time 1000ms
594rtt min/avg/max/mdev = 34.045/35.690/37.336/1.656 ms 608rtt min/avg/max/mdev = 34.045/35.690/37.336/1.656 ms
595</pre> 609</pre>
596 610
597</body> 611</body>
598</section> 612</section>
599</chapter> 613</chapter>
635This adds menu entries under Applications &gt; System Tools from where you can 649This adds menu entries under Applications &gt; System Tools from where you can
636easily start up the manager or File sharing to transfer files between devices. 650easily start up the manager or File sharing to transfer files between devices.
637</p> 651</p>
638 652
639<p> 653<p>
640To transfer files (the easy way): 654To transfer files (the easy way):
641</p> 655</p>
642 656
643<ul> 657<ul>
644 <li> 658 <li>
645 From the Phone to the Computer - Send the file from the phone via Bluetooth 659 From the Phone to the Computer - Send the file from the phone via Bluetooth
721 backing up this information and restoring it later, and syncing with the 735 backing up this information and restoring it later, and syncing with the
722 Evolution e-mail client. You will need the <c>irmc</c> USE flag set to 736 Evolution e-mail client. You will need the <c>irmc</c> USE flag set to
723 ensure that <c>multisync</c> has Bluetooth support. 737 ensure that <c>multisync</c> has Bluetooth support.
724 </li> 738 </li>
725 <li> 739 <li>
726 <c>media-plugins/xmms-btexmms</c>: Btexmms is an XMMS plugin that allows 740 <c>net-wireless/opd</c> and <c>net-wireless/ussp-push</c> are command line
727 you to use your Bluetooth-enabled (Sony) Ericsson mobile phone as a remote 741 tools (server and client) that can be used to send files to your mobile
728 control for XMMS. 742 phone.
729 </li> 743 </li>
730</ul> 744</ul>
731 745
732</body> 746</body>
733</section> 747</section>

Legend:
Removed from v.1.2  
changed lines
  Added in v.1.14

  ViewVC Help
Powered by ViewVC 1.1.20