health: Update README to remove .override [DO NOT MERGE]

The .override module does not have correct rc and
sepolicy file_contexts configured, so let's allow
OEMs to keep healthd. If an OEM does want to remove
healthd they can provide a device-specific
health service impl.

Test: none
Bug: 110228707
Change-Id: I9ba32ae366df4ba58994ef0e3f9eb57cab5626f7

diff --git a/health/2.0/README b/health/2.0/README
index 11e6a7aaf1e018a20cc4ac5d1796f558ed1111c6..dfd965aa5a45134a6d20dcb9f62760a58e0fe122 100644 (file)
--- 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.