light/2.0/default/android.hardware.light@2.0-service.rc

service vendor.light-hal-2-0 /vendor/bin/hw/android.hardware.light@2.0-service
    interface android.hardware.light@2.0::ILight default
    class hal
    user system
    group system
    # shutting off lights while powering-off
    shutdown critical
Add 'vendor.' prefix to a vendor HAL service name 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 http://go/treble-sysprop-compatibility. Test: succeeded building and tested on a walleye device Bug: 36796459 Change-Id: I4e8fbee791ec917a8f627a1366f4d44ec7e6febc 2017-08-30 11:13:32 +09:00			`service vendor.light-hal-2-0 /vendor/bin/hw/android.hardware.light@2.0-service`
Add interface specification for lights hal. 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 Change-Id: I846a7e2d9545b42af9b985adb74883bda1b8c355 2018-01-04 17:31:57 -08:00			`interface android.hardware.light@2.0::ILight default`
Adding android.hardware.light@2.0 service. Bug: 32022100 Test: end-to-end Change-Id: I2d143f3a283e3a230c5ae4999e492f29ffe4234c 2016-10-03 09:20:36 -07:00			`class hal`
			`user system`
Add 'vendor.' prefix to a vendor HAL service name 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 http://go/treble-sysprop-compatibility. Test: succeeded building and tested on a walleye device Bug: 36796459 Change-Id: I4e8fbee791ec917a8f627a1366f4d44ec7e6febc 2017-08-30 11:13:32 +09:00			`group system`
light service: mark as shutdown critical 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 2018-03-16 10:23:14 -07:00			`# shutting off lights while powering-off`
			`shutdown critical`