Skip to content
AI Box Fix

Apps & launchersReviewed

Can't Enable an App's Notifications or Accessibility Access

An app's notification access or accessibility switch greyed out on Android 13? Allow restricted settings from its three-dot menu. UX999, Picasou.

Illustration: ApplePie UX999 Plus 1.0 / 2.0 in a car on an open road

Quick answer

On an ApplePie UX999 Plus running Android 13, when an app you installed has every permission granted but its notification access or accessibility switch stays greyed out, open its App info page, tap the three-dot menu top right and choose Allow restricted settings. One owner confirmed this; reinstalling the app from the official store worked for another.

Symptoms

  • You installed an app yourself, its normal permissions are granted, but its notification access or accessibility switch is greyed out and will not turn on
  • Turning the switch on shows a message that the setting is unavailable for your security, or blocked by the system
  • It started only after the box moved to Android 13 or a later version
  • An automation app cannot get its accessibility permission (interaction with the interface) to tap the screen for you
  • The app was installed from a file or a copy sent in a chat, not from an app store

Applies to

Devices
Connection to the car
CarPlay and Android Auto
Highest risk on this page
Low risk
Status
Workaround confirmed by the community

Why it happens

Android 13 added a rule it calls restricted settings. A few powerful switches, notification access, accessibility, display over other apps and device admin, are treated as special access. When you install an app from a file instead of an app store, Android marks it and blocks those switches, so the toggle is greyed out even though the app’s ordinary permissions went through.

The block is deliberate. These switches let an app read every notification or act on the screen for you, so Android does not hand them to a side-loaded app on the first try. It does not remove the switch; it hides it behind one extra confirmation that you give from the app’s own App info page.

Apps installed from an official app store are exempt from the rule. That is why the same app can be blocked when it comes from a file and work normally when it comes from the store.

Fixes, ranked

Allow restricted settings from the app's three-dot menu

  • Low risk
  • Time: 3 minutes
  • Worked for 1 of 1 report
  1. Open Settings → Apps (called App management on some firmware) and select the app whose access you cannot turn on.
  2. On the app’s App info page, tap the three-dot overflow menu at the top right.
  3. Tap Allow restricted settings and confirm.
  4. Go back to the special-access list, Notification access, Accessibility, or whichever you need, and turn the switch on for the app.
On Android 13 the app's App info overflow (three-dot) menu holds Allow restricted settings; grant it, then the special-access switch stops being greyed out. Reconstructed screen, labels may differ by firmware.

One ApplePie UX999 Plus owner who had moved the box to Android 13 installed a launcher with every permission granted, but could not switch on its notification access. Another owner explained that Android 13 handles this from the app’s own page through the three-dot menu, and that cleared it.

A Carlinkit TBox Ambient owner was pointed to the same three-dot route to unlock an automation app’s accessibility; they followed it but did not report back, so that one is not counted. A third owner, whose accessibility switch showed “blocked by the system”, was given the same steps and also did not report a result. If the menu item is missing on your box, use the next fix.

Reinstall the app from the official store

  • Low risk
  • Time: 10 minutes
  • Worked for 1 of 1 report
  1. Uninstall the copy you installed from a file.
  2. Install the same app from the official app store on the box.
  3. Open the app and let it ask for its special access, or turn the access on in Settings.
  4. If a store install is not possible and the switch is still blocked, use the three-dot route in the first fix.

One Ottocast Picasou 3 Pro owner could not grant an automation app’s accessibility permission, the “interaction with the interface” access it uses to tap the screen automatically. They updated the box firmware, factory reset it, and reinstalled the automation app from the official store instead of a copy obtained outside the store; afterwards every permission could be granted.

They could not say whether the firmware update or the store install did it, so treat this as a store install together with a reset rather than one proven step. A store install fits the mechanism, because apps from the store are not held back by restricted settings. A copy obtained outside the store can also be altered, which is its own reason to reinstall from the store.

Things to try (unverified)

  • Check your Android version first. The restriction belongs to Android 13 and later. If your box is on Android 12 or earlier and a special-access switch is greyed out, the cause is something else; start from the apps symptom page.
  • If the switch turned itself off after a few days rather than refusing from the start, that is a different problem: a background or battery-saver setting shutting the service down. The restricted-settings unlock above will not fix it.
  • Grant the access while the app is open. Some apps have a button that jumps straight to their accessibility or notification-access screen. If that screen still shows the switch greyed out, the restriction is the cause and the first fix is the lever.

If nothing works

Note the box model and firmware date (Settings → About), the Android version, the app and where you installed it from, and exactly what the switch does: greyed out, or a message that it is blocked for your security. A short video of the App info page helps.

If the app will not install in the first place, that is a separate problem; see install an APK on the box. If the app you are fighting is a launcher that will not start at boot once its access is granted, see launcher or app doesn’t open when the box starts and, for a launcher that loops on “Loading phone”, stuck on “Loading phone”.

If a store-installed app is still blocked, contact the box maker’s support (Carlinkit: [email protected]; Ottocast: [email protected]) with the details above. If you are choosing a box and want a cleaner app experience, start here.

What owners said

“Updated the firmware. Reset the settings. Installed MacroDroid from Google Play […] I was able to grant all the permissions. […] I don't know what did it, the new firmware or installing from the store. But it works!”
Worked: Install the app from the official store
Owner, Ottocast Picasou 3 Pro, Dec 2025
“Thank you, kind person! It all worked!”
Worked: Allow restricted settings
Owner, ApplePie UX999 Plus 1.0 / 2.0, Sep 2024

Quotes are translated where needed and shortened ([…]); names are removed. Full counts are in the evidence table below.

Questions owners ask

Why is the switch greyed out only for some apps?

Android 13 restricts notification access, accessibility and similar special access to apps installed from an app store. An app you installed from a file is blocked until you allow restricted settings for that one app.

Is allowing restricted settings safe?

It lets that one app use the special access you turn on next, nothing more. Do it only for an app you trust and installed yourself; the warning is there because this access is powerful.

The three-dot menu has no Allow restricted settings item. Now what?

Then the app is not under the restriction, or your box hides the menu. Reinstall the app from the official store, which is exempt, and turn the access on again.

Is this the same as Install unknown apps?

No. Install unknown apps lets a file manager install an APK; restricted settings controls the special-access switches after the app is installed. If the app will not install at all, see the install guide.

Did this work for you?

Tell us which fix worked (or didn't), with your box, firmware date and car. Reports are how fixes get confirmed and re-ranked.

Send a report

Changelog

  • Last reviewed against new community reports:
  • Confirmed by 2 community reports on ApplePie UX999 Plus 1.0 / 2.0, Ottocast Picasou 3 Pro.
  • Page updated:

"Confirmed" means a community member reported that the fix worked on their unit. We have not tested it on our own hardware. How we verify.

Evidence behind these counts (2 cases)

One row per case: a device, a symptom and a fix, merged from owner reports. An owner counts once per fix. Reports with no outcome yet are not counted. Forum and chat message references are kept on file but not published, to protect owners' privacy; public Reddit and YouTube sources are linked.

CaseConfirmed onResultSource
case-9300ApplePie UX999 Plus 1.0 / 2.01 workedOwner discussion threads, 4 messages
case-9301Ottocast Picasou 3 Pro1 workedOwner discussion threads, 2 messages