Guide android

AOSP
chevron_right Set up
chevron_right Download
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.
Installing Repo
Repo is a tool that makes it easier to work with Git in the context of Android. For more information about Repo, see the Repo Command Reference .
To install Repo:
1. Make sure that you have a bin/ directory in your home directory and that it's included in your path:
2. Download the Repo tool and ensure that it's executable:
For version 1.25, the SHA-256 checksum for Repo is
d06f33115aea44e583c8669375b35aad39
Initializing a Repo client
After installing Repo, set up your client to access the Android source repository:
1. Create an empty directory to hold your working files. If you're using macOS, this has to be on a case-sensitive filesystem. 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 open_in_new . Make sure 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.
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.
To check out a branch other than master , specify it with -b . For a list of branches, see
Source code tags and builds.
A successful initialization ends with a message stating that Repo is initialized in your working directory. Your client directory should now contain 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:
The Android source files are located in your working directory under their project names. The initial sync operation takes an hour or more to complete. For more about repo sync and other Repo commands, see
Working with Android Code.
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.
The first step is to create a password with the password generator open_in_new and follow the instructions on the password generator page.
The second step is to force authenticated access by using the manifest URI https://android.googlesource.com/a/platform/manifest . Notice how the /a/ directory prefix triggers mandatory authentication. You can convert an existing client to use mandatory authentication with the following command:
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 that is then used by Repo:
More rarely, Linux clients experience connectivity issues, getting stuck in the middle of downloads (typically during receiving objects ). It's been reported that tweaking the settings of the TCP/IP stack and using non-parallel commands can improve the situation. You need root access to modify the TCP setting:
Using a local mirror
When using several clients, especially in situations where bandwidth is scarce, it's better to create a local mirror of the entire server content, and to sync clients from that mirror (which requires no network access). The download for a full mirror is smaller than the download of two clients, while containing more information.
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:
When the mirror is synced, you can create new clients from it. Note that it's important to specify an absolute path:
Finally, to sync a client against the server, sync the mirror against the server, then the client against the mirror:
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.
Copy and paste the key below, then type EOF (Ctrl-D ) to end the input and process the keys.
After importing the keys, you can verify any tag with:
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.
Some devices package these proprietary binaries on their /vendor partition.
Download proprietary binaries
You can download official binaries for the supported devices running tagged AOSP release branches from
Google's drivers open_in_new . These binaries add access to additional hardware capabilities with non-open source code. To build the AOSP master branch, use the Binaries Preview open_in_new instead. When building the master 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 will be 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:
Content and code samples on this page are subject to the licenses described in the Content License . Java is a registered trademark of Oracle and/or its affiliates.
Downloading the Source
mkdir ~/bin
PATH=~/bin:$PATH
curl https://storage.googlea
chmod a+x ~/bin/repo
mkdir WORKING_DIRECTORY
cd WORKING_DIRECTORY