com.google.android.overlay.modules.healthfitness.forframework Copy

A Runtime Resource Overlay (RRO) related to the Android Health module, which contains Health Connect: the on-device store for health and fitness data, protected by granular permissions. The "forframework" suffix indicates an overlay targeting the core framework package ("android") rather than the module itself, following the same pattern as the other module overlays documented here. On this site it is seen signed by OEMs rather than by Google. It has no launcher icon and is applied by the overlay manager, not opened; Health Connect itself is reached through Settings. Version note: this is the clearest version-dependent package in this file. The Android Health module (packages/modules/HealthFitness, an APK in APEX format) is available on Android 14 and higher, where Health Connect became part of the framework; on Android 13 Health Connect was instead a separate app installed from Google Play. That matches this site's sample, in which the overlay is observed only from API 34 (Android 14) upwards and not below. The specific resource values it sets are not publicly documented and vary by build. For Android Enterprise, EMM and kiosk use it has no enrolment or policy role, and it is not the control for restricting health data - that is governed by Health Connect's permissions. Disabling the overlay offers no benefit and could revert framework-visible configuration the build expects, so treat it as caution and test per device.

• Change the value of an app's resources at runtime (RROs) - Android Open Source Project →
• Android Health - Android Open Source Project →
• Migrate Health Connect from Android 13 (APK) to Android 14 (framework) - Android Developers →
• Package provenance for com.google.android.overlay.modules.healthfitness.forframework - Android System App Database →

• Re-signed by each device maker with its own platform key - 14 different certificates appear across 12 device makers in our sample. That is the signature of a stock AOSP/system package every OEM builds and signs itself, not a single maker's or a third party's preinstall. These are platform-level keys: they also sign the Android framework itself.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.