Do not update connection policies when service discovery fails
Application initiated service discovery starts a 6 second timer to generate an ACTION_UUID intent if service discovery does not conclude. This also results in internal modules, namely PhonePolicy, being updated with again with already known service UUIDs. PhonePolicy should not try to update the connection policies of the already discovered profiles. Test: mmm packages/modules/Bluetooth Flag: com.android.bluetooth.flags.prevent_duplicate_uuid_intent Bug: 340322814 Bug: 361182196 Change-Id: I7669e89cbf15b5fff7c4603142ce78889814411d
Loading
Please register or sign in to comment