个人工具

“UbuntuHelp:BluetoothSetup”的版本间的差异

来自Ubuntu中文

跳转至: 导航, 搜索
 
第3行: 第3行:
 
<<Include(Tag/ContentCleanup)>>
 
<<Include(Tag/ContentCleanup)>>
 
== Introduction ==
 
== Introduction ==
[[http://en.wikipedia.org/wiki/Bluetooth|Bluetooth]] is a widely supported local area communications technology for communications with cellphones, headsets, keyboards, mice, PDAs, and storage devices.
+
[http://en.wikipedia.org/wiki/Bluetooth Bluetooth] is a widely supported local area communications technology for communications with cellphones, headsets, keyboards, mice, PDAs, and storage devices.
See also BluetoothRemoteControl and BluetoothAudio on Ubuntu.
+
See also [[UbuntuHelp:BluetoothRemoteControl|BluetoothRemoteControl]] and [[UbuntuHelp:BluetoothAudio|BluetoothAudio]] on Ubuntu.
 
== Requirements ==
 
== Requirements ==
 
For a desktop or laptop without Bluetooth support use a Bluetooth dongle that connects through a USB.
 
For a desktop or laptop without Bluetooth support use a Bluetooth dongle that connects through a USB.
第10行: 第10行:
 
(http://ubuntuforums.org/showthread.php?t=572335
 
(http://ubuntuforums.org/showthread.php?t=572335
 
https://wiki.ubuntu.com/LaptopTestingTeam/DellLatitudeD430#bluetooth)
 
https://wiki.ubuntu.com/LaptopTestingTeam/DellLatitudeD430#bluetooth)
For Dell laptops with a Dell Wireless 355 Bluetooth card where the card is turned off, reenable the card before installation. Go to [[http://support.euro.dell.com/support/topics/global.aspx/support/dsn/en/document?docid=2D785CBB1BBFF5F1E040A68F5B282502|a utility]] in Windows to turn it on before you can reinstall the driver. If you turn the card off in Windows reenable the card so Ubuntu can recognize it.
+
For Dell laptops with a Dell Wireless 355 Bluetooth card where the card is turned off, reenable the card before installation. Go to [http://support.euro.dell.com/support/topics/global.aspx/support/dsn/en/document?docid=2D785CBB1BBFF5F1E040A68F5B282502 a utility] in Windows to turn it on before you can reinstall the driver. If you turn the card off in Windows reenable the card so Ubuntu can recognize it.
 
== Installation and Configuration ==
 
== Installation and Configuration ==
 
'''Before you begin''' open up the terminal and type the following:
 
'''Before you begin''' open up the terminal and type the following:
第38行: 第38行:
 
</nowiki></pre>
 
</nowiki></pre>
 
Review the output of '''hcitool dev''' for all your system's Bluetooth devices.
 
Review the output of '''hcitool dev''' for all your system's Bluetooth devices.
{{https://help.ubuntu.com/community/IconsPage?action=AttachFile&do=get&target=IconExample48.png%7D%7D
+
https://help.ubuntu.com/community/IconsPage?action=AttachFile&do=get&target=IconExample48.png
 
'''hcitool dev''' output:
 
'''hcitool dev''' output:
 
<pre><nowiki>
 
<pre><nowiki>
Devices:
+
  Devices:
 
hci0 00:11:95:00:1A:CF
 
hci0 00:11:95:00:1A:CF
</nowiki></pre>
+
  </nowiki></pre>
 
{i} ''Your Bluetooth device will have a different id.''
 
{i} ''Your Bluetooth device will have a different id.''
 
If the id is all zeros, restart the bluez-utils service and retry.
 
If the id is all zeros, restart the bluez-utils service and retry.
第51行: 第51行:
 
<pre><nowiki>
 
<pre><nowiki>
 
sudo hidd --search
 
sudo hidd --search
 +
 
(If that command doesn't work, try the following:)
 
(If that command doesn't work, try the following:)
hcitool scan
+
  hcitool scan
 
</nowiki></pre>
 
</nowiki></pre>
 
Each device's address has the aa:bb:cc:dd:ee:ff format.
 
Each device's address has the aa:bb:cc:dd:ee:ff format.
 
Hint: If no devices are shown for Edgy Eft (6.10), try the following:
 
Hint: If no devices are shown for Edgy Eft (6.10), try the following:
 
<pre><nowiki>
 
<pre><nowiki>
sudo hciconfig hci0 inqmode 0
+
  sudo hciconfig hci0 inqmode 0
 
</nowiki></pre>
 
</nowiki></pre>
See bug [[https://launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/70718|#70718]]. If this helps, you may add the hciconfig command (without "sudo") to your /etc/rc.local file for a permanent workaround.
+
See bug [https://launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/70718 #70718]. If this helps, you may add the hciconfig command (without "sudo") to your /etc/rc.local file for a permanent workaround.
 
=== Connect Devices for Current Session Only ===
 
=== Connect Devices for Current Session Only ===
 
For a temporary connection, use the address of the device 'aa:bb:cc:dd:ee:ff'
 
For a temporary connection, use the address of the device 'aa:bb:cc:dd:ee:ff'
第96行: 第97行:
 
Your Bluetooth devices should now connect at startup.
 
Your Bluetooth devices should now connect at startup.
 
=== Using Devices as Modems ===
 
=== Using Devices as Modems ===
Refer to page BluetoothDialup
+
Refer to page [[UbuntuHelp:BluetoothDialup|BluetoothDialup]]
 
=== Using audio devices ===
 
=== Using audio devices ===
* Refer to page BluetoothAudio
+
* Refer to page [[UbuntuHelp:BluetoothAudio|BluetoothAudio]]
* For Bluetooth Headsets specifically refer to [[BluetoothHeadset]]
+
* For Bluetooth Headsets specifically refer to [[UbuntuHelp:BluetoothHeadset|BluetoothHeadset]]
 
== Troubleshooting ==
 
== Troubleshooting ==
 
=== "obex://[xx:xx:xx:xx:xx:xx]" is not a valid location. ===
 
=== "obex://[xx:xx:xx:xx:xx:xx]" is not a valid location. ===
第111行: 第112行:
 
sudo hciconfig hci0 auth
 
sudo hciconfig hci0 auth
 
</nowiki></pre>
 
</nowiki></pre>
See [[http://ubuntuforums.org/showthread.php?t=580347|this forum thread]] for information.
+
See [http://ubuntuforums.org/showthread.php?t=580347 this forum thread] for information.
 
==== hcitool scan/dev/inq '''Connection timed out''' Error ====
 
==== hcitool scan/dev/inq '''Connection timed out''' Error ====
 
Reset the adapter:
 
Reset the adapter:

2010年5月19日 (三) 21:45的最新版本

<<Include(Tag/ContentCleanup)>>

Introduction

Bluetooth is a widely supported local area communications technology for communications with cellphones, headsets, keyboards, mice, PDAs, and storage devices. See also BluetoothRemoteControl and BluetoothAudio on Ubuntu.

Requirements

For a desktop or laptop without Bluetooth support use a Bluetooth dongle that connects through a USB. For Dell laptops install the latest drivers from Dell's website in Windows in order for the bluetooth module to work in Linux. (Required for D430 with Gutsy / Hardy and D830 and D630) (http://ubuntuforums.org/showthread.php?t=572335 https://wiki.ubuntu.com/LaptopTestingTeam/DellLatitudeD430#bluetooth) For Dell laptops with a Dell Wireless 355 Bluetooth card where the card is turned off, reenable the card before installation. Go to a utility in Windows to turn it on before you can reinstall the driver. If you turn the card off in Windows reenable the card so Ubuntu can recognize it.

Installation and Configuration

Before you begin open up the terminal and type the following:

sudo apt-get install bluez && sudo apt-get install bluez-utils

Restart the bluetooth server to ensure your pc can communicate with a bluetooth device

sudo /etc/init.d/bluetooth restart

By default the BlueTooth notification icon appears, although the service may not. If the service is not running try the service command, otherwise you can now connect. For jaunty (9:04) and above verify you have a supported adapter connected. When the icon appears, right click and configure your preferences. Devices should auto connect to your PC where you configure your security options. To configure mail for your phone, install the gnome-bluetooth package so the system finds it in the accessories menu. Send a file by right clicking the file and selecting Send-to. To automate, select System --> Preferences --> Sessions. Add a Startup program. For example you can name it, "Bluetooth File Transfer" and in the Command box, enter "gnome-obex-server". Click OK.

Manual Discovery

Open a terminal window and install the required packages with their dependencies:

sudo apt-get install bluez-utils

Connect your Bluetooth device and restart the Bluetooth services:

sudo /etc/init.d/bluez-utils restart

Verify your Bluetooth device is detected along with the appropriate modules. View the lsusb (in case of usb device) output: lsusb output:

Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Review the output of hcitool dev for all your system's Bluetooth devices. IconsPage?action=AttachFile&do=get&target=IconExample48.png hcitool dev output:

  Devices:
	hci0	00:11:95:00:1A:CF
  

{i} Your Bluetooth device will have a different id. If the id is all zeros, restart the bluez-utils service and retry.

Setup Devices

Find Device Addresses

Locate the device address, make the device discoverable (a "Connect" button for keyboards and mice or check the manual) and search for the device by the following:

sudo hidd --search

(If that command doesn't work, try the following:)
  hcitool scan

Each device's address has the aa:bb:cc:dd:ee:ff format. Hint: If no devices are shown for Edgy Eft (6.10), try the following:

  sudo hciconfig hci0 inqmode 0

See bug #70718. If this helps, you may add the hciconfig command (without "sudo") to your /etc/rc.local file for a permanent workaround.

Connect Devices for Current Session Only

For a temporary connection, use the address of the device 'aa:bb:cc:dd:ee:ff'

sudo hidd --connect aa:bb:cc:dd:ee:ff

You can now connect. <!> For a "Can't create HID control channel: Connection refused" error, the discovery period timed out. Try again but enter the command more quickly.

Connect Devices at Startup

To connect automatically, edit the configuration file:

sudo cp /etc/default/bluetooth /etc/default/bluetooth_backup
sudo nano /etc/default/bluetooth

Locate line:

HIDD_ENABLED=0

Change it to:

HIDD_ENABLED=1

Look in the same file for a line close to:

HIDD_OPTIONS="--master --server"

{i} Leave the "--master" command or remove it, it depends on the device. If you have problems with "--master", remove it or vice versa. Add additional "--connect" arguments for the device you want to connect to at startup:

HIDD_OPTIONS="--connect aa:bb:cc:dd:ee:ff --connect aa:bb:cc:dd:ee:ff --connect aa:bb:cc:dd:ee:ff --server"

Save and add HIDP to /etc/modules:

echo hidp | sudo tee -a /etc/modules

Your Bluetooth devices should now connect at startup.

Using Devices as Modems

Refer to page BluetoothDialup

Using audio devices

Troubleshooting

"obex://[xx:xx:xx:xx:xx:xx]" is not a valid location.

If you receive this error in Gutsy enter the following:

sudo apt-get install gnome-vfs-obexftp

Although this gives "Couldn't display "obex://[xx:xx:xx:xx:xx:xx]"." for some. In this case try:

sudo hciconfig hci0 auth

See this forum thread for information.

hcitool scan/dev/inq Connection timed out Error

Reset the adapter:

sudo hciconfig hci0 reset

The hcitool options can now connect and if often required despite an automatic connection setup.

Comments

bluez-gnome Reboot after you install bluez packages even if your dongle is recognized after installation. 2/8/2009 bluez-gnome bug: https://bugs.launchpad.net/ubuntu/+source/bluez-gnome/+bug/285007 Forum page: http://ubuntuforums.org/showthread.php?p=6438656#post6438656