Develop Bugs

Irritating TTS and Accessibility bug

I appologize if this has already been posted, I could not find any record of a thread similar.
Just thought I'd let you all know about this bug in case it happens to some of you.
I got my Nexus a few days ago and one of the first things I did was to install LightFlow (a necessity on any phone with a notification LED!). Everything was working perfectly fine until I opened Google Books and my phone started reading it out loud to me. I checked Talk Back in the accessibility menu and it was still 'Off'. I turned it on and off a few times (as you do) and unchecked everything in the talkback settings but it made no difference. My phone then started reading out websites to me on the browser (which was INCREDIBLY annoying when it hit a really long link!). I found out you can stop this from happening quite easily by going to 'Settings > Apps > All > Google TTS Engine > Disable'. The only problem with this is that when it's disabled, Google Books force closes for some ridiculous reason and the browser starts acting weird.
After a while I realized that it all started happening after I installed LightFlow. So I disabled it in the Accessibility menu and, hey presto, no more TTS bug. I'm not sure whether this is a problem with LightFlow or whether it's a problem with the accessibility menu, but it seems if something in the menu is enabled, then the other things will randomly turn on too.

I too would like to know how to fix this. Light flow worked just fine but then some notifications stopped working properly, so I reinstalled the app and now I have the irritating voice!!!
Sent from my Galaxy Nexus using XDA App

I have the same problem, when Light Flow is enabled, TTS read everything in my web browser :| disabling Light Flow solve the issue. But this is not what i want to do.

I find a solution on
http://www.folioflow.com/ff/page/website/lightflow/pageId/1931
Some users have issues where the TalkBack accessibility service gets enabled when the Light Flow accessibility service is switched on. This seems to be a bug in Ice Cream Sandwich and we've raised an issue for it. Add a star to it here: http://code.google.com/p/android/issues/detail?id=23105 as a temporary workaround, go into your phone "settings" --> Accessibility --> Install web scripts --> and make sure it's set to "Not allowed"
Click to expand...
Click to collapse

Thanks for sharing! I dont have a problem with Lightflow and reading browser. However I am having a problem with SVOX tts with some apps, so I thought this (disabling LF in accessibility) might fix my problem.. It did not. But it was worth a try!

[Q] [help] Google Books Reading Aloud Automatically

For some reason whenever I open up a book in google books, it starts reading it aloud. I can't find a setting for this anywhere and it is driving me nuts. Has anyone else seen this? I've searched around online and have found absolutely nothing about this. I've run into this on two different ROMs now (Bugless Beast as well as Codename Android). Any help is much appreciated.

I am having the exact same problem without any luck in finding a solution. I would also appreciate any advice to a solution.

Something similar was happening to me as I typed messages in Codename Droid. It would read aloud every word I typed. I'm using Thumb Keyboard - and finally discovered that Text-to-Speech was somehow checked in settings. I had definitely not done it myself - in fact I've never realized it was there, and I've used Thumb Keyboard for years now. Maybe check there? I don't know how it would impact it - but maybe it is.
Also check in the settings for Google's text-to-speech output.
Good luck.

In google books open the book and then hold your finger down near the top of the on screen button. A slider should appear to allow you to move through the book and a bar should appear on the top of the screen. Open the menu and choose the stop reading aloud option.

Yeah, I know you can tell it to stop reading aloud, but the problem is I have to do this every time I open any book. It automatically reads every book aloud as soon as I open it.

I would try wiping data from the Google Books app...

I did that. I can't uninstall it either because it's a system app apparently. I was going to try and uninstall / reinstall after wiping data.

sowelie said:
Yeah, I know you can tell it to stop reading aloud, but the problem is I have to do this every time I open any book. It automatically reads every book aloud as soon as I open it.
Click to expand...
Click to collapse
weird I only had to do it in one book and now none of them read aloud automatically. I just installed a 4.0.4 port with the updated gapps of course so maybe its broken in 4.0.2/3?

You should only have to change it once...
Since you've tried deleting data, I would try fixing permissions (using ROM Manager), to see of the changes are not sticking due to a permissions error...

