com.samsung.oda.service Copy

A Samsung system service labelled "SamsungOdaService" in every locale this site has recorded it in. It is signed by a Samsung OEM key that also signs the framework package, has no launcher entry, and is not user-facing in any observation here. Samsung publishes no documentation for it, and no document we read expands the letters "ODA", so we do not assert an expansion. What it does is readable from the permissions this site records against it, noting that the site records the permissions a package requests rather than which package declares them. The list includes com.samsung.euicc.LPA_SERVICE_ACCESS, com.samsung.TS43_AUTH_SERVICE_ACCESS, com.samsung.android.simagent.permission.ACCESS_SIM_AGENT_INTERFACE and com.samsung.oda.ODA_SERVICE_ACCESS in its own namespace. An LPA, or Local Profile Assistant, is the eSIM component that talks to a carrier's SM-DP+ server and to the eUICC in order to download and enable subscription profiles. TS.43 is the GSMA Service Entitlement Configuration specification, which AOSP itself implements in a platform library described as exporting "the APIs for querying the service status, based on GSMA TS.43 spec", and which carriers use to authorise services such as eSIM activation on a second device. Alongside those it holds INTERNET, CONNECTIVITY_USE_RESTRICTED_NETWORKS, READ_PRIVILEGED_PHONE_STATE, RECEIVE_BOOT_COMPLETED, POST_NOTIFICATIONS and com.google.android.c2dm.permission.RECEIVE. Taken together that is a background client that contacts a carrier entitlement service and drives eSIM profile download, which fits the automatic activation Samsung documents for Galaxy devices, where "the network carrier can send your new eSIM to your Samsung Galaxy device without the need for a complicated setup process". Nothing in the sources cited here names this package as the component behind that flow, so treat that tie as our reading of its permissions rather than a Samsung statement. Version note: Samsung's own Common Criteria mode application list for the Galaxy Note20 Ultra 5G on Android 10 records SamsungOdaService at version 1.5, so the package has been present since at least that release. This site records it on Samsung devices at API 33 to 37 (Android 13 to 17) at versions 3.1.00.57 to 6.0.00.25. No change in its role across Android releases could be sourced. The enterprise dimension did change, but on the Android side rather than Samsung's: from Android 15 the Android Management API supports remote provisioning and management of eSIM profiles on managed devices, which is a separate, platform path from the carrier-driven activation this service serves. For Android Enterprise, EMM and kiosk use it has no enrolment or policy role, but it is connectivity plumbing on any fleet that uses eSIM. Disabling it would be expected to break carrier-driven eSIM activation and any entitlement check that depends on it, which on a cellular fleet can leave a device unable to obtain a subscription. Its inferred eSIM role may be unnecessary on physical-SIM or Wi-Fi-only fleets, but other dependencies are unverified and there is nothing to gain from removing it, so leave it in place unless you have tested the specific handset and carrier combination without it.

• Galaxy eSIM and supported network carriers - Samsung Singapore →
• Service entitlement library (GSMA TS.43) - Android source →
• Implement eSIM - Android Open Source Project →
• Galaxy Note20 Ultra 5G (SM-N986B, Android 10) Common Criteria mode application list - Samsung Knox Documentation →
• Is it possible to manage eSIM? - Android Enterprise FAQ →
• enterprises.devices.issueCommand (ADD_ESIM, REMOVE_ESIM) - Android Management API →
• Package provenance for com.samsung.oda.service - 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 19 permissions: 1 runtime (user-granted), 3 signature or system-level, 5 install-time and 10 vendor or uncatalogued.
• APK size ranges from 2.9 MB to 11.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.