diff options
| author | 2020-12-10 16:25:29 -0800 | |
|---|---|---|
| committer | 2021-01-19 14:34:53 -0800 | |
| commit | 4aad491d8887c0d9daccaf7d11ddc422e6d5b495 (patch) | |
| tree | 18bdbc30131141c0b9d0e915f001862955d9ccdb /services/coverage/java | |
| parent | eab713e3517d60ea08f63c85d69d1be1acf65c01 (diff) | |
Polish sos gesture behind the lockscreen
Unlike camera, we only want one intent for the emergency action (rather
than a secure / insecure breakdown). The api startActivity didn't work
behind the keyguard (WAI, I believe) so this CL changes that approach
to start the activity more traditionally.
The existing test is unfortunately removed. In its implementation CL,
[ag/12721582] dupin@ and I discussed the best way to test the action
given we would either check the activity was started with the context
[mContext.startActivity] or from the ActivityStarter
[StatusBar#startActivity]. Unfortunately ActivityStarter doesn't work
for our use case given the Keyguard gets raised (what we're trying to
fix in this CL), so we're left with verifying the injected Context gets
called. In theory we could add a wrapper method and verify it gets
called, but that seems next-to-useless.
Bug: 172278542
Fixes: 171084088
Fixes: 175240607
Test: atest StatusBarTest
Change-Id: Idd855be8d8c9fd35691c32bf88b3b9e2cdbc7b50
Diffstat (limited to 'services/coverage/java')
0 files changed, 0 insertions, 0 deletions