Do you have lightflow installed? I read somewhere (I can't find it right now) there is a bug with the accessibility settings. It will sometimes enable talkback.

Bump any solution yet? It's really annoying

El Daddy said:
Do you have lightflow installed? I read somewhere (I can't find it right now) there is a bug with the accessibility settings. It will sometimes enable talkback.
Click to expand...
Click to collapse
I think there's something to this.
I have no idea if this is always the issue, but I had this problem and when I looked at the accessibility settings, lightflow did show up and was enabled there. I turned it off, and not only does lightflow still work, google books has stopped reading out loud all the time. I'd say turning off all of the accessibility settings that are enabled would be worth a shot, even if you don't have lightflow, there might be something there that's screwing with accessibility.

OwMySocks said:
I think there's something to this.
I have no idea if this is always the issue, but I had this problem and when I looked at the accessibility settings, lightflow did show up and was enabled there. I turned it off, and not only does lightflow still work, google books has stopped reading out loud all the time. I'd say turning off all of the accessibility settings that are enabled would be worth a shot, even if you don't have lightflow, there might be something there that's screwing with accessibility.
Click to expand...
Click to collapse
This is the issue. It is a bug with ICS and not lightflow - but happens none the less.
http://www.folioflow.com/ff/page/website/lightflow/pageId/1931

El Daddy said:
Do you have lightflow installed? I read somewhere (I can't find it right now) there is a bug with the accessibility settings. It will sometimes enable talkback.
Click to expand...
Click to collapse
Thanks! That definitely was the issue. Once I disabled light flow in accessibility settings, the problem went away! You rule!

Google Now Launcher not showing OK google from any screen

I can't seem to get "OK google" from any screen settings to appear. I only get the standard option from the home screen. A week ago I installed the launcher and it worked. I did a system restore and updated now it doesn't. Anybody know what causes this. I know I have the latest app and GPS.

From what I've seen inside the app, you need English US activated.

xRamz said:
From what I've seen inside the app, you need English US activated.
Click to expand...
Click to collapse
It is....any other suggestions? It worked a week ago now not....very weird issue.

The clearing the app's data, force stop it, and restart.

[Q] Ok Google not working Says can't open microphone. please help

Ok google was working fine but now when I tap the mic button on Google search its says can't open microphone. Please help. Also went to settings and all apps and couldn't find google search

Try a reboot, if not go to applications, Google voice, clear cashe/data.
Pp.

Same thing just happened to me. Had use OK Google earlier today and now the mic will not open. Since this has happen to others, what is the fix?
Google voice clear cashe does nothing
OK Google works fine on both my Samsung Galaxy S and my Nexus 7, so why did it have mic issue only on my Galaxy S5?

Same with me any solutions yet?

Try a reboot, no one has reported what worked for them.
Pp.

go to settings .
then go to installed apps.
then scroll down and select google app.
scroll down and select permission manager.
just wait a bit and you will get all the permission options.
now make sure that a green tick beside "record audio" and "make phone call" option.
if not the just click on the particular option and select "accept".
thank you.
make enjoy to have a great device or a gadget.

Its not about permissions i guess
badinfluence12001 said:
Same with me any solutions yet?
Click to expand...
Click to collapse
In simple words - another proggie uses this process and keeps the mic busy. As soon as it releases the mic it will become available to OkDoodle).
Just check it our - restart the phone and as soon as you can tap the mic - it will work. then it will say the same thing - cannot open the microphone.
Solution. In my case i had to find and delete an app that was using the mic non-stop - it was navigator. Go to settings>applications>app manager>slide to running applications. Now "stop" an app that uses any sort of microphone input - it could be a navigation, a dictaphone, a keyboard (remember, theres a little mic icon in da corner). It did help me to resolve this issue. Unfortunately, I am now using a google navi instead of my preferred one...
technically: record the log file of processes, check which process opens this -
android.media.AudioRecord;
android.media.MediaRecorder;
android.media.AudioFormat

Another good reason to keep stock Google apps that work properly.
Pp.

the same problem....
balashandr is right, I had the same problem and the solution for me was to uninstall a voice assistant had installed, restart the phone and ready (I have a Note4 by the way)

You're welcome hopefully
If you have the app audiko ringtones uninstall it and your mic will work instantly it worked perfectly for me. When I went s voice it told me that another app was using my microphone so I remembered that app that I just installed deleted it and boom my mic is fixed

Thanks a lot Helperthehelper
You're right. Since latest update a couple of days Audiko app blocks other app usage to microphone.
I've stopped the Audiko process and my phone it's perfect
Thanks

Helperthehelper thanks so much .. audiko is the problem

Alternative method
An alternative method is to modify the app permissions and ignore microphone. You get to keep the app and the problem is solved as well.

Thank you so much it worked for me!

ok google only works once after a restart then will only hear the ok google part. I installed a voice app yesterday called discord I disabled it first then tried no luck again only working after a restart and then only hearing ok google. I completely uninstalled the discord app and restarted and STILL only works right one time, then after only hears the ok google part. I have systematically turned off any app I could access to microphone only set for google. STILL no joy.
is this a ok google thing? or is my phone buggered?
editing to confirm that nothing happens after my phone hears my say ok google, hears ok google just fine but then nothing else after

Turning off s voice worked for me. I was also getting can't open microphone when using ok google on any screen

finally i found the problem, just go to samsung s voice and turn off mic permission

android Q builds for many phones have a google assistant glitch, deny mic perms to google app fixes it and regular microphone works again

Flash Google Nano Gapps
MrJesseJay said:
Ok google was working fine but now when I tap the mic button on Google search its says can't open microphone. Please help. Also went to settings and all apps and couldn't find google search
Click to expand...
Click to collapse
Try flashing nano gapps then clear cache

OK Google with screen off

I have been using the Moto Z2 Play for almost a year now, and the feature i used every day is waking the phone when the screen is off by using the OK/Hey Google command.
The tooltip in the Google voice match settings used to read: Access your assistant any time you say "OK Google", even if your screen is off or you're using your favorite apps.
However after updating the Google app to version 8.28 the tooltip changed to "whenever your screen is ON" instead of "even if your screen is off".
And sure enough, the phone will no longer respond to commands until i pick up the phone and manually turn on the screen, which defeats the purpose.
Why was this feature removed? I have tried everything and finally had to uninstall Google updates and install an older version(8.24) from apk mirror to get Assistant to work properly again.
What is even more puzzling to me is that this problem seems specific to my Z2 Play, i have the latest Google app version(8.28) on my Xiaomi phone, and the tooltip still says "even if your screen is off" and it works as it should.
I tried Googling this issue, i checked the Motorolla support forums, the Google assistant support forums etc. and couldn't find any mention of this issue.

This has also happened to me! I thought I just needed to reboot the phone to maybe fix a background service that had stopped, but I also see that "...even when your screen is off" has been removed from the Voice settings. This is one of the features that made the Moto Z line attractive to me, and I literally use (well, used) the feature several times a day, especially while driving. I also use Android Auto and now I have to either touch the microphone on my truck's head unit screen, press and hold the voice button on the steering wheel for 3 seconds, or unlock my phone so I can talk to it. I have a self-built Android Auto in my other car and it also has this issue, which I now know is not related to either car's system. Thank you for posting and bringing this to our attention.
I think this must be a bug in the latest Google app. Does anyone know where we can submit bug reports for the app, or voice control/Google Assistant in general?

Has any else experienced this problem, or does anyone have ideas about what to do to potentially resolve it? Surely OP and I can't be the only two people who have witnessed this issue.

tropho said:
Has any else experienced this problem, or does anyone have ideas about what to do to potentially resolve it? Surely OP and I can't be the only two people who have witnessed this issue.
Click to expand...
Click to collapse
It is likely that there just aren't many Z2 play users who frequent xda, and the ones that do never noticed the issue because they don't use the feature.