com.sec.android.app.personalization Copy

A very small Samsung platform component labelled "Perso" on the device. It is signed by Samsung OEM keys that also sign the Android framework, it has no launcher entry, and the builds recorded here are only tens of kilobytes. It declares just two permissions, both privileged telephony ones: MODIFY_PHONE_STATE and READ_PRIVILEGED_PHONE_STATE. Those permissions establish what it is permitted to do rather than what it actually does, but they are consistent with a telephony-related role, and the package presents no user interface of its own. Samsung publishes no description of this package. In mobile telephony the abbreviation "perso" conventionally refers to personalisation, the standard mechanism by which a handset can be locked to a network, a network subset, a service provider, a corporate customer or a specific SIM, and the two telephony permissions above are consistent with that reading. We could not source anything from Samsung or elsewhere that confirms it, so treat the connection as unconfirmed rather than established, and do not assume this package is what enforces a carrier lock on any given device. Version note: its version string tracks the Android platform release rather than an app version of its own. Samsung's published application lists show version 10 on an Android 10 Galaxy and version 11 on an Android 11 Galaxy, and the builds recorded here run from 12 to 17 with target SDK levels from 31 to 37. It is therefore rebuilt with each platform release, and it is still present on current Android versions. We could not source whether its role has changed across those releases. For Android Enterprise, EMM and kiosk deployments it has no enrolment or management role and presents nothing a user interacts with. It is small, silent and has no known benefit from being removed, while its privileged telephony permissions mean the consequences of disabling it are not predictable from the outside, so the safe course is to leave it alone. This matters most on operator-supplied or subsidised handsets, where telephony locking is part of the commercial arrangement.

• Galaxy A51 5G (A516V) Application List - Samsung Knox CC Mode documentation →
• Galaxy XCover Pro LTE (G715U) Application List - Samsung Knox CC Mode documentation →
• Package provenance for com.sec.android.app.personalization - 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 2 permissions: 2 signature or system-level. 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.