fba3ac86cc
Make VHAL to use the connector/server interfaces instead of talking to the (faked) vehicle directly. Use passthrough connector for now since we have not moved to the virtualized scenario yet (but soon :) Bug: b/141493212 Test: On both Osprey and Hawk. Build and flash the image. If on Osprey, see go/enable-google-vhal-on-osprey; if on hawk, `aae app vhal apply google` to enable Google VHAL ``` # no VHAL crash $ adb logcat $ vts-tradefed > run vts-hal-auto -m VtsHalAutomotiveVehicleV2_0Host # 30 passed, 2 failed, the same as the result before this patch # See value changed in Vehicle HAL tab, KitchenSink app: $ python packages/services/Car/tools/emulator/prop_event_simulator.py --property VEHICLEPROPERTY_HVAC_AC_ON --area 0 --value 1 # unit tests $ atest packages/services/Car/tests/vehiclehal_test/src/com/android/car/vehiclehal/test/CarPropertyTest.java ``` Change-Id: Iab77a0ae32db2c55b4c65aa8f3e4f73ec9ef2644 |
||
---|---|---|
.. | ||
audiocontrol/1.0 | ||
can/1.0 | ||
evs | ||
vehicle/2.0 | ||
OWNERS | ||
README.md |
Autmotive HALs
Overview:
The automotive HAL tree is used by Android Automotive to discover and operate hardware specific to a car.
The HALs are not (yet) frozen, as the HAL definition is expected to evolve between Android releases.