Re: [Bluez-devel] New A2DP support : HOWTO ?

[Frederic Dalleau <frederic.dalleau@access-company.com>]

> The reason why the audio service rejects the start command is that  
> STREAMING state should only be entered by request of alsa, since if  
> we have no app to provide audio it's unnecessary to have the headset  
> think it will receive some audio when in fact it wont.
> 
> Do you have any ideas how to solve this? I was thinking that we could  
> accept the start command but immediately afterwards send a suspend  
> command. OTOH this feels a little "hackish". The headsets that I have  
> which are capable of acting in initiator role will simply disconnect  
> when their start command is rejected, so I have not been very happy  
> with the current behavior either.

I had the feeling that start suspend and stop were some basic audio
player controls... Maybe the start command could be used to launch the
audio player and start playback. Then rejecting should only occur if
launching failed.

And acceptor role is mandatory.

Frederic

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel