Database Info

google now always listening stopped work?

My google now hot work detection stopped work for some reason, even tho I have hot work enabled thru google now and the language is English (US). You can see my google voice mic in the google search bar is hollow. Anyone know a fix for it? I tried rebooting the phone and it didn't help.
https://www.dropbox.com/s/u4bgk8j8ni186u0/Screenshot_2013-11-13-23-41-01.png

bluesfear said:
My google now hot work detection stopped work for some reason, even tho I have hot work enabled thru google now and the language is English (US). You can see my google voice mic in the google search bar is hollow. Anyone know a fix for it? I tried rebooting the phone and it didn't help.
https://www.dropbox.com/s/u4bgk8j8ni186u0/Screenshot_2013-11-13-23-41-01.png
Click to expand...
Click to collapse
Scroll over to Google Now and head to settings and look inside the Voice category.
See if Hotword Detection is on or not. If not, turn it on and that should do the trick!
If it IS on though, try giving it a toggle.

it is checked. I gave it a toggle it still doesn't work...

It likes to stop working for me too.
I found that putting in headphones tends to disable the hotword.
Try plugging in headphones, unplugging them, then screen off, and screen on.

I found the problem. It was pushbullet. Whenever I have that installed it disabled my always listening hot word detection. Not sure why.
Sent from my Nexus 5 using Tapatalk

[Q] Odd classic voice dialer intermittently when using wired headset

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.

Is Smart Lock (Lollipop) working for you consistently?

