yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Q&A, Help & Troubleshooting] Maozvi:
Thanks!

Many thanks! this method solve this issue for me :)
[Galaxy Note II Q&A, Help & Troubleshooting] Lightning:
Well done for working that out.... it's the only thing that worked for me ;)

(i must admit i needed to use a hex calculator)

PS This worked on my Samsung Galaxy S3 SCH-i535
[Galaxy Note II Q&A, Help & Troubleshooting] LenaertsJeroen:
Fantastic! Been having issues with the prox sensor for ages! Now its fixed again!
[Galaxy Note II Q&A, Help & Troubleshooting] Crossoverdoc:
On Cm11.. Entering that code into the dialer doesn't work for me.
[Galaxy Note II Q&A, Help & Troubleshooting] Formhault:
Yeah, well, *#0*# brings you to Samsung test modem. CM11 = not Samsung. TouchWiz = Samsung.
[Galaxy Note II Q&A, Help & Troubleshooting] rohanverma:
Please help, have tried this and everything else

OK. This is so weird I have tried everything.

When I check the cat state, I see the difference with finger on (210) and finger off (2). So I can conclude no hardware fault. I get my offset and push it to EFS. When I check the values the offset remains. But my proximity sensor still doesn't work.

I have tried different ROM's with clean installs (wipe cache, delvick cache, format system, etc.). I have tried the factory default samsung s3 and CM10.1.3. Which means different kernals and what not too.

I have tried compressed air and physcially taking the phone apart to see if its dirty. Nothing.

When I use something like Sensor Box, it doesn't recognize any change. Which means, from my perspective....the values from the proximity sensor aren't reaching the right place or aren't being read by the OS somewhere.

Any ideas? Can anyone help? Thanks very much in advance!

Details:

I'm on CM 10.1.3 right now (4.2.2).

i747mvluemk5
[Galaxy Note II Q&A, Help & Troubleshooting] Formhault:
With all that you reported being taken into account... There could be a possibility that the sensor is malfunctioning :/ .
[Galaxy Note II Q&A, Help & Troubleshooting] rohanverma:
Yeah, but it just bugs me because the sensor works like it's supposed to when I check it's cal state. The sensor is working... the information is just not getting through to where it needs to go.

---------- Post added at 10:21 PM ---------- Previous post was at 10:13 PM ----------

Update:

not a single sensor is working on the phone. I have another i747m to compare against.

I took the broken back to stock firmware. I go into the *#0*# menu and none of the sensors are working. The light, proximity, gyro, magnetic, are all off not moving numbers. Where as the functioning one has all sorts of numbers that are changing. The only number that changes is the proximity sensor..the adc value changes but the state stays to 0!

What could cause ALL sensors to not function?

What coul
[Galaxy Note II Q&A, Help & Troubleshooting] mikeuz:
What could cause ALL sensors to not function?

I may have an idea about the malfuncioning of the sensors as something like that happened to me once I restored a backup (4.1.2) and I was on 4.3 JB (apparently downgrading is not useful if using a nandroid backup)

so after a few days in doing some research and asking here on XDA nothing worked

but I had an old EFS backup (the very first one I made when I bought the phone) and decided to flash an official carrier ROM from my carrier Telcel MX and then I restored my EFS (cuz I lost my IMEI) and the problems with my sensor are gone now.

Hope it helps
[Galaxy Note II Q&A, Help & Troubleshooting] rohanverma:
Yes, that's very helpful. I also think it has to do with the efs. I think for Samsung phones the efs is pretty important. But unfortunately I don't have an efs backup.

I understand I can't just take another phones efs folder, but could I take and restore part of it? Like where the hardware or sensor information is?
[Galaxy Note II Q&A, Help & Troubleshooting] mikeuz:
I dont know.

you could try altought I don´t know how.
[Galaxy Note II Q&A, Help & Troubleshooting] Formhault:
Actually, your proximity sensor is not really correctly working. It should show 255 (when covered) and 20-50 when uncovered. Yours shows a value very close to 0 when uncovered and 202 when covered. :confused:

