On devices with multiple sensors, lockout should be reset whenever
any strong sensor authenticates.
Bug: 163058911
Test: atest CtsBiometricsTestCases
Change-Id: I4bcdc0279cdaa444e59cf0fac6645d9a67e7d11d
IFace and IFingerprint AIDL interfaces do not require challenge
for resetLockout. Rather, they are time-based. See the HAL interface
for more details.
Bug: 182327296
Test: reset lockout on Pixel4
Test: atest com.android.systemui
Test: atest com.android.server.biometrics
Change-Id: Ibf1130d77e714d15fb9eccd3175027a28de08f7b
1) resetLockoutRequiresHardwareAuthToken is moved to the base
SensorPropertiesinternal class, despite face always requiring
it. This will be clearer, since we are further splitting
resetLockout logic into "challenge-required" (IBiometricsFace@1.0)
and "challenge-less" (IFace@1.0) It would be weird to have
a "resetLockoutRequiresChallenge" property without a
"resetLockoutRequiresHardwareAuthToken" property.
2) Will be adding a resetLockoutRequiresChallenge to
SensorPropertiesInternal in the next CL.
Bug: 182327296
Test: reset lockout on Pixel4
Change-Id: Ifa4b36dc42d91e967506a59d2880f47f61ec6cdf
BrightnessTracker is now global.
Pass in the physicaldisplayid of the primary display device of the
logical display that the display power controller is associated with.
This is so that we can determine the brightness changes for each
physical screen.
Bug: 181767734
Test: manual
Change-Id: Iaebb12ec5fe7785545374cc639d7a345ca469db8
This adds calls that are easier to use for services and providers which
may multiuser aware.
Bug: 162549680
Test: Added callback to another service
Change-Id: Ie8c5c046cd31ae82b89206849a8983d60f0d66c5
- Indicates which int values can be sent via the
EXTRA_CLIENT_AUTHORIZATION_STATE extra
- Explicitly mentions how much time clients have to clean up their state
with a nanoapp so there's no ambiguity.
Fixes: 181350428
Test: presubmits
Change-Id: Id39c233b8678450e3c7687ed2bcb1c1f4516f8d7
Only registered when:
- udfps enrolled
- AOD is not enabled
- quickpick enabled:
adb shell settings put secure doze_quick_pickup_gesture 1
Currently by default, quickpickup is not enabled
On gesture trigger, AOD screen will show for 5 seconds
Test: manual
Bug: 176550666
Change-Id: I804a2590c1d95acad62fbfbc85228ecfc8bfa3ed
WIFI_DISPLAY_STATUS_CHANGED event contains the MAC address of peers.
As the MAC address is PII data, this should be restricted by proper
permission.
Bug: 176541017
Test: install PoC in b/176541017 and check PII data is not leaked.
Change-Id: I36b85f44678fe232486702fa009f5f06d1a7af75
The previous implementation of DeviceStateProviderImpl would report the
current device state as soon as a listener was registered leading to a
series of device state changes on boot as the state of the hardware
becomes known. This changes the implementation to await callbacks before
notifying the listener of a change in device state.
Fixes: 181671216
Test: atest DeviceStateProviderImplTest
Test: atest DeviceStateManagerServiceTest
Test: atest DeviceStateManagerGlobalTest
Change-Id: I3f133b6d7135b829b79c9f225ae52c71061faa3e
Prevent the UDFPS overlay from showing when system dialogs are
expected to be closed. Since the UDFPS affordances are not
actually shown in the application's window, we should nicely
hide the UDFPS overlay together with the system transitions.
1) Adds IUdfpsOverlayControllerCallback for SysUI to notify
FingerprintService of per-session events.
2) Adds AcquisitionClient#onUserCanceled, which notifies the
caller of ERROR_USER_CANCELED, and then cancels the HAL
request
Bug: 178403701
Test: Enroll, swipe up. UDFPS affordances animate away together
with the activity. BiometricScheduler logs also indicate
enrollment canceled.
Test: atest AcquisitionClientTest
Test: atest UdfpsControllerTest
Change-Id: I0b2c9eb20ef0686e426ea12896769e4df077cadb
LightRequest.Builder#setLight was renamed to
LightRequest.Builder#addLight, as metalava check enforce the check for a
getter. ApiChecker CTS test still check the method with API 28, 29, 30 and will fail on:
missing_method: android.hardware.lights.LightsRequest.Builder#setLight(android.hardware.lights.Light, android.hardware.lights.LightState) Error: No method with correct signature found.
Add the method back to SystemApi and annotate it as deprecated.
Bug: 181019981
Test: atest android.signature.cts.api.system.SignatureTest#testSignature
Change-Id: Id05f11ad77c01e26e62eaece78ffc875ec5e72df
Adds methods to BiometricManager to return localized strings that may be
used by apps that utilize biometric authentication. These methods should
provide strings that are appropriate for the specific authenticators
that are present on a device and that will actually be used for
authentication in practice. This should alleviate the issue of apps
needing to use overly broad, less user-friendly strings in order to
cover all possible authentication types that may be used.
Test: atest BiometricManagerTest
Test: Manually checked strings using biometric test app
Bug: 162973174
Bug: 180732913
Change-Id: Icd16d8a3b0339e4a963d47e4eb213fa7df83412c
This change allows using SoundModels with null or empty data.
Test: Manual testing of soundtrigger use-cases.
Testing of null-/empty-data models using SoundTriggerTestService
and mocked HAL.
Fixes: 181103994
Change-Id: I00b3c4e343a81e9f4f4580becf1128fd3ba60b14
state.
This:
1. Renames DeviceStateListener to DeviceStateCallback as there is more
than one method in the callback.
2. Adds a callback to DeviceStateCallback to notify clients about a
change in supported device states.
3. Adds a callback to DeviceStateCallback to notify clients about a
change in non-override state (the state of the device without
considering override requests).
4. Restructures the IDeviceStateManager callback interface to return a
DeviceStateInfo object on successful registration of the callback
instead of triggering callbacks after registation. This simplifies the
callback code paths.
Bug: 159401801
Bug: 154038218
Fixes: 179291575
Test: atest DeviceStateManagerServiceTest
Test: atest DeviceStateManagerGlobalTest
Test: atest DeviceStateInfoTest
Change-Id: I42841de3e19ec0161a8c7b18c5baac0f2c2548bf
Changing class DeviceProductInfo to public class with hidden ctor to expose via
Display#getDeviceProductInfo. Removing the relative address and changing
to connectionToSinkType.
Bug: 179775994
Test: atest CtsDisplayTestCases
Change-Id: I92f32461a054244b75dc4d5ddfd30e9a7968f3dd
Makes the following changes to help messages that will be shown during
traffic light face enrollment:
- Swaps messages for FACE_ACQUIRED_TOO_HIGH and FACE_ACQUIRED_TOO_LOW.
- Changes FACE_ACQUIRED_TILT_TOO_EXTREME message from "turn" to "tilt".
Test: Manually tested traffic light enrollment.
Bug: 179044580
Change-Id: I729cc1ac1909f3181b88d869358a4e9deb6761fd
- Relying on camera capture callbacks to switch appropriate
camera output surface image callbacks can result in timing
issues. For example a capture started callback from a new
capture request can execute before the sequence complete
callback gets scheduled for the old request. This can result
in images from the new request getting redirected to the
wrong/old callback.
Avoid this by using a single image callback instance per
camera output for the entire duration of the capture session
and allow individual images to be redirected to appropriate
handlers on a precise timestamp basis.
- Additionally refactor an odd looking if-else case within
'ImageWriter'.
Bug: 180451857
Bug: 180451435
Test: Camera CTS
Change-Id: Iae497ff2eefacc00ea45ff5e598581156aa64c0d
Rename the apis to be more consistent.
Also expose to test api.
Have the aosp mark that it supports the toggle features by default.
Test: atest CtsSensorPrivacyTestCases
Bug: 162549680
Change-Id: Ib38c16adfc5cec931347e1a1891618983d78248b
