healthd use vintf_fragments
This encourages device manufacturers to use
service.override over service and to remove healthd
on device, because it is one less step to do.
Test: make VINTF metadata
Bug: 66917623
Change-Id: I447395450060cdf17731514bb9a5e3ed912bbc66
Merged-In: I447395450060cdf17731514bb9a5e3ed912bbc66
(cherry picked from commit ae005c46101883a9c7938de9bc0286cfc4e7b7b8)
diff --git a/health/2.0/README b/health/2.0/README
index 11e6a7a..9f77b83 100644
--- a/health/2.0/README
+++ b/health/2.0/README
@@ -6,12 +6,7 @@
1. If the device does not have a vendor-specific libhealthd AND does not
implement storage-related APIs, just do the following:
- 1.1 (recommended) To remove healthd from the build,
- PRODUCT_PACKAGES += android.hardware.health@2.0-service.override
- DEVICE_FRAMEWORK_MANIFEST_FILE += \
- system/libhidl/vintfdata/manifest_healthd_exclude.xml
- 1.2 To keep healthd in the build,
- PRODUCT_PACKAGES += android.hardware.health@2.0-service
+ PRODUCT_PACKAGES += android.hardware.health@2.0-service
Otherwise, continue to Step 2.
@@ -53,16 +48,12 @@
header_libs: ["libhealthd_headers"],
- // Uncomment the following to remove healthd from the build.
- // overrides: [
- // "healthd",
- // ],
+ overrides: [
+ "healthd",
+ ],
}
- 3.1 (recommended) To remove healthd from the build, keep "overrides"
- section, and include the following in device.mk:
- DEVICE_FRAMEWORK_MANIFEST_FILE += \
- system/libhidl/vintfdata/manifest_healthd_exclude.xml
+ 3.1 (recommended) To remove healthd from the build, keep "overrides" section.
3.2 To keep healthd in the build, remove "overrides" section.
4. Create device/<manufacturer>/<device>/health/android.hardware.health@2.0-service.<device>.rc