The hal class is essentially triggered from the boot class, so it's possible that the HAL starts before the permissions are set, and manual intervention was added to deal with the issue. However, we can simply move chown to an earlier stage to avoid playing with the workflow. Change-Id: I189b247576151f76efaf26b2d266564dc7768fba |
||
---|---|---|
.. | ||
Android.bp | ||
android.hardware.light@2.0-service.xiaomi_sdm660.rc | ||
android.hardware.light@2.0-service.xiaomi_sdm660.xml | ||
Light.cpp | ||
Light.h | ||
service.cpp |