Rockchip · AI & Linux Hub

Android & BSP

Rockchip Android Application Preinstallation

Rockchip Android Application Preinstallation

· ArmSoM Editorial · Rockchip source documentation · 3 min read

Complete technical pages 6–7 of bilingual RK-SM-YF-203 V1.2. The technical scope is Android 8.1 and later with an Android Q update: historical source scope requiring target-BSP verification. Chinese/English follow their respective text, with extraction-collapsed English spacing repaired; Russian/German are complete translations. No technical images/tables exist. Cover dates, disclaimers, contacts, audience and revision history are removed. No commands, flashing or hardware tests were performed.

Audit: all three installation behaviors, input directories and output directories remain in their original order; the page-split correspondence is joined. No source script path was supplied, so none is guessed. The source pairs $OUT/oem with odm/odm.img; retain this and verify the target SDK. The systemuid restriction and native mk integration reference remain. Flashing may erase data: use authorized devices, back up and verify the image. This document does not grant redistribution rights for third-party APKs.

1 Overview

Android application preinstallation pre-installs prepared third-party applications into Android when configuring a product according to manufacturer requirements.

Preinstallation includes:

  1. Install applications that cannot be uninstalled.
  1. Install applications that can be permanently uninstalled.
  1. Install applications that are automatically restored after a factory reset if previously uninstalled.

2 Function enable instruction

2.1 Configuration and usage

After source, enter the following command to find the corresponding target directory, such as device/rockchip/rk3126c/.

get_build_var TARGET_DEVICE_DIR

The target directory contains three folders:

1. preinstall
2. preinstall_del_forever
3. preinstall_del

They respectively correspond to the types in the overview. Put applications in the appropriate folder. Prefer English APK filenames and avoid spaces.

After a successful make, corresponding folders are generated under $OUT/oem:

1. bundled_persist-app
2. bundled_uninstall_gone-app
3. bundled_uninstall_back-app

These also correspond to the types described in the overview.

After flashing, the system automatically installs these applications into the corresponding directories.

Note: preinstallation of applications with systemuid is not supported. Use the native Android method to write the mk file; see the integration under vendor/rockchip/common/apps/RkDeviceTest/.

2.2 Compiling result

After compilation, the configuration files are output to the odm partition ($OUT/oem/). After adding them, ensure odm.img is flashed for them to take effect.

Explore this topic → · Learning paths →