Bluetooth not working on Linux Mint 10

**Chulbul Pandey** · 10-01-2011

I am trying to use the Google voice on my desktop machine which is running Linux Mint 10 Julia. I guess it is working without any problem until phone rings. Actually when I am able to hear the rings but when it comes to the answer the call then it stops working. I don't have any idea that how it stops working suddenly only when call starts. Before that it works without any issue. Does anybody has any idea that where I might be going wrong?

**Ceesar** · 10-01-2011

Configuration be started after installation of any new Bluetooth service. This is done in the terminal with the command

Code:

  sudo / etc / init.d / bluetooth restart

The packages are installed, when you plug the Bluetooth USB stick normally automatically " hcid "(Host Controller Interface Device) is started. This serves as an interface to the Bluetooth device. If a Bluetooth USB stick is used, can use the command

Code:

  lsusb | grep Bluetooth

In the terminal, to determine whether the key has been detected. It also provided more information on the stick will be displayed. For example, the output of that line is as follows:

Code:

 Bus 003 Device 004: ID 1310:0001 Roper Class 1 Bluetooth Dongle

Even more useful information about the Bluetooth stick is obtained with the command

Code:

  hciconfig - all

The option --all ensures an enhanced information output. For example, the output looks like this:

Code:

hci0: Type: USB
         BD Address: 00:0 B: 0D: 33:8 E: 12 ACL MTU: 120:20 SCO MTU: 64:0
         UP RUNNING PSCAN iSCAN
         RX bytes: 834 acl: 21 sco: 0 events: 51 errors: 0
         TX bytes: 2926 acl: 39 sco: 0 commands: 18 errors: 0
         Features: 0xff 0xff 0x05 0x38 0x18 0x18 0x00 0x00
         Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
         Link policy: HOLD SNIFF PARK RSWITCH
         Link mode: SLAVE ACCEPT
         Name: 'konidesktop-0'
         Class: 0x100100
         Service Classes:
         Device Class: Computer, Uncategorized
         HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subversion: 0x757
         Manufacturer: Silicon Wave (11)

Of particular interest here, the BD hardware address on the second line and the name and the class (Class) are. The name is automatically assigned and is identical to the name of the computer (except for the attached -0). The class specifies what type of Bluetooth device you have.

**Antonio1** · 10-01-2011

With the installation of bluez-utils are in / / bluetooth with three configuration files created etc. Here, some small adjustments. This requires root privileges.

pin : pin in the file is nothing more than a number that is used for identification. During the first contact between the PC and mobile device, this figure is queried and the two devices thus bound together ( pairing ). The default here is 1234, but this can be changed at will. From Ubuntu 7.10 there is no separate file for the pin more. The pin is also found in the file hcid.conf:

Code:

  # Default PIN code for incoming connections
 passkey "1234";

hcid.conf : The file hcid.conf (in new versions also main.conf) is the central configuration file for Bluetooth. Particularly important is the bottom of the entry "class". This should be on a mobile phone

Code:

  class 0x100100;

be set. Otherwise, here you actually make any changes. If there are problems with the so-called "pairing" with your mobile phone or other devices, it is recommended to the entry

Code:

  pin_helper = / usr / bin / bluez-pin 

on 
  pin_helper = / usr / bin / bluepin

rfcomm.conf : Some programs require a serial interface for communication. This is in Bluetooth with rfcomm "made available. This allows the mobile phone to send modem commands. This is needed for example if you want to check the battery level, or go to the Internet via GPRS. When setting up the mobile device is bound by its hardware address to an rfcomm device. Possibly. this also requires a channel is specified. How this works exactly, is explained in the respective instructions for the appropriate software. The file contains rfcomm.conf those rfcomm-devices, which should already be set up during system startup. A very good example is already given in the file.

**Wiro** · 10-01-2011

SDP (Service Discovery Protocol) is used to query the services available on the remote device (Bluetooth profile). Which services the device offers, can be easily done with the command.

Code:

  sdptool browse

. Read If you use multiple Bluetooth devices that are added after the command and a space to have the hardware address of the desired device. Otherwise, all devices are read out. The list can be quite long and include some services also.