Wait for remote version information, before deciding Robust Cache support
Currently, GATT service discovery is scheduled immediately after connection to new LE device. Depending on timing of Link Layer, we might not read remote version information before checking for Robust Caching support. In this case, we would assume device doesn't support it. After this patch, we would wait for "remote version information" command to finish, and go back to schedulsed service discovery. This way, we would alawys use Robust Cache when newly connected device supports it. Test: Bond with a set of devices, where both of them have same GATT database hash. Verify service discovery is triggered only once in snoop log. Bug: 293249869 Change-Id: Id87ce6f8aa4a4f23a33d963dbbc28ef0891a6d75
Showing
- system/bta/gatt/bta_gattc_act.cc 68 additions, 16 deletionssystem/bta/gatt/bta_gattc_act.cc
- system/bta/gatt/bta_gattc_cache.cc 6 additions, 0 deletionssystem/bta/gatt/bta_gattc_cache.cc
- system/bta/gatt/bta_gattc_int.h 4 additions, 0 deletionssystem/bta/gatt/bta_gattc_int.h
- system/stack/acl/acl.cc 1 addition, 0 deletionssystem/stack/acl/acl.cc
- system/stack/acl/acl.h 3 additions, 0 deletionssystem/stack/acl/acl.h
- system/stack/acl/btm_acl.cc 23 additions, 0 deletionssystem/stack/acl/btm_acl.cc
- system/stack/include/btm_api.h 10 additions, 0 deletionssystem/stack/include/btm_api.h
- system/test/mock/mock_bta_gattc_api.cc 4 additions, 0 deletionssystem/test/mock/mock_bta_gattc_api.cc
- system/test/mock/mock_stack_acl.cc 5 additions, 0 deletionssystem/test/mock/mock_stack_acl.cc
- system/test/mock/mock_stack_acl.h 9 additions, 0 deletionssystem/test/mock/mock_stack_acl.h
Loading
Please register or sign in to comment