A proximity sensor is a small component near the top of your phone that detects when something, like your face, is close to the screen. Its most obvious job is turning off the display when you hold the phone to your ear during a call, preventing your cheek from accidentally tapping buttons, hanging up, or opening apps. It works invisibly, dozens of times a day, and most people never think about it until it stops working.
How the Sensor Actually Works
Most smartphones use an infrared-based proximity sensor. It has two tiny parts: an infrared LED that emits light invisible to your eyes, and a photodiode that receives light. When you bring the phone close to your face, the infrared light bounces off your skin and returns to the photodiode. The sensor registers that reflected light and tells the phone’s software to shut the screen off. Pull the phone away from your ear, the reflected light disappears, and the screen comes back on. The whole cycle takes a fraction of a second.
Some phones use ultrasonic sensors instead. These emit sound waves at around 40 kHz, far above what humans can hear, and measure how long it takes for those waves to bounce back. Ultrasonic sensors handle dusty or foggy conditions better than infrared ones, since sound waves aren’t disrupted by particles in the air the way light can be. In practice, though, infrared remains the dominant choice because it’s cheap, thin, and reliable enough for the short detection distances a phone needs.
Beyond Phone Calls
Turning off the screen during calls is the sensor’s headline feature, but it does more than that. Your phone uses proximity data alongside readings from its accelerometer and ambient light sensor to figure out whether it’s sitting in your pocket or bag. If the light sensor detects darkness and the proximity sensor confirms something is close to the screen, the phone knows it’s pocketed and can suppress notifications, lock the screen, or skip activating the always-on display. This saves battery because the phone avoids lighting up where nobody can see it.
To keep power consumption low, phones don’t run the proximity sensor constantly for pocket detection. Lower-power sensors like the accelerometer and ambient light sensor stay on as sentries. Only when they detect a change, say you suddenly start moving or the light level shifts, does the phone activate the proximity sensor briefly to confirm whether it’s been pocketed or pulled out. Once the check is done, the proximity sensor powers back down.
Where the Sensor Sits on Modern Phones
On older phones with thick bezels, the proximity sensor lived in the visible strip above the screen, usually next to the front camera and earpiece speaker. You could sometimes spot it as a tiny dark dot. As phone designs moved toward edge-to-edge displays, that real estate disappeared, and manufacturers needed a new approach.
Modern phones with OLED screens place the proximity sensor underneath the display itself. Because OLED panels are partially transparent at certain wavelengths, infrared light can pass through the screen, bounce off a nearby object, and return to a sensor sitting behind the display panel. The engineering challenge is that light also reflects internally off the display’s own layers, which can overwhelm the sensor. Manufacturers solve this with small light-blocking elements positioned at precise points inside the sensor assembly to filter out those internal reflections and let only the useful signal through.
Some phone makers are going a step further and removing the hardware sensor entirely. A company called Elliptic Labs has developed an AI-powered “virtual proximity sensor” that ships on recent vivo and iQOO phones. It uses data from other sensors already in the phone, processed by software, to determine proximity without a dedicated infrared or ultrasonic component. This frees up internal space, reduces manufacturing cost, and eliminates one more component that could fail.
Common Problems and Fixes
The most frequent proximity sensor complaint is the screen not turning off during calls, or turning off and refusing to come back on. The usual culprit is something physically blocking the sensor: a screen protector that’s too thick, not properly aligned, or made of a material that absorbs infrared light. Tempered glass protectors with dark coatings over the sensor area are the worst offenders. If your screen started misbehaving right after applying a new protector, that’s almost certainly the cause. Removing it or replacing it with one designed for your specific phone model typically fixes the issue.
Cases that wrap too far around the front edge of the phone can also partially cover the sensor. Even a millimeter of obstruction matters when the sensor sits right at the display’s border.
If there’s no physical obstruction, a software recalibration can help. On many Android phones, you can access a hidden service menu by dialing a specific code (the code varies by manufacturer, so search for your exact phone model). The calibration process is straightforward: the phone asks you to cover the sensor, then uncover it, and it resets its baseline readings. On iPhones, there’s no user-accessible calibration tool, but restarting the phone or updating iOS often resolves sensor glitches caused by software bugs.
Dirt and oil buildup is another simple cause people overlook. A quick wipe of the top portion of your screen with a microfiber cloth can restore normal function if grime has accumulated over the sensor area.
How to Test if Yours Is Working
The easiest test requires no apps. Start a phone call (you can call your voicemail) and slowly move your hand toward the top of the screen. The display should shut off when your hand gets within a centimeter or two, and light back up when you pull away. If nothing happens, the sensor likely needs attention.
On Android, several free apps labeled “proximity sensor test” in the Play Store will show you the sensor’s raw output in real time, reporting “near” or “far” as you cover and uncover it. This helps you pinpoint whether the problem is hardware (the sensor never changes state) or software (the sensor reads correctly but the phone doesn’t respond during calls). If the sensor reads correctly in a test app but fails during calls, a software update or settings reset is the likely fix. If it doesn’t respond at all, you’re looking at a hardware issue that needs professional repair.