Overlay Modules Permission Controller (com.google.android.permissioncontroller): a complete guide

Overlay Modules Permission Controller is an Android system component that often raises questions among users who find it in the list of applications or system logs. Despite its technical name, it plays a key role in managing permissions for overlay modules (overlays) that are used by many applications - from banking clients to game launchers. In this article, we will look in detail at what is hidden behind the package com.google.android.permissioncontroller, how it relates to device security, and why disabling it can lead to unexpected consequences.

If you have ever seen a pop-up window asking for permission to “display on top of other windows” (Display over other apps), then we dealt with this particular component. It controls which apps can create overlays on the screen, from notifications and chat bubbles to system dialogs. But its functions go beyond simple window management: Without Permission Controller working correctly, many applications, including Google Pay and accessibility services, will stop functioning.

In this article, we will not only explain the technical aspects, but also show you how to check the status of a component on your device, what permissions it controls, and what to do if it starts consuming too many resources. We will pay special attention to common myths - for example, that this module supposedly “spys” on users or can be safely removed.

What is Overlay Modules Permission Controller?

Overlay Modules Permission Controller is a system application from Google, included in Android Runtime (ART) and responsible for managing permissions for overlay modules. In simple terms, it controls which applications can display their elements on top of other windows. For example:

• 📱 Chat bubbles in messengers (Facebook Messenger, WhatsApp)
• 💳 Pop-up windows banking applications for confirming payments
• 🎮 Game overlays (for example, in Xbox Game Pass or Steam Link)
• ⚙️ System dialogs (low battery notifications, permission requests)

Technically, this component is part com.google.android.permissioncontroller of a package that is also responsible for processing permission requests in general (for example, access to a camera or geolocation). However, Overlay Modules are separated into a separate subsystem due to their special role in security:

• 🔒 Prevention phishing through fake ones. overlays (for example, fraudulent password entry windows)
• 🛡️ Control of applications that can intercept clicks on top of other windows
• 📊 Limitation performance - too many overlays can slow down the system

On devices with Android 10 and newer, this module is integrated into Android AppRuntime and cannot be removed without root access. On older versions. (for example, Android 8-9) it was sometimes separated into a separate application, which caused confusion among users.

How does the overlay permission mechanism work?

When an application requests permission to display on top of other windows, the following process occurs:

1. Request: Application (for example, Viber) sends a permission request SYSTEM_ALERT_WINDOW.
2. Verification: Overlay Modules Permission Controller analyzes:
   • 📌 Application signature (whether it matches Google certificates)
   • 📌 API level (on new Androids, some overlays are blocked by default)
   • 📌 Device policies (for example, on work phones, overlays may be prohibited)

It is important to understand that not all overlays require explicit permission. For example:

• ✅ System dialogs (notifications, menus) - allowed by default.
• ❌ Third-party applications (messengers, games) - require confirmation.
• ⚠️ Applications with rights Device Admin (for example, Find My Device) can bypass some restrictions.

On devices with Android 12+ Google has tightened the rules: now applications must explain why they need an overlay, otherwise the system can automatically block the request. This was done to combat fraudulent applications that used overlays to steal data.

Where to find Overlay Modules Permission Controller at device?

This component does not have a separate icon in the application menu, but it can be detected in several ways:

1. Through permission settings:
   1. Open Settings → Applications → Special access → Display on top of others windows.
   2. In the list you will see all applications that are allowed to create overlays.
   3. The system controller is not displayed here, but it controls this list.
2. Via ADB (for advanced users):

   adb shell dumpsys package com.google.android.permissioncontroller

   This command will show component status and associated permissions.

3. Through the task manager (if the component consumes resources):
   • Open Settings → Battery → Battery usage.
   • Find process Permission Controller (may be hidden in the "System" section).

On some firmware (for example, MIUI or ColorOS) the path to the overlay settings may be different. If you do not find the "Display on top of other windows" section, try:

• 🔍 Enter a query in the search settings overlay or overlay.
• 🔧 Use applications like App Inspector (requires ADB).

If you suspect that the component is not working correctly (for example, constantly asks for permissions or slows down the system), you can reset its cache:

1. Go to Settings → Applications → Show all applications (⋮) → Show system ones.
2. Find Permission Controller (or com.google.android.permissioncontroller).
3. Click Storage → Clear cache.

⚠️ Attention: Do not clear the data (Clear Data) of this application! This may reset all permissions on the device and cause system errors services.

Is it possible to disable or remove Overlay Modules Permission Controller?

Short answer: no, and here's why:

