My nexus 4 Lollipop 5.1 Seems to have a problem when I make a call. I hit the phone symbol, select the number I want to call from my requent call list. I hit the dial button and make the call........ The problem comes when I go to end the call the screen goes black such that I can end the call. I just have a black screen........
Does anyone out there have any idea whats happening and what the fix may be?
Thanks for any help
Remove your screen protector.
Blacksmith5 said:
My nexus 4 Lollipop 5.1 Seems to have a problem when I make a call. I hit the phone symbol, select the number I want to call from my requent call list. I hit the dial button and make the call........ The problem comes when I go to end the call the screen goes black such that I can end the call. I just have a black screen........ Does anyone out there have any idea whats happening and what the fix may be? Thanks for any help
Click to expand...
Click to collapse
The screen is supposed to go black when you make a call--or, rather, when you place the phone to your ear. There is a "proximity detector" along the top edge of the screen, and it detects your ear when your ear gets close. The phone then turns off the screen sensors so that your ear or your cheek doesn't push any buttons while you are talking, and turns off the screen illumination for aesthetic reasons. However, the proximity detector is supposed to cause the screen to turn back on when you remove the phone from your ear. That isn't happening for you. When it didn't happen for me, I took it to the shop. The tech said the proximity detector was broken, and ordered a new one. But replacing the proximity detector didn't help. He finally disabled the sensor so that proximity was never detected. that worked.
This story does not have a happy ending for me. The phone worked for a couple of days. Then I tried to reboot, and it went in to a boot loop. None of the standard cures for a boot loop is helping me. I doubt if the two problems are connected.
Proximity sensor turns off screen when you put it to your ear to avoid your skin touching the "End call" button or something else
kbakalar said:
The screen is supposed to go black when you make a call--or, rather, when you place the phone to your ear. There is a "proximity detector" along the top edge of the screen, and it detects your ear when your ear gets close. The phone then turns off the screen sensors so that your ear or your cheek doesn't push any buttons while you are talking, and turns off the screen illumination for aesthetic reasons. However, the proximity detector is supposed to cause the screen to turn back on when you remove the phone from your ear. That isn't happening for you. When it didn't happen for me, I took it to the shop. The tech said the proximity detector was broken, and ordered a new one. But replacing the proximity detector didn't help. He finally disabled the sensor so that proximity was never detected. that worked.
This story does not have a happy ending for me. The phone worked for a couple of days. Then I tried to reboot, and it went in to a boot loop. None of the standard cures for a boot loop is helping me. I doubt if the two problems are connected.
Click to expand...
Click to collapse
Thanks for that info I had not thought about that... That may be cause of my problem.... I will have to figure out a solution
Thanks again
Didgeridoohan said:
Remove your screen protector.
Click to expand...
Click to collapse
I am not using a a "screen protector" But thanks for the input
Ok, was worth a shot...
Then you must likely have a faulty proximity sensor, as stated previously.
Download an app, like AndroSensor, and see what the output for the proximity sensor reads. When nothing is covering the sensor (top left corner) it should read 5 cm/2 inch, or something similar. If it reads 0, it's busted...
Didgeridoohan said:
Ok, was worth a shot...
Then you must likely have a faulty proximity sensor, as stated previously.
Download an app, like AndroSensor, and see what the output for the proximity sensor reads. When nothing is covering the sensor (top left corner) it should read 5 cm/2 inch, or something similar. If it reads 0, it's busted...
Click to expand...
Click to collapse
I did as you suggested and the results say 2" uncovered 0 when covered
Hmm... The plot thickens...
That means you have a working proximity sensor. No idea what it could be then.
Didgeridoohan said:
Hmm... The plot thickens...
That means you have a working proximity sensor. No idea what it could be then.
Click to expand...
Click to collapse
I'll keep looking for a solution.......... It's a pain especially if if I have to respond to a VM and hit a Number.......
Thanks again
I have the same issue. In my case, the proximity sensor may have been broken or blocked by dust.
My "temporary" solution is using the power button to disconnect calls. While using a Bluetooth headset, the screen can be turned on. I hope there is a better solution.
Man of La Mancha said:
I have the same issue. In my case, the proximity sensor may have been broken or blocked by dust.
My "temporary" solution is using the power button to disconnect calls. While using a Bluetooth headset, the screen can be turned on. I hope there is a better solution.
Click to expand...
Click to collapse
Yes I resetthings so I only have to hit the power button to end a call Thanks for all the help
Related
Hey friends,
I am facing this problem while making calls that as soon as I press call button or receive button(while taking call) the screen turns off n stay that way till the call ends.
I have tried pressing all hardware buttons,even moved the dvp awayfrom me n into direct light but to no avial.though it did turn on once or twice out of twenty times.
Did anyone else experience this? Any suggestions are welcome..
Sent from my HD7 T9292 using Board Express
Do you have a screen protector or case that is obscuring the light sensor or proximity sensor? My first guess is that something is obscuring one or both, because during a call the screen being off is a feature.
Arcarsenal said:
Do you have a screen protector or case that is obscuring the light sensor or proximity sensor? My first guess is that something is obscuring one or both, because during a call the screen being off is a feature.
Click to expand...
Click to collapse
i know about this feature n still have that plastic skin on the screen i'll remove it n check again don't think it d block light but then wats the harm?
screen stays black/off during call
The screen stays black during a call and this happens ramdomly. I have a dell venue pro a t mobile phone but it is a pre release so it works on att 3g and all. I have switched the sd card with no improvement. I have ordered a transender 32 gb sd that I haven't received yet. The firmware version 2250.1400.7004.025 hardware is 112.576.2.0 radio soft 2.2.50.14 radio hard 8250. I have been unable to get any of the hardware keys to hang up the phone which if I get voicemail or something means I have to power the phone down to get the dang thing to hang up. Sometimes it works fine but I cant find a commonality software or hardware that causes this. It happens right out of the box so even after a software reset it can happen. Is there any solution for this issue?
I can't understand why the button on top doesn't hang it up.
PS I got this phone for free and I got ripped off LOL
wow just got a replacement phone today and im having this problem, As soon as I go to make a call the screen goes black and cant do anything on screen during the call, so i cant enter my password when checking voicemail
I think it's related to the proximity sensor. When you put the phone close to your head, the screen switches off. When you move it away, it will switch on - most of the time .
If it stays black, have you tried tapping the power button on the top of the phone? It switches the screen on without disconnecting your call.
A coworker got a replacement the other day(they send a refurb) phone and it had the same problem. Had to go through Twitter to get Dell to send him a new retail phone since they had send him 3 refurbs prior and they all had different issues.
This is just a general statement regarding phone proximity sensors. I have had multiple phones made by different manufactures that experience this to some degree (including the Venue Pro). One thing that I have noticed is that if the phone goes from your face directly into a bright light (outside is most common) it will keep the screen shut off but if the sensor is somewhat shaded it will resume normal function.
I got the same problem too and while it may be a proximity sensor problem, it is not controllable on the user's end. Unless the phone call disconnects magically, a battery pull is necessary.
I'm gonna be on my third one soon and I hope that i won't face the same problem.
magicsquid said:
I think it's related to the proximity sensor. When you put the phone close to your head, the screen switches off. When you move it away, it will switch on - most of the time .
If it stays black, have you tried tapping the power button on the top of the phone? It switches the screen on without disconnecting your call.
Click to expand...
Click to collapse
Yes i recently got a new refurbed phone and this problem has arised. Complained to Dell and they are going to send me a Brand new DVP. I see a lot of people having this same issue with the refurbs. Currently Dell is out of new DVP due to them upgraing the firmware, so I have to deal with a broke phone till the end of August. Talk about a dissatisfied customer. Im thinking about selling this brand new unit when I get it, hopefully Toshiba has their device out by then
This is a Proximity Sensor issue. You can fix it though in the EM app. You can adjust the sensor readings and the phone will function like normal. Let me know if you need the values or a step by step!
theusername said:
This is a Proximity Sensor issue. You can fix it though in the EM app. You can adjust the sensor readings and the phone will function like normal. Let me know if you need the values or a step by step!
Click to expand...
Click to collapse
please explain because im getting frustrated
theusername said:
This is a Proximity Sensor issue. You can fix it though in the EM app. You can adjust the sensor readings and the phone will function like normal. Let me know if you need the values or a step by step!
Click to expand...
Click to collapse
A step by step would be awesome. I like being able to see the screen during a call.
1) Get the EM app, if you dont have it dial ##634# into the dialer
2) Get into the advanced menu by double tapping the black area and typing in "qwertyuiop"
3) Select "RD test", now enter *#6336# in the box that pops up.
4) Select "Sensors", and the "Proximity Sensor Config"
5) Set the following to these:
LED strength - 1
Diode select - 2
Pulse Count - 43
6) Hit set and then you are good to go!
I have noticed that one of my DVP's needs to have this put in again everytime I reboot the phone, the other saves it. Just an FYI for ya!
I get to step 3 and when i clock on RD test, I am prompted with a white box with blue trim and an X at the top right. can you advise on how to proceed?
Oh yeah, Im sorry I forgot that part. Enter *#6336# as the password.
When I dial *#634# it says thic code is not supported.
What does that mean?
I put in a different number combo before and it put me in the EM screen
937dytboi said:
When I dial *#634# it says thic code is not supported.
What does that mean?
I put in a different number combo before and it put me in the EM screen
Click to expand...
Click to collapse
Try ##634#, Im made a typo there and put a * the first time.
did the steps and it didnt work for me am i doing something wrong
937dytboi said:
did the steps and it didnt work for me am i doing something wrong
Click to expand...
Click to collapse
I dont know, you could just have a defective phone. I know thats hard to believe that from Dell.....
This has been happening pre and post Nodo on my focus. If i'm on a phone call for at least a few minutes, then pull the phone away from my head, the phone's display should become active, but it isn't.
Anyone else having this issue or is it time to exchange the phone?
I have the same issue also it seems like I have to press the power button a couple of times to get it back.
Sent from my SGH-i917 using XDA Windows Phone 7 App
I'm also having this issue. Anyone remember if ther were having it pre-Nodo? Just wondering if the update changed something.
Regardless, it's a bit of a PITA.
I experienced this after having to replace a cracked screen. I just recalibrated the proximity sensor with my finger about an inch away and it worked fine.
ArcWhistler said:
I experienced this after having to replace a cracked screen. I just recalibrated the proximity sensor with my finger about an inch away and it worked fine.
Click to expand...
Click to collapse
How did you do that?
Yeah, ditto that - how do recalibrate the sensor?
Samsung Diagnostic App.
http://forum.xda-developers.com/showthread.php?t=839154
I was pecking around the screens months ago, and there was one bank of tests (multi-touch, red, green, blue, white, battery, etc, etc) that allowed setting and viewing the proximity sensor.
I remember playing with moving my hand closer, and further and watching it change from sensed to clear.
Sorry, can't remember which codes now.
I used the Wiki:
http://forum.xda-developers.com/wiki/index.php?title=Samsung_Focus
LCD Test - *#0*#
Ok, mine says No Detection. Is there anyway to set the value?
One other thing to note, about the samsung focus specific update regarding disabling the touch sensitive buttons while in a program, that also isn't working for me either. Not sure if they are related, but thought I'd throw it out there.
And as far as calibrating goes, not sure it would help since the problem only occurs while I'm on a longer phone call. On short ones the proximity sensor works just fine.
If you move your finger closer to the sensor, it should eventually change to Detected. The "set" button at the bottom should set the proximity sensor to the new distance. Mine is around 75.
ArcWhistler said:
If you move your finger closer to the sensor, it should eventually change to Detected. The "set" button at the bottom should set the proximity sensor to the new distance. Mine is around 75.
Click to expand...
Click to collapse
Mine says No Dectection. It has Prox Sensor: XXX I've taken my entire hand and covered my phone. NOTHING. When I push SET, It says ProxThreshold :0. Is there anyway to set it manually?
samsung focus post nodo
I believe the prox sensor issue is happening post nodo, I have never had this problem prior to the update... I have been able to fix it temporarily by pulling the battery and starting it up... don't know how long the fix works... got to do some testing... I am wondering if its a power thing as the screen wouldnt work when you plugged it in to power and had on a soft surface....
Still nothing. I didn't want to hard reset since I have Chevron installed. For some reason I did four updates on my phone and don't have a single backup. If I hard reset I'm S.O.L. with Twin Blades and other homebrew apps
What value does it show when you press the Reg button?
I've had issues with my earring tapping the screen while I talk and I had it fixed before NoDo, but the values reset when it was installed, they also appear to be different values now as my screen got supper finicky after the update. I was constantly hanging up or scrolling through multiple pages of stuff with my ear and you could see the screen turning on and off. I ran the proximity calibration while holding my hand in front and set to it to 1.
If it shows xx have you tried setting the value with nothing in front of the phone to see if it will at least zero out?
BooR4dley said:
What value does it show when you press the Reg button?
I've had issues with my earring tapping the screen while I talk and I had it fixed before NoDo, but the values reset when it was installed, they also appear to be different values now as my screen got supper finicky after the update. I was constantly hanging up or scrolling through multiple pages of stuff with my ear and you could see the screen turning on and off. I ran the proximity calibration while holding my hand in front and set to it to 1.
If it shows xx have you tried setting the value with nothing in front of the phone to see if it will at least zero out?
Click to expand...
Click to collapse
It has a big red box. It says No Detection. Prox Sensor:XXX Do I press Set or Reg?
another thing is wrong
seems like my light sensor is fried as well... I am starting to wonder if it's because of bad placement of the usb port... both lay right in front of the port, can't imagine pluging in and unpluging the phone would help if the sensors are right in front. I can't get either sensors to work anymore, even with a battery pull... does anyone else have this issue? goto the diagnosis menu and type
*#05#
you should be able to run through all the tests, I skip the feedback loop... Start at 1 and work your way through.
My Prox sensor says, no sensor XXX, and my light sensor is stuck with a value and will not change even when I cover the sensor... looks like a warranty replacement... how does this work with a sd card installed, the official WP7 ATT certified 8GB? Anyone else have to do this?
rockclimbaudiextreme said:
seems like my light sensor is fried as well... I am starting to wonder if it's because of bad placement of the usb port... both lay right in front of the port, can't imagine pluging in and unpluging the phone would help if the sensors are right in front. I can't get either sensors to work anymore, even with a battery pull... does anyone else have this issue? goto the diagnosis menu and type
*#05#
you should be able to run through all the tests, I skip the feedback loop... Start at 1 and work your way through.
My Prox sensor says, no sensor XXX, and my light sensor is stuck with a value and will not change even when I cover the sensor... looks like a warranty replacement... how does this work with a sd card installed, the official WP7 ATT certified 8GB? Anyone else have to do this?
Click to expand...
Click to collapse
same problem here. seems like those two sensors are burned
On my AT&T Galaxy S4, when I make a call the screen goes black when my face is next to the phone. This is good.
However, when I take my face away the screen will NOT turn back on. If I hit the [Power] or [Home] buttons, it will sometimes turn back on, but often times it requires several presses or requires me to wait several seconds until the phone turns back on.
I've tested this on stock and several ROMs...
Does anybody else have this problem?
If so, how do I fix it?
Pick up a can of compressed air and blow in the earphone. Sure enough the proximity sensor works perfectly now. I have solved this problem doing this. Tell me something
Enviado desde mi GT-I9505 usando Tapatalk
Dial *#0*#
You can test your proximity sensor readings here. It should turn the screen green and vibrate the phone constantly while your hand is in proximity. You can also see the numerical readings. The sensor works to about 6 inches.
If its not acting right, then you need to use faux kernel or you have a hardware failure.
If it is acting right, then use a better rom.
I seem to be having this issue on stock rom. When I bring my hand close to the sensor in diagnostic mode it goes green...but it doesn't stop when I remove my hand and there's nothing nearby. This seems to mirror the experience...where the phone goes black during a call, but doesn't wake up when it's removed.
faiyo said:
Dial *#0*#
You can test your proximity sensor readings here. It should turn the screen green and vibrate the phone constantly while your hand is in proximity. You can also see the numerical readings. The sensor works to about 6 inches.
If its not acting right, then you need to use faux kernel or you have a hardware failure.
If it is acting right, then use a better rom.
Click to expand...
Click to collapse
Hubris2 said:
I seem to be having this issue on stock rom. When I bring my hand close to the sensor in diagnostic mode it goes green...but it doesn't stop when I remove my hand and there's nothing nearby. This seems to mirror the experience...where the phone goes black during a call, but doesn't wake up when it's removed.
Click to expand...
Click to collapse
Yes, exactly!
I've flashed back to stock and tried that test screen. The sensor is OK at first, then I move my hand over it and it turns green and stays that way even after I remove my hand.
It seems like the sensor is half-working but gets stuck in the "on" position...
that sucks. i guess its time to contact samsung about warranty. just make sure theres no dirt on the sensor or anything
rpboronat said:
Pick up a can of compressed air and blow in the earphone. Sure enough the proximity sensor works perfectly now. I have solved this problem doing this. Tell me something
Enviado desde mi GT-I9505 usando Tapatalk
Click to expand...
Click to collapse
This is exactly what I done only I used a straw and I blew down it like hell and it cleared the problem. My phone was due to be returned to be fixed under warranty today but I tried a last ditch attempt and with the straw and blowing down it into the earpiece (aimed slightly towards the proximity sensor) I managed to sort the problem. It seems a little dirt or dust gets on the sensor and makes it malfunction.
Give it a whirl to see if it will work
I bought a used V20 with a defective screen. I change it, everything work for fine, but i notice a strange behaviour with the second screen.
The second screen is always on and i can unlock it by only touching the finger print sensor. BUT at night (or in the dark), the second screen turn off and i need to press 2 times on the power button to wake the phone.
The Knock On feature doesn't work too in the dark.
The light sensor seems to work correctly.
I would love to post a video but i can't......
This is an issue or it is normal ??
Thanks for your help !
Sounds like Doze.
I don't find anything related to Doze or "standby" about this screen.
check "daily timeout" on Show when main screen off. Seem u turn this function on at night
David_26 said:
I bought a used V20 with a defective screen. I change it, everything work for fine, but i notice a strange behaviour with the second screen.
The second screen is always on and i can unlock it by only touching the finger print sensor. BUT at night (or in the dark), the second screen turn off and i need to press 2 times on the power button to wake the phone.
The Knock On feature doesn't work too in the dark.
The light sensor seems to work correctly.
I would love to post a video but i can't......
This is an issue or it is normal ??
Thanks for your help !
Click to expand...
Click to collapse
thophan1975 said:
check "daily timeout" on Show when main screen off. Seem u turn this function on at night
Click to expand...
Click to collapse
Don't seems to change anything
Could it me the last security update ??
I reset the phone today and same "issue"
David_26 said:
Don't seems to change anything
Could it me the last security update ??
I reset the phone today and same "issue"
Click to expand...
Click to collapse
Sounds like there is an issue with the proximity sensor (not light sensor).
It's setup to turn the second screen off as well as disable knock on if the phone is in your pocket. Even during daylight hours if you put your finger within an inch of the sensor when the main screen is off, it should trigger it.
It seems your sensor may just be messed up.
David_26 said:
Don't seems to change anything
Could it me the last security update ??
I reset the phone today and same "issue"
Click to expand...
Click to collapse
There are a few apps on the play store you can try to fix it if you are rooted. You could also try a sensor app to see if the proximity sensor is showing feedback properly although you might need to be rooted for the apps to show the proximity sensor properly (not sure). My note 4 had a hardware test in the service menu not sure how to do it on V20 though.
Same Issue
Edit: Resolved the issue. Please read this post. There is a small rubber gasket-type thing that sits in the hole of the phone's frame where the proximity sensor is positioned. That rubber gasket was not included with my replacement screen. I pulled the rubber piece out of my original, broken screen, and installed it into my replacement screen. I am no longer having issues with the phone in the dark.
I am experiencing the same issue. I have a T-Mobile LG v20 (H918) and I cracked the screen last week. I ordered a replacement LCD assembly and installed it myself. Everything works fine during the day or in a well lit room, but at night, in a dark room, I experience all of the issues you are reporting. I am finding other posts online with our same issue, but as of yet, no resolution.
Even though the second screen is set to always be on, at night, in a dark room, it turns off almost immediately after locking the phone. It is almost as if the phone is in a "deep sleep" or something, because the following also occurs:
Knock On will not wake the phone
Fingerprint sensor will not wake the phone
Even connecting to the phone via AirDroid / AirMirror the phone doesn't wake
Need to press the power button multiple times to wake phone
Providing a light source immediately turns on second screen and resolves all issues
Hi!
I"m not the only having the problem: during a call unintended taps takes place while screen waking up is not registered during the call. So, you see, I'm not sure a proximity sensor is the reason of the problem as far as screen is kept turned off.
I have tried to reproduce the issue by fingers, but wasn't lucky.
Have you any ideas how to eliminate the problem?
I mean not-rooted official up-to-date stock firmware use case.
And, by the way, I haven't found proximity sensor calibration in service menu for A1. Is it placed somewhere into another place?
That happens to me all the time too.
Yup, me too. While in call I sometimes unknowingly turn on the flashlight and probably look like an idiot. ?
With the rn3p I would constantly end up muted. With mi a1 the problem is much less although I've noticed that numbers are still pressed. I've learned over time to switch to keypad so when something gets touched it's not the mute and at worst the other person receives some key tones.
I also have this problem a lot. I mute myself 9/10. To bypass to problem, I just lock the screen before placing it against my ear.
Yes, a simple soutions is just when you call someone, imidiately press power button to lock the screen (no password or fingerprint requred to unlock)
dejano said:
Yes, a simple soutions is just when you call someone, imidiately press power button to lock the screen (no password or fingerprint requred to unlock)
Click to expand...
Click to collapse
That's what I've been doing. That and pushing the top part of the mobile on my face just to make sure. lol
Oh and use the Feedback app and send it to xiaomi and hope they fix it on the next update.
i had this problem too, has it been fixed in the latest of updates? its a really annoying bug.
You must be doing something wrong. This issue "must" have been in all smartphone operating systems in the world, if what you are saying is the truth.
There's no way to drop the call, or press anything while you are calling someone. The proximity sensor doesn't allow turning on the screen when it's close to an object. The gyroscope also turns off the screen when you rotate the phone vertically during a call.
But all I can say is that it's not a bug, this is how is your phone knows when you are in a call, and you put your phone to your ear, or when you use your "speaker", and so the phone knows it's supposed to used it's speaker to transfer voice through the call.
Beside my poor English, try to move your phone a bit vertically before putting it close to your ear.
same problem here, also disabling ambient display... i also tested proximity sensor with some apps and it seems ok
I have that problem too from the beginning. None of the updates came up with a solution
Same here: I mute, turn on the flashlight or even open apps sometimes with my face. And thanks for the input @SmallTarzan but i know how to operate a smartphone and did not have any similar problems for the last five years. Apart from that annoying bug it's a great phone.
Wow, i dont know of this bug since i'm using custom rom from very beginning.
Try to make a call then use your hand to cover top part of the phone, screen doesn't lock??
I am having this issue too and it is really annoying
And still nobody came up with a solution???
It's easy to understand why it happens.
Proximity activates while you're in a call, but apparently the touchscreen digitizer remains working (even though the screen is off). Touching the digitizer with your ears or cheeks activates different actions while you think your screen is locked.
I can't believe how this issue is not fixed yet! That's a shame!
Same applies for the network fluctuation issues. You need to either choose 3G or 4G to avoid loosing your data connection.
Xiaomi that's more than LAME! You need to be ashamed of yourselves.
It happens to me quite often, although not always.
It's more frequent during long calls. If the call lasts for less than a minute or so, it doesn't happen.
Proximity sensor works, and screen turns off as soon as I put it at my ear.
Keyboard is off and not responding for a while. Then, all of a sudden the phone comes alive.
In my case it's not the torch. What I activate unknowingly is the handsfree loudspeaker, which can be even more embarrassing, sometimes.
Maybe it's because I am left-handed.
In an attempt to have the proximity sensor fully covered by my face, I tried to make calls by holding the phone with my right hand, but to no avail, after some time the screen wakes up regardless of everything.
Happens to me too. Although I did notice some differences regarding the position of the phone on my ear or which side of my head I put the phone on, I started pressing the power button long ago to turn the screen off. It may not be ideal, but it takes care of it.
AlaiSalaam said:
Happens to me too. Although I did notice some differences regarding the position of the phone on my ear or which side of my head I put the phone on, I started pressing the power button long ago to turn the screen off. It may not be ideal, but it takes care of it.
Click to expand...
Click to collapse
Try this app, some users say it helps.
https://play.google.com/store/apps/details?id=ss.proximityservice
Any fixes yet?
simontol said:
Any fixes yet?
Click to expand...
Click to collapse
None, same sh**