com.samsung.android.cidmanager Copy

A Samsung system component that sits in the same customisation area as com.samsung.android.sdm.config above, and like it has no launcher entry in any observation here. Devices on this site label it "Configuration update" across every locale recorded. The honest limitation first: Samsung publishes no documentation for this package, and the "CID" in its name is not expanded in any source available here, so this note does not assert what the abbreviation stands for or what the component does at runtime. What can be established is its identity and its reach. It is signed by a Samsung OEM key that also signs the Android framework, it requests com.samsung.sec.android.application.csc, com.sec.permission.preconfig, a READ_OMC_CONFIG permission named for the package above, and Samsung's carrier update permission, which places it squarely in the CSC and OMC customisation layer. Its declared permission set is the reason to leave it alone. This site records the permissions a package declares rather than what a given device has actually granted, and alongside those customisation permissions this one declares MASTER_CLEAR, DELETE_PACKAGES, CLEAR_APP_USER_DATA, REBOOT, INTERACT_ACROSS_USERS and WRITE_EMBEDDED_SUBSCRIPTIONS. Declaring a permission is not the same as being granted it, still less exercising it, and nothing here establishes that the package uses any of them. What the list does show is that it was built expecting to operate, where granted, in the factory-reset, package-removal and eSIM subscription paths, which is not the profile of an isolated add-on. Version note, and it is a genuine one. Samsung's own Common Criteria application list for the Galaxy S20 (the R-era G981U list) records this package under the label "CIDManager" at version 11, whereas current devices on this site report it as "Configuration update" at versions 1.0.57 to 6.0.09. A label moving from an internal component name to a user-readable configuration term, alongside a version series that restarts lower than the one Samsung listed, suggests the package was reworked at some point between those two points. The release at which that happened, and what changed with it, could not be sourced, and is flagged here rather than hidden behind an evergreen description. Samsung's Oreo-era Note9 list does not contain the package at all. On this site it is observed from API 31 through API 37, targeting API 32 to 37, and only on Samsung hardware. For Android Enterprise, EMM and kiosk use there is no documented role in enrolment or policy, and nothing a user interacts with. Given undocumented behaviour, undocumented dependents and declared permissions that, where granted, reach the reset and eSIM paths, it is not a trimming candidate. If a specific Samsung preinstalled app must be removed from a build, Samsung documents blocking it by package name through Knox Manage's application policies, and that should be tested on one device before it reaches a fleet.

• Galaxy S20 5G (G981U) application list - Samsung Knox CC Mode documentation →
• Galaxy Note9 (N960N) application list - Samsung Knox CC Mode documentation →
• Campaigns and firmware (CSC as an essential component of Samsung firmware) - Knox E-FOTA - Samsung Knox Documentation →
• Enable or disable a specific system app - Knox Manage - Samsung Knox Documentation →
• Package provenance for com.samsung.android.cidmanager - 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 21 permissions: 1 runtime (user-granted), 8 signature or system-level, 1 install-time and 11 vendor or uncatalogued.
• APK size ranges from 4.0 MB to 15.5 MB across the reporting device profiles, so the build differs substantially between them.
• Reported as an updated system app on 1 of 22 profiles - a newer build is installed over the one in the system image there.