From: Bobberino <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 0e78f7: adapter: add DisableDiscoveryOnConnect option for ...
Date: Sat, 18 Apr 2026 07:53:53 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1082799/000000-0e78f7@github.com> (raw)
Branch: refs/heads/1082799
Home: https://github.com/bluez/bluez
Commit: 0e78f7b650be5bc91ed43d289caf346bd0e8b85f
https://github.com/bluez/bluez/commit/0e78f7b650be5bc91ed43d289caf346bd0e8b85f
Author: StefanCondorache <condorachest@gmail.com>
Date: 2026-04-18 (Sat, 18 Apr 2026)
Changed paths:
M src/adapter.c
M src/btd.h
M src/main.c
M src/main.conf
Log Message:
-----------
adapter: add DisableDiscoveryOnConnect option for combo chip coexistence
On systems with combo chips (shared Wi-Fi/Bluetooth antenna), background
LE scanning for auto-connect devices competes with active connections,
causing audio stuttering and Wi-Fi packet loss due to antenna
multiplexing via Packet Traffic Arbitration (PTA).
Add a DisableDiscoveryOnConnect boolean option to the [General] section
of main.conf. When enabled and an active connection exists, the option
suppresses adding devices to the kernel auto-connect list in
adapter_auto_connect_add() on kernels supporting KERNEL_CONN_CONTROL,
and gates trigger_passive_scanning() on older kernels.
The option defaults to false to preserve existing behavior.
Signed-off-by: StefanCondorache <condorachest@gmail.com>
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-04-18 14:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bluez/bluez/push/refs/heads/1082799/000000-0e78f7@github.com \
--to=noreply@github.com \
--cc=linux-bluetooth@vger.kernel.org \
/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