Why "restricted"?

[irrlicht]

For a while now (I think this began with 2.4 but I’m not sure) I have again and again the situation that I install an app and then some settings are “restricted”. This happened yesterday with Lawnchair 3 I installed for testing from IzzyOnDroid using Foxy Proxy (F-Droid client app with additional repositories).

Some settings are gray:

But I can still tap on the Allow-notification-access-switch. When I do this I get an information that this is currently restricted:

I have the following questions:

1. Why has this app restrictions and other apps have not?
2. How long is “currently”?
3. What can I do to unrestrict these restrictions?

In the current case Lawnchair can’t show notification bullets because of the access on notifications is restricted. Lawnchair can also not react on all tap gestures. I call this a significant lack of functionality. But yes, when nothing is allowed I have then of course reached a great level of security.

[aibd]

Well that is a new one on me but I found https://www.xda-developers.com/android-13-restricted-setting-notification-listener/.

In a brief reading … it seems this can particularly happen when an app is sideloaded or perhaps the app comes from an “unofficial” source.

Is there a space in Settings > Accessibility to allow the launcher to “bypass” this behaviour ?

[irrlicht]

Thanks a lot for this link. This webpage contains another link which leads then to a simple work around. I tell it for all:

If you have such a restricted app …

• open the Settings app
• go into the Apps section
• search your app and tap on it, so you get a screen called “App info”
• if your app is indeed restricted until now you should have a three dots menu in the upper right corner, tap on it to open the menu
• the menu shows only one menu item: “Restricted Permissions”, tap on it

From that moment on this app is not restricted anymore. Also the menu is gone like in all other unrestricted apps.

BTW: the webpage tells a lot about Android 12 and the differences in Android 13, it mentions the undefined term “App Store” and distinguishes installations made by an App Store from not made by an App Store. – I had this phenomenon using at least the Aurora Store a lot, not as often also with F-Droid repositories. At least Aurora uses in my case also the so called “session-based package installation API” which should avoid this problem.