Open Devices

To be able to build the images that you will later flash on your device, you need to install a set of software packages and libraries which give you the tools to compile source code into binary files that can run on your device.

1. In a terminal window, enter the following commands, all at once:

   sudo apt-get install bison g++-multilib git gperf libxml2-utils make zlib1g-dev:i386 zip

Now you have the tools you need to compile and build a flashable AOSP image. Follow the steps below to learn how to do this.

In order to access and use the source code available on the Sonyxperiadev GitHub, you need to install the Repo tool that is provided by Google.

1. In a terminal window, enter the following commands to download and install Repo, and set the right access rules for it:

   mkdir ~/bin
   curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
   chmod a+x ~/bin/repo

2. Open the bashrc file included in the repo tool:

   nano ~/.bashrc

3. To set the right path for your local bin folder, paste the following code to a new line at the very bottom of the bashrc file, and then save the file using Ctrl+X:

   export PATH=~/bin:$PATH

4. Reload bash variables to include the new path:

   source ~/.bashrc

Now you have all the tools you need and can move on to initializing the AOSP code and Xperia device configurations. Learn how to do this below!

The next step is to create a folder on your computer, and then download the Android source code to it. Follow the steps below to do this.

1. In a terminal window, enter the following commands:

   mkdir ~/android
   cd ~/android
   repo init -u https://android.googlesource.com/platform/manifest -b android-6.0.1_r81

   Note: The downloaded data is around 20 GB, and for a successful build you need 100 GB free hard disk space. Depending on your Internet connection, it can take quite a long time to download the source code. When the download has finished you have the basic AOSP source code on your computer.

2. Clone the local_manifests from GitHub using the following commands:

   cd .repo
   git clone https://github.com/sonyxperiadev/local_manifests
   cd local_manifests
   git checkout m-mr1
   cd ../..

   Note: These repos include a precompiled kernel. If you want to change or improve the kernel, you can recompile a new kernel. The new kernel binary should be placed in the corresponding device repository along with new kernel modules for wireless hardware. For more information, see the page how to rebuild kernels for Xperia devices.

3. To download the code into the device repos created above, run the command:

   repo sync

Next two steps are only for the following devices:

• Xperia Tablet Z
• Xperia ZL
• Xperia Z
• Xperia Z Ultra
• Xperia Z1 Compact
• Xperia Z2 Tablet
• Xperia Z2
• Xperia Z3 Tablet Compact
• Xperia Z3 Compact
• Xperia Z3
• Xperia Z4 Tablet WiFi
• Xperia Z4 Tablet
• Xperia Z3+
• Xperia Z5 Compact
• Xperia Z5
• Xperia Z5 Premium

4. Find and download the software binaries for the device you want to use on Sony’s AOSP for Xperia devices
5. In the root of your Android code tree, unzip the software binaries file you downloaded.

In order for certain functions to work on the hardware in Xperia devices, you need to add a set of patches from the AOSP master branch. This is done by executing the following commands:

1. In a terminal window, enter:

   cd bionic
   git fetch http://android.googlesource.com/platform/bionic refs/changes/50/234150/1 && git cherry-pick FETCH_HEAD
   git fetch http://android.googlesource.com/platform/bionic refs/changes/53/236953/1 && git cherry-pick FETCH_HEAD
   git fetch http://android.googlesource.com/platform/bionic refs/changes/90/497890/1 && git cherry-pick FETCH_HEAD
   git fetch http://android.googlesource.com/platform/bionic refs/changes/95/506395/1 && git cherry-pick FETCH_HEAD
   cd ../external/libnfc-nci
   git fetch https://android.googlesource.com/platform/external/libnfc-nci refs/changes/61/170861/2 && git cherry-pick FETCH_HEAD
   cd ../toybox
   git fetch https://android.googlesource.com/platform/external/toybox refs/changes/53/265153/1 && git cherry-pick FETCH_HEAD
   cd ../../hardware/qcom/gps
   git revert --no-edit 5c7552e789e4f039bebb09b972425a6cb47fc8e8
   cd ../display
   git fetch https://android.googlesource.com/platform/hardware/qcom/display refs/changes/70/238470/1 && git cherry-pick FETCH_HEAD
   git fetch https://android.googlesource.com/platform/hardware/qcom/display refs/changes/52/265052/1 && git cherry-pick FETCH_HEAD
   git fetch https://android.googlesource.com/platform/hardware/qcom/display refs/changes/53/265053/1 && git cherry-pick FETCH_HEAD
   git fetch https://android.googlesource.com/platform/hardware/qcom/display refs/changes/92/265092/1 && git cherry-pick FETCH_HEAD
   git fetch https://android.googlesource.com/platform/hardware/qcom/display refs/changes/54/274454/1 && git cherry-pick FETCH_HEAD
   git fetch https://android.googlesource.com/platform/hardware/qcom/display refs/changes/55/274455/1 && git cherry-pick FETCH_HEAD
   cd ../audio
   git cherry-pick 582e0a5e965897ea54ecfa5fe206797dab577a45
   git cherry-pick 48e428ecccee5c585a5bcc2297ea21802861df6e
   git fetch https://android.googlesource.com/platform/hardware/qcom/audio refs/changes/10/250410/1 && git cherry-pick FETCH_HEAD
   git fetch https://android.googlesource.com/platform/hardware/qcom/audio refs/changes/13/252313/1 && git cherry-pick FETCH_HEAD
   git fetch https://android.googlesource.com/platform/hardware/qcom/audio refs/changes/84/278484/1 && git cherry-pick FETCH_HEAD
   cd ../media
   git fetch https://android.googlesource.com/platform/hardware/qcom/media refs/changes/90/258490/1 && git cherry-pick FETCH_HEAD
   cd ../keymaster
   git cherry-pick 888834f9aba0609222c6e6bbd86bd6625af28746
   git fetch https://android.googlesource.com/platform/hardware/qcom/keymaster refs/changes/70/212570/5 && git cherry-pick FETCH_HEAD
   git fetch https://android.googlesource.com/platform/hardware/qcom/keymaster refs/changes/80/212580/2 && git cherry-pick FETCH_HEAD
   git fetch https://android.googlesource.com/platform/hardware/qcom/keymaster refs/changes/61/213261/1 && git cherry-pick FETCH_HEAD
   cd ../../libhardware
   git cherry-pick 48f57ad4f470ebcb71ac10df4e5e0953a6cfacd8
   cd ../broadcom/libbt/
   git fetch https://android.googlesource.com/platform/hardware/broadcom/libbt refs/changes/17/114817/2 && git cherry-pick FETCH_HEAD
   cd ../../../system/core
   git cherry-pick 9cb3d3ccf49bf0fd484563fbf611c68789d5b8a9
   git fetch https://android.googlesource.com/platform/system/core refs/changes/92/269692/1 && git cherry-pick FETCH_HEAD
   git fetch https://android.googlesource.com/platform/system/core refs/changes/38/327438/1 && git cherry-pick FETCH_HEAD
   cd ../../packages/apps/Nfc
   git revert --no-edit 988c3fff5470a1de3a880bd07fa438cc47e283c8
   cd ../../../
   cd frameworks/base
   git fetch https://android.googlesource.com/platform/frameworks/base refs/changes/31/229331/1 && git cherry-pick FETCH_HEAD
   cd ../opt/telephony
   git fetch https://android.googlesource.com/platform/frameworks/opt/telephony refs/changes/52/268352/1 && git cherry-pick FETCH_HEAD
   cd ../../../hardware/ril
   git fetch https://android.googlesource.com/platform/hardware/ril refs/changes/11/229011/1 && git cherry-pick FETCH_HEAD
   cd ../../

Note: This information will be updated continuously for new Android versions and new devices, so you should always check the AOSP section on Developer World for the latest patches.

Now you are ready to build AOSP images that can be flashed to a device. To do this, you have to point out your specific device and then start building the images.

1. Enter the following commands:

   source build/envsetup.sh && lunch

2. When prompted, pick the number corresponding to your device in the list displayed and press enter.
3. To start the build, type:

   make –j <insert the cpu thread number of your computer>

   This step will take a long time. It may take up to several hours, so go grab a coffee or play a game while you wait. When it’s done, AOSP images that can be flashed to a device will be ready.

Before you flash the images that you built in the previous step, you must make sure your device is unlocked through Sony’s unlock boot loader service. Then you can flash the AOSP images on your device by following these steps:

1. On your device: Connect the device to your computer in Fastboot mode, by pressing volume up while inserting the USB cable. When the device is in Fastboot mode, the LED on the device will be illuminated in blue.
2. On your computer: Flash the boot, system and userdata images by entering the following commands in a terminal window:

   fastboot –S 256M flash boot out/target/product/<device>/boot.img
   fastboot –S 256M flash system out/target/product/<device>/system.img
   fastboot –S 256M flash userdata out/target/product/<device>/userdata.img

   Note: It’s not necessary to re-flash the userdata every time you flash your device, but sometimes the new software is incompatible with previous content, which might result in a device that doesn’t boot. If you experience this, try to re-flash only the userdata again.

3. Now when you disconnect your device from the computer and start it, it will be running AOSP.

Vendor image is supported by the following devices:

• Xperia X
• Xperia X Compact

1. Download the vendor image corresponding your device from List of devices and resources.
2. Unpack the vendor zip file to obtain the vendor image.

   unzip SW_binaries_for_Xperia_AOSP_M_MR1_<kernel version>_<release version>_<platform>.zip

   Note: Kernel version must match the version used when code was initialized. Release version should be equivalent to the latest downloaded image version, and platform should match your device.

3. On your device: Connect the device to your computer in Fastboot mode, by pressing volume up while inserting the USB cable. When the device is in Fastboot mode, the LED on the device will be illuminated in blue.
4. On your computer: Flash the vendor image by entering the following commands in a terminal window:

   fastboot flash oem SW_binaries_for_Xperia_AOSP_M_MR1_<kernel version>_<release version>_<platform>.img

   Note: Kernel version must match the version used when code was initialized. Release version should be equivalent to the latest downloaded image version, and platform should match your device.