com.samsung.android.accessibility.talkback Copy

Samsung's build of TalkBack, the Android screen reader, shipped under a Samsung package name on Galaxy devices. In our sample it is signed by the same Samsung key that signs the device framework, so this is Samsung's own copy rather than the Google-signed TalkBack (com.google.android.marvin.talkback) documented separately on this site. TalkBack speaks what is on screen and changes how touch input works, so a blind or low-vision user can navigate by gesture; it is the accessibility service behind the screen reader toggle in Settings. Version note: Samsung previously shipped its own screen reader called Voice Assistant. Samsung's support documentation states that on devices running One UI 3.1 or later the feature is called TalkBack, while on earlier software versions it is called Voice Assistant, with the functionality otherwise consistent. Samsung's newsroom announcement puts the One UI 3 generation on Android 11. What we could not source is whether older Voice Assistant devices carried a different package name to this one, so treat the naming change as documented and the package-level history as unconfirmed. For Android Enterprise, EMM and kiosk use, treat this as an accessibility dependency rather than bloat. It has no launcher icon, but it is what a visually impaired user relies on, and removing it on a shared or kiosk device can leave that device unusable for them. Separately, management policy can restrict which accessibility services may run: the Android Management API exposes permittedAccessibilityServices, where an unset field allows any accessibility service, a populated list allows only those services plus the system's built-in accessibility service, and an empty list allows only the system built-in ones. Whether a given OEM screen reader counts as a system built-in on a specific device is worth testing rather than assuming. If a screen reader has stopped responding, check policy before concluding the package is missing. Disabling it is possible but should be a deliberate decision, not a default debloat step.

• How to use TalkBack on a Galaxy phone - Samsung Support →
• Get started on Android with TalkBack - Google Accessibility Help →
• Samsung One UI 3 Takes User Experience to New Heights with Android 11 - Samsung Global Newsroom →
• REST Resource: enterprises.policies (permittedAccessibilityServices) - Android Management API →
• Package provenance for com.samsung.android.accessibility.talkback - 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 81 permissions: 8 runtime (user-granted), 4 signature or system-level, 10 install-time and 59 vendor or uncatalogued.
• APK size ranges from 1.9 MB to 102.1 MB across the reporting device profiles, so the build differs substantially between them.
• Reported as an updated system app on 7 of 22 profiles - a newer build is installed over the one in the system image there.