Develop Bugs

[Q] Proximity sensor

So this is strange. Using stock Samsung ROM and dial *#0*# the proximity sensor works off the light sensor values. Proximity will be 1 until held right in bright light which at that point will be 0. WTF! I've been having a problem where the phone app uses the proximity sensor to turn off the screen and I can't turn the screen on unless the other end hangs up(big problem when it goes to voice mail) or i run to a bright light so the screen comes back on.
light sensor goes below 60 lux phone will start vibrate.
light sensor goes above 110 lux phone will stop vibrating.
I've tried many ROMs and kernels with no success and have Odined back to a stock Samsung firmware to start over. As of right now nothing should be different from when I got the device. Anyone know whats going on? I'm about to call Samsung for a replacement but wanted to see what people here say first. also I've been flashing ROMs for many years and have never seen this.

My understanding is that proximity sensor in note 2 is set for 8 cm and values are either 0 or 1 above or below 8cm
Sent from my SGH-T889 using xda app-developers app

cforlife said:
So this is strange. Using stock Samsung ROM and dial *#0*# the proximity sensor works off the light sensor values. Proximity will be 1 until held right in bright light which at that point will be 0. WTF! I've been having a problem where the phone app uses the proximity sensor to turn off the screen and I can't turn the screen on unless the other end hangs up(big problem when it goes to voice mail) or i run to a bright light so the screen comes back on.
light sensor goes below 60 lux phone will start vibrate.
light sensor goes above 110 lux phone will stop vibrating.
I've tried many ROMs and kernels with no success and have Odined back to a stock Samsung firmware to start over. As of right now nothing should be different from when I got the device. Anyone know whats going on? I'm about to call Samsung for a replacement but wanted to see what people here say first. also I've been flashing ROMs for many years and have never seen this.
Click to expand...
Click to collapse
I have this exact problem here was my thread a few months ago:
http://forum.xda-developers.com/showthread.php?t=2099898
and the only response was to factory reset (which I haven't done yet and from what you're saying that won't fix the problem either...)
Quick question, I only see 1 light coming out of the two holes at the top of the phone, are there supposed to be 2 lights? (you can check using another camera since it uses infrared)
-- edit --
just found this thread on sprint forums:
http://community.sprint.com/baw/message/544084
apparently the person had a tech open it up and air out the sensor

Easy FIX!!!!!
I took a can of compressed air and blew it through the top earpiece grill a few times and Voila, it works great now!!
I actually used a Old perfume can wich purfume was over and it was only pressing Gas OFF!!

same issue
cforlife said:
So this is strange. Using stock Samsung ROM and dial *#0*# the proximity sensor works off the light sensor values. Proximity will be 1 until held right in bright light which at that point will be 0. WTF! I've been having a problem where the phone app uses the proximity sensor to turn off the screen and I can't turn the screen on unless the other end hangs up(big problem when it goes to voice mail) or i run to a bright light so the screen comes back on.
light sensor goes below 60 lux phone will start vibrate.
light sensor goes above 110 lux phone will stop vibrating.
I've tried many ROMs and kernels with no success and have Odined back to a stock Samsung firmware to start over. As of right now nothing should be different from when I got the device. Anyone know whats going on? I'm about to call Samsung for a replacement but wanted to see what people here say first. also I've been flashing ROMs for many years and have never seen this.
Click to expand...
Click to collapse
I had the exact same problem with the proximity sensor and other weird sensor issues. I had never rooted or anything. T-mobile exchanged my phone for a new one.

vaghotstuff said:
Easy FIX!!!!!
I took a can of compressed air and blew it through the top earpiece grill a few times and Voila, it works great now!!
I actually used a Old perfume can wich purfume was over and it was only pressing Gas OFF!!
Click to expand...
Click to collapse
This fixed for me too. But the sensors start acting up like every couple weeks and I'd have to blow air into the ear piece.

i9100 proximity sensor doesn't work
Hi to all!
I have the issue with proximity sensor and didn't manage to find a solution in other similar threads!
The matter is that it is always stay as Released.
In the same time in test screen (*#0*#) there are changing reading for PROXIMITY parameter from 2 up to 240 with no ADC parameter at all. Please look for screenshots. PROXIMITY parameter changes its value when I move my finger in front of the sensor, but as I can understand Android doesn't recognize it because of ADC absence.
Moreover I tried to change proximity sensor for working one (from another phone), but it shows the same as mine (with no ADC readings).
After all I think it is software problem, but I don't know how to solve it. I flashed different firmwares (now it is XWMSE NeatROM v.6.4), but nothing helped.
Please assist! Thanks!

TRY THIS
Sensor fix installed through a custom recovery I use when flashing aosp ROMs might work but I only use it on my Liquid Smooth updates might work for you. Just have a backup in case

BRANDENDEUCE said:
Sensor fix installed through a custom recovery I use when flashing aosp ROMs might work but I only use it on my Liquid Smooth updates might work for you. Just have a backup in case
Click to expand...
Click to collapse
Thanks for advise! I'll try it and revert!

BRANDENDEUCE said:
Sensor fix installed through a custom recovery I use when flashing aosp ROMs might work but I only use it on my Liquid Smooth updates might work for you. Just have a backup in case
Click to expand...
Click to collapse
It didn't help! After the fix is installed the sensor works at the same manner... Is it possible to try something else?

Proximity sensor drivers

Hi everybody! I'm experiencing an issue with the proximity sensor of my Galaxy Note 2 i317. I think it is screwed up because during calls screen goes off either if the phone is far away from any objects. I don't have a screen protector, so the problem is not there. I was looking for a way to disable the sensor once and for all, so I installed Hardware Disabler from play store and searched for the drivers. The problem is that I can't find it among the list. I know the drivers should be the one from Capella Microsystems, CM36651 but there is nothing like that among the list. I also checked "/" in the parameters settings but nothing. I know I can disable the sensor on samsung stock ROMS via the call settings, but it doesn't solve the problem with VOIP apps like Viber, or Skype or any other like it. But the real matter is that I wish to install a CM10.1 ROM, and that option is missing there so that problem persists in normal calls too.
Now, my questions are :
1) Am I doing something wrong?
2) is it possible that the sensor is screwed up because the drivers are missing somehow? And is there a way to fix it in this case?
3) Are there other ways to disable it?
4)Is there an option in CM10.1 or other AOSP ROMS to disable the sensor during normal calls at least?
Thanks for the help!!

Dialer call settings allow you to toggle the sensor to stay on or off. ..
When combined with the general proximity setting for the phone to stay on while looking at the screen. ..
The device should stay awake ...
Try turning both settings on....
If the device still sleeps. ..your device may have a problem. .
But do not load an AOSP build until you are sure the device functions normally. ..as CM does not contain the constant wake option under general settings. ..g

gregsarg said:
Dialer call settings allow you to toggle the sensor to stay on or off. ..
When combined with the general proximity setting for the phone to stay on while looking at the screen. ..
The device should stay awake ...
Try turning both settings on....
If the device still sleeps. ..your device may have a problem. .
But do not load an AOSP build until you are sure the device functions normally. ..as CM does not contain the constant wake option under general settings. ..g
Click to expand...
Click to collapse
Thanks for your help! Yes I'm using it like you said, on stock ROM. But I wished to know if there is a way to do something like that on any AOSP ROM out there, or to completely disable the sensor.

giulytheboy said:
2) is it possible that the sensor is screwed up because the drivers are missing somehow? And is there a way to fix it in this case?
3) Are there other ways to disable it?
Click to expand...
Click to collapse
Hey there, I have a similar problem due to a cracked glass, but I figured out a little hack to solve it and disable the sensor.
2) The driver files aren't missing; I'm pretty sure that Hardware Disabler just doesn't know where to look. The driver files are located in:
/sys/devices/virtual/sensors/proximity_sensor/
Since Hardware Disabler can't look there, that option is useless.
Do this at your own risk, BTW.
3) You'll need a hex editor app to do this. Open the file named "prox_thresh" (I use ES file explorer) and select your hex editor to edit the file. You'll see a lot of 0's, but you'll need to edit the first line only. Change
31 32 0a
to
30 0a
The rest of the line is just 00.
This seems to work, although I'm pretty sure it's only temporary because I can't get the app to save prox_thresh due to a weird permission error. Maybe you can figure that out.
I'm not sure if deleting the driver folder would work, but I'm not so desperate to try that yet.
Let me know if that helps!
Sent from my SGH-I317 using xda app-developers app

Possible simple fix
I had the same problem. Sometimes the proximity sensor is working well but covered with dirt from the inside.
I gently inserted a guitar pick between the glass and the sensor (light pressure so it will open a crack) and cleaned the glass a little from the inside.
I tested it before and after with an app called proximity finder. it really fixed the problem.

[Q] Backlight dimming by itself?

Every few minutes or so the backlight on my Tab 3 10.1 will turn off, and then back on again...I've been told it's the ambient light sensor doing its thing, but I've been using it in darkness where the only light is itself and it still happens.
There is so visible option related to the issue in the settings, and I've tried apps like Lux but to no avail
Anybody else having this problem? Is it a 'feature' or is my device faulty? Is there a fix (that doesn't involve rooting)?

yes yes holy %[email protected]*%&!!!
Kagari_ said:
Every few minutes or so the backlight on my Tab 3 10.1 will turn off, and then back on again...I've been told it's the ambient light sensor doing its thing, but I've been using it in darkness where the only light is itself and it still happens.
There is so visible option related to the issue in the settings, and I've tried apps like Lux but to no avail
Anybody else having this problem? Is it a 'feature' or is my device faulty? Is there a fix (that doesn't involve rooting)?
Click to expand...
Click to collapse
ahem,
uhmm....Yes :silly: I find it to be an issue. Seriously though, i think slaying the light sensor should fix it.
I'll mess around with possibilities and post if imcome up with anything.
m
edit- you need root sorry. the quickest fix i could find was renaming
/system/etc/permissions/android.hardware.sensor.light.xml to
/system/etc/permissions/android.hardware.sensor.light.xmld and changing perms to 000

It seems to work (no change after 3 hours) ' !
But doesn't it disable the sensor for the whole system ?

hmmm
UAdeveloper said:
It seems to work (no change after 3 hours) ' !
But doesn't it disable the sensor for the whole system ?
Click to expand...
Click to collapse
i would say no,the service still needs to be disabled from kernel/init'''''.rc.
i haven't found a solid answer on stopping it so will experiment. :silly:
alternately type getprop at # --meaning-- #getprop
scroll through and see if you have and option that way with setprop.
if i figure something out i'll post
m

Proximity sensor calibration or fix?

OK I've been searching for this for a few days now with no luck..
My proximity sensor isn't working in calls the screen either A. Stays on or B. It turns off in call but doesn't wake up until a reboot even after call has ended...
And apps like hover controls and apps the use the proximity sensor don't work my sensor isn't responding until I reboot the it works for 5mins or so then stops
I'm running kitstalk 4.4.4065 and Agni kernel 2.8.5 (which kitstalk has active display and that pocket mode set to always doesn't work either until reboot then it works for 5-10mins the stops)
*Here's what I tried so far.*
1.
I tried recalibrating the sensor by typing the commands in the terminal emulator app
Su
Echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
Echo 1 > /sys/class/sensor/proximity_sensor/prox_cal
And it says there's nothing there or something along this lines
2. I tried using the dialer codes to recalibrate it from the menu but the code work work *#0# (if I put the code down wrong my apologies I used the right one but can't remember it ecatly atm)
3. I tried proximity fix app from the play store with no luck
4. I tried cleaning the front of the phone and blow air around the sensor to free any dust or smudges with no luck
5. used an app from the play store to check the sensor and it says its at 8cm and max range is 5cm I'll take a screenshot then and post it and another app I used to check it it says it on all the time but its not registering anything..
Any suggestions are GREATLY appreciated!!!
Sent from my GT-N7105 using XDA Free mobile app

ArmStrongDickPunch said:
OK I've been searching for this for a few days now with no luck..
My proximity sensor isn't working in calls the screen either A. Stays on or B. It turns off in call but doesn't wake up until a reboot even after call has ended...
And apps like hover controls and apps the use the proximity sensor don't work my sensor isn't responding until I reboot the it works for 5mins or so then stops
I'm running kitstalk 4.4.4065 and Agni kernel 2.8.5 (which kitstalk has active display and that pocket mode set to always doesn't work either until reboot then it works for 5-10mins the stops)
*Here's what I tried so far.*
1.
I tried recalibrating the sensor by typing the commands in the terminal emulator app
Su
Echo 0 > /sys/class/sensors/proximity_sensor/prox_cal
Echo 1 > /sys/class/sensor/proximity_sensor/prox_cal
And it says there's nothing there or something along this lines
2. I tried using the dialer codes to recalibrate it from the menu but the code work work *#0# (if I put the code down wrong my apologies I used the right one but can't remember it ecatly atm)
3. I tried proximity fix app from the play store with no luck
4. I tried cleaning the front of the phone and blow air around the sensor to free any dust or smudges with no luck
5. used an app from the play store to check the sensor and it says its at 8cm and max range is 5cm I'll take a screenshot then and post it and another app I used to check it it says it on all the time but its not registering anything..
Any suggestions are GREATLY appreciated!!!
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
You tried calibration with terminal emulator, but what about adb? Take a look at this thread... I've seen people have success with this method.
http://forum.xda-developers.com/showthread.php?t=2045569&page=2
There are other commands to try there, similar to what you've already tried but expanded upon... It's worth a shot. If it's not working in terminal, try adb, for the sake of being thorough.
Another option (depending on how comfortable you are doing it, is to open the device, disconnect the sensor from the motherboard, clean the sensor surface, the connector & the contacts (VERY GENTLY), and reconnect it. Worst case scenario, a new sensor is only roughly ~$20.

absinthesummer said:
You tried calibration with terminal emulator, but what about adb? Take a look at this thread... I've seen people have success with this method.
http://forum.xda-developers.com/showthread.php?t=2045569&page=2
There are other commands to try there, similar to what you've already tried but expanded upon... It's worth a shot. If it's not working in terminal, try adb, for the sake of being thorough.
Another option (depending on how comfortable you are doing it, is to open the device, disconnect the sensor from the motherboard, clean the sensor surface, the connector & the contacts (VERY GENTLY), and reconnect it. Worst case scenario, a new sensor is only roughly ~$20.
Click to expand...
Click to collapse
OK I also tried duster gas to the ear piece I heard the cleans the dust that could reach the sensor I did have a successful calibration with the sensor although it still stays black it call but works when I reboot for a few minutes
I was just going to take it to the local cell fix store and see if they can replace the sensor for me lol or try going back to the stock Kernel for the ROM since I'm using Agni and see if there's a difference there
Its hard figuring if it software or hardware related issue haha
Sent from my GT-N7105 using XDA Free mobile app

ArmStrongDickPunch said:
OK I also tried duster gas to the ear piece I heard the cleans the dust that could reach the sensor I did have a successful calibration with the sensor although it still stays black it call but works when I reboot for a few minutes
I was just going to take it to the local cell fix store and see if they can replace the sensor for me lol or try going back to the stock Kernel for the ROM since I'm using Agni and see if there's a difference there
Its hard figuring if it software or hardware related issue haha
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah determining exactly what is the problem is the hardest part! Fixing it is easy

absinthesummer said:
Yeah determining exactly what is the problem is the hardest part! Fixing it is easy
Click to expand...
Click to collapse
Hey 2 questions could my proximity sensor be picking up my glass screen protector? Its not covering it but it just covers the Samsung logo at the top.
And how can I change the range the proximity sensor is set to BC an app I used to check it says it at 8cm and the max is 5cm?
Sent from my GT-N7105 using XDA Free mobile app

ArmStrongDickPunch said:
Hey 2 questions could my proximity sensor be picking up my glass screen protector? Its not covering it but it just covers the Samsung logo at the top.
And how can I change the range the proximity sensor is set to BC an app I used to check it says it at 8cm and the max is 5cm?
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Im not sure about changing the range, I'll look into that but yeah depending on the screen protector it could interfere with the sensor, especially if it's particularly thick or dirty. I don't use screen protectors anymore for that very reason. They can muck up the sensor and make the front camera take fuzzy pics.

Wake up problems after flashing AOSP 6 - E975

PROBLEM
After flashing to AOSP 6 I have problems with waking the screen up.
1. After or during the call
2. After longer sleep
It can take up to a minute to wake up. Usualy around 10-20 seconds after multiple presses (single press can sometimes doesn't wake the phone).
NO PROBLEMS WHEN:
1. I manualy sleep the screen, and press power again after a moment - I can bring it to a wake up state without any problems.
2. If the phone is connected through USB - there is also no problem to instantly bring the wakeup screen.
3. There is also no problem to bring the wakeup screen with adb
Code:
adb shell input keyevent 26
I was expecting it to be some sort of sensor problem, as it persists to other roms, even coming back to 5.1.1 which previously worked flawlessly in this department.
I've tried this: http://forum.xda-developers.com/opt...mpting-to-fix-broken-sensors-mm-e975-t3297566 without any results. I've also tried restoring factory settings.
Any ideas?

ZPZG said:
PROBLEM
I was expecting it to be some sort of sensor problem, as it persists to other roms, even coming back to 5.1.1 which previously worked flawlessly in this department.
Click to expand...
Click to collapse
What does CPU-Z think of your sensor data? it's being represented correctly?

blackbird5308 said:
What does CPU-Z think of your sensor data? it's being represented correctly?
Click to expand...
Click to collapse
The sensor as far as I know is binary, so either something is in proximity or not, and as that it works correctly under any system.
After reverting to stock 4.4.2 the problem does not appear.
Installing AOSP 6 again - the problem returns.

ZPZG said:
The sensor as far as I know is binary, so either something is in proximity or not, and as that it works correctly under any system.
After reverting to stock 4.4.2 the problem does not appear.
Installing AOSP 6 again - the problem returns.
Click to expand...
Click to collapse
well, i don't really know, my proximity sensor has been working well since first time i went 6.0 AOSP, even when no other sensor was working at all

blackbird5308 said:
well, i don't really know, my proximity sensor has been working well since first time i went 6.0 AOSP, even when no other sensor was working at all
Click to expand...
Click to collapse
Honestly I don't know what is the problem, but in every thread concerning wakup issues and E975 the sensors are blamed. The physical sensor is working properly as I am not having any problems running stock 4.4.2.