floss: Fix race between adapter prop change and device prop change
AdapterBondedDevices event would insert the remote device addresses into the bonded list. This event usually comes first and the device prop change event would update the list afterwards. However, it's found that they could come in the reversed order and Floss would "miss" the updated device prop. Bug: 331561532 Tag: #floss Test: mmm packages/modules/Bluetooth Test: Stress tested cl_HID_reports_restart_test.floss, no failure Flag: EXEMPT, Floss-only changes Change-Id: Id37b1adcbd3184a948d8dd2068274e8a0cb3bfea
Loading
Please register or sign in to comment