Age | Commit message (Collapse) | Author |
|
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
|
|
So that init knows how to start it and to provide
an example of how to specify interfaces since there
are no lazy starting services on Pixel yet.
In order to make lights a lazy service, it would also
have to be marked as 'oneshot'.
Test: manually using Light as a lazy service
Bug: 64678982
Merged-In: I846a7e2d9545b42af9b985adb74883bda1b8c355
Change-Id: I846a7e2d9545b42af9b985adb74883bda1b8c355
|
|
Change-Id: Id13a42976df428c95c19eae49e1c114f057510bb
|
|
* 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
[SQUASHME] Let's dejank paths a bit...
Change-Id: Ifd3d05588b0271e7a361aa4c7374a91fe5639a1f
|
|
Change-Id: I097c542f95434d85b8c041b156dfd81952c64164
|
|
Change-Id: Ib45e537c795b9ce6651c361b68f80ee28a616cad
|
|
Change-Id: I903039730f4181f6a326f28e0ea212db68bdabcc
|