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

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

  ViewVC Help
Powered by ViewVC 1.1.20