yashsingh1/xdaforums huggingface dataset:
[Galaxy Note 3 Q&A, Help & Troubleshooting] denialnw10:
You're more likely to get the science of it from someone else, sorry. Prior to blowing into the speaker I wiped and re-installed the software, but there was no change.

All I can say is that it wasn't working (ie. the screen remained off when I removed it from my face during calls until I pressed a physical button) and then I decided to blow air into the earpiece next to the sensor and now it works.

For me and the others that tried that solution, it seemed to work and that's why I concluded that the problem is most likely to be hardware.
[Galaxy Note 3 Q&A, Help & Troubleshooting] MarkSkov:
Hmm, it doesn't seem to help with mine, though that doesn't mean that this isn't a dust related issue. Certainly worrying that multiple people have had success with this "technique". How long has yours lasted between "blows"?
[Galaxy Note 3 Q&A, Help & Troubleshooting] tpdi:
What does yur y-angle show when your device is vertical?

I'm getting values in the low 80s for y-angle when the device is held vertically. Does this match what others are seeing on their devices?

More generally, how can I verify that my sensors are reporting the right values?.
[Galaxy Note 3 Q&A, Help & Troubleshooting] KTM690:
I too am having the same problem. My sensor vales go from 150 uncovered to 1004 fully covered.

This indicates that the sensor is working but it is not going low enough for it to turn the screen on during calls. This shows that the threshold setting is way to low. I'm no software expert but surely this could be fixed by changing the threshold value to something like 300+ in the software.
[Galaxy Note 3 Q&A, Help & Troubleshooting] ardeban:
Happening the same here... value from 100 and something and 1024.

Annoying...
[Galaxy Note 3 Q&A, Help & Troubleshooting] ardeban:
Solved in Note 2 forum, but only for rooted users:

Finally, this fixed my problem. I don't know why, but the other solution worked one time while using a CM 10.2 nightly

Code:

$ su

$ echo 0 > /sys/devices/virtual/sensors/proximity_sensor/prox_cal

$ echo 1 > /sys/devices/virtual/sensors/proximity_sensor/prox_calBut, when I upgraded to the latest nightly, this stopped working. It wouldn't work even if y restored my stock ROM backup using TWRP, I even flashed a stock image with odin and the sensor would still malfunction.

Today I followed this steps using the values returned for my phone and it finally worked! I did this.

Code:

$ cat state #finger on the sensor to test if the sensor is working properly

120

$ cat state #blank value

10

This returned 255 #finger on the sensor and 69 #blank value

and when I did

Code:

cat /sys/devices/virtual/sensors/proximity_sensor/prox_cal

this returned 47,60,45.....so my offset was 47. Ths sum of offset and #blank value was 47 + 69 = 116 that is equal to 74 in HEX.

so I did

Code:

$ echo -en $'\x74' > /efs/prox_cal

and then

Code:

$ chown system:system /efs/prox_cal

$ chmod 644 /efs/prox_cal

$ sync

After that I rebooted my phone from the terminal using que command

Code:

$ reboot

and that was it! Now my sensor is fixed and survives reboot. Thanks!
[Galaxy Note 3 Q&A, Help & Troubleshooting] juliano76:
Do you think you may explain once again in details what you have done so that the sensor works properly after reboot. Thanks!
[Galaxy Note 3 Q&A, Help & Troubleshooting] ardeban:
Step by step:

1 open a terminal session, type "su" ro grant root permissions

2 type cd /sys/devices/virtual/sensors/proximity_sensor/

3 with the sensor uncovered type "cat state" and write down the value (43 in my case)

4 type "cat prox_cal" and write down the first value (this is the offset), in my case it was 201

5 sum both values, in my case it was 244

