Installing applications on pure Android (AOSP)

Operating system Android Open Source Project (AOSP) is a reference version of the platform, devoid of proprietary shells from manufacturers like One UI or MIUI. In its pure form, it is often used by developers, custom firmware enthusiasts, and owners of specialized devices such as set-top boxes or tablets for business. The absence of a pre-installed store Google Play on many AOSP assemblies requires the user to know alternative methods for installing software.

The process of adding apps to such an environment is radically different from the usual tapping on the “Install” button in the marketplace. You will have to work with installation packages of the format .apk directly, using either the built-in system tools or debugging tools on your computer. Understanding Android's security architecture and access rights is a key factor in the successful integration of any software.

In this guide, we will examine in detail all the legitimate ways to transfer applications to a device running pure Android. We will look at both simple methods for ordinary users and advanced techniques for system administrators that provide complete control over the installed software.

Preparing the environment and installation sources

Before starting any manipulations, it is critical to ensure the safety of the device. Since you will be installing apps from external sources, the risk of introducing malicious code increases. Make sure to download files only from trusted repositories, such as APKMirror or F-Droidthat verify the digital signatures of developers.

In the security settings of pure Android, there is a mechanism that blocks the installation of unknown applications by default. To bypass it, you must grant permission to a specific Explorer or browser application. Go to menu Settings → Applications → Special access → Install unknown applications.

Here you will see a list of apps that can initiate installation. Select the file manager or browser through which you plan to run the installer, and activate the "Allow from this source" switch. Without this setting, the system simply will not allow you to run the installation script.

⚠️ Attention: Giving rights to install unknown applications to all apps in a row creates a vulnerability. Enable this option only for a specific tool at the time of need and disable it immediately after finishing work.

It is also worth checking the availability of free memory. The installer files may be small, but the unpacked cache and library data takes up a significant amount of space. On devices with small internal storage, this can be a critical limitation.

Directly installing APK files through a file manager

The most accessible method for most users is this manual installation of the downloaded file. After downloading the package .apk to your device, open any installed file manager. In a pure Android environment, the application Files from Google or the built-in explorer is often used.

Find the downloaded file in the folder Download and click on it. The system will parse the application manifest, check the required permissions, and display a confirmation window. If the digital signature matches the already installed version (when updating), the process will be seamless.

However, if you try to install a modified version or an application from another developer over the existing one, the system will throw a signature conflict error. In this case, you will need to completely remove the old version before installing the new one, which will result in the loss of local app data.

• 📂 Download the APK file via a browser or transfer it via Bluetooth/Wi-Fi Direct.
• 🔍 Open the file manager and go to the download directory.
• ✅ Click on the file and confirm the installation in the system dialog.
• 🚀 Launch the application from the menu or desktop after the process is completed.

