Building for Emulator/AVD

Introduction

In case you don’t have an officially supported device, don’t want to test changes on your daily driver, or are just someone who wants to test apps with OkcarOS-specific features, we’ve still got you covered.

These instructions will help you build an emulator-compatible version of OkcarOS, ready to run on your computer. If you want to use Android Studio/AVD there are also instructions for packing up/installing your custom build instead of the default AOSP images that Google provides.

What you’ll need

Let’s begin!

Build OkcarOS

Install the platform-tools

If you haven’t previously installed adb and fastboot, you can download them from Google. Extract it running:

unzip platform-tools-latest-linux.zip -d ~

Now you have to add adb and fastboot to your PATH. Open ~/.profile and add the following:

# add Android SDK platform tools to path
if [ -d "$HOME/platform-tools" ] ; then
    PATH="$HOME/platform-tools:$PATH"
fi

Then, run source ~/.profile to update your environment.

Install the build packages

Several packages are needed to build OkcarOS. You can install these using your distribution’s package manager.

To build OkcarOS, you’ll need:

For Ubuntu 23.10 (mantic), install libncurses5 from 23.04 (lunar) as follows:

wget http://archive.ubuntu.com/ubuntu/pool/universe/n/ncurses/libtinfo5_6.4-2_amd64.deb && sudo dpkg -i libtinfo5_6.4-2_amd64.deb && rm -f libtinfo5_6.4-2_amd64.deb
wget http://archive.ubuntu.com/ubuntu/pool/universe/n/ncurses/libncurses5_6.4-2_amd64.deb && sudo dpkg -i libncurses5_6.4-2_amd64.deb && rm -f libncurses5_6.4-2_amd64.deb

While for Ubuntu versions older than 23.10 (mantic), simply install:

Additionally, for Ubuntu versions older than 20.04 (focal), install also:

While for Ubuntu versions older than 16.04 (xenial), install:

Java

Different versions of OkcarOS require different JDK (Java Development Kit) versions.

* Ubuntu 16.04 and newer do not have OpenJDK 1.7 in the standard package repositories. See the Ask Ubuntu question “How do I install openjdk 7 on Ubuntu 16.04 or higher?”. Note that the suggestion to use PPA openjdk-r is outdated (the PPA has never updated their offering of openjdk-7-jdk, so it lacks security fixes); skip that answer even if it is the most upvoted.

Python

Different versions of LineageOS require different default Python versions.

If your default is python3, but you’re building branch that requires python2, there are various methods to using it, e.g. symlinking it manually or creating a virtualenv for it. We recommend the latter:

Generate the virtualenv once using virtualenv --python=python2 ~/.lineage_venv. Afterwards, activate it in each terminal where you need python2 as default by running ~/.lineage_venv/bin/activate.

The path ~/.lineage_venv can be chosen freely, this is just an example!

Create the directories

You’ll need to set up some directories in your build environment.

To create them:

mkdir -p ~/bin
mkdir -p ~/android/lineage

The ~/bin directory will contain the git-repo tool (commonly named “repo”) and the ~/android/lineage directory will contain the source code of OkcarOS.

Install the repo command

Enter the following to download the repo binary and make it executable (runnable):

curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo

Put the ~/bin directory in your path of execution

In recent versions of Ubuntu, ~/bin should already be in your PATH. You can check this by opening ~/.profile with a text editor and verifying the following code exists (add it if it is missing):

# set PATH so it includes user's private bin if it exists
if [ -d "$HOME/bin" ] ; then
    PATH="$HOME/bin:$PATH"
fi

Then, run source ~/.profile to update your environment.

Configure git

Given that repo requires you to identify yourself to sync Android, run the following commands to configure your git identity:

git config --global user.email "you@example.com"
git config --global user.name "Your Name"

Due to their size, some repos are configured for lfs or Large File Storage. To make sure your distribution is prepared for this, run:

git lfs install

Turn on caching to speed up build

Make use of ccache if you want to speed up subsequent builds by running:

export USE_CCACHE=1
export CCACHE_EXEC=/usr/bin/ccache

and adding that line to your ~/.bashrc file. Then, specify the maximum amount of disk space you want ccache to use by typing this:

