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
Since these were combined into libhidlbase.
Bug: 135686713
Test: build only (libhwbinder/libhidltransport are empty)
Change-Id: Iba2cd20b8b20fac3e7564de6b853b475fd4ebd2a
Signed-off-by: Subhajeet Muhuri <subhajeet.muhuri@gmail.com>
* squash from here
afafb3b3f3/light
* Added automatic max brightness detection
* Rework debug Statments
The xiaomi-sdm660-devs one created Led Light issues
Change-Id: Ie7b62a488770734e659f4db03436ebaa2f2f5f30
* 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
* To prevent property name collisions between properties of system and
vendor, 'vendor.' prefix must be added to a vendor HAL service name.
You can see the details in go/treble-sysprop-compatibility documents.
Test: succeeded building and tested on a sailfish device.
Bug: 36796459
Change-Id: I48e6ee0ae3fe401e39efb273256d991fac676357
Required because the lights need to be turned off late in boot
(e.x. during fsck for disk health), and before, blank_screen
accessing light encountered a race condition where if it didn't
get scheduled before all of the processes which were getting
shutdown were getting killed, the screen wouldn't blank.
Bug: 74976325
Test: adjusting brightness continues to work
Test: screen blanks during shutdown at the correct time
including when an artificial 5s delay is inserted when
the phone normally fscks (which can also be quick)
Change-Id: I57ebc11d7ecf57ee327c681455712f4b53de6fd3
