lucid can't use bluetooth headset
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bluez-utils (Ubuntu) |
Invalid
|
Medium
|
Unassigned | ||
Bug Description
I can't get my BT headset to work with Ubuntu. It works OK on the very same laptop when MS Windows is booted. Headset is Nokia HS-26 and BT is builtin USB device 0a5c:2110 Broadcom Corp.
I have in ~/.asoundrc:
#v+
pcm.bluetooth {
type bluetooth
device 00:13:70:59:F0:3D
}
#v-
when I run "mplayer -ao alsa:device=
#v+
[AO_ALSA] alsa-lib: pcm_bluetooth.
[AO_ALSA] Unable to set hw-parameters: Input/output error
Could not open/initialize audio device -> no sound.
Audio: no sound
#v-
and in daemon.log:
#v+
Mar 4 21:00:23 sandworm audio[6521]: Accepted new client connection on unix socket (fd=9)
Mar 4 21:00:23 sandworm audio[6521]: Audio API: received BT_GETCAPABILIT
Mar 4 21:00:23 sandworm audio[6521]: Audio API: sending BT_GETCAPABILIT
Mar 4 21:00:23 sandworm audio[6521]: Audio API: received BT_SETCONFIGURA
Mar 4 21:00:23 sandworm audio[6521]: config sco - device = 00:13:70:59:F0:3D access_mode = 2
Mar 4 21:00:23 sandworm audio[6521]: State changed /org/bluez/
Mar 4 21:00:23 sandworm NetworkManager: <debug> [1204660823.019636] nm_hal_
Mar 4 21:00:23 sandworm audio[6521]: /org/bluez/
Mar 4 21:00:23 sandworm hcid[6499]: link_key_request (sba=00:
Mar 4 21:00:23 sandworm audio[6521]: connect(): Connection refused (111)
Mar 4 21:00:23 sandworm audio[6521]: config failed
Mar 4 21:00:23 sandworm audio[6521]: Audio API: sending BT_SETCONFIGURA
Mar 4 21:00:23 sandworm audio[6521]: State changed /org/bluez/
Mar 4 21:00:23 sandworm audio[6521]: Unix client disconnected (fd=9)
Mar 4 21:00:24 sandworm NetworkManager: <debug> [1204660824.273623] nm_hal_
#v-
there is no sound. There is no question for passkey. There is no GNOME Popup any kind. There is only misterious line "Mar 4 21:00:23 sandworm audio[6521]: connect(): Connection refused (111) " in logs. Problem persist over reboots and "invoke-rc.d bluetooth restart".
Changed in bluez-utils: | |
assignee: | nobody → kernel-team |
Changed in bluez-utils: | |
assignee: | kernel-team → nobody |
I am getting the same under Hardy.
The headset used to work with Gutsy, and after the update to Hardy it doesn't work anymore.
I have Samsung WEP300.
Making the story short: Unlike the previous reporter, I get a request for the pin, if I remove the pairing. But the headset simply doesn't work anymore.
[...]
Used to work with Skype on Gutsy by doing: d/bluetooth restart d/alsa- utils restart
~ # modprobe snd-bt-sco
~ # /etc/init.
~ # /etc/init.
~ # hcitool cc 00:1D:25:B7:C2:C8
~ # btsco -v -s 00:1D:25:B7:C2:C8
And with ASoundrc I would get only audio (but audio would work):
~ % cat .asoundrc
pcm.bluetooth {
type bluetooth
device 00:1D:25:B7:C2:C8
profile "headset"
}
Now in Hardy, if I use the first method (btsco) Skype will hang!
And with .asoundrc (as above) I get: ------- ------- ------ IES_REQ IES_RSP TION_REQ audio/device1: HEADSET_ STATE_DISCONNEC TED -> HEADSET_ STATE_CONNECT_ IN_PROGRESS ------- ------- -----
-------
Mar 6 22:43:40 duo audio[6086]: Accepted new client connection on unix socket (fd=9)
Mar 6 22:43:40 duo audio[6086]: Audio API: received BT_GETCAPABILIT
Mar 6 22:43:40 duo audio[6086]: Audio API: sending BT_GETCAPABILIT
Mar 6 22:43:40 duo audio[6086]: Audio API: received BT_SETCONFIGURA
Mar 6 22:43:40 duo audio[6086]: config sco - device = 00:1D:25:B7:C2:C8 access_mode = 2
Mar 6 22:43:40 duo audio[6086]: State changed /org/bluez/
-------
testing with mplayer bluetooth /usr/share/ skype/sounds/ ContactAuthRequ est.wav
~ % mplayer -ao alsa:device=
MPlayer 1.0rc2-4.2.3 (C) 2000-2007 MPlayer Team
CPU: Genuine Intel(R) CPU T2300 @ 1.66GHz (Family: 6, Model: 14, Stepping: 8)
CPUflags: MMX: 1 MMX2: 1 3DNow: 0 3DNow2: 0 SSE: 1 SSE2: 1
Compiled with runtime CPU detection.
mplayer: could not connect to socket
mplayer: No such file or directory
Failed to open LIRC support. You will not be able to use your remote control.
When I hit Cntrl-C on the mplayer command. I hear a beep and get this in the daemon.log:
Mar 6 22:43:40 duo audio[6086]: /org/bluez/ audio/device1: Connecting to 00:1D:25:B7:C2:C8 channel 2 audio/device1: HEADSET_ STATE_CONNECT_ IN_PROGRESS -> HEADSET_ STATE_DISCONNEC TED
Mar 6 22:43:58 duo audio[6086]: Unix client disconnected (fd=9)
Mar 6 22:43:58 duo audio[6086]: State changed /org/bluez/