It is worth noting that some modern applications use a format Android App Bundle (.aabthat cannot be installed directly through the file manager on the device. Such packages require pre-processing on a computer or installation through specialized managers that can work with shared resources (split APKs).

Using Android Debug Bridge (ADB) for installation

For advanced users and administrators of AOSP-based devices, an indispensable tool is ADB (Android Debug Bridge). This utility package allows you to manage the device from a computer via the command line, bypassing many user interface limitations.

To get started, you need to activate developer mode on the device itself. Go to Settings → About phone and quickly click 7 times on the "Build number" item. After the message “You have become a developer” appears, a new section “For Developers” will appear in the settings menu.

In this section, activate the "USB Debugging" item. Connect your smartphone or tablet to your computer with a cable. A request to confirm debugging will appear on the device screen with the fingerprint of the computer's RSA key - be sure to click "Allow", otherwise the connection will not be established.

adb install -r path/to/application.apk

The command above is the basic one for installation. The flag -r indicates the system to reinstall the application while preserving the data if it is already present. This is especially useful when debugging your own developments or installing updates that are not accepted through the standard interface.

ADB command	Description of action	Use scenario
adb install app.apk	Standard installation	Initial installation of a new Software
adb install -r app.apk	Installation with replacement	Updating the version with saving data
adb install -d app.apk	Installation with downgrade	Rollback to the old version of the application (Downgrade)
adb install -g app.apk	Installation with granting rights	Automatic consent to all permissions

Using the console makes it possible to install applications even when the device interface is frozen or the touch screen does not function correctly. The main requirement is that the kernel boot system is running and the ADB service is active.

⚠️ Attention: The command adb install -d (downgrade) does not work for all applications. System components and apps with version rollback protection may block this operation, requiring a complete data reset or root access.

Working with split packages (Split APKs)

The modern Android ecosystem has moved to a modular application structure. One file .apk is often replaced by a set of files: a base module, configurations for different languages, screen densities and processor architectures. A regular installer will not be able to correctly process such a group of files separately.

To install such kits on a pure AOSP, you must use specialized utilities, for example SAI (Split APKs Installer) or command adb install-multiple. These tools assemble all the parts into a single whole directly during the installation process.

If you try to install each file from the set one by one through the file manager, the system will throw an "App not installed" error after the first file, since a base module without resources is not a full-fledged application. Always check the format of the downloaded archive.

When using ADB, the command for multiple installations is as follows:

adb install-multiple base.apk config.ru.apk config.arm64_v8a.apk

It is important to list all files related to one application in one command. The order of the files is usually not critical for the installer, but the presence of a basic module (often called base.apk) is mandatory.

Why do Split APKs appear?

Splitting applications allows you to reduce the size of the downloaded update on Google Play. The device loads only those language packs and graphic resources that are suitable specifically for your model, saving traffic and space.

Installing system applications and privileges

In the AOSP environment, there is a strict separation between user and system applications. Conventional installation methods place the software in a partition /data/app, where it runs with limited rights. Sometimes it is necessary to integrate a app as a system one so that it starts before the user logs in or has access to protected APIs.

For such an operation, superuser rights are required (Root). Without them, writing to the directory /system/priv-app is impossible due to the system partition being mounted read-only. Having root access allows you to move APK files to the desired directory and set the correct access rights (permissions).

The process is as follows: the file is copied to /system/priv-app/NameApp/, after which its permissions are set 644 (rw-r--r--). The owner of the file must be root:root. After the reboot, the system will scan the directory and register the application as built-in.

• 🔓 Get Root access through Magisk or a similar tool.
• 📁 Create a folder with the name of the application in /system/priv-app/.
• 💾 Copy the APK file to the created directory.
• ⚙️ Set access rights to 644 and the owner root through a terminal or file manager with root access.

Incorrect setting of system rights can lead to bootloop (cyclic reboot). If the system cannot read a critical file due to an error in access rights, the download process will freeze at the service initialization stage.

⚠️ Attention: Before making changes to the system partition, be sure to make a full backup (Nandroid backup) using custom recovery. An error in one byte of a system application can make the device unusable without flashing it.

Solving common installation problems

Even if you follow all the instructions, users may encounter errors. One of the most common problems on stock Android is the “App not installed” message. This may indicate a signature conflict, lack of space, or incompatible processor architecture.

If the device reports a "Parse error" error, this often means that the file was not downloaded completely or was damaged in transit. This error also occurs if the Android version on the device is lower than the minimum required SDK version specified in the application manifest.

In cases where the application is installed, but immediately closes (crashes), check the logs via adb logcat. Often the problem lies in the lack of the necessary Google services (GMS), which many commercial applications require to work, and in pure AOSP builds they may be absent.

For diagnostics, use the command:

adb logcat | grep "AndroidRuntime"

This filter will show only messages about critical runtime errors, which will help you quickly find the cause of the crash. If the logs mention a specific class or library missing, you may need to install an additional dependency or a different version of the application.

Why won't the application install even though there is enough space?

The problem may be in the file system. If the data partition is formatted incorrectly or the limit on the number of nodes (inodes) has been reached, the system will not be able to create new files, even if there are gigabytes of free space. Try clearing the application cache or checking the file system.

Is it possible to install an application from Android 13 on Android 11?

Usually no. Applications compiled for new versions of the SDK can use APIs that are not physically available in older versions of the system. Although backward compatibility is a strong point of Android, it does not guarantee the operation of software developed for future versions of the OS.

What is application verification during installation?

This is a security feature that checks the APK file for known viruses through the Google Play Protect database. On devices without Google services, this check may be absent or work incorrectly, so responsibility for security falls on the user.

How to delete an application that cannot be deleted through settings?

If an application has device administrator rights, it cannot be deleted in the standard way. Go to Settings → Security → Device administrators, uncheck the desired application, and then remove it using the usual method. In difficult cases, the command will help adb uninstall.

Is it safe to use third-party stores on AOSP?

Using alternative stores such as F-Droid or Aurora Store is quite safe and is often recommended for devices without GMS. They provide proven open source software or anonymous access to the Google Play directory, minimizing the risks of surveillance.