From: Bobberino <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 5c66c0: adapter: add DisableDiscoveryOnConnect option for ...
Date: Sat, 18 Apr 2026 10:04:16 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1082814/000000-68f99e@github.com> (raw)
Branch: refs/heads/1082814
Home: https://github.com/bluez/bluez
Commit: 5c66c091c37c1a360ad4e7dc46c1db337bd85c2d
https://github.com/bluez/bluez/commit/5c66c091c37c1a360ad4e7dc46c1db337bd85c2d
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>
Commit: 68f99e7bf5dcf29b184e1f6700ee97515927582b
https://github.com/bluez/bluez/commit/68f99e7bf5dcf29b184e1f6700ee97515927582b
Author: StefanCondorache <condorachest@gmail.com>
Date: 2026-04-18 (Sat, 18 Apr 2026)
Changed paths:
M src/adapter.c
Log Message:
-----------
adapter: remove connected device from kernel accept list on connect
When DisableDiscoveryOnConnect is enabled, remove the device from the
kernel accept list once it has successfully connected. This prevents
the kernel from continuing background LE scanning for a device that
is already connected, eliminating antenna contention on combo chips
with shared Wi-Fi/Bluetooth radios.
The device is re-added to the accept list upon disconnection to
restore auto-reconnect capability.
Signed-off-by: StefanCondorache <condorachest@gmail.com>
Compare: https://github.com/bluez/bluez/compare/5c66c091c37c%5E...68f99e7bf5dc
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-04-18 17:04 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/1082814/000000-68f99e@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