Google Pixel proximity sensor not working — screen goes black or won’t turn off during calls (safe checks)
Steve H.
Reviewed for technical accuracy
Specialities: Google Pixel call-screen issues (screen stays black / won’t wake, or screen won’t turn off), proximity sensor checks, Phone by Google app troubleshooting.
Pixel proximity sensor acting up? Common reasons + what to check first (screen protector, case, smudges, Phone app, after update)
Technician
• The screen turns black during a call and won’t wake up (hard to end the call).
• Or the screen doesn’t turn off near your ear, so you get accidental taps, muting, or speaker turning on.
We’ll do calm, low-risk checks first. I don’t want you changing lots of settings at once or doing anything that could make calls harder.
Quick questions (simple):
• Which Pixel model (Pixel 6/7/8/9, etc.)?
• During calls, is your problem “screen stays black” or “screen stays on”?
• Did this start after an update, a new case, or a new screen protector?
Technician
First “safe” thing: the Pixel’s proximity sensor sits near the top of the screen. If it thinks something is close (ear, case edge, smudge), it will darken the screen to prevent accidental taps.
Two quick checks (no settings changes):
• Do you use a screen protector or a thick case with a raised lip near the top?
• Is the top part of the screen a bit oily/smudged right now?
Technician
Trust moment: we’ll start with the least risky steps first, so we don’t make anything worse.
Safe check #1: gently wipe the top-front of the screen with a soft cloth (no liquids).
Safe check #2 (temporary test): for one call, try removing the case, just to see if the behavior changes.
Technician
Let’s learn from the symptom:
• When the screen goes black, does it stay black even if you pull the phone away from your ear?
• Or does it wake if you press the power button once?
Technician
Safe “one change at a time” checks during your next call (pick just one):
• Try switching to Speaker for a moment — it changes how the call screen behaves and can help us tell if it’s sensor-triggered.
• Or try a call with Bluetooth off, if you normally use it (sometimes it changes the call UI behavior).
No permanent changes — just observing.
Technician
Another calm check: do you notice this more with certain lighting (bright sun), or after the phone has been in a pocket or purse?
Technician
• Pocket/purse lint can add a film near the top of the screen.
• After an update, the Phone by Google call screen can occasionally behave oddly until the phone is restarted.
Trust moment: I’m not going to suggest a factory reset or anything extreme. We’ll keep this senior-friendly.
Have you already done a normal restart since it started?
Technician
If you’re comfortable, do a regular restart when you have a moment — then test one call again. (I’ll include Google’s official Safe Mode guide in Sources too, as a “next check” only if we need it.)
One more question: does the problem happen in all calling apps, or mainly the regular Phone app?
Technician
Safe “what to check first” list (no deep digging):
• Clean the top of the screen and remove the case briefly to compare.
• If you have a screen protector, check the top edge alignment (even a small shift matters).
• Restart once after the update, then test one call.
• Confirm the Phone app isn’t restricted — we can later check permissions in a simple menu (I’ll link Google’s permission manager guide in Sources).
If you tell me which of these changes the behavior even a little, we’ll narrow it down.
Technician
Trust moment: I don’t want you toggling lots of switches. We’ll look for the one place that lists permissions clearly, and we’ll only confirm whether the Phone app has what it needs.
If, after cleaning/removing the case and doing a restart, the screen still stays black (or stays on), then our next “safe” diagnostic is a short test in Safe Mode to see if any third-party app is interfering — no permanent changes, just a test.
Technician
If it’s the same even in Safe Mode, we’d focus back on protector/case alignment, the Phone app itself, and then consider whether hardware service is needed. But we only go there after the safe checks.
Quick answer: the accepted fix
Accepted first fix for a Google Pixel proximity sensor not working: rule out simple interference (smudges, case, screen protector) and confirm the call screen isn’t “stuck” after an update — before assuming hardware.
What usually helps most:
• Clean the top of the screen gently (where the sensor is) and retry one call.
• Temporarily remove the case to see if a raised edge is covering the sensor area.
• If you use a screen protector, check top-edge alignment or test one call without it (if possible).
• Do a normal restart after an Android/Pixel update, then retest the Phone app.
• If nothing changes, try a short Safe Mode test to see if an app is interfering.
Why Pixel call screens act strange suddenly (screen blackouts, accidental mute, can’t end call)
On Google Pixel phones, the proximity sensor helps prevent accidental touches during calls. If it’s blocked by a screen protector edge, a thick case lip, smudges, or pocket lint, the phone may think it’s against your ear and keep the screen dark. The opposite can happen too: if the sensor can’t “see” your face, the screen may stay on and your cheek can press mute, hold, or speaker. After an Android update, some people also notice the Phone app feels “stuck” until a restart. Start with gentle cleaning and simple comparisons before worrying about a repair.
What to check first: case/protector, Phone app, settings, or hardware?
Begin with the easiest, safest checks: wipe the top of the screen, remove the case briefly, and confirm the screen protector isn’t shifted or bubbled near the top. Then restart the phone once (especially if this started after an update). If the problem is mostly in the regular Phone app, we can also verify the app isn’t restricted and has normal permissions. Hardware becomes more likely only when the behavior never changes across safe tests (clean screen, no case, restart, and Safe Mode) and the problem is consistent in every calling app.
Pixel proximity sensor not working — calm, senior-friendly troubleshooting
Most call screen problems come from smudges, screen protectors, case edges, or a small after-update glitch.
Best approach: change one thing at a time. First, clean the top of the screen and test a call. Next, try one call without the case. If you use a screen protector, check that it isn’t covering the top area. A normal restart after an update can also help. If the issue continues, Safe Mode is a safe way to check whether an app is interfering — without deleting anything or making permanent changes.
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, call screen blackouts, accidental muting, screen protector/case checks, and after-update call problems.
Expert will respond in minutes
We’ll help you narrow down whether it’s simple sensor interference (smudges, case lip, screen protector), a Phone app glitch, a permissions restriction, or something that needs repair — without risky trial-and-error.
Save time & money
Safe diagnostics help you confirm the likely cause before replacing accessories or paying for service. Many Pixel proximity sensor problems improve with simple, senior-friendly checks and a careful restart after updates.
FAQ
Why did my Pixel proximity sensor problem start suddenly?
This often starts after a new screen protector, a different case, or a buildup of smudges near the top of the screen. Pocket or purse lint can also cause the phone to think something is close to the sensor. Sometimes the Phone app behaves oddly after an Android update until you restart. Start with gentle cleaning and one simple comparison test.
My Google Pixel proximity sensor stopped working after an update — can that happen?
Yes, it can. After an update, the call screen can occasionally feel “stuck” until the phone is restarted. This doesn’t mean your phone is broken. Try a normal restart and then test one regular call. If the behavior changes even slightly, that’s an important clue.
Is it hardware, or just settings/case/screen protector?
Most of the time it’s interference: case edges, screen protector alignment, or smudges near the sensor area. A simple restart can also clear a software hiccup. Hardware becomes more likely only when there’s no change after safe checks and the issue happens in every calling app. Testing in Safe Mode can help separate app interference from hardware.
Can this be fixed without service?
Often, yes. Many people improve the issue by cleaning the top of the screen, removing the case to test, and restarting after updates. A short Safe Mode test can also show whether a third-party app is interfering. If nothing changes after these safe checks, service may be the next step. Avoid making multiple changes at once so you know what helped.
Sources
- Google Support — Find problem apps by rebooting to safe mode (Pixel)
- Google Support — Change app permissions on your Pixel phone
- Google Pixel Community — My proximity sensor is not working
- Google Pixel Community — Screen turns off during audio calls
Filed under: Sensors & Permissions
Related articles
- Google Pixel proximity sensor not working — screen won’t turn off on calls (what to do next)
- Google Pixel proximity sensor not working — screen stays on during calls (what to check first)
- Google Pixel proximity sensor not working — screen stays on during calls (what to check first)
- 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
