How to Fix the “Someone Has Access to Your Screen” Popup Error on Android

Many Android users encounter a persistent popup that reads "Someone has access to your screen," often accompanied by a reference to a specific app package and instructions to stop sharing if unintended.
This alert appears across various brands, including Google Pixel, Samsung, OnePlus, and others running recent Android versions.
The message serves as a built-in security notification from the Android operating system. It signals that an app or system process has obtained permission to draw over other apps, capture the screen, or project content.
In most cases, the alert stems from legitimate features or temporary software glitches rather than malicious activity.
Android displays this warning to protect user privacy, especially when screen overlays, bubbles, or projection tools are active.
For instance, features like screen recording, casting to a TV, or even certain accessibility options can trigger it.
Common Reasons for the Popup
Several situations lead to this alert:
- Glitches in Google Messages: A frequent cause involves the default messaging app. When opening Google Messages, the popup appears due to a bug in how the app handles screen interactions or permissions on Android 14 and later.
- Screen Overlay Permissions: Apps that draw over other interfaces, such as chat bubbles, screen filters, or floating tools, request "display over other apps" permission. If multiple apps use this, conflicts arise and trigger the warning.
- Active Screen Sharing or Projection: Tools like Smart View (on Samsung), Cast, or Nearby Share can activate screen access. A green indicator dot in the status bar confirms ongoing sharing or recording.
- System UI References: References to "com.android.systemui" point to Android's core interface manager, which handles notifications and overlays. This is normal but can appear in error messages during glitches.
- Recent App Installs or Updates: New or updated apps that use overlays often cause the issue until permissions adjust.
In rare instances, the popup might flag a suspicious app, but most reports trace back to benign causes like the Messages app bug.
How to Verify If Your Screen Is Actually Shared?
Before addressing the alert, confirm whether sharing is active.
- Swipe down from the top of your screen to open the notification panel.
- Look for a green dot or icon in the status bar. This indicates screen capture, recording, or casting.
- If the dot appears, tap it to view which app or feature is using screen access. Disable it if unnecessary.
If no green dot shows, the popup likely results from a software glitch rather than real sharing.
7 Ways to Fix “Someone Has Access to Your Screen” Popup
Here are several reliable methods to eliminate the alert if you can't spot the particular app already from the error message. Try them one by one.
Method 1: Clear Cache and Data for Google Messages
This resolves the issue for many users affected by the Messages app glitch.
- Open Settings on your phone.
- Scroll to Apps and select Google Messages.
- Tap Storage (or Storage & cache).
- Select Clear cache first.
- If the popup persists, tap Clear data (this resets app settings but keeps messages if synced).
- Restart your device and reopen Messages.
Method 2: Force Stop and Uninstall Updates for the App
For glitches tied to recent updates:
- Go to Settings > Apps > Google Messages (or the app mentioned in the popup).
- Tap the three-dot menu and choose Uninstall updates.
- Confirm the action.
- Force stop the app.
- Restart your phone.
- The system may reinstall updates automatically; test if the popup returns.
Method 3: Temporarily Disable Google Play Services
This method resets background processes without permanent changes.
- Navigate to Settings > Apps > Google Play Services.
- Tap Disable and confirm.
- Restart your device.
- After reboot, go back and Enable Google Play Services.
- Test the affected app.
Method 4: Check and Adjust Screen Overlay Permissions
Apps with overlay access can conflict.
- Open Settings > Apps > Special app access (or search for "Display over other apps").
- Select Display over other apps.
- Review the list of apps with permission enabled.
- Disable permission for any unfamiliar or recently installed apps.
- Restart your device.
Method 5: Boot into Safe Mode to Isolate Third-Party Apps
Safe mode disables third-party apps to test if one causes the issue.
- Press and hold the power button until the power menu appears.
- Long-press "Power off" or "Restart" until the Safe mode prompt shows.
- Tap OK to enter Safe mode.
- If the popup disappears, a third-party app is responsible.
- Exit Safe mode by restarting normally.
- Uninstall recent apps one by one until the problem stops.
Method 6: Update Your Phone and Apps
Outdated software can trigger glitches.
- Go to Settings > System > System update.
- Check for Android OS and security updates.
- Install any available updates.
- Open Google Play Store and update all apps.
Method 7: Run a Security Scan (If Suspicious)
If the popup mentions an unknown package name:
- Install a trusted antivirus app from Google Play Store, such as Malwarebytes or Avast.
- Run a full scan.
- Remove any flagged apps.
That's it.
These methods work on every Android-powered device with any third-party UI and other customizations.
Prevention Tips for the Future
To avoid recurring alerts:
- Limit apps with "Display over other apps" permission to only trusted ones.
- Keep your device updated with the latest Android security patches.
- Avoid sideloading APKs from unknown sources.
- Monitor the notification panel for unexpected green dots.
- Regularly clear cache for frequently used apps like Messages.
When the Issue Persists
If none of the methods work, consider a factory reset as a last step (back up data first via Settings > System > Backup).
Persistent alerts with unfamiliar package names warrant caution, though most cases resolve through the steps above.
This alert reflects Android's privacy protections in action, and addressing it restores normal phone use quickly, but it sometimes gets glitchy and that's why I decided to share all the working methods here to remove/fix this error for you.