Based on Forrest run with earlier base build 6069142, the build with this submission failed apct/bluetooth/instrumentation_test
Reason for revert: Break tests
Bug: 146198238
Change-Id: I65060ca389bf3ae1f107552ca828bfc1e7baa7c1
add support for model parameter control APIs with THRESHOLD_FACTOR
as the first supported parameter
Bug: 141929369
Test: Tested manually with test app and confirmed with GTS test
gts-tradefed run gts-dev -m GtsAssistIntentTestCases
Change-Id: I06874fcf2ae2ef8796e7c52c4475252e8a026e2c
This API allows applications to instruct the connected display to do minimal
post processing on the produced image or video frames. This will switch the
display to a low latency mode (ALLM, Game mode or some other custom
implementation thereof), reducing lag in the final images. Thus, minimal post
processing would greatly enhance performance for gaming and video
conferencing applications. It would not, however, suit applications that
prioritise image quality over performance.
This CL adds 2 public method:
- Window.setPreferMinimalPostProcessing()
(this can also be set in WindowManager.LayoutParams.preferMinimalPostProcessing)
If minimal post processing is preferred, the connected display will be requested
to go into low latency mode, which reduces image processing, resulting in better
performance for gaming applications. If the Display sink is connected via HDMI,
the device will begin to send infoframes with Auto Low Latency Mode enabled and
Game Content Type. This will switch the connected display to a lower latency
mode (if available).
For more information, see HDMI 2.1 specification.
If the Display sink has an internal connection or uses some other protocol than
HDMI, effects may be similar but implementation-defined.
- Display.isMinimalPostProcessingPreferred()
Returns true if the connected display supports either Low Latency Mode (ALLM or
some other custom low latency implementation) or Game content type.
Bug: 135116095
Test: make -> flash on ATV OTT device -> open an activity which requests minimal
post processing -> check SurfaceControl logs -> verify correct signals are
passed to native
Change-Id: Id09160ba1513fef4dac979162bcda3bfeaace0e6
Interpret port as unsigned byte for consistency with uint8_t in SF/IF,
and clarify signedness in doc comments.
Bug: 143713778
Test: adb shell dumpsys display | grep physicalPort
Test: LocalDisplayAdapterTest
Test: DisplayWindowSettingsTests
Change-Id: I56ce0067367372a3a747fde783a1956975e833a0
AuthService in its current form is a thin wrapper around
BiometricService. It initializes BiometricService in onStart();
registers fingerprint, face, and iris authenticators; and forwards all
of the incoming calls to the corresponding methonds in BiometricService.
The next step will be to move non-biometric related functionality from
BiometricService to AuthService, and turn BiometricService into a module
with a stable API.
Bug: 141025588
Test: atest AuthServiceTest
Test: atest BiometricServiceTest
Test: BiometricPrompt works in BiometricPromptDemo
Change-Id: Ia861b7c2d80bfca386c3e0b44ec35b4aca3b0ffc
Default colour sampling off and add an API to enable it.
Bug: 143556482
Test: atest BrightnessTrackerTest
Test: atest BrightnessConfigurationTest
Change-Id: I955fa683d6410c7851e8f6ad503d5bfbdf0677f5
Bug: 136595429
Test: atest CtsAppOpsTestCases (now including two new test cases that
open a camera with a null and a non-null feature)
Change-Id: Ia9be1016e4e6a1a2af09b7b08c9d0373440813c6
Due to lock contention between the legacy camera
device implementation and the Camera2 framework,
result and error callbacks can be delayed which
can allow clients to update the repeating request
resulting in incorrect behavior.
To avoid this, check whether repeating request
errors still refer to valid and active request ids
tracked by the request queue before posting
callbacks.
Bug: 143727669
Test: Camera CTS
Change-Id: I8f2da0aace40b33757b3c3ac4febc3af7f0ec6cd
Introduce new bokeh mode metadata tags for camera device to enable bokeh
effect.
Test: Build and read docs
Bug: 118258123
Change-Id: Id0bb30b0fc9a50eb12b6062132fdac65755b0cdf
In order to get a correctly translated error messages, getString(...)
should be called on the application context, as opposed to the system
context. This is because the system context is unaware of the user's
locale.
Bug: 141025588
Test: Face Unlock works E2E
Test: Works with BiometricPromptDemo
Test: atest BiometricServiceTest
Test: atest AuthControllerTest
Test: atest CommandQueueTest
Change-Id: Ic228bb7ebb0d6a4ebaf96b9f1d2d70ed4e9dd79a
Created an interface, IBiometricAuthenticator, that encapsulates
fingerprint, iris, and face services. Removed direct references to these
services from BiometricService.
The interface will allow new biometric authenticators to be integrated
with BiometricService without modifying its code.
Bug: 141025588
Test: Face Unlock works E2E
Test: Works with BiometricPromptDemo
Test: atest BiometricServiceTest
Change-Id: I564ccdccbfe25b2c41f92f7e91eedde6acdeeed4
Also add mHasVideoCapture and mHasVideoPlayback members to UsbDevice.
Bug: 142321590
Test: Build, flash, connect USB Video Camera, examine logs
Change-Id: Ia6ae687182ec0b007c1688478545829395191984
Revert "Revert "change KeyphraseEnrollmentInfo to store services""
This reverts commit f2c31a51ee.
Bug: 139954183
Test: confirmed hotword enrollment is successful as a service after
device factory reset.
Change-Id: I41b78ba2b15c30c62d4ead55610fe44913741f2d
* 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
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
Includes lock icon, title, subtitle, description, lock pattern view.
Corner radius and padding animates nicely from !=0 --> 0.
Support for password/pin will come in a subsequent CL.
Unit tests for AuthCredentialView will be added when
password/pin are implemented.
Support for persisting across configuration changes
and landscape view will also be added in a subsequent
change.
Test: BiometricPromptDemo with the following:
1) Confirm pattern, callback received
2) Rejected, error string shown
3) Lockout (5 attempts), countdown string shown,
pattern view disabled until countdown is over
4) Cancel pattern auth, callback received
Test: atest BiometricServiceTest
Test: atest com.android.systemui.biometrics
Change-Id: Idc01e33be0074a6c8a43f60b172a4391bfbe5e8a
Test: Verified that confirm device credential still works
in the biometricpromptdemo app
Bug: 140128468
Change-Id: I28fc3c0dc16677ad953284ffa9670d7abd34cd40
To support, adding members to UsbDevice to mark devices as having audio
playback and audio capture capabilities.
Bug: 136080195
Test: Run "UsbAccess" test bed. Connect audio and non-audio USB devices
and see the additional prompt shown/not-shown.
Change-Id: Ie7c614d9ed30a163c350b18a54b8a9115698779d
Add getCameraIdListNoLazy() - a test method which necessarily makes a
call to cameraserver in order to get an updated list of camera ids. This
is needed since camera cts tests use SYSTEM_CAMERA permissions in a way
which are not permitted to happen in real world scenarios : processes
cannot gain and lose SYSTEM_CAMERA permissions for permission checking
purposes (through UiAutomation adopt(drop)ShellPermissionIdentity(). In
that case cameraserver doesn't send callback to the client app informing
it that system cameras aren't available.
Bug: 138130599
Test: camera CTS
Change-Id: Ic00951828ea289a1a04b1d655506ef6474336b91
Signed-off-by: Jayant Chowdhary <jchowdhary@google.com>
This reverts commit 07ba2b7f83.
This change is being reverted because it needs to be paired with an AGSA
prebuilt APK update.
Test: Confirm prebuilt AGSA apk does not crash on enrollment
Bug: 141155032
Change-Id: Ie504f125966d38a11c65ae96f39e9a5aa7ce43ed
Current hotword enrollment is done through a transparent activity which
when triggered causes a breif interuption on the UI. Because there is no
actual UI component to this activity, it is being transitioned from an
activity to a service.
applications supporting MANAGE_VOICE_KEYPHRASES are moved from ativity
to service based to allow for enrollment which does not effect the UI
Bug: 139954183
Test: confirmed enrollment and unenrollment intents can start the
registered enrollment service.
Change-Id: I1e2d80e08efaf47a5c1c8760e2979143df436a93
