Downloading the source

The Android source tree is located in a Git repository hosted by Google. The Git repository includes metadata for the Android source, including changes to the source and when the changes were made. This page describes how to download the source tree for a specific Android code line.

To start with a factory image for a specific device instead of downloading the source, see Selecting a device build.

Initializing a Repo client

After installing the Repo Launcher, set up your client to access the Android source repository:

  1. Create an empty directory to hold your working files. Give it any name you like:

  2. Configure Git with your real name and email address. To use the Gerrit code-review tool, you need an email address that's connected with a registered Google account. Ensure that this is a live address where you can receive messages. The name that you provide here shows up in attributions for your code submissions.

    git config --global Your Name
    git config --global
  3. Run repo init to get the latest version of Repo with its most recent bug fixes. You must specify a URL for the manifest, which specifies where the various repositories included in the Android source are placed within your working directory.

    repo init -u

    To check out the main branch:

    repo init -u -b main

    To check out a branch other than main, specify it with -b. For a list of branches, see Source code tags and builds.

    For Python 2

    For Python 3

    If you get a "/usr/bin/env 'python' no such file or directory" error message, use one of the following solutions:

    If your Ubuntu 20.04.2 LTS is a newly installed (vs. upgraded) Linux version:

    sudo ln -s /usr/bin/python3 /usr/bin/python

    If using Git version 2.19 or greater, you can specify --partial-clone when performing repo init. This makes use of Git's partial clone capability to only download Git objects when needed, instead of downloading everything. Because using partial clones means that many operations must communicate with the server, use the following if you're a developer and you're using a network with low latency:

    repo init -u -b main --partial-clone --clone-filter=blob:limit=10M

    For Windows OS only: if you get an error message stating that symbolic links couldn't be created, causing repo initto fail, reference the GitHub Symbolic Links documentation to create these, or to enable their support. For non-administrators, see the Allowing non-administrators to create symbolic links section.

A successful initialization ends with a message stating that Repo is initialized in your working directory. Your client directory now contains a .repo directory where files such as the manifest are kept.

Downloading the Android source tree

To download the Android source tree to your working directory from the repositories as specified in the default manifest, run:

repo sync

To speed syncs, pass the -c (current branch) and -jthreadcount flags:

repo sync -c -j8

The Android source files are downloaded in your working directory under their project names.

To suppress output, pass the -q (quiet) flag. See the Repo Command Reference for all options.

Using authentication

By default, access to the Android source code is anonymous. To protect the servers against excessive use, each IP address is associated with a quota.

When sharing an IP address with other users (for example, when accessing the source repositories from beyond a NAT firewall), the quotas can trigger even for regular use patterns (for example, if many users sync new clients from the same IP address within a short period).

In that case, you can use authenticated access, which then uses a separate quota for each user, regardless of the IP address.

First, create a password with the password generator and follow the instructions on the password generator page.

Next, force authenticated access by using the manifest URI Notice how the /a/ directory prefix triggers mandatory authentication. You can convert an existing client to use mandatory authentication with the following command:

repo init -u

Troubleshooting network issues

When downloading from behind a proxy (which is common in some corporate environments), you might need to to explicitly specify the proxy for Repo to use:

export HTTP_PROXY=http://<proxy_user_id>:<proxy_password>@<proxy_server>:<proxy_port>
export HTTPS_PROXY=http://<proxy_user_id>:<proxy_password>@<proxy_server>:<proxy_port>

More rarely, Linux clients experience connectivity issues, getting stuck in the middle of downloads (typically during receiving objects). Adjusting the settings of the TCP/IP stack and using non-parallel commands can improve the situation. You must have root access to modify the TCP setting:

sudo sysctl -w net.ipv4.tcp_window_scaling=0
repo sync -j1

Using a local mirror

When using several clients, you can create a local mirror of the entire server content and sync clients from that mirror (which requires no network access).

These instructions assume that the mirror is created in /usr/local/aosp/mirror. First, create and sync the mirror itself. Notice the --mirror flag, which you can specify only when creating a new client:

mkdir -p /usr/local/aosp/mirror
cd /usr/local/aosp/mirror
repo init -u --mirror
repo sync

When the mirror is synced, you can create new clients from it. Note that you must specify an absolute path:

mkdir -p /usr/local/aosp/main
cd /usr/local/aosp/main
repo init -u /usr/local/aosp/mirror/platform/manifest.git
repo sync

Finally, to sync a client against the server, sync the mirror against the server, then the client against the mirror:

cd /usr/local/aosp/mirror
repo sync
cd /usr/local/aosp/main
repo sync

It's possible to store the mirror on a LAN server and to access it over NFS, SSH, or Git. It's also possible to store it on a removable drive and to pass that drive among users or machines.

Verifying Git tags

Load the following public key into your GnuPG key database. The key is used to sign annotated tags that represent releases.

gpg --import

Copy and paste the key below, then type EOF (Ctrl-D) to end the input and process the keys.

Version: GnuPG v1.4.2.2 (GNU/Linux)


After importing the keys, you can verify any tag with:

git tag -v TAG_NAME

Obtain proprietary binaries

AOSP can't be used from pure source code only and requires additional hardware-related proprietary libraries to run, such as for hardware graphics acceleration. See the sections below for download links and Device binaries for additional resources.

Download proprietary binaries

You can download official binaries for the supported devices running tagged AOSP release branches from Google's drivers. These binaries add access to additional hardware capabilities with non-open source code. To build the AOSP main branch, use the Binaries Preview instead. When building the main branch for a device, use the binaries for the most recent numbered release or with the most recent date.

Extract proprietary binaries

Each set of binaries comes as a self-extracting script in a compressed archive. Uncompress each archive, run the included self-extracting script from the root of the source tree, then confirm you agree to the terms of the enclosed license agreement. The binaries and their matching makefiles are installed in the vendor/ hierarchy of the source tree.

Clean up

To ensure the newly installed binaries are properly taken into account after being extracted, delete the existing output of any previous build using:

make clobber