From: Brad Midgley <bmidgley@xmission.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] A2DP w/ Blueant headset
Date: Sun, 05 Feb 2006 01:43:30 -0700 [thread overview]
Message-ID: <43E5BAB2.5030800@xmission.com> (raw)
In-Reply-To: <5bab330d0602041925h53623f50h8560344f37a62d0d@mail.gmail.com>
Nigel
> Brad, I've just cracked it. For some reason the avdtp_discover is not
> returning the codec list straight away
ok--very nice detective work! would you like to give me a unified diff?
i'd like to see it coded to only retransmit when it fails in that
specific way...
thanks
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://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-02-05 8:43 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
2006-02-05 3:25 ` Nigel Sim
2006-02-05 8:43 ` Brad Midgley [this message]
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=43E5BAB2.5030800@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).