Status Update
No update yet.
Comments
va...@gmail.com
vi...@google.com
What steps are needed to reproduce this issue? Frequency of occurrence?
Which Android build are you using? (e.g. AP4A.241205.013.A1)
Which device did you use to reproduce this issue?
Please explain the issue in detail.
Can you confirm if this issue is reproducible on a Pixel/Nexus device?
Are you reporting this as Developer or User?
Please provide a sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
Screen Record of the Issue
Please capture screen record or video of the issue using following steps:
adb shell screenrecord /sdcard/video.mp4
Subsequently use following command to pull the recorded file:
adb pull /sdcard/video.mp4
Attach the file to this issue.
Android bug report (to be captured after reproducing the issue)
For steps to capture a bug report, please refer:
Alternate method
Navigate to “Developer options”, ensure “USB debugging” is enabled, then enable “Bug report shortcut”. Capture bug report by holding the power button and selecting the “Take bug report” option.
Note: Please upload the bug report and screenshot to google drive and share the folder to android-bugreport@google.com, then share the link here.
r....@gmail.com
Answers inline:
What steps are needed to reproduce this issue? Frequency of occurrence?
This issue happens every time the following steps are performed:
- Enable TalkBack, either through the Settings > Accessibility > TalkBack, or by telling Assistant to "turn on TalkBack."
- In TalkBack settings, enable the TalkBack Braille Keyboard, and switch to it as your input method.
- In TalkBack settings, go to Verbosity, then "Keyboard Echo: Onscreen keyboards" and set it to Words.
- Go to the home screen.
- Open the All Apps panel.
- Find the Google Search box and double tap to open it.
- When the TalkBack Braille Keyboard opens, type "this is a test."
Which Android build are you using? (e.g. AP4A.241205.013.A1)
AP4A.250105.002
Which device did you use to reproduce this issue?
Pixel 8
Please explain the issue in detail.
The Google TalkBack screen reader allows me to use my phone since I am blind. The TalkBack Braille Keyboard allows me to type in Braille using my phone screen. I prefer to have each word I type spoken, rather than characters (letters) or both characters and words, allowing me to concentrate more on my thoughts rather than every letter I write, while still allowing me to hear mistyped words.
However, when TalkBack's "Keyboard Echo" setting is set to "words," in order to fit my preference, TalkBack does not speak entered words if they have a punctuation symbol after them, like a comma or period. This means that, in the steps above, TalkBack will read "this", "is, and "a", but not "test.". Ideally, TalkBack would read "this", "is", "a", "test period".
Can you confirm if this issue is reproducible on a Pixel/Nexus device?
Yes
Are you reporting this as Developer or User?
user
Please provide a sample project or apk to reproduce the issue. Also mention the steps to be followed for reproducing the issue with the given sample project or apk.
N/a, no sample apk or project needed.
Please capture screen record or video of the issue using following steps:
Attached.
Android bug report (to be captured after reproducing the issue)
Link:
vi...@google.com
It looks like you are raising this request as an Android user, rather than an Android Open Source Developer. Our Android Support team will be in contact with you shortly. In the meantime, here are helpful resources:
Description
If you think you've found a developer bug, fill out the steps below. If this is a developer bug in Compose, please file against the Jetpack (androidx) component instead:
-------------------------------------------
STEPS TO REPRODUCE
*(This should be understandable years later, by someone who will never talk to the reporter or assignee.)*
EXPECTED RESULTS
OBSERVED RESULTS
-------------------------------------------
TALKBACK VERSION *(Settings --> Accessibility --> Talkback --> Settings --> Advanced --> Developer)*
ANDROID VERSION *(Settings --> System --> About --> Build number)*
DEVICE MODEL *(Settings --> System --> About --> Model)*
-------------------------------------------
ATTACH TALKBACK VERBOSE LOG
1. Enable logs at Settings --> Accessibility --> TalkBack --> TalkBack Settings --> Advanced --> Developer --> Log --> Verbose
2. Reproduce the problem
3. Capture logs by running "adb logcat > my.log" , or with bug-report tools.
-------------------------------------------
ATTACH VIDEO AND VIEW TREE LOG
For us to look into your issue quickly, we’d like to see the UI visually and from the view tree perspective. To help us do that, please also include:
* a video.
* a view tree log
View tree log steps:
* Settings → Accessibility → TalkBack → TalkBack Settings…
* Advanced → Developer → Log → Verbose
* Advanced → Developer → Node tree debugging → On
* Customize gestures → swipe-left-then-down → Print node tree
* Go to the content-app
* Ensure Talkback is on
* Gesture swipe-left-then-down
* Run adb logcat > my.log
* Look for lines containing “TreeDebug”
-------------------------------------------
Disclaimer:
TalkBack logs exposes the contents of your screen to your device's logs.
-------------------------------------------
To avoid the possibility of sharing private information, please share bugreports and screenshots from Google Drive. Share files with android-bugreport@google.com and include only Google drive links in your bug. Please note, bug report attachments should not be included directly in issue reports.
Disclaimer:
Please note, by submitting this bug report, you acknowledge that Google may use information included in the bug report to diagnose technical issues and to improve our products and services, in accordance with our Privacy Policy (
Bug reports include personal information logged on your device or by apps, such as:
File names
Installed apps and usage
Email addresses of the profiles on the device
Device identifiers, such as phone number
Web history information, including URLs / URIs
Location information, including limited location history
Network information, such as IP/SSID/MAC addresses and saved or scanned APNs
System or device information, such as memory and processes