I've got an intermittent problem - sometimes when I wake the phone up, the touch screen doesn't work. It happens when I wake it up with the power button, when someone calls, or when an alarm wakes up the screen. That means when the problem happens, I can't answer the call, or turn off the alarm (sometimes locking the screen and waking it up immediately works).
It doesn't seem to be affected by whether or not the phone is or has been charging, whether it's been in my pocket or the temperature of the device. I've not been able to discern a pattern at all. Once the phone is unlocked and the touchscreen is working though, it works perfectly. The problem never returns while I'm using it, only if I lock it, and only sometimes.
If I leave the screen on while touch is unresponsive, I can tell when it is responsive to touch again by a line that quickly flashes along the top edge of the screen. At that point, the screen operates entirely normally.
In what may be a related item, when I'm on a call, sometimes the proximity sensor doesn't work properly and the screen turns back on and starts working. I get off the call and find my phone in a different app.
Does the Nexus 5 use the proximity sensor while the screen is off as a way to weed out unintended touches while the phone is in a pocket?
I'm going to try and store it face up over the next couple of weeks and see if the problem continues, but I was hoping that someone might have some insight.
About the phone:
I cracked the screen over the summer and had it replaced, but I didn't have any issues with it at all until I installed Lollipop. 5.0.1 hasn't made a difference
Related
Hello!
I currently am running Jelly Beans ROM Build 8 on my phone and I have come across a strange problem. What I love about this phone is that, unlike my previous phone, when I would answer phone calls and put the phone to my face, the screen would black out/go to sleep so I don't accidentally end the calls with my cheek (with my previous phone I was constantly doing that). However, for some odd reason, if I answer/ignore a call, the sensitivity of the light sensor (or whatever it is called that would it on the top right corner of my phone that would help black out my screen once I put my face to it) is still on like I am in a phone call mode. For example, I go to text and my thumb gets too close to the sensor and the screen blanks out. I have to unlock it and in the process the screen blanks out. If I keep my fingers away from the sensor, it works fine, but I am so confused on why this screen sleep sensitivity continues. If I reboot my phone, it's fine and back to normal, but I don't want to keep doing that every time I answer a call or ignore it. Has anyone come across this problem or can aid me in finding out how to fix it?
Thank you! Any help would be appreciated!
Bump - anyone have any suggestions? Thanks!
The problem is like this:
SOMETIMES when I call someone, the screen turns off without approaching the phone to my ear. The screen is not turning off by pressing the power button or the volume buttons (I enabled using GravityBox to turn on the screen using the volume keys).
After I end up the call, after a couple of seconds, the phone comes back to normal.
Once again, this behavior appears just SOMETIMES! Usually I don't have this problem!
Any ideas to how so solve this problem?
peslap said:
The problem is like this:
SOMETIMES when I call someone, the screen turns off without approaching the phone to my ear. The screen is not turning off by pressing the power button or the volume buttons (I enabled using GravityBox to turn on the screen using the volume keys).
After I end up the call, after a couple of seconds, the phone comes back to normal.
Once again, this behavior appears just SOMETIMES! Usually I don't have this problem!
Any ideas to how so solve this problem?
Click to expand...
Click to collapse
I wouldn't worry too much about it, its just a glitch, it happens to me sometimes too , when i put it on speaker and i get close to the phone , the screen turns off and it comes back after a while. it doesn't bother me too much. It might be that the sensor is too sensitive. Have you tried a custom rom ?
This issue happens to my son's phone too.
Anyway, it shouldn't be random, please double check if it happens ALWAYS after a phone reboot, this is the behaviour of mine
I want the moderator to ban me.
display issue
Hello,
I have started to face the same issue mentioned above.
On googling I came across the motorola forum (google search: Moto G Proximity Sensor Software Issue)
It seems the issue is being discussed there and apparently they need more moto g users with this issue to help them out solve this.
On using z device i noticed the proximity sensor value stuck at 3 with no change covered/not covered (sensor) [Phone running without restart for 6+ hours]
After restarting the phone the sensor value in z device changes. 100 (uncovered) to 3 when covered.
I will keep checking this every few hours to see when does the proximity sensor stop working without restarting the phone. (uptime)
Can the DEV's here help us out? looks like Motorola may take some time in finding a solution to this issue.
This seems to have went away with 4.4.3 and the new Dialer app.
When I make or receive a phone call on my new Nexus the screen blacks out. I understand that it should black out when the phone is brought up to my ear, but it blacks out even though the phone is eighteen inches away from me. There is nothing on top of the proximity sensor and it is clean. The phone is not in a case. The sleep timer in set to two minutes. The cache partition has been cleared.
I think this happened after upgrading from Android 5 to 5.1, but I cannot be certain.
The AndroSensor app always reports that the proximity sensor detects something at 0.0 inches (with 12.7 mA), even though the sensor is uncovered.
I have seen several threads in various forums on this issue with the Nexus 5, but I have not seen a definitive answer as to what is wrong and what can be done about it.
Help would be very much appreciated as I need to know if it is a software bug that will be fixed as part of routine updates, if it is a user fixable problem (operator error!), or if the sensor is actually dead, in which case I can exchange the phone (Amazon uk).
Chasharv
Chasharv said:
When I make or receive a phone call on my new Nexus the screen blacks out. I understand that it should black out when the phone is brought up to my ear, but it blacks out even though the phone is eighteen inches away from me. There is nothing on top of the proximity sensor and it is clean. The phone is not in a case. The sleep timer in set to two minutes. The cache partition has been cleared.
I think this happened after upgrading from Android 5 to 5.1, but I cannot be certain.
The AndroSensor app always reports that the proximity sensor detects something at 0.0 inches (with 12.7 mA), even though the sensor is uncovered.
I have seen several threads in various forums on this issue with the Nexus 5, but I have not seen a definitive answer as to what is wrong and what can be done about it.
Help would be very much appreciated as I need to know if it is a software bug that will be fixed as part of routine updates, if it is a user fixable problem (operator error!), or if the sensor is actually dead, in which case I can exchange the phone (Amazon uk).
Chasharv
Click to expand...
Click to collapse
Just press the power button when that happens, screen will turn on again. Done.
Nexus 5 black screen: thanks, but more help needed
beekay201 said:
Just press the power button when that happens, screen will turn on again. Done.
Click to expand...
Click to collapse
Thanks for this, but if the power button it set to end the call it does indeed turn the screen on again, but of course also ends the call prematurely. If the power button is not set to end the call, then nothing happens when it is pressed during a call and the screen stays black. The only way out of the black screen under those circumstances is to hold the power button down to turn the phone off and then restart it!
Prior to the upgrade 5.1, from the version of 5 that came with the phone, when I made or received a call the screen remained active until I put the phone to my ear.
Further advice would be much appreciated.
Chasharv
Chasharv said:
Thanks for this, but if the power button it set to end the call it does indeed turn the screen on again, but of course also ends the call prematurely. If the power button is not set to end the call, then nothing happens when it is pressed during a call and the screen stays black. The only way out of the black screen under those circumstances is to hold the power button down to turn the phone off and then restart it!
Prior to the upgrade 5.1, from the version of 5 that came with the phone, when I made or received a call the screen remained active until I put the phone to my ear.
Further advice would be much appreciated.
Chasharv
Click to expand...
Click to collapse
if i make or answer a phone call, and put it on speaker, after a few secs it will turn the screen off automatically. If i then press the pwer button (i don't have the accessibility option on), it WILL wake the screen but doesn't end the call.
running stock LMY47D
Nexus 5 black screen, solved
beekay201 said:
if i make or answer a phone call, and put it on speaker, after a few secs it will turn the screen off automatically. If i then press the pwer button (i don't have the accessibility option on), it WILL wake the screen but doesn't end the call.
running stock LMY47D
Click to expand...
Click to collapse
Thanks for this, but the problem was that the screen blacked instantly on making or receiving a call and was unresponsive, so the only way forward was to press the power button. This either terminated the call or shut down the phone, according to how it was set, so neither was useful.
As I said originally, I suspected the proximity sensor was faulty as the a proximity detector sensor app always indicated that there was something close to it. Hence the phone would assume it was next to my ear when making or receiving calls, and so black the screen. This morning, for reasons that I don't understand at all as I have not changed anything on the phone, the proximity sensor is reported as working and the phone behaves as it should on making and receiving calls!
I suppose that either the sensor has an intermittent fault, or something in the phone's software has changed to permit it to work. I have a couple of week's left before the Amazon return window expires, so I will monitor the situation.
Thanks once more for the help.
Chasharv
I have the identical problem with my nexus 5 running stock kitkat. Makes it very hard to use the keyboard to reply to automated requests to "if... press 1, if.... press 2".
Is it possible to turn the proximity sensor off? I don't need it and it just causes problems for me.
Hi all!
I have the fingerprint locked option enabled. I find that sometimes, somehow the phone vibrates when it is in my pocket. When i take the phone out of my pocket, it will say fingerprint lock disabled. It's as though it is detecting the inside of pocket as a print, that's trying to unlock the phone. I also find that the flashlight turns it self on whilst it is in my pocket and also the bluetooth and wifi.
Is anyone having similar issues?
Finding it really annoying.
I've found some of my settings changed before, and I've noticed that the double tap to wake will work through thin material . . . like a jeans pocket.
When you put it in your pocket, turn the screen towards your body and see if that helps. Failing that, try disabling double tap to wake.
I've not had the fingerprint sensor disabled message myself, but the sensor can also trigger through thin material too. It obviously won't read any fingerprint, so if it happens a few times, it just temporarily disables the sensor.
I had to disable the double-tap to wake screen option as it was always triggering in my pocket (screen facing in). I only have screen lock set to swipe though so walking/climbing stairs was waking the screen, pulling down the notification panel and going to town changing settings. I even somehow managed to change the time display setting from 24 hour to 12 hour. I mean, how the hell can that happen in a short few minutes in a pocket?!
Glove mode is/was off if anyone thinks that might be the cause. No screen protector either.
I only have the sensor lock if my finger fails to unlock the phone after a few tries. Every time the fingerprint is not properly read it will vibrate, after about 4 go's, it locks and you need to type in your pin. I'm guessing something is pressing the power button in your pocket and it's trying to scan your finger but failing, so by the time you pull it out, it's locked itself!
I too had to diable double tap to wake because it kept coming on in my pocket. even if it does not get past the fingerpring lock it still wastes some battery.
it would be nice if something could be done in tasker to:
if phone is flat on table(accelerometer)
then enable double tap to wake.
else disable it.
DT2W is wayyy too sensible at the moment. I hope Sony will fix it. A touch or double touch shouldn't be detected through clothes when the screen is off.
That feature was perfectly tweaked on my OnePlus One running CM12.1, and I liked to use it
Yeah I find the screen touch, fingerprint and rotation all way too sensitive. I have already disabled 2 of them, fingerprint is next....
Sent from my E6653
Ditto with the tap to wake frustratingly waking my phone constantly in my pocket. Never had the problem with the Z3. So many issues with this phone that were perfect on the Z3 feel like I've gone backwards.
same issue here, tap to wake activated and called the cops on me LOL...OMG
This is so annoying. My phone always wakes (through dt2w) when in my pocket and does weird stuff: changes settings, calls people, etc...
The one thing I found working for me is keeping the screen facing away from my body while in my pocket. It doesn't wake the phone up then.
I have this problem as well.
Try gravity screen app. It should turn off the screen in 1 second or less should it accidentally turn on while in the pocket.
This has bothered me loads so i've disabled the feature. You'd think they would make use of the light sensor to detect if the phone is in the pocket and then not unlock the phone on double-tab. There's the standard Google 'on-body' feature which can be used to disable security when the phone is detected as on your person.
and this is how a very useful feature quickly became most annoying issue... because of a defective light sensor or its faulty software development.
another thing I don't understand: if screen is locked, why notification access isn't ?!? at least they should put an option to enable or disable it.
sony customer care ?!?
...
sadonlyone said:
another thing I don't understand: if screen is locked, why notification access isn't ?!? at least they should put an option to enable or disable it.
sony customer care ?!?
Click to expand...
Click to collapse
That's actually standard Android behaviour would you believe - both Lollipop and Marshmallow. Don't expect a "fix" for this anytime soon...
It's configurable on iPhone though. Go iOS!
I had to disable the double-tap to wake screen option as it was always triggering in my pocket (screen facing in). I only have screen lock set to swipe though so walking/climbing stairs was waking the screen, pulling down the notification panel and going to town changing settings. I even somehow managed to change the time display setting from 24 hour to 12 hour. I mean, how the hell can that happen in a short few minutes in a pocket?!
When I make a call and hold the device to my ear, the screen goes off. And that's fine. But when I remove the device from my ear, the screen is still black. I say goodbye to the caller, and to interrupt the conversation I have to press the power button or double tapp screen to wake the screen. Is there any option to wake the screen more actively?
The same problem here....
I hope they will fix this in future updates. My friend dont have this problem. On other forum some guy told me that i need move phone and i will get phone wake up. On my other phone (s9+) i dont have this problem. This problem have many s10 series phone. I read that the problem is because proximity sensor position. And AOD dont turn off when is phone in a pocket or screen down wich use more battery.
I tried old good wipe cache in recovery and...it's good, problem is gone.
Try it too!
I try. It didn't help
Same problem as well, it doesn't happen always but often enough to annoy me...
yeah, same problem here man
same problem.. if you turn your phone upside down it will get the movement and show the screen but don't think this is actually a good workaround! does anyone know if there is something to do for it?