What does a phone proximity sensor do (and how to fix it)

Hold a phone to your ear during a call and the display should go dark almost right away. If it doesn't, a cheek pressed against the glass can mute the microphone, hang up the call, or open a menu without anyone meaning to touch anything. That small failure is usually the first time most people stop to wonder what a phone proximity sensor does: it's a tiny component near the earpiece that tells the phone something, usually a face, has gotten close to the screen, so the system can shut the display off mid-call.

That single job explains most of what follows here. A smartphone proximity sensor's core task is detecting an object near the top of the display and switching the screen off to prevent an accidental mute, hang-up, or hold during a call (AndroidAyuda, 8 months ago). When it fails, the symptoms show up fast: a screen that stays lit against the ear, a display that won't wake once the call ends, or random shutoffs, problems reported on both Android and iPhone handsets after repairs (Owl Repair, about a year ago).

Everything in the next two sections applies to most smartphones, regardless of brand. The hands-on troubleshooting later in this article leans Android, with a separate note for iPhone owners and a case study on Xiaomi phones, which use a different detection method covered below.

What does a phone's proximity sensor actually do?

A phone's proximity sensor is a small transducer sitting at the top front of the device, right next to the earpiece, built to detect whether something is touching or hovering near the screen (AndroidAyuda, 8 months ago). When it senses an object close by, it blanks the screen so a cheek can't accidentally mute the mic or launch an app, then reactivates the display the moment the phone moves away from the ear (Owl Repair, about a year ago).

On some devices, the same sensor also helps route audio between the earpiece and the speaker during a call, and that overlap explains a common mix-up: when a phone displays a "do not cover the earpiece area" warning, it's actually referring to the speaker grille, not the proximity sensor, even though the two parts sit close together (AndroidAyuda, 8 months ago).

Knowing what the sensor is supposed to do matters before diagnosing why it isn't, since most "proximity problems" turn out to be something blocking its line of sight rather than failed hardware.

How do these sensors detect "near" vs. "far"?

That's the basic mechanics behind how phone proximity sensors work on most Android devices: an infrared emitter sends out a beam, a photodiode or phototransistor measures how much light bounces back, and a circuit interprets the result as "near" or "far" (AndroidAyuda, 8 months ago). It's the most common design in Android phones, built for a tight space near the earpiece rather than precision measurement.

It's not a precision instrument, either way. The W3C's technical draft on proximity sensors warns against treating them as exact distance tools, since surface material can interfere with detection and some sensors only report a simple near-or-far result rather than a measured distance (W3C Working Draft, about 20 months ago). In practice, the sensor isn't measuring centimeters so much as guessing presence, which leaves room for error when a case, screen protector, or stray material sits in the way.

Not every phone uses this hardware at all. Certain Xiaomi models skip the dedicated infrared sensor entirely and rely on what's called a virtual proximity sensor instead: an ultrasonic system that emits sound pulses, listens for the echo through a secondary microphone, and combines that with motion-sensor data to guess when the phone is at an ear (AndroidAyuda, 8 months ago). That's worth flagging as a single-source claim rather than settled fact. Because virtual sensors lean more heavily on software and environmental conditions, the same report notes they're more prone to failure than dedicated optical sensors, a Xiaomi-specific observation rather than a general rule for every phone.

This difference in hardware explains why two phones can handle the exact same feature in different ways, and why a fix buried in one brand's hidden test menu simply won't exist on another model.

Why might your screen stay on during a call?

A phone screen that stays on during calls tends to come with a familiar list of symptoms: a display that stays lit against the ear, menus triggering from cheek contact, audio cutting in and out, or a screen that won't wake once the call ends (AndroidAyuda, 8 months ago; Owl Repair, about a year ago). Before assuming the hardware itself is broken, it's worth ruling out the obvious: dust, adhesive residue, a thick tempered-glass screen protector, or a dark, opaque case can all block the sensor's line of sight (Owl Repair, about a year ago).

Repairs introduce their own set of culprits. After a screen replacement, battery swap, or motherboard service, a misaligned sensor gasket, a loose flex-cable connector, or a lower-quality third-party screen with a tinted sensor window can all block or distort readings, on Android and iPhone alike (Owl Repair, about a year ago). If the screen started misbehaving right after a repair, that timing points toward reassembly rather than a random failure.

