| commit | a8cb098fe7457097e2ea0f91662f911a7deea6dd | [log] [tgz] |
|---|---|---|
| author | Gurpreet Ghai <gghai@codeaurora.org> | Mon Dec 16 13:13:28 2019 +0530 |
| committer | Gurpreet Ghai <gghai@codeaurora.org> | Mon Dec 16 13:14:27 2019 +0530 |
| tree | 4c4449a6cc5f73a0de2be1a6519c57ed77210303 | |
| parent | fd41ddf0330246801271ee08e5855384c08146fb [diff] |
BT: Handle Duplicate SHO request from AVRCP - Race condition arise out of UI based SHO and play based SHO can result in duplicate SHO processing for same device. - Earlier this condition was handled at A2DP level. - With new design, this condition is being handled ay entry point. So, A2DP is handling for UI based SHO and AVRCP is handling for play-based SHO. CRs-Fixed: 2588019 Change-Id: I5f01c0135aab3011ab1c60fe8ccd092406c9d381