diff options
Diffstat (limited to 'health')
| -rw-r--r-- | health/2.0/README | 19 |
1 files changed, 5 insertions, 14 deletions
diff --git a/health/2.0/README b/health/2.0/README index 11e6a7aaf..9f77b8372 100644 --- a/health/2.0/README +++ b/health/2.0/README @@ -6,12 +6,7 @@ Upgrading from health@1.0 HAL 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 @@ cc_binary { 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 |