From: Brian Rogers <brian_rogers@comcast.net>
To: Mario Limonciello <mario_limonciello@dell.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: SCO headset not working with 4.12
Date: Wed, 15 Oct 2008 02:39:40 -0700 [thread overview]
Message-ID: <48F5BA5C.2080304@comcast.net> (raw)
In-Reply-To: <48EB9FCF.6070907@dell.com>
Mario Limonciello wrote:
> 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.
>
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.
prev parent reply other threads:[~2008-10-15 9:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-07 17:43 SCO headset not working with 4.12 Mario Limonciello
2008-10-15 9:39 ` Brian Rogers [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=48F5BA5C.2080304@comcast.net \
--to=brian_rogers@comcast.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=mario_limonciello@dell.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox