com.android.theme.font.notoserifsource Copy

Labelled "Noto Serif / Source Sans Pro", this is a font theme overlay: a Runtime Resource Overlay (RRO) whose only job is to switch the system typeface to Noto Serif (for serif text) and Source Sans Pro (for sans-serif text). An RRO changes a target package's resource values at runtime without modifying its code, and AOSP documents that "you can now use runtime resource overlays (RROs) to change fonts", which is exactly what this package does. It contains font resources only, with no executable app code, no launcher icon and nothing a user opens directly; it becomes active when a matching font style is selected in the device's theme or personalisation settings. On this site it is seen signed by Google and by many OEMs (Samsung, Xiaomi, Motorola, Nothing and others), because each build ships its own copy of the overlay. For Android Enterprise, EMM and kiosk use it is purely cosmetic. It plays no part in enrolment, policy or any device function; at most it offers an alternate system font. If the overlay is not the selected font it sits inert, and if it is, disabling or removing it simply reverts text to the default typeface, so it is safe to disable where an administrator wants to remove the option. Version note: this is an optional theming overlay rather than a fixed platform component, so its presence and the set of font styles offered vary by OEM, skin and Android release. The site records builds tagged for different Android versions (for example Samsung builds for Android 15 and Android 16), which reflects each vendor rebuilding the same overlay per release rather than a change in its role. Some OEM font pickers use their own mechanisms, so an equivalent option may be presented differently on non-Pixel devices.

• Change the value of an app's resources at runtime (RROs) - Android Open Source Project →
• Add custom fonts (use RROs to change fonts) - Android Open Source Project →
• Package provenance for com.android.theme.font.notoserifsource - Android System App Database →

• Re-signed by each device maker with its own platform key - 28 different certificates appear across 16 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.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.