In case of error during ov10635 init the I2C commands need to be resend.
The serial link however suffers spurious I2C acknowledges during OV10635 init
and it is required to raise reverse channel amplitude to get reliable
ACK/NACK response.
The OV10635 camera kit of max9271, max9286 can't be enumerated after soft
reset because of high threshold of communication channel. Keep the voltage
low. Also lets use max9271_set_translation for the camera addressing instead of
changing real camera address.
echo 0/1 > /sys/devices/platform/vehicle-dummy/auto_on has to change propertyValue of VEHICLE_AUTO_ON for same areaIDs that is used by VEHICLE_HVAC_POWER_ON property
Define known VehiclePropertyIds from Google documentation and suppressing kernel console messages related to them ('this type is not correct') during boot
Before migration of VHAL from hidl to aidl, changing any property for multiple areas could be handled by single message containing one areaId, which was equal to the sum of areaIds of the targets for this change. After the migration, this is no longer possible, and for each change there has to be a separate message with the specific areaId of the target.
Example:
hidl - change of X for every seat - 1 message with target area id HVAC_ALL = 117 = 1 + 4 + 16 + 32 + 64 (1_left,1_right,2_left,2_center,2_right)
aidl - change of X for every seat - 5 messages with target area id 1, 4, 16, 32, 64
Google probably chose this approach because it doesnt hardcode what all seats means, which makes sense since different cars could have different number and configuration of seats (for example we can already see definiton of 3rd row of seats in configs). So using this method will be easier for future HVAC apps..
However currently used HVAC app in A14 contains only one UI every element for every configuration that is using HVAC_ALL areaId. So now using aidl - message targeted at any of those configs and containing only ONE of the areaIds mentioned before 1 / 4 / 16 / 32 / 64 (not sum or combination) will result in changing the element. Using areaId 117 as before will result in failure. So for current HVAC app we are changing HVAC_ALL to 1 (as one of the available options).
Allow sending sending property values from Vehicle HAL into M4 prior
Android registration in M4. Added new INIT message. Without this
new state messages was possible to send only after registration.
Check on input value range moved from "dummy" specific support
to vehicle_core file common for "m4" and "dummy" implementations.
Now are the checks applied equally for both cases.
VHAL is now constantly sending the vehicle speed. Do not pass
this messages to M4 side. Otherwise it is incorrectly recognized
by the M4 demo and the cmd line is not usable there.
Car service now check if the areaID of the changed property match.
Otherwise change is ignored. With this fix correct areaID is
propagate together with the property value.
