I've notice that the Google Assistant on my 4XL no longer vibrates, either when I tap on it in the home search bar, or when I state "Ok Google." I have haptic feedback enabled and it works in other instances, e.g. active edge, keyboard presses, and the phone vibrates properly for rings. I've matched the settings on from my Pixel 3, where the assistant vibrates properly. I've done a general search on the web and couldn't find anything that resolves this. It is very annoying as this means I don't get any feedback letting me know the assistant is waiting on me when I try to activate it. I've thought about resetting the phone, but am hesitant as I that would require resetting my 2FA for work, which could take a day or more. Does anyone have any ideas or suggestions?
I'm bumping this to see if anybody else has encountered this problem.
Related
There seem to be several proximity sensor threads but I've done a search and have not found anyone that is having this same problem.
When I make a phone call, my screen turns off right away. I can only get it to come on by pressing the power button or tilting the phone so that a bright light or glare is on the proximity sensor or light sensor. This is a pain. I use my power button to end calls but I have to disable that option. Otherwise, any time I need to use touch tones for an in-call menu, I hang up or spend a minute tilting my phone or holding it up to a light bulb. I know there are workarounds that I could be using but I am wondering if my proximity sensor or light sensor is malfunctioning or if it is a software issue.
Also, when using the visual voice mail app, my screen goes black but not off. I can still see the status bar. It happens as soon as I tap the play button and works just fine after my voice mail stops. This is likely unrelated but I can't be sure.
Thanks in advance to anyone that helps!
Running stock and unrooted with no physical damage or obstruction of sensors. I have tried a factory reset... twice.
I'm having a weird issue with mine as well. Mine is a little different though. If I need to make a call that requires to enter # prompts and as soon as I move the phone away from my face the keypad will start beeping on the other end so the prompts will always get invalid responses. While on the phone and I move the phone away from my face for any reason, the person on the other end will hear the beeping.
mokash34 said:
There seem to be several proximity sensor threads but I've done a search and have not found anyone that is having this same problem.
When I make a phone call, my screen turns off right away. I can only get it to come on by pressing the power button or tilting the phone so that a bright light or glare is on the proximity sensor or light sensor. This is a pain. I use my power button to end calls but I have to disable that option. Otherwise, any time I need to use touch tones for an in-call menu, I hang up or spend a minute tilting my phone or holding it up to a light bulb. I know there are workarounds that I could be using but I am wondering if my proximity sensor or light sensor is malfunctioning or if it is a software issue.
Also, when using the visual voice mail app, my screen goes black but not off. I can still see the status bar. It happens as soon as I tap the play button and works just fine after my voice mail stops. This is likely unrelated but I can't be sure.
Thanks in advance to anyone that helps!
Running stock and unrooted with no physical damage or obstruction of sensors. I have tried a factory reset... twice.
Click to expand...
Click to collapse
It sounds like your issue is hardware related. Take it to a sprint repair store and have it exchanged.
mrwicked said:
I'm having a weird issue with mine as well. Mine is a little different though. If I need to make a call that requires to enter # prompts and as soon as I move the phone away from my face the keypad will start beeping on the other end so the prompts will always get invalid responses. While on the phone and I move the phone away from my face for any reason, the person on the other end will hear the beeping.
Click to expand...
Click to collapse
You issue also sounds hardware related. The touchscreen sounds like it is going out. It might be the dialer app but I doubt it. Speaking from experience of course.
I went to Sprint store yesterday and they gave me a replacement for mine.
insuusvenerati said:
It sounds like your issue is hardware related. Take it to a sprint repair store and have it exchanged.
You issue also sounds hardware related. The touchscreen sounds like it is going out. It might be the dialer app but I doubt it. Speaking from experience of course.
Click to expand...
Click to collapse
Thanks I will head to a store and follow up here for anyone else. Thanks again.
I would check the sensor settings and play around before trying the store. But if that doesnt work it prob is hardware issues
Anyone else having this problem? When phone is on standby and I say "Ok Google", instead of search popping up, the keyboard pops up. When the phone is not in standby, hot word detection works perfectly. I've toggled every setting relating to keyboard, voice search, and still nothing. I did a factory reset and still have the problem. I tried calling Google's hardware tech dept and they were no help at all...just asked me to factory reset.
I just turned lock screen on and I can now search from standby. I don't want to use a lockscreen though.
FTLShawn said:
Anyone else having this problem? When phone is on standby and I say "Ok Google", instead of search popping up, the keyboard pops up. When the phone is not in standby, hot word detection works perfectly. I've toggled every setting relating to keyboard, voice search, and still nothing. I did a factory reset and still have the problem. I tried calling Google's hardware tech dept and they were no help at all...just asked me to factory reset.
I just turned lock screen on and I can now search from standby. I don't want to use a lockscreen though.
Click to expand...
Click to collapse
I have the exact same problem. I hope this will get resolved soon.
Does anyone else have this issue? It's really driving me crazy to the point where I feel like ditching the Nexus 6. It's not even every call, but it is enough to annoy me. Pull the phone away from my head and the screen wont wake up. All I can do is long hold power to force a reset. It's really annoying. I've tried the proximity fix for 5.1 but it still happens. I can't set "power to end call" because also sometimes the phone doesn't wake the screen when there is an incoming call so I have to press power to wake the screen to see who it is.
Does anyone have any idea how to get around this other than the two solutions above? This has happened on both my devices (Original and RMA) and I just can't take it any more.
I sounds like a faulty proximity sensor. And I've observed intermittent behavior like this on previous phones (but not my N6). You can test this with a number of apps. I've used "Sensor Box for Android", but there are several more. Prox sensor is located near the top LH corner. With the app open and on prox sensor, passing your hand over it should register on the app.
You are so active on this forum that I won't even ask about a screen protector....
The proximity sensor seems to work fine under all tests that I have done. I actually use Tasker to utilise the proximity sensor to set ringer volume based on whether it is activated or not (eg in my pocket, proximity sensor CLOSE, set ringer high).
Its not every call either and multiple Nexus 6 devices have had this issue for me too. Proximity sensor works in every test
That's weird. I've had no issues at all. I assume you have the issue on the stock ROM too.....
I suppose I'll have to test though I don't really want to run stock.
What about disabling Tasker and trying it out.
Happens with or without tasker. It's pretty much always done it since 5.1
There are known issues with the prox being flaky on this device. I just need to find a way to overcome this.
Remember, we need to separate problem solving from the idea of how we want our phone to look and perform. Once you've identified the root cause, you can then decide what steps you want to take to solve it.
*Sigh* Yes I know. But it's so intermittent I won't know if it solves it for a looooong time. It would be quicker to return to stock, sell it and buy something else
I've literally never ran stock on the nexus 6.
Like Camera indicated, I'd try removing the screen protector if you have one and see if it's better.
It's not a protector issue.
Let's assume I've done all the obvious things except flash stock
Edit. I'm going to try and use power button ends call. Just to see of its an active call that causes it.
Hopefully it will happen when I can take a log cat but inise the phone very rarely.
Try this app in the Playstore.
https://play.google.com/store/apps/details?id=com.vorlan.screenoncall.free
I had a similar issue where the screen would time out while I was on a call and wouldn't wake when I moved the phone away from my face. I had to hit power button to wake phone and enter pin just to end a call. I make/recieve over 100 calls per day and it was getting old til I found this app. Works perfectly every time.
Thanks but that's not the same issue. Mine will not wake at all. I have to force a reboot to get display
You might give the app a try just to see. It keeps the screen on during a call but the proximity sensor still shuts the screen off unless you are on speaker phone. It may not work, but worth a try to keep your N6!
I've seen the same thing with my N6, display goes black (randomly, not even related to a call) and the only thing I can do is reboot. Haven't wasted any time looking for a solution, 'cause I don't think there is an easy one and there is no way to know if something you try is even going to work! I just reboot and move on.
Just posting to let you know you are not crazy and there is someone else out there with the same problem!!!
I'm not sure what you mean. I've been recommended this app before but I don't like the idea of mybscreen being on.
What do you mean it keeps the screen on but proximity still shuts it off? .
Thanks for confirming
Basically it doesn't let the screen timeout. Proximity sensor still functions like normal.
I would try it and see.
If it helps good, if not no harm. It definitely fixed my issue, even if my issue wasn't exactly what you're experiencing.
Well power button end call didn't help. I don't think it is a proximity sensor issue. Let's hope it happens when I can get a logcat. Unlikely. Maybe a job for tasker.
I had this issue too. I eventually thought it was tied to UV, but then I installed all stock and didnt change anything and it still happened. Maybe a bug in lollipop.
I'm having an interesting problem, and I've had this same issue with the n920C running OHx firmware, the N920I running OHx and OIx variants, and the N920I running a stock tmobile firmware.
I've enabled google's "okay google" detection, trained the voice, turned on "from the google app", turned on "from any screen" and turned on "trusted voice." At that point, I can be on any screen in the phone and if I speak "okay, google", it wakes up as expected.
As soon as my screen powers down, the voice detection stops working even when the phone is charging (both wireless and plugged in charging.) If I power back on the screen, "okay google" still won't work. If I unlock the phone manually (fingerprint), it still won't work. In fact, the google voice detection won't work again until I manually start the google app again (either via the app icon or press/hold the home button.)
The strange thing about this is that the google app is still running while the voice detection isn't working (as seen with various application managers and even the "smart manager" RAM tool.
It's as if something is turning off google's voice detect as soon as the screen turns off and not turning it back on.
I've had this same experience regardless of which version of the google app is installed, with all samsung apps running and enabled, immediately after a factory reset and only basic reconfiguration (so wiping data/cache isn't going to help), and also after disabling all "s voice" related samsung apps.
Can others please report if "okay google" detection works for them (or not) under the circumstances I've described? Even better, if someone had this problem and found a work-around, please let me know.
Thanks
Gary
I noticed the same issue a few times. However, even if it works, the screen won't fully unlock when you complete a voice command, which makes it basically useless.
Hi everybody, I've been having a hideous issue with my Note 8 ever since it updated to Android Oreo. So, before when I turned my phone on, either by pressing the home button on the screen or by using the button on the side, I could see the notifications and I could view the whole preview by sliding them down, touch them and open them, erase them or leave them where they where. Now as soon as I use either one of this buttons, the phone automatically selects one of those notifications and pops up the screen with the sign password and iris recognize without giving me the chance of seeing the notifications. If I go back without using the password, the notification it wanted to open gets deleted. It basically takes away the possibility to check the notifications. The problem gets worse when I'm at home because I have the smartlock enabled, so (when and if it works) it opens up any notifications by itself. Sometimes, it's actually rare but it happened a few times already, it does everything on its own. It's on my bed far from me, I'm not even looking at it, a notification arrives, it turns on by itself and asks for my password to open the notification. What do you think? I hope someone has an answer and I hope i didn't create a new thread on an issue already discussed about, but I couldn't find anything similar