Want to disable the proximity sensor on Android? This guide tells you the fastest, most reliable way to turn it off—or effectively bypass it—when the screen won’t stay on during calls. You’ll also get the Android-specific options and the limits of what you can and can’t control, so you can choose the right fix in minutes.
As an Amazon Associate I earn from qualifying purchases.
To disable the proximity sensor on Android, start by looking for a built-in “proximity sensor” (or “smart screen”) toggle in Settings; if your phone doesn’t provide one, use accessibility/display options or a careful developer/app workaround to stop the screen from turning off during calls. Because the proximity sensor is designed to prevent accidental touches, the safest approach is to change the behavior that affects call screens (rather than permanently disabling hardware), then test during a real call.
Check for a Built-In Proximity Sensor Toggle
Many Android devices expose a direct switch that effectively disables proximity-triggered behavior—especially during calls or when the phone is brought to your ear. The menu names vary widely by manufacturer, but the key is to search for the right keyword and check the most relevant submenus.
Start with these practical searches:
- Open Settings and use the search bar.
- Type “proximity” first. If that returns nothing, try “smart screen”, “call settings”, or “display while calling.”
- If you find a toggle, look for options like “Proximity sensor”, “Disable proximity sensor”, “Smart screen”, “Accidental touch protection”, or “Prevent screen from turning off.”
Where it commonly appears (names differ):
- Display (especially in “smart” or “gesture” areas)
- Accessibility (in interaction/touch protection categories)
- Call settings (some brands scope the sensor behavior specifically to calls)
If you want a fast method to avoid digging through menus:
- In Settings search, try multiple terms one at a time: proximity → smart screen → pocket mode → accidental touch → screen off during calls.
- Once you find the best match, toggle it and immediately confirm behavior on a call (because some settings apply only to voice calls, not video calls).
Common Ways to Stop Proximity-Triggered Screen-Off (Android)
| # | Method | Where to Look | Steps | Typical Time | Effectiveness |
|---|---|---|---|---|---|
| 1 | Built-in Proximity / Smart Screen Toggle | Settings search: “proximity” / “smart screen” | 2–5 | 1–3 min | ★★★★☆ |
| 2 | Accessibility: Prevent Screen Reacting (If Listed) | Accessibility > touch/interaction options | 3–6 | 2–4 min | ★★★☆☆ |
| 3 | Accessibility: Keep Screen Timeout Friendly | Accessibility > display/timeout-related settings | 2–4 | 1–3 min | ★★★☆☆ |
| 4 | Disable Call-Related “Smart” Display Features | Display > smart stay/glance/pocket modes | 2–6 | 3–7 min | ★★☆☆☆ |
| 5 | Developer Options (Only If Your ROM Exposes Sensor Controls) | Developer options search: “sensor” / “display” | 3–7 | 5–10 min | ★☆☆☆☆ |
| 6 | Automation/App Workaround (Keep Screen On During Calls) | Accessibility permissions & call-state triggers | 4–10 | 10–25 min | ★★☆☆☆ |
| 7 | System Update / Hardware Service (If Behavior Is Stuck) | System update + service diagnostics | 3–8 | Varies (hours) | ★★★☆☆ |
Disable the Sensor via Accessibility or Device Options
If there’s no straightforward “disable proximity sensor” switch, accessibility and display options are usually the next best path—because they let you control screen behavior without needing to tamper with hardware-level sensor functions.
What to do:
- Go to Settings → Accessibility.
- Look for categories related to touch interaction, accidental touches, display behavior, or screen management.
- If your device offers anything explicitly tied to the proximity sensor (some ROMs do), toggle it.
- If not, focus on screen timeout and “keep screen on” behavior so the screen doesn’t go dark unexpectedly when the sensor triggers.
Key ideas to search for:
- “Prevent screen timeout”
- “Keep screen on”
- “Touch & hold delay” / “Auto click” (less directly relevant, but sometimes paired with interaction protections)
- “Smart screen” or “Display while on call” (often sits near accessibility or display)
During a call, verify:
- Whether the screen turns off as soon as your phone nears your face.
- Whether you can still tap controls (keypad, speaker, end call) without the screen immediately going black.
- Whether the behavior differs between voice calls and video calls (many devices apply sensor logic only to voice calls).
Important safety note: the proximity sensor prevents accidental touch while you’re using the phone against your face. Disabling it globally can cause “phantom taps” (e.g., muting/unmuting, ending calls). That’s why accessibility options that soften the screen behavior are often preferable to fully disabling the sensor’s entire function.
Use Developer Options / Sensor Controls (If Available)
Developer Options can be tempting, but it’s only effective if your Android version or manufacturer firmware exposes explicit sensor/display controls.
How to check:
- Enable Developer options (if it isn’t already).
- Open Developer options and use the search bar for terms like:
- sensor
- proximity
- display
- screen
- input
- If you find an actual setting that controls proximity-driven behavior, change it carefully and restart the phone.
When to avoid this method:
- If you only see generic performance toggles (GPU rendering, animations, logging) with no sensor-specific option.
- If the setting is experimental or described vaguely (e.g., “disable hardware features”) without clear documentation.
Best practice:
- Make one change at a time.
- Restart after applying developer-related changes.
- Test immediately on a call so you can revert quickly if it affects call UX or touchscreen reliability.
Test Call Behavior and Screen Settings
Even when you successfully “disable” proximity behavior, the user experience can still be impacted by other screen features. This section is where you confirm the fix is truly what you want.
Adjust these related settings:
- Screen timeout: If the screen times out too quickly, you may mistake timeout issues for proximity issues.
- Smart Stay / Smart Glance (or brand equivalents): these features can keep the screen on/off based on front-camera or gesture logic, sometimes interacting with call UI.
- Pocket mode / motion/gesture controls: some devices use additional sensors or logic that behave similarly to proximity triggering.
Then test systematically:
1. Place a voice call to someone and bring the phone near your face.
2. During the call, see whether the screen turns off or stays on as desired.
3. Try key controls: speaker, mute, keypad, and end call.
4. If your goal is “screen should stay on,” also test with:
- speakerphone enabled
- screen dim/off preferences
- different brightness levels (some “smart” features depend on context)
If the behavior seems inconsistent by app:
- Some dialer or call-screen apps manage UI differently.
- Clear app-specific settings (or reset defaults) for your Phone/Dialer app if you suspect an app-specific issue.
- Check whether the issue happens in safe mode (to rule out accessibility/automation apps you installed).
Use a Trusted App Workaround (When No Toggle Exists)
When your device offers no proximity sensor controls, you can sometimes achieve the desired effect indirectly: keep the screen on (or stabilize call UI) while the phone is near your face—without truly turning off the hardware sensor.
How this workaround usually works:
- An automation or accessibility-enabled app monitors call state.
- When a call starts, it applies rules like keep screen active or prevent screen from dimming/locking.
Guidelines to stay safe:
- Use only well-reviewed apps with clear privacy policies.
- Review permissions carefully—accessibility services can be powerful and should be limited to trusted tools.
- Start in a controlled test scenario (for example, during a non-critical call) so you can confirm nothing else breaks.
A common best-effort outcome:
- You may not fully disable the proximity sensor, but you can prevent the screen from going dark or becoming unresponsive during calls, which is often the real goal.
If you notice side effects (random taps, call UI freezing, or battery drain), roll back the automation and revert settings. Proximity behavior changes can have subtle UX consequences.
Troubleshoot if the Sensor Won’t Disable
If the screen still turns off (or you get erratic behavior) after trying the steps above, you may be dealing with either a missing software control or a sensor-related fault.
Try this sequence:
- Restart the phone and re-check the Settings search results for proximity-related toggles.
- Update Android and manufacturer system apps (Dialer/Phone services, System UI, and any vendor hardware-management components). Hardware-related behavior sometimes gets fixed in software updates.
- If the proximity behavior looks “stuck” (e.g., screen always thinks it’s near your face even on a table), consider:
- removing the phone case (some thick cases can affect sensor readings)
- cleaning the area around the sensor lens/window (use a dry microfiber cloth)
- testing with another call scenario (voice vs. video, speaker vs. earpiece)
If it still won’t disable and the issue persists:
- It may be time for hardware diagnostics or service, especially if the sensor output appears incorrect.
- In business environments, it’s particularly important to verify call reliability—call-screen malfunctions can disrupt workflows.
When you want to disable the proximity sensor on Android, start with any built-in toggle in Settings, then try accessibility or display-related options that control screen behavior during calls. If your device lacks a direct switch, use developer options (only when supported) or a cautious app workaround, and then test with real call behavior. Try the methods in order, and if it still won’t work, update your system or check for hardware-related issues—so your screen behaves exactly how you need.
Frequently Asked Questions
How can I disable the proximity sensor on my Android phone?
Most Android phones don’t offer a single built-in “proximity sensor off” toggle, but you can disable proximity-based screen behavior. Try turning off features like “prevent accidental touches,” “pocket mode,” or “call screen off” in your Dialer/Call settings and Accessibility options. If you need a full disable, you may require a developer/ADB approach or an app that can block sensor behavior, but results vary by brand and Android version.
What’s the quickest way to stop the screen from turning off during calls due to the proximity sensor?
If the screen is darkening incorrectly, clean the top area of the phone and check for a case or screen protector covering the proximity sensor. Then, open your Phone app settings (or Call settings) and look for options related to proximity sensor, “Pocket mode,” or “Prevent accidental touches.” In some devices, toggling Accessibility → “Prevent accidental touches” can also reduce unwanted proximity sensor behavior.
Why does my proximity sensor seem stuck on or not work correctly on Android?
A proximity sensor can appear faulty due to blocked sensor hardware, moisture, dust, or a misaligned or thick screen protector/case. Software can also cause issues when a misconfigured app or accessibility feature is interfering with sensor readings. Restarting the phone, booting into Safe Mode to test for app conflicts, and updating your system/Phone app can help identify whether the problem is hardware or software.
Which Android apps or tools can help disable proximity sensor behavior without root?
Some third-party apps are designed to “control proximity sensor” or disable “pocket mode,” but their effectiveness depends on how your device handles sensor input. Look for apps that specifically mention proximity sensor blocking and confirm compatibility with your Android version and device model. For safety, prefer apps with strong reviews, clear privacy policies, and avoid granting unnecessary permissions.
What’s the best method to disable the proximity sensor for troubleshooting when the screen won’t stay on?
For troubleshooting, start with non-invasive steps: remove the case, remove/replace the screen protector, and ensure nothing covers the top speaker/sensor area. Next, test with Safe Mode and temporarily disable recently installed apps that might affect sensors or display behavior. If you still need to stop proximity sensor actions, consider using ADB commands (advanced) or a supported developer option approach, but be aware that forcing sensor changes can impact call performance and accessibility features.