This FC is driving me nutts! It always appears whenever I will use S-Voice, or view the Gallery, I already tried doing a Wipe but it is still the same. I even tried the tip that I got from the Sprint S3 on updating Google Search but I still have the problem.
Please help!
I have had the same problem, only on my tablet. I think the error starts appearing after you you set up Google Now. Clearing data for Google Search and using the google search without setting up google now might keep the problem from reappearing. let me know if this worked for you.
EDIT:
Go to System Settings>Accessibility>Text-to-speech output> Select Pico TTS or anything that's not Googe Text-to-speech Engine
G mini gt S5570
Unfortunately Google Text-to-Speech Engine has stopped, Please Help
)CM-10.1 JB-Gapps 13-10-201\3, don´t open keyboard, impossible to get wi-fi, no matter how you swith imput mode, switch settings, bla bla bla.
Sorry to bother.
Hey guys,
After I rooted my S4, I went in Titanium and uninstalled a lot of the bloatware, including ChatOn. Now I'm having issues with the Samsung text-to-speech engine, which I've heard is attributed to the lack of ChatOn. However, I did make a backup of all the apps, but restoring ChatOn didn't fix the problem, and when I start ChatOn, I just get a black screen. And any time I open the text-to-speech options, it just starts giving me "Unfortunately, Samsung text-to-speech engine has stopped." I can't look at the settings, change the language, or anything.
Does anyone know how to properly restore ChatOn, or some other way to circumvent this problem?
You can only download it on play store or samsung apps and just go to titanium backup and "convert to system app" is that I would try. Anyway I don't think deleting chaton may get you this problem, once I always have deleted it.
Enviado de meu GT-I9300 usando o Tapatalk 2
ODIN to the factory
I'm no developer but I don't think ChatOn is the cause of this because I've deleted it before on my Note 2 and it never gave me any problem like that. Although I was running OS 4.1.2 and S4 is 4.2.2. But I think it is something else you have froze or deleted. I would recommend go through TB and search the apps you have frozen or deleted that has to do with txt to speech like Talkback or something like that & restore them one by one to see if that corrects it. Just a suggestion.
Change your text to speech provider to google and that error goes away.
Sent from my GT-I9505 using xda app-developers app
---------- Post added at 01:11 PM ---------- Previous post was at 01:10 PM ----------
My device >language and input >text to speech >google.
Sent from my GT-I9505 using xda app-developers app
Thanks for the responses, everyone.
But yeah I guess I got the idea from here: http://forum.xda-developers.com/showthread.php?p=41287449 and another thread somewhere.
So, I guess my problem is a bit complicated, and pretty difficult to explain.
1) I already have Google TTS checked, and I don't get the Samsung TTS error unless I (a) open a Samsung app (like S-voice), or (b) open up my TTS settings.
2) I don't really care about S-voice, although when people ask me to show me S-voice, I'd like to have it functional.
3) The only reason I bring this issue up is because I'm trying to enter my TTS settings in order to enable Light Flow or LEDBlinker Accessibility.
4) The reason it's making me enter TTS settings is because for some reason my system language and TTS language don't match up. >_<
It's all very bizarre and roundabout, but I've just gotten a feeling from some threads that uninstalling certain Samsung Apps (like ChatOn) can cause these TTS problems. I don't have any other apps uninstalled with TiBU, although I do have a few ATT apps frozen.
I'm beginning to think Odin'ing back might be my only option, though I'd like to avoid it. :/
bhatbhai said:
Thanks for the responses, everyone.
But yeah I guess I got the idea from here: http://forum.xda-developers.com/showthread.php?p=41287449 and another thread somewhere.
So, I guess my problem is a bit complicated, and pretty difficult to explain.
1) I already have Google TTS checked, and I don't get the Samsung TTS error unless I (a) open a Samsung app (like S-voice), or (b) open up my TTS settings.
2) I don't really care about S-voice, although when people ask me to show me S-voice, I'd like to have it functional.
3) The only reason I bring this issue up is because I'm trying to enter my TTS settings in order to enable Light Flow or LEDBlinker Accessibility.
4) The reason it's making me enter TTS settings is because for some reason my system language and TTS language don't match up. >_<
It's all very bizarre and roundabout, but I've just gotten a feeling from some threads that uninstalling certain Samsung Apps (like ChatOn) can cause these TTS problems. I don't have any other apps uninstalled with TiBU, although I do have a few ATT apps frozen.
I'm beginning to think Odin'ing back might be my only option, though I'd like to avoid it. :/
Click to expand...
Click to collapse
I'm with you on this. I wish I could find more help on this problem. I did the exact same thing and had the same results: I backed up and then uninstalled ChatOn and ChatOnV using Titanium Backup. That made S-voice and S-Translator stop working. So I tried re-installing ChatOn and ChatOnV but they would just freeze when opening, so I uninstalled those again and searched for ChatOn in the play store, installed the two apps (ChatOn and ChatOn Video & Voice) and now ChatOn works, again. The problem is, S-Voice and S-Translator do not. I also switched to using Google TTS in the settings, but I really would like to get S-Voice to work again (S-Translator I can live without, but I'd love it if S-Voice worked). I can't figure out how to get that to work correctly short of Odin-ing, which seems like a lot of effort.
mnrbradley said:
I'm with you on this. I wish I could find more help on this problem. I did the exact same thing and had the same results: I backed up and then uninstalled ChatOn and ChatOnV using Titanium Backup. That made S-voice and S-Translator stop working. So I tried re-installing ChatOn and ChatOnV but they would just freeze when opening, so I uninstalled those again and searched for ChatOn in the play store, installed the two apps (ChatOn and ChatOn Video & Voice) and now ChatOn works, again. The problem is, S-Voice and S-Translator do not. I also switched to using Google TTS in the settings, but I really would like to get S-Voice to work again (S-Translator I can live without, but I'd love it if S-Voice worked). I can't figure out how to get that to work correctly short of Odin-ing, which seems like a lot of effort.
Click to expand...
Click to collapse
After I froze some bloatware, I actually started having problems with the Samsung text-to-speech (FC's repeatedly, very annoying). To fix the issue, I switched away to Google's TTS, and then froze the Samsung TTS to get it to go away. This, in-turn, broke S-Voice. To fix S-Voice, iirc, I ended up converting it to a User App and it began working again. Quite strange.
Try fiddling with these in different orders. Take backups with TiBu first, of course. As a last resort, Odin'ing to stock should fix anything.
EDIT: also, for broken apps (like Chat-On), try clearing the cache and data for each using TiBu (cache option is on page2).
Change text to speech to google it goes away.
Sent from my Samsung-sgh-i337 using xda app-developers app
Aou said:
After I froze some bloatware, I actually started having problems with the Samsung text-to-speech (FC's repeatedly, very annoying). To fix the issue, I switched away to Google's TTS, and then froze the Samsung TTS to get it to go away. This, in-turn, broke S-Voice. To fix S-Voice, iirc, I ended up converting it to a User App and it began working again. Quite strange.
Try fiddling with these in different orders. Take backups with TiBu first, of course. As a last resort, Odin'ing to stock should fix anything.
EDIT: also, for broken apps (like Chat-On), try clearing the cache and data for each using TiBu (cache option is on page2).
Click to expand...
Click to collapse
You are a fantastic person. Converting S-voice to a user app worked perfectly.
Sent from my Nexus 10 using Tapatalk HD
Aou said:
After I froze some bloatware, I actually started having problems with the Samsung text-to-speech (FC's repeatedly, very annoying). To fix the issue, I switched away to Google's TTS, and then froze the Samsung TTS to get it to go away. This, in-turn, broke S-Voice. To fix S-Voice, iirc, I ended up converting it to a User App and it began working again. Quite strange.
Try fiddling with these in different orders. Take backups with TiBu first, of course. As a last resort, Odin'ing to stock should fix anything.
EDIT: also, for broken apps (like Chat-On), try clearing the cache and data for each using TiBu (cache option is on page2).
Click to expand...
Click to collapse
I tried clearing the cache like you mentioned, but I didn't try freezing the Samsung TTS. I didn't have Titanium Backup Pro, so I couldn't do that, but I went ahead and made the purchase and froze Samsung TTS and that fixed it (I also changed S Voice to a User App, although I'm not sure if that is what fixed it or freezing the TTS).
At any rate, thanks for the help! S Translator works now, as well. I went ahead and froze several other apps that I don't need (rather than removing) and everything is smoother and less bloated
FIXED!
bhatbhai said:
Hey guys,
After I rooted my S4, I went in Titanium and uninstalled a lot of the bloatware, including ChatOn. Now I'm having issues with the Samsung text-to-speech engine, which I've heard is attributed to the lack of ChatOn. However, I did make a backup of all the apps, but restoring ChatOn didn't fix the problem, and when I start ChatOn, I just get a black screen. And any time I open the text-to-speech options, it just starts giving me "Unfortunately, Samsung text-to-speech engine has stopped." I can't look at the settings, change the language, or anything.
Does anyone know how to properly restore ChatOn, or some other way to circumvent this problem?
Click to expand...
Click to collapse
I did the exact same thing. Deleted some bloat ware (including chat on) and S Voice stopped working correctly. Even though I had a back up on TB I it didn't fix the error message. Finally I just unrooted it (just youtube how to unlock & unbrick galaxy s4). Very simple and straight forward. It took it back to factory firmware, then I just rooted it again. And no I'm obviously not going to delete chat on.
How to convert it to user app?
te
Aou said:
After I froze some bloatware, I actually started having problems with the Samsung text-to-speech (FC's repeatedly, very annoying). To fix the issue, I switched away to Google's TTS, and then froze the Samsung TTS to get it to go away. This, in-turn, broke S-Voice. To fix S-Voice, iirc, I ended up converting it to a User App and it began working again. Quite strange.
Try fiddling with these in different orders. Take backups with TiBu first, of course. As a last resort, Odin'ing to stock should fix anything.
EDIT: also, for broken apps (like Chat-On), try clearing the cache and data for each using TiBu (cache option is on page2).
Click to expand...
Click to collapse
Hi bro ... can you tell how to convert s-voice to a user app? please do reply ! im, stuck with this ... else ill have to factory reset which will b a long process!
firecruz said:
te
Hi bro ... can you tell how to convert s-voice to a user app? please do reply ! im, stuck with this ... else ill have to factory reset which will b a long process!
Click to expand...
Click to collapse
I used Titanium Backup to do this. I'm not sure if this option is available in the basic version - I purchased Pro a very long time ago. Reply if you need some specific instructions.
[email protected],
I've CyanogenMod 11 M7 installed on my Samsung Galaxy Note 3 N9005 (international). I have installed the newest version of the Google Search App and the Google Now Launcher as well. Google Now and the hotword detection are activated. But the hotword detection 'OK Google' does not work.
Is there no support for this in CM11? If not in general, is it not supported in CM11 for the Galaxy Note 3?
I've tried different workarounds. Usually I use Nova Launcher. As of late it supports the hotword detection as well. I thought maybe the feature is buggy. So I tried it with Trebuchet and Google Now Launcher. Both didn't work. It also doesn't work in the Google App itself!
I've configured my system in german. Usually voice input and also the hotword detection should work in german as well. Again I thought maybe it's buggy and switched to english (US). It didn't work.
I also never saw the prompt for the hotword in the Google search bar.
I use Xposed Framework with a module called Xprivacy. With Xprivacy one can restrict permissions for Apps, including access to media, like the camera and microphone. I thought this could be a reason, but I haven't restricted media for the Google Search App, Google Now Launcher and Nova Launcher. Can Xprivacy be a problem anyway?
Does anyone have the same problem? Does anyone know how to fix this?
Greets
The matter has sorted itself out. I got an update of the Google Search App today, now it works! :victory: :fingers-crossed:
It seams that this was a bug. I still don't see the prompt for the hotword in the Google search bar, but maybe this is another tiny bug and doesn't bother me.
I've still configured my system in german. Hotword detection works in the Google Search App, Google Now Launcher and even Nova Launcher! It doesn't work in Trebuchet, but one could assume that.
Anyway, thanks to everyone who contemplated about the case.
I have some more interesting information.
Because hotword detection didn't work again, I dealt with the topic again.
It seems that it wasn't a bug. I used Titanium Backup to integrate updates of system apps into the system. I don't know why , but obviously this caused the problem.
So I completely uninstalled the app using Titanium Backup and installed it again via the Play Store. Now hotword detection works again.
So if you have the same problem, do not integrate the newest version of the app into the system, or if you don't have it installed, simply install it via the Play Store and you should be fine. :good:
Greets