Skip to content
Smartphone top edge sensors near earpiece during a call

Proximity Sensor on Phone Explained: Screen Off During Calls (2026)

What the phone proximity sensor does, why the screen stays on or off during calls, calibration myths, dirty sensors, and fixes before repair.

10 min readproximity sensor, screen off during call, phone sensors

The proximity sensor sits near the top of most phones and answers a simple question during voice calls: is something close to the earpiece? If yes, the phone turns the display off. If no, the screen can stay interactive so you can hit speaker, mute, or keypad.

When that sensor (or the software reading it) fails, calls become miserable: cheek presses hang up, or the screen never wakes when you pull the phone away.

Where it is and what it is not

  • Location: top bezel / earpiece area — sometimes under the glass beside sensors for ambient light
  • Job: presence near the ear during calls (and some other listening experiences)
  • Not the same as: Face ID / Face Unlock cameras, the earpiece speaker, or the power button

Modern “hole-punch” phones still implement proximity, sometimes via virtual proximity using other sensors. Behavior can differ, but the user-facing goal stays the same: no accidental taps on your face.

Healthy behavior checklist

During a normal call:

  1. Phone to ear → screen goes dark
  2. Pull away → screen wakes to the in-call UI
  3. Palm cover over the top front → screen should darken similarly

If step 1 never happens, proximity is not registering. If step 2 never happens, the sensor may be stuck “near,” or the call UI is crashed/frozen.

Symptom → likely cause

Symptom Likely cause First fix
Screen always on; cheek taps End Dirty/covered sensor; bad protector Clean; remove glass
Screen stays black after call motion Stuck sensor; UI freeze Power wake; reboot
Works without case only Case lip covers sensor Different case
Started after screen replacement Flex seating / calibration Return to shop
White/blank call UI InCallUI software fault See blank-call guide

White incoming-call screens are not classic proximity failures — start with facing blank white screen during receiving call.

Software fixes that are worth your time

Do

  1. Wipe the top glass; remove privacy protectors for a test
  2. Disable Bluetooth headsets so you are truly on earpiece routing
  3. Reboot / force-restart a frozen phone
  4. Update system apps and Phone/Dialer from the official store
  5. Android: test a call in Safe mode (rules out overlay apps)
  6. Check for “pocket mode” / “accidental touch” features fighting the display

Do not

  • Install random “proximity calibrator” APKs from the web
  • Scrape the sensor with metal tools
  • Factory reset as step one for a dirty protector

If call audio is also missing while you chase sensors, split the problem: sensor issues do not mute the earpiece by themselves. Use how to fix iPhone no sound on calls when silence is the main symptom.

Screen protectors and “gaming” glass

Tempered glass that is slightly short, heavily inked at the top, or installed with dust under the earpiece area is a top cause of proximity tickets. Matte privacy filters are frequent offenders.

Test sequence:

  1. Peel protector carefully (or use a spare phone without one)
  2. Place a call
  3. Cover the top area with your palm
  4. Only reinstall a protector that leaves the OEM cutouts clear

After drops and third-party screens

Impact can misalign the sensor flex. Cheap screen jobs may omit or reseat the proximity component poorly. If problems began the day of a repair, go back to the repairer with a demo: palm cover should shut the screen off on a dialer call.

Bring notes using before sending a phone for repair so you do not lose apps/accounts while they open the device again.

OEM test menus

Some Androids expose sensor tests via service codes or #0# style menus (device-dependent). If a hardware test shows proximity never toggling while you cover the sensor, that is strong evidence for hardware — stronger than a third-party app claiming “0% calibration.”

iPhones do not give consumers a friendly calibration slider; diagnostics are mostly Apple Store / Apple Diagnostics territory.

Accessibility and dark screen confusion

Occasionally people mistake Auto-Lock, Attention Aware features, or Always On Display quirks for proximity faults. Compare:

  • Proximity: happens tied to active calls (or specific listening modes)
  • Auto-Lock: happens after idle timeout outside calls
  • Burn-in / dark AMOLED themes: UI still touchable

Wake the screen with the side button during a call. If the in-call UI is fine after wake, proximity was simply holding it off — expected near your face, buggy when in open air.

VoIP apps vs the Phone app

WhatsApp, Telegram, Zoom, and FaceTime do not always use the proximity sensor the same way the carrier Phone app does. Test with a normal cellular call first. If only one VoIP app keeps the screen on, clear that app’s cache/data or reinstall it before you condemn the hardware sensor.

Conversely, if every calling app fails the palm-cover test, the shared sensor path is the suspect.

Pocket dialing and reverse symptoms

When proximity fails “always far,” you get pocket dials and cheek mutes. When it fails “always near,” you get a black screen you must wake with the side button after every call adjustment. Both are proximity-class issues; only the stuck direction differs. Describe which direction fails when you talk to a technician — it changes their parts guess.

Soft proof you can perform in sixty seconds

  1. Open the stock Phone dialer and call a voicemail number
  2. Cover the top front glass with your palm
  3. Watch for the display to sleep
  4. Uncover and watch it wake
  5. Repeat after removing the case and protector

Film that test. It is more persuasive than “sensor feels weird.”

Developer options myths

Android Developer Options sometimes expose sensor graphs, but enabling random sensor logging will not repair a dead flex. Use visualization only to confirm whether the value toggles when covered. Turn developer options back off afterward so you do not leave stay-awake flags on overnight charging.

Bottom line

The proximity sensor turns the screen off when the phone is at your ear so you do not end calls with your cheek. If the screen stays on or stuck off, clean and uncover the top sensor area, remove bad protectors, force restart, and separate true sensor failure from in-call UI crashes. Skip shady calibrator apps; document hardware symptoms before another screen repair.

Frequently Asked Questions

What does the proximity sensor on a phone do?

It detects when your face or ear is near the top of the phone during a call so the screen can turn off. That prevents cheek taps on Mute, End, or Dialpad.

Why does my screen stay on during calls?

Dirty or covered sensor area, misaligned screen protector/case, software glitches after an update, or a failed proximity sensor/flex after a drop or screen replacement.

Why does the screen stay black after I move the phone away?

The sensor still thinks something is near — or the in-call UI crashed. Wake with power button, clean the sensor zone, and reboot. Persistent blackouts after calls suggest hardware or InCallUI bugs.

Can I calibrate the proximity sensor?

Some OEMs expose dialer tests or hidden menus; many modern phones do not offer user calibration. Cleaning and protector removal help more than random ‘calibrator’ APKs.