Ubuntu
bluez package

  1. Bug #327284
  2. Comment #31

Comment 31 for bug 327284

Revision history for this message
Ludovico Cavedon (cavedon) wrote : Re: [Bug 327284] Re: [Jaunty Alpha4] Bluetooth Headset pairs but freezes the system when used

thefluxster wrote:
> Ok, after some further hunting, I found the .deb packaged with Kharmic. I installed it on Jaunty and now I've got it working. Sort of. It's still a bit buggy. For instance, if I close Rhythmbox and then try to reopen and play something again, it may or may not work without reinitializing the bluetooth connection using:
> pactl load-module module-bluetooth-device address=00:0D:3C:BC:56:D9 sink_name="CardoS2" profile="a2dp"

Do you manually have to load module-bluetooth-device? In my case the
module is loaded automatically when the device pairs.

However I also noticed that when an application stops using it, it
disconnects, so I need to push the button on my headset to make it
connect again. However this triggers the loading of
module-bluetooth-device automatically.

This is done by module-bluetooth-discover. Make sure you have this
loaded before connecting the headset.

> 2. Download the Bluez 4.37 .deb package for Kharmic from here:
> https://edge.launchpad.net/ubuntu/karmic/i386/bluez/4.37-0ubuntu1
> Install with dpkg -i <package_name>
> This effectively backports the package, I think... Someone with more experience should probably confirm this. I'm fairly new to Ubuntu/desktop *nix.

The term backporting means rebuilding the packages for the older
distribution. In the case of bluez we are lucky that it does not build
rebuild.

However I filed a bug 370507 asking backporting of bluez 4.37 to jaunty.
Please help to promoting the backport by testing the bluez package I
mentioned in that page (i.e. the bluez package in my ppa) and reporting
to that bug

> 3. Switch your audio settings to "PulseAudio" in your system Sound
> settings - leave Sound Capture set to HDA <type>.

You can also install padevchooser and switch single application to the
headset.

thefluxster wrote:
> Please note that the "a2dp" is the correct Bluetooth profile for my
> headset, but it may not be the right one for yours... Please check your
> Bluetooth headset documentation to find the correct profile information.

in my case the headset is an earphone/mic combination, and my profile is
hsp.
However if the module-bluetooth-discover is doing his job correctly, it
should use the right one automatically.

Thanks for the details!
Ludovico