Halium-7.1 - Setting up the sources¶
The sources necessary for the full system image build for Halium-7.1. Halium 7 requires a full system image build.
Setting up the sources for Halium-7.1 builds¶
Create a directory for your Halium source tree:
mkdir halium && cd halium
This directory will be referred to as BUILDDIR throughout the remainder of this guide.
First, initialize your source to the correct version of Halium:
repo init -u https://github.com/Halium/android -b halium-7.1 --depth=1
Then download the code by issuing the command:
repo sync -c -j 16
The download will take some time as it counts several gigabytes. If you have a fast internet connection, you may set an extra JOBS=[number] environment variable at the beginning of the command to open more parallel downloading jobs. Generally, 12 is recommended, which is the default. When it completes, your BUILDDIR will contain a copy of the Halium source tree, but important parts are still missing.
Adding your device-specific source¶
The next step is to add the device-specific sources that need to be integrated into the source tree before you can attempt to build. The missing sources are those required to build the kernel as well as a host of other hardware-specific components of the port.
The necessary sources need to be located and specified by creating a device manifest file (or editing an existing one) in the directory
A correct device manifest is crucial to the success of your port.
Locating the sources¶
Locate your device repository on LineageOS’s GitHub organization. This is done by typing your device’s codename into the search box. The device repository follows the naming convention: android_device_[manufacturer]_[device]. Make a note of this name.
Open the device repository on Github. It will contain a
cm.dependencies) file which specifies all other repositories that your device is reliant upon.
Creating the device manifest file¶
Now create (or edit) the file
BUILDDIR/halium/devices/manifests/[manufacturer]_[device].xml. (The description below presupposes that you are creating the file from scratch.)
Paste the following into the file:
<?xml version="1.0" encoding="UTF-8"?> <manifest> </manifest>
The device repository¶
Your sources must now be entered into the manifest. Start with your device repository. Between the <manifest> and </manifest> tags, create the line below, making sure to replace the information inside the square brackets with your own:
<project path="device/[manufacturer]/[device]" name="[repository name]" remote="[remote]" revision="[revision]" />
‘path’ specifies the target path (subdirectory of your BUILDDIR) where the source code from repository ‘name’, which is found at ‘remote’, will be placed. The repository may contain a number of branches and it is important to secure the correct branch with ‘revision=’
The revision attribute may be omitted if the default revision for this remote is the one that you wish to use.
If you are unsure of your remote, refer to Remotes.
Now create more lines like the previous one, using the
cm.dependencies) file you found earlier in your device repository. This file lists all the remaining repositories needed to build for your selected device. Create one line for each entry in this file, using the following template:
<project path="[target_path]" name="[repository]" remote="[remote]" revision="[revision]" />
The target path is found in the repository’s name. The preceding “android” or “proprietary” is omitted and underscores are replaced with slashes. For example,
android_device_lge_bullhead goes in
Vendor blobs go in the
vendor/ folder of your
The first place to search for your device’s vendor blobs is in ‘TheMuppets’ GitHub organization. Enter your device’s codename into the search field and see if you get a match. If you are unable to find your device in TheMuppets, you will need to search elsewhere.
It may also be possible to extract the vendor blobs from the device itself by following instructions for your device on the LineageOS wiki as applicable.
A remote entry specifies the name, location (fetch) prefix, code review server, and default revision (branch/tag) for the source.
You can create a remote by adding a remote tag to your manifest as shown in the following example:
<remote name="aosp" fetch="https://android.googlesource.com" review="android-review.googlesource.com" revision="refs/tags/android-7.1.1_r25" />
Only the name, fetch, and revision attributes are required. The review attribute specifies a Gerrit Code Review server, which probably won’t be useful for initial porting purposes.
For example, let’s say that you have a bunch of repositories at https://github.com/SomeUserName/ and your desired branch name is los-14.1 in each. You would create a remote as follows and place it into your local manifest:
<remote name="sun" fetch="https://github.com/SomeUserName" revision="los-14.1" />
There are also some remotes available to you by default, though they differ between Halium versions. The following tables will help you identify these. See more information on these remotes can be found at the top of the file
The following remotes are available by default in Halium 7.1:
Remote Description, URL
Android Open Source Project, https://android.googlesource.com
Halium (link to GitHub root for legacy reasons), http://github.com
TheMuppets (for some xiaomi vendor repos) https://gitlab.com/the-muppets