Age | Commit message (Collapse) | Author |
|
Test: make
Change-Id: I3abb67e2b022737d2aa0226bb07f3966ad68fff7
|
|
|
|
Move timeout scheduling mechanism from KeyguardUpdateMonitor to
LockSettingsStrongAuth.
Move reporting about successful strong auth unlock from
KeyguardUpdateMonitor#reportSuccessfulStrongAuthUnlockAttempt()
to LockSettingsService#doVerifyCredential() - the latter also
covers work challenge strong auth unlocking.
Test: manual with all types of strong and non-strong auth, including work challenge
Bug: 29825955
Change-Id: I38e51b21e3a455b95e3c857e091fe07ee388c7f8
|
|
Test: Manually tested onDeviceUnlockLockout being called with an actual
TestAgentService implementation.
Notes:
- Active Trust Agents are no longer killed/unbinded from when a temporary
device lockout occurs. Instead, the onDeviceUnlockLockout callback of
the agent is called.
Change-Id: Ifa0984d1d7e5153568334d736e9ebd5a00ef1297
Bug: 34198873
|
|
Bug: 30876804
Test: manual
Change-Id: I9a50ee57d7acef1af866968e67feac7803801a02
|
|
Shows the clock without the date. Also stop
hiding the stack scroller in AoD.
Bug: 30876804
Test: manual
Change-Id: I5f2a8e39be7750493dd8dac83641ac0b96082d0e
|
|
|
|
When user fails an authentification in lockscreen many times,
"Try again in 30 seconds." is displayed and a 30 seconds
timer starts to count backwards.
This lets "Try again in 1 seconds" to be displayed for one second.
Bug: 31078006
Change-Id: I6c7de2b751582bb06a93e583b710f83201da1728
|
|
|
|
Test: Boot non-fp device, observe no wtf
Change-Id: If32b2370413f8bfe1477af52809c76e8c892cafa
Fixes: 32976626
|
|
The fingerprint timeout tracking in KeyguardUpdateMonitor has been
extended with use of StrongAuthTracker.
Test: timeout will be CTS tested, testing of unlocking TBD
Bug: 29825955
Change-Id: I5cc49ef46631c412f2d1db88e68a308322b27027
|
|
- Remove references to ActivityManagerProxy.
- Add isSystemReady to ActivityManager.
Bug: 30977067
Test: cts/hostsidetests/services/activityandwindowmanager/util/run-test android.server.cts
adb shell am instrument -e class com.android.server.am.ActivityManagerTest,com.android.server.am.TaskStackChangedListenerTest \
-w com.android.frameworks.servicestests/android.support.test.runner.AndroidJUnitRunner
Change-Id: I07390b6124fb1515821f5c0b37baf6ae74adc8fa
|
|
Bug: b/28974522
Change-Id: I5f3adf4946ee4ba1e09e4f40afe83c151405972a
|
|
Cleanup:
- Make sure all the state is nicely dumped.
- Remove some unused stuff.
- Fix a flicker when occluded -> unlocked
Bug: 32057734
Change-Id: Id87e26adccef740d608b325c2dc1f6db14dd4ec3
|
|
Fixes a bug where the keyguard message area would reorder clears
after a new message was set, leading to the bouncer prompt reason
not showing.
Change-Id: I33001300d9175c521809cd4fdae5158269245c00
Fixes: 32306174
Test: runtest -x $T/frameworks/base/packages/SystemUI/tests/src/com/android/keyguard/KeyguardMessageAreaTest.java
|
|
|
|
- Remove timinig out of messages. This is no longer
necessary because we do not show the owner and charging
info in that area anymore.
- Remove the "important" parameter, which was equivalent to
clearing the message if false.
Change-Id: I5fae5432724ad90a68f53f678f933c4a15dc6e9b
Fixes: 28270749
Test: manual; reboot device, swipe up, verify message doesn't disappear after 5s
|
|
Test: Make sure you don't get double latency output for a single
action.
Fixes: 32085767
Change-Id: I7f57f974737ce21e8513688a8d5fbf80a1f0571b
|
|
|
|
* changes:
Unlock latency improvements
Add latency tracking for checking PIN (1/2)
|
|
708543b5ff am: d94cc68123 am: 05efd16c46
am: e6f8904cd1
Change-Id: I99478a82c9b9db6147836e6e3ad053f2d767f9a7
|
|
- Move latency fake actions into a central location, LatencyTester
- Add latency test for screen turning on
Change-Id: I8aa3f475d56a4ee7a36b97bd6ece32e60c5851cd
|
|
- Make sure the latency also gets tracked on first unlocked in
which we cancel the AsyncTask.
- Also add it for pattern authentication
Change-Id: Ie1561264b0a3b75c09819ccc6d269e61e367e1be
|
|
Also move tags to Keyguard as we need it in Keyguard.
Change-Id: I718581cb4081830da1c3a2f4ad9b9f0ec6f09ae5
|
|
Change-Id: Ibcd5bab971c82a551623d226e4490b39d32fa8c0
|
|
708543b5ff am: d94cc68123
am: 05efd16c46
Change-Id: Ife64f5db81028f665101d434cd6345ed8dac2d7c
|
|
This commit makes it harder for a users pocket to trigger an MDM
remote wipe, by setting the warning dialog to noncancelable.
With this change the pocket would first need to tap on OK before
being able to attempt to enter a PIN. This mirrors the existing
behaviour of both PIN and PUK warning dialogs.
Test: manual - enable an MDM set to trigger a wipe of the device/user
on unsucessful unlock attempts. Then incorrectly enter your PIN until
the warning dialog appears. The dialog should only be dismissable
by pressing the 'OK' button.
Change-Id: I4d86af555a5d8b226ceffa4711bd5e277db93f1e
|
|
Test: Unlock freshly booted non-FBE device, make sure the transition
is fast as well as the icons have the correct state
Change-Id: I6427427d16edeceb0f410be0b88de601a3dffdb4
Fixes: 31203310
|
|
am: 8249ef437c
Change-Id: Ifaa93b7d4772c46ecb4a301606f29acc2aa8139e
|
|
am: 10691456b8
Change-Id: Ieb3a0da5d5693a186c92ab1c21ba189558207ae3
|
|
am: 316bf54484
Change-Id: Ia1e078cca8e29aa0f36b46daf74ce91ec1a90f48
|
|
|
|
|
|
Also shows the state only once radio is enabled.
Fixes: 30301831
Change-Id: Iaf3b96c3622e20d8ada6e1f6391d6065101fb281
|
|
am: 705442fa7d
Change-Id: I03ebb84119f9cb310882ba9ea90ee1e1d7118d03
|
|
* changes:
Fixed a bug where the dimmed background could be invisible
Fixed an issue where the inline controls where not usable
Added Emergency affordance feature
|
|
Added a service that listens whether emergency affordances
are necessary.
If the they are needed, it adds an option to the
global actions dialog that directly launches the
emergency call and also adds a long-press listener
to the keyguard emergency button.
Test: adb shell settings put global force_emergency_affordance 1 && adb shell settings put global emergency_affordance_number 111112
Fixes: 30404490
Change-Id: Ib96a15da2ef4b568a8d77140ebca6aa6f20f5ddb
|
|
Allows PO and DO configure strong auth timeout for fingerprint.
Bug: 31430135
Change-Id: Ie6451d49aa95527adc3720d9a2a0848f58940510
(cherry picked from commit 8f010dd25d18151cc47accc7d853b4f8f7fe8491)
|
|
|
|
am: 205e105306
Change-Id: Id3fc653d2ee1f01b732aea352c36d3fd63937ab4
|
|
1. When dreaming starts before locking, notifications can remain
pinned. This is because the device is locked without
screen off, and HeadsUp are not escalated.
As a result is the pinned heads up shown behind the bouncer
when unlocking.
In this case touchable bound is limited to headsup bounds,
so the user can't unlock at all.
2. Escalate HeadsUp when bar state changes to KEYGUARD
3. This also fixed a bug where the bouncer isn't touchable
When device is occluded and locked, HeadsUp can appear.
If the user then clicks on the HeadsUp and try to send
pending intent, Bouncer can be shown without expanding
panel.
Bug:30820511
Change-Id: I8604c9d00d839d773b32d8b913dfdcd2ed72f1dd
|
|
- Add onLockedBootComplete callback to UserSwitchObserver.
Bug: 30948225
Test: adb shell am instrument -e class android.multiuser.UserLifecycleTest -w com.android.perftests.multiuser/android.support.test.runner.AndroidJUnitRunner
Change-Id: I87533094805a81fbd85d4f492e637b3304ecd5e2
|
|
am: 90e224bda9
Change-Id: Iea4072a619d6a7ba058da0bd2e8c01d323f29fd1
|
|
We need to do the slow dismissal when the user is locked, and not the
other way around.
Bug: 31203310
Change-Id: I6ad0fc831bd9dc26e7375916a0a091552f7790ae
|
|
Change-Id: If389fa5e9139005766e694bc83ec6a07c025da1b
|
|
Allows PO and DO configure strong auth timeout for fingerprint.
Bug: 29825955
Change-Id: Ie6451d49aa95527adc3720d9a2a0848f58940510
|
|
Test: Tested the first unlock on both FDE and non-FDE device.
Change-Id: Ibfbb9d67fb83456acd7b12bbe2d03a961a998ba9
Fixes: 31203310
|
|
am: 9322632f6a
Change-Id: I9cd7ead4caa2843e3063d55ea357e9e989c72f0e
|
|
If we return to the lockscreen from a FLAG_SHOW_WHEN_LOCKED activity,
there was an additional black flicker as the wallpaper wasn't shown
for a couple of frames. The issue is that we didn't set the wallpaper
flag again, to fix another flicker with lockscreen wallpapers. Now,
we pass the state whether we currently have a lockscreen wallpaper
and if we don't have one, we immediately set the wallpaper flag
again.
Bug: 30829255
Bug: 30883413
Change-Id: I9faeaa77b98eb02058171ce19cf90b43826ebe9e
|
|
am: ed56804385
Change-Id: I89e2f79edf8a8213117f7cb46a2c0438ae6ca874
|