6 Convert it to hex (http://www.disfrutalasmatematicas.com/numeros/binario-decimal-hexadecimal-conversor.html), in my case, F4

7 type "echo -en $'\xF4' > /efs/prox_cal", instead of F4, put your value

8 type "chown system:system /efs/prox_cal"

9 type "chmod 644 /efs/prox_cal"

10 type "sync"

11 type "reboot"

And that's all, we've increased the value and this survives even a reboot.

BR!
[Galaxy Note 3 Q&A, Help & Troubleshooting] juliano76:
Thank you very much for your fast reply. Today I'm very happy because I'm about to find the solution of that issue bothering me since I bought this device. However, would you be so kind to rewrite the commands in the case I'm using Terminal emulator installed on my device?

Thank you!
[Galaxy Note 3 Q&A, Help & Troubleshooting] ardeban:
That's for terminal emulator on the phone ;)
[Galaxy Note 3 Q&A, Help & Troubleshooting] juliano76:
It was very hard for me to do it but finally succeded. RThank you very much for your assitance. Wish you all tyhe best from my heart.:highfive:
[Galaxy Note 3 Q&A, Help & Troubleshooting] Red reign:
took me a bit, i'm a total noob. for the other noobs out there, i'd like to add step 0...

type "/system/xbin/su -l"

thats to login as superuser...

but big thanks for posting! worked like a charm!!!:good::D
[Galaxy Note 3 Q&A, Help & Troubleshooting] ardeban:
I will update the post.

Glad it's working for you also, it was driving me nuts :D
[Galaxy Note 3 Q&A, Help & Troubleshooting] hwkchin:
thanks
[Galaxy Note 3 Q&A, Help & Troubleshooting] invivo:
Thank You ardeban!

Worked as advertised on my Note 3 :good:

My "cat state" was 101

My "cat prox_cal" was set to 0

So my hex value will be 85

I hope Samsung gets publically beaten up on this for not addressing a major bug to the same feature they paraded around on national TV trying to sell phones that don't work correctly.
[Galaxy Note 3 Q&A, Help & Troubleshooting] duytrum444:
My "cat state" was 77

My "cat prox_cal" was 0,120,80

Now will i have hex ???

Please help me
[Galaxy Note 3 Q&A, Help & Troubleshooting] ardeban:
Your hex value is 4D
[Galaxy Note 3 Q&A, Help & Troubleshooting] duytrum444:
Thank you!!! I have a question. This method is creat a file prox_cal then copy to efs folder,right?? If i want to back normal, i just delete it?? Will it work on any rom??
[Galaxy Note 3 Q&A, Help & Troubleshooting] Shooshi:
Cat State: 90

Cat Prox_Cal: 0, 120, 80

What would my Hex be? I don't get how the hex conversion tool work...

Thanks!

Edit: I figured it out... its 5A... :D

---------- Post added at 08:12 AM ---------- Previous post was at 07:59 AM ----------

You guys are amazing! I just did this and it fixed my problem!

Thanks to whoever that figured this out!!
[Galaxy Note 3 Q&A, Help & Troubleshooting] ZION959:
Thanks for the guide. My T-Mobile Note have this problem also. Now it work wonderful.
[Galaxy Note 3 Q&A, Help & Troubleshooting] demmo81:
actually this sollotion worked:)

strangly now the Prox_Cal values are like 348769 somehitng not like before 0,120,80

but it worked....:)

Thank you so so much

you are the best :)

---------- Post added at 04:27 PM ---------- Previous post was at 04:22 PM ----------

hey thanks for the way of doing that.,..its working now

although it changed the State to 34789,347824,34... something ...huge figures now but its working...

before it was like 0,120,80

thanks m8
[Galaxy Note 3 Q&A, Help & Troubleshooting] kuroy301:
Please help.

Mine is 92

cal is 0,120,80

thanks...
[Galaxy Note 3 Q&A, Help & Troubleshooting] fjrtha:
Verizon Note 3 Proximty Cal

Worked as advertised, thanx for the tutorial. Outstanding work!
[Galaxy Note 3 Q&A, Help & Troubleshooting] zmfl:
The terminal emulator fix is probably the more permanent one (thanks for that), but for now I managed to fix this with just blowing into the earpiece really hard. The reading for the sensor was about 80-90 before, and now after blowing into it it's 50-60, which is fine I guess.

Unfortunately this phone has a serious dust problem. There's dust around the gap where the screen meets the body, around the earpiece, and you'll definitely see some dust in the proximity sensor if you look at it really close.
[Galaxy Note 3 Q&A, Help & Troubleshooting] malnsk:
i have the same issue, but the gestures work except the quick glance option when the screen is turned off. when in the call screen my screen won't turn off when i put it on my ear.
[Galaxy Note 3 Q&A, Help & Troubleshooting] scottarbaugh:
Awesome. I'm surprised that this worked. I originally had the proximity sensor issue, and using a can of compressed air originally fixed it for me. Later, the issue came back again and the compressed air trick no longer worked. The steps in this post did the trick. Thank you!!!
[Galaxy Note 3 Q&A, Help & Troubleshooting] emyllis:
It worked for me too! After a week of frustration :) Thanks so much for sharing this solution.
[Galaxy Note 3 Q&A, Help & Troubleshooting] denialnw10:
OK,

Forgot to get back to you guys but, the issue did return and so I sent my phone back to Samsung for a warranty repair and it's been over a month now with no recurrence.

Would advise warranty return if there is no quick fix. I tried two quick fixes before I decided to let Samsung deal with it. Now I'm sorted! :)

