com.samsung.android.app.updatecenter Copy

A Samsung system component that devices here report as "App update", and which localises properly with the device ("Aggiornamento app", "Actualización de aplicaciones", "Mise à jour des applications", "App-update", "Aktualizacja aplikacji"). It nonetheless has no launcher entry in any observation on this site, so it is a background component with user-readable strings rather than an app a user opens. It is preinstalled, Samsung-signed with certificates this site also records as signing the framework, and no observation is marked Play-eligible, so on the devices seen here it arrives and updates with firmware. Samsung publishes no package-level documentation for it, so the description below rests on its manifest. The permission that settles what it is for is android.permission.INSTALL_PACKAGE_UPDATES, which AOSP defines in the framework manifest at protection level signature|privileged and documents as allowing "an application to install updates", described there as a limited version of INSTALL_PACKAGES. Alongside it the package requests QUERY_ALL_PACKAGES, INTERNET, ACCESS_NETWORK_STATE, ACCESS_WIFI_STATE, POST_NOTIFICATIONS, RECEIVE_BOOT_COMPLETED and READ_PRIVILEGED_PHONE_STATE. That combination, a component that can enumerate every installed package, reach the network, install package updates and raise a notification about it, is consistent with the label: a Samsung-side updater for applications already on the device. Which applications it actually updates, where it fetches them from and on what schedule are not documented by Samsung and are not claimed here. Two of its remaining permissions place it in Samsung's own layer rather than the platform one. It requests com.samsung.android.sdm.config.provider.READ_OMC_CONFIG, named for the Samsung customisation component documented separately on this site, and com.samsung.android.permission.SEM_APP_RESTRICTION. Take the first as a hint that what it offers can vary by carrier and regional customisation, which is inference from permission naming and nothing more. Version note, and a clear one. This package does not appear in any of the Samsung Common Criteria mode application lists checked here, which inventory the software preinstalled on a certified model: it is absent from the Oreo lists for the Galaxy Note9 and Galaxy S8+, from the Android 10 list for the Galaxy S20+ 5G, and from the Android 11 lists for the Galaxy S20 5G and Galaxy S21+ 5G. On this site the earliest observation is at API 31, and the sample runs from API 31 to 37 with versions 1.1.11 to 9.0.03 and target SDKs 31 to 37. Read together that points to the component arriving around Android 12 rather than being a long-standing part of the Samsung image. The exact release it was introduced in, and what it replaced if anything, could not be sourced, and is flagged here rather than smoothed over. For Android Enterprise, EMM and kiosk use, treat it as an app delivery path to be aware of rather than something to strip. A fleet that has deliberately pinned application versions has a legitimate interest in a system component that can install package updates on its own, but removing the updater is the wrong lever: Samsung documents an application update policy in Knox Service Plugin that blocks updates for specified apps, and that enforces a decision where a package removal only obstructs one route to it. Pulling the other way, updates to preinstalled Samsung applications can carry security fixes, so a fleet that disables this component should be confident those apps are being maintained by some other route. Where a specific Samsung preinstalled app has to be suppressed, Samsung documents blocking it by package name through Knox Manage; test on a single device first.

• INSTALL_PACKAGE_UPDATES permission definition - core/res/AndroidManifest.xml, Android (frameworks/base) source →
• How to block app updates with Knox Service Plugin - Knox Manage - Samsung Knox Documentation →
• Enable or disable a specific system app - Knox Manage - Samsung Knox Documentation →
• Galaxy S21+ 5G (SM-G996B, Android 11) Common Criteria mode application list - Samsung Knox Documentation →
• Galaxy S20 5G (SM-G981U, Android 11) Common Criteria mode application list - Samsung Knox Documentation →
• Galaxy S20+ 5G (SM-G986U1, Android 10) Common Criteria mode application list - Samsung Knox Documentation →
• Galaxy Note9 (SM-N960N, Android 8) Common Criteria mode application list - Samsung Knox Documentation →
• Galaxy S8+ LTE (SM-G955U1, Android 8) Common Criteria mode application list - Samsung Knox Documentation →
• Package provenance for com.samsung.android.app.updatecenter - 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 12 permissions: 1 runtime (user-granted), 2 signature or system-level, 5 install-time and 4 vendor or uncatalogued.
• APK size ranges from 0.5 MB to 5.7 MB across the reporting device profiles, so the build differs substantially between them.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.