Upgraded my N5 to its Lollipop Factory Image, and setup Smart Lock to work with my Moto 360. I'm noticing that my N5 will still prompt me for a passcode half the time, even though my moto 360 shows it's still connected (I can even PROVE it's connected, by doing an "Ok Google" voice search). I even set up face unlock to give it another unlock method, and that didn't seem to increase the success rate for Smart Unlock. It seems that no matter what, smart unlock doesn't work for me a lot of the time. To be more specific, it seems like it doesn't work if I haven't used the phone in awhile. Once I put my passcode in, smart lock seems to work just fine for awhile, but eventually it will stop working again, forcing me to enter my passcode to jumpstart it again.
Anyone else experiencing this?

Yes, this seems to be what I'm experiencing as well.

Same here... really want this to work. I assumed it might be because I dirty flashed, are you running a clean install?

same here...
Same here with a nexus 9. Tried connecting it to a moto and to my nexus 5. The units ARE connected to the nexus9 but in smartlock they have status "not connected". After setting up it works until the units are out of reach for the first time....after that it is back to pincode
jt3 said:
Upgraded my N5 to its Lollipop Factory Image, and setup Smart Lock to work with my Moto 360. I'm noticing that my N5 will still prompt me for a passcode half the time, even though my moto 360 shows it's still connected (I can even PROVE it's connected, by doing an "Ok Google" voice search). I even set up face unlock to give it another unlock method, and that didn't seem to increase the success rate for Smart Unlock. It seems that no matter what, smart unlock doesn't work for me a lot of the time. To be more specific, it seems like it doesn't work if I haven't used the phone in awhile. Once I put my passcode in, smart lock seems to work just fine for awhile, but eventually it will stop working again, forcing me to enter my passcode to jumpstart it again.
Anyone else experiencing this?
Click to expand...
Click to collapse

got no problem at all since N5 is paired with my LG G watch.
Got problems making NFC tag work. I have a NFC sticker at home, i use it with this app https://play.google.com/store/apps/details?id=com.jwsoft.nfcactionlauncher&hl=en making toggle wifi when i enter home (wifi on) and when i walk out (wifi off). I tried to use the same tag for smart unlock, but it simply doesn't works. Tag writing seems to be ok but still have to enter the pin when i pass my phone over it. Should i use another tag?

Mine works but RARELY
Sent from my Nexus 5 using XDA Premium 4 mobile app

Well, I figured out my issue anyway. It seems it's Gravity Screen. I use it to turn off my screen when I put the phone in my pocket (and turn it back on when I take it out). Because of this, I rarely touch the power button anymore. Apparently, when Gravity Screen locks the device, it REALLY locks it, making it so that Smart Lock can't unlock it, and forcing you to enter a passcode. I've left a note in the dev's thread, asking for a fix, but for now, I had to disable that feature.
Now, Smart Lock is working almost all of the time. I still have the occasional need to enter a passcode (like after rebooting), but for the most part, this fixed my issue.
I guess the tl;dr of all this is to make sure you don't have any apps running that lock or power-off your screen. They may be interfering.

jt3 said:
Well, I figured out my issue anyway. It seems it's Gravity Screen. I use it to turn off my screen when I put the phone in my pocket (and turn it back on when I take it out). Because of this, I rarely touch the power button anymore. Apparently, when Gravity Screen locks the device, it REALLY locks it, making it so that Smart Lock can't unlock it, and forcing you to enter a passcode. I've left a note in the dev's thread, asking for a fix, but for now, I had to disable that feature.
Now, Smart Lock is working almost all of the time. I still have the occasional need to enter a passcode (like after rebooting), but for the most part, this fixed my issue.
I guess the tl;dr of all this is to make sure you don't have any apps running that lock or power-off your screen. They may be interfering.
Click to expand...
Click to collapse
I don't use Gravity Screen, but have it installed. Could that cause the problem? I'm currently on 5.1 Cataclysm on my Nexus 5.
I have added Moto 360 as a trusted device. The moment I add it i'm able to unlock without PIN. However, after a few minutes, although the watch is connected, smart lock doesn't seem to work. I had this issue on stock Android 5.0 (no root or bootloader unlock) also with a Sony bluetooth headphones!

My smart lock "trusted places" is not working. I am assuming it is associated with the recent update to the Google Play Services for the "on body detection."
My Google Play Services has been sucking up my battery usage when location services is on. Other users have been experiencing the same issues. Some fixes suggest turning the smart features off then back and another is reinstalling the Google play services (revert then update again.)
I side loaded my Google Play Services but it didn't fix the problem. I am still looking for a fix so trusted places will work.
Sent from my Nexus 5 using Tapatalk

chrisinsocalif said:
My smart lock "trusted places" is not working. I am assuming it is associated with the recent update to the Google Play Services for the "on body detection."
My Google Play Services has been sucking up my battery usage when location services is on. Other users have been experiencing the same issues. Some fixes suggest turning the smart features off then back and another is reinstalling the Google play services (revert then update again.)
I side loaded my Google Play Services but it didn't fix the problem. I am still looking for a fix so trusted places will work.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Having absolutely the same problem. The "on body detection" feature works perfectly, howeve, the "trusted places" - almost never. I find myself entering my PIN at home every time I want to unlock the device, except for the times I slide it out of my pocket. If Google fixes these problems, Smart Lock would be my favourite feature!

I've pretty much given up on Smart Location Unlock. It's been broken for weeks now. I'm on CM12 and made profiles to disable pin/password/pattern when connected to my home Wi-Fi.

OK Google - Doesn't work

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 Google" on Always on Display when charging

Hi,
I'm wondering if someone else is having that issue:
I have my phone set up on a wireless charger and it's charging as I know that "Ok Google" only works when the phone is charging.
Also I've set up Google Assistant to launch when saying "Ok Google" and it works fine when the phone is awake.
When the phone is at the Always on Display however and I say "Ok Google" it ends up vibrating, showing a bubble for a new notification, the screen edges are "glowing" as if it's listening but if I say something nothing happens.
As soon as I then wake the phone it executes the command immediatly.
In some very rare cases it seems to work and Google seems to respond directly but it's not waking the phone and stays at the Always on Display.
And in some cases it's not even reacting to "Ok Google" at all.
Any idea what might cause this?
Is this a bug?

Try this-
I'm guessing you have a lock screen set up? Try turning on Trusted Voice in the voice settings for assistant, or delete and retrain the voice model if it's already on. If that doesn't work try disabling the lock screen entirely and see how it does.
:good:

Thanks. However that's not the problem. I turned off the lock screen completly and just used swipe to unlock and it still is the same.
The always on display is not turned off with "ok google" when it does respond and often it doesn't respond at all.
It also doesn't make the sound that it's listening when the AOD is on.
If you're lucky it responds, if not it will most of the time respond once you activate the display.
Feels very strange and buggy.
EDIT: I found out what the problem seems to be!
I have enabled "Edge Lighting" (Settings → Display → Edge screen) which makes the edge glow when a new notification arrives. However that also seems to prevent the screen from turning on when saying "ok google"! Once I disabled Edge lighting it works as expected! As you can disable edge lighting per App I disabled it for the Google app and now everything is fine again!

Thank you so much! Edge lighting really was the problem for me too!

whitepaw said:
EDIT: I found out what the problem seems to be!
I have enabled "Edge Lighting" (Settings → Display → Edge screen) which makes the edge glow when a new notification arrives. However that also seems to prevent the screen from turning on when saying "ok google"! Once I disabled Edge lighting it works as expected! As you can disable edge lighting per App I disabled it for the Google app and now everything is fine again!
Click to expand...
Click to collapse
Does ok Google work with AOD now with edge lighting off?
Mine only works when plugged in when screen is off
Sent from my SM-G955W using Tapatalk

I can't get it working even with your suggestions

angka8 said:
I can't get it working even with your suggestions
Click to expand...
Click to collapse
I think they are talking about ok Google working with screen off but charging....
It works if charger is connected but not without the charger connected.
This has been a problem with Touchwiz.
Sent from my SM-G955W using Tapatalk

Oh thanks. That is bad. But they sound like it is working with AOD

angka8 said:
Oh thanks. That is bad. But they sound like it is working with AOD
Click to expand...
Click to collapse
Aod but plugged in
Sent from my SM-G955W using Tapatalk

Techvir said:
Aod but plugged in
Sent from my SM-G955W using Tapatalk
Click to expand...
Click to collapse
:crying::crying::crying:

https://play.google.com/store/apps/details?id=com.RSen.OpenMic.Pheonix. Try this app

rogerandgina said:
https://play.google.com/store/apps/details?id=com.RSen.OpenMic.Pheonix. Try this app
Click to expand...
Click to collapse
Nope. Won't help
Sent from my SM-G955W using Tapatalk

Has no one been able to get this to work when AOD is enabled?

I can't even get it to work when it's charging, why is that? Please help

rotkiv3451 said:
I can't even get it to work when it's charging, why is that? Please help
Click to expand...
Click to collapse
Try clearing cache and storage in app system settings
Sent from my SM-G955W using Tapatalk

Techvir said:
Try clearing cache and storage in app system settings
Sent from my SM-G955W using Tapatalk
Click to expand...
Click to collapse
Unfortunately that doesn't work =( Why does samsung have to make everything so difficult?

Yeah I can't get mine to work even when charging. Now if I got the power button or the home button to go from AOD to lock screen it will work, but not with the screen off or on AOD even when plugged in and charging. None of these suggestions have worked for me. US Unlocked version on latest stock OS.

Try deleting the voice model in Google app and then check... Worked for me when it was not detecting
Sent from my SM-G955W using Tapatalk

Try turning off samsung voice in on screen keyboards under manage keyboards, works better.
---------- Post added at 07:24 PM ---------- Previous post was at 07:20 PM ----------
this issue has been happening for years on other devices too. its google issue.

Techvir said:
Try deleting the voice model in Google app and then check... Worked for me when it was not detecting
Sent from my SM-G955W using Tapatalk
Click to expand...
Click to collapse
lostagain2day said:
Try turning off samsung voice in on screen keyboards under manage keyboards, works better.
---------- Post added at 07:24 PM ---------- Previous post was at 07:20 PM ----------
this issue has been happening for years on other devices too. its google issue.
Click to expand...
Click to collapse
Nope neither one neither of these worked. It still doesn't work from AOD or screen off, even when actively charging.
And how is this a Google issue, when it works perfectly on all other Android devices??