We are adding things to them, and in order for core libraries like libui
to use them, the newer versions need to be in the VNDK.
Bug: 170435409
Test: build
Change-Id: I4094240656f357b5ae52194befd0e10627b9fe23
Merged-In: I4094240656f357b5ae52194befd0e10627b9fe23
The fact that these variables are 'FILE' instead of 'FILES' is due to
historical changes, but updating comment to reflect this to avoid
confusion.
Bug: N/A
Test: N/A
Change-Id: I92b685eceaab99c7786384c08076dcf3bd087326
Fix VtsHalWifiSupplicantP2pV1_0TargetTest to skip tests
in such a way that VTS reports the module as complete on
devices that don't support Wifi Direct.
Bug: 170326147
Test: run vts -m VtsHalWifiSupplicantP2pV1_0TargetTest
Change-Id: Ia418c4bb72f4772422d724636453395c4ba9fb2d
This CL creates the following primary sets of functions:
* V1_X::utils::convert(<canonical_type>) -- Converts a canonical type
to the corresponding HAL version type.
* nn::convert(<V1_X_HAL_type>) -- Converts a HAL version type to the
corresponding canonical type.
* neuralnetworks::utils::hasNoPointerData -- Indicates if the object
contains no pointer-based data that could be relocated to shared
memory.
* neuralnetworks::utils::flushDataFromPointerToShared -- Relocate
pointer-based data to shared memory.
* neuralnetworks::utils::unflushDataFromSharedToPointer -- Undoes
`flushDataFromPointerToShared` on a Request object. More
specifically, `unflushDataFromSharedToPointer` copies the output
shared memory data from the transformed Request object back to the
output pointer-based memory in the original Request object.
It also introduces some other minor utility code, including
makeQuantized8PerformanceConsistentWithP, countNumberOfConsumers,
validate, valid, and validatedConvertToCanonical.
Bug: 160667419
Test: mma
Change-Id: I0732e658c1f4ed40cd122f1ca8581fb40b056757
Merged-In: I0732e658c1f4ed40cd122f1ca8581fb40b056757
(cherry picked from commit a685c3dbf4)
Various wifi protocol MAC randomizations are mandatory in Android 11.
So, deprecate older versions of wifi HAL which don't support the
corresponding API's.
Bug: 169201652
Test: Compiles
Merged-In: I20f5b3665650c86fc0f976c544194f87157e6b90
Change-Id: I20f5b3665650c86fc0f976c544194f87157e6b90
In places where we are passing interfaces, pass around
android.hidl.base.IBase to give flexibility to the test implementation,
specifically in order to avoid passing local binders to Java process,
which is a disabled feature.
Bug: 169369810
Test: atest hidl_test hidl_test_java
Change-Id: I7721a6ec7e72b96915a0dc66aa8e75c327032d1f
According to the Q CDD, an Android Automotive OS device is not required
to support GnssMeasurements.
Bug: 161549048
Test: atest VtsHalGnssV1_0TargetTest VtsHalGnssV2_0TargetTest VtsHalGnssV2_1TargetTest
Change-Id: Idcd59f36ca2ea28925f6766a7abcdf7b6ad0f0ff
When user input 'fastboot erase userdata' in fastbootd, may need an
oem specific API doOemSpecificErase() to wipe other userdata in device.
If oem doesn't need this specific API, oem could return NOT_SUPPORTED
to fastbootd.
Bug: 169173873
Change-Id: Ie12ede31ef071a3c15265777b55746536a861292
auto_gen_config: this is a helper binary, so we avoid actually running a
test by not creating a test configuration
test_suites: vts, so that this is built and packaged with VTS
Bug: 168806888
Test: fmq_test
Change-Id: I640b848297667594153c207f8a4fcad989585d98
NNAPI VTS is parameterized by discovered devices. When there is no
device available, the compilation caching and memory domain tests will
not be instantiated, and will cause a gtest error. This patch suppresses
the error by GTEST_ALLOW_UNINSTANTIATED_PARAMETERIZED_TEST macro.
Bug: 168152007
Test: 1.2/1.3 VTS without NNAPI driver
Change-Id: I715ae6f45df66e4a03c12b5d3f38bcc028a9ed7c
Merged-In: I715ae6f45df66e4a03c12b5d3f38bcc028a9ed7c
(cherry picked from commit af9ac3b8a0)
We don't need to test supplicant in the presence of vendor HAL & without
it. For a given device, this behavior is fixed.
Bug: 161951052
Test: atest VtsHalWifiSupplicantV1_1TargetTest
Merged-In: I71097c3afef1765ca514abf2c350c423e3999020
Change-Id: I71097c3afef1765ca514abf2c350c423e3999020
(cherry picked from commit 984b6e0607)
Only the variant(s) actually implemented by the device will be
instantiated.
This is consistent with tests for other versioned or optional HALs.
Bug: b/167222309
Test: atest VtsHalGraphicsMapperV2_0TargetTest:GoogleTestVerification#UninstantiatedParameterizedTestSuite<GraphicsMapperHidlTest> -- --abi arm64-v8a
Change-Id: I4f1bfbad47bdbf75578ec48a3a56fb5351e7729a
Changes to make hidl_test_java symmetric (this implementation mirrors
one in system/tools/hidl).
Bug: 168152294
Test: atest hidl_test_java
Change-Id: I29a468d1804ba494bfe5ca59d68b3ab2581eb9b4
aosp/1427815 add invoke terminate function in teardown function.
It will cause Create Test case fail since Create killed global hostapd_
service to re-generate the local one.
Use global hostapd_ to replace local variable to make teardown function
work normally.
Bug: 169248773
Test: atest -c VtsHalWifiHostapdV1_2TargetTest
Test: atest -c VtsHalWifiHostapdV1_1TargetTest
Test: atest -c VtsHalWifiHostapdV1_0TargetTest
Change-Id: I6300a626db76e68873bbc34c489a9a8ee2d55e7a
Test: Run the test under an implementation that doesn't support
batteryChargeTimeToFullNowSeconds
Bug: 166841711
Change-Id: I18fb11bb0a2233a9a89183a5f9ecf597e7719172
Revert "Change payload type to int32_t for fmq device tests"
Revert submission 1431616-thirtytwo
Reason for revert: This topic broke the aosp_x86-userdebug target. Details at http://b/169077648
Reverted Changes:
If736389eb:Add template parameters to MQDescriptor
Ice9c28c3d:Change HIDL fmq tests to use int32_t for payload
Ia18d8459b:Add template arguments to MQDescriptor for AIDL
I95586cc83:Change payload type to int32_t for fmq device test...
Change-Id: Iaf37a5dca7a915f098e49ecb076c0932eb60e0c3
Revert "Change payload type to int32_t for fmq device tests"
Revert submission 1431616-thirtytwo
Reason for revert: This topic broke the aosp_x86-userdebug target. Details at http://b/169077648
Reverted Changes:
If736389eb:Add template parameters to MQDescriptor
Ice9c28c3d:Change HIDL fmq tests to use int32_t for payload
Ia18d8459b:Add template arguments to MQDescriptor for AIDL
I95586cc83:Change payload type to int32_t for fmq device test...
Change-Id: Ib7c409b164c76517d642a415cdfc2406e4f2f351
First parameter is used to determine the type of the payload, and the
second parameter is used to determine the type of queue.
Added two types to be use in that second parameter.
SynchronizedReadWrite and UnsynchronizedWrite.
Test: atest fmq_unit_tests fmq_test
Bug: 142326204
Change-Id: If736389ebecd02b87879850714606523e5145579
This is in preperation for more AIDL fmq testing. The types need to be
the same and AIDL does not support unit16_t.
Test: atest fmq_test fmq_unit_tests
Bug: 142326204
Change-Id: Ice9c28c3d0df064ea43c31950b3438d2e0d19063
