From: manuel gysin <gwydion.dot@morrigan.ch>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] BlueZ4.x, headset and oss problem
Date: Wed, 24 Dec 2008 01:21:33 +0100 [thread overview]
Message-ID: <4951808D.8020907@morrigan.ch> (raw)
In-Reply-To: <1230074036.4954.15.camel@californication>
Hi Marcel,
> Hi Manuel,
>
>> I've manged to get my headset running with BlueZ4. Sound and Voice is
>> working very well with Skype.
>>
>> Now I tried to use my headset with teamspeak. I tried to run it with
>> aoss teamspeak, but the problem is now I have no /dev/dspx device for
>> the headset.
>
> I don't even have any idea what /dev/dspx is used for. Remember that all
> Bluetooth audio is virtual and lives in userspace. So if you require a
> kernel device node, then the kernel (meaning ALSA) has to do some magic
> here.
>
> Regards
>
> Marcel
>
>
>
/dev/dspx should be an oss device like /dev/dsp0.
In the old version of BlueZ there was a plugin called snd-bt-sco and
created an entry under /proc/asounds/cards.
With that the oss emulation created a dsp-device of the alsa device. But
the wiki tells that this is no longer needed.
I use a 2.6.26 kernel with "ALSA for SoC audio support" (I know SoC is
not ScO, I think this is not what I'm need).
My problem is now, that I can't use the aoss command cause there is no
card entry for the headset and so no /dev/dspx will be created.
I searched around the internet but find nothing about it. So I don't
know if it a mistake from my side or bluez does not have such a feature.
The man page of aoss told me that I can "fake" such e device with
"pcm.dsp0 { type plug slave.pcm "headset" }"
in ~/.asoundrc.
But this will not work, there is no such routing to the bluetooth device.
Regards
Manuel
PS: I hope my English is not to bad to understand
------------------------------------------------------------------------------
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2008-12-24 0:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-20 12:19 [Bluez-users] BlueZ4.x, headset and oss problem manuel gysin
2008-12-23 23:13 ` Marcel Holtmann
2008-12-24 0:21 ` manuel gysin [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4951808D.8020907@morrigan.ch \
--to=gwydion.dot@morrigan.ch \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.