Related
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.
This past week, I've been reading that Google is pushing "Google Assistant" out, to replace the standard "Ok Google", to a bunch of Marshmallow and Nougat phones.
Has anyone received that yet, or know if the Axon 7 is going to get it soon?
Every phone running Android 6.0+ will receive the update but you already knew that. They are running the roll out as we speak but only for English users in US. English users in Australia, Canada and UK and Germany will soon follow. Rest during the course of the year apparently. So if you are in the US you will likely receive it soon or may already have received an update to the app. Hope this clarifies.
I just got the update a few minutes ago! I'm in northern California.
Sent from my ZTE A2017U using XDA-Developers Legacy app
I literally just got it a few minutes ago, Northeast US here. It's extremely quick, I'm impressed.
Yep, you guys prompted me to check mine, and I have it too!
I hate it. I use long press for Google Now to search like a hundred times a day. Now it is the Assistant and I see no way of typing my query. So now I have no way to do a search in one step. Anything I can do to get it back the way it was? Or a way to get a text field into Google Assistant?
yes!.. its working for me.. but..
dont know how it started working?
dont know where it the got the update from?
dont know where to check the update?... can someone pls help me find the answer?
use to use the long home press to check screen search.. disabled it today and thought because i disabled it, the assistant got kicked in.
Happy its working now coz the only reason wanted to get the pixel is for the assistant. this is great!
It seems like Google just doesn't want me to have assistant lol
---------- Post added at 04:50 AM ---------- Previous post was at 04:49 AM ----------
I can force my phone to set up the Google Assistant, naturally, by removing my account and clearing data from the Google App, Play Services, and Play Store, and then holding the home button > then adding my account. But as soon as I back out of the assistant it goes back to On Tap.
How do you update, is this an upgrade to Google home? Presume this is not available to the Chinese version?
swashybrigand said:
dont know how it started working?
dont know where it the got the update from?
dont know where to check the update?... can someone pls help me find the answer?
use to use the long home press to check screen search.. disabled it today and thought because i disabled it, the assistant got kicked in.
Happy its working now coz the only reason wanted to get the pixel is for the assistant. this is great!
Click to expand...
Click to collapse
If you have the correct Google app, you already have Assistant. It just wasn't enabled yet. I don't know exactly how it works, but the app sees that you're on Marshmallow or higher in your build.prop and enables it. I currently have a Nexus 6p and before Google decided to enable it for all phones over 6.0, devs figured out that changing a couple of lines in the build.prop tricked the app to think the phone was a Pixel, thus enabling Assistant.
effluent said:
I hate it. I use long press for Google Now to search like a hundred times a day. Now it is the Assistant and I see no way of typing my query. So now I have no way to do a search in one step. Anything I can do to get it back the way it was? Or a way to get a text field into Google Assistant?
Click to expand...
Click to collapse
https://android.gadgethacks.com/how...ndroid-device-switch-back-google-now-0174676/
Howie Dub said:
If you have the correct Google app, you already have Assistant. It just wasn't enabled yet. I don't know exactly how it works, but the app sees that you're on Marshmallow or higher in your build.prop and enables it. I currently have a Nexus 6p and before Google decided to enable it for all phones over 6.0, devs figured out that changing a couple of lines in the build.prop tricked the app to think the phone was a Pixel, thus enabling Assistant.
https://android.gadgethacks.com/how...ndroid-device-switch-back-google-now-0174676/
Click to expand...
Click to collapse
I found those instructions weeks ago but I'm not rooted and there's no option to add languages so I'm screwed. The update also made do not disturb mode turn on 24/7 unless I completely disable it. What a load of BS.
effluent said:
I hate it. I use long press for Google Now to search like a hundred times a day. Now it is the Assistant and I see no way of typing my query. So now I have no way to do a search in one step. Anything I can do to get it back the way it was? Or a way to get a text field into Google Assistant?
Click to expand...
Click to collapse
I feel your pain bro. I hate this fact. I'm still using the Pixel launcher which has the search widget for text. I find myself going to the home screen to do my Google searches. It's horrible.
Avantiel said:
I feel your pain bro. I hate this fact. I'm still using the Pixel launcher which has the search widget for text. I find myself going to the home screen to do my Google searches. It's horrible.
Click to expand...
Click to collapse
I'm using Nova so I set it up so that pressing home (once home) or swiping up on the drawer icon takes me to search. Yeah it really sucks to have to go to the home screen. That damn assistant sucks. It forgets my voice training after awhile too and I have to do it again.
I have on my G version, I don't know for sure, but I got so fed up waiting, I tried changing my language to US, rebooted the phone and bam! Within 10 seconds I had it. Also I had updated to the latest google play services. I had done this a million times but nothing happened until the language change. Coincidence?
Mike
A few days after a fresh install of Nougat on a new device, Voice Typing started acting funny. It's inserting ALL of the likely variations of what I'm saying in one run-on sentence. (See sceeenshot) Tried wiping cache through recovery. Have not yet uninstalled Google app. Reproduced bug on stock and 3rd party messaging and keyboard apps. Ideas?
thefoss said:
A few days after a fresh install of Nougat on a new device, Voice Typing started acting funny. It's inserting ALL of the likely variations of what I'm saying in one run-on sentence. (See sceeenshot) Tried wiping cache through recovery. Have not yet uninstalled Google app. Reproduced bug on stock and 3rd party messaging and keyboard apps. Ideas?
Click to expand...
Click to collapse
It's not nugget, it's Google assistant
That's what I suspected. Any work around?
I have to say things 3 and 4 times with Google Search. First time it doesn't hear me the second time it doesn't hear me and the third time it's just here's the first word....
Sent from my SM-G935T using XDA-Developers Legacy app
Tried uninstalling Google App and Play Services updates, and turning off assistant. The only thing that works for now is disabling Google Voice Typing. Which then defaults to your keyboard apps built in voice to text, which is far inferior. Maybe wiping Dalvik cache?
Apparently I'm not the only one. The reviews for Google App on Play Store have plummeted since the update. Multiple users have the same complaint. Thinking about starting a petition...
I think I have a workaround, at least until Google fixes the problem. Find the Google App under Settings > Applications and Unistall Updates. This rolled me back to ver 6.7.21.21arm64. Next you're going to have to roll back Google Play Services. Download from Play Services Info app from Play Store and check your version. DON'T update through Play Store. Use APK Mirror.
https://www.apkmirror.com/apk/googl...s-10-2-98-440-146496160-android-apk-download/
Select "Google Play services 10.2.98 (440-146496160)" (this one is dated early February, before Assistant role out.) Side load and soft reset phone. Just make sure you do NOT accept any updates to the Google App for now and you should be good to go. Google. Voice Typing works as expected again.
I'll keep you all updated on how this works out.
Moderators ; can you maybe move this thread to the Guides forum? Hopefully it can help more people there.
Hello all. I just noticed an issue that I dont remember having before. My Shield is updated to whatever the current official release is, and I might be rooted, can't remember (every update unroots me, cant remember if I re-rooted before or after the last update..). So the issue is, when I use the Voice commands to search anything, it applies very heavy censoring using Google's preferred logic (for instance, the word "porn" is censored but another dirty P-word is not..? I tested a ton of dirty words and it made no sense what it decided was bad and what was ok...). In the Shield's settings I have safe search off as well as the bad word filtering in the Voice settings disabled. I tested voice searching and voice to text input on my phone using the same Google account and it doesnt censor anything... Anyone have any idea how to resolve this? I Google'd around and all I found were a number of people saying they also have this issue, and it seems to have sprung up out of the blue. But it wasnt any help as there was no resolution, the reports spanned from 2011ish to 2016, and there was no common device or Android OS version...
also, JFYI, I noticed this issue by trying to search for SourceFed's video where they attended the hentai convention. "SourceFed Hentai Con" said aloud to my Shield resulted in it searching for "SourceFed H***** Con," and Youtube ignoring the H***** and just giving me every result containing "SourceFed" and/or "Con." Manually typing the word into the search on the Shield yielded the desired result, though... I am certain I have been able to voice cuss words in the past to look up songs on Youtube, but I cant give even a vague guess at when this censoring began for me..
Do you happen to have a different google search installed? A sideloaded version of the phone google search? If so, that has some voice settings too.
But if you are just using the inbuilt search function, maybe try changing language first, to a different english, then check the filters again etc. And try enabling blocking offensive words, use it, reboot, uncheck?
Or else, go to settings, apps, then in system apps select Google Search and Uninstall updates. Then it will reinstall updates probably, or do it manually via Play Store. And try Clear Data as well.
If that doesn't work, sign out of your google account. and last resort, factory reset?
Ive tried much of what you suggested already, but Ill give the rest a shot (changing languages temporarily and uninstalling/reinstalling updates mainly). If that doesnt work I will just have to live with it, not a big enough issue to warrant a factory reset lol. Thanks for the suggestions. I considered doing basically evertything you suggested, but figured it was unlikely to help. You also suggesting the same things makes me think there is a sliver of hope. Ill report back.
So, first thing I did was change the language to UK English and test it. Its not censoring voice search from the main menu, but IS censoring in Youtube only now. Changing back to US English, Youtube is censored and main screen searches arent. So, progress at least.
faaaaq said:
Ive tried much of what you suggested already, but Ill give the rest a shot (changing languages temporarily and uninstalling/reinstalling updates mainly). If that doesnt work I will just have to live with it, not a big enough issue to warrant a factory reset lol. Thanks for the suggestions. I considered doing basically evertything you suggested, but figured it was unlikely to help. You also suggesting the same things makes me think there is a sliver of hope. Ill report back.
So, first thing I did was change the language to UK English and test it. Its not censoring voice search from the main menu, but IS censoring in Youtube only now. Changing back to US English, Youtube is censored and main screen searches arent. So, progress at least.
Click to expand...
Click to collapse
Disable Restricted Mode in the youtube settings?
Restricted Mode has always been disabled. Voice-searching Youtube on my phone isnt censored, I should have mentioned. So at the moment, across all of the Google ecosystem, for some reason the only thing being censored is voice search in Youtube on my Shield... Going to clear Youtube data and updates on the Shield and let it refresh itself and see what happens.
Now that you mention it, Youtube does filter out some words as well. It does show the word titties, but the word fu ck is with stars. Maybe it's just the youtube app?
I can say f you in the regular search option. in Youtube I see stars. So maybe it's just youtube censorship...
---------- Post added at 01:03 AM ---------- Previous post was at 12:54 AM ----------
faaaaq said:
Restricted Mode has always been disabled. Voice-searching Youtube on my phone isnt censored, I should have mentioned. So at the moment, across all of the Google ecosystem, for some reason the only thing being censored is voice search in Youtube on my Shield... Going to clear Youtube data and updates on the Shield and let it refresh itself and see what happens.
Click to expand...
Click to collapse
Yeah, it does seem to restrict outputting several words in the Youtube leanback app. In any language.
Maybe that's just built in the youtube app for tv.
You could consider using the phone/tablet youtube app. You can find it on the Aptoide app, or just download it from apkmiror.com and install it on your device. Then use an app (on the tv play store) called TV App Repo to create a shortcut on your Homescreen.
Maybe using the full youtube app will work. You can probably use the right stick on your controller as a mouse. Right trigger to click, hold to scroll. A to confirm, B for back.
EDIT: Tried it, the regular app doesn't seem to act any different. It uses the same voice overlay.
I actually used the regular app for a short time, as there are modded versions available that completely block ads, but it was entirely unusable for me. Barely even seemed to respond to input so all I could do was view front-page videos. Now I am doing the four month free trial of Youtube Red/Play Music, so no ads anyways haha. Thanks for your help though. Definitely looking to be no "fix" for this, but...I realized a very simple workaround. Doing the voice search from the main screen by default (for me at least) uses Youtube as its main results source. So I just have to remember if I need to search for anything with a potentially dirty word in it, just make sure to hit the Home button then the search button. I think that is an acceptable option, just not sure why Youtube's Leanback app has the restriction in the first place..
faaaaq said:
I actually used the regular app for a short time, as there are modded versions available that completely block ads, but it was entirely unusable for me. Barely even seemed to respond to input so all I could do was view front-page videos. Now I am doing the four month free trial of Youtube Red/Play Music, so no ads anyways haha. Thanks for your help though. Definitely looking to be no "fix" for this, but...I realized a very simple workaround. Doing the voice search from the main screen by default (for me at least) uses Youtube as its main results source. So I just have to remember if I need to search for anything with a potentially dirty word in it, just make sure to hit the Home button then the search button. I think that is an acceptable option, just not sure why Youtube's Leanback app has the restriction in the first place..
Click to expand...
Click to collapse
Yeah, I find it strange that there are apparently two voice search apps built-in. But indeed, searching from home does the trick.
Rooted, installed Nova, disabled all Amazon bloatware. Kindle working great, only issue is Google Search will not respond with a voice. I'll ask what the weather is and it simply displays the result without telling me with the voice "It's 100 degrees and sunny." I'll ask using the mic button/Voice Search "who won the allstar game", no sound, no voice, just displays the answer. Have the latest google installed, playstore working fine, framework, etc. Got everything updated.
butthump said:
Rooted, installed Nova, disabled all Amazon bloatware. Kindle working great, only issue is Google Search will not respond with a voice. I'll ask what the weather is and it simply displays the result without telling me with the voice "It's 100 degrees and sunny." I'll ask using the mic button/Voice Search "who won the allstar game", no sound, no voice, just displays the answer. Have the latest google installed, playstore working fine, framework, etc. Got everything updated.
Click to expand...
Click to collapse
It's a bug in the Google app. I had the same issue with past updates. Whatever that last update did they broke the sound again.
butthump said:
Rooted, installed Nova, disabled all Amazon bloatware. Kindle working great, only issue is Google Search will not respond with a voice. I'll ask what the weather is and it simply displays the result without telling me with the voice "It's 100 degrees and sunny." I'll ask using the mic button/Voice Search "who won the allstar game", no sound, no voice, just displays the answer. Have the latest google installed, playstore working fine, framework, etc. Got everything updated.
Click to expand...
Click to collapse
I figured it out. Turn on Nova in accessibility options. Then say ok google.
I followed your directions and OK Google now works. I also hear the beep, but it still will not respond through a voice telling me what the weather is, or who won the ballgame. It just displays the information on the search app. Again no voice telling me if it's going to rain, or who won last night's game, Etc. I greatly appreciate you looking into this. So do you think it's still a glitch? I really like to hear the voice telling me stuff, I'm too lazy to read the info, LOL.
butthump said:
I followed your directions and OK Google now works. I also hear the beep, but it still will not respond through a voice telling me what the weather is, or who won the ballgame. It just displays the information on the search app. Again no voice telling me if it's going to rain, or who won last night's game, Etc. I greatly appreciate you looking into this. So do you think it's still a glitch? I really like to hear the voice telling me stuff, I'm too lazy to read the info, LOL.
Click to expand...
Click to collapse
Tap Google app > three lines bottom right > settings > voice. Make sure speech output is on. Also make sure you have offline speech downloaded. From there tap settings under assistant at the top > tablet and make sure thats all set.
Speech output is on, offline speech is downloaded in US English, I turned on Nova and accessibility settings, and it definitely turns on and beeps when I say OK Google but I still do not get a voice response when I ask any question. The Google app isn't your default Assist app. I'm getting that are on the Google Voice match settings. I have already deleted Alexa completely from the phone. Using ES File Explorer Pro, with root. I have also enabled Google through ADB and disabled Alexa through ADB.
butthump said:
Speech output is on, offline speech is downloaded in US English, I turned on Nova and accessibility settings, and it definitely turns on and beeps when I say OK Google but I still do not get a voice response when I ask any question. The Google app isn't your default Assist app. I'm getting that are on the Google Voice match settings. I have already deleted Alexa completely from the phone. Using ES File Explorer Pro, with root. I have also enabled Google through ADB and disabled Alexa through ADB.
Click to expand...
Click to collapse
You need to follow this guide: https://forum.xda-developers.com/hd8-hd10/general/guide-enable-google-assistant-ok-google-t3740145
You basically need to download settings database editor and make the edits to secure settings. Make sure to grant settings database editor the proper permissions.
Thanks Dragonfire, started with a brand new Kindle from scratch. I accidentally bricked my old one. Long story short I started with a new Kindle HD 10, rooted, installed all the Google apps, followed all of the directions from the guide... I still do not get speech output, the Google voice does not give me the answer that I asked for. Only displays the answer. Maybe it is a glitch as you originally suggested. I disabled Alexa as the guide says, and I was able to do the voice match and everything. Google does not speak the answers. I only get the famous Google beep. And that's it. The sweet lady Google Voice stays silent.
butthump said:
Thanks Dragonfire, started with a brand new Kindle from scratch. I accidentally bricked my old one. Long story short I started with a new Kindle HD 10, rooted, installed all the Google apps, followed all of the directions from the guide... I still do not get speech output, the Google voice does not give me the answer that I asked for. Only displays the answer. Maybe it is a glitch as you originally suggested. I disabled Alexa as the guide says, and I was able to do the voice match and everything. Google does not speak the answers. I only get the famous Google beep. And that's it. The sweet lady Google Voice stays silent.
Click to expand...
Click to collapse
Sorry I can't help more. I've not had this issue aside from the sound issue i had mentioned earlier, which was fixed by activating nova in accessibility.