From: Thomas Ruprecht <thomas.ruprecht@tu-dresden.de>
To: linux-bluetooth@vger.kernel.org, luiz.von.dentz@intel.com
Subject: Bluez does not connect to A2DP sink
Date: Tue, 7 Jan 2020 09:50:15 +0100 [thread overview]
Message-ID: <d27a0f72-4c78-92ed-4b0a-1010a4b63f0e@tu-dresden.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]
Hi,
I got a problem with bluez since 5.51 that was recently discussed in the
thread https://marc.info/?l=linux-bluetooth&m=157081619423081&w=2: My
headset auto-connects but is not registered as a2dp sink. Unfortunately,
the proposed patch did not solve this issue for my setup.
I also could track down this regression to commit 477ecca (policy: Add
logic to connect a Sink); applying it to 5.50 yields the connection
issues. After that, I applied your patch in commit 52faac4 (audio: Fix
cancelling disconnect timeout), but it did not change. I used only these
two commits on top of version 5.50 to isolate the problem (it is the
same with version 5.51 and 5.52) and gathered the logs of running
`bluetoothd -dn` and `btmon -w` for the three setups:
* version 5.50 (patch-0),
* version 5.50 + 477ecca (patch-1), and
* version 5.50 + 477ecca + 52faac4 (patch-2).
For all three logs I powered the headset on to connect it, waited a few
moments, and then powered off to disconnect. You can find them at
https://gist.github.com/6d733ba9ac6cf04c71625a08e8365178.
@Luiz Augusto von Dentz: Sorry if I sent you this mail multiple times,
it probably got filtered from the mailing list as I attached the logs in
previous attempts.
Please let me know if you need anything else. Thanks.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5204 bytes --]
next reply other threads:[~2020-01-07 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 8:50 Thomas Ruprecht [this message]
2020-01-07 21:51 ` Bluez does not connect to A2DP sink Luiz Augusto von Dentz
2020-01-08 20:51 ` Thomas Ruprecht
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=d27a0f72-4c78-92ed-4b0a-1010a4b63f0e@tu-dresden.de \
--to=thomas.ruprecht@tu-dresden.de \
--cc=linux-bluetooth@vger.kernel.org \
--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).