Merge "health: properly support charger mode." am: 21c1e163d4 am: d9964bb31a

Original change: https://android-review.googlesource.com/c/platform/hardware/interfaces/+/1894881

Change-Id: I07f1661448c9229e4c2d906abc4903d481ccc940
This commit is contained in:
Treehugger Robot 2021-12-01 04:18:19 +00:00 committed by Automerger Merge Worker
commit 233a367c14
2 changed files with 5 additions and 4 deletions

View file

@ -63,8 +63,7 @@ Specifically:
* You may ignore the `service` line. The name of the service does not matter.
* If your service belongs to additional classes beside `charger`, you need a
custom health AIDL service.
* You may ignore the `seclabel` line. When the health AIDL service runs in
charger mode, its original SELinux domain is kept.
* Modify the `seclabel` line. Replace `charger` with `charger_vendor`.
* If your service has a different `user` (not `system`), you need a custom
health AIDL service.
* If your service belongs to additional `group`s beside
@ -240,6 +239,8 @@ for an example:
```text
service vendor.charger-tuna /vendor/bin/hw/android.hardware.health-service-tuna --charger
class charger
seclabel u:r:charger_vendor:s0
# ...
```
@ -315,6 +316,5 @@ permissions. Example (assuming that your health AIDL service runs in domain
`hal_health_tuna`:
```text
type hal_health_tuna, charger_type, domain;
hal_server_domain(hal_health_default, hal_health)
domain_trans(init, hal_health_tuna_exec, charger_vendor)
```

View file

@ -7,6 +7,7 @@ service vendor.health-default /vendor/bin/hw/android.hardware.health-service.exa
service vendor.charger-default /vendor/bin/hw/android.hardware.health-service.example --charger
class charger
seclabel u:r:charger_vendor:s0
user system
group system wakelock input
capabilities SYS_BOOT