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
* Use libbase logging and file utils
* Read max brightness from sysfs
* Convert constants to constexpr
* Move helper functions to anonymous namespace
* Bug fixes
* Remove redundant chmod
* Start the service after permissions are set up because it reads max
brightness in constructor.
Change-Id: I145d393c785e182060c5651e796d489f8c4d697b
