Separate service discovery and read remote name callback
Long time ago someone decided that using one callback for service search and device search is good idea. Turns out it's a bad idea that's causing service discovery callback when name read callback comes back. This, in turn, causes profiles to not connect properly. To fix this, separate event is introduced for name read. Test: atest net_test_btif_stack Bug: 311217960 Change-Id: I343a585ffcb7b6112b493af1593beca871d70c91
Showing
- system/bta/dm/bta_dm_disc.cc 1 addition, 1 deletionsystem/bta/dm/bta_dm_disc.cc
- system/bta/include/bta_api.h 3 additions, 1 deletionsystem/bta/include/bta_api.h
- system/bta/test/bta_dm_test.cc 1 addition, 0 deletionssystem/bta/test/bta_dm_test.cc
- system/btif/src/btif_dm.cc 9 additions, 4 deletionssystem/btif/src/btif_dm.cc
- system/btif/src/btif_util.cc 1 addition, 0 deletionssystem/btif/src/btif_util.cc
- system/btif/test/btif_core_test.cc 1 addition, 0 deletionssystem/btif/test/btif_core_test.cc
Loading
Please register or sign in to comment