[bluez/bluez] 322c39: bap: Start BIG sync after receiving BIGInfo

[bluez/bluez] 322c39: bap: Start BIG sync after receiving BIGInfo

[hadess]

  Branch: refs/heads/master
  Home:   https://github.com/bluez/bluez
  Commit: 322c39a643232643ccd514a8f8dfc9683e3e3f1b
      https://github.com/bluez/bluez/commit/322c39a643232643ccd514a8f8dfc9683e3e3f1b
  Author: Yang Li <yang.li@amlogic.com>
  Date:   2026-07-27 (Mon, 27 Jul 2026)

  Changed paths:
    M profiles/audio/bap.c

  Log Message:
  -----------
  bap: Start BIG sync after receiving BIGInfo

The current implementation starts BIG sync before receiving a BIGInfo
report. According to the Bluetooth Core Specification, BIG sync should
only be initiated after BIGInfo has been received.

Starting BIG sync too early may cause unexpected controller behavior.

Trigger BIG sync from the BIGInfo callback, following the same approach
used by the short PA flow.

Fixes: https://github.com/bluez/bluez/issues/2345


  Commit: 729f96089cf66831d911385623ca932e0c245913
      https://github.com/bluez/bluez/commit/729f96089cf66831d911385623ca932e0c245913
  Author: Bastien Nocera <hadess@hadess.net>
  Date:   2026-07-27 (Mon, 27 Jul 2026)

  Changed paths:
    M .github/workflows/stale.yml

  Log Message:
  -----------
  github: Disable stale bot for triaged bugs

When the "bug" label is set on an issue, don't reap it with the stale
bot, as we've triaged the problem and seen a bug.


Compare: https://github.com/bluez/bluez/compare/89d477bb5494...729f96089cf6

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