Google Pixel proximity sensor not working — screen stays on during calls (what to check first)
Steve H.
Reviewed for technical accuracy
Specialities: Google Pixel call screen issues (screen won’t turn off by your ear), proximity sensor checks, accidental cheek taps (mute/speaker/hang up)
Pixel proximity sensor not working? Common reasons + what to check first (case, screen protector, smudges, after update)
Technician
We’ll do this in a calm, low-risk order. I don’t want you to change a bunch of settings at once or do anything that could make calling harder.
Quick questions:
• Which Pixel model (Pixel 6/7/8/8a/9, etc.)?
• What exactly happens on calls — does the screen stay bright the whole time, or only sometimes?
• Did it start after a system update, a new screen protector, or a new case?
Technician
During a call, are you using:
• regular handset to your ear, or speaker?
• Bluetooth earbuds or a car system?
And one more: do you have a screen protector on right now (even a thin one)?
Technician
Trust moment: we’ll start with the least risky check — no resets, no complicated menus.
Safe check to try (just as a test):
• Make one quick call (like voicemail).
• Gently place the phone to your ear and see if the screen goes dark.
• Then, for comparison, do the same call with the case removed (if you use one).
Did you notice any change at all when the case is off?
Technician
Next safest check is cleanliness. A thin layer of skin oil, makeup, sunscreen, or dust near the top edge can confuse the proximity sensor.
Please do this gently (no liquids):
• Wipe the top front of the screen (near the earpiece) with a clean, dry microfiber cloth.
• Make sure there’s no smudge right at the top center area.
Then try one short call again. Any difference?
Technician
Trust moment: I don’t want you to factory reset or remove important things. We can test this safely.
Two quick questions:
• Did you install anything recently that affects calls (call recorder, caller ID/robocall app, accessibility tool)?
• When the screen stays on, do you notice it’s showing the keypad or other buttons as if it’s sensing touches?
Technician
The safest way to check if an app is causing the Pixel proximity sensor issue is a temporary test in Safe Mode. Safe Mode loads only the basic system apps — it doesn’t erase your photos or contacts.
I won’t dump complicated steps here. If you’re willing, we can do a simple “yes/no” test: does the screen turn off during a call in Safe Mode?
If you’re comfortable, try Safe Mode using Google’s official steps (linked in Sources), then place one short call and see if the behavior improves.
Technician
Safe Mode doesn’t delete anything. It’s like a “diagnostic mode” to check whether a downloaded app is involved. You can always exit by restarting normally.
And yes, the screen protector can absolutely be the cause — especially if it covers the top sensor area, has a dark border, or has a slight lift/bubble near the earpiece.
Low-risk choice: before Safe Mode, you can do a quick “protector test” by checking the top edge for bubbles/dust and making sure nothing is overlapping the sensor area. If it looks misaligned, that’s a strong clue.
Technician
A safe, senior-friendly way to narrow this down is to test one thing at a time:
• If the protector is misaligned, that’s the easiest “physical” suspect.
• If it’s update-related, a normal restart and checking for any pending updates can help stabilize things.
I also want to protect you from extra frustration: don’t uninstall a bunch of apps at once. We need clear cause-and-effect.
Technician
It’s more likely settings/app/interference if:
• the issue started after an update, a new screen protector, or a new call-related app
• it works sometimes (then stops) or improves in Safe Mode
Hardware is more likely if:
• it never works, even after removing case/protector and testing in Safe Mode
• the phone had a recent drop, crack near the top, or moisture damage
The goal is to get a clear “signal” from safe tests before deciding on service.
Technician
If those safe checks don’t change anything, then service becomes the sensible next step — not because you “did something wrong,” but because the sensor or top assembly may need inspection.
If you tell me one thing: do you feel comfortable trying Safe Mode just for a single test call? That one test usually gives the clearest answer without risk.
Quick answer: the accepted fix
Accepted first fix for a Google Pixel proximity sensor not working issue: confirm nothing is blocking the sensor and use a simple “one-change-at-a-time” test before assuming hardware failure.
What most often helps:
• Remove the case and check the screen protector alignment near the top edge (borders/bubbles can interfere).
• Gently clean the top front of the screen (near the earpiece) with a dry microfiber cloth.
• Make one test call without Bluetooth or speaker to confirm normal handset behavior.
• If the problem started after an update or a new app, do a brief Safe Mode test call to see if a downloaded app is involved.
• If nothing changes after safe tests, consider hardware inspection (especially after drops or cracks near the top).
Why Pixel proximity sensor problems can start suddenly (even if it worked yesterday)
Many people notice this “out of nowhere” because the issue is often caused by small changes: a new screen protector, a case edge shifting, a smudge near the top speaker area, or a recent Android update that changes call-screen behavior. If the sensor can’t “see” your face properly, the screen may stay on and you may get accidental taps during calls. Some call-blocker or caller-ID apps can also interfere with the Phone app’s call screen. Hardware is possible, but it’s usually the last conclusion — not the first.
What to check first: screen protector, case, Phone app, settings, or hardware?
Start with the easiest comparisons: remove the case, examine the screen protector alignment at the top, and clean the sensor area. Then confirm you’re testing on a normal handset call (not speakerphone and not Bluetooth), because those can keep the screen awake. If the issue began after an update or a new call-related app, a Safe Mode test is a gentle way to see if a downloaded app is involved. Only after these safe checks fail should you suspect a hardware sensor problem.
Google Pixel proximity sensor not working — calm, safe checks for seniors
Most cases are caused by a screen protector, case interference, smudges, or an app/update call-screen change.
Best approach: make one short test call, remove the case, and check the top edge of the screen protector for misalignment or bubbles. Clean the top front of the display with a dry microfiber cloth, then test again. If the issue started after an update or a new call blocker app, Safe Mode can help confirm whether a downloaded app is involved. Avoid changing many settings at once — one safe check at a time makes the cause clearer.
Disclaimer: This information is AI-generated and intended for general guidance only. Avoid making multiple system changes at once. For device-specific steps, consult a verified expert on Whizz-Tech or the manufacturer’s support before making decisions.
Getting Started Is Easy
Ask for help, 24/7
Members enjoy round-the-clock access to 12,000+ verified Experts, including Google Pixel proximity sensor issues, screen staying on during calls, accidental cheek taps (mute/speaker/keypad), Safe Mode testing, and screen protector/case checks.
Expert will respond in minutes
We’ll help you narrow down whether the problem is the screen protector, a case edge, a smudge near the sensor area, a Phone app conflict, or an update-related change — without risky trial-and-error.
Save time & money
Safe diagnostics can prevent unnecessary repairs by confirming whether it’s interference (protector/case), an app issue, or a true hardware sensor fault before you book service.
FAQ
Why did my Google Pixel proximity sensor stop working suddenly?
It often starts after a small change like a new screen protector, case, or a smudge near the top of the screen. An Android update can also change call-screen behavior or trigger a temporary glitch. Some call-blocker or caller-ID apps can interfere with the Phone app during calls. A drop or crack near the top edge makes hardware more likely.
My Pixel screen stays on during calls after an update — is that common?
Yes, it can happen after an update, especially if the Phone app behavior changes. A normal restart and checking that updates are fully installed can help stabilize things. Still, it’s smart to rule out physical interference first (case/protector/smudges). A Safe Mode test call can help confirm whether a downloaded app is involved.
Is this a hardware problem or just settings/app interference?
Most of the time it’s interference from a protector/case or a software/app conflict rather than hardware. If the behavior improves in Safe Mode, that points to a downloaded app issue. If it never improves after removing the protector/case and doing Safe Mode testing, hardware becomes more likely. Recent drops, cracks, or moisture exposure also increase the chance of hardware damage.
Can I fix a Pixel proximity sensor issue without service?
Often, yes, when the cause is a misaligned screen protector, a case edge, or a smudge near the sensor area. Many people also resolve it by confirming no call-related apps are interfering (using a Safe Mode test). If the screen still won’t turn off during calls after those safe checks, service may be needed. The key is testing one change at a time so you don’t lose track of what helped.
Sources
- Google Pixel Help — Find problem apps by rebooting to safe mode
- Google Pixel Help — Fix touch & response issues on your Pixel screen (incl. screen protector mode)
- Google Pixel Community — “My proximity sensor is not working” (common checks)
- Google Pixel Community — Screen doesn’t turn off during calls (what to re-check first)
Filed under: Sensors & Permissions
Related articles
- Google Pixel proximity sensor not working — screen stays on during calls (what to check first)
- Google Pixel proximity sensor not working — screen goes black or won’t turn off during calls (safe checks)
- Google Pixel NFC not working — tap doesn't register payments or cards (what to check first)
- Google Pixel alarm not going off — no sound or vibration in the morning (what to check first)
- Google Pixel GPS not accurate — still not working after restart
- Google Pixel fingerprint not recognizing my finger
- Google Pixel apps can’t access microphone? “Mic blocked” — what to check first
- Google Pixel apps can’t access the camera — safe permission checks (what to do first)
