| commit | f67a41580ea476da32bdf51f6c3a11630c9fbefb | [log] [tgz] |
|---|---|---|
| author | William Hester <williamhester@google.com> | Wed Oct 07 12:35:56 2020 -0700 |
| committer | William Hester <williamhester@google.com> | Wed Oct 07 12:43:31 2020 -0700 |
| tree | cb16f14ab8425ee6c27268f8154f5474bffd3572 | |
| parent | c64ccdb1ef7b2804d726d479a64ceb37b1add7f5 [diff] |
Directly call 'ctl.restart' on adbd if adb is enabled Rather than disabling adb and relying on the settings ContentObserver to take care of re-enabling adb, just kick adbd ourselves directly. Relying on the ContentObserver appears to cause a race condition on some devices. Test: manual, run adb shell cmd testharness enable on a userdebug device Bug: 170327166 Change-Id: I204857c14251a60886b7023ada717812cbf70c59