Now that's... funky... :eek:

---------- Post added at 09:28 AM ---------- Previous post was at 09:26 AM ----------

I think you can take a good file explorer, such as File Explorer (FX, with the respective Root Add-On) or ES File Explorer and manually replace all the sensors-related files in the EFS partition from another backup.

EDIT: I just checked... the EFS partition doesn't seem to contain any sensors-related files. Besides, any file I try to open is either empty, either has one character or something like that.

The (only) file inside the imei folder has a single code in it that says "BTU". LMAO.

If it would have been that simple to meddle with EFS contents, I think people wouldn't be f***ed without having a backup of it anymore. So... I don't think there's anything you can do without a backup of it :eek:.
[Galaxy Note II Q&A, Help & Troubleshooting] berfles:
Mine has been troublesome for months now. When I put my finger over the sensor I get 255(255,255,255) and when I remove it I get 51(51,51,51). Blowing into the earpiece seems to help sometimes, but usually it doesn't.

I tried the automatic recalibration but it didn't do anything, can anyone advise? It's a bit late right now and I can't really figure out what I should do at this point.
[Galaxy Note II Q&A, Help & Troubleshooting] Formhault:
You can manually calibrate it and then make the values stick (on the file from the EFS partition). That totally fixed the problem I had on my S2 :good:.

How to calibrate.

Before you start making changes to the file from EFS, make sure the EFS partition is writable. How to mount it RW? See here. I know I failed like 3 times at this because I didn't know I had to mount EFS as RW, so the values obviously didn't stick...

That will surely help you. You just have to get it right :D.
[Galaxy Note II Q&A, Help & Troubleshooting] berfles:
Thanks. I'm already stuck on the

$ cat state #finger on the sensor to test if the sensor is working properly
120
$ cat state #blank value
10

part though, says it's not found. I think I need to go to sleep because I'm probably missing something very simple.
[Galaxy Note II Q&A, Help & Troubleshooting] Formhault:
My bad. This post is more comprehensive.

Still, it is not mentioned how to mount EFS as read-write there neither, so you'll still have to check the link I mentioned in my previous post.

Hope you get it right this time :D.
[Galaxy Note II Q&A, Help & Troubleshooting] berfles:
Thanks again. What I did so far was basically everything but that step I had issues with. I used the numbers I saw from the *#0*# menu, so since my blank value seemed to settle at 51 I used that. My offset came back as 0, so that means the offset+blank = 51 which = 33 in hex. I used that number but didn't reboot because I just wanted to test quickly and my sensor is already working as it should.

When I wake up I'll make sure EFS is read/write and try those other steps to double check my numbers and do it again.
[Galaxy Note II Q&A, Help & Troubleshooting] planetf1:
And me.

BRILLIANT! the echo'ing of 0, 1 didn't help, but the manual insertion into efs worked a treat.

Now my guess is my sensor has drifted a lot - I ended up with a value of 7B, so it's perhaps a sign of pending failure - not sure what others get, but it's fixed the immediate issue. even though my phone is under warranty (though knox=1) it would be hassle resetting and being without for a while!
[Galaxy Note II Q&A, Help & Troubleshooting] lettereleven:
Manual calibration is actually easy and works.

Call me lame, but I feared Terminal for many months. I looked for multiple ways of fixing my sensor issue, even considered reverting to stock S4 (yuck). Big thanks to those that made this "how to fix your sensor". The manual method below totally works, and its really not scary.

Note for the noobs (like me): make sure you enter "su" to get super user/root access. You dont actually type the hash marks. You get those when you are in super user mode. No super user, no work. I know, totally obvious for clever people, but i didnt know.

-Jamie.

