Proximity sensor - T-Mobile Samsung Galaxy S 4

Is there a way to calibrate the proximity sensor
Sent from my SGH-M919 using XDA Premium 4 mobile app

mrgwap said:
Is there a way to calibrate the proximity sensor
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't believe there is a "Calibration" for it, however you can test it's operation as far as sensitivity, etc by using the *#0*# and select the sensor test. move your hand near and close to the sensor and you will see the change. the screen turns green when it's very close.

Same Issue, would love some tips.
bobolinko said:
I don't believe there is a "Calibration" for it, however you can test it's operation as far as sensitivity, etc by using the *#0*# and select the sensor test. move your hand near and close to the sensor and you will see the change. the screen turns green when it's very close.
Click to expand...
Click to collapse
I also have this problem I flashed Cyanogen Mod 11 and everything is working great (much prefer Cyanogenmod to the stock Rom), but I still get that issue with the proximity sensor. Phones screen goes black from the moment a call connects to its target, and doesn't come back on until the person im calling hangs up.
Also when I tried to run the code *#0*# i get 2 error messages , which are the following 1: USSD Code running then 2: Connection Problem or MMI code.
I am running the latest nightly build of CM11 (I updated to this from latest stable CM11 to see if this would fix the issue, it didn't)
My device is the T mobile SGH M919 version of the Galaxy S4 16GB.
Any advice at all would be much appreciated thanks guys /gals!
Martin

Martsmac said:
I also have this problem I flashed Cyanogen Mod 11 and everything is working great (much prefer Cyanogenmod to the stock Rom), but I still get that issue with the proximity sensor. Phones screen goes black from the moment a call connects to its target, and doesn't come back on until the person im calling hangs up.
Also when I tried to run the code *#0*# i get 2 error messages , which are the following 1: USSD Code running then 2: Connection Problem or MMI code.
I am running the latest nightly build of CM11 (I updated to this from latest stable CM11 to see if this would fix the issue, it didn't)
My device is the T mobile SGH M919 version of the Galaxy S4 16GB.
Any advice at all would be much appreciated thanks guys /gals!
Martin
Click to expand...
Click to collapse
There is a 99% chance that your proximity sensor is dirty, from the inside. It's a known flaw with the S4 design. Dust gets in through the speaker grill and piles up in the proximity sensor housing.
The good news is that it's an easy fix. You just have to take the phone apart and clean that housing. It takes like 15 minutes and is REALLY simple, with minimal risk to breaking the phone. Here's a guide on how to do it...
http://forum.xda-developers.com/showthread.php?t=2683582
Alternatively there are ways to calibrate it to compensate for the dirt, but they are much more temporary fixes and in my opinion (which is expenstive since I've tried both methods on multiple devices) not as good.

thanks
I appreciate the response , however I'm sure its not dirt on the sensor and that its actually an issue with the software (in this case Cyanogenmod 11 nightly build) not detecting it/initializing it correctly. My reasoning for this is that as soon as I revert back to the stock ROM my issue is gone.
Really hope someone figures this out but for the time being I'm going to have to use a different ROM/stock. Love CyanogenMod though so hopefully it can be resolved soon.
Skipjacks said:
There is a 99% chance that your proximity sensor is dirty, from the inside. It's a known flaw with the S4 design. Dust gets in through the speaker grill and piles up in the proximity sensor housing.
The good news is that it's an easy fix. You just have to take the phone apart and clean that housing. It takes like 15 minutes and is REALLY simple, with minimal risk to breaking the phone. Here's a guide on how to do it...
http://forum.xda-developers.com/showthread.php?t=2683582
Alternatively there are ways to calibrate it to compensate for the dirt, but they are much more temporary fixes and in my opinion (which is expenstive since I've tried both methods on multiple devices) not as good.
Click to expand...
Click to collapse

Related

[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?

[Q] Samsung Galaxy Note 2 Motion Sensor and Gyroscope not working

hi i just recently bought a galaxy note 2 phablet, im very happy with it every thing works perfectly fine, however i did come across a slight problem which is bugging me alot, as i loaded the phone up it shows you all the tutorials and stuff, for panning and zooming in using motion control.... i did not realise the problem before as i was really happy to just get the phone after so long, My motion sensor and gyroscope functions are not working
i have tried everything from factory reset to restarting , taking the battery out and putting it back in, has anyone stumbled upon this problem, and is there a solution to this problem, whether this is a software glitch/problem or a hardware issue. if anyone can help me please and thanks in advance
*#0*# check there if they are working.
Sent from my GT-N7100 using xda premium
mariosraptor said:
*#0*# check there if they are working.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
hi thank you for the quick reply, i had a look at what you asked me to do and i did manage to find all the settings, however it looks to me everything is working apart from the light sensor one, all the other settings came up as a PASS apart from the light sensor which came as level 0, which i dont know what that means, while i was on the sensor screen i swiped my hand across the sensor and the screen shifted colour from white to yellow, which is a good indication that it is working , however i went back on the operating system and tried the palm swipe and it did not work, niether did the quick glance, and the pan to zoom features are not working either, i did test the gyrocope settings and it came out as a PASS too, could you explain maybe why this may be happening and what does the level 0 on the light sensor option means, please and thank you , i really do appreciate it.
Lavel 0 says to all phones I have tried including mine. As long as the LUX changes it is working.
Now for your primary problem try to recalibrate gyroscope.
Do it by going settings-motion-advanced settings-gyroscope calibration.
If that does not help try clearing cache in recovery.
If that does not help then backup and try reflashing your rom.
Sent from my GT-N7100 using xda premium
darkgallion said:
hi i just recently bought a galaxy note 2 phablet, im very happy with it every thing works perfectly fine, however i did come across a slight problem which is bugging me alot, as i loaded the phone up it shows you all the tutorials and stuff, for panning and zooming in using motion control.... i did not realise the problem before as i was really happy to just get the phone after so long, My motion sensor and gyroscope functions are not working
i have tried everything from factory reset to restarting , taking the battery out and putting it back in, has anyone stumbled upon this problem, and is there a solution to this problem, whether this is a software glitch/problem or a hardware issue. if anyone can help me please and thanks in advance
Click to expand...
Click to collapse
Hello in response to your issues with the motion sensor. Have you installed a screen protector on your note 2? i noticed that after installing the screen protector on my Note 2 some of the motion actions did not work properly. So if you do have one on remove it and see if that corrects the issue. :good:
Useful help.
This was a very Useful thread, thanks. I've done the tests and came up vitha a fail when i tried my motion sensor. Is it likely to be broken? I'm going to reset to factory settings and pull of my screenprotector and se what happens before i do anything else. Is there anyone out there who has replaced the motion sensor? Is it soldered to the main board? Hard to replace?
Thanks beforehand. Tommie.
i thnk my sensor is nt wrkin... when i do the test, d color is alredy green nd isnt changin nd is vibratin continuosly?? is it broken or somthng lyk dat??
note 2 sensor help
mariosraptor said:
*#0*# check there if they are working.
Sent from my GT-N7100 using xda premium
Click to expand...
Click to collapse
can't get quick glance to work
*#06*# does nothing on my note 2 why? Sensor not working was but stopped for some reason?:crying:
Samsung Galaxy Note 2 Motion Sensor and Gyroscope not working
hi my samsung note 2 was working well for last 2 years bur recenrtly its motion sensor has stopped working.
i have checked all settings, it isnt working at all..
gyroscope and motionsensor tests are fail on checking. please help me, what to do?
I have had the exact same issue. The only way to fix it is to get the whole motherboard replaced. I went into Samsung store and they said that. Issue here is that it costs £145 to replace the main board. The sensors are on the main board itself and that is why it costs a lot to fix. I've been using my Note 2 with no gyroscope for a few months now, going to buy a new phone. Rather buy a brand new phone than get it fixed
just loosen the screw nearest to the microsd card. motion sensor is under it. it work on my phone.
gyroscope sensor
Hi,
my gyroscope is burned and i buy it and now i opened my phone and i don't know how to replace it. Any help is welcome...
haakhan said:
just loosen the screw nearest to the microsd card. motion sensor is under it. it work on my phone.
Click to expand...
Click to collapse
Yeahhh!!!
You are a Hero! I tried nearly everythink since January 2016! I took the screw out, shut down my phone, put it into download mode and pull the battery out.
Im not shure if a restart would do it alone, i did all to be shure. And it now works again. My srew was magnetized! Maybe that was the reason or the chip has
a loosen contact.
Up to now it works great! I thought my sensor was dead.

Disable proximity sensor

Is there any way on kitkat 4.4 to disable my proximity sensor, it acts up when I'm in a call. Its only on this certain ROM and its driving me nuts. If I call someone and they don't pick up, I get a voicemail, but I can't hang up because screen won't come back on. Help plz.
Edit: its not dusty
Sent from my SGH-M919 using xda app-developers app
fateownzyou3 said:
Is there any way on kitkat 4.4 to disable my proximity sensor, it acts up when I'm in a call. Its only on this certain ROM and its driving me nuts. If I call someone and they don't pick up, I get a voicemail, but I can't hang up because screen won't come back on. Help plz.
Edit: its not dusty
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
You can disabled it in TouchWiz. I'm not sure you can in an AOSP rom, which your 4.4 rom is.
It could also just be a ROM bug that hasn't been worked out yet. I'd check the development thread for this rom and see if it's a known issue.
If it is, help the developers by posting a logcat of the problem in the develoment threads. (Because odds are no one else has)
Well iv went thru the threads of the development section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent from my SGH-M919 using xda app-developers app
fateownzyou3 said:
Well iv went thru the threads of the development section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
You didn't get a response in a development thread because development threads are not for tech support. They are for discussing development. Tech support questions (which this is) do not belong in development threads.
The rest of XDA isn't even for tech support. We are just happy to try and assist if you get stumped. And don't get me wrong, we are legitimately happy to try and assist you. But complaining that it's "usual that no one responds to you" is pretty rude. No one promised you tech support here. If you get help, it's because someone was trying to be nice, not because you are owed an answer.
If you are using an alpha release ROM it's YOU who should be providing tech support to the developers by giving them logcats of your error so they can review them and find out what is causing the conflict. That's how you can help add to XDA and assist the developers who are building cutting edge software for you and giving it away free as a gift.
If you aren't willing to put up with the proximity sensor errors, or to help the developers fix it by providing them with the logs of the error, then your best bet is to move back to a stable build of a 4.3 or 4.2 ROM for another month or two until the major issues with 4.4 are hammered out.
As for asking for help here, what else have you tried? Have you verified that the bug doesn't exist if you revert to a different ROM?
Have you done a full wipe and clean install of the 4.4 rom and tested for the bug immediately, before installing any other apps or user data? Since you are the only one having the issue this could easily be a conflict with some other app that you have installed. The full wipe and test is the best way to confirm that or rule it out.
fateownzyou3 said:
Well iv went thru the threads of the development section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent from my SGH-M919 using xda app-developers app
Click to expand...
Click to collapse
Same scrap happening with me. The problem is the proximity sensor is always detecting something is in its proximity (most likely dust that got in through the ear piece grill). As a result, the screen turns off immediately when a call is answered, and in Android 4.4 the power or home button can not override this. Interestingly, in 4.3 the power or home button does in fact override the proximity sensor. Why the difference between 4.4 and 4.3 I'm not sure. As Skip Jack alluded to, in Touchwiz roms under settings>my device>call> "turn off screen during calls" can be toggled off to shut down the proximity sensor. If I could find a setting like this in stock 4.4, that would solve this issue.
I need to reflash a 4.4 rom and look for this setting, although I do not think it exists.
I've tried the "pressurized air into the ear piece grill" fix, but it didn't work for me.
Any other suggestions?
https://www.youtube.com/watch?v=zm4f2XjQLAM&feature=youtube_gdata_player
QUOTE=fateownzyou3;47870242]Well iv went thru the threads of the developme, section, and didn't find anyone else having same problems. So I posted there, and nobody responds to me as usual
Sent I rom my SGH-M919 using xda app-developers app[/QUOTE]
Canned air didn't work. So I took my phone apart as demonstrated on YouTube , and when I peeled back the proximity sensor and gesture sensor assembly (they're one piece, attached to the earpiece) i found little bits of sand and dust. A lot. I enjoy the beach in the summer. I cleaned the sensors and the screen area that they are housed in (the part of the screen they "look" out of) with a dry q tip. after putting it all back together its as good as new. *#0*# confirms all sensors now working. The vid above is what I used. You only have to remove sim, sd card, little screws, back speaker, side housing, and a small bracket (in that order) before disconnecting and peeling back the proximity/gesture sensors in order to clean.
You don't have to remove all that other stuff.
I am having the same issue since puttin on CM 11. In 4.1 there was a setting to turn the proximity sensor off but in 4.4 there isn't. I keep looking for an app or something else to trigger it but it is also driving me crazy.
It only happens when my protective case is on my phone, but I am the type of person that NEEDs a case on their phone otherwise itll crack or drown within a couple of days. Any help would be appreciative.
I am having the same issue. Just installed CM 10.2.0-jfltetmo
How do I get a logcat to post? Also, what other information would be helpful for development?
I don't think my issue is sand in the sensor... but I will post back after I open it up and check it out.
If anyone knows of a fix or way to access settings for the proxy sensor, that would be awesome! Also, isn't there a way to use the terminal session to read data from the sensor?
Thanks for any help provided!
Another idea for those who are stuck. I didn't find a way to disable the proximity sensor, but there is another way to hang up a call. If you go into Accessibility options, there is an option to hang up call with Power button. This way you at least have a way to hang up the phone call without having to pull the battery, etc. But it doesn't help if you need to enter additional numbers on the keypad unfortunately. But at least we can hang up now!
I've been having this issue as well which seems to be an aosp bug, but for the mean time, has anyone come up with a solution? Ive tried tasker actions to turn screen on during calls but it seems to be blocked due to the proximity sensor. I know that downgrading to 4.3 is an option but a workaround must be possible. If you find it, Post it.:good:
Edit: Came across this post. Haven't tested yet but it seems promising
Edit2: Wasnt able to get the app to solve the issue as others stated
Hardware fix for proximity sensor
The apps mentioned in this forum and others did not worked for me. My phone is not rooted; perhaps this is required. Apps that I tried are:
Proximity Screen Off Lite
Caffene
I did find the Phone Tester app very useful during the surgery.
I was able to desensitize the proximity sensor as follows. The sensor is made of an IR emitter and an IR detector. It is very sensitive. Small reflections from one side to the other will cause the sensors to show "near" instead of "far."
0. When you look at the Nexus 4 straight on (front camera on top right), of the two elements on the top left, the one more to the right is the IR emitter.
1. Open the phone and gently peel back the proximity sensor/headphone jack (2 + 9 screws; pry plastic and one flex).
2. On the hole corresponding to the IR emitter, apply two small squares of masking tape cut to 1.5 mm x 1.5 mm. Only cover that hole; you do not want to cover the ambient light sensor. The masking tape blocks enough IR to desensitize the system, but won't deactivate it.
3. Gently pry up the digitizer from the phone near the corner when the sensor is. Using a toothpick, apply a drop of superglue just inside the top left corner. Apply pressure and ensure that the digitizer sits firmly on the frame. This is necessary because a slightly separated digitizer will reflect the output of the IR emitter back to the sensor (think about standing behind a window about a foot versus having your nose up to it; you don't see your reflection when you are close).
All this assumes that you know your way around opening the phone and have the correct tools. Sharp objects, execessive force along any step can break your screen or the phone in a split second. If you are not comfortable with it, don't do this.
-PD
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!
You only need to post your question once. You have it in a more appropriate thread already. Please don't dig up 5 month old threads to multi post your questions.

[Q] Proximity sensor problem

Hi there, I think my DHD's proximity sensor is not working, i.e. screen is not turning off during calls resulting in disconnections. I installed Android Sensor Box from play store. Its indicating that proximity sensor is present but always at 9 cm even I covered the top portion of the screen. What do you guys suggest, is it a faulty sensor? I am using latest cm10.1 nightly.
Hey have you tested this proximity sensor app?
http://forum.xda-developers.com/showthread.php?t=951858
Sent It From Outer Space.
Thanks for the suggestion, I'll definitely try it and report back.
Hi,
disassemble the phone and clean up sensor
it work for me
I face the same problem and the app also always shows far
Yeah same problem. Its always showing far except 0,0
Sent from my Desire HD using Tapatalk 2
Easy Way Out!
Possible calibration procedure:
1. Put both values high (will show FAR).
2. Cover sensor with finger.
3. Lower High threshold till it says NEAR.
4. Lower Low threshold by a notch or 2.
5. Test behavior.
Different person will guide you different ways.....that's their way to explain,no offence here.And sometimes different ROM could also requires different calibration,best way to do it is mentioned above.
Example: I'm on AoCP my own custom way made look of 4.2.2 kitkat*
I've OK Google working and Everything as stated in KitKat.But obvious im on 4.2.2 instead of 4.4.2!
In this ROM ive sets Lower @ 13 and Higher @15 but it could be different by user to user.
Thanks.
the other sensor test app shows 9.0 cm always

No notification LED after MM update on ZE551ML?

Maybe it is just me and my device, but since the MM update (the real one, not the beta) my notification LED doesn't work. I have tested it with text messages, emails, missed calls, charger plugged into my computer, charging plugged into a standard charger, and charging plugged into the fast charger... nada on any of them.
Anyone having this issue? If so how have you rectified it? It has been a minute since I first got this thing (got it at launch) and the MM update reset all my settings so maybe there is a setting to turn it back on I am missing?
Help out a brother if you can. Thanks.
OK, so does anyone have any suggestions for an app that might help by letting me manually setup the notification LED?
Is Do not disturb mode on?
Sent from my ASUS_Z00AD using XDA Premium HD app
madman604 said:
Is Do not disturb mode on?
Sent from my ASUS_Z00AD using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the reply. It is not in DND as far as I can tell (not on).
If you haven't already, try a factory reset first
Trotter516 said:
Thanks for the reply. It is not in DND as far as I can tell (not on).
Click to expand...
Click to collapse
Have you found a fix for that? Facing the same issue and so far no luck.
godzin said:
Have you found a fix for that? Facing the same issue and so far no luck.
Click to expand...
Click to collapse
Actually yes. After I wiped my phone for my wife the notification now works.
Another issue that I recently found the solution to... if your ZF2's proximity sensor has gotten crazy sensitive since the update try cleaning it. Seriously. Especially if you have a tempered glass screen protector. I thought the piece of advice was bogus but I cracked out my lens cleaning spray and cloth and BOOM, the proximity sensor works correctly again.
Trotter516 said:
Actually yes. After I wiped my phone for my wife the notification now works.
Another issue that I recently found the solution to... if your ZF2's proximity sensor has gotten crazy sensitive since the update try cleaning it. Seriously. Especially if you have a tempered glass screen protector. I thought the piece of advice was bogus but I cracked out my lens cleaning spray and cloth and BOOM, the proximity sensor works correctly again.
Click to expand...
Click to collapse
Thanks! Got the led working again after a factory reset.
By the proximity sensor do you mean the little one next to the selfie camera or the GPS?
After a lot of fixed I've got the ZF2 working fine, except for the "smartlock - safe places" that thing can never work right.
godzin said:
Thanks! Got the led working again after a factory reset.
By the proximity sensor do you mean the little one next to the selfie camera or the GPS?
After a lot of fixed I've got the ZF2 working fine, except for the "smartlock - safe places" that thing can never work right.
Click to expand...
Click to collapse
Sorry, I just realized that you had replied.
Yes, the one beside the camera. Many have had an issue where the screen goes black after you start or answer a call, especially after the update. It seems the update made the proximity sensor much more sensitive. Since all decent screen protectors have a small cutout for the proximity sensor it will tend to accumulate dirt and oil from your skin. Wiping it down doesn't seem to get it clean enough for the sensor so you have to get a little more aggressive to clear the problem up. I went months enduring the problem and even set my phone so I could disconnect from calls using the power button and then ended up stumbling over the solution when setting up the phone for my wife when I upgraded to my Axon 7.
No led indicator
Hi i've been experiencing the same issue. After I update my zenfone 2 ZE551ML 4gb/64gb version, I have noticed that the led incator is not working and it is not found in the settings. Also, another issue I have encountered is that quick charging feature is not working sometimes but sometimes it works. I don't know how to fix. I'd be glad if someone could help with a step by step process. Thanks in advance!

Categories

Resources