Google Now Hot keyword "okay google" not working when talkback accessibility service is enabled

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Turn on talkback, two, enabled the hot word detection in google now.  Now 
when talkback is running and google now is active say "okay google".
2. If you say "okay Google" nothing happens.
3. Now, suspend talkback in the global context menu, tap your mic button, ask 
google a question and when you say okay google again it works while talkback is 
suspended.

What is the expected output? What do you see instead?
I am expecting to tap google search, say "okay Google" hear the chime and ask 
it a question all with out touching my screen.  At this time,  nothing is 
happening I have to use the mic button to get Google now's attention.

What version of the product are you using? On what operating system?
Nexus5 kitcat 4.4.2

Please provide any additional information below.
I would hope someone emails me back at danny.mathis@gmail.com

Original issue reported on code.google.com by danny.ma...@gmail.com on 9 May 2014 at 7:29

[GoogleCodeExporter]

Talk back & OK Google are needed for accessibility.  Enabling talkback turns 
the microphone symbol to a hollow icon, OK Google does not work.  Disabling 
talkback turns the microphone symbol to a solid icon and OK Google works as 
expected.  This needs to be addressed as high priority as OK Google AND talk 
back are indispensable for the blind like a family member. 

Original comment by mpet...@gmail.com on 19 Aug 2014 at 11:01

[GoogleCodeExporter]

I think this issue goes even deeper.

I have the same problem, but also an additional one.

I'm in the Google Search application, I disable talkback, tap the microphone 
icon, hear the acknowledging sound, speak my query, and hear hear the 
acceptance sound. All of a sudden, talkback starts talking (though there's no 
explore by touch or swipe navigation). Note that I haven't locked and unlocked 
the phone yet, or anything like that. It's as though I only partially disabled 
talkback in some way. When I subsequently lock and unlock the phone, everything 
returns to normal.

I'll also add that occasionally I will "get lucky". I'll tap the microphone on 
my homescreen and everythign will work perfectly without me messing with 
talkback at all. I cannot explain the intermittent behavior.

For reference, I'm using the Motorola Atrix HD with 4.1 Jellybean. 

Original comment by aohas...@gmail.com on 20 Aug 2014 at 6:36

[GoogleCodeExporter]

Its a shame that the functionality of google now and voice search are disabled 
once TalkBack is enabled. Infuriating actually. Toggling back and forth between 
the two should not be the best work around. I'm new at this. My feeling is that 
the software as it exists now cannot listen, for google voice functionality, 
and speak for the tts function. Maybe re-purpose the volume button to a listen 
now / microphone on button. My 2 cents. This could be so much better, let's 
keep working!
Peter b

Original comment by petesph...@gmail.com on 26 Dec 2014 at 7:57

[GoogleCodeExporter]

Had the same issue on xperia z2 Tab, galaxy tab, xperia z3 smartphone, and htc 
one m8. I'm not sure if there is something locking a file or it's a "feature". 
But anyway there should be added some options olfor how and where you can "okay 
Google " as a hot word,  even using talkback. 

Original comment by ManuelBa...@gmail.com on 3 Jan 2015 at 11:12

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

It's unfortunate that at the very least, a dialogue that would state the OK 
Google Feature will be disabled when talkback is running, would be shown. I'm 
curious if a phone like the Motorola Moto X, which is always listening for 
voice input, will work with accessibility enabled.

Original comment by vega...@gmail.com on 9 Mar 2015 at 5:54

[GoogleCodeExporter]

I thought the issue would've been resolved with the latest google now
update but still nothing! Google should try harder!

Original comment by starcann...@gmail.com on 9 Mar 2015 at 6:01

[GoogleCodeExporter]

It's really pity that my blind friend cannot use speech recognition due to this 
problem. 
Google talkback should shut up as soon as the speech recognition is active. 
This is really enoying 

Original comment by skaterke...@gmail.com on 18 Mar 2015 at 11:48

[GoogleCodeExporter]

I agree to all comments! Is anyone even working on it? They are making the
iPhone look better and better.

Original comment by pennymc...@gmail.com on 18 Mar 2015 at 12:58

[GoogleCodeExporter]

I read somewhere that an app called open mic worked. Has anybody tried it out?

Original comment by starcann...@gmail.com on 18 Mar 2015 at 4:32

[GoogleCodeExporter]

I tried with applications that open the microphone , but I failed ...
I'm looking for a way to use both applications ( essential for a blind person )

Original comment by rodrigo....@gmail.com on 29 May 2015 at 7:03

[GoogleCodeExporter]

I am a blind individual and I can verify what this particular person is saying. 
You must turn off audio docking which shouldn't need to be done, yet has not 
been fixed since Android 4.3 jelly bean. Space space also, and lollipop 5. 01 
okay Google is broken when talkback accessibility is enabled and also breaks 
Samsung S voice when interacting with s voice. Please fix, I really use this a 
lot. I have a Nexus 6 that is running Android 5. 1. 1 in this issue has been 
resolved, but the audio ducking has not.

Sent from Type Mail

Original comment by danny.ma...@gmail.com on 29 May 2015 at 11:06

[GoogleCodeExporter]

The problem goes even deeper than this, I have a Samsung Galxy S4 running 5.1, 
and I have learned that if talkback is on, not only does google now work, but 
all speech recognition fails.  if you try and open your mic manually, it will 
make a sound, and as you start to talk, it will instantly cut off the mic. THus 
you cannot send text messages if talkback is enabled.  You can use S-voice 
which is a Samsung provided app, as long as you manually activate the Mic, but 
it doesn't work correctly.  After entering a voice command rather than oing as 
you are telling the phone, you have to touch your screen a couple of times, and 
then it will eventually work.  

I'm an IT guy whom is vision impared, and I am personally thining about moving 
to Windows Phone 8.1 and then installing Windows 10 on it just to see if this 
works better with Cortana, because I refuse to purchase an apple product. 

Bill "Thevirus"

Original comment by Thevirus...@gmail.com on 20 Jul 2015 at 3:11