com.sec.bcservice Copy

A Samsung system component that ships without a friendly label: every observation on this site records it under its own package name, and so do Samsung's own published application lists. It has no launcher entry and this site records no user-facing observations of it. It is signed by Samsung keys that also sign the Android framework. The honest position first. Samsung publishes no documentation for this package, and the descriptions circulating for it, which typically assert that it handles call processing, appear only on APK catalogues and general Android blogs. That is not a basis for a functional claim, so this note does not repeat it and does not guess in its place. What can be established is provenance and permissions. Samsung's own Common Criteria application lists record com.sec.bcservice under the same package-name label on the Galaxy Note9 (the Oreo-era N960N list, version 2) and on the Galaxy S20 (the R-era G981U list, version 2.0). Every observation on this site also reports version 2.0, which is consistent with a component that is rarely changed. The permissions recorded here are worth reading before anyone concludes it is inert: READ_CONTACTS, READ_CALENDAR, a read permission on Samsung's memo provider, READ_PRIVILEGED_PHONE_STATE, REBOOT, RECEIVE_BOOT_COMPLETED and INTERACT_ACROSS_USERS, alongside two AT-command permissions (com.sec.android.phone.permission.AT_COMMAND and Samsung's SVC agent FENRIR_AT_COMMAND) and com.sec.factory.permission.KEYSTRING. That combination of personal-data reads with AT-command and factory keystring access is unusual for a package with no user interface, no source explains it, and it is recorded here rather than left out. Version note: the package holds one version across a target SDK range of API 31 to API 37, so it is long-standing rather than tied to one Android release, and no source establishes a change in its role across versions. For Android Enterprise, EMM and kiosk use, no source gives it a role in enrolment or policy enforcement. Where a preinstalled Samsung package needs to be turned off, Samsung documents doing that from the EMM console rather than by stripping packages. No disable rating is given below, because neither the package's function nor what depends on it can be sourced: treat it as something to test against on your own hardware rather than to trim on assumption.

• Galaxy Note9 (N960N) application list - Samsung Knox CC Mode documentation →
• Galaxy S20 5G (G981U) application list - Samsung Knox CC Mode documentation →
• Enable or disable a specific system app - Knox Manage - Samsung Knox Documentation →
• Package provenance for com.sec.bcservice - 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 10 permissions: 2 runtime (user-granted), 3 signature or system-level, 1 install-time and 4 vendor or uncatalogued.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.