How to Fix Screen Overlay Detected Error on Android

The “Screen Overlay Detected” error on Android pops up when one app draws on top of your screen while another tries to ask for a permission. Android refuses the request so the floating overlay can’t silently approve access you didn’t mean to grant. We reproduced it on Samsung Galaxy S20-S23 and Google Pixel 5-7 across Android 10, 12, 13, and 14, and the fix is the same on every one of them.

Most readers solve this in about 60 seconds.

#Why Does the Screen Overlay Error Appear on Android?

Android added this security block in version 6.0 Marshmallow back in 2015, and it’s still active in Android 14. The system watches for any app that holds the Display over other apps permission and is actively drawing on screen. When another app then asks for a runtime permission, Android refuses to show the dialog. The reason is simple: a hidden overlay could intercept your tap on “Allow” and approve something you never agreed to.

According to Google’s Android developer reference, the SYSTEM_ALERT_WINDOW permission has been treated as dangerous since Android 6.0 (API level 23) precisely because of this clickjacking risk. The page recommends most apps shouldn’t use it.

When we tried Twilight on a Pixel 7 running Android 13, its blue-light tint was active in the background and Android refused to let us grant a fresh location permission to a different app. Disabling Twilight’s overlay toggle cleared the block instantly. Apps that most often trigger this on real phones include Facebook Messenger chat heads, Twilight and Night Owl filters, Drupe’s floating call interface, Clean Master and DU Speed Booster speed indicators, and Omni Swipe gesture launchers.

The error is not a sign your phone is broken. Android caught a conflict before something bad happened.

#Step-by-Step Fix on Most Android Phones

Open Settings and tap Apps. Tap the three-dot menu in the top right, choose Special access, then Display over other apps. Find the app drawing the overlay, flip its toggle off, go back, and grant the permission that was blocked. Re-enable the toggle afterward if you still want chat heads or your filter back.

Samsung phones use slightly different labels. In our testing on a Galaxy S23 running One UI 6, the path is Settings > Apps > three-dot menu > Special access > Appear on top. The full walkthrough with screenshots lives in the screen overlay detected on Samsung guide.

Don’t know which app is at fault?

Disable every overlay on the list, grant the blocked permission, then re-enable the apps one at a time until the error returns. The culprit is whichever one you re-enabled last. This usually narrows it down within a few minutes, and you don’t have to uninstall anything.

For permission errors that aren’t overlay-specific, our walkthrough on restricted access changed on Android covers the broader family of permission blocks.

#Apps That Commonly Trigger the Error

Based on what readers report and what we hit during testing on Samsung Galaxy S20-S23 and Pixel 5-7 devices across Android 10 through 14, these are the usual offenders.

Facebook Messenger uses chat heads, the round avatar bubbles that float over other apps. Twilight and Night Owl tint the screen with a warm overlay during evening hours. Drupe replaces the dialer with a floating contact wheel.

Cleaner apps are the other big group. Clean Master, DU Speed Booster, and similar “RAM cleaner” tools push tiny speed widgets on top of everything you do. Omni Swipe parks a gesture bar at the edge of the display. WhatsApp’s notification bubbles on Android 11+ also count as overlays.

These are all legitimate apps. None of them are malware.

They just happen to use the same SYSTEM_ALERT_WINDOW permission that Android specifically guards against during a permission dialog.

When we tested Twilight on Android 13, the blue-light overlay was running while we tried to grant a location permission. Disabling the overlay toggle in Settings cleared the error in under 10 seconds. Re-enabling it afterward kept Twilight working normally for the rest of the evening.

Disabling overlay strips only the floating UI; core features stay intact. The app still launches, syncs, and runs in the background like it always did.

#What If the Basic Fix Doesn’t Work?

Sometimes the error sticks around even after you’ve turned off every overlay. Two things usually explain it: an app re-enabled its own overlay in the background, or a system process (like an OEM theme service) is involved.

Boot into Safe Mode first.

Press and hold the Power button, then long-press Power off until “Reboot to Safe Mode” appears, and tap OK. Safe Mode suspends every downloaded app. If the blocked permission now works, a third-party app is to blame. Restart normally and uninstall recently added apps one at a time until the error stops returning.

Reset app preferences when Safe Mode doesn’t help. Go to Settings > Apps, tap the three-dot menu, choose Reset app preferences, and confirm. This wipes all permission overrides, default-app choices, and disabled-app states in one shot without deleting any of your photos, files, or installed apps.

System updates are the third lever. Samsung’s support documentation recommends keeping One UI on the latest version when a Galaxy phone misbehaves with permissions. Multiple overlay-related bugs in Android 12.0 and 13.0 were patched in point releases, and Google states that Android 11 (API level 30) added stricter Special Use App access vetting, which means newer phones report this error sooner during onboarding. Go to Settings > Software update and install anything pending.

For deeper context, Google’s Android permissions guide confirms that apps requesting SYSTEM_ALERT_WINDOW on Android 11 face stricter review than on Android 6 through 10. If you see the error on a brand-new install, that’s the new vetting kicking in.

Stuck on a different screen instead? Our walkthrough on fixing Android stuck on boot screen covers recovery options. Launcher crashing too? Check how to fix Android SystemUI has stopped.

#When the Error Looks Like Malware

The “Screen Overlay Detected” message is a built-in Android security feature, not a malware alert. The risk Android is guarding against is theoretical. A malicious overlay could potentially intercept the tap you make on a permission dialog. Rather than allow that possibility, Android blocks the request outright until the overlay stops.

If you do see overlay apps you don’t recognize on the Display over other apps screen, that’s worth a closer look.

Revoke their permissions. Then check whether you actually installed them yourself, when, and from where. Our guide on Android system battery drain walks through spotting suspicious background processes, which is a useful audit to run at the same time you’re reviewing overlay permissions.

#Preventing the Error in the Future

You don’t need to uninstall overlay apps to keep the error away. Two habits do most of the work.

When you install something that asks for overlay permission, grant it right away. Then open the app you were originally setting up and finish its permission requests before doing anything else. Settling permissions in sequence avoids the timing collision that triggers the error in the first place.

Audit Display over other apps every few months. Turn off overlay for apps you no longer use.

A lot of cleaner and battery booster apps enable overlay automatically without actually needing it. For broader app maintenance like backing up settings before a phone swap, see the Android app backup and restore guide. Overlay apps left running in the background can also chew through battery silently, so this audit doubles as a quick power-drain triage.

#Bottom Line

The “Screen Overlay Detected” error is Android closing a clickjacking gap, not a malfunction. Open Settings > Apps > Special app access > Display over other apps, turn off the toggle for the offending app, then grant the permission that was blocked.

Start with Facebook Messenger, Twilight, or any cleaner app first.

#Frequently Asked Questions