All biometrics (fingerprint/iris/face) are now under
android.hardware.biometrics namespace. Fingerprint has a legacy
android.hardware.fingerprint definition for compatibility.
Bug: 115639644
Test: biometrics are available on their respective devices
Change-Id: I947d6793a879b2b92aea2ed5e57c86e490c7289e
This patch adds a feature flag for IPsec Tunnel Mode. This implies VTI
(with output-mark updating), or XFRM-I in the kernels.
Bug: 117183273
Test: Compiles
Change-Id: I9c1a84707366c841c27b74050d276cac9bd61460
AOSP builds have different product & brand values than the ones flashed
onto the device's Keymaster in the factory.
As a result, Device ID attestation will not work on them correctly
because there is a mismatch between the values sent to Keymaster by the
platform and the values Keymaster is expecting to attest to.
Mark AOSP builds as not having this feature since it would affect all
AOSP builds on all devices.
Bug: 110361822
Test: atest com.android.cts.devicepolicy.MixedDeviceOwnerTest#testKeyManagement
Change-Id: I55e7c68b3e082af465c19cf18aeeeecffc4eb356
Updated AppOpsManager.h constants with those defined in AppOpsManager.java
Test: Builds
Bug: 110385761
Change-Id: Idc7da66f318b9f34d8e513e82c9cf622e73d4ca2
Signed-off-by: Gilad Bretter <gilad.bretter@intel.com>
Remove library tag in android.hardware.usb.accessory.xml, since it will
be generated automatically by soong when the library is built with
java_sdk_library.
Bug:77577799
Test: make -j
make checkapi
Change-Id: I9555678e5551aba2eebfe74184fe9cbc91948dfa
android.hardware.location.network is incorrectly getting included in
aosp targets without a valid location provider. Adding this xml to
include in aosp target configurations.
Test: lunch aosp_taimen-userdebug; build and flash
Then
atest android.app.cts.SystemFeaturesTest
Bug: 33380753
Change-Id: I4f4d189bd605b8d4798dbd7640ac56cbec28c618
This doesn't make sense on things like wear and appliances,
so make this an optional feature that the device must enable.
If the feature is not set, then the system will ignore
the app's request.
Bug: 76213401
Test: atest CtsAppTestCases:ActivityManagerProcessStateTest
Change-Id: I6330d2586004ee0a03cbcd8e10be5f6cda2bcbae
Add a feature flag to find out if Device ID attestation is supported or
not, as it is an optional feature.
Otherwise, the cts tests could not meaningfully say if the device
correctly supports this feature or not.
Bug: 72642093
Bug: 73448533
Test: Modified CTS tests.
Change-Id: I1f26dacc8bbe7e9c11bb8b14efae41e10d918a73
Add feature flag to indicate that the device has EMBMS middleware
installed
Test: compile and use adb
Change-Id: I307dfc24f20262e84fc4e540c4e01352ac04cae7
Add Wi-Fi RTT feature flag - allows configuration of devices to
indicate whether or not they support the feature.
Bug: 65014628
Test: builds, integration tests pass
Change-Id: Iab18e1607ec6a8eefc7de6646d6cd66dee43d7d0
Conditionally add the "android.software.preview_sdk" feature to any
targets that have a Build.VERSION.CODENAME != "REL". This allows clients
to filter out platforms that are not running official Android releases.
Bug: 31064561
Test: verified using PackageManager#getSystemAvailableFeatures()
Change-Id: I0c6a96d611df0823769feb12105b9669a2109358
So we can start the NFC process whenever one of
these is present.
Bug: 36873979
Bug: 37269025
Test: NFC is still started on devices with this feature
Change-Id: I879c084c1ed56e33a4249172c8fa3c04b1c5f236
...File ata/etc/tv_core_hardware.xml does not exist
Add new separate file for the CTS feature.
Test: none needed
Change-Id: I3be83072e65781224c735b920b0b4fba22f57e4c
