From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] A2DP w/ Blueant headset
Date: Wed, 21 Dec 2005 12:56:52 -0700 [thread overview]
Message-ID: <43A9B384.5040202@xmission.com> (raw)
In-Reply-To: <5bab330d0512201659w8af0301r7fd09cba76c6ca92@mail.gmail.com>
Nigel
Your headset is misbehaving. We are supposed to be able to discover the
stream endpoint id in the reply to the avdtp_discover request.
You could try adding code to work around this problem and guess at the
seid. The seid seems to always be 1 on my headsets.
Brad
> OK, new cvs version, I get this:
> mpg123 --au - /home/nigel/03\ -\ They\ Got\ Lost.mp3 | ./a2play
> 00:0A:56:00:B5:91 -
> subbands = 8 blocks = 16 bitpool = 32
> High Performance MPEG 1.0/2.0/2.5 Audio Player for Layer 1, 2, and 3.
> Version 0.59q (2002/03/23). Written and copyrights by Joe Drew.
> ...
> MPEG 1.0 layer III, 128 kbit/s, 44100 Hz stereo
> len=2048
> Header size=28
> Sample Rate:44100
> Channels:2
> Using address: 00:0A:56:00:B5:91
> Found A2DP Sink
> Found A2DP Sink at the destination
> Connected [imtu 672, omtu 672, flush_to 65535]
> Sent the Stream End Point Discovery Command
> couldn't get avdtp_discover (only 2 bytes read)
>
> On 12/20/05, *Brad Midgley* <bmidgley@xmission.com
> <mailto:bmidgley@xmission.com>> wrote:
>
> Nigel
>
> > A2DP with the bluetooth-alsa project doesn't work with the Blueant
> > stereo headphones, and by looking at this page it appears that it
> might
> > be because these headphones don't support AVDTP
> > (http://www.robertwebbe.nl/extendedA2DP.html
> <http://www.robertwebbe.nl/extendedA2DP.html>) Is this possible?
>
> if I remember my alphabet soup correctly, avdtp is a fundamental part of
> a2dp.
>
> > couldn't get avdtp_discover
> > Sent the Stream End Point Discovery Command
>
> i'm not sure why it can't read this information back. perhaps the
> headset for some reason does not report any supported codecs?
>
> i've improved the debug output somewhat. you could try it again.
>
> brad
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc. Do you grep through
> log files
> for problems? Stop! Download the new AJAX search engine that makes
> searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
> http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
> <http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click>
> _______________________________________________
> Bluez-devel mailing list
> Bluez-devel@lists.sourceforge.net
> <mailto:Bluez-devel@lists.sourceforge.net>
> https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2005-12-21 19:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-20 4:18 [Bluez-devel] A2DP w/ Blueant headset Nigel Sim
2005-12-20 4:49 ` Brad Midgley
2005-12-21 0:59 ` Nigel Sim
2005-12-21 19:56 ` Brad Midgley [this message]
2006-02-05 3:25 ` Nigel Sim
2006-02-05 8:43 ` Brad Midgley
2006-02-05 11:39 ` Nigel Sim
2006-02-06 1:51 ` Brad Midgley
2006-02-06 8:39 ` Brad Midgley
2006-06-28 21:51 ` [Bluez-devel] pin_helper missing? Nelson Murilo
2006-06-28 22:05 ` Claudio Takahasi
2006-06-29 1:03 ` Nelson Murilo
2006-06-29 15:17 ` Nelson Murilo
2006-06-29 16:01 ` Marcel Holtmann
2006-06-29 17:08 ` Nelson Murilo
2006-06-29 17:51 ` Claudio Takahasi
2006-06-29 20:03 ` Nelson Murilo
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=43A9B384.5040202@xmission.com \
--to=bmidgley@xmission.com \
--cc=bluez-devel@lists.sourceforge.net \
/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;
as well as URLs for NNTP newsgroup(s).