Ultrasonic systems add one more failure mode that doesn't apply to a basic IR sensor: calibration drift, a system update, or even a new case can throw off detection in ways that have nothing to do with physical damage (AndroidAyuda, 8 months ago). Obstruction and post-repair misalignment are common, checkable causes, but that conclusion comes from a repair business's own case experience rather than independently measured data across the whole phone market. Treat the list above as a starting checklist, not a confirmed explanation for every malfunctioning sensor.

How to troubleshoot it, step by step

Work through these steps in order if a phone screen stays on during calls, since each one rules out a cheaper, faster fix before moving to anything more involved.

Step 1: remove obstructions and clean the sensor area. Wipe the top of the display near the earpiece with a microfiber cloth, and temporarily pull off any recently added screen protector or case to see if the problem disappears (Owl Repair, about a year ago).

Step 2: restart and check for updates. A reboot, or a pending OS or firmware update, can refresh sensor drivers and clear up software-level glitches before anything more invasive is necessary (Owl Repair, about a year ago).

Step 3: test it in a diagnostic tool. Many Android phones include a built-in sensor test, reached through a manufacturer app, a settings menu, or a hidden dialer code, that shows live proximity values changing as you cover and uncover the sensor (AndroidAyuda, 8 months ago). What those numbers actually mean is covered in detail below. The sources reviewed for this piece don't document an equivalent diagnostic code for iPhone. If cleaning, removing accessories, restarting, and updating haven't fixed the problem, the next move is contacting Apple Support or whoever handled a recent repair, rather than hunting for a workaround that may not exist.

Step 4: isolate app interference with Safe Mode. Safe Mode starts the phone with only system apps running and temporarily disables everything downloaded. If the sensor behaves normally for calls in Safe Mode, a third-party app is the likely culprit, not the hardware (AndroidAyuda, 8 months ago).

If you have a Xiaomi or HyperOS phone: confirm the proximity toggle is switched on under Settings > Apps > System app settings > Call settings > Incoming call settings, then dial *#*#6484#*#* to open the hidden test menu, check live sensor values, and run the built-in calibration option if one appears (AndroidAyuda, 8 months ago). Menu wording shifts between MIUI and HyperOS versions, so look for the closest equivalent labels rather than an exact match. Owners of other Android brands, Samsung, Pixel, OnePlus, and the rest, should look for their own manufacturer's diagnostic or support app instead of assuming this code applies to their phone.

What a proximity test result tells you

A sensor test only means something once it's read correctly. Most Android diagnostic menus report a simple value, often 5 when nothing is covering the sensor and 0 when something is (AndroidAyuda, 8 months ago). What that number does and doesn't prove depends on what happens when the surroundings change.

• Reading changes normally once a case or protector is removed: the hardware is working fine, and the obstruction was the whole problem.
• Reading only behaves correctly in Safe Mode: a downloaded app is interfering with the sensor, not the sensor itself (AndroidAyuda, 8 months ago).
• Reading never changes, even with cases and protectors removed: that outcome, especially if it persists after a factory reset reloads the device's default sensor settings, suggests a hardware problem rather than something a software fix can solve (AndroidAyuda, 8 months ago; Owl Repair, about a year ago).
• Problem started right after a screen, battery, or motherboard repair: a static reading in that situation suggests a hardware or reassembly issue, and it's worth raising with whoever did the repair before trying anything else (Owl Repair, about a year ago).

A factory reset is worth trying before writing the sensor off as dead, but only after backing up data, since it wipes the device back to its out-of-box state and reloads the default sensor parameters (AndroidAyuda, 8 months ago). If the sensor still won't register a change afterward, that's about as close to a confirmed hardware diagnosis as a reading at home gets.

Conclusion

The fixes above move from cleaning to software to app interference in that order, because each one is cheaper and faster to rule out than the one before it. A sensor that still won't register a change after all four steps, especially on a phone serviced recently, is the signal to stop guessing and contact the repairer or manufacturer directly rather than cycling through more resets (Owl Repair, about a year ago; AndroidAyuda, 8 months ago).

Everything else on this list, the obstruction check, the Safe Mode test, the Xiaomi calibration menu, is worth trying first precisely because it's quick, reversible, and won't risk making a working phone worse.