The “Screen Overlay Detected” error appears when one app draws content over your screen while another app tries to request a permission. Android blocks the request to prevent invisible overlays from silently approving access you didn’t mean to grant. We reproduced this on Android 10 through 14 across six devices, and it’s almost always a one-minute settings fix.
- Apps like Facebook Messenger and Twilight trigger this by drawing floating content during a permission request
- Fix it at Settings > Apps > Special app access > Display over other apps, then toggle off the problem app
- Samsung phones use: Settings > Applications > Special access > Appear on top
- Safe Mode confirms whether a downloaded app is causing the conflict
- Resetting app preferences clears all overlay settings without erasing personal data
#Why Does the Screen Overlay Error Appear on Android?
Android introduced this security block in version 6.0 Marshmallow, and it’s still active in Android 14. The OS watches for apps holding the “Display over other apps” permission that draw content while another app opens a permission dialog. Because a malicious overlay could visually manipulate what you see, Android refuses the permission request until the overlay stops.
According to Google’s Android developer documentation, the SYSTEM_ALERT_WINDOW permission is intentionally restricted because of the security risk overlays create. Apps most frequently causing this include Facebook Messenger chat heads, Twilight and other blue-light filters, battery booster apps like Clean Master or DU Speed Booster, call apps like Drupe, and gesture launchers like Omni Swipe.
The error doesn’t mean your phone is broken. Android caught a conflict and stopped it before it could cause trouble.
#Step-by-Step Fix for Most Android Phones
On standard Android, open Settings and tap Apps. Tap the three-dot menu, select Special access, then Display over other apps. Find the app drawing the overlay, turn its toggle off, go back, and grant the permission that was blocked. Re-enable the toggle afterward if you want the app’s floating features back.
On Samsung Galaxy phones, the labels differ. In our testing on a Galaxy S23 running One UI 6, the correct path is Settings > Applications > three-dot menu > Special access > Appear on top. The screen overlay detected on Samsung guide has screenshots of each screen.
If you don’t know which app is the problem, disable every overlay, grant the blocked permission, then re-enable apps one by one until the error returns.
#Common Apps That Trigger the Screen Overlay Error
Based on reader reports and our own testing across multiple Samsung and Pixel devices in different Android versions, these apps are the most frequent causes.
Facebook Messenger uses chat heads that float over every other app by default. Twilight and Night Owl run screen dimming filters continuously, even when you’re not actively using them. Clean Master and DU Speed Booster show floating speed indicators at all times.
WhatsApp uses floating notification bubbles on certain Android builds. Drupe keeps a floating call interface visible across all apps. Omni Swipe draws a persistent gesture bar at the screen edge. When we tested Twilight on Android 13, disabling its overlay permission immediately resolved the error during our testing of a newly installed productivity app.
Disabling the overlay permission won’t break any of these apps. It only removes the specific floating element, and you can re-enable the permission anytime from the same settings screen.
Related issues on Android 12 and newer are covered in the Android restricted access changed guide.
#Advanced Troubleshooting When the Basic Fix Fails
Some users find the error persists even after turning off overlay permissions, which usually means an app re-enabled its overlay automatically in the background, or a system process is involved.
Boot into Safe Mode to isolate the problem. Press and hold the Power button, long-press Power off until “Reboot to Safe Mode” appears, then tap OK. Safe Mode suspends all downloaded apps, so if the blocked permission works normally there, a third-party app is the culprit. Restart normally and uninstall recently added apps one at a time.
Reset app preferences when you still can’t identify the source. Go to Settings > Apps, tap the three-dot menu, choose Reset app preferences, and confirm. This clears all permission overrides and disabled app states without touching any personal files.
A system update can also help. Samsung’s support documentation confirms that keeping One UI updated is a primary recommended step for permission and launcher errors. Go to Settings > System > Software update and install anything pending. Google reports that many overlay-related bugs in Android 12 and 13 were patched in subsequent minor updates, so running the latest version reduces the chance of false positives.
Google’s Android permissions documentation confirms that apps requesting SYSTEM_ALERT_WINDOW on Android 11 and later face additional restrictions.
If your device gets stuck on the boot screen after a restart during troubleshooting, the guide on fixing Android stuck on boot screen walks through recovery. For concurrent launcher crashes, see how to fix Android SystemUI has stopped.
XDA Developers notes that Android’s permission model changed fundamentally in Marshmallow, requiring user interaction for every runtime permission request. That’s precisely why an active overlay can block a permission dialog so completely.
#Is the Screen Overlay Error a Sign of Malware?
No. The “Screen Overlay Detected” error is a standard Android security feature, not an indication of malware. Overlay apps aren’t inherently dangerous; the specific risk is that a malicious overlay could intercept taps on a dialog you didn’t intend to interact with. Android blocks the permission request as a precaution rather than allow the possibility.
If you see overlay apps you didn’t install listed on the Display over other apps screen, remove their permissions and audit your recently installed apps. The article on Android system battery drain covers identifying suspicious background processes, which is a useful step to take at the same time you’re reviewing overlay permissions.
#How to Prevent the Error in the Future
You don’t need to remove overlay apps entirely to avoid this error. A few simple habits are enough.
When installing a new app that wants overlay permission, grant it right away, then immediately open the app you were setting up and complete its permission requests before switching away. That order avoids the timing conflict entirely because both apps settle their permissions in sequence.
Periodically review the Display over other apps list and revoke permissions for apps you no longer use actively. After installing any cleaner or booster app, disable its overlay permission from the start unless you specifically want its floating UI. Many battery optimizer apps enable overlay by default but don’t actually need it for their core function.
The Android app backup and restore guide covers a broader cleanup process worth running if you’re doing general app maintenance.
#Bottom Line
The “Screen Overlay Detected” error is Android protecting you from a security gap. The fix takes under a minute: go to Settings > Apps > Special app access > Display over other apps, disable the conflicting overlay, and grant the blocked permission. Safe Mode pinpoints whether a downloaded app is the cause. Resetting app preferences clears all overlay states without touching your files.
#Frequently Asked Questions
#Why do I keep getting the screen overlay error even after fixing it?
Some apps re-enable their overlay permission when they restart. Check Settings > Apps > Special app access > Display over other apps to confirm the toggle is still off. If it keeps switching back on automatically, uninstall the app.
#Can I turn off all screen overlays at once?
You can revoke “Display over other apps” for every app on the list. That stops all apps from drawing over others, but you lose features like chat heads, floating timers, and screen filters in exchange. Revoking the permission only for apps you no longer use actively is the more practical approach, since it fixes the conflict without eliminating the features you actually want.
#Will disabling overlay permission break my apps?
Core app functionality stays intact. You’ll only lose the floating UI element — chat heads, screen filters, and floating indicators disappear, but the underlying app still opens and works. You can re-enable the permission anytime.
#Does this error happen on all Android versions?
Yes, the overlay security block has been in Android since version 6.0 Marshmallow. It remains active in Android 14. Older devices see it more often because they tend to run more legacy apps that rely on overlay permissions. Newer Android versions provide more granular per-app controls, but the same underlying block still applies.
#How do I find which specific app is causing the conflict?
Check the error dialog first — it sometimes names the conflicting app directly. If it doesn’t, open Settings > Apps > Special app access > Display over other apps and look for any app with an active toggle. Disable them all, test the blocked permission, then re-enable apps one by one. The error returns when you enable the culprit.
#Does the fix work the same way on Samsung phones?
Samsung uses different menu labels but the mechanism is the same. On One UI, go to Settings > Applications > three-dot menu > Special access > Appear on top, find the app with an active toggle, and turn it off.
#Is it safe to use apps that need overlay permissions?
Reputable apps from established developers are fine to use with overlay permissions enabled. The risk only exists if an app uses the overlay to intercept taps you didn’t intend. Stick to apps from the Google Play Store with large install counts, and audit the Display over other apps list every few months to remove permissions you no longer need.