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>
This patch converts Tetheroffload HIDL to AIDL and adds an empty
example implementation.
There are some changes in AIDL HAL:
1. Combine IOffloadConfig and IOffloadControl into IOffload
2. Use AIDL builtin errors exception code with message as return
Bug: b/205762647
Test: m android.hardware.tetheroffload-update-api
m android.hardware.tetheroffload-V1-ndk
m android.hardware.tetheroffload-service.example
atest VtsHalTetheroffloadTargetTest
Change-Id: I9859ff3df608c058786b4e2b91cb6cd5f38e653a
This interface is deprecated as of level 8. Use the AIDL CAS interface
instead.
Test: none
Bug: 227673974
Change-Id: I34c1034f247796f81f37a0c337385cdbe2005191
This HIDL interface is deprecate in level 8. The AIDL gatekeeper
interface should be used instead.
Test: none
Bug: 205760843
Change-Id: I58b8ca77ae9ab8d055a45871918dbd91435823a7
