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
ok story, as of this month whenever I called any one I had to reboot my phone so that they could hear me, if I didn't the person I was calling would just keep saying hello.
well the problem is with the ok Google from any screen setting it is messing up the calls on phone and Bluetooth.
go to Google settings,> search & now,> voice,> ok Google detection,> turn off the from any screen and reboot.
after that problems with calls should be gone.
cmlucht said:
ok story, as of this month whenever I called any one I had to reboot my phone so that they could hear me, if I didn't the person I was calling would just keep saying hello.
well the problem is with the ok Google from any screen setting it is messing up the calls on phone and Bluetooth.
go to Google settings,> search & now,> voice,> ok Google detection,> turn off the from any screen and reboot.
after that problems with calls should be gone.
Click to expand...
Click to collapse
Hopefully this works. Thanks! How did you come up with this?
Hey all,
Just wondering if anybody is having a similar issue. Before I get started I did a quick search and havent found any recent threads stating the same issue.
What happens is often I will place a call and immediately switch to speakerphone so I can put the phone down and be handsfree, however for some reason I cannot hear ANYTHING the other line is saying, but they can hear me just fine. Switching back to earpiece does nothing either. This problem has been happening for about a week or so.
The only remedy I have found is to either call back, or reboot my phone but both of these options are unacceptable IMO.
Has anybody else experienced this? If so, what was your solution? I have gone through all the call settings and nothing seems to be out of the ordinary. I don't mute or hold calls and my call volume is almost at max.
Any help or input is appreciated.
Same problem since I went to lollipop. Met a lgcrep who had never seen this
Thanks for the response. It must be a pretty bad software bug then
The problem is with the 3/19 update of the Google search app. Either roll back the build on your phone or disable OK Google from any screen. Same problem exists on KitKat.
OMG thank you so much!
I was starting to think I would never be able to use speakerphone again
Yaminashi said:
OMG thank you so much!
I was starting to think I would never be able to use speakerphone again
Click to expand...
Click to collapse
You are welcome. I almost RMA'ed my phone. Apparently, lots of people have already only to have the same problem as soon as they apply updates.
Here's the apk for the older version. Make sure that you roll back updates to the installed version of Google (and turn off auto-updates) before installation:
http://www.apkmirror.com/apk/google...-app-4-1-29-1706998-arm-android-apk-download/
Same issue
datawrhsdoc said:
You are welcome. I almost RMA'ed my phone. Apparently, lots of people have already only to have the same problem as soon as they apply updates.
Here's the apk for the older version. Make sure that you roll back updates to the installed version of Google (and turn off auto-updates) before installation:
http://www.apkmirror.com/apk/google...-app-4-1-29-1706998-arm-android-apk-download/
Click to expand...
Click to collapse
I had this same issue and disabling the from any screen feature fixed it. I do like that feature however and would like to continue to use it. Do you know if the version in your link supports that function? If not do you know if there's a version that does that does not interfere with speakerphone function?
Thanks.
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.