Devices with legacy/O/O-MR1 VINTF won't be able to
update to Android S. Devices launching with pre-O,
O, or O-MR1 will need to update its VINTF to P and
above to work with Android S.
Test: builds
Bug: 163419744
Bug: 171260360
Bug: 171260613
Bug: 171260670
Bug: 171260715
Change-Id: I2a65f5a24c0731df9c4247bf9dd2616c2279042f
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
Add CAP_BLOCK_SUSPEND to android.hardware.health@1.0 and
android.hardware.health@2.1 service so that when epoll_wait()
is waiting on uevents and timer_fd events it can block suspend
to take the necessary action. Without this permission, eventpoll
is going to ignore the flags EPOLLWAKEUP used in health HAL or
healthloop.
Bug: 169873088
Change-Id: If9b0e1f60e47d7bf54942f589acbfbb883b9bac8
Moved the types to andrdoid.hardware.common.fmq.
This allows modules to depend on the unstable version of the library
without conflicting with modules that depend on the stable version of
android.hardware.common.
Test: atest fmq_unit_tests fmq_test
Bug: 142326204
Change-Id: I3091f52c4e763a15fd9a1b7451a1455a06fb4c30
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 needs to be disabled on Pixel 3, but this is the only place w/
source code visible in AOSP. So, it is implemented as a mechanism.
Bug: 166675194
Test: atest android.hardware.camera2.cts.PerformanceTest
Change-Id: I0d91389432906a917696d27d27b4d6d96e64d09f
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
