[pulseaudio-discuss] bluetooth, sooooo close I can taste it

Lennart Poettering lennart at poettering.net
Mon Jun 29 14:34:04 PDT 2009


On Sun, 28.06.09 13:26, Brian J. Murrell (brian at interlinx.bc.ca) wrote:

> On Sat, 2009-06-27 at 08:39 -0400, Brian J. Murrell wrote:
> > So, I have pulseaudio 0.9.15 and bluez 0.41 installed and everything
> > seems to look good for getting this headset to work with pulse.
> 
> A couple more observations:
> 
> When I move an audio application to the headset, its output blocks.
> When I move it back to the sound card, it's output resumes.  When I say
> blocks, I really do mean blocks.  I don't just mean that it mutes and
> the application continues to process output... the application actually
> blocks on trying to output sound.

Are you running this in HFP moder? Or HSP? Could you try to to switch
that? (i.e. edit bluez's audio.conf and change one setting, dunno
which, pretty sure you find that with google)

> Further, I also noticed, when output to the headset is attempted, dmesg
> reports:
> 
> [109169.568110] btusb_isoc_complete: hci0 corrupted SCO packet
> [109169.573743] hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
> [109169.581151] hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
> [109169.588604] hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
> [109169.596007] hci_scodata_packet: hci0 SCO packet for unknown connection handle 0
> [109169.603425] hci_scodata_packet: hci0 SCO packet for unknown connection handle 0

Hmm, smells like a faulty dongle. 

This is probably something to discuss on the #bluez irc channel.

Lennart

-- 
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net
http://0pointer.net/lennart/           GnuPG 0x1A015CC4



More information about the pulseaudio-discuss mailing list