• 🔐 This system componentis critical for Android security. Disabling it will lead to:
• 🚫 Inability to install or update applications from Google Play.
• 🚫 Errors in the operation of banking applications, instant messengers and services. Google.
• 🚫 Loss of functionality Android Accessibility Suite (for people with disabilities).
• 🛠️ Even with root access removal of this component requires deep modification of the firmware and often leads to bootloop (boot loop).
• 📵 On devices with Android 11+ an attempt to disconnect via ADB blocked by politicians Google Play Protect.

However less, there legitimate ways to limit its influence:

If you still want to experiment, here is the command to disable it via ADB (but remember the risks!):

adb shell pm disable-user --user 0 com.google.android.permissioncontroller

⚠️ Attention: On some devices (for example, Samsung s One UI) this command may reset all application permissions. They can only be restored through a complete reset.

Problems with Overlay Modules Permission Controller and their solutions

Despite its importance, this component sometimes causes failures. Here are the most common problems and ways to fix them:

1. Constant requests for permissions

Symptom: Applications constantly ask for permission to overlay, even if it has already been granted.

Cause: A failure in the permission database or a conflict with another system component (for example, Android System Intelligence).

Solution:

Clear cache Permission Controller|

Restart the device|

Check for system updates|

Disable unnecessary overlays manually-->

If the problem persists, try reset permission settings via ADB:

adb shell pm reset-permissions

2. High battery consumption

Symptom: In battery statistics Permission Controller occupies top positions.

Cause: Most often this is due to a large number of applications actively using overlays (for example, several instant messengers with chat bubbles).

Solution:

• 📉 Disable overlays for unnecessary applications in Settings → Special access.
• 🔋 Enable Adaptive battery in the power settings.
• 🚫 Remove or freeze applications that abuse overlays (for example, some manga readers or streaming services).

3. Error "Permission Controller has stopped"

Symptom: A message appears about the component stopping, applications stop working.

Cause: Damage to system files, conflict after update or unsuccessful firmware modification.

Solution:

1. Restart the device.
2. Clear cache and data Google Play Services.
3. If the error persists, perform a factory reset.

⚠️ Attention: If the error appeared after rooting or installing custom firmware, the only reliable way to fix it is to reflash the device to the official version of Android.

Overlay Modules and security: how do scammers use overlays?

Overlays are not only a convenient tool, but also a potential vulnerability. Fraudsters often exploit permission SYSTEM_ALERT_WINDOW for:

• 🎭 Phishing: Creating fake password entry windows (for example, on top of a real banking application window).
• 👁️ Clickers: Automatically clicking on advertisements or buttons in games.
• 📱 Spying: Intercepting keyboard input through transparent overlays.

Google fights this in several ways:

To protect yourself:

Never give overlay permission to unknown apps|

Check reviews and app reputation before installation|

Use Google Play Protect to scan|

Disable overlays for applications that do not use them (for example, for a flashlight)-->

If you suspect that a fraudulent application is installed on your device overlay:

1. Go to Settings → Applications → Display on top of other windows.
2. Find the suspicious application and disable permission for it.
3. Uninstall the application via Safe Mode (press the power button → Safe Mode).

Overlay Modules Permission Controller on custom firmware

On devices with custom ROM (for example, LineageOS, Pixel Experience) the operation of this component may differ:

• ✅ Pros:
  • 🔧 More control over permissions (you can disable unnecessary overlays globally).
  • 🛠️ Ability to replace the standard Permission Controller with an alternative (for example, XPrivacyLua).
• ❌ Cons:
  • 🚨 Risk of breaking compatibility with Google Mobile Services (GMS).
  • 🔄 Frequent bugs with permission requests after updates.

On firmware without GMS (for example, /e/OS) com.google.android.permissioncontroller replaced with an analogue from the ROM developers. In this case:

• 📌 Overlays are controlled through the firmware settings (usually in the Privacy or App Permissions).
• 📌 Some applications (for example, Google Pay) may not work. due to the lack of an original controller.

If you are using custom firmware and encounter problems:

1. Check whether your firmware supports Signature Spoofing (needed for work microG).
2. Install Magisk module Universal SafetyNet Fixif there are problems with SafetyNet.
3. Use AppOps (hidden Android function) to fine-tune permissions:

   adb shell am start -n com.android.settings/.Settings\$AppOpsSummaryActivity

⚠️ Attention: On some custom firmware, disable Permission Controller may make it impossible to pass SafetyNetwhich will block the operation of banking applications and Google Pay.

FAQ: Frequently asked questions about Overlay Modules Permission Controller

adb shell cmd appops set <package_name> SYSTEM_ALERT_WINDOW deny

adb logcat | grep "SYSTEM_ALERT_WINDOW"