- Expose api via TestApi
- Add ASSOCIATE_INPUT_DEVICE_TO_DISPLAY permission to Shell
- Add port for uinput command
Bug: 215631144
Test: atest CtsInputTestCases
Ignore-AOSP-First: Permission that should be kept internal until T releases
Change-Id: I55f2141aabceb71475f5e7f7d590b2f95e05c5aa
Operations that wait for cookies (authentication) do not set their lifecycle callback until started. This leaves a small window when failures are not propogated to callers (i.e. fast/immediate failures).
This also adds some additional checking for stale UI events (point up/down) that are delivered after the operation has ended.
Fix: 216071532
Test: atest com.android.systemui.biometrics com.android.server.biometrics
Change-Id: I7f7500db0a42b2ea97e171e26148ee68b15f5ae8
This adds the committed state to the display.
The `state` is used to set the correct power state (e.g. turning display on/off), however there was no way to know when this power state change finished. This new "committedState" aims to fulfill this gap.
DisplayListeners receives a `onDisplayChanged` callback whenever the power state change is fully committed, and can get this information from DisplayInfo.
This will be used in a follow up cl to improve unfold latency performances.
Bug: 223808403
Bug: 220690092
Bug: 197515205
Test: atest LocalDisplayAdapterTest && manual
Change-Id: Ia2fbab768b696c59578d974c88157ee3c8f3ddde
Previously we only stopped HBM if we receive onAcquired with
info=FINGERPRINT_ACQUIRED_GOOD.
Update the onAcquiredGood method to be more generic (onAcquired,
with an acquiredInfo parameter) so the UdfpsOverlay can turn
off HBM for the appropriate acquiredInfo messages.
Bug: 222117182
Test: manually test on Lock Screen, enroll and biometric prompt
Test: atest SystemUITests
Change-Id: I6b21fbf65a6f38660fe8beab617d17cef3ad50ba
The standard dynamic range profile will always be present as part of the
advertised profiles. Additionally the same profile must never advertise
extra latency due to the format selection.
Bug: 215396395
Test: Camera CTS
Change-Id: I0ad7dd23a1b1f742293b4c52a48a8fca98b7925c
Content recording relies upon a class describing current state.
rather than passing around details from media > display > wm.
WMService keeps track of the session in ContentRecordingController.
ContentRecordingController manages hand-off between different
DisplayContent instances, as the session details are changed.
Manually tested that fold/unfold handling when screen recording
from QS tile still works, and that taking over a screen cast
with a screen recording works.
Refactoring logic from DisplayContent into new recording
delegate will come in a future change.
Bug: 216756854
Test: atest FrameworksCoreTests:ContentRecordingSessionTest
Test: atest WmTests:DisplayContentTests
Test: atest WmTests:ContentRecordingControllerTests
Change-Id: Ib4f125dd703d362ac13fcbe469d00b345827e706
Migrate simple views to Kotlin & remove useless test. Will add new tests in a follow up change.
Bug: 217393533
Test: atest com.android.systemui.biometrics com.android.server.biometrics CommandQueueTest
Test: manual (via BP test app)
Change-Id: Ic8c80344d75f34f4b5f65ef14b61bbb5cddb0349
Refactor existing tests to remove unnecessary mocks and boilerplate code to
cover more of the real behavior. This is prep for adding new tests in another
change to add the new face and fingerprint behavior.
Bug: 217393533
Test: atest AuthBiometricViewTest AuthContainerViewTest
Test: manual (authenticate using test app)
Change-Id: If984d1c07fee98d2d7a20cb0025ad434ad9977f4
frame rate of each camera stream.
Bug: 209669709
Test: Verified values received by the CameraServiceProxy are reasonable.
Change-Id: I5cff78bf6f055e5f04ed5da33d5d6ef3a3d64bb6
Implements API feedback about the safety center constants. Also renames
Safety Hub to Safety Center
Fixes: 215301946
Test: build
Change-Id: Ie07e8fc3ae7371e94d23ac6dfa9a446ef92da074
Additionally switch the dynamic range profiles to long values
instead of integers.
Bug: 215396395
Test: Camera CTS
Change-Id: I4700af73f31423fd9316cfb08a351b0cde731d76
This is a workaround for the fact that currently, relying on the GC to
release those resources is unreliable and on the other hand having an
explicit close() that isn't tightly coupled with the internal details
of the parcelable is not possible (filed a bug).
Test: Manual verification of soundtrigger operation.
Test: atest com.android.server.soundtrigger_middleware.SoundHw2CompatTest
Fixes: 219411458
Change-Id: I43bd43ca80eadf97f0254678b0e817fc6f8a06b2
Merged-In: I43bd43ca80eadf97f0254678b0e817fc6f8a06b2
(cherry picked from commit 578eadd1b4)
