Name | Last modified | Size | License | |
---|---|---|---|---|
Parent Directory | ||||
MANIFEST | 12-Jan-2018 07:11 | 240 | open | |
MD5SUMS | 12-Jan-2018 07:11 | 0 | open | |
boot.img | 12-Jan-2018 07:11 | 4.4M | open | |
lava-job-info | 12-Jan-2018 07:11 | 74 | open | |
linaro_android_build_cmds.sh | 12-Jan-2018 07:11 | 6.7K | open | |
pinned-manifest.xml | 12-Jan-2018 07:11 | 51.6K | open | |
ramdisk-recovery.img | 12-Jan-2018 07:11 | 1010.6K | open | |
ramdisk.img | 12-Jan-2018 07:11 | 447.1K | open | |
recovery.img | 12-Jan-2018 07:11 | 4.9M | open | |
source-manifest.xml | 12-Jan-2018 07:11 | 64.3K | open | |
system.img | 26-Feb-2018 16:12 | 363.7M | open | |
userdata.img | 26-Feb-2018 16:12 | 135.5M | open |
Linaro releases monthly binary Android images for the Galaxy Nexus platform.
About the Android Nexus Release
This release includes Linaro Android Jelly Bean (4.2.2), and boots on the Galaxy Nexus. Sources are also made available so you can build your own images. The 13.05 release is built with 4.8 toolchain. The release also includes optimized memory routines from the Toolchain Working Group. Please report bugs if any regressions are observed.
Where To Find More Information
More information on Linaro can be found on our website.
Feedback and Support
Subscribe to the important Linaro mailing lists and join our IRC channels to stay on top of Linaro development.
- Linaro Android Development mailing list
- Linaro Android IRC channel on irc.freenode.net at
#linaro-android
- Bug reports should be filed in Launchpad against the individual packages that are affected. If a suitable package cannot be identified, feel free to assign them to Linaro Android project.
- Questions? ask Linaro.
- Interested in commercial support? inquire at Linaro support
Fixed in this release
None listed.
Known issues
None listed.
Get artifacts
Scroll down to the ‘Downloads’ section
Click on each link to download:
- boot.img
- system.img
- userdata.img
Get merge-gnexus-blobs script
The script is available from:
or from git:
$ git clone git://android.git.linaro.org/device/samsung/tuna.git $ cd tuna $ git checkout -b linaro_android_4.2.2 origin/linaro_android_4.2.2
Make sure your computer is connected to the Internet, since the script downloads non-free binaries and tools to extract images.
Run merge-gnexus-blobs script, giving the directory containing the .img files as its sole argument.
The script will do the remaining bits for you, including flashing the phone.
WARNING There is no guarantee whatsoever that the build will work. If it breaks your phone, you get to keep both pieces.
Install Google Apps
If you wish to use the phone as a real phone rather than a pure development device, chances are that you want to install the Google Apps on it:
- Install the Linaro Android build as described above
- Grab the current Google Apps zip for JellyBean from http://goo.im/gapps . At the time of the writing, the current version is: gapps-jb-20120726-signed.zip
- If you downloaded from a device other than your Galaxy Nexus, transfer the file to your Galaxy Nexus using: mtp-sendfile gapps-jb*.zip 8
- Turn your Galaxy Nexus off completely (remove the battery if in doubt)
- Hold down the Volume Up and Volume Down buttons at the same time, and turn on the phone
- Use the Volume Up button to select “Recovery mode”, then press the power button to launch it. Wait for recovery to come up.
- Select “install zip from sdcard”
- Select “choose zip from sdcard”
- Choose the gapps-jb zip file you downloaded earlier (it should be in the Download/ folder)
- Select “Yes – Install gapps-jb-*-signed.zip”
- Select “+++++Go Back+++++”
- Select “reboot system now”
- Enjoy your Google Apps enabled Linaro Android build!
Instructions for https://android-build.linaro.org/builds/~linaro-android/
Get artifacts
Scroll down to the ‘Downloads’ section
Save linaro_android_build_cmds.sh to where you’d like to make your build.
Run the build script
The linaro_android_build_cmds.sh script will download the source and create the build.
$ chmod +x linaro_android_build_cmds.sh $ ./linaro_android_build_cmds.sh -h #To print the script usage
Most commonly used build options:
$ ./linaro_android_build_cmds.sh -t #To build from the tip of the branch without overlay $ ./linaro_android_build_cmds.sh -t -o <overlay> #To build from the tip of the branch with provided overlay $ ./linaro_android_build_cmds.sh -m <pinned_manifest> -o <overlay> #To reproduce an exact build from pinned manifest $ ./linaro_android_build_cmds.sh -t -l <login-id> #Provide login/access ID to clone and build code from linaro-private repositories
Get linaro image tools
Run these commands to get all the dependencies for linaro-image-tools and the tip of linaro-image-tools
$ sudo add-apt-repository ppa:linaro-maintainers/tools $ sudo apt-get update $ sudo apt-get install linaro-image-toolsIf you’re using a released build (with a -release or from releases.linaro.org), skip this step. If you’re using a “tip” build do not skip the step and do the following: $ sudo apt-get install bzr $ bzr branch lp:linaro-image-tools
Create media (SD card)
Disable automount (instructions provided for Gnome)
$ TMP1=$(dconf read /org/gnome/desktop/media-handling/automount) $ TMP2=$(dconf read /org/gnome/desktop/media-handling/automount-open) $ dconf write /org/gnome/desktop/media-handling/automount false $ dconf write /org/gnome/desktop/media-handling/automount-open false
Insert an SD card
Run ‘dmesg’
$ dmesg
Look for a line that looks like the following at the end of the log
[288582.790722] sdc: sdc1 sdc2 sdc3 sdc4 < sdc5 sdc6 >
WARNING In the next step, make sure you use /dev/“whatever you see above”.
You can erase your hard drive with the wrong parameter.
Run linaro image tools
$ linaro-android-media-create --mmc /dev/sdc --dev <BOARD> --boot out/target/product/<BOARD>/boot.tar.bz2 --system out/target/product/<BOARD>/system.tar.bz2 --userdata out/target/product/<BOARD>/userdata.tar.bz2
If you’re using tip of linaro image tools
$ ./linaro-image-tools/linaro-android-media-create --mmc /dev/sdc --dev <BOARD> --boot out/target/product/<BOARD>/boot.tar.bz2 --system out/target/product/<BOARD>/system.tar.bz2 --userdata out/target/product/<BOARD>/userdata.tar.bz2
Restore automount
$ dconf write /org/gnome/desktop/media-handling/automount $TMP1 $ dconf write /org/gnome/desktop/media-handling/automount-open $TMP2
Remove the SD card from the device writer and plug it into the board.
Check console output
Plug in an USB-to-serial converter and run minicom
$ minicom -D /dev/ttyUSB0 -w -C minicom.txt