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

Johan Hedberg
2007-08-17T11:42:53Z

Hi Fabien,

On Aug 17, 2007, at 14:28, Fabien Chevalier wrote:
> The issue seems to be that my headset doesn't seem to like very
> much the
> rejection of the start cmd that the daemon sends to him.
> After a while when xmms starts the daemon sends a start cmd, to which
> the headset answers with a start rsp, which should indicate that
> everything is ok... however i hear no sound in the headset
> whatsoever :-(

To me this sounds like a bug in your headset. 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? 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.

Johan