Android Restricted Settings Explained: Why a Sideloaded APK Can't Enable Accessibility
Your APK installs and launches, but the accessibility toggle is greyed out with 'setting not available for security reasons'. That is Android's restricted settings gate, not a corrupt package. Here is how the mechanism works and how to clear it safely.
There is a particular class of Android problem that looks like a broken APK but isn't. The file installs cleanly, the app launches, the account works, and then you go to Settings → Accessibility and find the toggle for your app greyed out, with a line saying the setting isn't available for security reasons.
Reinstalling does nothing. Clearing cache does nothing. A different version of the same app does nothing. That is because the block is applied by the OS based on how the app was installed, not on what is inside the package.
This guide explains the mechanism, which Android versions it applies to, and the decision tree for clearing it — including the cases where you cannot.
The mechanism, in one paragraph
An AccessibilityService can read everything on screen, observe every tap, and perform clicks on the user's behalf. It is also the single most abused permission in Android malware: once granted, it can harvest one-time codes, dismiss confirmation dialogs, and drive a payment flow. Starting with Android 13, the OS records the installing package for every app. Apps delivered through a trusted installer (the Play Store, or a device-owner provisioning flow) get the normal permission flow. Apps installed from a browser download, a file manager, or ADB are flagged as coming from an untrusted source, and the OS disables the switches for the highest-risk settings: accessibility services, notification listeners, and on some vendor skins usage access.
The flag is about provenance, not reputation. A byte-for-byte official build with a valid signature gets the same treatment as a random file from a forum. This is why people assume they downloaded a bad APK and go hunting for another mirror.
A decision tree before you touch anything
| What you see | Actual gate | Where to fix it |
|---|---|---|
| "Installation blocked / unknown sources" during install | REQUEST_INSTALL_PACKAGES | Settings → Special app access → Install unknown apps |
| "App not installed" / parse error | Signature, ABI, or package corruption | Verify the file, check SDK/ABI |
| Location or camera permission disappears after weeks | Permission auto-reset (Android 11+) | App info → Permissions → disable auto-revoke |
| Accessibility / notification listener toggle greyed out | Restricted settings (Android 13+) | App info → ⋮ → Allow restricted settings |
If the app installs and runs and only the sensitive toggle is dead, you are on the last row.
Clearing the flag (stock Android 14–16)
- Launch the app at least once. On several builds the "Allow restricted settings" menu item does not render until the app has been opened. Skipping this step is the most common reason people report the menu is missing.
- Open Settings → Apps → See all apps → [your app].
- Tap the ⋮ overflow menu and choose Allow restricted settings.
- Complete the screen lock / biometric confirmation.
- Go back to Settings → Accessibility → Downloaded services. The switch should now be live.
Vendor skins move the item around. If the overflow menu has nothing: use the Settings search box and search restricted; open the app's detail page from system Settings rather than a third-party cleaner; check whether the app lives inside a work profile or secondary user, in which case you must repeat the steps in that space; and confirm the device is on Android 13 or later — on Android 12 a greyed toggle has a different cause entirely.
Why the fix sometimes doesn't stick
| Symptom | Cause | What to try |
|---|---|---|
| No menu item at all | App never launched, or OEM hid the entry | Launch once; use Settings search; check Special app access |
| Still grey after allowing | Device admin / MDM policy, or security suite override | Check Device admin apps; on managed devices, stop here |
| Toggle turns itself off | Battery optimisation or vendor "background protection" | Whitelist the app from battery optimisation |
| A different APK version works | That build no longer declares the service or targets an older SDK | Don't rely on it — it is a downgrade, not a fix |
| Installed via ADB, still blocked | ADB is also an untrusted installer | Same flow, no special case |
Managed devices are a hard boundary. If an organisation owns the profile, the policy comes from the admin console and no local menu can override it. Any guide claiming otherwise is either outdated or asking you to compromise the device.
Before you grant accessibility to a sideloaded app
You are about to hand over screen content and tap control. Two minutes of checking is worth it:
- Source. Get the package from the developer's site or the official Play listing. When using a downloader such as gptoapk, confirm you are getting the original file rather than a repack.
- Signature.
apksigner verify --print-certs app.apkprints the certificate. Compare it with a previous version or the developer's published fingerprint. - Manifest.
aapt dump permissions app.apkshows what the app asks for. A "cleaner" that requests SMS access and device-admin rights is not a cleaner.
If any of those three don't line up, leave the restriction in place. The gate is doing its job.
FAQ
Does allowing restricted settings void warranty or trip a security warning? No — it is a documented user-facing switch, just buried. Some vendor security hubs will show a reminder once accessibility is on; that is informational.
Why doesn't the Play Store version need this? The trusted installer has already validated the developer identity and package provenance, so the OS does not add the extra gate. That is the whole reason the same app behaves differently depending on where it came from.
Do I need to repeat it after every update? A normal in-place update with the same signing certificate usually preserves the allowance. Uninstall/reinstall, a signature change, or a different installer resets it.
Is there a way to get accessibility without changing the setting? Some desktop-companion tools use ADB authorisation instead, and a few apps offer a non-accessibility mode. Workarounds that spoof the installer tend to break with the next security patch.
Bottom line
A greyed-out accessibility switch is an install-source problem, not a file problem. Confirm the app installs and launches, apply "Allow restricted settings" from the system app detail page, and verify the package's source, signature, and permissions before you hand over that much control. When you need a clean official build to verify against, search by app name or paste a Play Store URL into gptoapk and check the signature first.