[bluez/bluez] a95380: device: Fix btd_device_connect_services not discov...

[Luiz Augusto von Dentz <noreply@github.com>]

  Branch: refs/heads/1078371
  Home:   https://github.com/bluez/bluez
  Commit: a9538003a81014b7ddfb4f8effea72d67de69a13
      https://github.com/bluez/bluez/commit/a9538003a81014b7ddfb4f8effea72d67de69a13
  Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
  Date:   2026-04-07 (Tue, 07 Apr 2026)

  Changed paths:
    M src/adapter.c
    M src/device.c

  Log Message:
  -----------
  device: Fix btd_device_connect_services not discovering

btd_device_connect_services would not attempt to discover in case the
selected bearer is BR/EDR and once discover is complete then it shall
proceed with connecting the services.


  Commit: 4013afdfbe12a5ec353d5f7769e4caa1a9947b6c
      https://github.com/bluez/bluez/commit/4013afdfbe12a5ec353d5f7769e4caa1a9947b6c
  Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
  Date:   2026-04-07 (Tue, 07 Apr 2026)

  Changed paths:
    M client/main.c

  Log Message:
  -----------
  client: Prompt user to start scanning on connect command

If connect command don't find the device object make it prompt the
user to start scanning and set discovery filter pattern to given
address and mark it to auto-connect:

[bluetoothctl]> connect XX:XX:XX:XX:XX:XX
Device XX:XX:XX:XX:XX:XX not available
[XX:XX:XX:XX:XX:XX] Scan and connect (yes,no): y
SetDiscoveryFilter success
Discovery started
[NEW] Device XX:XX:XX:XX:XX:XX
[NEW] BREDR /org/bluez/hci0/dev_XX:XX:XX:XX:XX:XX
[CHG] Device XX:XX:XX:XX:XX:XX Connected: yes
[CHG] BREDR XX:XX:XX:XX:XX:XX Connected: yes


Compare: https://github.com/bluez/bluez/compare/a9538003a810%5E...4013afdfbe12

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