From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] cc13ea: device: Fix btd_device_connect_services not discov...
Date: Wed, 08 Apr 2026 12:42:55 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/1078829/000000-e7cf12@github.com> (raw)
Branch: refs/heads/1078829
Home: https://github.com/bluez/bluez
Commit: cc13ea5b68c31cfd9fa5e143f8c1da3c07230fcf
https://github.com/bluez/bluez/commit/cc13ea5b68c31cfd9fa5e143f8c1da3c07230fcf
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-08 (Wed, 08 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: 218d158cb27c07e5c7295ab2267cbfd0929d798e
https://github.com/bluez/bluez/commit/218d158cb27c07e5c7295ab2267cbfd0929d798e
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-08 (Wed, 08 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
Commit: e7cf124debab534fb301c8b6d7581955e911ce5a
https://github.com/bluez/bluez/commit/e7cf124debab534fb301c8b6d7581955e911ce5a
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-08 (Wed, 08 Apr 2026)
Changed paths:
M client/main.c
Log Message:
-----------
client: Stop discovery when connected with filter.auto_connect
If device was connected via filter.auto_connect method (e.g. connect or
scan.auto_connect) stop the discovery session after the device connects.
Compare: https://github.com/bluez/bluez/compare/cc13ea5b68c3%5E...e7cf124debab
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-04-08 19:42 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/1078829/000000-e7cf12@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