From: Luiz Augusto von Dentz <noreply@github.com>
To: linux-bluetooth@vger.kernel.org
Subject: [bluez/bluez] 418306: device: Fix btd_device_connect_services not discov...
Date: Thu, 09 Apr 2026 13:03:04 -0700 [thread overview]
Message-ID: <bluez/bluez/push/refs/heads/master/a73fcb-516099@github.com> (raw)
Branch: refs/heads/master
Home: https://github.com/bluez/bluez
Commit: 418306daec600cdb20afec5763a2a1f2f29f1616
https://github.com/bluez/bluez/commit/418306daec600cdb20afec5763a2a1f2f29f1616
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: c8527a27723baa4acbeaba59e60fd6e28a63425e
https://github.com/bluez/bluez/commit/c8527a27723baa4acbeaba59e60fd6e28a63425e
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
Commit: 44e54e39ae1ac0f95c61e7c0b923bd8a0c163f4c
https://github.com/bluez/bluez/commit/44e54e39ae1ac0f95c61e7c0b923bd8a0c163f4c
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.
Commit: 950853f328610ccc20332f1175413935f8de1aef
https://github.com/bluez/bluez/commit/950853f328610ccc20332f1175413935f8de1aef
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-08 (Wed, 08 Apr 2026)
Changed paths:
M src/shared/gatt-server.c
M src/shared/gatt-server.h
Log Message:
-----------
shared/gatt-server: Add bt_gatt_server_set_permissions
This adds bt_gatt_server_set_permissions which can be used to
enabled/disable permission checking before operations which can be
useful on testing only environment where encryption/pairing is not
desirable/needed.
Commit: 516099a9d40515e8cead446634bc25270152f5b0
https://github.com/bluez/bluez/commit/516099a9d40515e8cead446634bc25270152f5b0
Author: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
Date: 2026-04-08 (Wed, 08 Apr 2026)
Changed paths:
M src/btd.h
M src/device.c
M src/main.c
M src/main.conf
Log Message:
-----------
main.conf: Add GATT.Security option
This adds GATT.Security option which by default is set to auto to
detect if encryption/authentication is required on demand, but if
Testing is set enables the user to enter a desirable security level.
In case the security level is low it then proceeds to disable checking
GATT attribute permissions for server operations.
Compare: https://github.com/bluez/bluez/compare/a73fcbf207d3...516099a9d405
To unsubscribe from these emails, change your notification settings at https://github.com/bluez/bluez/settings/notifications
reply other threads:[~2026-04-09 20:03 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/master/a73fcb-516099@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