A hinge angle sensor type has been added to the sensor HAL which
requires updating sensor.h and sensor-base.h.
Bug: 144139857
Test: N/A
Change-Id: I0d8e7d028cc1b2e05a8ec74b7ab3da9ffff5dbde
getClientTargetProperty will give hardware composer the ability to request some
properties of the client target that hardware composer wants. Prior to this
API, the client will does its best to produce the client target of which the
properties are pretty much fixed.
BUG: b/145968912
Test: boot
Change-Id: Ib8ba44d274a0c8a86c3fde1d09b72f592445ee91
Bug: 146363190
Test: atest VtsHalSoundtriggerV2_3TargetTest
&& Assist GTS test suite and manual testing
Change-Id: I6a1ac196cb7f5ad1c0b60f0adfb67680bb18568b
Add a function to audio HAL interface allowing the attachement of an
audio effect to an audio device.
This is used when an audio effect is implemented below the HAL (e.g by an audio DSP)
and is attached/enabled when a particular sink(e.g speaker) or source(e.g mic) device
is selected.
This function must be supported from legacy HAL version 3.1.
Bug: 136294538
Test: make
Change-Id: Id63c83403fef580579c52d92758a552d67c3faec
Merged-In: Id63c83403fef580579c52d92758a552d67c3faec
Add the possibility to specify a target audio device when
creating an audio effect by passing its audio port handle
to createEffect API.
Add new create_effect_3_1() function to audio_effect_library_t
interface for interface version to 3.1.
Bug: 136294538
Test: make
Change-Id: Ia84eaf32f2a7c0cc73a43075c84902a395bafe58
Merged-In: Ia84eaf32f2a7c0cc73a43075c84902a395bafe58
Add a callback to notify the client it should retry a
setActiveConfigWithConstraints call in case of SEAMLESS_NOT_POSSIBLE error.
Test: rev up composer to 2.4
Bug: 141329414
Change-Id: I102bedc9cb89f9d1886a431f8804897bb838eb8f
Based on Forrest run with earlier base build 6069142, the build with this submission failed apct/bluetooth/instrumentation_test
Reason for revert: Break tests
Change-Id: Icccbdafc14394349baf6d116d6590552ebcbeba9
add support for 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: Id0b48d90d02a0edbabfebb12697dabb8ea4edfae
Add a function to audio HAL interface allowing the attachement of an
audio effect to an audio device.
This is used when an audio effect is implemented below the HAL (e.g by an audio DSP)
and is attached/enabled when a particular sink(e.g speaker) or source(e.g mic) device
is selected.
This function must be supported from legacy HAL version 3.1.
Bug: 136294538
Test: make
Change-Id: Id63c83403fef580579c52d92758a552d67c3faec
Add the possibility to specify a target audio device when
creating an audio effect by passing its audio port handle
to createEffect API.
Add new create_effect_3_1() function to audio_effect_library_t
interface for interface version to 3.1.
Bug: 136294538
Test: make
Change-Id: Ia84eaf32f2a7c0cc73a43075c84902a395bafe58
- getSupportedDisplayVsyncPeriods was removed as the vsync period
can be obtained by getDisplayAttribute for each individual config.
- renamed setActiveConfigAndVsyncPeriod -> setActiveConfigWithConstraints
to better describe what this function does.
- added VsyncPeriodChangeTimeline and onVsyncPeriodTimingChanged
Test: rev up composer to 2.4 and test refresh rate switching
Bug: 141329414
Change-Id: Ifec51c893bb9038e9ac48d02c1c7b0fe9e25c108
Add new functions to improve vsync period switching by the platform:
- Adding a list of supported vsync periods to hwc2_config_t to avoid the need to expose
separate hwc2_config_t for each vsync period.
- Adding an API to set the vsync period with timeline constraints to allow better
synchronization with vsync period change.
- Extending HWC2_CALLBACK_VSYNC callback to provide the current vsync period.
Test: rev up composer to 2.4 and test refresh rate switching
Bug: 141329414
Change-Id: I0e3371dc41c4fbcf97073a120307f7a8923c9325
Brightness is already a per display capability, we don't need this API.
BUG: 130313275
Test: build
Change-Id: If1ddf2a6224c9aa86f250178fc5cae3b01334b57
This was added in KM4, but didn't make it into this header.
Additionally, KM_TAG_UNLOCKED_DEVICE_REQUIRED was squatting on
KM_TRUSTED_CONFIRMATION_REQUIRED's number.
See hardware/interfaces/keymaster/4.0/types.hal for correct numbering.
Bug: 128851722
Test: Keymaster VTS 4.0 + Trusty
Change-Id: I89117ffe91602884edb8dd19ffd22e659f40fb1c
Extend "CAMERA3_MSG_ERROR_RESULT" comments and describe
how Hal must notify about physical device result failures
and logical device result failures.
Bug: 128835627
Test: Successful build
Change-Id: I935fba5a5676a0fe9440f43b281fc9eeb50578ea
The race condition is now handled by default HAL wrapper so
we don't need to send this information to HAL implementation.
Test: Pixel 3 + Camera CTS + GCA
Bug: 120986771
Change-Id: I48e611ba45d45ebf34359e828bcb23cb6eec4af2
Enable Hal to trigger or skip stream reconfiguration
based on session parameter updates.
Bug: 122609098
Test: Manual using application,
VtsHalCameraProviderV2_4TargetTest
--hal_service_instance=android.hardware.camera.provider@2.4::ICameraProvider/legacy/0
--gtest_filter=CameraHidlTest.configureStreamsWithSessionParameters
Change-Id: Ie931e7cb7f46257276cc1796fccd301c85a90d85
- Add new BlobId to specify JPEG APP segments.
- Add new gralloc usage flag for HEIC encoder.
Test: testHeic CTS test
Bug: 79465976
Change-Id: Ie70654504eecb280e3a51b60c104124035c5fbe5
