Needless to say, I was unhappy.
I figured out what happens using xda-developers. Apparently, the phones have so-called "proximity sensor", which they use to determine if you are holding the phone next to your ear. When you cook it during lens swap, or when the screen is generally dirty, you get it to misfire.
Proximity Sensor |
You can test what proximity sensor thinks about the distance by enabling hidden menu (enter number *#22745927 in dialer), then *#0*#, then click on "Sensors". Look the number in "Proximity Sensor" section, and see how it changes when you bring your hand close to the sensor. When ADC is less than 14, proximity is zero, after that it is one.
My sensor was always showing ADC of 16 or more. That is the problem, which I could not fix even by replacing sensor. I was able to get ADC down to 12, but this barely worked, because a hand even near a phone, while in the call caused screen to turn off, which is annoying to say least. I compared it with my wife's SIII, and it was 1 to 2, depending on lighting, so the problem was clearly in the sensor. But I had a new one!!!
After several days of looking for solution, I got an idea. There are two openings. It is probably because light is emitted from one opening, and (when your ear is close to the phone) gets reflected into a second one. What could go wrong? Screen could be slightly dislocated, and then the light will hit the dark spot between openings and get reflected into receiver, even when no ear is close to the sensor. How could this be resolved? Apparently very easily: put some black rubber paste or dough in between emitter and receiver, and the light will be blocked.
This solution worked for me so amazingly well, that I decided to publish some pictures, demonstrating the process.
Unscrew the last one and carefully pry out the sensor |
Put some BLACK paste or dough. NOT TOO MUCH!!! Make sure you don't smear any on the windows |
Your mileage may vary, but after I reassembled the phone, ADC stays around 2 at all times. It is amazing. I was expecting a small effect, but the problem was gone completely.
PS: Oh, and for what it's worth, here's the compound I used to separate light from receiver. As I said, you can be good with probably just about anything, this just happened to lay around.
Thanks :) This did the job for me. I started having the problem after replacing the glass on the phone. I think the replacement glass might not be translucent enough for the LED to shine "out" of the sensor holes in the glass. I bridged the gap between the light and sensor with a piece of sticky backed foam and the proximity sensor is working again.
ReplyDeleteThis makes sense. Most optical sensors need a barrier between emitter and receiver, and the s3 proximity sensor doesn't have it. Luckily, the sensor is accessible from behind, no need to mess with the glass.
ReplyDeleteThis definitely helped me trouble shoot an S3 with a replaced glass. I had to go so far as scraping the black coating from the two lenses for the proximity sensor on the glass. It finally brought the ADC down to a working level.
ReplyDeleteWow! sososososo Thanks :)
ReplyDeleteI dont own the S3 though, i wanted to thank you for making people life easy. May god bless you with good health.
ReplyDeletethanks a lot it is unbleiveable solution its realy amazing working nice
ReplyDeletethanks a lot! this actually works!!!
ReplyDeleteThanks for taking this opportunity to discuss this; I appreciate with this and if you have some more information please share it with me.click here
ReplyDeleteThanks a lot, it worked for me. I used blue tac. For me problem started after changing the screen of my samsung s4.
ReplyDeleteI really impressed after read this because of some quality work and informative thoughts . I just wanna say thanks for the writer and wish you all the best for coming!. galaxy tab s3 release date
ReplyDelete