* changes:
Animate panel to transparent if profile is managed
17/n: Show credential UI if setDeviceCredentialAllowed(true) and no biometrics
16/n: Add PIN/Password
15/n: Allow Auth UI to start in credential UI
14/n: Animate to device credential UI when lockout occurs
13/n: persist device credential across configuration changes
12/n: Add LockPatternView for setDeviceCredentialAllowed(true)
11/n: Animate panel to full-screen when "Use Password" is pressed
Removing old confirm device credential logic
am: bd2c67b336 -s ours
am skip reason: change_id I078d28ed81a84e32aaece839a51590364a974481 with SHA1 44e80de8be is in history
Change-Id: I33107ede5da364324a3e009ba5002fdb51a8fb5e
For managed profiles, we need to show the managed device background with
the device admin color theme during credential UI. Since it's shown on
the "background" view behind the panel, we can animate/fade the biometric
view down, and slide in the credential UI on the "background" layer.
Bug: 140127687
Test: manual test with device admin
Test: atest com.android.systemui.biometrics
Change-Id: I2d0a1b4367912e4bf6ddf701ad68fc387501f048
This reverts commit 078fe45552.
Reason for revert: This change introduced a bug and it completely changed the functionality of WiFi data stall detection, e.g., high Tx link speed can easily trigger data stall. We would like to roll back them to restore the normal functionality of Wifi data stall detection.
Bug: 141995185
Change-Id: I024808b580955545b084112c4b14921f038b595f
Merged-In: I078d28ed81a84e32aaece839a51590364a974481
Also, get credential type after userId is set. Otherwise the UI is
incorrect.
Bug: 140127687
Test: atest BiometricServiceTest
Test: manual test with managed profile, one-lock disabled, with/without
fingerprint, and with different types of credentials between
owner and managed profile
Change-Id: Ibaf537acf6190458d093a404d9b20d279937a6cc
Bug: 140127687
Make AuthCredentialView abstract, and have the following subclasses
1) AuthCredentialPatternView
2) AuthCredentialPasswordView
Back button cancels password authentication
Test: manual test with pattern, pin, password
Test: atest com.android.systemui.biometrics
Change-Id: I95e42144616a59827da25d10d063990452714f76
If the user is locked out of biometrics, and
BiometricPrompt#setDeviceCredentialAllowed(true), the user should be
shown the credential UI.
This change gives BiometricService the ability to request SystemUI
to show AuthCredentialView without first showing AuthBiometricView.
Bug: 140127687
Test: atest BiometricServiceTest
Test: atest com.android.systemui.biometrics
Change-Id: Ic26986ba044b7992641676c3d3b99fc1395a45b7
am: 7dc5cc80fe -s ours
am skip reason: change_id I65c71569d0dd8a40bc6fecabb22c5373dd6e806e with SHA1 7fe065eb66 is in history
Change-Id: I88f0f3c777367139ba70bbc716dfa01210e0a7cf
This will avoid pinging the DevicePolicyManager twice.
Fixes: 140060745
Test: logcat, not StrictMode logs
Change-Id: Ib7a411a2ffa21eca62281a922b51dffdf6619352
am: 36329e5725 -s ours
am skip reason: change_id I65c71569d0dd8a40bc6fecabb22c5373dd6e806e with SHA1 249810df2e is in history
Change-Id: I59ee897d7778ff603c5bb96f8968d56f09661d97
am: 273a67d261 -s ours
am skip reason: change_id I65c71569d0dd8a40bc6fecabb22c5373dd6e806e with SHA1 7fe065eb66 is in history
Change-Id: I3db7c28eb045cdc2564d5803b3f41babf810de3d
We had accidental usages of the PermissionChecker for cases where no
private data was provided to the app but the checkPermission API on
the latter also did blame data access on the app. The PermissionChecker
was designed to handle IPC calls and not for generic API checks.
To avoid future accidental incorrect PermissionChecker usages this
change renames the existing APIs of the latter to clearly indicate
that they should be used for data delivery and also adds sibling
methods for doing the same permission checks for preflight purposes.
Also the documentation is improved to furhter assist developers.
In addition, this change fixes accidental permission checker usages
that blame when they should not by using the new preflight flavor
of the permission check APIs.
Test:
atest com.android.settingslib.location.RecentLocationAppsTest
atest CtsPermissionTestCases
added: LocationAccessCheckTest#notificationOnlyForAccessesSinceFeatureWasEnabled
added: LocationAccessCheckTest#noNotificationIfFeatureDisabled
added: LocationAccessCheckTest#noNotificationIfBlamerNotSystemOrLocationProvider
added: LocationAccessCheckTest#testOpeningLocationSettingsDoesNotTriggerAccess
bug:141028068
Exempt-From-Owner-Approval: merge
Change-Id: I65c71569d0dd8a40bc6fecabb22c5373dd6e806e
This way it can be turned on/off without a recompile, and checking the
flag doesn't require a context
Test: adb shell device_config put systemui notifications_use_people_filtering false && adb shell kill $(pid com.android.systemui)
Bug: 140232781
Change-Id: I8ba5e7809dc58e9493397db8447456601a398540
The PIN area can be dragged vertically to retry face auth,
the touch slope was already scaled up to avoid accidental
drags but some users still reported that taps were being
ignored. This CL increases the touch slope size.
Fixes: 140030986
Bug: 141873371
Test: manual
Change-Id: I8db78942797f2c44caf9c9bdc0ec693e6c6a65f9
