Apps : No auto start / bloquer démarrage auto

Using /e/OS Applications
1

Hello
I want to lock/avoid auto-start of some apps

  • at boot
  • after boot
    I made a lot of searchs on this forum and in the wiki/FAQ , but without results :cry:

Any help would be welcome

S9 bought from /e/ :grinning: /e/OS 1.5-20221028230220

Regain your privacy! Adopt /e/ the unGoogled mobile OS and online servicesphone

2

In the past I believe Lineage’s Privacy Guard could handle that. Now one probably needs a root-enabled app to control that. Not sure what’s possible via adb.

3

OK , thanks

May i suggest the development team to deal with this item
If yes , where ?

1 Like
4

I should’ve mentioned that Privacy Guard, and by extension the ability to use Lineage addonsu (root), was removed by Lineage after Pie I believe. There’s nothing that the Murena team can do about that.
There’s been many a discussion online over the years about this. Here’s one that covered a number of items.

Transitioning from LOS16’s Privacy Guard to LOS17’s Permission Hub (feature regression)

There was/is a commandline utility called appops that could probably be used but one needs to know the exact autostart permission to use it. Then it’s a matter of whether or not that permission is still available. Such as…

appops set <package> BOOT_COMPLETED deny

BOOT_COMPLETED didn’t work in my test. At the moment I haven’t checked for other perms.
[ It’s almost 6:30am. I should get some sleep first. :slight_smile: ]

A root terminal or adb is needed to use appops. Of course if one is rooted this is moot as there are any number of apps and tools that can be used.

Here’s a brief overview of the appops command.
Set permissions via adb and appops command

5

OK
eOS is anyway already a fu… good O.S. ,
this feature could have set eOS to perfection :grin:
but i can live without it :sunglasses:

6

This topic was automatically closed after 47 hours. New replies are no longer allowed.