CODEWITHSUNDEEP
androidtext-to-speech
smart_cookie
smart_cookie

Reputation: 85

“pico TTS Engine has Stopped" error

I am writing a codes using TextToSpeech. It went well throughout the codes, however, every single time I exit the codes, it gives me the error message saying that 'Unfortunately, pico TTS engine has stopped." This only happens when I exit the code. I am wondering why this happens. Thanks.

Upvotes: 2

Views: 4960

Answers (3)

user2550012
user2550012

Reputation: 11

Please see the issue at this link

CTS cases fail due to NE in SVOX TTS library

Failed CTS cases:
android.speech.tts.cts.TextToSpeechTest#testSpeak
android.speech.tts.cts.TextToSpeechTest#testSpeakStop
android.speech.tts.cts.TextToSpeechTest#testSynthesizeToFile

We can also reproduce this NE by following steps:
1. Go to Accessibility Settings
2. Select Text to speech output
3. Click play

Analysis: Exception occurs due to calculation of
picokpr_getAttrValArrInt32(...) is incorrect. The logic here intends
to clear the MSB and return the rest of the bits. We found if library
compiled in Android N environment the result of comparison operation
is different from library compiled in Android O environment. In
Android O, actual returne value doesn't process the value and returns
as it is. This causes invalid pointer access and hence native
exception due to segmentation fault.

Solution: Changed to use bitwise shift instead.

Bug: 64204643 Test: After applying this patch, CTS cases can pass and
exception can be fixed.

Change-Id: Ife3137225ecf9667df62321472420fab6ab88d2e

Upvotes: 0

Ahmad Shbita
Ahmad Shbita

Reputation: 73

I got the same problem. every time I changed activity or exit the program I got “pico TTS Engine has Stopped". I changed the api from 23 to 24 and used android 7.0 and the error have gone.

Upvotes: 1

user5104628
user5104628

Reputation:

I was getting this message too whenever I exited my code or whenever I called textToSpeech.shutdown();

I solved this problem by deleting my AVD (Android Virtual Device Nexus_6_API_23) and creating a new one. The new AVD worked without giving any error message.

Apparently this was a problem with my AVD and not a problem with my code or the TTS engine.

Upvotes: 1

Related Questions