Open GoogleCodeExporter opened 8 years ago
I was able to reproduce this problem in TalkBack version 4.3.1, with an
extremely simple app. The app has one activity, which has one button. When
the user presses the button, the app attempts to do TTS speech. If TalkBack is
turned off, then the speech happens correctly. If TalkBack is turned on, then
no speech is heard. The app writes log entries that indicate, in both cases,
success status on all TTS calls.
See attached code.
Original comment by lewlas...@gmail.com
on 6 Oct 2015 at 9:42
Attachments:
I just looked at the recently-opened source code for TalkBack.
Evidently, the code where TalkBack interrupts speech from other apps is in the
method FailoverTextToSpeech.stopAll() .
The question that I would like to investigate is whether this code is, perhaps,
being called overzealously, from the Java class SpeechController, in
circumstances where TalkBack has nothing to say, but where it just wants to
clear out its own, higher-level queue, without doing a SPEECH_FLUSH_ALL at the
level of the underlying TTS engine.
Original comment by lewlas...@gmail.com
on 7 Oct 2015 at 4:18
Original issue reported on code.google.com by
henk.a...@gmail.com
on 25 Sep 2015 at 9:54