Skip to contentSkip to conversation

SCO headset not working with 4.12

DISCUSSION Mario Limonciello 2 participants 2 messages Oct 7, 2008 – Oct 15, 2008 Bluetooth drivers

lore
Share & tools
lore
#0 lore raw

Hi:

I recently upgraded to bluez-4.12 and added in the SCO patch that came shortly after the 4.12 release. It seems that my SCO headset is connecting, and receiving commands for volume levels, etc, but doesn't actually play back any audio. I was trying to use the test/hstest app to verify like this:

./hstest play /usr/share/sounds/alsa/Front_Center.wav 00:19:7F:30:47:AB 1
Voice setting: 0x0060
RFCOMM channel connected
SCO audio channel connected (handle 1, mtu 64)

It just idles there sitting at that until I hit ctrl-c. I've attached bluetoothd -nd output as well.

Regards

Signature · 3 lines
Mario Limonciello
*Dell | Linux Engineering*
[email protected]
#1 lore raw
Quoted 8 lines · Mario Limonciello

Hi:

I recently upgraded to bluez-4.12 and added in the SCO patch that came shortly after the 4.12 release. It seems that my SCO headset is connecting, and receiving commands for volume levels, etc, but doesn't actually play back any audio. I was trying to use the test/hstest app to verify like this:

Quoted 9 lines

./hstest play /usr/share/sounds/alsa/Front_Center.wav 00:19:7F:30:47:AB 1
Voice setting: 0x0060
RFCOMM channel connected
SCO audio channel connected (handle 1, mtu 64)

It just idles there sitting at that until I hit ctrl-c. I've attached bluetoothd -nd output as well.

I've noticed this as well with the bluez 4.12 build that's currently included in Intrepid. My test is to output to the headset using mplayer and the alsa plugin. It doesn't always fail to start playing, but when it does fail I get the same endless delay. But with a few tries, sometimes requiring a restart of headsetd, it will eventually start working, and it usually continues to work.

My Bluetooth device is this:
Bus 003 Device 004: ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth

And my headset is the Jabra BT350.