From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] A2DP Profile Certification
Date: Mon, 19 Jun 2006 08:49:16 -0600 [thread overview]
Message-ID: <4496B96C.4060207@xmission.com> (raw)
In-Reply-To: <44965944.6090908@palmsource.com>
Fr=E9d=E9ric
>> This is how we find out a combo headset is taking a voice call.
>> =
> I noticed that my headset stopped streaming when pressing the main =
> button and didn't get back playing after pressing the button again.
> Is that what you mean?
yes this should cover that scenario.
>> We're still missing something here... we don't listen for new control
>> connections from the set. You could look at a2recv.c for code that will
>> listen for new connections. This will be more complicated since you may
>> want to use dbus to start up the media player in response.
>>
> I was wondering how to generate such connections? Simply switch on the =
> headset? Any ideas?
the play button on an avrcp set? i was surprised to find when I ran
"sdptool add AVRTG" then avrecv that the play button did not cause the
set to connect to avrecv. maybe it's really trying to start up a one of
these plain a2dp connection (or maybe not doing anything :)
brad
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-06-19 14:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 15:19 [Bluez-devel] A2DP Profile Certification Frédéric DALLEAU
2006-05-30 15:32 ` Brad Midgley
2006-05-30 15:50 ` Frédéric DALLEAU
2006-05-30 16:30 ` Brad Midgley
2006-05-30 16:33 ` Marcel Holtmann
2006-06-19 5:33 ` Brad Midgley
2006-06-19 7:59 ` Frédéric DALLEAU
2006-06-19 14:49 ` Brad Midgley [this message]
2006-06-19 15:20 ` Frédéric DALLEAU
2006-06-21 16:50 ` Frédéric DALLEAU
2006-06-21 17:24 ` Brad Midgley
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=4496B96C.4060207@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).