diff options
| author | Nikita Ioffe <ioffe@google.com> | 2020-03-31 01:28:35 +0100 |
|---|---|---|
| committer | Nikita Ioffe <ioffe@google.com> | 2020-04-01 14:34:54 +0100 |
| commit | 92116e4129812eccb32d7a20208e03be7ee2ec75 (patch) | |
| tree | fd3b27c1150fb7d47c676c40edfaf04c5b9e152b /trusty/coverage/coverage_test.cpp | |
| parent | 884b570100698ab0f3e1ef9341b98a7053e6e6ed (diff) | |
Properly fail userspace reboot if it's not supported
Previously, after `adb reboot userspace` is called on a device that
doesn't suppor it, init would've logged an error and quietly exit the
shutdown sequence. This was leaving adb handing forever.
With this approach, init will fail setprop
"sys.powerctl=reboot,userspace" in case userspace reboot is not
supported.
Test: adb root
Test: adb setprop init.userspace_reboot.is_supported 0
Test: adb reboot userspace
Test: atest CtsInitTestCases
Bug: 146639622
Change-Id: I1264078f53ed3ff54638c7f3b6846b7437f98ee5
Diffstat (limited to 'trusty/coverage/coverage_test.cpp')
0 files changed, 0 insertions, 0 deletions