All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brad Midgley <bmidgley@xmission.com>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] audio & dbus
Date: Fri, 17 Nov 2006 12:35:02 -0700	[thread overview]
Message-ID: <455E0EE6.6000402@xmission.com> (raw)
In-Reply-To: <1163697494.5169.72.camel@localhost>

Marcel

>>>> 		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.

It looks like RING could be sent when sco is up but probably is not a 
good idea.

I've been reading through HFP more and I think we need special states 
for both kinds of incoming calls: custom ring and builtin ring. If we 
don't use special states then the use cases are very different--in the 
custom ring case, it means Playing() will be signaled before the call is 
in progress. I'd much rather have Answered() and Playing() always 
signaled together regardless of the ring type used to indicate the call.

Headset hierarchy (experimental)
==============================

Service		org.bluez
Interface	org.bluez.Headset

Methods		void Connect(string identifier)

			Opens the control connection to an audio device.
			Will not open the audio channel until requested
			by the audio plugin or directly from the
			application.

		void Disconnect(string identifier)

			Stops audio if it was playing and closes the
			control connection to the audio device.

		void Play(string identifier)

			Opens the audio stream. Called from the audio
			plugin or from the application if audio is
			routed somewhere other than the daemon (eg
			through PCM, direct to the DSP).

		void Stop(string identifier)

		void Pause(string identifier)

		void Resume(string identifier)

		void SetTimeout(string identifier, uint32 timeout)

			Set the idle Stop for the device.

			Only applicable when audio is routed through the
			daemon. Stop the stream and emit a signal if
			timeout elapses without any audio being sent
			to the daemon from an application. A value of 0
			indicates no idle stop; this is the default.

		uint32 GetTimeout(string identifier)

		uint16 GetSpeakerGain(string identifier)

		uint16 GetMicrophoneGain(string identifier)

		void SetSpeakerGain(string identifier, uint16 gain)

			Gain is 0..15

		void SetMicrophoneGain(string identifier, uint16 gain)

			Gain is 0..15

		void Ring()

			Uses the headset's builtin ringer and go into
			ringing state to indicate an incoming call.

		void CustomRing()

			Brings up the audio connection (similar to the
			playing state) to indicate a custom ring tone
			and go into custom ringing state.

		void CancelRinging()

			Cancel ringing or custom ringing incoming call.

Signals		void Connected()

			Indicate device and profile.

		void Disconnected()
		
			Indicate device and profile.

		void Playing()

			Indicate device and profile.

		void Stopped()

			Indicate device and profile.

		void Paused()

			Indicate device and profile.

		void Resumed()

			Indicate device and profile.

		void Ringing()

			Headset is in ringing state. RING will be
			sent every 3 seconds.

		void CustomRinging()

			Headset is in custom ringing state. Application
			may now send custom ring tone.

		void Answered()

			User answered a call so ringing or custom
			ringing	state will go to playing state.

		void Ignored()

			User ignored a call.

		void Canceled()

			Ringing call was canceled.

		void TimeoutChanged()

			Indicate the new idle, device, profile

		void SpeakerGainChanged()

			Indicate new gain, device, profile.

		void MicrophoneGainChanged()

			Indicate new gain, device, profile.

		void HeadsetButtonPressed()

			Indicates the headset button was pressed.

		void RedialButtonPressed()

			Indicates the headset requested the last number
			redialed.

Brad

-------------------------------------------------------------------------
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

  reply	other threads:[~2006-11-17 19:35 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
2006-11-17 19:35           ` Brad Midgley [this message]
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=455E0EE6.6000402@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.