Thank you so much all of you to help me understand different talkbacks. Nirmal
On Thu, Jun 26, 2025 at 1:32 PM Ejaz Ahmed Shah <[email protected]> wrote: > From > > Accessible Android - <https://accessibleandroid.com/> > > A Beginner’s Guide to Samsung TalkBack and How It Differs from Google’s > Version > > Published 21 June 2025 by Kareen Kiwan > > > Google TalkBack is the default built-in screen reader for Android. > However, starting with One UI 3.0 based on Android 11, Samsung phones and > tablets come with Samsung’s own version of TalkBack set as the default > screen reader. > > Choosing between the two screen readers on a Samsung device is not a > straightforward process. It involves some advanced steps, such as using ADB > to enable Google’s version of TalkBack and uninstall Samsung’s version. > > This article aims to highlight what’s available and what’s not in > Samsung’s version of TalkBack, for beginners who are currently using a > Samsung phone or tablet, planning to do so, or simply looking to clear up > the confusion surrounding this topic, which is often discussed among blind > Android users. > > It’s important to note that this article is purely informative. It is > based on factual details and user observations, and is not intended to > express opinions about the separation of TalkBack versions. That topic has > already been addressed in a previous opinion piece > <https://accessibleandroid.com/opinion-why-samsung-google-talkback-separation-is-nothing-but-a-headache/> > . > > Table of Contents [hide > <https://accessibleandroid.com/a-beginners-guide-to-samsung-talkback-and-how-it-differs-from-googles-version/#> > ] > > - What is Samsung TalkBack > > <https://accessibleandroid.com/a-beginners-guide-to-samsung-talkback-and-how-it-differs-from-googles-version/#What_is_Samsung_TalkBack> > - Installing and Updating Samsung TalkBack > > <https://accessibleandroid.com/a-beginners-guide-to-samsung-talkback-and-how-it-differs-from-googles-version/#Installing_and_Updating_Samsung_TalkBack> > - Core Functions, Gestures, and Settings > > <https://accessibleandroid.com/a-beginners-guide-to-samsung-talkback-and-how-it-differs-from-googles-version/#Core_Functions_Gestures_and_Settings> > - No Gemini Online Detailed Image Descriptions > > <https://accessibleandroid.com/a-beginners-guide-to-samsung-talkback-and-how-it-differs-from-googles-version/#No_Gemini_Online_Detailed_Image_Descriptions> > - No Option to Use the Proximity Sensor to Interrupt Speech > > <https://accessibleandroid.com/a-beginners-guide-to-samsung-talkback-and-how-it-differs-from-googles-version/#No_Option_to_Use_the_Proximity_Sensor_to_Interrupt_Speech> > - Probably Better Integration with Samsung Services > > <https://accessibleandroid.com/a-beginners-guide-to-samsung-talkback-and-how-it-differs-from-googles-version/#Probably_Better_Integration_with_Samsung_Services> > - Multi-Finger Gestures Support > > <https://accessibleandroid.com/a-beginners-guide-to-samsung-talkback-and-how-it-differs-from-googles-version/#Multi-Finger_Gestures_Support> > - Should You Install Google TalkBack on Your Samsung Device? > > <https://accessibleandroid.com/a-beginners-guide-to-samsung-talkback-and-how-it-differs-from-googles-version/#Should_You_Install_Google_TalkBack_on_Your_Samsung_Device> > - Conclusion > > <https://accessibleandroid.com/a-beginners-guide-to-samsung-talkback-and-how-it-differs-from-googles-version/#Conclusion> > > What is Samsung TalkBack > > Samsung TalkBack is the TalkBack screen reader found on Samsung phones and > tablets running Android, starting with One UI 3.0 or Android 11. The screen > reader itself is not developed by Samsung; rather, it is Google’s version > with some changes. The core of the screen reader remains the same as the > TalkBack found on other Android devices. > According to Samsung, this version is optimized to work more efficiently > and be more compatible with Samsung devices. > > Samsung TalkBack is the default screen reader on Samsung phones and > tablets, and it can be installed from the Galaxy Store > <https://galaxystore.samsung.com/prepost/000005296612>. In contrast, > Google TalkBack—the default screen reader on other OEM devices—is available > on the Play Store as part of the Android Accessibility Suite > <https://play.google.com/store/apps/details?id=com.google.android.marvin.talkback&hl=en> > app. > Installing and Updating Samsung TalkBack > > There is no need to take any steps to install Samsung TalkBack, as it is > already built in and can be enabled during phone setup: either by pressing > Power + Volume Up or by holding both volume keys. The traditional method of > tapping and holding two fingers on the screen may also work. If Samsung > TalkBack wasn’t enabled during setup, it can be activated later from the > Accessibility settings, where a shortcut can also be assigned to toggle it > quickly. > > Although TalkBack is available in the Galaxy Store, major version upgrades > are delivered through One UI updates. This means that to receive new > versions of Samsung TalkBack, the device must first get the corresponding > One UI update. As a result, the TalkBack version on a phone running One UI > 5 differs from the version found on One UI 6 or 7. > > This update mechanism differs from how Google TalkBack is updated. In that > case, updates are delivered directly through the Play Store to all > supported Android versions, though some features may depend on the Android > version. For example, HID Braille support over Bluetooth is only available > on Android 15 and later. > Core Functions, Gestures, and Settings > > As mentioned earlier, Samsung TalkBack is based on Google’s version, which > means that operating the device using the screen reader is the same. It > uses the same default gestures and offers a similar set of features. > However, Samsung TalkBack omits certain options and functions. > Additionally, because different One UI versions include different TalkBack > builds, some features may not be available on older versions of One UI. > No Gemini Online Detailed Image Descriptions > > The most notable omission in Samsung TalkBack is the absence of Gemini-based > detailed online image descriptions > <https://accessibleandroid.com/impressions-of-google-talkback-15-0s-detailed-gemini-image-description-a-feature-with-great-potential/>. > This feature, introduced in Google TalkBack 15.0, allows Gemini to describe > the currently focused element. It was further expanded in TalkBack 16.0 > <https://accessibleandroid.com/whats-new-in-talkback-16-0/> to include > entire screen descriptions and the ability to ask follow-up questions. > > This feature is currently not available in Samsung TalkBack, even for > users running the One UI 8 beta 2. The only form of image descriptions > appears on the Galaxy S25 series, where offline descriptions are powered by > the on-device Gemini Nano. However, this implementation does not support > follow-up questions or full screen descriptions. > > It’s important to note that the item labeled “Describe image” in Samsung > TalkBack only extracts text from images and icon labels using offline text > and icon recognition. When neither is detected, a message is displayed to > inform the user that the image cannot be described. This is the case on > devices other than the S25 series, as on S25 phones, this item performs > actual image descriptions using the offline on-device model. > > As a result of not having image description support, Samsung TalkBack also > lacks any related settings, including the older basic offline description > features that were available before the introduction of Gemini descriptions. > > While Samsung may add Gemini image descriptions in the future, it is > likely that the feature will only become available starting from a specific > One UI version. Older versions are unlikely to receive it retroactively. > No Option to Use the Proximity Sensor to Interrupt Speech > > Google TalkBack includes an option to interrupt speech by placing the hand > close to the proximity sensor. Samsung TalkBack does not offer this > feature, likely because Samsung devices use virtual proximity sensing > rather than a dedicated hardware sensor. > Probably Better Integration with Samsung Services > > According to Samsung sources, the separation of Google and Samsung > TalkBack allows Samsung to further enhance the TalkBack experience on its > devices. This could mean better compatibility with Samsung-specific > features. > > While practical differences are usually minor, there have been cases where > Samsung TalkBack performed better on certain devices or with specific > features. For example, users who used Google TalkBack on Samsung devices > sometimes experienced issues with TalkBack speech interrupting Bixby, > whereas this problem did not occur when using Samsung TalkBack. > > Another observed difference is in One UI 7, where only Samsung TalkBack > can utilize Samsung’s TTS (text-to-speech) engine. > > A more responsive experience might also be noticed, especially since > Samsung TalkBack is a system app, whereas Google TalkBack, when installed > on Samsung devices, is treated as a user app. > > An interesting observation involves the cover screen of Samsung Flip > phones. Samsung improved its version of TalkBack by enabling the display of > overlay screens—such as the TalkBack menu—on the cover screen, a capability > that wasn’t present in Google’s version. Eventually, the same improvement > was added to Google TalkBack in later versions. > > However, the expected flawless integration is not always present. One > prominent example is the Proofread TalkBack feature, which shows > misspellings and grammar errors and offers suggestions to fix them. This > feature doesn’t work if Gboard is not set as the default spell checking > service, even on Samsung devices. The expected behavior would be for the > feature to be compatible with the default Samsung keyboard’s spell checking > service, especially since on some Samsung devices, Gboard is not > preinstalled. > Multi-Finger Gestures Support > > Both TalkBack versions support multi-finger gestures. However, Samsung > TalkBack enables this support starting from Android 11, while Google > TalkBack requires Android 12 or higher, except on a few Pixel devices where > support is available from Android 11. > Should You Install Google TalkBack on Your Samsung Device? > > It’s difficult to give a straightforward answer to this question. Neither > Google nor Samsung recommends using Google TalkBack instead of Samsung’s > version on Samsung phones or tablets. > > Additionally, running Google TalkBack on a Samsung device is not as simple > as installing an app from the Play Store and enabling the accessibility > service. Google TalkBack does not appear among the accessibility services > by default on Samsung devices, nor can it be assigned to an accessibility > shortcut. > > If you encounter issues while running Google TalkBack on a Samsung device, > reporting them to either Google or Samsung can be complicated, since you > are using an unsupported configuration. > > Using Google TalkBack on Samsung devices requires advanced steps such as ADB > (Android Debug Bridge) > <https://developer.android.com/studio/command-line/adb> commands. Because > conflicts have been observed when both versions coexist on the same device, > it is typically recommended to uninstall Samsung TalkBack if you intend to > use Google TalkBack. Since TalkBack is a system app, uninstalling Samsung > TalkBack also requires ADB, as it cannot be removed through normal means. > > Despite the risks, uninstalling Samsung TalkBack and replacing it with > Google TalkBack is common among Samsung users. John Dyer’s guide with > simple step-by-step instructions > <https://accessibleandroid.com/how-to-uninstall-samsung-talkback-and-install-googles-version-in-simple-steps/> > is particularly popular. However, it is important to understand and > assess the risks involved, as compatibility issues or crashes might occur > at any time when using Google TalkBack on a Samsung device. > Conclusion > > If you own a Samsung phone or tablet running One UI 3.0 or higher, you > should understandthat the TalkBack screen reader on your device is > Samsung’s TalkBack. The version and, consequently, the available features > depend on the One UI version your device is running, with updates delivered > mainly through One UI system updates rather than the Galaxy Store. Version > numbers may not match those of Google TalkBack, as the two are not always > synchronized. > > Samsung TalkBack remains similar to Google TalkBack in many respects, and > you might even encounter the same bugs that affect users on other devices. > > If you are planning to get a Samsung device, it’s important to understand > how TalkBack currently works and not rely on assumptions about future > changes. The separation between Samsung TalkBack and Google TalkBack should > be considered a reality, despite rumors that it might end. This article > will be updated to reflect any major changes if they occur. > > On 23/06/2025 07:36 pm, Nirmal Verma wrote: > > Dear Learned friends > > As the subject line says I want to know what is the difference between > samsung talkback and the talkback we download from play store. Does it make > any difference to how we connect to braille devices? what challenges do you > face in using samsung talkback. > > -- > Nirmal Verma > > -- > Disclaimer: > 1. Contents of the mails, factual, or otherwise, reflect the thinking of > the person sending the mail and AI in no way relates itself to its veracity; > > 2. AI cannot be held liable for any commission/omission based on the mails > sent through this mailing list.. > > > Search for old postings at: > http://www.mail-archive.com/[email protected]/ > --- > You received this message because you are subscribed to the Google Groups > "AccessIndia" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/a/accessindia.org.in/d/msgid/accessindia/CAKX4VoVtfbvPedRGCKkgQnggxPhoJg%2BPqekBta%2B5rAfGM55TUQ%40mail.gmail.com > <https://groups.google.com/a/accessindia.org.in/d/msgid/accessindia/CAKX4VoVtfbvPedRGCKkgQnggxPhoJg%2BPqekBta%2B5rAfGM55TUQ%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > -- > Disclaimer: > 1. Contents of the mails, factual, or otherwise, reflect the thinking of > the person sending the mail and AI in no way relates itself to its veracity; > > 2. AI cannot be held liable for any commission/omission based on the mails > sent through this mailing list.. > > > Search for old postings at: > http://www.mail-archive.com/[email protected]/ > --- > You received this message because you are subscribed to the Google Groups > "AccessIndia" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion visit > https://groups.google.com/a/accessindia.org.in/d/msgid/accessindia/VI0P189MB282103413B525E6176307CC1DA7AA%40VI0P189MB2821.EURP189.PROD.OUTLOOK.COM > <https://groups.google.com/a/accessindia.org.in/d/msgid/accessindia/VI0P189MB282103413B525E6176307CC1DA7AA%40VI0P189MB2821.EURP189.PROD.OUTLOOK.COM?utm_medium=email&utm_source=footer> > . > -- Nirmal Verma -- Disclaimer: 1. Contents of the mails, factual, or otherwise, reflect the thinking of the person sending the mail and AI in no way relates itself to its veracity; 2. AI cannot be held liable for any commission/omission based on the mails sent through this mailing list.. Search for old postings at: http://www.mail-archive.com/[email protected]/ --- You received this message because you are subscribed to the Google Groups "AccessIndia" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/accessindia.org.in/d/msgid/accessindia/CAKX4VoUinV%3Dq4PpWXQYw6j5q_Acv4kWhWFZ5eGHpVHAV31KqWg%40mail.gmail.com.
