com.sec.app.RilErrorNotifier Copy

Labelled "RilNotifier", this is a Samsung-signed system package with no launcher entry, recorded as not user-facing on every observation here. RIL is the Radio Interface Layer, the telephony layer AOSP documents in its core connectivity material, so the name places this app alongside the modem and service-mode tooling this site covers elsewhere. The reason to read this entry is that its declared permissions are far broader than the name suggests. Recorded here are android.permission.HARDWARE_TEST, which the platform manifest defines as allowing access to hardware peripherals and describes as intended only for hardware testing, at signature protection level and not for third-party use; ACCESS_CHECKIN_PROPERTIES, which the same manifest defines as read and write access to the properties table in the checkin database, to change values that get uploaded; and REBOOT, MODIFY_PHONE_STATE, READ_PRIVILEGED_PHONE_STATE, WRITE_APN_SETTINGS, WRITE_SETTINGS, CLEAR_APP_USER_DATA, MOUNT_UNMOUNT_FILESYSTEMS, CHANGE_CONFIGURATION, MODIFY_AUDIO_SETTINGS, BLUETOOTH_ADMIN and INTERNET. It also declares com.sec.android.app.factorymode.permission.KEYSTRING and com.sec.phone.permission.SEC_FACTORY_PHONE. A keystring is one of the star-and-hash sequences typed into the dialler to reach a hidden engineering screen, and that declaration is consistent with the keystring family covered by this site's notes on Service mode and DRParser Mode. It establishes what this package declares, not that it is itself reachable from the dialler: no source examined here demonstrates a runtime route. Samsung publishes no functional documentation for the package, so what it does with that set is not sourceable, and this note does not guess. The honest summary is that a component named as an error notifier declares the ability to reboot the device, rewrite APN settings and clear application data, and that the gap between the name and the declaration is itself the finding. Version note. Samsung's application lists record it at 1.0.0 on Android 9-era Galaxy S10+ firmware and at 1.0.0 on both Android 11-era lists examined here, and this site records 1.0.0 as both the oldest and the newest build observed, so the version string is static across every data point available and cannot be used to tell builds apart. The target SDK moves from 31 to 37 and the package is observed from API 28 through API 37. Nothing sourced suggests it has been superseded, modularised or default-disabled in a recent release. For Android Enterprise, EMM and kiosk use, treat it the same way as the rest of Samsung's engineering tooling. Its declared reach into APN settings, phone state and device reboot is exactly the sort of surface a dedicated or shared device should not expose, and where a build also makes engineering screens reachable from the dialler that compounds it. The practical control is the app allowlist: keep the dialler and other system apps out of a kiosk allowlist unless they are needed, then test the finished build by actively trying to escape it. In the Android Management API the documented lever is an application policy with installType BLOCKED, which the reference defines as the app being blocked and unable to install, and uninstalled if it was installed under a previous policy; the reference does not state what that does to a package preinstalled in the system image, so confirm the outcome on the device model in question. Samsung does not document what depends on it, so disabling is rated caution.

• core/res/AndroidManifest.xml (android.permission.HARDWARE_TEST, ACCESS_CHECKIN_PROPERTIES) - Android platform source →
• RIL refactoring (Radio Interface Layer) - Android Open Source Project →
• Galaxy S10+ LTE (G975F) application list - Samsung Knox CC Mode documentation →
• Galaxy S20 FE 5G (G781B) application list - Samsung Knox CC Mode documentation →
• Galaxy S20 Ultra 5G (G988W) application list - Samsung Knox CC Mode documentation →
• Policies resource (ApplicationPolicy installType) - Android Management API →
• How do I prevent users from escaping kiosk (lock task) mode? - Jason Bayton →
• Package provenance for com.sec.app.RilErrorNotifier - Android System App Database →

• Signed by the device maker's own signing key (Samsung), so it is an OEM preinstall, but 2 different certificates appear across the fleet, so OEMs ship their own builds of it. It also signs the Android framework, so it is a platform-level key on its device(s). Inferred from the certificate appearing only on Samsung devices (508 packages, 10196 observations).
• Its largest observed manifest declares 19 permissions: 1 runtime (user-granted), 10 signature or system-level, 6 install-time and 2 vendor or uncatalogued. The signature/system share marks it as a privileged component, not an ordinary app.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.