| commit | 2a550ee0aafe6431b24c01e930ddd77971ca0689 | [log] [tgz] |
|---|---|---|
| author | Lais Andrade <lsandrade@google.com> | Wed Aug 26 09:54:51 2020 +0000 |
| committer | Lais Andrade <lsandrade@google.com> | Wed Aug 26 09:54:51 2020 +0000 |
| tree | e21551fa44512e8c93e6da4c6334c69369cffde2 | |
| parent | 1a19435911704c8ef37741e5765df42ac9903e1d [diff] |
Execute DelayedCallback outside CallbackScheduler lock The execution will lock the VibratorService.mLock object to finish the current vibratio, and the CallbackScheduler will require the same lock to start a new vibration. This is currently causing a deadlock. Fix: 166285780 Fix: 163901838 Test: atest CorePerfTests:ViewPerfTest Change-Id: I9631166de3546154ce738c9688fadf3d0442e4d3