Please make bluetooth headset Just Work

[Tobias]

I would like to use my Bluetooth Headset with Gnomemeeting in Ubuntu without
recompiling the kernel or any other commandline tasks.
Some Links:
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=480
http://bluetooth-alsa.sourceforge.net/
http://www.dcs.gla.ac.uk/~jp/snd-bt-sco/

[Andreas Schildbach (schildbach)]

I would second this.

And if possible, any button on the headsets should be able to disconnect the
phone line (if you are using VoIP, say with Linphone) or log out of the
conference server (if you are using a program like TeamSpeak).

The Windows behaviour of just disconnecting the BT connection from the headset
to the driver is not very helpful (you'll still pay phoneline charges for example).

[Tobias (tobias-j)]

Just an other link:
http://udu.wiki.ubuntu.com/BluetoothSupport

[Andreas Schildbach (schildbach)]

I am wondering if this could be considered for the Drake?

[Ben Collins (ben-collins)]

This bug has been flagged because it is old and possibly inactive. It may or may
not be fixed in the latest release (Breezy Badger 5.10). It is being marked as
"NEEDSINFO". In two weeks time, if the bug is not updated back to "NEW" and
validated against Breezy, it will be closed.

This is needed in order to help manage the current bug list for the kernel. We
would like to fix all bugs, but need users to test and help with debugging.

If this change was in error for this bug, please respond and make the
appropriate change (or email <email address hidden> if you cannot make the
change).

Thanks for your help.

[Andreas Schildbach (schildbach)]

I can't believe this bug was flagged NEEDINFO, since there were no questions
asked. Also, it is now already NEW, so we can't "update back to NEW".

As for the enhancement, it is still valid with Breezy.

[Charles Majola (chmj)]

I have looked into providing this fuctionality. So far I haven't found any user
friendly app/tool that can be used. btsco is still premature, at least for hte
non-geek users, however it will be provided in the archives and possible in the
default install for those who can use it. If you have any other useful info,
suggestions, please do provide. Changing status to assigned...

[Charles Majola (chmj)]

forgot to mention, the kernel driver(snd-bt-sco) is already in the kernel

[Andreas Schildbach (schildbach)]

bluez-btsco is now in universe I think, but it seems completely without GUI.
Also, I did not manage to get it working with my Nokia Headset.

[Miles (miles-prower)]

I second this request. I have a Logitech BT headset but I just can't get it to work, whatever wiki I tried to follow.

[Marius Gedminas (mgedmin)]

The BluetoothSupport wiki link does not work for me.

I've had success with a bluetooth headset in Dapper. Here's what I did:

  sudo /etc/init.d/bluez-utils restart
    # workaround for bug 21926:
    # PIN dialog doesn't appear until you
    # restart bluez-utils

  sudo apt-get install bluez-btsco
  sudo modprobe snd-bt-sco
  btsco XX:XX:XX:XX:XX:XX
    # btsco just sits there without saying anything
    # the first time you do this, you should put your
    # headset in pairing mode and type in the correct
    # PIN in the popup dialog on your Ubuntu desktop

Now I can use /dev/dsp1 for applications that use OSS, or choose the headset from a dropdown for applications that can query ALSA for a list of devices (e.g. Ekiga).

When you're done, hit Ctrl+C in the terminal where you started btsco.

[Andres Mujica (andres.mujica)]

hi i've followed this steps with an encore bluettoth dongle and a treo 650 headset.

It worked fine, i could hear music from xmms for a while but it seems to get disconnected.

Also if i try to use kiax or idefisk as phones using /dev/dsp1 this packages died

[Nikolaus Filus (nfilus)]

Hi.
I'm using Dapper upgraded to Edgy (maybe some upgrade problems).
For me the missing PIN request is still a problem and I discovered the following workaround working for me (found at http://www.ubuntuforums.org/archive/index.php/t-210176.html)

HOSTADDR=<bt-address of your dongle>
BTADDR=<bt-address of your headset>
PIN=/etc/bluetooth/pin

if [ -x /var/lib/bluetooth/$HOSTADDR ]; then
rm -r /var/lib/bluetooth/$HOSTADDR
fi;
modprobe snd-bt-sco
hcitool cc $BTADDR
passkey-agent $PIN $BTADDR &
btsco $BTADDR >/dev/null 2>$1 &

/etc/bluetooth/pin:
#!/bin/sh
echo "PIN:0000"

[Matt Zimmerman (mdz)]

I've done a little work with the SCO support in plugz, and have my headset about half working so far. Once I get it fully working, I'll see what can be done to automate the setup for Feisty+1.

[Marcel Holtmann (holtmann)]

This will happen within the next bluez-utils releases. The headsetd from plugz with its ALSA plugins will be merged into the Bluetooth audio service. This is work in progress and should be ready for Feisty+1. The setup of Headset will be done through D-Bus. The API specification for that has already been written.

[zeddock (jim-leaders)]

Where could one go to watch the development? I was surprised that bluetooth was not a working piece of Feisty so if it is close I could test.

Thanx!
zeddock

[Tom Albers (tomalbers-deactivatedaccount)]

Please let me know if I can test someting.

[Xamusk (ronanpaixao)]

I have tried to use a usb bluetooth dongle both in feisty and in gutsy.
The dongle appears to work ok: it scans and finds devices, but the devices doesn't work correctly.
I'm testing with a Motorola HT820 Headset, but everytime I try to make it work, I get a kernel panic.
Usually the panic comes trying the btsco driver. I've had no success with a2dp.
Another problem is that the gnome-bluetooth applet can detect the headset, but when I try to connect to it, it shows an error message saying that it wasn't possible to connect. However that message shows an address obex://[MAC_ADDR], with the MAC of the device. It's interesting to note that it's trying to connect via obex, which I think is only for file transfers, not for audio devices. Moreover, when I make it connect with a2dpd -a <MAC> and ad2pd_ctl Connect, it (gnome-bluetooth-applet) does show the messages and asks for password. Yet, after connected, the device appears in the "Bonded devices" list, but not in any entry in the "Services" tab, not even in the "Audio service" entry.

[Jean-Francois Saucier (jfsaucier)]

I got the kernel panic too, using btsco and .asoundrc file (the new method : http://wiki.bluez.org/wiki/HOWTO/AudioDevices )

Let me know if you find a fix to this...

[Jean-Francois Saucier (jfsaucier)]

Ok, I seem to have solve my problem.

I have changed my bluetooth dongle for a new one and everything work fine at the first try. My old dongle was a bluetooth 1.2 and my new is a bluetooth 2.0.

So, it seem that my headset require a bluetooth 2.0 dongle to not make a kernel panic!

[Rodrigo Linfati (rlinfati)]

look Bug #327284

[Brian Rogers (brian-rogers)]

In Karmic, pulseaudio handles Bluetooth nicely. In the hardware tab of the sound preferences, you'll find any connected headsets and you can set them for SCO or A2DP. Then an output device (and input device for SCO) becomes available and you can switch to them. No command line operations required. This bug probably counts as fixed at this point.

[Jonathan Blackhall (johnny-one-eye)]

Agreed with Brian Rogers, this bug should be marked as fixed in Ubuntu 9.10