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
Howdy.
On the Model: SM-N900W8" Bell Galaxy Note 3
Basically when in call, Here is a problem that is reoccuring for the past few weeks ever since a couple over the air (ota?) updates I have received compliments of google.
Enabled right now, via "call settings" = "Turn off screen during calls" is CHECKED with Green checkmark.
Just handset call, moving handset to ear to talk. Handset goes black. When removing handset from ear to click hangup, or press buttons, ie to "see" the screen... screen is continually black. - Fix = PRESS HOME BUTTON... brings screen up...
When on speaker phone call, screen is lit. Move hand to the first of 2 sensor circles by the main earpiece part, screen goes black, but does not return on.
I have tried *#0*#. = "Connection problem or invalid MMI Code". - However try again, and I get red green blue receiver etc etc.
I clicked "sensor hub test" and it went BLACK.
I had to click home button, unlock screen, and I get a white with black text stating that..
INT Check: OK
FirmwareCheck
MCU Firm Version : ST0113090300
Bin Firm Version : ST0113090300
MCU Name: STM32F401CCY6B
"blue letters" PASS
I don't see how it passed, a screen went black, did not return, just went black..
Hit the back button. Tried "TSP HOVERING". That works fancy, drawing green squares everywhere...
Under "SENSOR"
I move the hand over proxmimity sensor - ACD goes to 1000+ when I put my finger over it and the screen goes green with black fonts of the prox, acceler, barometer, lights, etc...
Prox is native when sitting still anywhere from 80-95 averages for ACD
Proximity is 0.0 and TSP Color ID: 00
The different tests are rather cool to try, but not helpful in solving my issue...
What I have done: Use a lcd led plasma tv screen cleaner from nexxtech for non streaking. A cloth that came to clean my glasses I have to clean the screen. It is streak free. I have used compressed air to thoroughly blow the area around the upper speaker / sensors and even had the battery out / cover off, etc and blown every hole around the phone.
I still cannot solve this issue of black screening.
The only resolution which leads my ear to "hang up calls accidentally" is to "un check" ie single box, no checkmark, the "turn off screen during calls" option.... ie disable that sensor thing...
I have hard booted, rebooted, cleaned, etc...
Suggestions?
I have the same problem, hoping I won't have to send my device to the service because it's a pain in my country and I will be without a phone for more than a week.
Anyone know any fix for this?
Sent from my SM-N9005 using Tapatalk
Does anyone have an idea on this yet?
See here:
http://forums.androidcentral.com/sa...-sensor-issue-during-calls-3.html#post3233866
And here:
http://forum.xda-developers.com/showpost.php?p=47329433&postcount=22
I plan on trying to return mine before re-calibrating via the above technique. Though I would like to hear peoples opinion on if its a calibration issue (i.e they didn't calibrate it from factory properly) or a hardware defect and the sensor it self is bad. My ADC value's when not covered sit at about 70 (clean screen after blowing with air at ear piece) My screen was solid green, wouldn't go white until I blew it out, I didn't check the value beforehand.
Went to Bell today and they will let me exchange it (backing it up now) I checked out the new phone they have for me and its ADC value is 30 with nothing close. From the link above it shows the "normal" value with nothing close to the proximity is around 10, not sure if I should be concerned with the new phone and try and find another if they are willing? Either way its better then my ADC 90 I'm getting today (blew with air yesterday to get it down to 70)
Thoughts? I would love to know a few more peoples ADC values.
bnevets27 said:
See here:
http://forums.androidcentral.com/sa...-sensor-issue-during-calls-3.html#post3233866
And here:
http://forum.xda-developers.com/showpost.php?p=47329433&postcount=22
I plan on trying to return mine before re-calibrating via the above technique. Though I would like to hear peoples opinion on if its a calibration issue (i.e they didn't calibrate it from factory properly) or a hardware defect and the sensor it self is bad. My ADC value's when not covered sit at about 70 (clean screen after blowing with air at ear piece) My screen was solid green, wouldn't go white until I blew it out, I didn't check the value beforehand.
Click to expand...
Click to collapse
I can't install superuser as i'm on a different model then the 2 common series out there... Unless you have some way to install root to correct...
It's more then likely difficult to complete without this...
well, I've had this exact same issue, but I read somewhere that if I blow into the earpiece (no air spray, I mean by my mouth, normally blow air into earpiece) it might get fixed. so I did and it is ok now it seems there might be getting dust under the glass through the speaker
jmaciak said:
well, I've had this exact same issue, but I read somewhere that if I blow into the earpiece (no air spray, I mean by my mouth, normally blow air into earpiece) it might get fixed. so I did and it is ok now it seems there might be getting dust under the glass through the speaker
Click to expand...
Click to collapse
I used a can of compressed air... and ADC went form 120 and non working proximity sensor to 10-15 with a good working proximity sensor.
I've contacted the seller where I bought my device (Omegacell somewhere in Alberta... for a SM-N900 imported from some other country)... they told me that if I can reproduce the problem, they will replace my device since I bought the exchange warranty at the same time. So now I'm back to square one... because I got it working with the air through the speaker "trick". Hoping that this fix will last for ever... but if it ever comes back, I hope that it will be within my 1 year exchange warranty.
Deep cleaning
I had the same problem with my proximity sensor. First it wouldn't work at all. Then ,after wiping the screen and blowing (with compressed air and mouth), it would work somewhat. The screen would go black when I put it to my ear but would not come back on after I took it down.
I tested it by dialing *#0*# and using the "Sensor" button. It would sense my hand approaching the sensor but not my hand going away.
I disassembled the phone following the instructions from GalaxyNote3Root.com (Sorry I can't post a link, not enough posts yet).
I wiped the sensor and the inside of the glass with a clean cloth, reassembled and the phone is now good as new.
This might obviously void your warranty, but on my AT&T SM-N900A there are no seals or tapes of any kind that has to be broken to get access. So no warranty voidage. At least no way anyone can tell you the phone was opened as long as you are carefull.
The whole operations takes about 15 mins.
Using beanstalk Kitkat 4.4 uring calls my screen has been going black, when i hit the power/home button it comes on for a spit second then shuts off so I am unable to use my keypad... screen protector is not blocking the sensor, is there an option keep the screen on in this rom? I went into the beanstalk option and tried to remove the sensor proximity option but still getting thr same results. Any help is appreciated
Ill answer my own post as this seems to be an issue with galaxys. If you are having issues with your screen during calls its more than likely a proximity sensor hardware issue.. Had to unscrew the back and open the sensor area then spray with computer duster.. Fixed it immediately
Sent from my SCH-I545 using XDA Free mobile app
templton said:
Using beanstalk Kitkat 4.4 uring calls my screen has been going black, when i hit the power/home button it comes on for a spit second then shuts off so I am unable to use my keypad... screen protector is not blocking the sensor, is there an option keep the screen on in this rom? I went into the beanstalk option and tried to remove the sensor proximity option but still getting thr same results. Any help is appreciated
Click to expand...
Click to collapse
Add these lines at the bottom of your Build.prop and you done
ro.lge.proximity.delay=15
mot.proximity.delay=15
ro.ril.enable.amr.wideband=1
I recently bought a 6P (yey!), so far I've enjoyed it a lot! Came from a N4 that also served quite good.
Anyways, I bought a screen protector without the cutout for the proximity sensor. So as you would guess the screen goes black after I answer a call and it is really annoying.
Is there a way to disable the "darken the screen when a call is active" or another solution without replacing the screen protector?
So far I only enabled the Hang Up power button press feature, and I don't like this solution.
Thanks in advance
The only workaround (on stock) is to enable power button to end calls in accessibility options. My toast skin and TGSP was doing this to me until I got fed up and made the cutout wider - haven't had the issue since. If you download a proximity sensor tool or test suite from Play store you'll see that the phone can't detect distances - which is why it assumes it's pressed to your face.
Hello guys,
I've got a problem, starting yesterday, my Samsung S10 Plus (G975F on ASJG firmware) has some touch screen issues and proximity sensor issues.
What is happening is that when I start a call and I place my phone near ear, it turns the screen off, but when I move it from my ear, it stays off. This issue started yesterday.
I removed the screen protector, did factory reset via ODIN (flashed clean firmware with factory reset).
The test on star#77692# works (proxy sensor test), when I place my finger it turns on, when I lift it it turns off.
Thank you for your help!
perhaps try cleaning the screen. I hear there is a number you can dial to run system tests but I am not sure if it.
Tutuapp9appsShowbox
Just to finish the thread.
I had to replace the screen due to the fact a brand new phone (3 months old) had its display unglued somehow and the issues I described started to appear.
Now everything works...huge dissapointment in Samsung screen quality.