Cheers,

D
[Galaxy Note 3 Q&A, Help & Troubleshooting] indieN8:
Terminal edit worked like a charm! Thanks!
[Galaxy Note 3 Q&A, Help & Troubleshooting] skrilin5:
Worked well!!! thanks
[Galaxy Note 3 Q&A, Help & Troubleshooting] SquirtingCherry:
Guys the re-calibrating is only a temprary fix you know that right, i work at a phone repair shop and i suffered the same thing with my prox sensor, so i opened up the phone and my prox sensor hole was filled with dust because they placed it too close to the earspeaker so it collects dust, you need to clean out the proximity sensor lens and all is fine, i myself have put an little piece of foam between the earspeaker and proximity sensor hole so it blocks the dust from now on.

Re-calibrating may work for sure but its not the reason your sensor goes nuts, open up your phone and see what i mean.
[Galaxy Note 3 Q&A, Help & Troubleshooting] undrwater:
Beauty. Was the teardown simple? Do you perhaps have a link to one?
[Galaxy Note 3 Q&A, Help & Troubleshooting] zadigre:
I would appreciate more information on that too... I have all the tools... But before doing it, I would like to know if it's "easy" or not.

Sent from my SM-N900 with Tapatalk
[Galaxy Note 3 Q&A, Help & Troubleshooting] SquirtingCherry:
teardown is super easy like all samsung phones, just unscrew all the screws you see when you take off the backplate and then use the s-pen to gently lift up the midplate, its all clicking from here, when you have taken it off you can lift up the proximity sensor and clean the lens with an earbud or a folded piece of cloth.

here is a video of the teardown

http://www.youtube.com/watch?v=p3jTy4DZLnw
[Galaxy Note 3 Q&A, Help & Troubleshooting] Mircoron:
Put this file in /efs/ with "ES file explorer" or "root explorer", rename to "prox_cal" only and set permissions to "rw- --- ---",

reboot and all is ok
[Galaxy Note 3 Q&A, Help & Troubleshooting] undrwater:
This ended up within well. I would recommend popping up both the ear speaker AND the proximity sensor. Lots of lint ended up here. Placing some kind of barrier so lint does not get into the cavity where the sensor sits. I see now why using canned air no longer worked; it just forced the lint into the pocket.

Now I can make and take calls without pressing the power button, or making inadvertent key presses with my cheek.

Thanks!
[Galaxy Note 3 Q&A, Help & Troubleshooting] tadyanh:
I tried to type the line 2, but the result is always not found. I am noob, so can someone help me with this?
[Galaxy Note 3 Q&A, Help & Troubleshooting] Mircoron:
http://xdaforums.com/showpost.php?p=50682403&postcount=45
[Galaxy Note 3 Q&A, Help & Troubleshooting] pallabbaba:
Where can I kiss you? It worked like a Thailand *****'s ass!

Thanks from the bottom of my heart :)
[Galaxy Note 3 Q&A, Help & Troubleshooting] zmfl:
it happened again and this time i had to tear it apart. a LOT of dust there...

works as new after cleaning.
[Galaxy Note 3 Q&A, Help & Troubleshooting] gaganmohal:
thanks it worked
[Galaxy Note 3 Q&A, Help & Troubleshooting] fonuza:
Had same problems, screen off when on call near ear but would not turn back on when removed.

Blew here and there, worked for a few days then problem started again.

Looking from front of phone the sensor screen area looked clean.

Pull it apart - I could see the dust that built up. Cleaned dust off.

Now it's working as it should. :victory::good:

Thank you!
[Galaxy Note 3 Q&A, Help & Troubleshooting] cdvillarreal:
Muchas gracias genio!! / Thank you very much genius!!

Muchas gracias. Funcionó perfectamente. No encontraba la solución por ninguna parte. Sos un genio. Saludos desde Argentina. :good:

Thank you very much. It's works perfectly. I could not find the solution anywhere. You're a genius. Greetings from Argentine. :good:
[Galaxy Note 3 Q&A, Help & Troubleshooting] SquirtingCherry:
I just put a little piece of rubber between the speaker hole and the proximity sensor so that the dust from the speaker cannot reach the sensor.
[Galaxy Note 3 Q&A, Help & Troubleshooting] paolo200:
Way to go ardeban!! the terminal fix worked like a charm and I didn't even put my HEX value, I just left yours. I just hope it lasts beyond reboots and updates.

I know it's because of the dust but I prefer not to open it up, I'm afraid to break something in the phone

