Just got my Galaxy S3 a few days ago and today when I answered a call the screen immediately went blank and I could not turn it back on until the caller hung up. I've had other calls prior to today and cannot recall if the phone behaved the same way. I've been searching for a solution and everything points to a faulty proximity sensor. I've worked around the problem by disabling "Auto screen off during calls" under "Call settings". This works but it's not perfect since if I forget to manually turn off the screen I'm likely to press buttons with my face.
Under *#0*# -> Sensor -> Proximity Sensor: The PROXIMITY always reads 1.0. The ADC field increases as I get closer to the proximity sensor but never drops below 1 (should it?). Are PROXIMITY and ADC both readings from the same sensor?
Under *#7353# -> Proximity Sensor: It always says "Working" and vibrates. From the other tests in this menu I assume this is the "On" state and that the correct behavior would be to not vibrate and display a different message when the sensor is "Off" (ie: nothing is close to the sensor).
Several test apps (Android Sensor Box, Proximity Sensor, Sensor Test) also report 0cm or something similar indicating that something is close to the sensor.
Thanks in advance for any help :good:
machx0r said:
Just got my Galaxy S3 a few days ago and today when I answered a call the screen immediately went blank and I could not turn it back on until the caller hung up. I've had other calls prior to today and cannot recall if the phone behaved the same way. I've been searching for a solution and everything points to a faulty proximity sensor. I've worked around the problem by disabling "Auto screen off during calls" under "Call settings". This works but it's not perfect since if I forget to manually turn off the screen I'm likely to press buttons with my face.
Under *#0*# -> Sensor -> Proximity Sensor: The PROXIMITY always reads 1.0. The ADC field increases as I get closer to the proximity sensor but never drops below 1 (should it?). Are PROXIMITY and ADC both readings from the same sensor?
Under *#7353# -> Proximity Sensor: It always says "Working" and vibrates. From the other tests in this menu I assume this is the "On" state and that the correct behavior would be to not vibrate and display a different message when the sensor is "Off" (ie: nothing is close to the sensor).
Several test apps (Android Sensor Box, Proximity Sensor, Sensor Test) also report 0cm or something similar indicating that something is close to the sensor.
Thanks in advance for any help :good:
Click to expand...
Click to collapse
This may be a stupid question, but do you have a case that might be covering the proxy sensor? I'm also assuming you have cleaned the area where the sensor is. Other than that you might be able to take the phone into the Sprint store and get it replaced. If they won't take it back, call up Samsung customer service. If it's a faulty sensor, they might replace the phone free of charge (others have had good experiences with Samsung customer support)
Hope you get it fixed!
topherk said:
This may be a stupid question, but do you have a case that might be covering the proxy sensor? I'm also assuming you have cleaned the area where the sensor is. Other than that you might be able to take the phone into the Sprint store and get it replaced. If they won't take it back, call up Samsung customer service. If it's a faulty sensor, they might replace the phone free of charge (others have had good experiences with Samsung customer support)
Hope you get it fixed!
Click to expand...
Click to collapse
Thanks for the response. No screen protector or case. I did clean the entire screen this morning and the behavior didn't change. Was hoping I wouldn't have to take the phone back but then again if this was a common problem with a simple solution my searching this morning probably would have turned up an answer
machx0r said:
Thanks for the response. No screen protector or case. I did clean the entire screen this morning and the behavior didn't change. Was hoping I wouldn't have to take the phone back but then again if this was a common problem with a simple solution my searching this morning probably would have turned up an answer
Click to expand...
Click to collapse
Lol yeah, this is the first time I've seen anything about this, and I respond to literally almost every thread, or at least read through each one. But like topherk said, its probably a hardware issue. Would you be able to check to see if the "1.0" value is present on another S3? Maybe its a default of some kind (i would check myself, but my S3 took a 4 story dive recently and is out of service)
CNexus said:
Lol yeah, this is the first time I've seen anything about this, and I respond to literally almost every thread, or at least read through each one. But like topherk said, its probably a hardware issue. Would you be able to check to see if the "1.0" value is present on another S3? Maybe its a default of some kind (i would check myself, but my S3 took a 4 story dive recently and is out of service)
Click to expand...
Click to collapse
I don't know anyone else with an S3 but if anyone wants to check their *#0*# -> Sensor screen and tell me what the PROXIMITY and ADC values are when you aren't close to the sensor I'd appreciate it. Maybe I'll hit up the Sprint store and test it on a display model :laugh:
That said the page I discovered the *#0*# menu on has a screenshot and the PROXIMITY is showing 0.0 (I assume he's away from the sensor):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Where as this is mine when I'm away from the sensor:
After digging a little deeper it appears that the G3 uses the same IC (a GP2A from Sharp) for both the proximity and light sensor. From looking at the GP2A kernel module code it appears that the ADC values are from the light sensor output and the PROXIMITY value is from the proximity sensor output (0.0 = nothing within 5CM, 1.0 = something within 5CM). The ADC values definitely change and the interpreted light sensor lux values change when I cover it or shine a flashlight into it.
So now I'm not so sure if it's possible for it to be a hardware issue or if it's a software issue caused by some weird state. Think I'll try a factory reset and see if the situation changes...
machx0r said:
After digging a little deeper it appears that the G3 uses the same IC (a GP2A from Sharp) for both the proximity and light sensor. From looking at the GP2A kernel module code it appears that the ADC values are from the light sensor output and the PROXIMITY value is from the proximity sensor output (0.0 = nothing within 5CM, 1.0 = something within 5CM). The ADC values definitely change and the interpreted light sensor lux values change when I cover it or shine a flashlight into it.
So now I'm not so sure if it's possible for it to be a hardware issue or if it's a software issue caused by some weird state. Think I'll try a factory reset and see if the situation changes...
Click to expand...
Click to collapse
Have you ever installed a flip cover app?
Sent from my SPH-L710 using xda premium
xblackvalorx said:
Have you ever installed a flip cover app?
Click to expand...
Click to collapse
No, pretty standard apps installed and nothing specific to motion or proximity (aside from the handful of test apps I've installed to see what the proximity sensor readings are).
machx0r said:
After digging a little deeper it appears that the G3 uses the same IC (a GP2A from Sharp) for both the proximity and light sensor. From looking at the GP2A kernel module code it appears that the ADC values are from the light sensor output and the PROXIMITY value is from the proximity sensor output (0.0 = nothing within 5CM, 1.0 = something within 5CM). The ADC values definitely change and the interpreted light sensor lux values change when I cover it or shine a flashlight into it.
So now I'm not so sure if it's possible for it to be a hardware issue or if it's a software issue caused by some weird state. Think I'll try a factory reset and see if the situation changes...
Click to expand...
Click to collapse
Interesting...
Lol, i would recommend going to the Sprint store (if its not a hassle) and testing it out with their S3 on display, surefire way of knowing if something got borked with yours
I dont know whether they would charge for this or not, hopefully they dont, but you could also ask the reps to check it over for you and say you've been having some weird behavior with your incoming calls and the screen on/off events
machx0r said:
I don't know anyone else with an S3 but if anyone wants to check their *#0*# -> Sensor screen and tell me what the PROXIMITY and ADC values are when you aren't close to the sensor I'd appreciate it. Maybe I'll hit up the Sprint store and test it on a display model :laugh:
That said the page I discovered the *#0*# menu on has a screenshot and the PROXIMITY is showing 0.0 (I assume he's away from the sensor):
Where as this is mine when I'm away from the sensor:
Click to expand...
Click to collapse
Exactly what's been happening with my Samsung Galaxy Note 2 running stock firmware (rooted) with no screen protector. Been searching the internet for months and tried several proximity screen off apps to no avails. After countless tests and trials I am convinced that the proximity sensor when activated is stuck "near" (PROXIMIY = 1.0 at ADC level <= 12) unless there is bright enough ambient light. If some gurus could shade some lights on how to set the proximity threshold "prox_thresh" to be greater than 12 (say 30) (and that setting will stick after restart) that would be great!
I have the same problem with my brand new TMobile Galaxy Note 2 where proximity sensor does require a lot of ambient light in order to switch the screen on and off during the call. I noticed that the screen protector is part of the problem so I removed it and it helped a bit but not always. I was afraid the sensor is broken itself and requested for replacement phone however I tried the *#0*# combination to test the sensor and found that ADC (analog to digital converter) output changes as I approach the sensor. With no proximity ADC shows value of between 11 and 15 and it is increasing smoothly to 140 as I move closer and furthermore reaches 190 as I press my finger against the screen. So the proximity sensor hardware actually works just fine it is the software layer including driver that possibly creates a problem which results in Proximity value being always equal 1.0 despite of ADC output precisely following the actual proximity. Several applications available call play market follows the Proximity value therefore making sensor based ofperation difficult or useless. I hope that upcoming system update will address the flaw making sensor based functions to work finally as they should.
Sent from my SGH-T889 using Tapatalk 2
Galaxy S3 proximity sensor replacement
Same issue here. A few things that may be of interest. My issue did not start after an update, it just started happening out of the blue. It is not because of being dirty or a because of a case. When I get into the diagnostic screen, the proximity sensor reads 0 and then goes to 1 when you get in proximity. It then stays at 1 and won't go back to 0. The ADA changes values, apparently correctly. The one thing that I thought was interesting, if I flash a bright LED flashlight on it, it does go back to zero. It is almost like it is not as sensitive to light all the sudden. This light trick works no matter how far away the light is. I am thinking the sensor is going bad.
I see several options to replace it on eBay, I changed out the screen last year, so I know how to change out the front camera and sensor. The only OEM ones I see are used or from China. Has anyone ever tried any of these, OEM or otherwise? They are cheap, I think I will give it a shot.
SOLVED
Just a heads up, I fixed my problem with a new front facing camera and sensor off of ebay. It took less than 10 minutes to put it in and it works great now. It was $5.99 shipped.
try this
esdwa said:
I have the same problem with my brand new TMobile Galaxy Note 2 where proximity sensor does require a lot of ambient light in order to switch the screen on and off during the call. I noticed that the screen protector is part of the problem so I removed it and it helped a bit but not always. I was afraid the sensor is broken itself and requested for replacement phone however I tried the *#0*# combination to test the sensor and found that ADC (analog to digital converter) output changes as I approach the sensor. With no proximity ADC shows value of between 11 and 15 and it is increasing smoothly to 140 as I move closer and furthermore reaches 190 as I press my finger against the screen. So the proximity sensor hardware actually works just fine it is the software layer including driver that possibly creates a problem which results in Proximity value being always equal 1.0 despite of ADC output precisely following the actual proximity. Several applications available call play market follows the Proximity value therefore making sensor based ofperation difficult or useless. I hope that upcoming system update will address the flaw making sensor based functions to work finally as they should.
Sent from my SGH-T889 using Tapatalk 2
Click to expand...
Click to collapse
On Samsung devices like i9100 (Galaxy S3) or N7100 (Note II) you can do the following if you have root permissionsn Android Terminal App or adb shell do:Code:$ su $ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal $ echo 1 > /sys/class/sensors/proximity_sensor/prox_calThe zero resets the actual calibration offset.The one does an auto calibration (read sensor value, set offset to this sensor value, write calibration offset to "/efs/prox_cal" which is read while device is booting).Best for calibrate your sensor is to keep it dark, the glass have to be clean and the sensor free (so that the sensor doesn't measure anything).*The calibration offset is stored in efs, thats why you can make full wipe and use other ROMs without the need of recalibration.You can check the running config by:Code:$ cat /sys/class/sensors/proximity_sensor/stateThe first value is the calibration Offset, the second one is the sensor threshold (threshold is set at compile time).Open *#0*# to see "sensors" and check if your proximity sensor is now working properly.*
This work on the first try for me try it and c if it help u
I can now stop pulling out my hair...
Gryncc said:
On Samsung devices like i9100 (Galaxy S3) or N7100 (Note II) you can do the following if you have root permissionsn Android Terminal App or adb shell do:Code:$ su $ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal $ echo 1 > /sys/class/sensors/proximity_sensor/prox_calThe zero resets the actual calibration offset.The one does an auto calibration (read sensor value, set offset to this sensor value, write calibration offset to "/efs/prox_cal" which is read while device is booting).Best for calibrate your sensor is to keep it dark, the glass have to be clean and the sensor free (so that the sensor doesn't measure anything).*The calibration offset is stored in efs, thats why you can make full wipe and use other ROMs without the need of recalibration.You can check the running config by:Code:$ cat /sys/class/sensors/proximity_sensor/stateThe first value is the calibration Offset, the second one is the sensor threshold (threshold is set at compile time).Open *#0*# to see "sensors" and check if your proximity sensor is now working properly.*
This work on the first try for me try it and c if it help u
Click to expand...
Click to collapse
Worked like a charm! Original values were evidently not properly calibrated, but the above approach reset the values such that the display now switches off (in phone calls) at approximately 8 cm, and following hang up, immediately powers on.
Thank you
Gryncc said:
On Samsung devices like i9100 (Galaxy S3) or N7100 (Note II) you can do the following if you have root permissionsn Android Terminal App or adb shell do:Code:$ su $ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal $ echo 1 > /sys/class/sensors/proximity_sensor/prox_calThe zero resets the actual calibration offset.The one does an auto calibration (read sensor value, set offset to this sensor value, write calibration offset to "/efs/prox_cal" which is read while device is booting).Best for calibrate your sensor is to keep it dark, the glass have to be clean and the sensor free (so that the sensor doesn't measure anything).*The calibration offset is stored in efs, thats why you can make full wipe and use other ROMs without the need of recalibration.You can check the running config by:Code:$ cat /sys/class/sensors/proximity_sensor/stateThe first value is the calibration Offset, the second one is the sensor threshold (threshold is set at compile time).Open *#0*# to see "sensors" and check if your proximity sensor is now working properly.*
This work on the first try for me try it and c if it help u
Click to expand...
Click to collapse
sea2summit said:
Worked like a charm! Original values were evidently not properly calibrated, but the above approach reset the values such that the display now switches off (in phone calls) at approximately 8 cm, and following hang up, immediately powers on.
Thank you
Click to expand...
Click to collapse
God, i've been looking for that information for dozens of years (felt this way at least).
And i find it the day i put my phone back to stock for an RMA !
I went back to root, and tried those lines in the ROM Toolbox Pro's terminal, it says " can't create /sys/class etc. permission denied", what's wrong please guyz ?? I tried several ways to re root, root checker says "status : rooted, ID : uid=0(root) gid=0(root), SuperUser (can't find), BusyBox : /system/xbin/busybox, Su : /system/xbin/su => maybe that's the issue, am i badly rooted ?
Isn't there a no root solution, a very simple way to calibrate ? While looking for a solution, I heard about Als-Ps calibration, doesn't it exist on the N7100 ?
Any help would be very appreciated.
EDIT : OK, i typed "su" to get the terminal to get the SU request, and typed the command, rebooted the phone : the issue's still there.
I'm a noob to Android Terminal, so i tried putting
do:Code:$ su $ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal $ echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
into it, but it didn't work, then i tried
"$ su $ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal $ echo 1 > /sys/class/sensors/proximity_sensor/prox_cal"
and it didn't work, so i had to remove the first "$" to get it to work
(so it looks like "su $ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal $ echo 1 > /sys/class/sensors/proximity_sensor/prox_cal")
Am I doing something wrong ?
Gryncc said:
On Samsung devices like i9100 (Galaxy S3) or N7100 (Note II) you can do the following if you have root permissionsn Android Terminal App or adb shell do:Code:$ su $ echo 0 > /sys/class/sensors/proximity_sensor/prox_cal $ echo 1 > /sys/class/sensors/proximity_sensor/prox_calThe zero resets the actual calibration offset.The one does an auto calibration (read sensor value, set offset to this sensor value, write calibration offset to "/efs/prox_cal" which is read while device is booting).Best for calibrate your sensor is to keep it dark, the glass have to be clean and the sensor free (so that the sensor doesn't measure anything).*The calibration offset is stored in efs, thats why you can make full wipe and use other ROMs without the need of recalibration.You can check the running config by:Code:$ cat /sys/class/sensors/proximity_sensor/stateThe first value is the calibration Offset, the second one is the sensor threshold (threshold is set at compile time).Open *#0*# to see "sensors" and check if your proximity sensor is now working properly.*
This work on the first try for me try it and c if it help u
Click to expand...
Click to collapse
Thank you Gryncc!!! it worked for me in im i9500. I did it with ADB Shell... the comands where...
su
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
the 0 did nothing, so I tried 1 and after reset, the sensor worked again!
Regards,
Julián
julianbl said:
Thank you Gryncc!!! it worked for me in im i9500. I did it with ADB Shell... the comands where...
su
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
the 0 did nothing, so I tried 1 and after reset, the sensor worked again!
Regards,
Julián
Click to expand...
Click to collapse
can u post a screen shot for commands to be used.
a video will be most appreciable,,
This is how it looks like,
2 separate commands, echo 0 = reset, echo 1 = calibrate
For me it worked till i restarted device.
Gonna send it in for repair now.
Yes it works on note 2 even.but how to stop it going away after restart any thing permanent? ??
Related
Hi
how can i disable the proximity sensor on my HTC Touch Pro 2, windows mobile 6.1 ?
I use a screen lock app that dims the screen during calls but when coming near proximity sensor during call, the screen is turned on again - a real pain.
Please if any onw have an advice to shut it off cpmpletely or when i am on bluetooth i would be really happy for some help
PS i thought paroximitysensor was supposed to disable when tp2 is connected to bluetooth - but its not ??
thanks
Nolan
no one ?
regards nolan
having the exact same issue. I found a cab called TurnOffTheLight but haven't had a chance to try it yet.
For me, it would be better if the proximity sensor was off permanently, if possible.
thisisallen said:
having the exact same issue. I found a cab called TurnOffTheLight but haven't had a chance to try it yet.
For me, it would be better if the proximity sensor was off permanently, if possible.
Click to expand...
Click to collapse
Hi
could you test teh cab and tell us here if that can turn of permanemtly the proximity sensor ?
regards Nolan
TurnOffTheLight works to turn off the backlighting but as soon as you move the phone the proximity sensor kicks in again.
in the app called Advanced Config there is a category for adjusting the threshold of the Light Sensor. Unfortunately I have no idea how to adjust it (it is at 0 now) and/or if adjusting this would affect the proximity sensor. Can someone comment on this?
thisisallen said:
in the app called Advanced Config there is a category for adjusting the threshold of the Light Sensor. Unfortunately I have no idea how to adjust it (it is at 0 now) and/or if adjusting this would affect the proximity sensor. Can someone comment on this?
Click to expand...
Click to collapse
Hi
light functionality would not solve the problem regarding proximity sensor - its 2 different matters unfortunately
regards Nolan
i have allmost the same problem. my sensor is broken and alwayas is "On". so when i make a call on my hd2 android 2.2 screen goes off and never goes on again. how to kill it???
Called today helpdesk with same problem, cant be turned off , must go for a repair.
Proximity Sensor behavior and solution
I am a late comer to this bb! Hey,I thought all the bugs would be worked out by now! My keyboard did not work right, .... and I have had several other problems with the touchpro2. What are the Chinese doing over there? I had programmed many embedded units and microprocessor systems, but, really, how can they mass produce units like these? Too many cooks in the soup? They are leaving their quality control to the general community.
My problem was I use my gps for bicycling, and if I place it in the support case, the proximity sensor would shut off the screen, even though I was not placing a call. The screen would blank and not come back on. I noticed there was no problem if the physical keyboard was opened and also if the unit were held horizontally. It did this all the time, regardless of the app running.
There are two sensors at the top of the unit: proximity sensor and light sensor. This is a problem with the proximity sensor, at the left.
So I just placed duct tape over it. Now it does not blank.
I flash energy's rom,it's good.but screen light off when calling makes me crazy.However I press the power button,the screen does not light on.every way i can do (regedit,change light sensor) does not work.
so please ,anybody knows?
You're saying that no matter what you do, the screen will not light up at all during a phone call once the proximity sensor turns turns the screen off?
yeah,you are right,but some rom can light up during a phone call,others can not.I'm crying for this
I've used Energy ROMS, and they were bullet proof, ran perfect, did everything they were supposed to do, like turn the screen off when I help the phone to my ear or had an object within proximity of the sensor, and the screen relit whenever I pulled the phone from my ear or moved an object away from the sensor...if you're saying the screen stays dark and you cant turn it on even with nothing blocking the sensor, then I recommend posting that issue in the Energy ROM thread as there could be a solution...if you're saying the proximity sensor works normally and you'd prefer to deactivate it, I searched around for that for you and didn't find a resolution...you can, however, if the sensor works properly...cover it up all the time (perhaps a small piece of black tape or something)...you'll have to hit the power button one time each time the phone takes or makes a call but the screen will stay lit til you turn it off again, even during a call
thank you Gt247. thank you so much.I think I found the way to resolve my screen's problem
I read a bunch where people were looking for a way to disable the proximity sensor...perhaps if that's what you've done, you could post the solution here in the event those peple are still looking
I have tried some apps to disabled my proximity sensor,but those all do not work,I think it's my phone's hardware problem,I have already decided to open my phone to fix it.
so before I fix this fool sensor ,any knows which app can test the proximity sensor?
just a app to test whether my proximity sensor work normally, any clue?
usomething said:
I have tried some apps to disabled my proximity sensor,but those all do not work,I think it's my phone's hardware problem,I have already decided to open my phone to fix it.
so before I fix this fool sensor ,any knows which app can test the proximity sensor?
just a app to test whether my proximity sensor work normally, any clue?
Click to expand...
Click to collapse
You don't need any app to test the proximity sensor , just turn on your screen , and cover the sensor with your finger . If your proximity sensor works normally , screen will be off . When you remove your finger in seconds , the screen will be turned on again .
I think you can disable the proximity sensor simply by removing the shortcut in the "startup" folder , and restart .
If I misunderstood your words , ignore me pls ~
thanks pcgg.I have tested my proximity sensor,it seems not notice my finger,the screen always on.
I have not found the proximity sensor shortcut in my startup folder,here is the file list in my startup folder:
DeviceLockXT.lnk
LockDevice.lnk
SpbMobileShell.lnk
so could you tell me which lnk is the proximity sensor?I can't find the file about what you say by the name
It seems that there is not priximity sensor app in your phone ....
While there is an app called "Rhodium setting tool" in mine , and it has a option under the menu "phone" named "Light Sensor" . If I turn it on , screen will auto turn off during a call .
Maybe you can try that ?
Well , I must say that I did misunderstood your words ... I thought you were complaining an app called "Proximity Sensor" . I found it in the "Jackos" ROM ... Sorry for misleading you .
You can try that app "Rhodium setting tool" . If it can not work , I will have no idea about it .
thanks pcgg.
I have already try the light sensor,I have tried many apps those can control the light sensor,but those don't work at all,at last I get a conclusion that is proximity sensor has a higher priority than the light sensor,proximity sensor can decide whether the screen can turn itself on or off.
my rom now is seeM_ZA's simplicity rom 21916,I'm now ready to flash jackos'r rom.whether it works ,I will tell you the result later
Any of the two, i suspect the first:
- you probably have some dirt inside your phone, at top left corner where the digitizer has a semi transparent glass for the proximity sensor (you hardly see it without disassembling screen)
- the proximity sensor is KO, you have to replace flex to cure it (about 35$ on eBay)
Once i replaced the digitizer on a TP2 and a little drop of glue went near the window of proximity sensor, it didn't work at all till i disassembled all again, cleared the the glue around the window letting again enough light to enter the sensor.
Hi,
The proximity sensor on my Galaxy Note 2 has broken, which means as soon as a I make a phone call the screen goes black and I can't end the call or wake the screen up.
In touchwiz there is an option to disable the proximity sensor during calls but I'm using an AOSP rom, I have had a look in all the settings and there is nothing about disabling the proximity sensor during calls.
The sensor is called "cm36651", I have tried to disable it using Hardware Disabler but I can't find it in the list of devices even when I search from "/".
So does anyone know another method of disabling the proximity sensor?
Thanks
Go into the phone app. Click settings. Untick the turn on proximity sensor during calls.
Sent from my GT-N7105 using XDA Premium 4 mobile app
You ever figure out how to disable that annoying thing?
I'm pretty certain that after hours of endless searching, I'm just going to unsolder it from the board... grr
During calls, does your screen turns on again if you shine the proximity sensor under a bright source of light? If yes, all you need to do is recalibrate. I had the same thing happening.
http://forum.xda-developers.com/showthread.php?t=2045569
Sent from my GT-N7105 using xda app-developers app
spigget said:
You ever figure out how to disable that annoying thing?
I'm pretty certain that after hours of endless searching, I'm just going to unsolder it from the board... grr
Click to expand...
Click to collapse
Hi, what I found works for me is to run these two commands after every reboot.
echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
and
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
The 0 resets it and the 1 calibrates it, not sure what the problem is but it works for me everytime.
costcutter said:
Hi, what I found works for me is to run these two commands after every reboot.
echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
and
echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
The 0 resets it and the 1 calibrates it, not sure what the problem is but it works for me everytime.
Click to expand...
Click to collapse
Please help me fix this I want to run Google edition ROMs but can't handle Prix sensor on very call
CanadianKB said:
Please help me fix this I want to run Google edition ROMs but can't handle Prix sensor on very call
Click to expand...
Click to collapse
I Got It! Click Here --------> https://play.google.com/store/apps/details?id=com.vrognaas.proximityfix ... the app is call Proximity Fixer i have a Note 2 Verizon running on CM 11 and it works perfectly :good: :laugh:
is there any way to turn off this proximity feature in cm11. I'd rather just be able to turn the screen off and on with my power button. my prox sensor gets dusty way too fast and then my screen stays black during calls.
disable prox sensor
j3oomerang said:
is there any way to turn off this proximity feature in cm11. I'd rather just be able to turn the screen off and on with my power button. my prox sensor gets dusty way too fast and then my screen stays black during calls.
Click to expand...
Click to collapse
I tried everything I could find, including several root programs, and nothing would keep my screen from going black when I made phone calls on Nexus 5 (after broken screen replaced). Tried every single proximity sensor "fix", and disabler app but nothing worked. The Sensor kept showing 0.0 meaning it though it was right up against an object.
I finally put a piece of foil in front of the sensor, and now it reads 5.0 (max distance) and FINALLY the screen stays on in phone calls - unless I tap the power button to shut it off.
There must be some factory calibration they do with the original screen, and any replacement one is just not quite exactly the same.
Hello all
I have replaced a broken touchscreen with the new one (bought on ebay). Everything seemed to be working fine but when I make a call or someone is calling me I see a black screen as display is turned off (just like it does when you put your smartphone to your ear).
I tested all sensors and saw that proximity sensor is always showing "0" so I can understand why display is turned off. It just thinks that it's closed by something
Can someone tell me how this could be? As I see there are 2 sensors on the one cable: Light and proximity. Light sensor is working ok, but proximity is always showing zero "0". Can someone tell me is this a common situation while replacing a touchscreen (could I just break the sensor somehow) or I might missed some details while i replaced this touchscreen?
Can I test the sensor somehow without touchscreen? (pull it off the touchscreen and try to close/open it by the hand?)
Proximity sensor of my note 8 pro not working at all. During calls display turns off and doesn't turn on till the call ends. Cpuz and CIT test show 0.0 reading which doesn't change no matter what i do. Also i am not using any sort of case,cover or screen protector and i can't open engineering mode to calibrate the sensor as it is available in most mediateck devices.
Same here ?
In CIT, there's additional tools ( on top/right of thé screen) where you Can calibrate the proximity sensor
where is this calibration tool? Link?
How to do this CIT test?
In About phone, tap on kernel version multiple times to open cit test
GRoMSTeiN said:
In CIT, there's additional tools ( on top/right of thé screen) where you Can calibrate the proximity sensor
Click to expand...
Click to collapse
Thanks a lot man, i knew all it needed was calibration but i was unable to find the option. It working fine now
Same issue.... test failed, calibration didn't help... Btw CIT on most recent firmware works via *#*#64663#*#*
Any other options to try?
same issue here. screen remains always on during call:crying:
If you installed a black border screen protector 5D 6D 9D whatever, Please remove it and try again you will find that the sensor is working very good
Any Solutions
Bro did u get any solution
Issue resolved (Proximity Sensor - RN8P)
nagaraju5663 said:
Bro did u get any solution
Click to expand...
Click to collapse
Yes !
The actual problem was the screen protector (Glass Hammer) having black boarder on its sides. Proximity sensor starts working immediately after adjusting the screen protector little precisely.
There is a solution ,
Go settings > about phone > all specs > 5 touch the "Kernel Verison" > in CIT there is a menu which is top/right > Additional Tools > 10.Proximity Sensor > you how to do what it says and calibrate and if it's done pass. Then push back > 14.Proximity Sensor > if it is working push "PASS" > Then exit CIT, there is an alert about data erasing push "OK" and live long
I am starting to freak out. Even the tests passes, my phone doesn't configure backlight automatically and on most calls, the screen won't turn off when holding to the ear.
Work
sametatila said:
There is a solution ,
Go settings > about phone > all specs > 5 touch the "Kernel Verison" > in CIT there is a menu which is top/right > Additional Tools > 10.Proximity Sensor > you how to do what it says and calibrate and if it's done pass. Then push back > 14.Proximity Sensor > if it is working push "PASS" > Then exit CIT, there is an alert about data erasing push "OK" and live long
Click to expand...
Click to collapse
Works great
MohamedYousri said:
If you installed a black border screen protector 5D 6D 9D whatever, Please remove it and try again you will find that the sensor is working very good
Click to expand...
Click to collapse
You are my man!
This really fixed the problem for me. Thanks a lot :good: