Related
Does anyone have an issue with your cheek pushing buttons while you are on the phone? I am running liberated_aria and whenever i am on the phone, my screen does not shut off like other phones and I end up either hanging up on people or moving widgets and even adding widgets..
has anyone else noticed this? is there a fix for it?
Its happened to me once on an Aosp rom. Haven't had any problems after that though.
Sent from my HTC Liberty using XDA App
I haven't had any problems. The proximity sensor is on the top right of the phone, where the AT&T logo is. Try making a call, to voicemail or something, and then waving your finger over the sensor. Does it ever turn the display off? Could be a software bug I suppose, or just a faulty sensor.
if you use your left hand/ear its pretty easy to dodge the sensor, unfortunately.
I tried a call using my right hand and I dont have that problem. Only the left.. I guess Ill have to start making all my calls right handed.
It figures...
Us southpaws always get the short end of the stick. FWIW, I almost always hold my phone(s) left handed, and only rarely seem to have this problem. ( It might just be that I have a huge head, and big ears. )
Im a righty and sometimes when making calls i get a haptic vibration from my face touching the nav buttons i think, nothing happens though.
My girlfreind is having the same issues with her handset.
We found her an Aria about 2 weeks ago at Best Buy Mobile for $1. They are running some great special for non-iphone handsets. The Aria was giving her problems and we ended up exchanging it. The 2nd Aria also has the same issue. While on the phone, her cheek will press random buttons and even hang up. Sometimes she just feels vibration, sometimes its a number pad press, and sometimes she just hangs up all of a sudden.
It seems to be some sort of sensor issue. Does anyone have some insight as to how to fix it? It's kinda of a big deal if the phone function is impaired by having to hold it away from your face.
Thanks!
NomeUF said:
My girlfreind is having the same issues with her handset.
We found her an Aria about 2 weeks ago at Best Buy Mobile for $1. They are running some great special for non-iphone handsets. The Aria was giving her problems and we ended up exchanging it. The 2nd Aria also has the same issue. While on the phone, her cheek will press random buttons and even hang up. Sometimes she just feels vibration, sometimes its a number pad press, and sometimes she just hangs up all of a sudden.
It seems to be some sort of sensor issue. Does anyone have some insight as to how to fix it? It's kinda of a big deal if the phone function is impaired by having to hold it away from your face.
Thanks!
Click to expand...
Click to collapse
Other then making sure her head is covering the sensor, she canlock the phone in mid call and it should stop her phone from registering her cheek while on a call
Sent from my Behold II using XDA App
ryan92084 said:
if you use your left hand/ear its pretty easy to dodge the sensor, unfortunately.
Click to expand...
Click to collapse
Huh. I'm a righty, but I talk left hand / left ear, and I never have any problems. Do you tilt the phone in some strange way?
Sent from my HTC Liberty using XDA App
psychoace said:
Other then making sure her head is covering the sensor, she canlock the phone in mid call and it should stop her phone from registering her cheek while on a call
Sent from my Behold II using XDA App
Click to expand...
Click to collapse
Thats a good idea. Thanks.
This issue is really pissing me off. I love this phone a lot but the proximity sensor is not working as it should, atleast with my head shape.
Seems almost in every other call I make/receive my cheek contacts the screen and pushes something because the proximity sensor is not detecting me head.
I've tried locking the phone with the button on top of the phone but that does not work, it's only temporary until the proximity kicks back in.
And, the funny thing is, when I try to "test" it out or replicate the situation I can never seem to do it again! It always happens unexpectedly.
I'm in the same boat with this too, but it's a hit or miss thing and really could be much worse.
Sent from my HTC Liberty using XDA App
i can't say i've ever run into this specific problem. i've actually been impressed with how well the sensor has been working.
i would agree with the previous poster who suggested to lock the screen once the call is active. make your call then tap the power button to lock the screen and that should help you avoid the issue.
mattbollenbach said:
i can't say i've ever run into this specific problem. i've actually been impressed with how well the sensor has been working.
i would agree with the previous poster who suggested to lock the screen once the call is active. make your call then tap the power button to lock the screen and that should help you avoid the issue.
Click to expand...
Click to collapse
This doesn't work unfortunately.
Sent by Aria
Just wanna ask if there is any temporary fix to the proximity sensor of nexus 4.
During calls the screen doesn't turn off when placed close to the face.
I didn't get the chance to test it on stock 4.2 because when i turned my phone on it updated first to 4.2.1. Ever since then it has had proximity sensor not working during calls.
And i have never had any screen protectors on the screen.
Tried many custom ROMS as well but no difference at all.
Sent from my Nexus 4 using xda premium
how about kernals could be a bug in franco.
return it to 100% stock make sure its still doing it under those conditions then if it is contact Google and ask for an RMA this is probably your best course of action. if it has been like this since you pulled it out of the box then contact google right now and tell them the proxmity sensor is clearly broken
I have this issue too, but I'm on CM. Not sure if it's CM being a problem. Can someone on STOCK comment?
BTW as for screen protectors, unless you have a giant bubble or crap on your protector or underneath in the adhesive layer, the proximity sensor should perform fine. Before you blame my screen protector, I downloaded a proximity sensor app to show the readout. The screen protector with no cutout is fine. It's not optimal to have one like that, but the proximity sensor works fine.
isnt there a proximity senor app which lets you test it on the market?
dmo580 said:
I have this issue too, but I'm on CM. Not sure if it's CM being a problem. Can someone on STOCK comment?
Click to expand...
Click to collapse
Using stock. No issues on the sensor. Turns off on calls and turns on when I remove from the face. Have a spigen protector on with a cutout for it
Sent from my Nexus 4 using Tapatalk 2
dmo580 said:
I have this issue too, but I'm on CM. Not sure if it's CM being a problem. Can someone on STOCK comment?
BTW as for screen protectors, unless you have a giant bubble or crap on your protector or underneath in the adhesive layer, the proximity sensor should perform fine. Before you blame my screen protector, I downloaded a proximity sensor app to show the readout. The screen protector with no cutout is fine. It's not optimal to have one like that, but the proximity sensor works fine.
Click to expand...
Click to collapse
I was on stock 2 weeks ago when I started noticing it.
I am on cm now as well and its very much messed up.
Sent from my Nexus 4 using xda premium
bobola said:
isnt there a proximity senor app which lets you test it on the market?
Click to expand...
Click to collapse
There is.
I've installed and tested.
According to the app results, The proximity sensor seems to know when my hand is on it and when its off it. The value changes from 1.0 to 2.0
It just won't work on phone calls.
Sent from my Nexus 4 using xda premium
noobdeagle said:
how about kernals could be a bug in franco.
return it to 100% stock make sure its still doing it under those conditions then if it is contact Google and ask for an RMA this is probably your best course of action. if it has been like this since you pulled it out of the box then contact google right now and tell them the proxmity sensor is clearly broken
Click to expand...
Click to collapse
It doesn't seem to be a hardware issue.
Sensor tests were made and the proximity sensor picks up when my thumb is placed on it.
Problem is on phone calls alone. Right from stock ROM to CM, PA, Xylon, AOKP, almost all of the ROMs.
Sent from my Nexus 4 using xda premium
slimldj said:
It doesn't seem to be a hardware issue.
Sensor tests were made and the proximity sensor picks up when my thumb is placed on it.
Problem is on phone calls alone. Right from stock ROM to CM, PA, Xylon, AOKP, almost all of the ROMs.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Mine is stock and during calls it usually goes to my settings menu and changes my clock setting. When I get off the phone, screen is blank and I hit power button to end call. Still annoying at times when the clock changes.
any luck with finding a fix for the proximity sensor? Mine never works when I'm in a phone call. I have to either wait for the call to end or reset the phone by holding the power button to end the call.
feedmylittletroll said:
any luck with finding a fix for the proximity sensor? Mine never works when I'm in a phone call. I have to either wait for the call to end or reset the phone by holding the power button to end the call.
Click to expand...
Click to collapse
I think it's a bug and not a hardware issue. Perhaps one of the other reason for having a new factory image soon.
Sent from my Nexus 4 using xda premium
feedmylittletroll said:
any luck with finding a fix for the proximity sensor? Mine never works when I'm in a phone call. I have to either wait for the call to end or reset the phone by holding the power button to end the call.
Click to expand...
Click to collapse
I'm suffering this same problem too, hope they fix it soon..
slimldj said:
I think it's a bug and not a hardware issue. Perhaps one of the other reason for having a new factory image soon.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Yes I think the fact that the app testing showed the sensor working so it points to software. Something is missing when the phone is in a call its not connecting to turn off. I thing Jellybean was flawed in many ways. My drop down brightness slider doesn't work for me nor auto brightness its OK for me cause I don't use either but still makes me mad.
Using Tapatalk 2
meetoo
Same problem here. Nexus 4. Stock Android 4.2.1. No screen protector installed.
While I'm in a call - the proximity sensor seems to work, as the screen goes dark... but at the end of the call when removing the phone away from my face, the screen does not come back on - making it impossible to hang up on the call (unless the caller on the other end hangs up first). It also makes it difficult to impossible to switch to and from speakerphone in the middle of a call.
Pushing the power button when this happens doesn't wake the screen either... sometimes it flashes but then goes black again. It doesn't happen on every call... maybe 75% of the time it does happen though. I've installed the proximity sensor app and it seems to recognize "covered" and "uncovered" states correctly when I cover the sensor at the top left corner of the phone while not in a call... so I'm thinking this is actually a software issue with the sensor and not a hardware issue. Drives me nuts though.
I've set "accessibility settings" to have the power button hang up calls as a temporary workaround... we'll see how that works.
treaty said:
Same problem here. Nexus 4. Stock Android 4.2.1. No screen protector installed.
While I'm in a call - the proximity sensor seems to work, as the screen goes dark... but at the end of the call when removing the phone away from my face, the screen does not come back on - making it impossible to hang up on the call (unless the caller on the other end hangs up first). It also makes it difficult to impossible to switch to and from speakerphone in the middle of a call.
Pushing the power button when this happens doesn't wake the screen either... sometimes it flashes but then goes black again. It doesn't happen on every call... maybe 75% of the time it does happen though. I've installed the proximity sensor app and it seems to recognize "covered" and "uncovered" states correctly when I cover the sensor at the top left corner of the phone while not in a call... so I'm thinking this is actually a software issue with the sensor and not a hardware issue. Drives me nuts though.
I've set "accessibility settings" to have the power button hang up calls as a temporary workaround... we'll see how that works.
Click to expand...
Click to collapse
Having the exact same issue here too on stock ROM.
Good idea on the accessibility settings! Will work until/if they fix it..
Also no screen protector.
I had the opposite problem to this where my screen would stay off during a call and I have to force restart to regain control.
Turns out it was the rubbish screen protector causing the issue. This was quickly fixed by cutting the screen protector so that the sensor was uncovered.
Dav_prime said:
I had the opposite problem to this where my screen would stay off during a call and I have to force restart to regain control.
Turns out it was the rubbish screen protector causing the issue. This was quickly fixed by cutting the screen protector so that the sensor was uncovered.
Click to expand...
Click to collapse
It was the same fix for mine when I first got my bse it worked fine for about a week but then over time it got worse. It was the screen protector just that lil bit worth of it wear caused enough blockage of the sensor. I got some new bse's and they now have a cutout for the proximity sensor and are screen optimized.
Sent from my Nexus 4 using Xparent Blue Tapatalk 2
use Proximity Actions by Novum Inceptum in playstore
rat99 said:
use Proximity Actions by Novum Inceptum in playstore
Click to expand...
Click to collapse
That won't fix anything.
Hello guys! After a long search on the recent questions in this amazing forum I couldn't find anything similar to my girlfriend problem...
Her Nexus 4 was just fine until the update to 4.3.. After that it started to show a problem during/after calls, the screen turns black completely (even when is not near the face or anything) and its impossible to do anything with the phone after that. Power button doesn't work, and there is only two ways to get the phone working again: the other person hang up the call.. or to hard press the power button until the restart...
I tried already to change for a 4.3 ROM and now I changed it to a 4.2.2 ROM... any idea or suggestions to a possible solution?
Thanks a lot guys!
I too recently had this problem. There was a simple fix after dealing with it a couple of days. My 4yo daughter had been playing with my phone after which I started having the problem. What I found was one of her hairs had become stuck in the bumper and was resting on the screen over the proximity sensor. Once I cleared that, no more problem.
The sensor is on the upper left of the screen.
Sent from my Nexus 4 using Tapatalk 4
If You use screen protector and it goes over sensors, than will be the reason of Your problem. Just remove it.
It could be the 4.3 update. I didn't have any such issues until the update and then they began. AndroSensor confirms that no matter what, proximity sensor is at 0.
Any thoughts on what to do short of RMA?
--Dan
I can assure you its your screen guard that is creating an occlusion for your sensor on top left. Remove it and it will definitely work.
vasusharma.28 said:
I can assure you its your screen guard that is creating an occlusion for your sensor on top left. Remove it and it will definitely work.
Click to expand...
Click to collapse
Not sure if I mentioned it earlier (perhaps in another thread) - no screen guard. That wasn't the issue. Finally, I changed the proximity sensor itself, all bueno. No RMA which means avoiding a bunch of hassles (namely new phone, data xfer, etc).
--Dan
Hello to all.
I have this wierd problem. While I am on a call if I put the phone on my face it turns black. Then when I put it off and it lights up BUT then the HOME button and the right and left virtual buttons stop working ! I can only end the call.
If I do the same but without touching the proximity sensor everything works fine . The problem begins after the use of proximity sensor. Could this be softare or hardware? Anyone else with this problem? Any advice on this?
Doing a hard reset seems to fix the problem. Maybe it was a conflict with some app...thank you though.
Sent from my SM-N9005 using Tapatalk
Hello folks, I noticed that during calls the screen does not behave the way it should and turn itself on/off depending on how close it is to your face. It simply turns off as soon as you click the call button and stays off until you press home/power button. I did a factory reset, which didn't help.
I am suspecting that the proximity sensor broke. Running stock nonrooted firmware.
Would like your input as to whether Samsung will be more inclined to repair or fix this device?
The note 3 is from Rogers Canada in Toronto
Thanks
mediumsteak said:
Hello folks, I noticed that during calls the screen does not behave the way it should and turn itself on/off depending on how close it is to your face. It simply turns off as soon as you click the call button and stays off until you press home/power button. I did a factory reset, which didn't help.
I am suspecting that the proximity sensor broke. Running stock nonrooted firmware.
Would like your input as to whether Samsung will be more inclined to repair or fix this device?
The note 3 is from Rogers Canada in Toronto
Thanks[/QUOTE
It's a bug that happen for note 3. You can try the fixed from this thread, post #18 to caliberate the proximity sensor. This
method did fixed a lot of note 3 same problem as yours
http://forum.xda-developers.com/showthread.php?t=2488031&page=2
Click to expand...
Click to collapse
ZION959 said:
mediumsteak said:
Hello folks, I noticed that during calls the screen does not behave the way it should and turn itself on/off depending on how close it is to your face. It simply turns off as soon as you click the call button and stays off until you press home/power button. I did a factory reset, which didn't help.
I am suspecting that the proximity sensor broke. Running stock nonrooted firmware.
Would like your input as to whether Samsung will be more inclined to repair or fix this device?
The note 3 is from Rogers Canada in Toronto
Thanks[/QUOTE
It's a bug that happen for note 3. You can try the fixed from this thread, post #18 to caliberate the proximity sensor. This
method did fixed a lot of note 3 same problem as yours
http://forum.xda-developers.com/showthread.php?t=2488031&page=2
Click to expand...
Click to collapse
You sir are a gentlman and a scholar. Thank you very much. I shall decide whether to root and fix this myself, or to contact Samsung and obtain a new device.
Though I do want a new phone just for the heck of it, I think this method would be the easier way out.
Thanks again
Click to expand...
Click to collapse
Hello,
I have the same "problem",
I asked Samsung in the Netherlands, what could cause this problem. (so please do not shoot me for having it wrong)
and they stated, that this was not a faullt.
in case you were having a phone call,and the touchscreen stayed turned on, that there was a possibility, that you're ear could make contact with the touchscreen, and for instance could disconnect youre phone call or putt in on hold.
Kind regards, Wiebe
mediumsteak said:
Hello folks, I noticed that during calls the screen does not behave the way it should and turn itself on/off depending on how close it is to your face. It simply turns off as soon as you click the call button and stays off until you press home/power button. I did a factory reset, which didn't help.
I am suspecting that the proximity sensor broke. Running stock nonrooted firmware.
Would like your input as to whether Samsung will be more inclined to repair or fix this device?
The note 3 is from Rogers Canada in Toronto
Thanks
Click to expand...
Click to collapse
This happens to me daily but I don't want to change my phone for nothing... Or should I? Anyway....the first time I blew some air into the speaker grill up top and then wiped the sensor clean . Solved the issue . You can check this out by going into the service menu by dialing*#0*# and going to sensor . You'll figure it out from there . Now when It happens I just wipe it clean or I just blow some air again. Hope this helps !
I had a same problem with my galaxy s4 before, I was going crazy exchanged 2-3 times within a month, then I read someware that if you blow on the earpiece it fixes the problem, because the earpice is very close to the proximity sensor so from earpice dust gets in there and the proximity starts giving problems. So try to blow on the earpice cuple of times see if it works. It worked for me.
Sent from my SM-N900T using xda premium
Yep, blow into the earpiece in the direction of the sensor. (to the right towards the powerbutton side of the phone.) Alternatively, use an air compressor or a can of dust cleaner from an electronics store.
If that does't work, what you can try is to set 'turn off screen during calls' under phone --> call settings to disabled, that way you manually turn off the screen with the power button. (you will need to disable 'end calls using power button' if you have it enabled.)
It's not ideal, but that way you can at least have the screen on during calls.
wiebew said:
Hello,
I have the same "problem",
I asked Samsung in the Netherlands, what could cause this problem. (so please do not shoot me for having it wrong)
and they stated, that this was not a faullt.
in case you were having a phone call,and the touchscreen stayed turned on, that there was a possibility, that you're ear could make contact with the touchscreen, and for instance could disconnect youre phone call or putt in on hold.
Kind regards, Wiebe
Click to expand...
Click to collapse
Dat klopt, dat is waar de nabijheidssensor voor dient, om het scherm uit te schakelen als je oor in de buurt van de telefoon komt. Bel maar eens en hou je vinger op de twee sensors naast de speaker aan de bovenkant van het scherm; dan gaat het scherm uit.
Het probleem dat de OP heeft, is dat het scherm meteen uit gaat, ook al is er niets in de buurt van de sensor. En dat hoort niet.
English:
You are partly correct. That's why the proximity sensor disables the screen when the ear get into close proximity. Try dialing someone, then press your finger over the two sensors to the right of the speaker at the top of the screen; the screen will turn off.
The problem the OP has, is that the screen turns off immediately, even if there is nothing in proximity of the sensor. That's not how it should be.
samomamo said:
I had a same problem with my galaxy s4 before, I was going crazy exchanged 2-3 times within a month, then I read someware that if you blow on the earpiece it fixes the problem, because the earpice is very close to the proximity sensor so from earpice dust gets in there and the proximity starts giving problems. So try to blow on the earpice cuple of times see if it works. It worked for me.
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
I tried blowing air AND using a compressed air canister. Looks like the dust particles are wedged in there for good.
Running sensor check from the *#0*# tells me that the ADC value is 150 with nothing in front of the screen and 1004 with my hand over it.
It's a common issue of the last mj7 mk2 roms.. it's "normal"
mediumsteak said:
I tried blowing air AND using a compressed air canister. Looks like the dust particles are wedged in there for good.
Running sensor check from the *#0*# tells me that the ADC value is 150 with nothing in front of the screen and 1004 with my hand over it.
Click to expand...
Click to collapse
it should go under 80 to turn on and over some high value to turn off . 150 is kinda a lot... there is def something there inside...
@ShadowLea and all others,
Thank you veyr much for the answers, merry christmas