When I think that I almost didn't root my note 3... I never would have thought that rooting would not just allow me to customize it but actually fix a very important part of its functionality like the proximity sensor calibration. That sensor has never worked properly since I purchased it last October. What is more upsetting is that after multiple firmware/OS updates, the problem has never been solved even though it has been reported by so many users
[Galaxy Note 3 Q&A, Help & Troubleshooting] fastguy:
I also teared off the phone using a youtube video as a guide and then removed proximity sensor, it will full of dust. I cleaned the area, reassembled the phone, now working perfect. Not really hard to do.
[Galaxy Note 3 Q&A, Help & Troubleshooting] BLEK0TA:
Is normal my proximity senzor is still little red? Everything works fine. Like test or calls but is still slightly red. When i restart phone is black but after first call is slightly red and turn black only after restart.. but works fine. Any solution?
[Galaxy Note 3 Q&A, Help & Troubleshooting] kpederson9999:
Fix

The problem isn't really with dust being in front of the proximity sensor. The problem is there is light transfer between the Proximity sensor and the Ambient light sensor. If you take the back off the phone and remove the proximity sensor/light sensor and make a gasket to go in between where the 2 sensors go that will fix it permanently. My Proximity sensor ADC number would read in the 80's when there was nothing in front of the screen and now that I made a gasket between the 2 sensors it reads a dead 0 all the time when nothing is in front of the screen and the number gradually goes up like its supposed to when you get closer to the sensor.

Removing the sensor was relatively easy and I used 2 thin strips of electrical tape that I cut with an x-acto knife to fit the space.:D
[Galaxy Note 3 Q&A, Help & Troubleshooting] Red reign:
Not sure what I was doing wrong, but this time I had to manually change permissions on the file with es file explorer. Was failing repeatedly. This may help the next guy, need to make it readable by "group".
[Galaxy Note 3 Q&A, Help & Troubleshooting] hugufgs:
Problem Solved

Finally, I have my problem solved! :good:
[Galaxy Note 3 Q&A, Help & Troubleshooting] lauri_ylonen:
help me please how write value?

su

root@android:/ # cd /sys/devices/virtual/sensors/proximity_sensor/

cd /sys/devices/virtual/sensors/proximity_sensor/

root@android:/sys/devices/virtual/sensors/proximity_sensor # cat state:43

cat state:43

tmp-mksh: cat: state:43: No such file or directory

1|root@android:/sys/devices/virtual/sensors/proximity_sensor # cat prox_cal:20

_cal:201

tmp-mksh: cat: prox_cal:201: No such file or directory

1|root@android:/sys/devices/virtual/sensors/proximity_sensor #
[Galaxy Note 3 Q&A, Help & Troubleshooting] lauri_ylonen:
check on n9005 but still problem and not fix!!!:(
[Galaxy Note 3 Q&A, Help & Troubleshooting] Albatros2605:
I have had the problem with this sensor (black screen in call even my head was far away the screen). I tried the apk. "S4 sensors [requires root!]" from Google play. I know it's for S4 but I was desperated. On my n9005 was working awesome ! My sensor problem was gone. Maybe this will help you.
[Galaxy Note 3 Q&A, Help & Troubleshooting] junaidqt:
i fixed it easily...try this once please

Same happened with me. I googled many forums and i found solution myself....Just do as i did ...

- Go to phone dialer

- Enter *#0*# and dial

- Tap on "Sensor" it will keep vibrating contin'sly with green screen. Leave it vibrating...

Now its time for action...

- Just hold in one hand and stroke it 4/5 time on other hands palm with camera side down just like you are clapping. Stroke it till it stops vibrating.

My note 3 sensor problem is solved since last 2 days.

Hope it will help many users. If its solved for you then please share this trick so we can help many.

Good Luck
[Galaxy Note 3 Q&A, Help & Troubleshooting] khudko83:
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!
[Galaxy Note 3 Q&A, Help & Troubleshooting] id_nellly:
Sensor ok... I think

Software problem?

My sensor respond ok to sensor test... But is not working.

Not turning green and vibrate... Not turning screen off durring calls...

What can i do to fix this...
[Galaxy Note 3 Q&A, Help & Troubleshooting] id_nellly:
Nobody????
[Galaxy Note 3 Q&A, Help & Troubleshooting] Az-one786:
Wow...!!

Your method is working like "magic" for me .... so easy , I just hold the sensor and clapped my hand several times just like what u says before ... And now my sensor seem to be start working back .. I can see ADC value is increase from 0 to 20 just for now.... :good:

Thanks Bro .... ;)
[Galaxy Note 3 Q&A, Help & Troubleshooting] lansi.cheng:
My note 2 same problem has been solved!