Galaxy S4 running Danvh's incredible Dandroid rom
[Galaxy Note II Q&A, Help & Troubleshooting] AMoosa:
I was a bit wary of the manual method. I tried it with the values reported an by my phone and it didn't work. Then I tried it with the values in the example and I totally worked. Awesome! I've been struggling for months manually turning my screen on and off (first world problem), but all fixed now. :)
[Galaxy Note II Q&A, Help & Troubleshooting] CoolRanchLuke:
On my jfltexx (CM 11 M3) this just gives me "Connection problem or invalid MMI code." :(
[Galaxy Note II Q&A, Help & Troubleshooting] Formhault:
Yeah... that only works on Samsung ROMS. No such debug / test stuff in CM or other custom ROMs based on AOSP / Google Edition.
[Galaxy Note II Q&A, Help & Troubleshooting] nethyr:
Canned air and quick recalibration failed for me, Greaty's manual recalibration worked perfectly. Thanks!

Link to method - http://xdaforums.com/showthread.php?p=43806906

Galaxy S4 (jfltevzw) running Cyanogenmod 11m3
[Galaxy Note II Q&A, Help & Troubleshooting] fusionite96:
How do i reset the calibration or delete the calibration file. I tried all the above steps but still didnt find a fix. Please help me
[Galaxy Note II Q&A, Help & Troubleshooting] Vaporsilver:
I cannot, for the life of me, figure out how to make the EFS file writable so I can input the new variables
[Galaxy Note II Q&A, Help & Troubleshooting] 0xnth:
What rom you are using?:rolleyes:
[Galaxy Note II Q&A, Help & Troubleshooting] Ali_Shaikh:
This worked for me! It actually fixed it. Thank you so much! This was troubling me for months!
[Galaxy Note II Q&A, Help & Troubleshooting] eheinzeiii:
Worked for me on the s4 Verizon edition. Thanks a ton.
[Galaxy Note II Q&A, Help & Troubleshooting] Formhault:
How did you mount the /efs partition read-write, guys?!

I did this trick a long time ago but don't remember how. And I figure the newbies could use the help :good:
[Galaxy Note II Q&A, Help & Troubleshooting] eheinzeiii:
I just used root explore or ES file Explorer to make everything read/write. Requires ROOT.

If you read every post and follow every direction. It works.

I noticed my problem when my screen would not turn on when I pulled it away from my face during calls.
[Galaxy Note II Q&A, Help & Troubleshooting] Formhault:
Oh, right. I thought you have to mount /efs as rw via Terminal only.

Don't you think I already know that? As I said, I already did this trick a while ago :)

At the time I did this trick

- about three months ago - there was no indication whasoever as per how to mount EFS as rw. So I googled and googled and found a long command. But forgot. The thought that I can mount it rw with something like a file explorer didn't really cross my mind.

Speaking of which, what specific file explorer did you use to do this?
[Galaxy Note II Q&A, Help & Troubleshooting] zee24:
Hey I don't know how to do any of that and this proximity sensor is pissing me off can you explain it for a noob
[Galaxy Note II Q&A, Help & Troubleshooting] Laurentiu27:
Hello o just wanna write the think that worked for me

Try this

echo 0 > /sys/class/sensors/proximity_sensor/prox_cal

echo 1 > /sys/class/sensors/proximity_sensor/prox_cal
[Galaxy Note II Q&A, Help & Troubleshooting] Formhault:
The problem will return once you reboot. If you follow the entire guide (which may seem intimidating, but it really isn't that hard), the issue will fixed forever :) .
[Galaxy Note II Q&A, Help & Troubleshooting] nisavid:
tl;dr: the /efs/prox_cal method worked for me. i reformulated it below so that the arithmetic and base conversion are done automatically.

like many others with Galaxy S4s, i encountered this issue on a Galaxy S4 Google Play Edition (GT-I9505G). if i remember correctly, the proximity-aware dialer functionality worked fine with stock and with CM 10, but it stopped working with some version of CM 11 and had been broken ever since. the symptoms were the now classic combination: immediately after starting a call, the screen would turn off, and it would refuse to turn on (except for occasional brief moments) or accept any input (besides the power button) until the call was ended.

i was unable to use the Samsung General Test Mode USSD code, *#0*#, to test the proximity sensor. attempting to dial the code resulted in the message, "Connection problem or invalid MMI code." however, an equally acceptable test for me was to dial into my voicemail, checking whether the screen turned on and accepted touch inputs.

the method of writing 0, then 1, to /sys/devices/virtual/sensors/proximity_sensor/prox_cal, did not work for me.

the method of writing the calibration value to /efs/prox_cal fixed it! in summary,

su
cd /sys/devices/virtual/sensors/proximity_sensor
sh -c "echo -en \$'\x$(printf %x $(($(cat prox_cal | cut -d , -f 1) + $(cat state))))'" > /efs/prox_cal
chown system:system /efs/prox_cal
chmod 0644 /efs/prox_cal

you can verify that the correct value was written by checking that both of the following commands output the same value:

echo $(($(cat prox_cal | cut -d , -f 1) + $(cat state)))
hexdump -n1 -e '"%u\n"' /efs/prox_cal

note: verify before rebooting. after rebooting, it is likely that the above values will no longer match up.

many thanks to everyone who has shared their suggestions!
[Galaxy Note II Q&A, Help & Troubleshooting] sZx1:
OmniROM + Sensor fix

check OmniROM thread

or try to flash other ROM

At least that is what i usually do =)

Anyways, good tutorial on calibrating sensors. Bookmarked.
[Galaxy Note II Q&A, Help & Troubleshooting] Skipjacks:
All that is because the sensor is dirty. Reprogramming the values is just a stall until it gets more dirty.

Sent from your phone. You should be more careful where you leave that thing.
[Galaxy Note II Q&A, Help & Troubleshooting] amr.tawalbeh:
working on Galaxy S4 GT-I9500

:good: :good: :good: :good: :good: :good:

thanks a lot my friend it's working perfectly
[Galaxy Note II Q&A, Help & Troubleshooting] omewillem:
ofset = 0

Hi, i'm trying to fix my note 3 and proximity problem.

during test all is green and vibrating constantly.

default nr is approx:120.

it responses to 1000+ when i come near,

i looked up cat /sys/devices/virtual/sensors/proximity_sensor/prox_cal

and my values are

0 / 120 / 80

normal state 129

should i add 0 + 129 = 129 HEX = 81 ass new value

or is there another problem with the 0 as offset nr.?

regards, wilem
[Galaxy Note II Q&A, Help & Troubleshooting] jalusk:
Could also be dust

I just wanted to point out that my phone had identical symptoms, but the solution was to disassemble the phone and clean the large amount of dust which had gotten between the proximity sensor and the front glass (use the ifixit guide for removing the front-facing camera, the proximity sensor is the component right next to it).

Cheers,

Jeremy
[Galaxy Note II Q&A, Help & Troubleshooting] omewillem:
pff.. i just tried method 1. (reboot) 2 times in a row. did not work.

then 2 (reboot) did not work.

then 1 again. (reboot) worked a little bit. not green and vibrate at start of sensortest but when close to sensor, it went green and vibrate. this stayed on. it was stuck.

then method 1 again. reboot command and violla. now the sensor acts normal!

i'm a little affraid to reboot again.......

in pot we trust.

thanxz for all your brainpower and kindness to utilize it for the good.

ome
[Galaxy Note II Q&A, Help & Troubleshooting] eeeric:
The problems of lights sensor and proximity sensor bothered me for a long time. I tried many ways and solutions to my N7100. However, it's not work at all. Then I also flashed other roms( from stock 4.1.1 to 4.4.4), it not work. Finally, I tried to restore the EFS and it was either not work.

I have no way to fix my N7100. Can anyone give me any suggestion? Thank yo very much. (Begging for my poor English :P )
[Galaxy Note II Q&A, Help & Troubleshooting] Skipjacks:
Take it apart and physically clean the sensor. Odds are its got dust built up around it.
[Galaxy Note II Q&A, Help & Troubleshooting] eeeric:
Thanks a lot.

I'd done this. It's still not work... :(

Now, I have no idea to fix these 2 problems (lights sensor and proximity sensor).
[Galaxy Note II Q&A, Help & Troubleshooting] Skipjacks:
Restore the rom to stock using odin? Its worth a shot.
[Galaxy Note II Q&A, Help & Troubleshooting] eeeric:
Thanks, I also flashed other roms( from stock 4.1.1 to 4.4.4), it not work.

You can see what I already done before. http://xdaforums.com/showpost.php?p=58137883&postcount=79
[Galaxy Note II Q&A, Help & Troubleshooting] vvtiett:
Thermohygro sensor in S4 CALIBERATION

Is there any way to restore thermohygro sensor caliberation as I have ported the custom ROM to my S4 GT I 9500

But I lost this thermo hygro sensor.

Can anybody help me to correct that.
[Galaxy Note II Q&A, Help & Troubleshooting] MEAKU15:
I've been having this problem since dont know when. TODAY i got it fixed.... thanks for providing the link.. it worked beautifully .. I am using DITTO ROM at the moment.. going to change to RR though...
[Galaxy Note II Q&A, Help & Troubleshooting] Surik4t4:
Better solution:

"I9505 Proximity Sensor fix" from Google Play
[Galaxy Note II Q&A, Help & Troubleshooting] aleson:
For what it's worth the same procedure fixed the issue on my Galaxy S4 (i9505).

Thanks
[Galaxy Note II Q&A, Help & Troubleshooting] yaro666:
I've just replaced proximity sensor for 6$ and now it works like it should. The old one was stuck in 1 position often, so it turned off lcd, but couldn't wake up for 95% of the calls.

Replacing is easy and took me about 10min with cleaning of the speaker - I work in metal industry and there were a lot of debris on the speaker cloth, now sound is also clear.

Just remove 11 screws, remove middle plastic and 1 more screw that holds proximity sensor.

My device droped a lot during it's life and still everything works again
[Galaxy Note II Q&A, Help & Troubleshooting] valiboy87:
Solution

Hello, the solution it's very easy, just install Proximity sensor reset from App Store, works great after restart ! ;)
[Galaxy Note II Q&A, Help & Troubleshooting] rohitdhavade:
Thats not always the solution, although that is one of the solution that may work.
[Galaxy Note II Q&A, Help & Troubleshooting] flayman:
Fixed proximity sensor problem on Lineage OS hero2lte 14.1

This is an old thread, I know. But it has a few years worth of comments. I had a frustrating time with my Samsung Galaxy S7 Edge (G935F) after flashing the Lineage OS 14.1 rom. The proximity sensor was stuck in the near state. The usual apps to fix the sensor did not seem to work (except once something did, but it reset after reboot). This thread helped me to solve the problem in a terminal emulator. The issue is that the prox_cal file is not in the usual location at /efs/prox_cal. Instead it is at /efs/FactoryApp/prox_cal, but it has been blank. I copied /sys/devices/virtual/sensors/proximity_sensor/prox_cal (same as /sys/class/sensors/proximity_sensor/prox_cal) over the blank /efs/FactoryApp/prox_cal and problem solved! You have to be root. I'm posting this comment hoping that it saves someone else the trouble. Thanks for the help.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ahmedzj:
Hi

I was rooted my stock rom few months back.. it was working until now..

My phone was restarting every now and then so i decided to flash my ROM(Stock ROM 4.04[Rooted] ).. so i downloaded N7000DDLRB_N7000ODDLR4_INU from Dr. Ketans section of ICS Stock ROM and flashed it using odin,, the process was completed and the device showed updating andriod ... optimizing applications ,, then shut down,,, when i rebooted it,, it just goes till before the samsung logo and shuts down,,,i can still go in download and recovery mode.. did i i brick my phone?.. please help....
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] azzledazzle:
sounds like you need a full wipe, Its more than likely old system files causing it to bootloop.

Revert to GB, or quicker, Flash a safe kernel, do the full wipe in recovery and then it should boot normally.

DO NOT wipe with the stock kernel, thats a recipe for disaster
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ahmedzj:
ould you please point to DDLRB safe kernel? dont want to flash the wrong kernel
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] geekynoob:
Use abyss kernel..or any of the latest Speedmod Kernels..!

