This reverts commit 9ed325bfff.
Bug: 218588089
Test: 1. Build cf_x86_64_auto lunch target.
2. Launch cvd in the accelerated graphics mode.
3. Run evs_app and confirm the color bar pattern is shown on the
display.
> adb root && adb shell evs_app --test
4. Do the same on sdk_car_x86_64 lunch target.
Change-Id: If15ee3c14eb2a9fce00bd7950b717e7fc690755b
We are serving V3 of the interface, so reflect that in the manifest
fragment.
Allow it in the compat matrix.
Test: lunch cf_x86_64_auto-userdebug && atest hal_implementation_test
Bug: 266868868
Change-Id: Ib858b6e9eb7025fe05670641d55ca98389553077
We are serving V2 of the vhal interface, so reflect that in the manifest
fragment.
Test: lunch cf_x86_64_auto-userdebug && atest hal_implementation_test
Bug: 266868868
Change-Id: I86217712f225df64cb3494be3461d7ff39d80064
Revert submission 20583557-Satellite APIs
Reason for revert: We need to revert these changes for U
Reverted changes: /q/submissionid:20583557-Satellite+APIs
Bug: 271297374
Test: Call and SMS/MMS with live network.
atest TelephonyManagerTestOnMockModem
atest VtsHalRadioTargetTest
atest com.android.cellbroadcastreceiver.compliancetests.CellBroadcastConfigTest
atest android.telephony.cts.TelephonyManagerTest
atest android.telephony.cts.SatelliteManagerTest
Change-Id: I7ada8e72d77543f1ac03b267d61e8fd037ec3708
This cl removes the unused service android.hardware.security.dice
together with all its usages (all of them are tests), because the
service is incomplete and not used anywhere for now and in the
near future.
The cl also removes dice from the compat matrix.
This helps us reduce some maintainance burden for the Rust dice
wrapper libraries such as libdiced_open_dice[_nostd],
libdiced_sample_inputs, libdiced_utils and their tests.
Test: atest diced_utils_test diced_sample_inputs_test \
diced_open_dice_cbor_test \
libdiced_open_dice_nostd.integration_test \
libdiced_open_dice.integration_test diced_open_dice_cbor_test
Test: m pvmfw_img microdroid_manager
Bug: 267575445
Bug: 270511529
Change-Id: I3d2497d2e8d3f88c49cae9ae80a6b4f7b652cc4a
Define in-vehicle network android device HAL.
This HAL is used for providing run-time information about other
connected Android devices in the same vehicle for multi-soc use
cases.
Test: m android.hardware.automotive.ivn-update-api
Bug: 258494092
Change-Id: I0b16e17b04e3470ad8f05d36daac3052f004a53f
To avoid incompatibility errors marking the hidl version of
gatekeeper as optional.
Bug: 268342724
Test: VtsHalGatekeeperTargetTest
Change-Id: Id9546844998ce88ed597eaae0c05a119fb9322c9
This interface is deprecated for new devices from level 8 of the
framework compatibility matrix.
Test: none
Bug: 170405615
Change-Id: Ibdf12a382435abe845a31cce580c4e98b2d57e06
Devices launching with P VINTF requirements
(including HALs and kernels) will
not be able to update to Android U.
If a device wish to do so, it must update the
vendor / odm partitions to match newer VINTF
requirements.
The list in fcm_execlude is generated with:
system/libvintf/analyze_matrix/hals_for_release.py -d -j --package-only | python3 -m json.tool
in the 3~4 section.
Test: TH
Bug: 205175891
Change-Id: I0f3584f461f9545ca9d3a508baa1e2fc562eabd3
The AOSP-version of wifi hal apex now contains the VINTF fragment in it.
Bug: 247018693
Bug: 266885060
Test: atest CtsWifiTestCases
Merged-In: Id8f196386967c3023cb5ee308d31b8cdeed7df0b
Change-Id: Id8f196386967c3023cb5ee308d31b8cdeed7df0b
The AOSP-version of wifi hal apex now contains the VINTF fragment in it.
Bug: 247018693
Bug: 266885060
Test: atest CtsWifiTestCases
Change-Id: Id8f196386967c3023cb5ee308d31b8cdeed7df0b
A common workflow for vendors is to develop their new launching devices
targeting N-1 compatibility matrix so they can update each of their HALs
independently at different times.
This works because the target (N-1) framework compatibility matrix is squashed
with the newer compatibility matrices allowing the use of newer
interfaces.
This doesn't work when converting a service from HIDL to AIDL when the
HIDL service is marked as optional="false". It allows for the use of the
new AIDL interface, but it still requires the old HIDL interface.
Marking the old HIDL interfaces as optional allows vendors to develop
before the device targets level 8.
Test: atest vts_treble_vintf_vendor_test
Bug: 247575800
Change-Id: I0da1b10b2bf5c10b19b2713b56be72738a15eec1
A common workflow for vendors is to develop their new launching devices
targeting N-1 compatibility matrix so they can update each of their HALs
independently at different times.
This works because the target (N-1) framework compatibility matrix is squashed
with the newer compatibility matrices allowing the use of newer
interfaces.
This doesn't work when converting a service from HIDL to AIDL when the
HIDL service is marked as optional="false". It allows for the use of the
new AIDL interface, but it still requires the old HIDL interface.
Marking the old HIDL interfaces as optional allows vendors to develop
before the device targets level 8.
Test: m
Bug: 247575800
Change-Id: I4446cdaa4a44b4dae1e9eee68089bf723dd25276
1. add the new propertes
- batteryHealthData
- batteryStateOfHealth
- chargingState
- chargingPolicy
2. add new types to health status
3. add new methods
- setChargingPolicy
- getChargingPolicy
- getBatteryHealthData
Bug: 251425963
Test: m android.hardware.health-update-api
Change-Id: Ie2339c50e1f9bfc28427e4108a95b1a16c739205
Signed-off-by: Jack Wu <wjack@google.com>
