halogenOS / android_manifest

Getting Started with XOS

0. Preliminary Knowledge

Before beginning this entire process, please ensure you have sufficient storage space. To carry out a single device build an excess of over 40 GB will be required. If building for more than one device, this amount of required storage increases. For speedy builds it is highly recommended that you store the sources in a fast storage medium such as Solid State Drives (SSDs), with modern computers it often turns out to be a greater bottleneck than the processor itself when compiling Android. If you decide to build on a SSD, make sure that you use MLC or SLC SSDs only as the lifetime of TLC and QLC SSDs will be impacted as you build the OS. You can also build on a HDD but keep in mind that doing so without a read/write cache will harm build speed as random access to storage is inherently slow on HDDs compared to SSDs.

It should also be noted that in order to build Android from source successfully, you will require GNU Make and Git as well as a few build and compiler centric packages, this will vary from distribution to distribution. If you read on, you'll find more information as to what is necessary. Note that the tools needed depend on quite a few factors, some being out of our control, so please make sure you look the necessary packages up in case any is missing before contacting us about issues with the build.

Before you continue, make sure you follow the Setting up a Linux build environment guide as it contains a lot of useful and important information regarding building AOSP.

While most builders will probably use a Ubuntu-based distribution, you can also build on other distributions including Arch Linux and derivatives. In case you use Arch Linux you could follow this guide for more information. Below we have outlined which packages will be necessary.

You need to install a few tools for everything to work properly, these are our recommended set of tools to use: clang, bc, bison, ccache, curl, flex, python, repo, unzip, zip, imagemagick, bash, git, xmlstarlet, make

Depending on your distro of choice, you may need to specify a package name other than the ones outlined above.

For Arch Linux users:

There are quite a few things that need to be installed before starting.

We recommend running following command to ensure you have all the tools you need:

# Instead of yay you can use your preferred AUR helper or just pacman
yay -S \
  base-devel multilib-devel bc bison ccache curl flex \
  gnupg gperf libxslt ncurses perl-switch python2-virtualenv \
  noto-fonts repo rsync schedtool sdl squashfs-tools unzip \
  vim zip zlib lzop pngcrush imagemagick bash git brotli xmlstarlet

CCache

We also recommend you to use CCache for faster builds (if you don't know what CCache is, do some research about it or skip this step):

In your environment (e. g. .bashrc and make sure you copy&paste the two lines into your terminal):

CCACHE_DIR="/path/to/ccache"
USE_CCACHE=1

Run following command to set the size limit of Ccache (minimum 80G recommended):

ccache -M 80G

1. Getting Started

To get started with XOS, you should first become familiar with the basics of the utilities named Git and repo, if using a development oriented distro or are already an actual developer working with source based Android ROMs or other similar projects you should more likely than not already have these obtained, if not here's an idea of what one should do below.

Installing repo

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

Now add the directory to your PATH variable in your environment (e. g. by appending it to your ~/.bashrc and running the same command in your shell)

export PATH="$HOME/bin:$PATH"

Installing git

If you followed the Arch Linux steps above, you can go right to step 2. Git would more likely than not probably be already installed in your distribution, if it is not then you should try one of the following terminal commands depending on your distribution:

Ubuntu, Debian (apt): apt-get install git
OpenSUSE: zypper install git
Fedora: yum install git-all
Gentoo: emerge --ask --verbose dev-vcs/git
Arch Linux: pacman -S git # this was listed above already, you can skip it

The derivatives of these common distributions should also have the git package available, if you believe your distribution does not offer git in the default package repositories then you may consider compiling and installing git from source.

2. Initiating Repository and Acquiring Sources

First, create a new empty directory of your choice, and cd into it:

mkdir xossrc
cd xossrc

Of course, you can use any directory name you desire. It is recommended to avoid spaces.

Now initialize a repo source tree, to do this please use following command:

repo init -u https://git.halogenos.org/halogenOS/android_manifest.git -b XOS-10.0

Then synchronize the source tree using repo, which will fetch the source of XOS. You should be warned that this is a procedure which downloads huge amounts (about 25-40 GB in total) of data, it may take hours to complete. Be prepared with something fun to do as will be waiting for a while or just listen to EDM.

repo sync -c --no-tags --no-clone-bundle -f build/make external/xos vendor/aosp
source build/envsetup.sh
reposync

3. Building

First, in order to build XOS you should source the build/envsetup.sh script in your shell, this will set up and import all of the available device configurations for the ROM as well as giving you some fancy "macro" commands for your build environment. As such, in order to do this, run the command:

source build/envsetup.sh

By running

breakfast <device>

you can fetch the device tree and its dependencies of devices hosted by us.

Now, you should select and configure the build target by using the lunch command. Type 'lunch', and a list of the available devices and build targets will be offered, give it a whirl, it won't bite.

Additionally here's a list of build types for your target device that you will likely encounter while running 'lunch'.

Before you start building, make sure that you have all necessary device-specific trees. Official trees, maintained by the team, can be retrieved using:

breakfast <device>

Example:

breakfast cheeseburger

At this point you should be able to build the ROM freely, all that's left to do is enter...

build full aosp_<device>-userdebug

Example:

build full aosp_cheeseburger-userdebug

This build command is a specialty made by the XOS team. It does everything for you, from lunching to breakfasting, and initiating a new build, as well as finding out which amount of threads are optimal for your machine. Hence you must not specify a thread count using -j on this command, as that will be done automatically for you. If you want to do a dirty build (i. e. skip make clean), simply add noclean to the end of your command like this: build full aosp_<device>-userdebug noclean

In your terminal, the master chef that is 'Mr Compiler' (aka Ninja) will do the cooking of the ROM for you, this will take another while and depend on your storage speed and the capability of your CPU.

Once done you should find a cute flashable zip either in your directory or within out/target/product/, this is your creation, you compiled it, she's yours, your own adorable pet... just make sure to treat her very nicely :).

Additional build notes : If you're bringing up a new device, our wiki has some important info

4. Flashing

If you do not know how to flash an Android ROM then you probably shouldn't have followed this guide in the first place, or have a case of amnesia, but in the case that you do need a briefing then here's a short guide on flashing XOS: https://goo.gl/BB53SU