Comment 21 for bug 130870
Revision history for this message
| Robert W. Brewer (rwb123) wrote Re: [Bug 130870] Re: Bluetooth headset no longer works [regression] | #21 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
Ok... my bluetooth dongle has a CSR chipset which I believe is the best
supported for SCO on linux. I'm on my second or third dongle since I began
my own journey. :) I have used my headset in full duplex with a small
python app I'm developing. The app uses the ALSA APIs to open the device.
The way the direct ALSA API works is the device is opened once for capture
and once for playback. Before giving up on bluez audio I would try a test
with running aplay and arecord at the same time in different windows with
the same sampling rate, etc. to see if that works. I don't have time to
find an example commandline right now.
I have tried to layer dmix and dsnoop on top of the bluetooth device (via
the .asoundrc) to no avail. dmix balks that the bluetooth plugin is not the
right type of slave device or something. That would have allowed multiple
apps to open the bluetooth device at the same time and would have simplified
some things in my app. Perhaps Twinkle is trying to do that. At some point
I'm hoping that switching to pulseaudio will solve this. It's the next-gen
audio daemon and sounds like it can replace dmix and dsnoop.
On Dec 21, 2007 5:35 PM, Johan Brannlund <email address hidden>
wrote:
> Finally I now *almost* have it working. Adding the line
>
> options hci_usb force_scofix=1
>
> to /etc/modprobe.
> bluetooth-alsa. Also, the bluez audio service works somewhat better than
> before. I can now play back audio using mplayer for instance. However,
> using the headset in duplex mode with the audio service does not work.
> Twinkle can open the device *once* but it actually seems to want to open
> the device three times (for speaker, ringtone and microphone).
>
> Oh well, it's getting there. Robert, can you use your headset to do
> VoIP, for instance with Twinkle?
>
> --
> Bluetooth headset no longer works [regression]
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
--
Robert W. Brewer