9fdaad5598a35bce58bfc8192f2bf19aa83adbc9 - platform_frameworks_base

commit	9fdaad5598a35bce58bfc8192f2bf19aa83adbc9	[log] [tgz]
author	Lais Andrade <lsandrade@google.com>	Tue Aug 31 18:47:20 2021 +0100
committer	Lais Andrade <lsandrade@google.com>	Thu Sep 02 13:45:52 2021 +0100
tree	37414e9bc095ab7c335e20ccb0c5616a8851cc5e
parent	637cc7dcea50f86d4673c23411741f50a61ada1e [diff]

Set external control to false on VibratorManagerService init

The VibratorManagerService turns off all vibrators during initialization
to handle the scenario where the system server has restarted (e.g. after
being killed by watchdog after a deadlock) but the vibrator hardware was
still performing a previous vibrate command.

This also sets the external control state to false, so the service won't
attemp to vibrate when the hardware is actually set for external
control.

Bug: 197165183
Test: VibratorManagerServiceTest
Change-Id: If4f0df57333fb5863fe9c1e781575634606ee662

services/core/java/com/android/server/vibrator/VibratorController.java[diff]
services/core/java/com/android/server/vibrator/VibratorManagerService.java[diff]
services/tests/servicestests/src/com/android/server/vibrator/FakeVibratorControllerProvider.java[diff]
services/tests/servicestests/src/com/android/server/vibrator/VibratorControllerTest.java[diff]
services/tests/servicestests/src/com/android/server/vibrator/VibratorManagerServiceTest.java[diff]

5 files changed