The change makes the distinction between VibrationEffect and
CombinedVibratio clearer. The later is a combination of the former with
the extra information about the vibrator ids, allowing effects to be
played in one or more vibrators in parallel or in sequence.
The methods create/start synced where also renamed to parallel (together
with respective builder classes), to indicate they perform one or more
effects in parallel on multiple vibrators. This is also a better match
to the sequential combinations.
This change also deprecates the Context.VIBRATOR_SERVICE in favour of
the new VIBRATOR_MANAGER_SERVICE. The default vibrator can be retrieved
from the manager system service.
Same deprecation applied to InputDevice.getVibrator method.
Fix: 184123900
Test: CombinedVibrationTest
Change-Id: I44d8b225098d35fbf7783254acaf6a78f9fb4505
1) Sets the sensor property based on the HAL, instead of hard coding
false
2) Schedules/cancels detection when requested
3) Updates biometric dumpsys to include internal properties
Test: atest com.android.server.biometrics
Test: adb shell dumpsys biometric
Test: manual
Bug: 184672091
Change-Id: I2fb1db0994f6d2ed235420967d78e70f1b13cdd0
HdmiControlService.oneTouchPlay method is already switching the
long running one touch play process to the service thread from
the UI thread and is also able to handle multiple OTP requests
in parallel. Remove TODO to use PendingResult.
Bug: 159901363
Test: None
Change-Id: Ife8c8268edb8a40255a52dd1eda2ab60020803c8
With Frame Rate Override enabled, an app could get an onDisplayChanged
events which seems redundant. An example would be:
1. Display changed refresh rate to 60Hz - onDisplayChanged was called
2. App's frame rate override changed to 60Hz - onDisplayChanged was called
To avoid sending these redundant events, DisplayManagerGlobal caches
the last DisplayInfo that was reported to the app and based on it it
decides whether to send the event or not.
Bug: 184588343
Test: atest SetFrameRateTest
Test: atest FrameRateOverrideHostTest
Change-Id: I97c7b2b9a799424998b1b717a4311d3d08b3178f
Bug: 182530469
Test: Make Emulator back camera system camera; atest FlashlightTest.java
Merged-In: I0a149ba3d93a740cfbfdc2d04c1235e648061156
Change-Id: I0a149ba3d93a740cfbfdc2d04c1235e648061156
Signed-off-by: Jayant Chowdhary <jchowdhary@google.com>
(cherry picked from commit bedb9950c8)
The call to Compatibility.isChangeEnabled also logs so no need to
make an explicit call to Compatibility.reportChange().
Bug: 183512729
Test: TH
Change-Id: I062a9cfa364c36868180cce3be49da020dd91341
Physical camera ids aren't included in concurrent camera combinations.
The logs aren't real errors. Make them debug logs.
Bug: 184194887
Test: atest LogicalCameraTest#testBasicPhysicalStreaming doesn't show
unecessary logs while calling getCameraCharacteristics for
physical camera ids.
Change-Id: I4f6e9030f23c31e0dc796882e6e82964d5a80668
Signed-off-by: Jayant Chowdhary <jchowdhary@google.com>
Use the local reader argument instead of the member
variable which can get reset.
Additionally, make sure to execute the extension forward
processor 'ImageReader' callback using the extension session
handler.
Bug: 184447319
Test: atest -c
cts/tests/camera/src/android/hardware/camera2/cts/CameraExtensionSessionTest.java#testCloseCaptureSession
--iterations=10
atest -c
cts/tests/camera/src/android/hardware/camera2/cts/CameraExtensionSessionTest.java
Change-Id: Id8f8818ad478b70438cbd18d46ef79263bc4de9d
For the AIDL providers, send the scheduler the callback that
was passed in. Otherwise, the test infrastructure wouldn't know
when cleanup completes. This saves ~20s from each test session
close time.
The added logs do not affect/spam production code.
Bug: 152240892
Test: atest CtsBiometricsTestCases
Change-Id: I047ec8da01b3237e738e4567eb6ef3554f6b868d
Bug: 182530469
Test: Make Emulator back camera system camera; atest FlashlightTest.java
Merged-In: I0a149ba3d93a740cfbfdc2d04c1235e648061156
Change-Id: I0a149ba3d93a740cfbfdc2d04c1235e648061156
Signed-off-by: Jayant Chowdhary <jchowdhary@google.com>
(cherry picked from commit bedb9950c8)
This touches the sensor use dialog and the notification.
Also we shouldn't leak listeners every time the dialg is made.
TODO: Detect when both camera and mic are opened at the same time
TODO: Settings page
Test: Manually open all UI available
Bug: 183985427
Change-Id: Ie743f402835d8fd3e644a0374f03062f0a61c31a
Bug: 182530469
Test: Make Emulator back camera system camera; atest FlashlightTest.java
Change-Id: I0a149ba3d93a740cfbfdc2d04c1235e648061156
Signed-off-by: Jayant Chowdhary <jchowdhary@google.com>
The maximum size flag indicates whether the mandatory stream
information contains a maximum size from stream configuration map.
Test: Camera CTS
Bug: 156254356
Change-Id: I197716d4174d6c9630042f8120e0248fec281e50
Setting is configured in DozeSensors, so no need to double check in
AmbientDisplayConfiguration for the setting.
Test: manual
Bug: 176550666
Change-Id: If194e43ab5834f63e56cd1ca553b48af069d38fa
The onStatusChangedLocked removes entries from the ArrayMap. Needs to
iterate in the reverse order.
Test: Vendor testing
Bug: 182876702
Change-Id: I5891f24a25c83f096d23ca5675126889a7d2a61c
1) Make the resulting face/fingerprint can be @Nullable. Not all
removal callers care about the template that was removed, just
that they were all removed.
2) FingerprintService/FaceService should wait for all providers to
finish removing before notifying the upper layer of completion
Fixes: 183758063
Test: atest CtsBiometricsTestCases, notice
testLockoutResetRequestedAfterCredentialUnlock finishes
10 seconds quicker now (latch in LSS doesn't time out anymore)
Change-Id: I87c50ccf5524fd5440c9a6c2c7a0fd4cc61e684d
This will allow Car System UI to enquire about sensor privacy for
multiple users.
Bug: 182826082
Test: Manual
Change-Id: Ibc4271f095597e3cee5e61c7e930a8365b1312c8
Adding new APIs in display manager to get the user disabled formats, to get the formats
supported by device and get formats reported by display.
Bug: 172905874
Test: N/A
Change-Id: I58a7714f03a3e165bbd22f2fa7a021ad90b41b39
Merged-In: I58a7714f03a3e165bbd22f2fa7a021ad90b41b39
(cherry picked from commit 25f1822005)
Added new APIs to DisplayManager to set the user disabled HDR formats,
and get/set if user disabled formats should be ignored or not.
These new settings are stored in Settings.Global.
Modified the implementation of Display#getHdrCapabilities to not return
the formats disabled by user.
Bug: 172905874
Test: atest CtsDisplayTestCases
Change-Id: I4841af251ee0e4938614b154d0c5239814ea7cd9
Merged-In: I4841af251ee0e4938614b154d0c5239814ea7cd9
