Skip to content

Feature: Disable Packages

Overview

This feature allows for disabling packages at start up (after configuration is loaded).

It uses the values in disablePackages, but also makes sure the package is not in the 'protected' list of applications (for example, a device administrator cannot disable com.bluefletch.ems.support

<<<<<<< HEAD

Flow

======= WARNING: Disabling system applications may affect device behavior. Always test changes before deploying to production.

Flow

ab53d97057da9ca55d49e967389ce54915d6e012

There are two ways that a package can be disabled.

  1. After Configuration is loaded, the configuration is read for disablePackages. All packages within the disablePackages collection are disabled.

  2. After a package installation is detected, if the package exists within the disablePackages collection, it is disabled.

Note: If a package is within the Protected List collection, it will not be disabled.

Technical Notes

Configuration :

disablePackages : list of packages to disable.

Example:


   "disablePackages": [
         "com.google.android.googlequicksearchbox","com.android.browser"
   ],

Feature Introduced

Feature Introduced in Launcher 2.8.x