Related
So it's happened 2-3 times now since I got the phone...all of the sudden voice input stops working. I can no-longer say OK Google to open it up, and even if I open it manually and hit the search button, it doesn't record any voice at all.
The weird thing is, I can still use voice input in any keyboard location (like in SMS or Chrome), but the basic functionality doesn't work.
Anyone else have this happen?
did you by any chance use third party launcher?
gd6noob said:
did you by any chance use third party launcher?
Click to expand...
Click to collapse
Nope, stock launcher. All options for Google Now are enabled, and it works great 90% of the time, but then it just...stops. Only way to get it working again is a restart.
Hi there. I also have this problem. I have narrowed it down to MX player or chrome video player (also same issue with headphones + video). When you play a few movies and exit MX player, "OK Google" will not respond to voice commands. The only fix is to reboot your phone. I have tested this today. I played a few movies after i made sure "OK Google" was working fine and sure enough, the feature stopped working immediately after i played a couple of movies. Sometimes it will not get affected, but most of the time MX player or the integrated Chrome video player will break this function. I would like someone else to confirm this, thanks.
ps; Just tested my theory again after a phone reboot and now it seems to work fine... I have no idea wtf is going on with this feature, but when it breaks, even the search bar stops working. The whole thing just stops functioning - speech , search just stops working.
hotleadsingerguy said:
So it's happened 2-3 times now since I got the phone...all of the sudden voice input stops working. I can no-longer say OK Google to open it up, and even if I open it manually and hit the search button, it doesn't record any voice at all.
The weird thing is, I can still use voice input in any keyboard location (like in SMS or Chrome), but the basic functionality doesn't work.
Anyone else have this happen?
Click to expand...
Click to collapse
update : i have Xperia Z2
in my case it's the opposite , lol
i have my OK Google working but my voice input not , unfortunatelly anyone can help me ? pls ?
ryan42680 said:
update : i have Xperia Z2
in my case it's the opposite , lol
i have my OK Google working but my voice input not , unfortunatelly anyone can help me ? pls ?
Click to expand...
Click to collapse
Sort of. I've had a few things happen like this in the past, and I've realized there's always been a reason (sometimes it's changing settings in Android Wear that pertain to Voice support, sometimes it's switching the voice stuff on on my iPhone 6, sometimes it's changing my Google password, etc...).
The way I've always been able to fix it is just to log out of Google Now and log back in. It says it'll lose things, but it doesn't at all. Takes ~15 seconds, and it's always fixed all of my voice issues, including the one listed above and the other one where it recognizes everything and opens the Google Search...but then everything is blank.
hey, thx i got google voice input working on apps and saying ok goole works but voice input isn't working when i'm in the search bar strange haha
UPDATE: try flashing another Official Rom, gd luck
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
bambam2k3 said:
Folks,
Any help or thoughts would be much appreciated.
Running stock 4.4.2, rooted, Franco Kernel, w/ Xposed ( GravityBox ) and Tasker
Has anyone else had problems with a single button wired headset intermittently launching a classic looking voice dialer versus the new voice search stuff when using the headset's button?
I basically have a Tasker profile that unlocks and wakes my phone after I plug in my headset. This all works fine.
Problem is, when trying to actually use the headset to call someone, this classic looking (and I say that because it's a black background with white text, nothing fancy) voice dialer comes up but no matter what, can not make out what I am asking it to do.
If I hit the back button and try the headset button again, it will then sometimes go to the new voice search and work completely as expected. Not every time. Sometimes the classic dialer wants to hang around for 2 or 3 attempts.
Anyone seen this before? I was hoping to find a way to just disable this 'classic' voice dialer because I'm essentially trying to have my phone be more hands free if the headset is plugged in and know the new voice search works just fine.
Thanks,
bambam2k3
Click to expand...
Click to collapse
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
joannn said:
Could you try starting your device in safe mode and not running any apps you've installed to test if one of them is causing the problem? If you don't experience the problem while in safe mode that's a good indication that an app you've installed is the source of your issue.
I'd appreciate it if you could let me know how your safe mode test went after you get a chance to give it a try.
Click to expand...
Click to collapse
Joannn,
Thanks for the thoughts.
I tested safe mode and the classic voice dialer does not come up at all so it definitely has to be some sort of app or weird way my system is calling something when using the headset in normal mode.
I tried the following with no success in normal mode:
1) Disabled Xposed and all modules - rebooted - no change
2) Disabled tasker and tested with just plugging in the headset and testing the button - no change
3) Switched from Nova launcher back to stock launcher - no change
4) Uninstalled a headset button control app - no change
So, I'm not sure why the phone randomly thinks this old dialer is the correct one to launch, nor do I have any idea where it is coming from. It doesn't appear to be a separate app and even when I look through the system apks, I see nothing that looks like it references this classic voice dialer. Not sure what's triggering it.
--Bambam2k3
take a screenshot of your classic looking dialer and post it here.
simms22 said:
take a screenshot of your classic looking dialer and post it here.
Click to expand...
Click to collapse
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
bambam2k3 said:
Hey Simms,
Here is a screenshot of the voice dialer window.
--Bambam2k3
Click to expand...
Click to collapse
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
simms22 said:
thats not a google app. its especially obvious since "dialler" is spelled wrong. thats a third party app.
Click to expand...
Click to collapse
Holy hell, Simms, I did NOT even notice that.
Marvelous. Now to find out what app installed this crap...
--bambam2k3
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
simms22 said:
instead of looking in your app drawer, since apps dont always get put there, open the phones main settings, apps, and look there.
Click to expand...
Click to collapse
I've got to assume it's something related to Tasker or the Secure Settings plugin for it. I uninstalled every single app I could think of that may have had the ability to make any calls of any nature, and in Settings>Apps I don't see the Voice Dialler at all, even before I started uninstalling things.
Without Tasker being used, I haven't seen the bad dialer come back again.
Was really only using tasker to get around the fact that the headset button is ignored if the phone is pin locked. Guess I'll try and find another way around it.
Thanks for your help,
bambam2k3
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
bambam2k3 said:
Okay, I'm going to take that back.
It's got to be stock somehow. I read some other posts and a quick google image search shows other people with the same dialer, especially when using bluetooth headsets from the lockscreen. I've pretty much removed everything from my phone aside from the stock apps. In the varying posts I've seen, the spelling is incorrect in 50% of them, and I don't know maybe if that has something to do with the language settings of the phone.
I also tested a bluetooth headset that had never been paired with my phone before and when the phone is locked, I get the odd dialer, when it's unlocked, I get the proper google voice search.
My next step would be to completely wipe and reinstall. But, I think I'm going to keep trying to figure this out before going to that length.
--bambam2k3
Click to expand...
Click to collapse
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
simms22 said:
the spelling incorrect is not google. and if it was google, it would be spelled incorrect for all, not 50% of the people. the next question is do you have a mod for your lockscreen? whatever it is, it is not googles app that you screenshoted. and you wrote that in safemode, it didnt appear. which also indicates that its a 3rd party app.
Click to expand...
Click to collapse
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
bambam2k3 said:
Simms,
Figured out the 'spelling mistake'. Since I'm Canadian, I was running my phone in English (UK) versus English (US). When I changed it back to English (US), now Dialer is spelled correctly.
As for lockscreen mods, I do have GravityBox running with some Lockscreen tweaks, but in my previous testing, I totally shutdown Xposed. That's all I've got. Had the same problem with it totally disabled.
Just came across this post on Android Police with a lot of comments with the exact same problem I'm having. Seems even with using Tasker and Secure Settings to disable Pin lock, turn off keyguard, wake the device and take it to the homescreen, the phone still thinks the screen is 'off' and brings up the old dialer.
http://www.androidpolice.com/2014/02/10/neat-google-search-v3-2-finally-enabled-google-voice-search-instead-of-the-old-voice-dialer-with-bluetooth-headsets/
Bambam2k3
Click to expand...
Click to collapse
so it seams then that you either need to update your google search or you are using a samsung device and not a nexus 5.
...and other times I just get a "beep" where I can say Call John. I'd prefer one or the other - more specifically the latter. Can anyone shine a light on this? I am thinking that it has something to do with Swype/Dragon vs. Google's version, but how can I disable one and still keep the other features?
If anyone knows, thanks in advance!! Been bugging me for a long time....
Sorry to ask again, but can anyone confirm this issue or even better, make a suggestion on how to fix it? The only thing I didn't mention in the original post was that I'm using a wired headset where I push and hold the button on it.
ShermCraig said:
...and other times I just get a "beep" where I can say Call John. I'd prefer one or the other - more specifically the latter. Can anyone shine a light on this? I am thinking that it has something to do with Swype/Dragon vs. Google's version, but how can I disable one and still keep the other features?
If anyone knows, thanks in advance!! Been bugging me for a long time....
Click to expand...
Click to collapse
I can confirm that something has been recently "pushed" down to our phones. I used to get "Say Call, followed by name or number" when using a long-press on a BT headset(plantronics). I now simply get the beep.
Also, it now seems to be a *requirement* for google to have your contacts, as it now tells me "Sure, but when its safe, please unlock your phone and enable device information" when I try to make a call. Bummer. I liked the local "lookup" mode and really don't want all my phone numbers linked to my google account. I tried downgrading "google play services", but it goes to the factory version which is way too old... it seems more difficult if you just want to go back a few months, not to the original version installed on your phone.
I just noticed that my phone will not recognize the "OK Google" Command. I've tried trainging it by saying "OK Google" 3 tims but even then, the phone does hear me. It will hear me and recognize my words ok if i press the microphone button first and then speak. Anyone else have the same issue?
brandypuff said:
I just noticed that my phone will not recognize the "OK Google" Command. I've tried trainging it by saying "OK Google" 3 tims but even then, the phone does hear me. It will hear me and recognize my words ok if i press the microphone button first and then speak. Anyone else have the same issue?
Click to expand...
Click to collapse
Nop, works for me even on BT. Maybe you have it disabled?
so what should I do? under the screen "OK Google" detection, it shows, From the Google App=on, but the other options are greyed out. When I turn on From Any Screen, it asks me to Just say OK Google three times, and it's listening, but it never recognizes my voice even if I say it 100 times. But, I can do a voice search OK in I manually click the google microphone button.
I have the same problem. Recently bought an Idol 3 5.5, and cannot get 'OK Google' to work. Any amount of 'OK Google' commands in different accents (and by different people) are useless. I can do voice search by clicking the microphone button on Google search app. Not sure what is the problem here. How do I make sure this feature is not disabled on my phone?
Same issue here as well. It "will" work if you open the Google App first. It then recognizes commands without having to select the microphone. But yes, without first opening the google app, it does not work.
you have to add english as primary language in google settings (beside the language you use). Works for me (i am from Europe). It also works from any screen.
There is something wrong with it on the Idol 3. If you boot into safe mode, you can enable it but only from safe mode. I did this and it workd for awhile but then something disabled it again. Very Frustrating. Unfortunately, I doubt we will get any fixes from Alcatel. BTW, to boot into safe mode, press the power button and then long press on either restart or power off. I can't remember which.
like i said it works well on my and many other devices, so you have to set it right.
DallasCZ said:
you have to add english as primary language in google settings (beside the language you use). Works for me (i am from Europe). It also works from any screen.
Click to expand...
Click to collapse
Yes, it works from any screen as long as you have "previously" opened the "Google App", and, it's still running in the background.
For instance, if I cycle my phones power, and come to the home screen, "Ok Google" will not work, it simply doesn't work. But, if I open the "Google App" after a reboot, and then go back to my home screen, or any screen, it will work. You have to open that "Google App" first, or it doesn't recognize any command, because it's not "listening" / running in the background. If I "close" all running apps, which you should be doing quite often, "Ok Google" will not work, until I again open that "Google App".
The phone should "Always" be listening (provided you want to use this feature), without the need to run the "Google App" first, but that's simply not the case. To me it's just poor implementation, because it forces you to always make sure the "Google App" is running, or hit the microphone. This shouldn't be necessary. It should just work from the moment the phone has booted up (again, if you want this feature), but it doesn't.
Better implementation would have been a "service" you either turn on, or off, under settings, so it's always running (from the moment the phones powered up), or it's not running.
I hope that's clear, and makes sense?
Makes sense that that's what happening to me as well. I recall it worked just fine previously. I wonder if the recent updates did something to that interface.
I'm having the same problem after doing a factory reset and reloading everything.
It was working fine before the reset and since it will only work if I've recently opened the Google app. I've checked all of the settings multiple times, uninstalled/reinstalled the Google app, and it's still occurring.
Has anyone found any possible solutions?
(Not sure if this is anyhow related, but before the reset the flip to mute and snooze gestures didn't work at all. Since the reset, they work perfectly.)
Ok So pretty simple request. I want to activate "Ok Google" using the home button just like S Voice or Siri behaves. With Google set as the Device Assistance App a long press of the home button pulls up the google app, then I have to click the mic button. Or I have to activate it by saying "Ok Google" which is super annoying. I've searched everywhere for a solution and the only thing I found was the following:
https://www.reddit.com/r/AndroidQue...t_possible_to_activate_ok_google_with_a_home/
Which doesn't work at all on the S7. A long press of the home button opens the Launcher App which asks me to select google. Basically adding a 3rd step.
I'd appreciate any help!
I use the Google Now Launcher and I had that ability. I will have to play around with my settings to get it back because I installed Labs so when I hold my home button down it waits for me to say a contact name and it calls them. I will have to get back with you on that when I can get access to my phone.
Ok, maybe the new version of the launcher doesn't support that. Now long press doesn't do voice search, it instead shows Now on Tap, but different than what I remember.
Outbreak444 said:
Ok, maybe the new version of the launcher doesn't support that. Now long press doesn't do voice search, it instead shows Now on Tap, but different than what I remember.
Click to expand...
Click to collapse
Yup.. I still haven't found a workaround. Having the mic always on to detect "OK Google" seems to be a waste of battery.
Hopefully a solution comes up. Thanks for trying.
H3lipil0t said:
Yup.. I still haven't found a workaround. Having the mic always on to detect "OK Google" seems to be a waste of battery.
Hopefully a solution comes up. Thanks for trying.
Click to expand...
Click to collapse
I have found a solution that works great! I just tested it myself.
Download this app here:
https://play.google.com/store/apps/details?id=com.dynamicg.homebuttonlauncher&hl=en
You'll want to open it up, select the 3 dots, and then select add.
Add Voice Search, then do the same steps but remove whatever else was there by default.
Now if you're on marshmallow, which I assume you are, then you'll need to go to Settings -> Applications -> Default Applications -> Phone assistance app
And change it to Home Launcher
Give that a try and let me know if that works for you.
Outbreak444 said:
I have found a solution that works great! I just tested it myself.
Download this app here:
https://play.google.com/store/apps/details?id=com.dynamicg.homebuttonlauncher&hl=en
You'll want to open it up, select the 3 dots, and then select add.
Add Voice Search, then do the same steps but remove whatever else was there by default.
Now if you're on marshmallow, which I assume you are, then you'll need to go to Settings -> Applications -> Default Applications -> Phone assistance app
And change it to Home Launcher
Give that a try and let me know if that works for you.
Click to expand...
Click to collapse
You are the man!!!! This worked.. "Auto Start mode" had to also be selected but this finally got the job done.
It wasn't perfect at first. for some reason the responses to my questions where not audible.
For Example.. If I held the home button, the voice prompt shows up and I say "What's my next appointment?". It displayed the calendar item but didn't read back the result. If I activated it saying "OK Google" and asked the same question, I was shown the response and it read back to me. "You're next calendar entry is tomorrow at 7am...".
I tried it again a few more times. Now it seems to be working properly with the home button.
You've made my day. Wish I could buy you a pint of beer remotely.
Cheers!
A simple thanks is plenty, I've got all the beer I need in my fridge. Lol
Was looking for a solution as well. Works great. Thanks.