Android source code versions
Start here to download your own Android filesystem, bootloader and kernel source code. There will be different considerations to work out depending on the device you are using and the appropriate Android release. This page will help you decide the Android release to download and use and relevant configuration details based on the device you are using.
Create the following directories:
$ cd ~/ $ mkdir bin $ mkdir mydroid
Export tool chain path:
$ export PATH=$PATH:/home/<user_name>/bin $ export MYDROID=/home/<user_name>/mydroid
For detail information regarding repo visit: Using Repo and Git
Other reference links on Git can be found in technical references page
Download repo to environment
$ cd ~/bin $ curl http://android.git.kernel.org/repo > ~/bin/repo $ chmod a+x ~/bin/repo
Source code versions
Two different versions of source code is available for the community. The "Latest Code" provide up to the minute release. This version of source code is considered unstable. "Stable Release" source code has been tested and is considered to be rather stable.
Initialize the project to use the latest manifest
$repo init -u git://git.omapzoom.org/platform/omapmanifest.git
Eclair Maintenance Releases
$repo init -u git://git.omapzoom.org/platform/omapmanifest.git -b eclair -m L25.Inc2.7.P3.Maintainance.xml
$repo init -u git://git.omapzoom.org/platform/omapmanifest.git -b froyo
Then just run:
To download a particular project, run:
$repo sync hardware/ti/omx $repo sync external/opencore $repo sync frameworks/base ...
The stable tested release version will provide a tested, verified stable point in the release. Download these versions if you want a point of known functionality. These stable versions are tested by TI test team and both test results and release notes have been produced.
All the Open Sourced code will be accessible via this method. Apart from this you can access certain HW accelerated codecs, WLAN/BT firmware for Zoom-II platform. There will be additional HW accelerated codecs, 3rd part content & features that may be available from releases obtained through TI. To obtain licenses for additional content, contact your TI representative.
Branches for Blaze/OMAP4430
L27.4rc0, branch: 8ee7e3e6b9c7442cc81c4d812e5bd88283b7ed4b L27.3p2, branch: 7a1b579f774477f33e62cf3bfb532448a32615af
To use Blaze branch
mkdir -p <your directory path>/mydroid cd <your directory path>/mydroid export MYDROID=`pwd` repo init -u git://git.omapzoom.org/platform/omapmanifest.git -b <branch> repo sync
Else to access other releases,
- obtain the correct manifest file from omapmanifest
- initialize your project with the manifest you have chosen
- obtain the source code for the release
Obtain Correct Manifest
Create a directory to store your manifest
$ cd $MYDROID $ mkdir my_manifest $ cd my_manifest
Obtain Source Code for Release
Clone manifest project and reviewing current available tags
$ git clone git://git.omapzoom.org/platform/omapmanifest.git $ cd omapmanifest $ export MANIFEST=`pwd` $ git tag
These tags specify which Android source version tags are currently available. Tag and platform specific details follow:
Example of git tag print out
RLS25.INC2.5rc2 RLS25.12RC0 RLS25.6rc4 RLS25.6rc7 RLS25.6rc8 RLS25.7rc0 RLS25.7rc1 RLS25.7rc2 . . . RLS27.3 RLS27.3p2 RLS27.3rc0 RLS27.3rc1 RLS27.4rc0 Test android-1.0
- Indicates official released software versions. These versions will have published Release Notes and Product Test results associated with them.
- For example: RLS25.6 indicates the official 25.6 release version.
- Indicate an intermediate build between official releases. These intermediate builds are called "release candidates". They should be considered unstable intermediate builds.
- They are used to provide a stable compilation point at which testing can begin between releases. The test results for these builds will not be published externally.
- For example: RLS25.7rc1 is a point used for testing between the 25.6 release and the 25.7 release.
- Indicates an officially released software versions for Blaze/OMAP4430. These versions will have published Release Notes and Product Test results associated with them.
- For example: RLS27.3 indicates the official 27.3 release version.
- Indicate official released software versions for OMAP3630. These versions will have published Release Notes and Product Test results associated with them.
- For example: RLS25.INC2.6 indicates the official 25.6inc2 release version.
- Indicate an intermediate build between official releases for OMAP3630. These intermediate builds are called "release candidates". They should be considered unstable intermediate builds. They are used to provide a stable compilation point at which testing can begin between releases. The test results for these builds will not be published externally.
- For example: RLS25.INC2.7rc1 is a point used for testing between the 25inc2.6 release and the 25inc2.7 release.
- For example: RLS25E.16 indicates an Eclair (rather than Donut) build.
Select a release git tag and use a hard reset command
$ git reset --hard RLS25.6
Initialize project based on manifest chosen
$ cd $MYDROID $ repo init -u $MANIFEST $ repo sync
This process takes around an hour.
- Note: You might see the following error when you try to initialize repo:
- Error: IOError: [Errno 2] No such file or directory: '/home/<user_name>/ mydroid/.repo/manifests/.git/HEAD'
- Following instructions may solve the above error
- $ touch ~/.gitconfig
- $ rm -rf .repo
Downloading Partial Code
If a user wants to download partial code instead of complete android source , the user can do the below steps
After "repo init" give the below command
$ repo sync <path of git repository>
Eg: If user wants latest omx code from eclair branch
$ repo init -u git://git.omapzoom.org/platform/omapmanifest.git -b eclair $ repo sync hardware/ti/omx
TI's official releases usually contain additional licensed content (including 3rd party software) in addition to the content in open source. Licensed content such as Hardware Accelerated MP3, H264 Encoder,720p Video codecs can be obtained via the official releases by license holders through TI.
Now that you have the source code downloaded, you are ready to build the bootloader, kernel or filesystem. Proceed accordingly with "Building bootloader", "Building kernel" or "Building Android filesystem" in the main page.