Hi. I never found an answer to this and haven't been able to get it to work.
I'm on Cyanogen 10.2 latest nightly build and when I speak after hitting the goggle search mic. It never does anything. Even when trying to send a text hitting the mic button.
Is it supposed to work with 4.3?
coresare said:
Hi. I never found an answer to this and haven't been able to get it to work.
I'm on Cyanogen 10.2 latest nightly build and when I speak after hitting the goggle search mic. It never does anything. Even when trying to send a text hitting the mic button.
Is it supposed to work with 4.3?
Click to expand...
Click to collapse
That definitely should work. I'm on the GPe 4.3 build and it works flawlessly for me. In fact I side loaded the Kit Kat launcher apk so the "Ok, Google" activation even works on the home screen. Something else is wrong. Does the mic work in calls or when using a voice recording app? That would be the first thing that I would look at.
ptdarkness said:
That definitely should work. I'm on the GPe 4.3 build and it works flawlessly for me. In fact I side loaded the Kit Kat launcher apk so the "Ok, Google" activation even works on the home screen. Something else is wrong. Does the mic work in calls or when using a voice recording app? That would be the first thing that I would look at.
Click to expand...
Click to collapse
Strangely enough I can see the speaker icon pulsate when I speak into it like its detecting the sound but nothing happens. Every other function works fine. Before when I took video with my phone the volume was very low but it was fixed with a later cyanogen nightly. I've tried uninstalling Google search and reinstalling with no luck.
Related
Anyone got same issue with Google voice search under Alpha 3
no problem here. searching name or phrases. what can you not search?
nomadman said:
no problem here. searching name or phrases. what can you not search?
Click to expand...
Click to collapse
I have setting up as English(us), whatever I say, the result always is "mmm"
I have try recording voice at Webos, it is OK, but not working at android !
Have you tried voice search on another device? Reason I ask is last year I had issues with voice search returning jibberish when I used it, problem was with the voice data they collected getting screwed up online. If voice search fails on another device that's most likely the cause. You can clear the data in your Google account.
i think i might have misunderstood you. I use the actual google voice app for texting and I can search fine. there is another app call Voice Search which is completely different.
In any case, Voice Search app does not recognize that I say.
kitsunisan said:
Have you tried voice search on another device? Reason I ask is last year I had issues with voice search returning jibberish when I used it, problem was with the voice data they collected getting screwed up online. If voice search fails on another device that's most likely the cause. You can clear the data in your Google account.
Click to expand...
Click to collapse
I have not problem on my HTC mobile phone!
What do mean clear data on my Google account? It is remove Google account on touchpad!?
nomadman said:
i think i might have misunderstood you. I use the actual google voice app for texting and I can search fine. there is another app call Voice Search which is completely different.
In any case, Voice Search app does not recognize that I say.
Click to expand...
Click to collapse
I am using actual Google voice search app which is downloan from android market!
It is I am only one got problem on Google vice search with Alpha 3 ?
i just tried it. its not working for me either.
The Jack of Clubs said:
i just tried it. its not working for me either.
Click to expand...
Click to collapse
Good to hear that I am not alone !
have you try using "Sound Recorder" app from Alpha 3, It is not working for me as well, the sound record got abnormal playback. the sound record only work on WebOS ! Sad.....
Google voice search from the market does not work for me either, but.... the mic button on smart keyboard pro does work. It works pretty good, especially if you talk directly into the top of the touchpad where the mic is. Just thought I'd let you guys know. FWIW the voice recording app ALSO works for me. it sounds a bit muffled, but it does record and playback legibly.
vinscuzzy said:
Google voice search from the market does not work for me either, but.... the mic button on smart keyboard pro does work. It works pretty good, especially if you talk directly into the top of the touchpad where the mic is. Just thought I'd let you guys know. FWIW the voice recording app ALSO works for me. it sounds a bit muffled, but it does record and playback legibly.
Click to expand...
Click to collapse
I have try smart keyboard, it not working for me, the result is same, whatever I say, the result always is "mmm"
ok so google now has updated to allow voice search over bluetooth headset which DOES work...or for me anyways,. HOWEVER
we still have the same ol' problem of being not able to "push bluetooth headset button" to open google now .
or shall i say i cant find a way, has anyone else had success with this?
so far ive tried disabling s-voice in apps menu, and now it goes to google voice dial,
i cannot disable voice dial.,
ive also tried using the "bluetooth launch" app from market to no response,
any help would be majorly appreciated
update:
ive now gotten google now to come up from bluetooth button push, however seems googlenow just freezes once opened, still works fine from widget microphone press just not from BT,
this post from another site helped
1
down vote
I'm not sure if this is true for other phones listed above, but for The Galaxy Note II, I had to make sure S-Voice was disabled (it says Voice Dialer on the first post).
Also, if you have downloaded bluetooth launcher you probably already tried:
"Google Search" and then selected "com.google.android.googlequicksearchbox.VoiceSearchActivity"
and was still launching S-Voice. Once you disable S Voice (note the space) go into Settings > Application manager and scroll to the right to ALL. Then find S Voice and disable it.
Once you disable it and hit the button on the paired bluetooth device, you will get a "Complete Action Using" dialog. Resist the temptation to choose Google search. I know it's the logical choice, however you will not get Google Now; you will get a Google voice dialer instead. So make sure you choose "Bluetooth Launch" and select ALWAYS. Now when you hit the bluetooth button, you should get Google Now.
soooo, no progress
still stuck at getting the microphone to actualy work when google now is accessed.
i see a thanks from member "exitcode1" did you have any better luck ?
Oops
chismay said:
soooo, no progress
still stuck at getting the microphone to actualy work when google now is accessed.
i see a thanks from member "exitcode1" did you have any better luck ?
Click to expand...
Click to collapse
My mistake... activating Now from bluetooth worked so well I just assumed the whole process would work, but the phone mic was actually hearing me from inside my bag, not the BT mic.
exitcode1 said:
My mistake... activating Now from bluetooth worked so well I just assumed the whole process would work, but the phone mic was actually hearing me from inside my bag, not the BT mic.
Click to expand...
Click to collapse
Is that even with the google now setting enabled to listen to google now voice searches via bluetooth when bluetooth device is connected???
I had to select the box to enable blutooth mic in Google now, then it worked. I still have to hit my bt button a few times the first time I use it.
Sent from my HTC One using xda app-developers app
Did you ever figure out how to fix this issue? I want Google Now to pop up when I press my bluetooth button on my headset. I'm currently running 4.1 on my DNA (About to me 4.2.2 in about 20 minutes)
zookkz said:
Did you ever figure out how to fix this issue? I want Google Now to pop up when I press my bluetooth button on my headset. I'm currently running 4.1 on my DNA (About to me 4.2.2 in about 20 minutes)
Click to expand...
Click to collapse
open btlaunch
click the googlesearch dropdown
select the third one down "on my phone" com.......googlesearchvoiceactivity
go to s-voice and disable the home button shortcut
profit./
chismay said:
open btlaunch
click the googlesearch dropdown
select the third one down "on my phone" com.......googlesearchvoiceactivity
go to s-voice and disable the home button shortcut
profit./
Click to expand...
Click to collapse
I don't have a samsung phone. But I'll try using this method and see what happens.
Got mine working with HTC One, maximushd 30, kk 4.4 and a 2014 bmw.
Used bluetooth launch and chose voicesearchactivity under google search.
Also I made sure bluetooth headset was checked on in google now-settings-voice.
Sent from my HTC One using XDA Premium 4 mobile app
Hi. I'm using an HTC one X but still can't get the mic to listen after using bluetooth launcher to at vote Google now when the phone is locked. Any ideas from the HTC users here who have this working?
Sent from my HTC One X using XDA Free mobile app
Since the OTA Kitkat (4.4.2) update of my stock Verizon Galaxy S4 (SCH-i545), when I use the voice-to-text microphone button (Google voice typing) on the stock Samsung keyboard, it does not pause music played by Play Music or Pandora as it used to. I've been through troubleshooting with Samsung and VZW Support, including:
- Clearing cache for S Voice, Google Voice, Samsung Keyboard
- Testing in Safe Mode
- Performing a hard reset of the device
The music pauses for half a second and resumes with the mic active... not cool when listening to music and want to use voice to answer a text message.
VZW last said they want to discuss replacing the phone, but before I go down that rabbit hole, does anyone have any ideas on what to check or change to fix this?
The same thing happened to me. This used to work fine. My guess is it's software related. Replacing the entire phone seems like overkill.
Let's troubleshoot further. I'll keep you updated on anything I try, and obviously if anything fixes it.
EDIT: Found your follow-up thread here. Seems like an update to Google Search was the culprit.
sweeds said:
The same thing happened to me. This used to work fine. My guess is it's software related. Replacing the entire phone seems like overkill.
Let's troubleshoot further. I'll keep you updated on anything I try, and obviously if anything fixes it.
EDIT: Found your follow-up thread here. Seems like an update to Google Search was the culprit.
Click to expand...
Click to collapse
Anyone find a resolution for this? I have same issue on Galaxy S4 I337M (Canada), both stock and custom ROMs using 4.4.2.
BlindDroid said:
Anyone find a resolution for this? I have same issue on Galaxy S4 I337M (Canada), both stock and custom ROMs using 4.4.2.
Click to expand...
Click to collapse
Follow that thread; bottom of first page. The problem was an update to Google Search (and thus Google Voice input). Current solution is to downgrade to older version, link in that other thread.
Sent from my SCH-I545 using Tapatalk
sweeds said:
Follow that thread; bottom of first page. The problem was an update to Google Search (and thus Google Voice input). Current solution is to downgrade to older version, link in that other thread.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Thank you very much.
I had this issue where i sounded like a mouse and you could not understand what i was saying on the other end of a hangouts call. I tried everything to resolve it and it turned out to be the google now (search) settings ok google hotword detection allowing ok google to work from any screen. No clue why, as my sons galaxy nexus has the same setting and it works fine.
Just wanted to post in case anyone else ran into this.
JewRican said:
I had this issue where i sounded like a mouse and you could not understand what i was saying on the other end of a hangouts call. I tried everything to resolve it and it turned out to be the google now (search) settings ok google hotword detection allowing ok google to work from any screen. No clue why, as my sons galaxy nexus has the same setting and it works fine.
Just wanted to post in case anyone else ran into this.
Click to expand...
Click to collapse
I'm going to have to try this out. Me and my wife are having this same exact issue where I sound like a robot.
JewRican said:
I had this issue where i sounded like a mouse and you could not understand what i was saying on the other end of a hangouts call. I tried everything to resolve it and it turned out to be the google now (search) settings ok google hotword detection allowing ok google to work from any screen. No clue why, as my sons galaxy nexus has the same setting and it works fine.
Just wanted to post in case anyone else ran into this.
Click to expand...
Click to collapse
I have the same problem, but still trying to figure out a solution
dgmoodey said:
I have the same problem, but still trying to figure out a solution
Click to expand...
Click to collapse
so did you try disabling the setting that I posted?
workaround
But what if one wants to have the ok google functionality turned on? Isn't this issue/bug supposed to be addressed by samsung?
MimKoRn said:
But what if one wants to have the ok google functionality turned on? Isn't this issue/bug supposed to be addressed by samsung?
Click to expand...
Click to collapse
Sure is, but who knows when that will happen
http://forum.xda-developers.com/galaxy-s4-verizon/help/video-call-audio-kit-kit-upgrade-t2856743
I started a whole other thread on this.
Is not just a Hangouts issue, but it's a Skype and any other video chat issue.
Are you guys on 4.4? This might be it, but since hot word detection on any page was a Kit Kat function.
I tried turning off Google Now, but but I didn't turn off the hot word on any page function. I'll try it and let you know if it's the issue.
JewRican said:
I had this issue where i sounded like a mouse and you could not understand what i was saying on the other end of a hangouts call. I tried everything to resolve it and it turned out to be the google now (search) settings ok google hotword detection allowing ok google to work from any screen. No clue why, as my sons galaxy nexus has the same setting and it works fine.
Just wanted to post in case anyone else ran into this.
Click to expand...
Click to collapse
Thank you sir. After a week and a half of trouble shooting, you found the answer.
The problem is indeed, and Google Search's new "anytime /any screen" hotword section function..
Go to Google Search, Settings, Voice, Uncheck hotword detection from any screen.
Why this breaks the wifi audio when using a video chat service is a mystery.
I now realize that this wasn't an issue under 4.3, because Hotword detection from any screen is a Kitkat only feature.
I don't know if this a Samsung, possibly or Google Search issue. But I'll submit a ticket to Google under in the play store.
Hopefully, everyone else will too.
I'm on the galaxy s4 from tmobile. I was also having this problem, but I turned off the hotword from any screen and it worked. I first noticed this trying to make a google voice call from hangouts, which is audio only, but it did it with video chats as well. I'll definitely report this.
Thanks for figuring it out!
Delete
I can also verify that this fix works. I'm going home for Thanksgiving & we wanted to set it up so the gf and stepson can video chat with me while I'm gone. She was trying to set it up on her PC & having issues, which I've never even tried.
I asked her why she didn't just use her phone like a normal person & she said she'd tried it with her mom & had the high pitched noise. We tried it & confirmed & a Google search brought me here.
I disabled hotword detection from any screen & it went away (she doesn't use it all the time like I do).
This is weird though, because this is the vzw s4 that I used to video with her on her s3 thriugh hangouts before & I've had Google now set to detect from any screen since I could.
Not that I think it matters, but her mom has an s5 & I assume she's got hotword detection off. I'm on the Note 4 & have it on with no issue.
I know the OP is a little old, but I'm wondering if the latest OTA for the s4 has something do to with it? I swear I videoed her from the s4 with detection on.
In any case, after my long rambling, thanks for posting the fix!
Sent from my Note 4
Jonny Kansas said:
I can also verify that this fix works. I'm going home for Thanksgiving & we wanted to set it up so the gf and stepson can video chat with me while I'm gone. She was trying to set it up on her PC & having issues, which I've never even tried.
I asked her why she didn't just use her phone like a normal person & she said she'd tried it with her mom & had the high pitched noise. We tried it & confirmed & a Google search brought me here.
I disabled hotword detection from any screen & it went away (she doesn't use it all the time like I do).
This is weird though, because this is the vzw s4 that I used to video with her on her s3 thriugh hangouts before & I've had Google now set to detect from any screen since I could.
Not that I think it matters, but her mom has an s5 & I assume she's got hotword detection off. I'm on the Note 4 & have it on with no issue.
I know the OP is a little old, but I'm wondering if the latest OTA for the s4 has something do to with it? I swear I videoed her from the s4 with detection on.
In any case, after my long rambling, thanks for posting the fix!
Sent from my Note 4
Click to expand...
Click to collapse
Its strictly a kit Kat 4.4 issue. That Google has dropped a serious ball on. But they can care less now, since they are on to lollipop 5.0
Maybe it will be fixed in 5.0
Looks like the issue wasn't fixed in Lollipop either. I'm running Dan's GPE ROM, and I had to disable any-screen hotword detection to return the normal voice.
Ever since I updated to Lineage 14.1, I have not been able to get either Android Keyboard AOSP or Gboard to work with "Voice to Text Typing"
With Android Keyboard AOSP, there is a microphone on the right next to word suggestion, but nothing happens when you click it.
With Gboard, no matter what setting I choose, there is never a button or microphone to hit to use Voice to Text in any way.
Anyone have any ideas ?
lunaris242 said:
Ever since I updated to Lineage 14.1, I have not been able to get either Android Keyboard AOSP or Gboard to work with "Voice to Text Typing"
With Android Keyboard AOSP, there is a microphone on the right next to word suggestion, but nothing happens when you click it.
With Gboard, no matter what setting I choose, there is never a button or microphone to hit to use Voice to Text in any way.
Anyone have any ideas ?
Click to expand...
Click to collapse
The funny thing is that now I am using Lineage 14.1 and now mine is working, but when using Candy 14.1 I have been unable to use it for a long time.
Well that is nuts, when I was using Candy 14.1 I had no problem with Voice to Text. . . there has to be some other forces at work here.
I managed to install "Multiling keyboard" and get it to work, but none of the other keyboards do. . . just weird.
I have Google and Google Voice Search installed and working.
If anyone has a fix or knows more, let me know. Thanks !!
With Android Keyboard AOSP, there is a microphone on the right next to word suggestion, but nothing happens when you click it.
Click to expand...
Click to collapse
Same problem on my device, HTC One M9 with LOs 14.1. Does anyone have a solution or workaround?