IntRange just matches what would have resulted in an
IllegalArgumentException, no new restrictions
Fixes: 124767261
Test: N/A
Change-Id: Iad04587f2c10008798098fc56481e45de4c64c0b
When setting folded area with changes both in width and height (set
0,0,540,1080 to a 1080x2160 device), the content of display will be
auto-scaled to physical display size. It is not an expected behavior
for foldable devices. Disable auto-scale to fix this issue.
1. LogicalDisplay.configureDisplayLocked() scales the contents according
the DisplayInfo.flags.
2. DisplayInfo.flags should not be overridden by design for a logical
display.
3. Adds disableDisplayScaling() for DisplayFoldController to bypass that.
Bug: 123245311
Test: atest WmTests
Test: adb shell wm folded-area 0,0,840,1260
Change-Id: I9a24c5d56799981b4f2cfe82fdf1898d87193681
InputForwarder was used by ActivityView. InputForwarder is not used by
anyone now.
Bug: 120675821
Test: Manual test with ActivityViewTest
Test: atest CtsActivityManagerDeviceTestCases:ActivityViewTest
Change-Id: I6bd2338c921e6dfb1dfe357decb878d558df8bfd
Lockout reset now happens at the source of truth, where the HAT is received
from Gatekeeper.
Fixes: 121198195
Test: Lockout is reset properly
Change-Id: Icd72a20494a65f0e48cff1258109d82fb58cdc98
Most common code is now in BiometricServiceBase
Fixes: 122118421
Test: Unknown templates in Framework and HAL are cleaned as expected
Change-Id: Ia35efa5c2dac26d66b6f2813dd98fbdbb674f605
Looper.myLooper() can return null, according to the docs.
But in the DisplayManagerGlobal code, this method is assumed to return
non-null looper.
To ensure that a looper is available, use the main thread looper if the
looper for the current thread is null.
Test: atest cts.ViewGroupTest
Bug: 123592612
Change-Id: I80aaf5703e62837720395bfac4d95144cd6ab9f0
with ColorDisplayManager, where possible
Bug: 123352608
Test: atest FrameworksServicesTests:ColorDisplayServiceTest
Change-Id: I4feb67197462d49002582931aee285abe85054e6
Note that we handle volume key the same way as other keys before when
forwarding them to other cec devices. But the destination device of
volume key might be different from other function keys.
We might need to take the System Audio Control logic into this
forwarding proccess to find the proper audio receiver address.
Test: make -j44
Bug: 123369653
Change-Id: I6c9dba2b333e7eaa5137a8d2f5bfed506ae8554b
(cherry picked from commit 5db0138297836baf570f354c0b2ecb988d30936b)
Change brightness tracker to enable / disable color
sampling on screen on / off.
Add value channel to BrightnessChangeEvent if available.
Bug: 112756444
Test: atest BrightnessTrackerTest
Test: atest android.display.cts.BrightnessTest
Test: manual checked pixel3 which supports this and pixel2 which doesn't
Change-Id: I94384752235d891cee975b01f933c0bc0b4572a9
The bitmap.createHardwareBitmap doesn't take a ColorSpace as input, as a result
the returned bitmap is always in SRGB color space. Given that we want to remove
the assumption of SRGB color space, we replace the usage of
createHardwareBitmap with wrapHardwareBuffer which takes an extra argument
ColorSpace. As a result, we will be able to also fix SurfaceControl and various
other places that use screenshot in follow up patches.
BUG: 120904891
Test: CtsUiRenderingTestCases
Change-Id: I57fc0c85d68df43b0e69f9a1ebac00d2ba39554d
These are useful for testing by apps, or for vendor extension points
in vendor SDKs.
Test: atest cts/tests/camera/src/android/hardware/camera2/cts/SimpleObjectsTest.java
Bug: 116298360
Change-Id: Icaa5d789e950a9379d72e784eedfa18a37cb71d6
To ensure future BP builder changes don't require a 1:1 addition to the
CC API, we're deprecating CC and moving the API to BP.
Since CDC is an activity, and BP can't receive onActivityResult from CDC,
we need to have BiometricService launch CDC. CDC will return auth/reject
results to BiometricService using a private protected aidl method, which
can then forward the reuslt to BP/app.
Bug: 111461540
Test: builds
Test: demo app, receives correct callbacks
Change-Id: I7111ca2842534a596302fe0eb7338fbfaca72eec
Add Display.getPreferredWideGamutColorSpace() to return the preferred wide
color space that the rendering and composition pipeline prefers.
BUG: 120904891
Test: atest android.display.cts.DisplayTest#testGetPreferredWideGamutColorSpace
Change-Id: I1bcd9db72689a734b2a7c097b99a01464810994a
Need to actually respect the given usage or the API doesn't
work. Shift the default to be done Java-side where it's clear
if usage was user-provided or not. Remove the incorrect
validations and assertions around usages.
Add missing HardwareBuffer#isSupported to let users
check if a usage & format combination is supported.
Change-Id: I70bfe6e6c41e78425a38af6b17d421f0e80e818b
Fixes: 123423319
Test: HardwareBuffer CTS tests
