1) Existing metrics logging-ness can be derived from it
2) EnrollReason is clearer and can be used by other parts of the
system, such as SysUI
3) Do not show progressbar in SysUI if it's "find sensor"
Bug: 179447737
Test: Builds
Change-Id: I84f82b5c81a668e11c1a380e6fa4e3080db53dc9
For apps that are still using FingerprintManager, have the system show
BiometricPrompt when authenticating with a UDFPS sensor. This will
ensure that the user is directed to authenticate on the correct part of
the screen, rather than requiring the app to draw an authentication UI.
Test: FingerprintManager test app, Keyguard, and Settings.
Bug: 174490952
Change-Id: I60ba2dce983812996f6baa44557533575051e476
Merged-In: I60ba2dce983812996f6baa44557533575051e476
Extend Vibrator state and listener support to InputDevice vibrator.
InputDevice users can use the Vibrator listener API to register listener
to vibrator for state change.
Bug: 161634264
Test: atest InputDeviceVibratorTest
Change-Id: I991d3e79ad1734b5c6c99b802aab030bd1597daf
This change promotes DeviceStateManager to a TestApi and exposes three
additional methods:
- getSupportedStates: returns a list of state ids that can be used with
requestState().
- submitRequest: requests that the device enter the supplied state.
- cancelRequest: clears the current requested device state.
to be used initially in CTS tests.
Bug: 177235528
Bug: 177236115
Test: atest DeviceStateManagerServiceTest
Test: atest DeviceStateManagerGlobalTest
Change-Id: Ieae9208420ddecea641a5c44f1610d3cb7071b07
Updates the AIDL face sensor implementation to forward the
onAuthenticationFrame and onEnrollmentFrame events to appropriate
methods in the FaceAuthenticationClient and FaceEnrollClient monitors.
This implementation also converts the hardware AIDL models
AuthenticationFrame and EnrollmentFrame to equivalent framework classes
FaceAuthenticationFrame and FaceEnrollFrame, respectively. This will
allow the framework to define AIDL interface methods with these models.
Test: atest CtsBiometricsTestCases
Bug: 178414967
Change-Id: I093c4396dddab9cb9fb8fd8ec3426b4f3a81abeb
DisplayGroupListeners can now be added and will be informed of addition,
removal, and modification of DisplayGroups.
Bug: 138328918
Test: make
Change-Id: I1dcb52931a798288a0255acd2862f9188f5d83ff
Created new API methods that allow apps to access external battery info
of devices such as bluetooth connected gamepads.
Bug: 161633432
Test: atest android.hardware.input.cts.tests.SonyDualshock4BluetoothTest
atest android.hardware.input.cts.tests.SonyDualshock3UsbTest
Change-Id: Iba59fc9a259818b03c24ee8c2c49601952ed65a3
Merged-In: Iba59fc9a259818b03c24ee8c2c49601952ed65a3
Pass displayId through from brightnesscontroller to
settemporarybrightness on the correct displaypowercontroller.
Bug: 175286226
Test: atest frameworks/base/services/tests/servicestests/src/com/android/server/display
Test: atest ColorModeControls
Change-Id: Ibb65b8c5a70445702b711739551ffb9f727ef450
Attribution tags allow clients to denote if they are providers of
specific data in the system which can be useful when noting permissions
operations later.
Bug: 166846988
Test: compile
Change-Id: I7b0ba9a9ffc6a49f79f80e8078f50625404ddafe
Updates the ContextHub APIs to support notifying clients (either through
traditional callbacks or via PendingIntent) that their ability to
communicate with nanoapps has changed.
Also, adds the ability for clients to discover the permissions required
to communicate with nanoapps so they know whether their initial or
subsequent nanoapp messages will successfully be delivered.
Bug: 166846988
Test: compile
Change-Id: I37e475a1457a031890693d2858b5d5f7de34de26
This interface can be used to listen for addition, removal, or
modification of DisplayGroups.
Bug: 138328918
Test: make
Change-Id: I3a2f39838ab00808816366d2484190b401aabed0
There are two categories of color modes: the standard color modes, which
are defined and implemented in AOSP, and a reserved range of vendor color
modes, which are defined and implemented by the vendor. Currently, there
is no way to distinguish between two vendor's color modes that use the
same value within the reserved range. This will allow OEMs to specify a
hint as to which vendor's color mode definitions were used on the
original device. If the hint from the restored device matches the hint
on the new device, the color mode from the restored device can still be
considered valid for the new device if it is within the vendor reserved
range. If it does not match, the restored device's color mode value is
invalid on the new device, and must be replaced by the default on the
new device.
Bug: 167449433
Test: builds
Change-Id: Ie5ac0a2d783e1ea703e0342f5cdb41dca07d04d4
For TV panel and source devices.
Bug: 169121289
Test: atest HdmiCecLocalDevicePlaybackTest and HdmiCecLocalDeviceTvTest
Change-Id: I6e870a35bcaf55153eaa2274c9f2d8b8f7bf1dda
* changes:
[CEC Configuration] Fix race condition with listeners
[2.0] Disable sending <User Control Pressed> in attempts to change the active source to a 2.0 device
[CEC Configuration] Add 'tv_wake_on_one_touch_play' option
Add the necessary APIs that will allow Camera2 clients to access
and work with existing CameraX extensions.
Bug: 170481080
Test: Camera CTS
Change-Id: Iaa22fea69ebe01599b3f2e66c1b46ca92015cdc5
This ports the Settings.Global.HDMI_CONTROL_AUTO_WAKEUP_ENABLED to
HdmiCecConfig.
Bug: 166433775
Test: atest HdmiCecLocalDeviceTvTest
Change-Id: I63c7cf35b9769da193e950f362f51a0f79898a5f
Currently, UsbManager#setCurrentFunctions takes a bitmask of
functions to enable, but will only allow callers to enable one
function at a time.
Allow it to enable both RNDIS and NCM together as well. This is
because from the user's point of view the two functions are the
same (i.e., USB tethering).
Android has historically used RNDIS for tethering. NCM performs
better, but it doesn't work on older OSes like Windows 8.1.
Also change the import order to keep the linter happy.
Bug: 172793258
Test: added unit test for UsbManager.areSettableFunctions
Change-Id: I51b6752781528b09f8929e1fb3b1fa7e4ac36aae
1) Adds biometrics.proto definition for BaseClientMonitor subtypes
2) Adds BiometricScheduler proto dump
When dumping the scheduler, the caller may request for the recent
operation queue to be cleared after dumping or not.
Note that we don't need BiometricScheduler.Operation#STATE_*
in the dump, since (for now) we just want to know what operations
have been run.
We can always add additional state, success/failure, etc in the
future if needed.
Bug: 159667191
Test: atest com.android.server.biometrics
Test: atest CtsBiometricsTestCases
Change-Id: I7d2350f00aaeef03ab7d74013b476af053240320
This CL changes the behavior of PM#goToSleep to instead turn off the
power for the default display group. PM#wakeUp turns on the default
display group.
If all display groups are turned off, the device will go to sleep. If
any display group is on, the device will remain interactive.
This results in no behavior change if there is a single display group.
However if there are multiple display groups then it will be possible to
interact with ones that are on while others are off.
Bug: 138328918
Bug: 170935083
Bug: 175919649
Test: atest PowerManagerServiceTest
Change-Id: I8b475c38886eda3e43d6e8da7e68102a25da1584
Sometimes we want to show a dialog, sometimes a notification, sometimes
nothing.
- Also some minor UI tuning to match mocks.
- Also suppress dialog while dialog is visible and shortly after. This
avoids a dialog directly after closing previous dialog.
Test: Triggered dialog. Needs exhaustive test of all
cases though.
Bug: 162549680
Change-Id: I52ccd22858969823d8670a9e345d3da994ec1c19
Read value whether HDMI CEC is enabled from HdmiCecConfig and cache it
in HdmiControlService. This changes the type from boolean to int.
Adapt the @hide listener for a change of this value to return integers
instead of booleans as well.
Bug: 171870477
Test: atest com.android.server.hdmi
Change-Id: I6275fe1b3e1ca62c210019e1df216f8731a0b5ab
