com.samsung.android.app.telephonyui.esimclient Copy

A Samsung system component labelled "EsimClient", part of Samsung's telephonyui family and signed by the same Samsung key that signs the framework. It has no launcher entry and is not user-facing in any observation on this site, which fits a component launched from Settings rather than from the app tray. Its permissions describe a front end for adding an eSIM rather than the eSIM engine itself. Its recorded list includes CAMERA, which fits the QR-code scanning journey Samsung documents, alongside READ_MEDIA_IMAGES and READ_MEDIA_VISUAL_USER_SELECTED, which would suit selecting a saved QR image instead; Samsung documents no such image-picking route, so that reading of the media permissions is our inference. The list also includes ACCESS_FINE_LOCATION and ACCESS_COARSE_LOCATION; INTERNET with CONNECTIVITY_USE_RESTRICTED_NETWORKS and READ_PRIVILEGED_PHONE_STATE; and two cross-app permissions that place it in the same suite as the service above, com.samsung.android.simagent.permission.ACCESS_SIM_AGENT_INTERFACE and com.samsung.oda.permission.ODA_HQM_ACTION. Notably its recorded list does not include the LPA access permission that com.samsung.oda.service holds, so reading it as a client onto Samsung's eSIM machinery rather than the Local Profile Assistant itself is a reasonable inference, though Samsung does not document the split. Samsung's own support pages describe the three ways a profile is added, Simple Setup, a scanned QR code, or a manually entered activation code, and state that "eSIM service may vary depending on the country and carrier". Version note: Samsung's Common Criteria mode application list for the Galaxy Note20 Ultra 5G on Android 10 records EsimClient at version 11.5.05.4, so this package long predates the current builds. This site records it at API 33 to 37 (Android 13 to 17) at versions 15.1.00.634 to 18.0.00.106. No change in its role across Android releases could be sourced. The relevant boundary for managed fleets is again Android 15, from which the Android Management API can provision and manage eSIM profiles remotely, through ADD_ESIM and REMOVE_ESIM device commands. Whether that managed path is wholly independent of this Samsung package could not be sourced. For Android Enterprise, EMM and kiosk use, disabling it would be expected to remove the user-facing route to add or change an eSIM on the device while leaving the underlying profile machinery in place, which is a plausible hardening step on company-owned cellular fleets where profiles are managed centrally. Whether EMM-driven eSIM commands remain unaffected on a Samsung device with this package disabled could not be sourced, so test on one device before rolling it out. Note also that your EMM may already offer a supported control for this: from Android 15 the Android Management API exposes a userInitiatedAddEsimSettings field under deviceRadioState that governs whether users may add their own eSIM profiles on company-owned devices, which is a policy lever rather than a disabled package.

• Galaxy eSIM and supported network carriers - Samsung Singapore →
• Galaxy Note20 Ultra 5G (SM-N986B, Android 10) Common Criteria mode application list - Samsung Knox Documentation →
• Implement eSIM - Android Open Source Project →
• Is it possible to manage eSIM? - Android Enterprise FAQ →
• enterprises.devices.issueCommand (ADD_ESIM, REMOVE_ESIM) - Android Management API →
• Package provenance for com.samsung.android.app.telephonyui.esimclient - 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 18 device profiles. 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 11 permissions: 5 runtime (user-granted), 2 signature or system-level, 1 install-time and 3 vendor or uncatalogued.
• APK size ranges from 6.5 MB to 15.4 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.