| commit | 289f167929cccc74985cdb9dddbe8bfb25290a55 | [log] [tgz] |
|---|---|---|
| author | Michael Wachenschwanz <mwachens@google.com> | Tue Apr 20 16:07:12 2021 -0700 |
| committer | Michael Wachenschwanz <mwachens@google.com> | Tue Apr 20 16:31:15 2021 -0700 |
| tree | d5e013532c426eaa1d9e0d4fe6db299033aa619b | |
| parent | 466a9e2b68e3e9805256a94e7b93aa0a3ee243d3 [diff] |
Handle STOPPED to PAUSED Usage events UsageStatsService wrongly assumed a ACTIVITY_PAUSED event must be preceded by a ACTIVITY_RESUMED event, but there are some scenarios where it is possibly to go directly from STOPPED to PAUSED. Fixes: 182007710 Test: manual (start a pip activity, turn off the screen, and turn it back on. UsageStats logs should not report unexpected events.) Test: atest android.app.usage.cts.UsageStatsTest Change-Id: I609ecb574d8401ab597aa61ba7c3b9d1f4e66827