diff options
| author | 2022-05-24 13:31:57 -0700 | |
|---|---|---|
| committer | 2022-06-01 00:16:08 +0000 | |
| commit | f8287f503e3e6ff4e4cdc83185fb2fc606175481 (patch) | |
| tree | fc0fcc732e838ba738b7e7d587544bc93759ed3a /libs/androidfw/StringPool.cpp | |
| parent | 99945d5d70e0cdbffcc00cdeeb4d8c8d8a2a908e (diff) | |
Consolidate point where ADB is enabled for Test Harness Mode
Test Harness Mode relies on enabling ADB upon boot. However, currently,
there appears to be a race condition when enabling ADB. Test Harness
Mode enables ADB in PHASE_BOOT_COMPLETED, and ADB sets itself up in
PHASE_ACTIVITY_MANAGER_READY, both by writing a setting. It appears that
sometimes, the setting for initializing ADB's state commits *after* the
setting to enable ADB for Test Harness Mode, which means that ADB turns
on for a brief moment, then off until the device is manually fixed.
This changes it so that the AdbService checks the Test Harness Mode
property when initializing ADB state, always enabling ADB on boot if
Test Harness Mode is enabled.
Bug: 232813060
Test: tested with user and userdebug builds, both enable adb correctly
Change-Id: I518415dda275bc3d563820ead611e5f017368c95
(cherry picked from commit dfca3dbdb6b7fd922d78b5776d7da65c30d6f8fb)
Merged-In: I518415dda275bc3d563820ead611e5f017368c95
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions