Question to the kernel or rom devs. Is there a way to change the threshold of the proximity sensor? I am asking because I had proximity sensor problems where my ADC value would be roughly around 46-50 at rest. I sent my phone into samsung to get it fixed and then the senor started working again as I was hovering around 16-18 at rest (they replaced the sensor) . Now after a few weeks later, I am noticing my adc value at rest is starting to slowly increase (the ADD in me keeps me checking ) and now it's at 32. I have an i337m rooted and running the latest stock TW rom (MG1 for Canadian models). I have a feeling in about another 3 weeks or so, I am going to have the same issue again.
Related
Hi all,
I apoligise in advance if this has been posted before but it's 4:30am and I don't have anymore time to search for this problem.
I've noticed ever since I've updated my phone to Darky's ROM (starting in dec 2010 with v8) my proximity sensor hasn't been turning my screen off during calls. I'm not sure if this is rom related or not but I ran some tests tonight (using SGS tools and sensor test/z-devicetest) and in all those apps my sensor doesn't seem to respond.
Does this mean it's broken?? Or am i missing some drivers or something??
I'm currently running DarkyROM v10.1.
TIA
Edit: found out that it is indeed working, however only when a bright light shines onto the sensors. Is this normal??
Hi all,
I have a i9500 phone.
I have this firmware installed onto my phone
I9500XXUEMJ5_I9500ODDEMJ5_I9500DDUEMJ5_HOME
2 days ago i got a push update, and then i updated my phone.
And then i see that automatic rotate isn't working, because the shealth walking mate wasn't counting the steps.
So i tried rotating my phone didn't work.
I did *#0*# to check the sensors and see that
Accelerometer sensor is showing 0 for everything
Proximity Sensor same
Barometer Sensor same
Light sensor working
Gyroscope Sensor same showing 0
Magnetic sensor same showing 0
I did a hard reset and didn't solve my problem, i then flashed the same firmware again and still didn't work.
Can you guys help me out?
Can't go to samsung tech since i didn't buy the phone their store and i'm from south america (Country Suriname) also
Wishaal said:
Hi all,
I have a i9500 phone.
I have this firmware installed onto my phone
I9500XXUEMJ5_I9500ODDEMJ5_I9500DDUEMJ5_HOME
2 days ago i got a push update, and then i updated my phone.
And then i see that automatic rotate isn't working, because the shealth walking mate wasn't counting the steps.
So i tried rotating my phone didn't work.
I did *#0*# to check the sensors and see that
Accelerometer sensor is showing 0 for everything
Proximity Sensor same
Barometer Sensor same
Light sensor working
Gyroscope Sensor same showing 0
Magnetic sensor same showing 0
I did a hard reset and didn't solve my problem, i then flashed the same firmware again and still didn't work.
Can you guys help me out?
Can't go to samsung tech since i didn't buy the phone their store and i'm from south america (Country Suriname) also
Click to expand...
Click to collapse
I tried to flash the latest version of arrow rom, and all the sensors worked for like 5 minutes then it stopped again.
I flashed the same rom again and same thing happening again.
I had to flash back to GoldenEye 4.3 to get my dialer back! After I flashed ASOP (or any non touchwiz based ROMs) I had a bug where I couldn't turn my screen back on during a call...
It was extremely annoying but the ROM's that I were running were so good that I tolerated it. Well today I decided I couldn't let my phone not be a phone. I have this problem with
Kangakat 5 Stock Kernel
KangaKat 6 Stock Kernel AND Ktoonsez's kernel
CM11 with stock kernel
CM10.2 with stock kernel
Danvdh's ASOP 4.4.2 ROM with stock kernel
None of these work. Its still the same call bug.
I've tried proximity sensor recalibration. Didn't work. I've tried compressed air. Didn't work. Nothing has worked.
Finally I HAD to go back to debloated TW GoldenEye 4.3 which I am on right now, and it doesn't work. Proximity sensor is enabled in settings but when I pull my phone away from my head the screen doesn't turn on! However I can atleast access my dialer so atleast I can use my phone as a freaking phone!!!!
I typed *#0*# and went to the test area and went under sensor and my proximity sensor will have a value of 69 until something gets in its way and then quickly max out at 255...but I noticed also that the farther my finger goes the lower the number gets so it seems like its doing its job correctly. However the screen is always green and always vibrating. It never stops...
Guys. I can't stand 4.3 debloated. Once you've run KitKat you can't go back. Do you guys have ANY last ditch efforts on how I can fix this? Maybe even just disable the proximity sensor when I flash a ROM? I just hate Touchwiz. Been flashing 300MB ROM's and had to flash a 1.4GB ROM today which is just stupid...
please please help..
EpicMango said:
I've tried proximity sensor recalibration. Didn't work. I've tried compressed air. Didn't work. Nothing has worked.
Click to expand...
Click to collapse
Do you still have a warranty? Go back to stock and make a claim.
EpicMango said:
I had to flash back to GoldenEye 4.3 to get my dialer back! After I flashed ASOP (or any non touchwiz based ROMs) I had a bug where I couldn't turn my screen back on during a call...
It was extremely annoying but the ROM's that I were running were so good that I tolerated it. Well today I decided I couldn't let my phone not be a phone. I have this problem with
Kangakat 5 Stock Kernel
KangaKat 6 Stock Kernel AND Ktoonsez's kernel
CM11 with stock kernel
CM10.2 with stock kernel
Danvdh's ASOP 4.4.2 ROM with stock kernel
None of these work. Its still the same call bug.
I've tried proximity sensor recalibration. Didn't work. I've tried compressed air. Didn't work. Nothing has worked.
Finally I HAD to go back to debloated TW GoldenEye 4.3 which I am on right now, and it doesn't work. Proximity sensor is enabled in settings but when I pull my phone away from my head the screen doesn't turn on! However I can atleast access my dialer so atleast I can use my phone as a freaking phone!!!!
I typed *#0*# and went to the test area and went under sensor and my proximity sensor will have a value of 69 until something gets in its way and then quickly max out at 255...but I noticed also that the farther my finger goes the lower the number gets so it seems like its doing its job correctly. However the screen is always green and always vibrating. It never stops...
Guys. I can't stand 4.3 debloated. Once you've run KitKat you can't go back. Do you guys have ANY last ditch efforts on how I can fix this? Maybe even just disable the proximity sensor when I flash a ROM? I just hate Touchwiz. Been flashing 300MB ROM's and had to flash a 1.4GB ROM today which is just stupid...
please please help..
Click to expand...
Click to collapse
I had the same bug. Have you wiped? I ran kitkat, and after many bugs like the one you're describing, wifi disconnects and app errors I went back to 4.3 stock. Debloated, and run nova prime with kiatkat theme. Looks like kitkat, feels like kitkat, but I don't have any bugs.
I should've update this thread...I FOUND A SOLUTION! It basically forces a new value for the sensor to pick stuff up on!
I'm now back on optimized 4.4 KK with GravityBox and I hold the perfect phone in my hand ATM
Here is the solution
http://forum.xda-developers.com/showthread.php?t=2045569&page=4
Methods that worked for me.
Method 1.
Blow Air it will solve your prob hopefully.
Method 2.
go to samsung code *#0*#. then SENSORS and Read your Proximity sensor values.
<<< DECISION >>>>>
####Calibration isnot needed if ####
.
your phone doesnt vibrate in normal but does so when u physically put your finger on the Sensor.
#### Calibration needed if ####
.
your phone is vibrating in this menu no matter what, you put your finger on the sensor or not
Follow these steps
1. download Android Terminal from store
2. type these commands to calibrate automatically
$ su
# echo 0 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
# echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal
Reboot and see if it works.go to *#0*# and check if it continuously vibrating or only does so when you put your finger on the SENSOR.
<<<< IF Continuously Vibrating Follow these steps>>>>
you need to manually put values in ur /efs/prox_cal.it Reads Hexadecimal value. so you have to convert your decimal values into HEX.
##### FIND YOUR Decimal Values and pushing them into /efs/prox_cal ######
Method : finding two values for calibration . offset + normal value.
##.. FINDING OFFSET ######
cat /sys/devices/virtual/sensors/proximity_sensor/prox_cal
note down the values it returns.. mine is 5,64,100.. you only need the 1st value which is 5.
### FINDING NORMAL STATE ######
cat /sys/devices/virtual/sensors/proximity_sensor/state
note down the value if returns. mine is 64
now ADD OFFSET value + Normal Value
5 + 64 = 69
Convert in Hexadecimal which is 45.
<<<<<<<<<<< Pushing the value in /efs/prox_cal >>>>>>>>>>>>>>
# echo -en $ '\x45' > /efs/prox_cal
then
# chown system:system /efs/prox_cal
# chmod 644 /efs/prox_cal
# sync
# Reboot
All done. after that go to *#0*# then SENSORS and move your finger on the sensor, your phone will Vibrate only when you put your finger on the sensors.
Manual method worked for me.
ENJOY.
Click to expand...
Click to collapse
Those instructions will sound confusing to you, but if you read the entire thread and get an idea of what they are talking about then you'll understand! It worked for me! And I'm positive it will work for you to!!
It turned out that my proximity sensor was always on! If you type in *#0*# into the stock dialer you'll bring up diagnostics. Go to sensor. What should happen is when you wave your hand near the sensor the screen should turn green and vibrate. If you are always vibrating regardless (my situation) that means your proximity sensor is always on and you have to hard calibrate it.
I'm thinking of doing a full writeup for this so others can fix this issue! I have no problems now!!! So Happy to report this!
Hi all.
I have an issue with proximity sensor on my i9505.
It works well when i reboot my phone... But after 30 min - 1 hour it stops to work.
I'm on c-rom 7.1 but i have this issue on all roms.
I've tried to clean it. I've disassembled my phone and cleaned the sensor with alchool and a cotton fioc, but i have even the problem.
I've noticed the problem because when i go to modify the automatic brightness values, the value "lux" is stopped on a number and doesn't change...
What can be? Please help me!!!
santya95 said:
Hi all.
I have an issue with proximity sensor on my i9505.
It works well when i reboot my phone... But after 30 min - 1 hour it stops to work.
I'm on c-rom 7.1 but i have this issue on all roms.
I've tried to clean it. I've disassembled my phone and cleaned the sensor with alchool and a cotton fioc, but i have even the problem.
I've noticed the problem because when i go to modify the automatic brightness values, the value "lux" is stopped on a number and doesn't change...
What can be? Please help me!!!
Click to expand...
Click to collapse
Hi mate,
See if the sensor calibration is ok, check here:
http://forum.xda-developers.com/showthread.php?t=2569141
Hi all.
Is it possible to fix light sensor for good values?
I have rooted i9506 with samsung fw v 4.4.2.
I had custom cm11 fw installed and light sensor worked perfect. Sadly i don't like cm so went back to default firmware and sensor again shows nonsense.
Now there is light shining in the room and pbone shows only 2lux. I have s3 too.it shows 60-70lux
Same problem: new S4 i9506, low light sensor values
Using [ROM][GT-I9506][ks01ltexx] LineageOS 16.0 UNOFFICIAL for the Galaxy S4 LTE-A, was working fine for a while, but at some point in first few days of use the screen started going very dim, and sensor apps report very low lux readings, ranging from 1 to 200 when older S4 shows 50--1500... Using Lux app to compensate, but that's not curing the underlying problem...