Pre-installed Apps

To selectively enable pre-installed apps, the respective package name of the app is required. A complete list of all pre-installed apps that are no longer available after enrollment in Android Enterprise can be obtained by resetting the device to factory settings and completing the full device setup process without enrolling the device in Android Enterprise.

Whether non-vital pre-installed system apps are disabled during enrollment is defined by the enrollment switch Keep system apps enabled. Relution only includes it in the QR code, not in the DPC identifier, see Enroll EDLA devices →.

Once the device is fully set up and ready to use, a connection to the device is established via Android Debug Bridge →. The following command then exports a list of all installed packages:

 adb shell cmd package list packages > list1.txt

The device is then reset to factory settings again and enrolled in Android Enterprise.

After successful enrollment, the device is connected via ADB again and the following command is run:

 adb shell cmd package list packages > list2.txt

Both files can now be compared.

All apps that appear in the file list1.txt but are missing from list2.txt need to be added with the installation type Pre-installed in the Manage apps configuration.

In the Manage apps configuration, Add opens the Select an app dialog. There, Manually add app is selected as the Source. In the next step, Name (display name of the app) and Internal name (package name) are entered. The internal name corresponds to the entry from the file list1.txt to be added – but without the package: prefix. Example: If the entry package:io.relution.files is to be added, io.relution.files is entered as the internal name.

The app is then listed with the installation type Force-installed. In the Installation type column, Pre-installed is selected.

Customer Hub

Pre-installed Apps