Bluetooth: update mgmt setup to use secure-connection for LE
The previous mgmt setup no longer working with the latest Raspberry Pi
OS, Linux 5.10.17 + BlueZ 5.50. Without a secure-connection feature
explicitly set, the LE connection initiated by the device may use a
different address type than the one used during bonding, causing the
connection to fail. This patch update uses the secure-connection and
turns off the unnecessary settings.
BUG=b:182302803
TEST=bluetooth_AdapterQuickHealth.AVL passed with Raspberry Pi with
TEST=kernel 5.10, 5.4, and 4.19.
Change-Id: If1726e626a67b656e76d2440f53e96eef4d77ef0
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/chameleon/+/2758408
Tested-by: Michael Sun <michaelfsun@google.com>
Auto-Submit: Michael Sun <michaelfsun@google.com>
Commit-Queue: Michael Sun <michaelfsun@google.com>
Reviewed-by: Daniel Winkler <danielwinkler@google.com>
diff --git a/chameleond/utils/bluetooth_raspi.py b/chameleond/utils/bluetooth_raspi.py
index 4629826..72bfe3b 100644
--- a/chameleond/utils/bluetooth_raspi.py
+++ b/chameleond/utils/bluetooth_raspi.py
@@ -342,9 +342,8 @@
if use_ble:
state_change_cmds = ['sudo btmgmt power off',
'sudo btmgmt le on',
- 'sudo btmgmt privacy on',
'sudo btmgmt bredr off',
- 'sudo btmgmt ssp on',
+ 'sudo btmgmt sc on',
'sudo btmgmt power on']
else:
