Today, I finally got bluetooth-alsa working properly. I installed the
sbc and plugz packages, and configured my .asoundrc like this:
pcm.headset {
type plug
slave {
pcm headsetx
}
}
pcm.headsetx {
@args [BDADDR TIMEOUT]
@args.BDADDR {
type string
default "00:11:22:33:44:55"
}
@args.TIMEOUT {
type integer
default 6000
}
type sco
bdaddr $BDADDR
timeout $TIMEOUT
}
ctl.headset {
type sco
}
With this setup I can use 'aplay -D headset somefile.wav'. I also got
the newest skype 1.4 beta working with it (this beta finally allows you
to select non-hw alsa outputs).
aoss also seems to work fine when I do 'ALSA_OSS_PCM_DEVICE=headset aoss
mplayer -ao oss somefile.ogg'. The trouble starts when I try to use
teamspeak. When I run 'ALSA_OSS_PCM_DEVICE=headset aoss TeamSpeak', the
headset enables itself for a second, then disables itself again
(headsetd claims that nobody is using the device). I get no sound in
teamspeak, no error message on the console. I find it rather strange
that 'aoss TeamSpeak' seems to work fine (I have sound from my built-in
soundcard).
My question is, how do I find out more about the problem, are there any
more tricks or workarounds to make aoss, TeamSpeak and the sco plugin
work together? Any help is appreciated.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user
