Been running lollipop on my nexus 5 for a few days now. I have notice a few bugs when in a phone call. When i put the phone up too my ear, the screen doesnt always go black, sometimes it just dims, and when the big red end call button touches my cheek, the call disconnects. The second problem when the screen only dimes, my ear pulls down the notification tab and activates what ever notification are showing. I never had these problems with kitkat. Anyone else noticing these problems.
Yes...
I have same problem...
Sometimes in a call, the screen lights up even with my nexus flip case closed....
eric1212 said:
Been running lollipop on my nexus 5 for a few days now. I have notice a few bugs when in a phone call. When i put the phone up too my ear, the screen doesnt always go black, sometimes it just dims, and when the big red end call button touches my cheek, the call disconnects. The second problem when the screen only dimes, my ear pulls down the notification tab and activates what ever notification are showing. I never had these problems with kitkat. Anyone else noticing these problems.
Click to expand...
Click to collapse
Am I the only one to want a gif of your ear pulling down the notification tab?
Related
Some kind of weird problem here; everytime i make a call and want to hold my phone to my ear the following happens:
- My screen turns to black (normal behaviour)
- Simultaneously my ear speaker mutes for as long the screen is black
- My screen almost instantly turns on again, turning on my ear speaker too
- This continues to happen as long as i hold my phone to my ear, so my ear speaker goes on-off-on-off-on-off, i cannot make a conversation like this.
The strange thing is, when i remove the phone from my ear, preventing the proximity sensor to see my face and to black the screen, nothing happens and the ear speaker keeps on (so is the screen).
Any idea how this could be caused? When i opened my phone recently, i noticed that there is a ribbon cable damaged (the ear speaker one, i thought it was the (-) side, the (+) is still connected).
Could this be the reason of my ear speaker simultaneously muting when the screen is turning to black? I don't see the relation to those two things happening.
Thanks!
have the same problem with mine, anyone has any ideas?
Same here
I am having this same issue.
It started all of a sudden around June 28th. I submitted a bug report to google approximately two weeks ago and haven't heard anything back. Hopefully, the Jelly Bean update will fix this issue if it isn't corrected sooner.
For now, I just hold the phone horizontally with the screen facing upwards to prevent the screen from turning off and killing the audio.
Official Bug Report
Since I am still experiencing this issue I have posted the issue on Google's Android support. If you are also experiencing this problem please go here <code(dot)google(dot)com/p/android/issues/detail?id=36595>, leave a comment, and follow along as we hope to get this solved.
My screen all of a sudden when I turn on my phone, its grey. No color, words, or anything. Blank screen- no cracks or I dont think its due to a cracked screen.
The phone works because when I call it it rings and I would slide the middle area and its able to pickup the call.
Tried disconnecting the battery for a few minutes. did not solve the issue.
Any suggestions?
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.
Hello.
I changed ROM from stock 2.3.5 to CM11 Open Desire) and now i have problem with ending calls. When i'm initiating call or respond to the incoming call, after closing phone to ear, screen goes blank. It's normally. But when i want to end this call, after removing phone from ear, sometimes screen doesn't get to work for several seconds and i can't tap the hang up button. Sometimes i have to wait for the other side to hung up to get the screen back to work. Until this, the phone not respond for buttons. Sometimes screen back to work and there is a calendar app running and bluetooth turning on (and both of them were off before call).
Sometimes everything is ok and i can't figure out - where is problem?.
I'm 100% sure that it's not a problem with proximity sensor, because on stock ROM sensor worked perfectly.
My Mi Note 10 updated to Android 11 with MIUI 12.1.3 and now when I get an incoming call, sliding up the button to answer the call doesn't work. The button sides up, the screen goes black for a few seconds, then the green button appears again, and sliding it up does nothing.
Someone else I know who has the Mi Note 10 had the same happen to them a few times.
Anyone else experiencing this? Any ideas how to fix it?
I should add that it's not just on the phone, but today I couldn't answer from my car's screen either. Pressing the Answer button on the car's screen could not make the Note answer the call.
I don't have the update yet, but often issues after updating can sometimes be fixed after resetting your phone.
A clean install is generally more stable than an updated one, so it's worth a try.
Good luck,
Oliver
MacGuy2006 said:
My Mi Note 10 updated to Android 11 with MIUI 12.1.3 and now when I get an incoming call, sliding up the button to answer the call doesn't work. The button sides up, the screen goes black for a few seconds, then the green button appears again, and sliding it up does nothing.
Someone else I know who has the Mi Note 10 had the same happen to them a few times.
Anyone else experiencing this? Any ideas how to fix it?
I should add that it's not just on the phone, but today I couldn't answer from my car's screen either. Pressing the Answer button on the car's screen could not make the Note answer the call.
Click to expand...
Click to collapse
Reset cache and data from the telephone app
joke19 said:
Reset cache and data from the telephone app
Click to expand...
Click to collapse
And working?
I just reset all the data, keeping my fingers crossed it fixes the problem.
Thanks!
Sadly, it keeps happening. It seems random, but about 40% of the time I keep hitting the answer button in the notification on top of the screen and nothing happens.
Or, the green Answer button will appear at the bottom of the screen, but when I slide it up, the screen goes blank and then the green button appears again. The call never gets answered.
Similarly, when I dial out, many of the calls would ring once and then it cuts off.
It's really frustrating. I am using Google-Fi.
The same is happening with me.
It happens when you're not connected to the wifi. It's a bug related to mobile data, when the mobile data is turned on you cannot receive calls neither decline them.
I have tried clearing data of dialer app, but it only works for a little time, then the bug again starts to act up.
The main bug is only for when you try to recieve or decline the call with sliding, you can answer the call from notification shade.
Solution: A temporary solution i found is when you're getting a phone call, turn off you mobile data then you can answer the call.