Last updated on 28 October 2025
Update: Samsung has just released a TalkBack update on the Galaxy Store with Version number 16.0.01.0, which includes a fix for the issue. After installing the update on one device, we can confirm that Explore by Touch is now working normally when the Hide Screen feature is active.
Samsung’s One UI 8 update has started rolling out to the S25 Series. This Update includes Samsung’s version of TalkBack 16.0. This version of TalkBack contains a serious bug for those who use the “Hide Screen” feature. Note that Google TalkBack is not affected
The Hide Screen Bug in Samsung TalkBack 16.0
With the new version of TalkBack, when the screen is hidden, you are not able to use explore by touch at all. It is also not possible to use any pass-through gestures. This includes both the pass-through system gesture (which is to double tap and hold with four fingers by default), as well as any two-finger gesture you would use when scrolling a screen or similar. All one-finger swiping gestures and other multi-finger gestures still work, as well as double tapping to activate items.
Not only does this make TalkBack pretty much unusable for those that keep their screen hidden, but this introduces a very problematic situation when installing the update. If you have your screen hidden when the update installs, it will remain hidden when the phone boots back up. This will cause you to not be able to get back into your phone since a pass through gesture (swiping up with 2 fingers) is required the first time you unlock your phone after a reboot.
Workaround
The workaround here is to show (or unhide) your screen. You can do this from the TalkBack menu (if you have not removed the option) or by performing the assigned gesture (if you have customized it). If you can’t show the screen using either of these methods, you will have to turn off TalkBack with an accessibility shortcut (assuming you have assigned one to TalkBack), swipe up with one finger, and use the accessibility shortcut to turn TalkBack on again. From here, you should be able to swipe and double tap to input your PIN. However, if you use a pattern, you will have to put it in before you turn TalkBack on again.
Once you have gotten into your phone, you will want to show (or unhide) your screen if you haven’t already, and keep it this way until Samsung provides a fix for this.
This is a total lack of care or consideration to visually impaired people that use TalkBack. I won’t be upgrading to the S25 series. And will be urging others also not to upgrade.
This issue happens sometimes on my Galaxy S23 with TalkBack 15.1 and One UI 7.0. Do you know if the bug where TalkBack doesn’t automatically recognize unlabeled objects or buttons is fixed in TalkBack 16?
When I sideloaded Google’s Talkback 16 on my Galaxy S23+, I saw no change. Commentary/Jieshuo is still the best for proper app labeling support, sad to say. Especially since Jieshuo’s labels can be shared with the world via the Jieshuo Cloud after signing up for a free account in their usr center.
I see nothing has changed in Android Google does no testing. This despite the fact they and Samsung are supposed to be partnered. Just switch to iOS.
This has nothing to do with Google. If you use Google’s own version of TalkBack, installing it through on ADB on your Samsung device before you upgrade, this issue won’t occur. This is a Samsung TalkBack–only issue, and this exactly proves why Samsung should use Google’s version of TalkBack, and not their own.
I also do hope you realize that you’re telling an Android forum to switch to iOS, right? That’s like telling an Apple forum to switch to Android..
this talkback issue is also why i tell people to not get a samsung phone. Avoid them at all costs. get a google pixle or something that uses google’s own version of talkback. or lern how to use ADB. even useing a Huawei phone sounds like a better idea then getting a samsung phone at the moment.
there, i said it.
look if you dont have any thing nice to say that isn’t constructive criticism then dont even say anything. it isn’t helpful and your comment isn’t going to fix the problom. telling android users that they should be better off swiching to ios is just not right, especially considering the fact that you’re saying this in an android forum. you only come on here to just put in pointless criticisms of android, that are only a few words long. they do nothing to fix any of the issues you call out. if you don’t like the fact that android doesn’t fix any issues, specifically samsung, pick up an android, sign up to the beta program, and submit feedback. you don’t like it when people criticise iOS, and voice overs issues, but yet you are completely fine with an operating system that you haven’t used in five years, mabey even more.
android has came along long waigh from what it was for blind people. just be thankful that google doesn’t add some ios voice over featchers, or u’d be cooked.
and yes whilst i criticised android on applevis back in late 2023 before my account got unlawfully banned i at least didn’t make it 6 words long. i put out why i had issues with android. Specifically Samsung, and other stuff. my next phone will be an android, not a samsung, unless i can flash a custom rom on it.
android has made a lot more progress for blind people compareed to ios over the last few years.
so, denus, if you dont have anything nice to say about an os that you don’t even use anymore., don’t even talk.
also, btw, telling android users they should swich to ios is also just a sad presadent of ignorance from your part. i see you have enuf munny to get an ipHone 16-e. not every android user has the munny to go and get an ipHone, even the cheepest one. realise peoples economic situation first before you go and say stuff like that.
i can’t waight to test android and make talkback better.
Hello, IOS!
Selection mode anyone?
Granular editing mode anyone?
TTS speech rate and volume boost anyone?
Multiple text to speech voices and TTS channels anyone?
So stop advertizing your featureless OS. VOver is feature dead in 2025. Plugins, custom OCRs, custom everything anyone on IOS?
The title is a bit misleading and worrysome for those who see it in passing. It should say for *some* Talkback users. Not all of us hide the screen, and some of us use physical keyboards, so this wouldn’t affect those of us in that group anyway.
Hello guys!
My name is Ciprian, the person behind Samsung accessibility framework reviews.
This thing that’s happening to Samsung devices is Google’s talkback.
You may ask why?
Let’s read together:
“windowName:Dim Layer for – Display 0 name=”Built-in Screen”#2185 isn’t optimized for the latest version of Android. Screen touches may be delayed or not recognized.”
So this shows only one thing:
Google gave to Samsung a very, very early version of TalkBack16 that was released before Android16 itself reached platform stability so this is why: Something was modified in the frameworks after this TalkBack version of TalkBack was released, and Google didn’t give Samsung a later version.
Hello guys. I’ve received news that an update for the TalkBack screen reader has arrived on the Galaxy Store and that the issue has already been fixed. Is that true?
it seams as if this is a google talkback issue as this is happening on my moto g04s, running google talkback and android 14