This appears to have been broken with
Ic3c0415612b1387671ab8efa0ec95ed727f6bf68, which attempts to destroy
layers for all displays using a single writer. The display command that
destroys a layer must be in the writer for that display, in order for
the displays to run independently. Do so in the test itself, rather than
relying on TearDown to destroy all of them.
Bug: 333974982
Test: atest VtsHalGraphicsComposer3_TargetTest
Flag: TEST_ONLY
Change-Id: Ib6807c85bc6cb32c56cc72126a9fa68363365912
The update process for prebuilts/abi-dumps/platform will be adapted for
trunk stable. The ABI dumps for libimapper_stablec are moved to
"abi-dumps" in this project so that the trunk stable release process
will not affect them.
Test: m libimapper_stablec_abicheck
Test: development/vndk/tools/header-checker/utils/create_reference_dumps.py \
-libs libimapper_stablec_abicheck --lib-variant PLATFORM \
-ref-dump-dir hardware/interfaces/graphics/mapper/stable-c/abi-dumps \
-products aosp_arm64
Bug: 333532038
Change-Id: Ia69daa721ef983c18118bd6d0a70dd5b7a0a47a2
As of VNDK deprecation, any libraries that defines vndk is no longer
valid anymore. This change removes all VNDK definition(s) from modules
which was VNDK.
Bug: 328994089
Test: AOSP CF build succeeded
Change-Id: Ifdade9c052db29c989ce7d804ba725361c4c0f8e
Merged-In: Ic4f19113c1a25dc1fb60cdfbf9c0f2d8d7d09726
With different VRR modes we may have 2 modes with
exactly the same minFrameIntervalNs, and in this case we can't
differentiate between 2 modes.
Test: atest VtsHalGraphicsComposer3_TargetTest
BUG: 328350178
Change-Id: I5cddfee8b789ed6ce1b223ec345175f19a0db091
Some HWC implementations which do not support DISPLAY_DECORATION are
handling DISPLAY_DECORATION layers in VTS by reporting an error (as
required by the test) AND by proposing ChangedCompositionTypes. The
latter is unnecessary, as SF will never read the changed types. Update
the documentation to be more specific that this is unnecessary.
Bug: b/324977561
Bug: b/329119344
Bug: b/329017438
Bug: b/327322951
Bug: b/327090469
Test: GraphicsComposerAidlCommandTest#DisplayDecoration
Change-Id: I09c90e40818dc43b968c3e79e61e8b13a13e6344
As of VNDK deprecation, any libraries that defines vndk is no longer
valid anymore. This change removes all VNDK definition(s) from modules
which was VNDK. Any former VNDK-SP libraries will be marked as double-loadable,
so it can keep be able to be referenced by LLNDK libraries.
Bug: 328994089
Test: AOSP CF build succeeded
Change-Id: Ic4f19113c1a25dc1fb60cdfbf9c0f2d8d7d09726
Ignore-AOSP-First: Merge conflict
- add sRGB and DisplayP3 layers in HWC, if mixedColorSpaces is
supported, only DPU composition happens.
Bug: 311252937
Test: this
Change-Id: I400a6dd18a05bbdf69e249907e13a4fa7eafbf01
Includes VTS for notifyExpectedPresent call,
frameRate change in the present call and
notifyExpectedPresent after timeout.
Test: atest VtsHalGraphicsComposer3_TargetTest
BUG: 291792736
Change-Id: I1ef7011d7dcbdd6bb378b80ca0b0d7cd52832897
It's not supposed to be sign-extended as that blocks off the entire
28-64 bit range instead of the 28-31 bit range as indicated in the
comment
As this value is correct in HIDL and in the docs, do a history
re-write of the AIDL value to match the intended (and previous)
values.
Test: make
Bug: 323484008
Change-Id: I0b373576a366c853c87109a9b24ec9f8d9cbdb4d
I6c436b6b80b27930d82aabf22107216172773b56 adds a dependency for
librenderengine on flags. Add that dependency so we can use
librenderengine here, too.
Bug: 305445199
Test: atest VtsHalGraphicsComposerV2_2TargetTest
Test: atest VtsHalGraphicsComposer3_TargetTest
Change-Id: If339ac94a6eff4af34e60cf1c1135289b8915441
This CL is created as a best effort to migrate test targets
to the new android ownership model. If you find incorrect or unnecessary
attribution in this CL, please create a separate CL to fix that.
For more details please refer to the link below,
go/new-android-ownership-model
Bug: 304529413
Test: N/A
Change-Id: Ic8c4bd6ac246e7efa98bbdaf822d12ae8e1230a5
This CL is created as a best effort to migrate test targets
to the new android ownership model. If you find incorrect or unnecessary
attribution in this CL, please create a separate CL to fix that.
For more details please refer to the link below,
<add g3 doc link>
Bug: 304529413
Test: N/A
Change-Id: I3322344f595f974f730dc824af0110388076d838
Fixing a bug that caused Teardown to clear the errors before
checking them
Bug: 303735490
Test: presubmit
Change-Id: Ieb02ab3015fc21bcef6624f8f45c3b84549005c2
When the tests fail, ensure we continue running so we can run the
remainder of the tests.
Bug: 304976052
Test: atest GraphicsComposerAidlCommandTest
Change-Id: Ia6ab2bbd284bb7eddeb49164dcbe7285829ad9c3
Ensure the primary display to set power on before running
getClientTargetSupport tests for VTS 2.1 - 2.3.
Bug: 308252481
Test: atest VtsHalGraphicsComposerV2_1TargetTest
Test: atest VtsHalGraphicsComposerV2_2TargetTest
Test: atest VtsHalGraphicsComposerV2_3TargetTest
Change-Id: I6b793537ee42c87f37c4c1d7141364541f448134
Update the timeoutNs description to specify what 0 and not absent value
expected behavior is
BUG: 294102485
Test: VTS
Change-Id: I3954c8f1efad8190ed6d608e2968fe1dc15c2f11
Ensure the primary display power on before run the
SetDisplayBrightness test item.
Bug: 313794734
Test: atest VtsHalGraphicsComposer3_TargetTest:PerInstance/
GraphicsComposerAidlCommandTest#SetDisplayBrightness/
0_android_hardware_graphics_composer3_IComposer_default
-- --abi arm64-v8a
Change-Id: I94fb700704bcbd8543f2a608dd75b9e745e40e37
Merged-In: I94fb700704bcbd8543f2a608dd75b9e745e40e37
Ensure the primary display power on before run the
SetDisplayBrightness test item.
Bug: 313794734
Test: atest VtsHalGraphicsComposer3_TargetTest:PerInstance/
GraphicsComposerAidlCommandTest#SetDisplayBrightness/
0_android_hardware_graphics_composer3_IComposer_default
-- --abi arm64-v8a
Change-Id: I94fb700704bcbd8543f2a608dd75b9e745e40e37
* changes:
[Composer3-VTS] Test Composer3-V3 for refreshPeriodNanos and vsyncPeriodNanos
[HWC3] AIDL change to add refreshPeriodNanos to RefreshRateChangedDebugData
