com.samsung.android.smartface Copy

A second Samsung service in the same naming family as com.samsung.faceservice above, and a different job. Every observation on this site reports it under the untranslated label "SmartFaceService" in every locale recorded, it is preinstalled and Samsung-signed with certificates that also sign the framework, it has no launcher entry, and no observation is marked Play-eligible, so it too ships with firmware. Samsung publishes no package-level documentation for it. Its manifest is unusually small and that is the most informative thing about it. It declares six permissions: CAMERA, GET_TASKS, INTERACT_ACROSS_USERS_FULL, OBSERVE_SENSOR_PRIVACY, STATUS_BAR and WAKE_LOCK. OBSERVE_SENSOR_PRIVACY is a hidden platform permission that AOSP documents as allowing "sensor privacy changes to be observed", which is what a component watching the camera privacy toggle would need. Taken together, live camera access plus foreground-task awareness plus status bar and wake lock access is the profile of a service that watches the front camera and reacts by changing what the screen does. That is a reading of the permission set, not a sourced description: which user-facing Galaxy features depend on this service is not documented by Samsung and is deliberately not named here. Note also what is absent. Like com.samsung.faceservice it requests no biometric permission and no media permission in anything this site records, which is a reason to doubt that it is either the face unlock component or part of the gallery face indexing path, rather than proof that it is not. Version note, and it is an unusual one. The version name is frozen. Samsung's Common Criteria mode application lists record "SmartFaceService" at version 1 or 1.0 on the Galaxy S8+ and Galaxy Note9 (Oreo), the Galaxy S20+ 5G (Android 10), and the Galaxy S20 5G and Galaxy S21+ 5G (Android 11), and every observation in this site's sample also reports 1.0, across API 28 to 37. The version string therefore carries no information about whether the component has changed. Two things suggest it is still maintained rather than abandoned: the target SDK moves from 30 to 36 across the sample, and package size ranges from roughly 1.4 MB to 2.3 MB. Whether its role changed in any recent Android release could not be sourced, and is flagged here rather than described as evergreen. For Android Enterprise, EMM and kiosk use it has no documented role in enrolment or policy. The point worth carrying into a deployment review is the CAMERA permission: this is a preinstalled system service with live camera access, which matters on secure sites and camera-restricted kiosks. That is a reason to know it exists, not a reason to remove it. Camera use is controlled through device policy, which exposes a control for disabling the camera outright, and that enforces something a package removal does not. Given platform-level signing and undocumented dependents, treat removal as a per-device test rather than a fleet-wide default, and where a Samsung preinstalled app must be suppressed, Samsung documents blocking it by package name through Knox Manage.

• 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 →
• OBSERVE_SENSOR_PRIVACY permission definition - core/res/AndroidManifest.xml, Android (frameworks/base) source →
• DevicePolicyManager.setCameraDisabled - Android developer reference →
• Enable or disable a specific system app - Knox Manage - Samsung Knox Documentation →
• Package provenance for com.samsung.android.smartface - 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 6 permissions: 1 runtime (user-granted), 3 signature or system-level and 2 install-time. The signature/system share marks it as a privileged component, not an ordinary app.
• Never reported as user-facing, so it runs as a background or system component rather than an app the user opens.