I thought I had saw a thread about this but couldn't find it when I searched.
I have noticed sometimes "Ok Google" will not work when my screen is off. Sometimes I have to turn the screen on to get it to detect but just now I tried and it wouldn't detect it even when I woke the device. It didn't detect it until I swiped into google now and looked to make sure the setting didn't get turned off or something (it didn't and all the settings were correct so I exited settings) and then after that it started working again. Anyone else notice any issues with it not always detecting you say "Ok Google". This was the first time it didn't detect it when the screen was off or when the screen was on though.
graffixnyc said:
I thought I had saw a thread about this but couldn't find it when I searched.
I have noticed sometimes "Ok Google" will not work when my screen is off. Sometimes I have to turn the screen on to get it to detect but just now I tried and it wouldn't detect it even when I woke the device. It didn't detect it until I swiped into google now and looked to make sure the setting didn't get turned off or something (it didn't and all the settings were correct so I exited settings) and then after that it started working again. Anyone else notice any issues with it not always detecting you say "Ok Google". This was the first time it didn't detect it when the screen was off or when the screen was on though.
Click to expand...
Click to collapse
I had this happen only once so far. Had to reboot device as it seemed Google was logging me out of chrome and other apps as well. I decided to wipe device and flash the factory image and it has not happened again. Yet...
I've had this happen to me as well. More than a few times. Verizon Pixel, unlocked, rooted, and running ElementalX-0.05 (Not saying any of that is causing this).
I have the same issue as well.
Had it a few times from lock screen on a stock Pixel XL.
I have had it happen quite a bit. Started a support ticket with Google .. and they blamed third party apps.. That wasn't much help, as don't we all have apps on our phone. My phone is not rooted. Not sure how to track this one down.
Same problem for me, and I have remained stock.
Good to know it's just not me. I'm completely stock as well. It seems to happen when I have let my phone sit for a while and not used it. I wonder if something is happening when the phone goes into deep sleep/doze.
Same problem here.
Sent from my Pixel XL using XDA-Developers mobile app
Yep happening to me too.
Verizon XL Elemental X P firmware for now.
It was working and it stopped at some point. Haven't tried to trouble shoot any apps yet. I'm having to wake and unlock. Trusted voice is on.
Thoughts / ideas?
Same issue here. Stock Pixel XL.
Same for me too. Stock Pixel XL
Yeah ok google doesnt always hear u. Everything stock non rooted strait from the google gods
Same here...all stock. Works great sometimes but others when the screen is off I'll go to ask it something and get no response.
Same here. Stock. Annoying AF.
Contacted Google Support. The staff told me to turn on and off Google Assistant then reboot the phone. Still no luck. The staff also mentioned that they never aware of this issue...
This issue is part of a larger issue stemming from the microphone not working. Have any of you also noticed while on a call, suddenly the person can no longer hear you but the call doesn't drop until someone hangs up. There is a large post on Google Pixel community forums about this and the microphone issues. Apparently they believe it's software related.
Hi guys. Please check your APN setting.
"OK Google" works for me after I amended my APN. Not sure why they are related but it works for me.
mdroid01 said:
Hi guys. Please check your APN setting.
"OK Google" works for me after I amended my APN. Not sure why they are related but it works for me.
Click to expand...
Click to collapse
What should the APN settings be set to?
mdroid01 said:
Hi guys. Please check your APN setting.
"OK Google" works for me after I amended my APN. Not sure why they are related but it works for me.
Click to expand...
Click to collapse
What should the APN settings be set to?
xSpaceGhost said:
What should the APN settings be set to?
What should the APN settings be set to?
Click to expand...
Click to collapse
Please check with your own service provider APN setting.
Related
Anyone else have this problem?
Basically when using Google Now Voice Commands it keeps searching and then says "Offline".
I find this strange because it is still connected to my phone and I still receive notifications such as text messages.
Anyone know what the cause of this issue is?
Thanks!
mr3army said:
Does your phone have a wifi/data connection?
Click to expand...
Click to collapse
Yup. I'm using a Oneplus One (International Model).
make sure google "now" is installed and enabled
EDIT: installed on your phone* I know I had it turned off because it was annoying lol
v3ngence said:
make sure google "now" is installed and enabled
EDIT: installed on your phone* I know I had it turned off because it was annoying lol
Click to expand...
Click to collapse
I think I found my problem. My Google Now voice commands on my phone sometimes hangs. It just stays on "Recognizing". Anyone know how to fix this?
footsouljah said:
I think I found my problem. My Google Now voice commands on my phone sometimes hangs. It just stays on "Recognizing". Anyone know how to fix this?
Click to expand...
Click to collapse
My solution was to kill the process by doing to Recent Apps screen and swiping it away. I then tried "OK Google" again on the phone to see if it works. Generally, it comes back working and then the Moto 360 responds to my voice query.
Dennis
I believe I figured this out. In Google now settings there is a allow search from lock screen option. This seems to be the hangup when the watch is on and phone is off
i have the same problem too, please help me i'm going crazy
help me please i have the same problem, and i notice when i try to respond one message with voice, it shows "google now not available" or something like that, please help me!!
For whatever reason callers can't hear me.
I think I have narrowed it down to Bluetooth, doesn't matter which device. A reboot seems to resolve the issue.
What can I do besides the infamous hard reset? I know it isn't a microphone issue because I used Voice recorder and it was crystal clear when callers could not hear me.
mikemikemikexxx said:
For whatever reason callers can't hear me.
I think I have narrowed it down to Bluetooth, doesn't matter which device. A reboot seems to resolve the issue.
What can I do besides the infamous hard reset? I know it isn't a microphone issue because I used Voice recorder and it was crystal clear when callers could not hear me.
Click to expand...
Click to collapse
I am coming here to solve THIS EXACT problem.
If you go to google card settings -> Voice -> "Ok Google" detection
Turn off "From Any Screen"
I have Verizon LG G3 unrooted and just had my phone swapped out from Verizon on Saturday because of this issue. Got my new phone after it was mailed to me, bought a new glass screen protector for $50 set all my settings back up and then today it started again. I have been searching for HOURS online and found a reddit article suggesting this solution. Tried it, and like magic my phone was working fine again. It is entirely software related.
First thing I did was come to this forum to make sure it was recorded here for others suffering.
AHpatriots37 said:
I am coming here to solve THIS EXACT problem.
If you go to google card settings -> Voice -> "Ok Google" detection
Turn off "From Any Screen"
I have Verizon LG G3 unrooted and just had my phone swapped out from Verizon on Saturday because of this issue. Got my new phone after it was mailed to me, bought a new glass screen protector for $50 set all my settings back up and then today it started again. I have been searching for HOURS online and found a reddit article suggesting this solution. Tried it, and like magic my phone was working fine again. It is entirely software related.
First thing I did was come to this forum to make sure it was recorded here for others suffering.
Click to expand...
Click to collapse
Do you by any chance have bluetooth in Google Settings enabled?
I do have it enabled
AHpatriots37 said:
I do have it enabled
Click to expand...
Click to collapse
Sorry missed this post. Just as an FYI, your suggestion works but also keeping everything checked except Bluetooth
Having lots of difficulties with "OK Google" on this watch. Bluetooth stays connected fine and so does wifi because i'm getting all my notifications instantly and it doesnt say that im disconnected. When I say OK Google the prompt comes up to speak...but only like 4 of the 30 times I tried did it actually work and not show the cloud symbol. I restarted the watch a couple times and the same thing happens, i've also done a factory reset since purchasing the watch 4 days ago. Thoughts? Thanks.
ultimatdan said:
Having lots of difficulties with "OK Google" on this watch. Bluetooth stays connected fine and so does wifi because i'm getting all my notifications instantly and it doesnt say that im disconnected. When I say OK Google the prompt comes up to speak...but only like 4 of the 30 times I tried did it actually work and not show the cloud symbol. I restarted the watch a couple times and the same thing happens, i've also done a factory reset since purchasing the watch 4 days ago. Thoughts? Thanks.
Click to expand...
Click to collapse
I found it to be very hit or miss as well.
Sent from my Nexus 6 using Tapatalk
I've not had it work once yet. The mic works as if I manually launch it everything seems fine.
I've tried restarts, factory resets & all the above. I'm pretty close to returning in all honesty as the voice launch is a huge deal for me!
I use my Huawei Watch with a OnePlus One on stock COS12.1 and have the same problem.
A lot of times when I use the watch to say "Okay Google" it will tell me it's disconnected. The only work-around I found was to quickly wake up the phone and it would start working right away. It seems like the internet pauses if my phone has been idle too long. I receive notifications in real time so I don't know what's really causing it.
I had the same problem with the huawei and a dutch HTC one M8.
The problem was gone after changing "Google voice typing primary language" from dutch in english.
And teach Google the sound of my voice in "OK Google" detection =>> From any screen.
Try turning off the restricted data for google app and google play services under Data Usage in settings.
ultimatdan said:
Having lots of difficulties with "OK Google" on this watch
Click to expand...
Click to collapse
I find it very hard for it to recognise my Australian accent. However, when I put on an American accent it works 100% of the time!
Any way of fixing that?
salada2k said:
I find it very hard for it to recognise my Australian accent. However, when I put on an American accent it works 100% of the time!
Any way of fixing that?
Click to expand...
Click to collapse
Did you try going into Google Settings on your phone? There's an option to retrain the voice model in there.
ts_mpls said:
Did you try going into Google Settings on your phone? There's an option to retrain the voice model in there.
Click to expand...
Click to collapse
HI mate, yes I've done that countless times to no avail unfortunately. It works fine on my phone, but it's like retraining the voice model has no effect on the Huwaei Watch.
salada2k said:
HI mate, yes I've done that countless times to no avail unfortunately. It works fine on my phone, but it's like retraining the voice model has no effect on the Huwaei Watch.
Click to expand...
Click to collapse
Dang, I was wondering about that. Sorry!
I've been smashing my head over this to no avail. Prior to side loading 8.1, when my phone rang the caller and swipe up/down would appear on the lock screen, now it rings, but nothing on the lock screen till I wake it with the fingerprint sensor. Did I miss something? Was this changed? I've been through the settings and still can't see anywhere that I missed. This a security feature so no one can see who's calling till you hit the sensor? Any feed back would be appreciated.
I agree surprised more are not annoyed...lol
Doublecore said:
Well it seems it's only happening when connected to Bluetooth. I hadn't noticed since I'm connected to my headset all day at work. Disconnected from Bluetooth and had my wife call me...screen popped right on. So it's another Bluetooth bug I guess.
Click to expand...
Click to collapse
I tested incoming phone calls with and without bluetooth, and came to the same result. Since it's very annoying for the screen to not turn on, I ended up making a macro with Macrodroid to turn the screen on when a call comes in. This workaround will be sufficient for me until Google fixes the bug.
I posted on this same issue last week. It's the last update to Google Phone app that broke this. I don't have the time to report it to them...so hopefully it gets fixed!
https://forum.xda-developers.com/pixel-2-xl/help/google-phone-update-bug-t3718424
*Edit- To fix(?), uninstall the phone app and it will remove the update. Should work then. Of course you won't be able to use Duo for video calling within the dialer...but I couldn't care less about that.
I just had this happen yesterday. Here is a work around with Tasker and Secure Task to wake screen on incoming call.
Import it in Profiles tab in Tasker and make sure you have Secure Task and have it configured with adb.
5150jpd said:
I've been smashing my head over this to no avail. Prior to side loading 8.1, when my phone rang the caller and swipe up/down would appear on the lock screen, now it rings, but nothing on the lock screen till I wake it with the fingerprint sensor. Did I miss something? Was this changed? I've been through the settings and still can't see anywhere that I missed. This a security feature so no one can see who's calling till you hit the sensor? Any feed back would be appreciated.
Click to expand...
Click to collapse
This may be related to the Proximity Sensor bug introduced with 8.1. Do you have a screen protector on your device? Does it cover the PS?
Nope.. No protector on phone at all.
v12xke said:
This may be related to the Proximity Sensor bug introduced with 8.1. Do you have a screen protector on your device? Does it cover the PS?
Click to expand...
Click to collapse
It started for me on the Google Phone update to version 15 on Dec. 14th. I never had this issue on 8.1 that I did the OTA sideload when I got my phone on Dec. 4.
My proximity sensor is fine. Even with always on display, AOD goes off in pocket and turns back on when I pull it out. On a phone call the screen blanks when I put it to my ear and wakes when I pull it away from my head.
Yep -- I just ran into the problem today as well. I've got 8.1.0 on my Pixel 2 XL, and I get this behavior (display not waking up for incoming call) when connected via Bluetooth -- to my car, headphones (Sennheiser PXC 550) or to my Jabra Speak 710 BT speakerphone.
I considered trying Drupe or Truecaller, but then I read that packet sniffing tests show them sending your contacts data off their servers...so I think I'll wait for a fix from Google. Really annoying. There are a couple of threads on this in Google's product forums / Pixel User Community:
https://productforums.google.com/fo...QEn6fH0OI;context-place=forum/phone-by-google
https://productforums.google.com/forum/#!topic/phone-by-google/hdmLGWSMhSM;context-place=topicsearchin/phone-by-google/category$3Adevice-performance%7Csort:relevance%7Cspell:false
So far, Google doesn't appear to be weighing in with any useful commentary. The only "fix" for now seems to be "uninstalling" the phone app (which just reverts back to the OEM installed version) and then not accepting updates to the app. But I've read that this can spin up other issues.
jonstrong said:
Yep -- I just ran into the problem today as well. I've got 8.1.0 on my Pixel 2 XL, and I get this behavior (display not waking up for incoming call) when connected via Bluetooth -- to my car, headphones (Sennheiser PXC 550) or to my Jabra Speak 710 BT speakerphone.
I considered trying Drupe or Truecaller, but then I read that packet sniffing tests show them sending your contacts data off their servers...so I think I'll wait for a fix from Google. Really annoying. There are a couple of threads on this in Google's product forums / Pixel User Community:
https://productforums.google.com/fo...QEn6fH0OI;context-place=forum/phone-by-google
https://productforums.google.com/forum/#!topic/phone-by-google/hdmLGWSMhSM;context-place=topicsearchin/phone-by-google/category$3Adevice-performance%7Csort:relevance%7Cspell:false
So far, Google doesn't appear to be weighing in with any useful commentary. The only "fix" for now seems to be "uninstalling" the phone app (which just reverts back to the OEM installed version) and then not accepting updates to the app. But I've read that this can spin up other issues.
Click to expand...
Click to collapse
Have you tried the tasker profile from post #7 by Pkt_Lnt? That fixed it for me.
JimSmith94 said:
Have you tried the tasker profile from post #7 by Pkt_Lnt? That fixed it for me.
Click to expand...
Click to collapse
Thanks. If this issue goes on much longer, I'll probably try that. Oddly enough, despite having played with custom Android ROMs and modding over the years, I never used Tasker -- concerned that having the add'l service(s) running in the background around the clock would be more of a battery drain.
I updated my phone app yesterday, and the screen lights up again upon receiving a phone call. I disabled the macro that I made in Macrodroid just to make sure.
EMcTx said:
I updated my phone app yesterday, and the screen lights up again upon receiving a phone call. I disabled the macro that I made in Macrodroid just to make sure.
Click to expand...
Click to collapse
Thanks for the info. My phone app updated too, so I'll disable the Tasker profile and see if it lights up without it for me too.
Is there a xposed module to disable the stupid proximity sensor? I'm having some issues with it. It does not wake my screen up when I pull it away from my face.
EMcTx said:
I updated my phone app yesterday, and the screen lights up again upon receiving a phone call. I disabled the macro that I made in Macrodroid just to make sure.
Click to expand...
Click to collapse
JimSmith94 said:
Thanks for the info. My phone app updated too, so I'll disable the Tasker profile and see if it lights up without it for me too.
Click to expand...
Click to collapse
Reports on G+ state it fixes the issue. I've not seen v.16 yet.
https://plus.google.com/u/0/+ArtemRussakovskii/posts/byEHovfFbMj
My last name starts with "S" too, not sure why Jim gets priority over me. I always get updates late, which is why apk mirror is bookmarked. :good:
Pkt_Lnt said:
Reports on G+ state it fixes the issue. I've not seen v.16 yet.
https://plus.google.com/u/0/+ArtemRussakovskii/posts/byEHovfFbMj
My last name starts with "S" too, not sure why Jim gets priority over me. I always get updates late, which is why apk mirror is bookmarked. :good:
Click to expand...
Click to collapse
Oops, mine was still on v15 so thanks to you, I just installed v16 from your link. See there, you're still da man! :good::highfive:
JimSmith94 said:
Oops, mine was still on v15 so thanks to you, I just installed v16 from your link. See there, you're still da man! :good::highfive:
Click to expand...
Click to collapse
I can confirm V16 fixes the phone app and resolves this issue. It's being rolled out gradually, in waves. If you don't see the update on the Play Store, you can download it from APKmirror. Start here:
https://www.apkmirror.com/apk/google-inc/google-phone/
My issue is the exact opposite..
I answer a call on my bluetooth headset while the phone is in my pocket and buttons start being pressed so I have to take the phone out to lock the screen.
Any quick fixes on this issue?
I'm late to the party, but I fixed this on a Pixel 2 XL in our household. In the system's app settings I force stopped the phone app and cleared the app cache, then I disabled the "Flip to Shhh" feature in the phone app settings. If that fix works for you, please leave a reply so we can validate.
Hello,
I have been struggling recently to answer or reject calls when given the swipe up or down option.
When its unlocked and I get the tap to answer or reject as a notification its fine.
I'm just wondering if anyone else had a similar issue or had found a fix.
I'm on the official firmware, running 8.1.0
I've experienced something similar too. Sometimes I find myself swiping over and over again just to get one call answered or rejecte I have no idea why it does that, or when, it seems to be random on mine
I have to swipe upp exactly(?) 3 times to answer a call from the lock screen.
Also running official ROM 8.1, no root or mods so far.
Have only had the phone for a few weeks, so don't know what is normal.
Otherwise it seems to work very well.
I've found you can swipe down from the top of the screen and can answer it from the notification menu instead.
Just takes longer.
cobben said:
I have to swipe upp exactly(?) 3 times to answer a call from the lock screen.
Also running official ROM 8.1, no root or mods so far.
Have only had the phone for a few weeks, so don't know what is normal.
Otherwise it seems to work very well.
Click to expand...
Click to collapse
Just after having written the above, the phone corrected itself.
Now I can answer calls on the first swipe.
Interesting . . .
Sometimes my phone will let me answer normally. most of the time however I have to use the notification bar.
I have been having this issue since the very beginning. I even changed to the google phone app and jt still does that. Its because of the framerate. I think. Its very hard to test because uts vey inconsistent.
Yup, been having the same issue. Stock phone, no root. What's frustrating is there as no further updates.
iliais347 said:
I have been having this issue since the very beginning. I even changed to the google phone app and jt still does that. Its because of the framerate. I think. Its very hard to test because uts vey inconsistent.
Click to expand...
Click to collapse
I had display set to 90Hz for no particular reason, have now tested having it set to 60Hz, and I have been able to answer every call directly with one swipe .
Of course I don't get so many calls to this sim card I have in it now, but previously it hardly worked at all
So the problem might welll be connected to the display refresh rate for some reason.
cobben said:
I had display set to 90Hz for no particular reason, have now tested having it set to 60Hz, and I have been able to answer every call directly with one swipe .
Of course I don't get so many calls to this sim card I have in it now, but previously it hardly worked at all
So the problem might welll be connected to the display refresh rate for some reason.
Click to expand...
Click to collapse
What i did is i added the google dialer app to my phone, then to game booster and set its fps to 40. Now i can answer the calls.