Revert "libmemtrack: Add support for AIDL memtrack HAL"
Revert "Add stable aidl memtrack HAL to product packages"
Revert "Add stable aidl memtrack hal to vndk list"
Revert "Memtrack HAL stable aidl sepolicy"
Revert "Add android.hardware.memtrack-unstable-ndk_platform"
Revert submission 1518702-memtrack-aidl
Reason for revert: Broken tests and boot time regressions
Reverted Changes:
Ic4dd70e2c:Add android.hardware.memtrack-unstable-ndk_platfor...
Iaf99d0ca4:Add stable aidl memtrack HAL to product packages
Iac54ae2ba:Add stable aidl memtrack hal to vndk list
If310210a3:libmemtrack: Add support for AIDL memtrack HAL
Ib6c634def:Memtrack HAL: Add stable AIDL implementation
I5e1d0e006:Memtrack HAL stable aidl sepolicy
Change-Id: I4a9e3522afe9e9189b7eddc9520d5ef2e2b74520
1ffcdebadd
Bug: 175345910
Bug: 171429297
Exempt-From-Owner-Approval: re-landing topic with no changes in this CL.
Change-Id: I691cad252f188b54a8076589d9955774d74d4729
The existing HAL has a setter, but no getter for the active slot for
next boot. The information is useful. For example, clients may need
to figure out which build the device will boot into.
In the resume on reboot case, we want to put the vbmeta digest
together with an encrypted key. And the vbmeta digest is associated
with a set of images (depending on which slot to boot into).
Bug: 173808057
Test: run vts test on cuttlefish
Change-Id: Ia8578926c781eb8e006589f45ab35a95dfe4f9a0
* Asks the device what set of capabilities are supported on the device
with respect to the Radio Hal
* The capabilities struct is left empty and will be filled
in once the first set of radio hal capabilities are nailed down later
in Android S
Test: Added cts, ran cts, and std tests
Bug: 163085807
Change-Id: I867f26bc649005e89ebf7a0b74f6fbeb2f44ac93
Introduce interface for vibrator manager HAL.
A default implementation is made available to the existing
android.hardware.vibrator-service.example, which now provides a top
level devault IVibrator and a top level IVibratorManager with a
different vibrator in it.
VTS tests were also introduced for the new manager, and existing tests
for IVibrator where changed to run in all top level and managed HAL
instances found on a device.
Bug: 166586119
Test: atest VtsHalVibratorTargetTest
atest VtsHalVibratorManagerTargetTest
Change-Id: Iec9175167e795bc03c4f3d873e2ac6682ed52512
USB Gadget hal v1.2 include:
1. NCM function support
2. inquiry USB speed
3. inquiry HAL version
Bug: 168282708
Test: build pass and functions works normally
Change-Id: I16927a06cd3e311ac6ab945f490eb0747638e6da
- Updated APIs to use strings instead of enum for AudioUsages
- Updated dumpsys commands to take strings for usages instead of
integers
Bug: b/170335834
Test: build and run VTS tests
Change-Id: I1773383812e97e7dee6da2eba250ea842d59b8cb
All HIDL HALs defined in the source tree must be specified
in some framework compatibility matrix.
Bug: 110261831
Test: builds
Change-Id: I98a0798cc08761e8aa6a9ca920c67aa6f8155de4
Merged-In: I98a0798cc08761e8aa6a9ca920c67aa6f8155de4
Also updates the compatibility matrix.
Bug: 166845383
Test: Run test on device with HAL 1.2 implemented, verify pass
Change-Id: Iac53e755cfa38fbd1322421279475de76b4bb572
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
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
Change-Id: I20f5b3665650c86fc0f976c544194f87157e6b90
No requirement has changed because TV HALs are optional.
Also remove TV CEC and tuner from fcm_exclude list.
Bug: 110261831
Test: m check-vintf-all
Change-Id: Ia41575f97d9e81fcc4279d8b274e626a33fc9c60
All HIDL HALs defined in the source tree must be specified
in some framework compatibility matrix.
Bug: 110261831
Test: builds
Change-Id: I98a0798cc08761e8aa6a9ca920c67aa6f8155de4
The first feature to support in this new Tuner HAL is the 64-bit id.
In the current CL, we support Demux and Filter ids in 64-bit format.
More component ids will be suppored in 64-bit in the following CLs.
Test: atest VtsHalTvTunerV1_1TargetTest
Bug: b/159058358
Change-Id: If05eb9f0cd76935064b2e51ff3ff1a3a477e3bd1