Hi Luiz,
On Mon, 2011-08-15 at 05:42 -0400, Luiz Augusto von Dentz wrote:
> Hi Peter,
>
> On Mon, Aug 15, 2011 at 11:21 AM, Luiz Augusto von Dentz
> <luiz.dentz@xxxxxxxxx> wrote:
> > Looks like the device really don't like that we start sending commands
> > while it is the initiator of the connection, afaik we are just
> > following the recommendations from the white paper but since they are
> > only recommendations some implementations may ignore them completely.
> > Retrying should work in this case because it might force the remote
> > stack to enter acceptor mode, but this is only valid when we are
> > acting as A2DP source as a A2DP sink we should probably not retry at
> > all.
>
> It seems there is something calling Audio.Connect in your system since
> device_set_avdtp_timer is only called when auto_connect is set, this
> normally happen only after paring, not sure if that is the case.
I believe auto_connect is being set in ag_confirm (which is the RFCOMM
accept callback) from the default value in manager.c. These 2 trials
didn't involve pairing (let me know if you'd like the complete
captures).
Regards,
Peter Hurley
��.n��������+%������w��{.n�����{��� �^n�r������&��z�ޗ�zf���h���~����������_��+v���)ߣ�
