From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] audio & dbus
Date: Thu, 16 Nov 2006 18:18:14 +0100 [thread overview]
Message-ID: <1163697494.5169.72.camel@localhost> (raw)
In-Reply-To: <455C95AB.8030800@xmission.com>
Hi Brad,
> >> void RingHeadset()
> >>
> >> Indicate a single RING to the connected headset.
> >
> > No need to do this. This should be handled automatically via Play or
> > some other method.
>
> Play will always open the sco channel without waiting for the user to
> hit the button so it can't be overloaded to do ringing.
>
> Would you like it better if we used a ringing state instead of sending a
> single ring? Should custom ring (open sco, send ring sound, wait for
> button press) and HSP ring (send RING on rfcomm channel) be combined
> together somehow?
need to check in what states are RING can be sent. I think it would not
be needed, but we will see.
> >> void PressHeadsetButton()
> >>
> >> Indicate a button press to the connected audio
> >> gateway.
> >
> > Unneeded. We are not in the role of a headset.
>
> right. I will save this for org.bluez.AudioGateway or whatever we call it.
>
> That brings up another question. Do you want one interface to do
> handsfree and headset or do we have one interface for each? I was
> imagining combining them but I need to read through HFP to be sure.
We will have one interface for Headset, Handsfree and A2DP. There is no
difference between expect the voice quality.
Regards
Marcel
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2006-11-16 17:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 6:14 [Bluez-devel] audio & dbus Brad Midgley
2006-11-16 10:22 ` Marcel Holtmann
2006-11-16 15:48 ` Brad Midgley
2006-11-16 16:03 ` Marcel Holtmann
2006-11-16 16:17 ` Johan Hedberg
2006-11-16 16:45 ` Brad Midgley
2006-11-16 17:18 ` Marcel Holtmann [this message]
2006-11-17 19:35 ` Brad Midgley
2006-11-17 19:53 ` Brad Midgley
2006-11-16 19:19 ` Brad Midgley
2006-11-16 19:38 ` Fabien Chevalier
2006-11-16 20:45 ` Brad Midgley
2006-11-16 19:27 ` Fabien Chevalier
2006-11-16 20:36 ` Brad Midgley
2006-11-19 17:20 ` Fabien Chevalier
2006-11-20 1:27 ` Brad Midgley
2006-11-21 19:23 ` Fabien Chevalier
2006-11-21 21:02 ` Brad Midgley
2006-11-22 11:09 ` Fabien Chevalier
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=1163697494.5169.72.camel@localhost \
--to=marcel@holtmann.org \
--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