linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: yayfortrees <yayfortrees@gmail.com>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Subject: Re: Bluez stopped connecting A2DP sink
Date: Fri, 11 Oct 2019 11:48:54 -0600	[thread overview]
Message-ID: <CAJ0=ZJ0XsqEUuD=Std8676EtgspOZ8yD9TiFUM4gQRAui_WeCw@mail.gmail.com> (raw)
In-Reply-To: <CABBYNZ+3hobO1HkoKru0Z_NXgyPz-6BDqpWr6vEDktAOku8qVA@mail.gmail.com>

Hello,

The patch works, I get the a2dp sink consistently through re-connects now.

I am still seeing the a2dp-sink profile error in the logs, but other
than that everything seems to be fine.

bluetoothd[16493]: src/device.c:device_profile_connected() Headset
Voice gateway Success (0)
bluetoothd[16493]: plugins/policy.c:policy_connect()
/org/bluez/hci0/dev_34_DF_2A_0D_F8_C2 profile a2dp-sink
bluetoothd[16493]: profiles/audio/a2dp.c:a2dp_sink_connect() path
/org/bluez/hci0/dev_34_DF_2A_0D_F8_C2
bluetoothd[16493]: a2dp-sink profile connect failed for
34:DF:2A:0D:F8:C2: Device or resource busy
bluetoothd[16493]: plugins/policy.c:service_cb() Added Headset Voice
gateway reconnect 0

Thanks!

On Fri, Oct 11, 2019 at 6:59 AM Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
>
> Hi,
>
> On Thu, Oct 10, 2019 at 11:13 PM yayfortrees <yayfortrees@gmail.com> wrote:
> >
> > Hello,
> >
> > I've attached debug logs for 5.50 nopatch and 5.50 with the patch.
> >
> > To me it looked like it may be a timing issue - trying to connect the
> > a2dp sink too early. As an experiment I put a sleep(1) at the top of
> > the hs_cb function from your patch and the a2dp sink was connected.
> > With the sleep I still get the "Device or resource busy" error early
> > on, but it does reconnect the a2dp sink later in the connection and
> > things work. It's not consistent though, maybe 1 of 5 attempts would
> > fail to connect the a2dp profile.
>
> Try with the following patch.
>
> > I included that debug log as well.
> >
> > Hope this helps, thanks!
> >
> > On Thu, Oct 10, 2019 at 2:10 AM Luiz Augusto von Dentz
> > <luiz.dentz@gmail.com> wrote:
> > >
> > > Hi,
> > >
> > > On Wed, Oct 9, 2019 at 10:51 AM Luiz Augusto von Dentz
> > > <luiz.dentz@gmail.com> wrote:
> > > >
> > > > Hi,
> > > >
> > > > On Wed, Oct 9, 2019 at 1:56 AM yayfortrees <yayfortrees@gmail.com> wrote:
> > > > >
> > > > > Hello,
> > > > >
> > > > > I've attached btmon traces for 5.50 and 5.51. Thanks for taking a look!
> > > > >
> > > > > Let me know if you need anything else.
> > > >
> > > > Must likely the following error has something to do with it:
> > > >
> > > > = bluetoothd: a2dp-sink profile connect failed for 34:DF:2A:0D:F8:C2:
> > > > Device or resource busy
> > > >
> > > > I will check why this could be happening.
> > >
> > > I tried this one and couldn't reproduce with the headsets I have,
> > > could you please run bluetooth -dn and attach the logs here?
> > >
> > > > > On Tue, Oct 8, 2019 at 4:24 AM Luiz Augusto von Dentz
> > > > > <luiz.dentz@gmail.com> wrote:
> > > > > >
> > > > > > Hi,
> > > > > >
> > > > > > On Mon, Oct 7, 2019 at 10:34 PM yayfortrees <yayfortrees@gmail.com> wrote:
> > > > > > >
> > > > > > > Hello,
> > > > > > >
> > > > > > > I recently upgraded bluez to 5.51 from 5.50 and my headphones stopped
> > > > > > > using the A2DP sink during autoconnect. The headphones instead go to
> > > > > > > HSP/HFP mode and the A2DP sink is disabled in pavucontrol/pactl. The
> > > > > > > A2DP sink will only work when the device is initially paired.
> > > > > > >
> > > > > > > This had worked flawlessly for years. I was able to track down the
> > > > > > > regression to this patch:
> > > > > > > https://www.spinics.net/lists/linux-bluetooth/msg76180.html ([PATCH
> > > > > > > BlueZ] policy: Add logic to connect a Sink). If I apply the patch to
> > > > > > > 5.50, my headphones no longer connect to the A2DP sink, if I remove it
> > > > > > > the problem goes away.
> > > > > > >
> > > > > > > Not sure what else I should include to help track this down. The
> > > > > > > headphones I'm using are Beats Wireless (Solo Bluetooth).
> > > > > > >
> > > > > > > The only relevant log entry I see with the patch applied is:
> > > > > > > a2dp-sink profile connect failed for 34:DF:2A:0D:F8:C2: Device or resource busy
> > > > > >
> > > > > > Can you collect the HCI traces of the problem using btmon? I didn't
> > > > > > expect that to cause any problems, it should in theory solve them but
> > > > > > lets see.
> > > > > >
> > > > > > > Let me know if any other information is needed.
> > > > > > > Thanks.
> > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > Luiz Augusto von Dentz
> > > >
> > > >
> > > >
> > > > --
> > > > Luiz Augusto von Dentz
> > >
> > >
> > >
> > > --
> > > Luiz Augusto von Dentz
>
>
>
> --
> Luiz Augusto von Dentz

      reply	other threads:[~2019-10-11 17:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07 19:30 Bluez stopped connecting A2DP sink yayfortrees
2019-10-08 10:24 ` Luiz Augusto von Dentz
     [not found]   ` <CAJ0=ZJ1pD4dHZe98eZnZ6R-ZBazGip_mrPVV_XjFgThXM0Ebmg@mail.gmail.com>
2019-10-09  7:51     ` Luiz Augusto von Dentz
2019-10-10  8:09       ` Luiz Augusto von Dentz
     [not found]         ` <CAJ0=ZJ17vp_N-P2df6xzVON5yTr0U1v5jk7LTYfrgCpcu6kfBg@mail.gmail.com>
2019-10-11 12:59           ` Luiz Augusto von Dentz
2019-10-11 17:48             ` yayfortrees [this message]

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='CAJ0=ZJ0XsqEUuD=Std8676EtgspOZ8yD9TiFUM4gQRAui_WeCw@mail.gmail.com' \
    --to=yayfortrees@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).