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:
~ # modprobe snd-bt-sco
~ # /etc/init.d/bluetooth restart
~ # /etc/init.d/alsa-utils restart
~ # 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:
---------------------------
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_GETCAPABILITIES_REQ
Mar 6 22:43:40 duo audio[6086]: Audio API: sending BT_GETCAPABILITIES_RSP
Mar 6 22:43:40 duo audio[6086]: Audio API: received BT_SETCONFIGURATION_REQ
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/audio/device1: HEADSET_STATE_DISCONNECTED -> HEADSET_STATE_CONNECT_IN_PROGRESS
--------------------------
testing with mplayer
~ % mplayer -ao alsa:device=bluetooth /usr/share/skype/sounds/ContactAuthRequest.wav
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
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/audio/device1: HEADSET_STATE_CONNECT_IN_PROGRESS -> HEADSET_STATE_DISCONNECTED
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/