have your problem solved since you posted this last year? my phone has same problem since after few months i bought, i found the solution here. i am new user here can't post external link here. at androidlegend dot com type in the search field of that website.. how to perform proximity sensor. from there you will find the tutorial to solve your problem.

just follow the instruction to recalibrate your sensor. while check your offset and normal state values please make sure your phone is in very dark environment.
[Galaxy Note 3 Q&A, Help & Troubleshooting] CalcProgrammer1:
Awesome, recalibrated my sensor with the efs file and it worked perfectly. I never had an issue with the sensor until now (a month past one year of owning the phone, plus Knox is long tripped so warranty isn't happening). If it gets worse I'll take it apart and clean the sensor but for now the recalibration trick worked just fine.
[Galaxy Note 3 Q&A, Help & Troubleshooting] ThePRG:
Had issues with proximity sensor after updating my Note3 to 5.0, this method helped to get the sensor back to work. Thank you!

My values were 221 and 0, resulting in DD in hex sum )
[Galaxy Note 3 Q&A, Help & Troubleshooting] newbie19:
Hi guys.

Could someone tell me how to do the terminal emulator fix. i installed terminal emulator but i cant seem to put in the commands.

---------- Post added at 12:52 AM ---------- Previous post was at 12:17 AM ----------

I was able to fix it with the recalibration only problem is it is not sensitive enough for most of the air gestures but it fixes the issue of not being able to hangup
[Galaxy Note 3 Q&A, Help & Troubleshooting] dyuburg:
Sensor dead?

If cat state #finger returns 1, then sensor is broken?
[Galaxy Note 3 Q&A, Help & Troubleshooting] pooch11:
when doing this step: 7 type "echo -en $'\xF4' > /efs/prox_cal", instead of F4, put your value

I always get PERMISSION DENIED. What am I doing wrong? I definitely have root with su permission. Anything else?
[Galaxy Note 3 Q&A, Help & Troubleshooting] ellghost00:
nice

thánks
[Galaxy Note 3 Q&A, Help & Troubleshooting] sky034:
Help!

My Cat State: 0 n Cat prox_cal: 0, 120, 80

how do i get my hex when my cat state is 0. :( even i put my hands on the sensor it wont vibrate or change into green. i already replaced my sensor with new one. but still it doesn't work. help please! :crying:
[Galaxy Note 3 Q&A, Help & Troubleshooting] joeyakaspce1130:
I was able to fix my proximity sensor with this app: https://play.google.com/store/apps/details?id=com.vrognaas.proximityfix

I'm assuming it calibrates it? I don't know, but my sensor wouldn't work and when I tested it, it didn't operate correctly either and after running this app, it worked PERFECTLY. I was very surprised to say the least lol

The only problem I am having now, is that the screen turns off and on fine during a call BUT IT STILL is responsive, meaning I can touch where the end call button is when the screen is off and it will hang up...

Anyone know any reason for this?

Verizon Note 3 on T-Mobile service running CM13
[Galaxy Note 3 Q&A, Help & Troubleshooting] Ch saim:
dear sir i have problem in my samsung note 3.

after restarting proximity sensor work for few mints after few mints sensor stop working,kindly solve my problem
[Galaxy Note 3 Q&A, Help & Troubleshooting] JJEgan:
You read and search the thread first its all posted .
[Motorola Atrix 2] Imabitslow:
I have a motorola atrix 2 mb 865. i was on gb 2.3.6 and not knowing what i was doing i updated it to jelly bean using cwm from recovery menu. i got a message saying every thing was successful but when it went to boot it got stuck in a boot loop. i have tried rsd lite fxz fastboot but my computer will not recognize the phone i have uninstalled and reinstalled the correct drivers but still the pc will not recognize. i am able to update with sdcard going into stock recovery on android but every blur_version i have tried either says assert failed or veryfing signature failed. im at a complete loss here please can some one help me. i have looked all over the web but to no avail.
[Motorola Atrix 2] buddykartz:
Just download suitable ICS ROM from the below link and flash your phone using RSD Lite application.

ROM Download link:

http://xdaforums.com/showthread.php?t=1934874

Tutorial:

http://www.youtube.com/watch?v=AHaEHjSzvQQ
[Motorola Atrix 2] Imabitslow:
the thing is that i cant get my pc to recognize my atrix2
[Motorola Atrix 2] minhajlk:
Switch the device to Bootloader and see if the computer can see your device. Press the Vol Down + Power Switch simultaneously to switch to Bootloader.
[Motorola Atrix 2] hatimc:
Download the latest drivers

Download the sbf files from the droid developers

Switch off the phone

Download volume key +power button

Then connect to PC

Load sbf file to rsdlite and flash

Say thanks or click thanks :good: