[bluez/bluez] 454ff2: adapter: Trigger profile connection on inbound dev...

[uos-eng <noreply@github.com>]

  Branch: refs/heads/1127225
  Home:   https://github.com/bluez/bluez
  Commit: 454ff2ff75699a2fb88b5ad2ff0b6f99ed923aa3
      https://github.com/bluez/bluez/commit/454ff2ff75699a2fb88b5ad2ff0b6f99ed923aa3
  Author: Chengyi Zhao <chengyi.zhao@qq.com>
  Date:   2026-07-14 (Tue, 14 Jul 2026)

  Changed paths:
    M src/adapter.c

  Log Message:
  -----------
  adapter: Trigger profile connection on inbound device connection

When a bonded device initiates an inbound ACL connection before the
host sends an outbound one (e.g., after resume the remote wins the
race), BlueZ accepts the ACL link via connected_callback() but does
not establish AVDTP/AVCTP profiles. The remote's subsequent L2CAP
connect for PSM 25 fails with "security block" because the link is
not yet encrypted, and the kernel does not retry. The ACL link stays
up with no audio.

Fix: in connected_callback(), call btd_device_connect_services() for
bonded inbound devices. This initiates outbound profile connections
from the host side. Unlike inbound L2CAP, outbound L2CAP is queued
by the kernel until encryption completes, so it survives the race.
Safe when the host already won: the function returns -EBUSY if
dev->connect or dev->pending is set.



To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications