Describe the callback purpose so it is consistent
with the rest of the callbacks.
Bug: 128427361
Test: Successful build
Change-Id: Ia97dbd33eb65f8166865ce0b297a83d4728507ff
Exempted-From-Owner-Approval: Automatic changes to the codebase
affecting only @UnsupportedAppUsage annotations, themselves added
without requiring owners approval earlier.
Bug: 122331906
Test: m appcompat
Change-Id: I3abc8221706bd69668c90aa61b8ca5f137a88bb9
For packages:
android.database
android.hardware.display
android.hardware.input
android.hardware.location
android.location
android.media
android.media.projection
android.media.tv
This is an automatically generated CL. See go/UnsupportedAppUsage
for more details.
Exempted-From-Owner-Approval: Mechanical changes to the codebase
which have been approved by Android API council and announced on
android-eng@
Bug: 110868826
Test: m
Merged-In: I570c08292f8a9f512c96f9dce13f5337718f112c
Change-Id: I1d6c60fcb53f404d5775163bf6929395921f5a45
To fix compatibility problems with existing devices.
Test: Vendor extension libraries work as expected on Pixel.
Camera app starts.
Bug: 126901248
Change-Id: Id585eaf7126828093497f0600767381b85d9fb6b
It would be nice if there is a common & reliable method for both outer
& internal modules to check the UID presense of the display.
Add more check in Display#hasAccess() to ask system if calling UID can
precense on the specific display, to consolidate only few special UIDs
& display flag checking.
Bug: 117347985
Test: atest ActivityManagerMultiDisplayTests
Change-Id: I2f8989598c99c0962e925c5aa65500972b4fc62b
CameraCharacteristics.getKeysNeedingPermission() must have
correct nullability annotation.
Bug: 126700407
Test: Camera CTS
Change-Id: I5a4186299fa386c3dcaec1f6fa358e711720a1eb
If they were null, then the Parcelable would fail to work.
Bug: 126726802
Test: manual
Change-Id: I7929ffa2f20e5de1c8e68e8263cca99496e9d014
Exempt-From-Owner-Approval: Trivial API annotations
Also extend the documentation and clarify the meaning of
mandatory and reprocessable stream combinations.
Bug: 126391833
Bug: 126702075
Bug: 126699529
Test: Camera CTS, docs build without errors
Change-Id: I8773458062a1b661e7eef61df982374b6b8e3092
Camera availability callbacks must support client
notifications about access priority changes. Such
data can be useful for any client that is actively
waiting for access to a particular camera device.
Bug: 121379978
Test: Camera CTS, successful docs build.
Change-Id: I423960c3a5bc5a2e156ccf3e8623c26d49350131
On devices with no hardware, the service is null. We need to return the
correct error in that case.
Fixes: 126392276
Test: Builds
Change-Id: I184bd6afce71bf36b659286cd7dd6aa17d490657
For packages:
android.database
android.hardware
android.hardware.display
android.hardware.input
android.hardware.location
android.location
android.media
android.media.tv
android.media.projection
This is an automatically generated CL. See go/UnsupportedAppUsage
for more details.
Exempted-From-Owner-Approval: Mechanical changes to the codebase
which have been approved by Android API council and announced on
android-eng@
Bug: 110868826
Test: m
Change-Id: I570c08292f8a9f512c96f9dce13f5337718f112c
Add annotations to clarify the brightness
correction API.
Bug: 125347154
Test: atest android.display.cts.BrightnessTest
Test: manual, flash phone, get app using API to push corrections, adb shell dumpsys display
Change-Id: Icbb61bb542a49c49f279b865d69d59a542c0e42b
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
