diff options
| author | Kweku Adams <kwekua@google.com> | 2019-01-30 10:55:34 -0800 |
|---|---|---|
| committer | Kweku Adams <kwekua@google.com> | 2019-02-07 18:28:36 -0800 |
| commit | b7ce190aba62bc0e47a8e1b695e49126fd0b360f (patch) | |
| tree | df7ef8324b17c703ce25f8192b4652f496555473 /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | b9218244e61995da9dd47e9bdf8f61dccc2d0eb2 (diff) | |
Ensure AlarmManager is brought out of device idle.
In certain cases, DeviceIdleController would come out of STATE_IDLE but
not properly tell AlarmManager (by removing the IDLE_UNTIL alarm). This
meant that alarms wouldn't go off even though the user may be using the
device.
Manual testing steps:
1. Turn on WAIT_FOR_UNLOCK ('adb shell settings put global device_idle_constants "wait_for_unlock=true"')
2. Enable screen lock
3. Unplug device ('adb shell dumpsys battery unplug')
3. Turn screen off
4. Enter IDLE state (repeat 'adb shell dumpsys deviceidle step' until IDLE)
5. Turn screen on
6. Shake device (or run 'adb shell dumpsys deviceidle motion')
7. Check dumpsys output:
- 'adb shell dumpsys deviceidle get deep' should say "INACTIVE"
- 'adb shell dumpsys alarm' should not have "Idle state mode" in the output
Bug: 118321869
Test: atest com.android.server.DeviceIdleControllerTest
Change-Id: Ie41b5a4bd9f2b386fe709108c39a443bd40fd573
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions