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

[Fabien Chevalier <fabchevalier@free.fr>]

Hi Johan,
> To me this sounds like a bug in your headset.

I agree.. however interop experience shows that most a2dp headsets are 
buggy, but all in different ways :-(

  However we should of
> course strive to be interoperable with as many as possible  
> implementations.
> 
> 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? 

Right now : no. But i knwo a guy who knows :-)
I'm gonna check what is the most interoperable way of handling this 
behaviour.

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'm gonna ask a work colleague to know how he solved this issue. Might 
take a week or so, as he's in hollidays :-(

Fabien

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