From: Thomas Ruprecht <thomas.ruprecht@tu-dresden.de>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: "linux-bluetooth@vger.kernel.org"
<linux-bluetooth@vger.kernel.org>,
Luiz Augusto Von Dentz <luiz.von.dentz@intel.com>
Subject: Re: Bluez does not connect to A2DP sink
Date: Wed, 8 Jan 2020 21:51:51 +0100 [thread overview]
Message-ID: <c493d409-a9a6-4504-4a81-5698dc86056b@tu-dresden.de> (raw)
In-Reply-To: <CABBYNZKZsF=gRJh4LHNt9eOXVyfFsH0Et3xvxrPOcyhOYDjPnw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
Hey,
On 1/7/20 10:51 PM, Luiz Augusto von Dentz wrote:
> From the logs it looks like it does connects but it aborts after the
> suspend, so it might not be related to reconnection policy but
> something else that you device do not like, perhaps the suspend being
> initiated or something like it? What headset model is this btw?
sorry, I am not familiar with the bluetooth stack, so I cannot make much
of these logs. The most obvious things I noticed when I took a look into
the diffs between 5.50 and the later versions are:
* in version 5.50 there are no logged calls to
`plugins/policy.c:policy_connect()`, just `plugins/policy.c:service_cb()`
* only in version 5.50 there's a logged call to
`profiles/audio/a2dp.c:confirm_cb()`.
Tomorrow I'll try adding some debug messages into the code that was
added by the patch and see if I can make something of that.
The headset model is JBL E65BTNC.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5204 bytes --]
prev parent reply other threads:[~2020-01-08 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 8:50 Bluez does not connect to A2DP sink Thomas Ruprecht
2020-01-07 21:51 ` Luiz Augusto von Dentz
2020-01-08 20:51 ` Thomas Ruprecht [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=c493d409-a9a6-4504-4a81-5698dc86056b@tu-dresden.de \
--to=thomas.ruprecht@tu-dresden.de \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=luiz.von.dentz@intel.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).