Related
Hi! I have a problem with my N1, the proximity sensor don't work good, when it isn't under a light, if I cover it the screen shutting down, but when i discover it, the screen stay shut down; however if the sensor is under an high light like sun it work good and the screen lighting up instantly.
I don't have any screen protector on the glass, so i don't understand the problem , can someone tell me why and if i can resolve?
The other question is: it is a software or hardware problem??
thanks Mattia
EDIT: I have the original rom, with the update 1, and i've not unlock bootloader.
Did you recently put a screen protector on your phone?
How did you solve it?
i hadn't solved it, i have that problem.. and i have never put any screen protector.
Try hard-resetting the phone. It may work if its any software glitch.
i've already tryed hard reset too, for 2 or 3 times...
i have done a test with an app called "sensor test" and i have found that the sensor start with 1 status and then covering the sensor, it change to 0, but when I discover it, the status stay on 0.
if i restart the app, bit status come back to 1. it had problem returning to 1 value automatically when i discover the sensor... always using it in a dark ambient.
otherwise if i test it under a light it work great!
masca88 said:
i've already tryed hard reset too, for 2 or 3 times...
i have done a test with an app called "sensor test" and i have found that the sensor start with 1 status and then covering the sensor, it change to 0, but when I discover it, the status stay on 0.
if i restart the app, bit status come back to 1. it had problem returning to 1 value automatically when i discover the sensor... always using it in a dark ambient.
otherwise if i test it under a light it work great!
Click to expand...
Click to collapse
Looks like your phone is busted.
Is it a huge deal to you? If so, call up HTC and send it back.
http://www.htc.com/www/support/nexusone/
If not, replace it in 364 days for a brand new one
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
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.
Hello XDA,
I have a weird problem going on with my Note 3. I had an issue where my screen would not shut off during calls so I immediately figured I'd test the proximity sensor with some debugging app and also the built-in service menu. I went ahead and did that and noticed it was sort of working but one of the values (the main one that ranges from 0.0 to 8.0) stayed at 0.0 and didn't change. I did some research and used an app that I believe recalibrated it and it began to work perfectly… EXCEPT, when the screen goes off during a call and SHOULD be locked from touch events I can still touch the screen and it is responsive, meaning even thought the screen is black I can end the call, mute it etc granted I touch the right area seeing as I can't see anything. Another thing that's going on that leads me to believe this is some sort of software bug is, when the screen is turned off due to the takeover setting, when I press the home button to turn it back on, it turns back on BUT the front app is lowered and i am brought to the home screen as if the screen was on and I hit it. Weird huh?
Any help would be appreciated…
Verizon Note 3 running on T-Mobile and CM13
Hello everyone!
I have a problem with my Galaxy S8 (G950F). Proximity sensor working like is too sensitive - without any screen protectors, cases etc. it showing ADC value of ~2400 and it's always turned on. When I bring my hand closer the value increases and when I move it away it decreases - randomly it starts to work correctly (then the ADC value showing 140-160). I tried to clean the holes near the sensor using compressed air, factory reset, firmware flashing - nothing helped. Is there a way (with or without root) to change initial value at which the sensor begins to detect face, for example to start working when ADC value is greater than 2500?