[bluez/bluez] 088de1: shared/bap: Fix not handling read offset

[Remi Pommarel <noreply@github.com>]

  Branch: refs/heads/master
  Home:   https://github.com/bluez/bluez
  Commit: 088de118d17c017d66030384d772395e0e26345d
      https://github.com/bluez/bluez/commit/088de118d17c017d66030384d772395e0e26345d
  Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
  Date:   2025-05-27 (Tue, 27 May 2025)

  Changed paths:
    M src/shared/bap.c

  Log Message:
  -----------
  shared/bap: Fix not handling read offset

Some attributes may need to handle offset other than 0 in case read long
procedure is used, so this properly handles that for PAC_SINK_CHRC_UUID
and PAC_SOURCE_CHRC_UUID.

In addition to PAC record this also uses
gatt_db_attribute_set_fixed_length for attributes that are considered of
fixed size so gatt_db can handle offset directly.

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


  Commit: 2a552b93de8b319a8350b1057be4a53c025ab28e
      https://github.com/bluez/bluez/commit/2a552b93de8b319a8350b1057be4a53c025ab28e
  Author: Remi Pommarel <repk@triplefau.lt>
  Date:   2025-05-27 (Tue, 27 May 2025)

  Changed paths:
    M plugins/policy.c

  Log Message:
  -----------
  policy: Fix service retry counters reset

Control and Target retries counter were reset when service state
goes from CONNECTED to DISCONNECTED, but usually an extra DISCONNECTING
state is reached before going to DISCONNECTED. This causes retry counter
to not being reset in this case, leading to service not being able to
initialize on next connection. Source, sink and HS retry counter were
only reset when limit was reached, moreover HS timer was not removed on
CONNECTED state.

Reset all service retry counter as soon as CONNECTED state is reached to
avoid that. Also remove hs timer to match other services.


Compare: https://github.com/bluez/bluez/compare/b14bfe90ae4e...2a552b93de8b

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