Camera capture requests need an extension to support multiple
physical cameras. Clients should be able to include the list
of additional physical camera ids as part of the request builder
call and then be able to modify them individually.
Test: Manual using camera application,
Camera CTS
Bug: 64691172
Change-Id: I280cb24b41076a2fb5603e91db30f060f7b53456
- Add physicalCameraId in OutputConfiguration
- Add static metadata for logical camera
Test: LogicalCameraDeviceTest CTS test
Bug: 64691172
Change-Id: I1b3ea005796d07e361cc3d1b04aa6e5ca26643f4
If a UID is idle (being in the background for more than
cartain amount of time) it should not be able to use the
camera. If the UID becomes idle we generate an eror and
close the cameras for this UID. If an app in an idle UID
tries to use the camera we immediately generate an error.
Since apps already should handle these errors it is safe
to apply this policy to all apps to protect user privacy.
Test: Pass - cts-tradefed run cts -m CtsCameraTestCases
Added - CameraTest#testCameraAccessForIdleUid
Change-Id: If6ad1662f2af6592b6aca1aeee4bd481389b5e00
Allow client to add a description to a brightness
config and dump to dumpsys
Dump time and package name of system app that
set the last brightness config.
Bug: 71854421
Test: atest PersistentDataStoreTest
Test: manaual - check adb shell dumpsys display
Change-Id: I5ff0c0d3a4c5e30c9d4aa7eea850c7174ee20450
This allows the DisplayManager to pick up changes to the
DisplayCutout resource, which is used to implement emulation
of the overlay.
Bug: x
Test: adb shell overlay enable ...; verify cutout is picked up immediately and not only after toggling the display
Change-Id: I0fa2d50366a17231f45990d2d3854321d48653f0
Cherry-pick from 30b9adfad1
The screen unlocked functions save effort on setting
the usb config during each connection. These
functions persist between connections and between
boots. When the screen is unlocked and these
functions are set, the current functions will
be automatically set to the screen unlocked functions.
Also added svc command for this so it can be
used and tested while the UI is worked on.
Bug: 62876645
Test: svc usb setScreenUnlockedFunctions mtp
Test: Test functions with locking, unlocking, and
disconnecting, with no lockscreen, swipe, and pattern
Change-Id: Ia05e095917166d25398c4d310b02971e3a1bb12a
Make the API for tracking brightness
slider events and setting brightness
curves @SystemAPI and @TestAPI
Add developement scope to the brightness
slider events permission to allow cts
testing.
Bug: 69405990
Test: atest android.permission2.cts.PermissionPolicyTest#testPlatformPermissionPolicyUnaltered
Test: atest BrightnessTrackerTest
Change-Id: I39b0b26454528425b62cf99dc8bbccded4e14a18
The screen unlocked functions save effort on setting
the usb config during each connection. These
functions persist between connections and between
boots. When the screen is unlocked and these
functions are set, the current functions will
be automatically set to the screen unlocked functions.
Also added svc command for this so it can be
used and tested while the UI is worked on.
Bug: 62876645
Test: svc usb setScreenUnlockedFunctions mtp
Test: Test functions with locking, unlocking, and
disconnecting, with no lockscreen, swipe, and pattern
Change-Id: Ia05e095917166d25398c4d310b02971e3a1bb12a
- MOTION_TRACKING capability defines a camera with accurate lens calibration
values, accurate timestamps relative to the inertial sensors, and ability
to limit exposure time to 20ms max.
- Add android.lens.poseReference for supporting gyroscope-centered lens calibration
data for MOTION_TRACKING.
- Minor changes to some docs formatting.
Test: Builds
Bug: 63629224
Change-Id: Ic303240890c709725f60e69dfff76beea4a0ef91
Methods not covered are related to tuning or program list.
This makes 11 passing test cases and still 6 failing for the new HAL.
Test: instrumentation
Bug: 69958777
Change-Id: I2631d66d05774adb9e8fd42c8309e16f832c4478
* changes:
Rethrow RemoteException instead of log in ContextHubManager
Remove unnecessary log from ContextHubManager
Remove legacy bug comment in NanoAppInstanceInfo
