com.google.android.overlay.modules.cellbroadcastservice Copy

The sibling of com.google.android.overlay.modules.cellbroadcastreceiver, a Runtime Resource Overlay whose name points at CellBroadcastService rather than at the receiver app. CellBroadcastService is the half of the CellBroadcast Mainline module that handles cell-broadcast SMS decoding, geofencing for wireless emergency alerts and distribution of those messages, where CellBroadcastReceiver is the part that displays them. AOSP documents the RRO customisation route for the receiver and names that package as the overlay target; it does not publish an equivalent description for a service-targeting overlay, so the exact resource values this package sets could not be sourced and are treated here as build-specific. Like its sibling it has no user interface and is applied by the overlay manager. Version note: as above, CellBroadcast has been an updatable Mainline module since Android 11. In this site's sample this overlay is recorded with version names 12 through 17 and target SDK 31 to 37, and always appears alongside the receiver overlay on the same devices. Provenance note: as with the receiver overlay, this site's sample records it only on Samsung devices, signed consistently with a single Samsung certificate that is not recorded as also signing the framework. For Android Enterprise, EMM and kiosk use it has no enrolment or policy role and nothing a user interacts with. Because the module it accompanies carries emergency alerting, which is a regulated function in many countries, this is not a package to experiment with on managed fleets; disabling it offers no benefit, so treat it as caution and test per device if it is touched at all.

• CellBroadcast - Android Open Source Project →
• Change the value of an app's resources at runtime (RROs) - Android Open Source Project →
• Package provenance for com.google.android.overlay.modules.cellbroadcastservice - Android System App Database →

• Signed by the device maker's own signing key (Samsung), so it is an OEM preinstall, and that single certificate is consistent across all 22 device profiles. Inferred from the certificate appearing only on Samsung devices (81 packages, 1815 observations).
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.