From: Johan Hedberg <johan.hedberg@gmail.com>
To: Jothikumar Mothilal <Jothikumar.Mothilal@Atheros.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: A2DP issue with latest BlueZ in Ubuntu 9.04
Date: Thu, 9 Jul 2009 10:08:08 +0300 [thread overview]
Message-ID: <20090709070808.GA11972@jh-x301> (raw)
In-Reply-To: <44EE5C37ADC36343B0625A05DD408C485068EDD151@CHEXMB-01.global.atheros.com>
Hi Jothi,
On Wed, Jul 08, 2009, Jothikumar Mothilal wrote:
> I am able to hear songs properly using mplayer.
>
> I have upgraded the BlueZ version 4.44 in the same setup by manual compile.
> A2DP not working...and found following line in bluetoothd daemon output
>
> "bluetoothd[17495]: Invalid seid 0"
>
> Pairing is ok. Mplayer throws an error message.
>
> I am not able to track what is the issue.
> Any once faces such issue? Let me know how to fix this issue.
The "Invalid seid" message is coming from audio/unix.c. The value is
indeed invalid (since in the hcidump your headset reports to have SEID 1
and 6 and bluetoothd configures a stream to SEID 1) and it is being sent
by the UNIX socket client (i.e. your alsa player) to bluetoothd.
The reason why your player is sending invalid data to bluetoothd could be
that you're using an old version of the bluetooth alsa plugin with a new
version of bluez. To fix this make sure that you don't have any old
libasound_module_pcm_bluetooth.so lying around in /usr/lib/alsa-lib or
/usr/local/lib/alsa-lib and install the new version there instead.
Johan
next prev parent reply other threads:[~2009-07-09 7:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 14:32 A2DP issue with latest BlueZ in Ubuntu 9.04 Jothikumar Mothilal
2009-07-08 19:43 ` Luiz Augusto von Dentz
2009-07-09 6:40 ` Jothikumar Mothilal
2009-07-09 7:08 ` Johan Hedberg [this message]
2009-07-09 8:38 ` Jothikumar Mothilal
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=20090709070808.GA11972@jh-x301 \
--to=johan.hedberg@gmail.com \
--cc=Jothikumar.Mothilal@Atheros.com \
--cc=linux-bluetooth@vger.kernel.org \
/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