This HAL version is not supported by the framework. Remove the code to
avoid confusion.
Bug: 178772241
Test: make
Change-Id: I278415d1945fbf5010539840efdc9e9502957f3f
This HAL is not supported by the framework. It was confirmed that
no devices were using this HAL version and it will be removed
following this change.
Bug: 178772241
Test: make
Change-Id: Ie73e78ffde79345331753eb9ed4616653616ddf3
With current setDataLimit API, tethering offload hardware will
stop offload and trigger callback when the given limit bytes is
reached.
However, for data usage warning to work, an API that allows
tethering offload hardware to report event without stopping
offload hardware is needed.
Test: hidl-gen -Lformat android.hardware.tetheroffload.control@1.1
Bug: 149467454
Bug: 170699770
Bug: 170179169
Change-Id: I804d15f92251ef902dd2e1ff1c31ba157fa91067
- Add IIdentityCredential.deleteCredentialWithChallenge()
- Deprecate IIdentityCredential.deleteCredential()
- Add IIdentityCredential.proveOwership()
- Add IIdentityCredential.updateCredential()
- Add ProofOfBinding CBOR to AuthenticationKey X.509 certificate
- Document which API versions new methods/features appeared in.
- Mention need to declare android.hardware.identity_credential system
feature (w/ feature version number) and do this for the default
implementation.
Bug: 170146643
Test: atest VtsHalIdentityTargetTest
Change-Id: Ib47c7caa5f3d6fff6919f019eee44a735dba9cf8
* 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
Merged-In: I867f26bc649005e89ebf7a0b74f6fbeb2f44ac93
Change-Id: I837d82592e8ddfef5b1ff5eb0dd983a0d13383ed
If a device launching with S VINTF uses health storage HAL,
it must use AIDL. If HIDL health storage HAL is used,
a build error will occur to complain about deprecated HALs.
Test: manual test that if the HIDL HAL is served on cuttlefish, then
`m check-vintf-all` shows the following error:
android.hardware.health.storage@1.0::IStorage/default is deprecated
in compatibility matrix at FCM Version 6; it should not be served.
Bug: 177470478
Change-Id: I3c28352f5f8d491ed0e1f9292b80d2083699f829
* changes:
health storage AIDL VTS test.
health storage: refactor common code for test
Add default impl for health storage AIDL HAL
Add health.storage AIDL HAL
Refactor common implementation for health storage HAL.
This is reverted in AOSP because vibrator 2 has not been published
in AOSP, but relanded in internal because vibrator 2 is in internal.
This reverts commit 6135189a29.
Test: TH
Bug: 150034914
Change-Id: I94a663be8a07a24587127d3ca489647a16c0be7a
Revert submission 1540633
Reason for revert: AOSP not updated yet
Reverted Changes:
I418cd4fc5:Update AIDL IVibrator manifest version to 2.
I08b4b189d:matrix: IVibrator AIDL has version 2.
Change-Id: I429faacf309aa61aa044d72b873e23ba25ed5bca
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
This reverts commit 540dc2771a.
Reason for revert: reland because target-level 2 are fixed
Bug: 163419744
Change-Id: I293852d50de9a4eeaeec6ccf4c0290f1c1b0012d
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
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
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
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