ccache -M 50G

where 50G corresponds to 50GB of cache. This needs to be run once. Anywhere from 25GB-100GB will result in very noticeably increased build speeds (for instance, a typical 1hr build time can be reduced to 20min). If you’re only building for one device, 25GB-50GB is fine. If you plan to build for several devices that do not share the same kernel source, aim for 75GB-100GB. This space will be permanently occupied on your drive, so take this into consideration.

You can also enable the optional ccache compression. While this may involve a slight performance slowdown, it increases the number of files that fit in the cache. To enable it, run:

ccache -o compression=true

Initialize the OkcarOS source repository

The following branches have been tested for building emulator images:

Enter the following to initialize the repository:

cd ~/android/lineage
repo init -u https://github.com/OkcarOS/android.git -b lineage-20.0 --git-lfs

Download the source code

To start the download of the source code to your computer, type the following:

repo sync

The OkcarOS manifests include a sensible default configuration for repo, which we strongly suggest you use (i.e. don’t add any options to sync). For reference, our default values are -j 4 and -c. The -j 4 part implies be four simultaneous threads/connections. If you experience problems syncing, you can lower this to -j 3 or -j 2. On the other hand, -c makes repo to pull in only the current branch instead of all branches that are available on GitHub.

Start the build

Time to start building!

Setup the environment:

source build/envsetup.sh

Select the build target by running the following command, where <target> is one of the entries in the table below:

lunch <target>
    Build targets Supported <arch>
OkcarOS 17 and below      
Phone Emulator/GSI lineage_<arch>-eng arm, arm64, x86 and x86_64
OkcarOS 18.1      
Phone Emulator/GSI lineage_<arch>-eng arm, arm64, x86 and x86_64
TV Emulator/GSI lineage_tv_<arch>-eng arm, arm64, x86 and x86_64
Automotive Emulator/GSI lineage_car_<arch>-eng arm64 and x86_64
OkcarOS 19 and above      
Phone Emulator lineage_sdk_phone_<arch>-eng x86 and x86_64
Phone GSI lineage_gsi_<arch>-eng arm, arm64, x86 and x86_64
TV Emulator lineage_sdk_tv_<arch>-eng arm and x86
TV GSI lineage_gsi_tv_<arch>-eng arm, arm64, x86 and x86_64
Automotive Emulator lineage_sdk_car_<arch>-eng arm64 and x86_64
Automotive GSI lineage_gsi_car_<arch>-eng arm64 and x86_64

For starting, x86 or x86_64 is recommended, as your computer can run it natively using hardware acceleration.

Instead of eng one can also target userdebug, the latter is used by official AOSP emulator images, but ADB and communication with the emulator will need to be enabled first.

Now, build the image:

mka

Running the emulator

Assuming the build completed without errors, type the following in the terminal window the build ran in:

emulator

The emulator will fire up and you’ll see the OkcarOS boot animation. After some time, it will finish booting up and be ready to use.

Success! So… what’s next?

You’ve done it! Welcome to the elite club of self-builders. You’ve built your operating system from scratch, from the ground up. You are the master/mistress of your domain… and hopefully you’ve learned a bit on the way and had some fun too.

Exporting for use in Android Studio/AVD

In case you want to run the emulator image independently from the system/terminal you built it in, you are able to export the built image into a format that can be used by Android Studio/AVD. To do that, run the following command in the same terminal that you originally started the build in:

mka sdk_addon

If you now look into the out/host/linux-x86/sdk_addon directory, you will find a ZIP file (ending in -img.zip) that contains all the necessary files for running the emulator image externally.

To deploy the build into your Android Studio installation, move the contained folder (which is named after the architecture that you built for) into a subfolder of /path/to/android/sdk/system-images. AOSP uses the following path name by default, but you are free to make up your own as well:

system-images/android-<sdk version>/<tag>/<arch> (where <tag> is one of default/google_apis/google_apis_playstore)

OkcarOS emulator builds will use the tag lineage by default (visible as “OkcarOS” in the images list).

As long as you haven’t moved the folder directly into system-images, the emulator image should now show up in the of the lists of images when creating a new virtual Android device.

To get assistance