summaryrefslogtreecommitdiff
path: root/tools/aapt2/java/JavaClassGenerator_test.cpp
diff options
context:
space:
mode:
authorVenkata Jagadeesh Garaga <quic_vgaraga@quicinc.com>2020-03-03 12:45:52 +0530
committerJakub Pawlowski <jpawlowski@google.com>2020-03-04 08:41:32 +0000
commitb0474448d5638311fc5167ebc9eaf66b8a6688aa (patch)
treed63c3ff141404fd3732f26ab50bdd023db03a296 /tools/aapt2/java/JavaClassGenerator_test.cpp
parent2edc5306da96af228ebb971ba15981ef639b69aa (diff)
Title: Auto connection not getting initiated after pairing
Issue: mProfiles list getting corrupted as its not protected with lock and auto connection failing Steps: 1.Turn on BT 2.Scan the remote headset from DUT 3.Initiating pairing to remote device 4.unpair the remote from DUT UI Repeat steps from 2 to 4. Some times auto connection not getting initiated from DUT. RootCause: if mProfiles accessed simultaneously from onUuidChanged and connectAllEnabledProfiles ,its leading to list corruption. Settings not able to initiate Auto connection as mProfiles list shown as empty. Fix: Remove redundant mProfiles empty check in onUuidChanged - mProfiles accessed inside onUuidChanged without syncronization, if mProfiles accessed simultaneously from onUuidChanged and connectAllEnabledProfiles ,it might lead to list corruption. - mProfiles empty check already there in connectAllEnabledProfiles Hence removing mProfiles empty conditional check in onUuidChanged Test: Follow steps above Bug: 150653750 Change-Id: I88aa6a6cd46d264f4dd32db71e413079bbd40779
Diffstat (limited to 'tools/aapt2/java/JavaClassGenerator_test.cpp')
0 files changed, 0 insertions, 0 deletions