they are safe and compatible.. :)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ahmedzj:
PhilZ-cwm6-DDLR9-INU-v2.7

http://www.mediafire.com/file/u6vwb3...2.7-signed.zip

http://www.mediafire.com/file/b7yee0...NU-2.7.tar.md5

OR

DDLR9-INU-3.1 (Dr Ketan's Link)

OR

DDLRB-ODD

http://www.mediafire.com/file/qqbct2....71-signed.zip

http://www.mediafire.com/file/i38g65...D-3.71.tar.md5

Which of the singed zip files should i flash ? do i need to download the .tar file in download mode too?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Ksandrius:
Switch the phone GT-N7000. connected to the USB and nothing happens ... Before that sews the firmware and it flew. bootloader spoiled. how to work in servistnom mode via USB. where to start? urgently. thanks
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ahmedzj:
Got it Fixed

Ok sent it to samsung service centre,... the damn battery was the issue,,, got it replaced with a new,,,
[Samsung Galaxy Fit GT 5670] GuestK00420:
http://www.mediafire.com/?wb4xfb6fraw8jtv
[Samsung Galaxy Fit GT 5670] Deleted member 4398224:
This works fine for me. Thanks.

Not need uninstall old version, than just install this version same as every .apk app.
[Samsung Galaxy Fit GT 5670] samo_gf:
Need the moded version :D
[Samsung Galaxy Fit GT 5670] joooba:
Thank you <

Downloading ............. :d
[Samsung Galaxy Fit GT 5670] pavel73:
what is differce ? between official and this?
[Samsung Galaxy Fit GT 5670] Deleted member 4398224:
This is official, but the newest version.
[Samsung Galaxy Fit GT 5670] sandy4u:
No difference :rolleyes:

Cheers :)
[Samsung Galaxy Fit GT 5670] Brady_4love:
Is this JB play store?
[Samsung Galaxy Fit GT 5670] GuestK00420:
For all versions of Android.
[Samsung Galaxy Fit GT 5670] sohana:
my playstore is broken :(

Is this supposed to work on a rooted htc explorer? I still have the stock rom on it. Since i downloaded and installed play store has been force closing every 2 seconds. So i had to uninstall it. Nd now i feel empty without it. :crying: Reinstalling it doesnt work either.

cn anyone giv me advice on wat to do?
[Samsung Galaxy Fit GT 5670] GuestK00420:
Install this as system application then clear cache and data of Google play store. Reboot.

:thumbup:
[Samsung Galaxy Fit GT 5670] navneetkhare:
Thaaaaaaaaaaaaankssssssssssssssssssss :d

HOLY HOLY HOLY S*** !!!! Thanks a million! After installing CM10 on my Sk17i, the Google Play would keep crashing. I tried flashing different gapps but none of them worked. Finally, this one has solved my problem and google play is working fine now! :good: :good: :good: :good: :laugh: :laugh: :victory::D:angel:
[Samsung Galaxy Fit GT 5670] NemesisEnforcer:
I have try this and the google play store closes after a second.Any suggestions.I'm trying this on the Exhibit II.Thanks!
[Samsung Galaxy Fit GT 5670] Deleted member 4398224:
I've just installed this Google Play Store APK v3.10.10 and all works fine. Don't uninstall old version. Just install this version.
[Samsung Galaxy Fit GT 5670] uzairpandith:
Updating And Downloading Not Working

when i try to update or install any app,,,,,its flashes an error...... i am on cm 10 ...
[Samsung Galaxy Fit GT 5670] Deleted member 4398224:
How did you install?
[Samsung Galaxy Fit GT 5670] 1k001:
I have the exact same issue
[Samsung Galaxy Fit GT 5670] skoop99:
Same here on my rooted Kindle Fire HD... :(
[Samsung Galaxy Fit GT 5670] SetJixus:
Ynt: Download Google Play Store APK v3.10

Thank u soo much !!!

Sended by GT-I8150 by Tapatalk 2

www .androidhatti.co m