diff options
author | Venkata Jagadeesh Garaga <quic_vgaraga@quicinc.com> | 2022-04-14 12:09:22 +0530 |
---|---|---|
committer | Venkata Jagadeesh Garaga <quic_vgaraga@quicinc.com> | 2022-04-25 15:34:49 +0530 |
commit | 22c38ddb34533bcb9fed795ef94fb66959d6cd69 (patch) | |
tree | 09676f5f8e7c808dd822a285a4e92616ed2c8d28 | |
parent | 2da454803208cb9d3123c539edfa504ed320aa48 (diff) |
Pairing: Don't delete bonding devices from dev prop map
When LE scan in backgound , there is chance that APP
dev prop map reaches its max size and hence old entry will be
removed. If bonding device entry remeoved , then user accepted pairing
pop up can' be forwarded to stack as dev entry removed
Hence Don't delete bonding devices from dev prop map
when max entries reached
Change-Id: I6c7faae3c5c5f5fe620c802fa8734cd04dacb016
CRs-Fixed: 3172117
-rw-r--r-- | src/com/android/bluetooth/btservice/RemoteDevices.java | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/src/com/android/bluetooth/btservice/RemoteDevices.java b/src/com/android/bluetooth/btservice/RemoteDevices.java index 471d64945..b82f492f1 100644 --- a/src/com/android/bluetooth/btservice/RemoteDevices.java +++ b/src/com/android/bluetooth/btservice/RemoteDevices.java @@ -271,6 +271,13 @@ final class RemoteDevices { return prop; } } + + BluetoothDevice newdevice = getDevice(Utils.addressToBytes(deleteKey)); + DeviceProperties deviceProperties = getDeviceProperties(newdevice); + if (deviceProperties != null && deviceProperties.isBonding()) { + debugLog("Bonding device " + deleteKey + " Don't remove from property map"); + return prop; + } debugLog("Removing device " + deleteKey + " from property map"); mDevices.remove(deleteKey); } |