System App Permissions

[deleted]

Why do system apps have permissions to access network/sensors by default if they work without them?

Is it possible to add permissions to sensors and network only if it is necessary to work?

matchboxbananasynergy

As a general rule, you're achieving nothing by disabling permissions from system apps. The only thing that's going to end up happening is things breaking and us not knowing how to help you fix them, since we won't know exactly what you've changed.

If you trust GrapheneOS, there's no reason to be adjusting permissions or anything else for system apps.

The Network and Sensors permission are granted by default to ensure compatibility as these are permissions that GrapheneOS adds.

For user-installed apps, you have a checkbox to disallow network for the app you're installing in the installation confirmation prompt.

There's also a toggle in the Settings to revoke the Sensors permission for newly installed apps.

[deleted]

matchboxbananasynergy If you trust GrapheneOS, there's no reason to be adjusting permissions or anything else for system apps.

One rule I learned in my life is to have limited trust to anyone. GOS is not a cult. This OS is used by people with some awareness.

I think states trusted in Crypto AG, do you know the story?

[deleted]

The topic is not solved in my opinion.

unwat

@[deleted]

It's easier to trust them, but if you don't the code is available for you to audit: https://github.com/GrapheneOS.

I doubt that anyone thinks that you're incapable of administering your phone. But the fact is many users just don't fully know what system apps do. Many users see a system app/service with a name they don't understand and want to disable its permissions.

The sensors & network permissions are added by GrapheneOS, so apps don't know how to check for or request the permissions. This is why they're granted by default. AOSP is a huge code base. Removing an app/service's network or sensors permission can have unintended and unexpected consequences.

One foolproof way of keeping GrapheneOS stable for everyone is by restricting users' ability to make changes to system permissions.

Flatty

If changing permissions in the system apps leads to OS crashes, then why do you make them available to be changed? Just fix them and dont show, then you will have less post on this forums "GOS crashes, what to do?"

de0u

Flatty If changing permissions in the system apps leads to OS crashes, then why do you make them available to be changed? Just fix them and dont show, then you will have less post on this forums "GOS crashes, what to do?"

Maybe, but I suspect this may be a can't-win situation for the developers. I believe GrapheneOS has made previously made it impossible for users to change a few specific permissions, and people have complained about not being in full control (even though anybody can build their own tweaked GrapheneOS).

Flatty

So maybe golden middle would be to display some warning message with info saying what may go wrong after changing certain permission, while one tries to toggle the setting switch of system app?