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!
Related
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!
Problem: While I am driving if someone sends me a text. my SGS2 will automatically respond to that message with the text "I am driving now."
I have no way of stopping it before it goes out. I do not have any apps that I have installed that are supposed to do this. I've gone through every setting I can think of. And yes I have searched xda before posting this, but no luck.
Currently running CM10. Please help! If there is no way to actually stop this from going out, I would at least like to change the message to something indicating it's an auto response.
Oh and this is not one of my SMS templates. I've erased all of them. Never had much use for those.
The culprit here is most likely your stereo. I'm guessing your phone is connected to your (likely Kenwood) stereo via Bluetooth, while this is happening. This is due to BT-SMS (SMS over Bluetooth) implementation, and can be disabled from one of your stereo's menus.
See this thread for another example of this, in which case a bad BT-SMS implementation was doing even worse, by sending that text not only to those who were trying to call/text you, but also to other contacts heh.
http://rootzwiki.com/topic/28312-b3...iving-now-sent-automatically-to-contact-list/
Hope it helps.
Driving mode?
onoroff said:
Problem: While I am driving if someone sends me a text. my SGS2 will automatically respond to that message with the text "I am driving now."
I have no way of stopping it before it goes out. I do not have any apps that I have installed that are supposed to do this. I've gone through every setting I can think of. And yes I have searched xda before posting this, but no luck.
Currently running CM10. Please help! If there is no way to actually stop this from going out, I would at least like to change the message to something indicating it's an auto response.
Oh and this is not one of my SMS templates. I've erased all of them. Never had much use for those.
Click to expand...
Click to collapse
Is your "Driving Mode" turned on? I was getting a similar experience once (don't remember the ROM I was on then), and then I realised I had the "Driving Mode" turned on. Hope this helps!
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.
Hello,
I've had this issue since launch and I can't figure a way to fix this. Basically, when I first got my phone, the lock screen was displaying the temperature under the time, with a "tap to learn more" button. And after clicking that, it simply vanished from existence, never to be seen again. It does show itself back when there's a Google Calendar event, but the temperature is gone. And after doing a factory reset recently, the temperature is back, with the "tap to learn more" (which I don’t plan to press, now that I know this will make it go away)
Is there a way to fix this? Thanks
That's a lot of overkill
Find the app and clear it's data next time.
There may be a conflict... like with the Google app*. Could be in settings, somewhere, or in notifications. Disable all power management for now... it will cause erratic behavior.
You need to play with it.
* that nasty little permission to change system settings... can be misused.
blackhawk said:
That's a lot of overkill
Find the app and clear it's data next time.
There may be a conflict... like with the Google app*. Could be in settings, somewhere, or in notifications. Disable all power management for now... it will cause erratic behavior.
You need to play with it.
* that nasty little permission to change system settings... can be misused.
Click to expand...
Click to collapse
I get it. But I had to reset my phone anyway.
My problem is that it shows the temperature, but as soon as I press the "tap to learn more" thing, it shows a slide about at a glance and it just goes away.
So I don't think it's a permission issue if it works just fine before clicking on the forsaken text
Andrew8578 said:
I get it. But I had to reset my phone anyway.
My problem is that it shows the temperature, but as soon as I press the "tap to learn more" thing, it shows a slide about at a glance and it just goes away.
So I don't think it's a permission issue if it works just fine before clicking on the forsaken text
Click to expand...
Click to collapse
You need to track down the associated apks first then look them over. It may be a glitch that you can correct or maybe resetting the apk data is the only way to correct it.
Try clearing the system cache.
Try it in Safe mode to rule out 3rd party apps.
blackhawk said:
You need to track down the associated apks first then look them over. It may be a glitch that you can correct or maybe resetting the apk data is the only way to correct it.
Try clearing the system cache.
Try it in Safe mode to rule out 3rd party apps.
Click to expand...
Click to collapse
The question is, does it even work for you? I understood that it will be fixed eventually but nah.
Also what kind of apk are you talking about? This is literally the lock screen
Andrew8578 said:
The question is, does it even work for you? I understood that it will be fixed eventually but nah.
Also what kind of apk are you talking about? This is literally the lock screen
Click to expand...
Click to collapse
I don't have that device but troubleshooting is troubleshooting. You need to dig around for the apk but it's most likely there under system apps.
It's possible the firmware flash was corrupted if so a factory reset won't work. More likey it's a glitch.
Hopefully someone here knows the answer but it's not a major issue. I would tend to just ignore it other then to play with it as a curiosity. No doubt you'll find better fish to fry...
I posted this question in the A13 Beta 4 thread but didn't got any feedback, so post it as a separate question to see if someone can help.
I switch to A13 since beta 2 and just updated to beta 4, everything seems run smoothly. However, I just found out that my "Google Assistant" lost the "beep" sound! What it means is that if I say "OK, Google" or "Hey, Google", I can carry out to give the command or instruction as I want but I am losing the "Ting" sound of the reaction once I say "OK Goolge" or "Hey Google". It's not really a big deal but just gave me a funny feeling as I would have to look at the phone screen to see if Google Assistant really working. All I can say is that I don't know when this is started as I didn't use Google Assistant for quite a long time, but it is definitely working when my P6P was on A12.
Can't someone confirm if this is just me or if there is a setting I can get this "beep" sound to come back. I play around with the phone for a couple hours and couldn't figure out any setting in "Google" app, "Assistant" app and system sound to have this be related.
acwcanada said:
I posted this question in the A13 Beta 4 thread but didn't got any feedback, so post it as a separate question to see if someone can help.
I switch to A13 since beta 2 and just updated to beta 4, everything seems run smoothly. However, I just found out that my "Google Assistant" lost the "beep" sound! What it means is that if I say "OK, Google" or "Hey, Google", I can carry out to give the command or instruction as I want but I am losing the "Ting" sound of the reaction once I say "OK Goolge" or "Hey Google". It's not really a big deal but just gave me a funny feeling as I would have to look at the phone screen to see if Google Assistant really working. All I can say is that I don't know when this is started as I didn't use Google Assistant for quite a long time, but it is definitely working when my P6P was on A12.
Can't someone confirm if this is just me or if there is a setting I can get this "beep" sound to come back. I play around with the phone for a couple hours and couldn't figure out any setting in "Google" app, "Assistant" app and system sound to have this be related.
Click to expand...
Click to collapse
You have to turn on an accessibility option. Once I remember where it's at I will post again
thethruth said:
You have to turn on an accessibility option. Once I remember where it's at I will post again
Click to expand...
Click to collapse
And then you turn on switch access but it doesn't make the system run as smoothly for some reason. I want the beep as well but I had to eventually turn the option off. Try it out. Don't see if you like it
thethruth said:
And then you turn on switch access but it doesn't make the system run as smoothly for some reason. I want the beep as well but I had to eventually turn the option off. Try it out. Don't see if you like it
Click to expand...
Click to collapse
Thanks for pointing me to this. Like you said, I don't like it at all! I even not giving enough time to see if it would affect how the system runs but getting an accessibility slider when volume button is pressed when "Switch Access" is turned on already make me hate it. I couldn't find a thing how this accessibility slider is doing but definitely don't want it to appear whenever I press the volume button.
I never turn on anything in Accessibility menu, always leave it as default. This seems to be a A13 thing as I remember that the Assistant has the beep when I was on A12. Anyway, I will try to make myself get used to this behavior.