[TUTORIAL] Setting up and Compiling JB and ICS from AOSP

Search This thread
By:
Advanced…
Sparx639

Sparx639

Senior Member
Mar 29, 2012
1,046
101
North Woodstock
enricocid said:
if you get bootanimation logo... i don't think is a kernel problem then... because it would stuck at google logo...
maybe you got a framework bootloop...
but logcat is necessary
have you tried to get logcat via adb interface using sdk?
Click to expand...
Click to collapse

Yeah, I'm not getting an output, adb detects my phone but I get waiting for device. I thought I needed to fully boot and add my computer to the list of devices that can perform adb operations. And yeah I didn't think that it was a kernel problem because I knew that if it reached the boot logo then it was a ROM problem, yet, the only mods I've made to the ROM were adding the proprietary binaries and changing the default backup transport server to Google

Sent from my Galaxy Nexus using XDA Premium 4 mobile app
 
beekay201

beekay201

Senior Member
Nov 8, 2010
5,224
1,221
Sparx639 said:
Yeah, I'm not getting an output, adb detects my phone but I get waiting for device. I thought I needed to fully boot and add my computer to the list of devices that can perform adb operations. And yeah I didn't think that it was a kernel problem because I knew that if it reached the boot logo then it was a ROM problem, yet, the only mods I've made to the ROM were adding the proprietary binaries and changing the default backup transport server to Google

Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse

Does the ROM fully boot without the custom kernel? Which gapps package do you use? Is this a custom kernel you compiled yourself? Maybe try diff the config against the default config?

a maguro sent this.
 
Last edited:
Sparx639

Sparx639

Senior Member
Mar 29, 2012
1,046
101
North Woodstock
beekay201 said:
Does the ROM fully boot without the custom kernel? Which gapps package do you use? Is this a custom kernel you compiled yourself? Maybe try diff the config against the default config?

a maguro sent this.
Click to expand...
Click to collapse

I've tried it both with gapps and without gapps, and the gapps package doesn't seem to make a difference. Its not a custom kernel, its the aosp kernel that you would get out of the compiler on your first build. As in I haven't touched any of the kernel sources yet. The ROM boots with the kernel it compiles with, but does not boot when I try a custom one. I didn't have this problem on 4.2.2 aosp and its a little weird.

Sent from my Galaxy Nexus using XDA Premium 4 mobile app
 
beekay201

beekay201

Senior Member
Nov 8, 2010
5,224
1,221
Sparx639 said:
I've tried it both with gapps and without gapps, and the gapps package doesn't seem to make a difference. Its not a custom kernel, its the aosp kernel that you would get out of the compiler on your first build. As in I haven't touched any of the kernel sources yet. The ROM boots with the kernel it compiles with, but does not boot when I try a custom one. I didn't have this problem on 4.2.2 aosp and its a little weird.

Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse

ramdisk conflicts perhaps?
 
Sparx639

Sparx639

Senior Member
Mar 29, 2012
1,046
101
North Woodstock
beekay201 said:
ramdisk conflicts perhaps?
Click to expand...
Click to collapse

When I was getting the bootloops, I tried using the stock Google kernel hoping it would boot, but it didn't only the kernel that was built with the ROM would make it boot. I'm not sure if the Google nexus kernel has a different ramdisk, but if it doesn't then thats not the problem. Maybe its because I was using the latest repo updates and the changes somehow disallowed the Google kernel from working, but I'm still testing

Sent from my Galaxy Nexus using XDA Premium 4 mobile app
 
beekay201

beekay201

Senior Member
Nov 8, 2010
5,224
1,221
Sparx639 said:
When I was getting the bootloops, I tried using the stock Google kernel hoping it would boot, but it didn't only the kernel that was built with the ROM would make it boot. I'm not sure if the Google nexus kernel has a different ramdisk, but if it doesn't then thats not the problem. Maybe its because I was using the latest repo updates and the changes somehow disallowed the Google kernel from working, but I'm still testing

Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse

Cool, report back. One more thing: on your previous post, you refered "the kernel that you get from the compiler after your first build". Actually, the kernel image you get, is the already compiled zImage, aka the kernel doesn't get compiled there, it's just a binary which will be included with the build. It would take much longer to build the Android platform, because of one component which isn't even part of the Android OS platform. ;)
 
Sparx639

Sparx639

Senior Member
Mar 29, 2012
1,046
101
North Woodstock
beekay201 said:
Cool, report back. One more thing: on your previous post, you refered "the kernel that you get from the compiler after your first build". Actually, the kernel image you get, is the already compiled zImage, aka the kernel doesn't get compiled there, it's just a binary which will be included with the build. It would take much longer to build the Android platform, because of one component which isn't even part of the Android OS platform. ;)
Click to expand...
Click to collapse

*boot.img :p so the kernels are already prebuilt? How do people mod them them?

Sent from my Galaxy Nexus using XDA Premium 4 mobile app
 
Sparx639

Sparx639

Senior Member
Mar 29, 2012
1,046
101
North Woodstock
beekay201 said:
You grab the source, make your changes and build.

a maguro sent this.
Click to expand...
Click to collapse

I see, another question, when I add koush's superuser to my build, just the app, not the integrated settings, I get an error that says there are undefined values LOGE LOGD and LOGW in the su.c and db.c files. How would I work around these? I haven't added busybox into the ROM and I'm not sure if its mandatory for it, but that's what I was suspecting. Any insight? I can't find any results on the web for it

Sent from my Galaxy Nexus using XDA Premium 4 mobile app
 
E

EnricoD

Guest
I and my friend have a problem with a Cyano successfully compiled from source
We have no probloems during compilation, and build boots up

Here is our problem:

1) I connect my device to PC:

image.png


2) Click on Connected as Media device... bla bla

image.png


3) and I open this submenu... normal :)

image.png


BUT

4) When I uncheck MTP

image.png


5) and I came back

"Connected as Media device.. bla bla" from point 1) Will disappear forever and I'm unable to connect to PC

image_2.png



Can someone give me an hint? :)
Have We miss something?

@Carlos_Manuel, I know You compile Cyanogen from sources... ;) can You help me to figure this out?


Thank You everyone

Regards,

Enrico
 
Last edited:
Carlos_Manuel

Carlos_Manuel

Senior Member
Apr 28, 2011
4,092
5,368
27
Kuressaare
enricocid said:
I and my friend have a problem with a Cyano successfully compiled from source
We have no probloems during compilation, and build boots up

Here is our problem:

1) I connect my device to PC:

image.png


2) Click on Connected as Media device... bla bla

image.png


3) and I open this submenu... normal :)

image.png


BUT

4) When I uncheck MTP

image.png


5) and I came back

"Connected as Media device.. bla bla" from point 1) Will disappear forever and I'm unable to connect to PC

image_2.png



Can someone give me an hint? :)
Have We miss something?

@Carlos_Manuel, I know You compile Cyanogen from sources... ;) can You help me to figure this out?


Thank You everyone

Regards,

Enrico
Click to expand...
Click to collapse

Hi, same thing happens here...
But you can go back to USB connection settings and then to enable MTP again and then everything is working correctly.

What seems to happen is that when you have disable both USB connection types from USB connection settings and after that you connect your Nexus to PC via USB then CM does not use either MTP or PTP and that's why you are unable to connect to PC...
 
E

EnricoD

Guest
Carlos_Manuel said:
Hi, same thing happens here...
But you can go back to USB connection settings and then to enable MTP again and then everything is working correctly.

What seems to happen is that when you have disable both USB connection types from USB connection settings and after that you connect your Nexus to PC via USB then CM does not use either MTP or PTP and that's why you are unable to connect to PC...
Click to expand...
Click to collapse

OK. :) gonna try new build soon and see what happens ;) now i'm on stock again.. thank You for quick reply, i was getting worried for nothing :)
 
beekay201

beekay201

Senior Member
Nov 8, 2010
5,224
1,221
anybody having the following issue when getting the manifest?

object 12fd10c20115046dcd2fbe468a45e566f38ffbc9
type commit
tag v1.12.7
tagger Conley Owens <cco3@android.com> 1381959964 -0700

repo 1.12.7

gpg: Signature made Wed Oct 16 22:46:04 2013 WEST using RSA key ID 692B382C
gpg: Can't check signature: No public key
error: could not verify the tag 'v1.12.7'
Click to expand...
Click to collapse

it's not on my end (i've even tried adding gpg key here, no dice - http://source.android.com/source/downloading.html)
valhalla% gpg --version
gpg (GnuPG) 2.0.22
libgcrypt 1.5.3
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Home: ~/.gnupg
Supported algorithms:
Pubkey: RSA, ELG, DSA, ?, ?
Cipher: IDEA, 3DES, CAST5, BLOWFISH, AES, AES192, AES256, TWOFISH,
CAMELLIA128, CAMELLIA192, CAMELLIA256
Hash: MD5, SHA1, RIPEMD160, SHA256, SHA384, SHA512, SHA224
Compression: Uncompressed, ZIP, ZLIB, BZIP2
Click to expand...
Click to collapse
valhalla% python --version
Python 2.7.5
Click to expand...
Click to collapse


Please, come back JBQ!

edit: cool. 4,500 posts.
 
Last edited:
  • Like
Reactions: djmatt604
R

rubikqj

Member
Nov 28, 2012
48
18
Wow, thank you for this tutorial. I thought I couldn't compile a ROM on my computer. Even though it took some time, it worked from the first try! So happy xD
 
beekay201

beekay201

Senior Member
Nov 8, 2010
5,224
1,221
Q

quantan

Senior Member
Jan 26, 2011
341
162
Hi,
I'm a newbie. I just built a custom rom successfully for gnex (4.3, AOKP based). Everything is OK except GPS. The GPS cannot lock, it cannot find my location. I know there are many issues about GPS on 4.3, but some ROMs I flashed before don't have. How do I fix this from source?

Thanks so much. Your help should be appreciated.
 
Carlos_Manuel

Carlos_Manuel

Senior Member
Apr 28, 2011
4,092
5,368
27
Kuressaare
quantan said:
Hi,
I'm a newbie. I just built a custom rom successfully for gnex (4.3, AOKP based). Everything is OK except GPS. The GPS cannot lock, it cannot find my location. I know there are many issues about GPS on 4.3, but some ROMs I flashed before don't have. How do I fix this from source?

Thanks so much. Your help should be appreciated.
Click to expand...
Click to collapse


You can try this:

Copy sirfgps.conf from JB 4.3 ROM (/system/vendor/etc/)
and place it to /*/vendor/samsung/maguro/proprietary/

Now from:
/samsung/maguro/proprietary/
Open and edit: Android.mk

Code: 
include $(CLEAR_VARS)
LOCAL_MODULE := sirfgps
LOCAL_MODULE_OWNER := samsung
LOCAL_SRC_FILES := sirfgps.conf
LOCAL_MODULE_TAGS := optional
LOCAL_MODULE_SUFFIX := .conf
LOCAL_MODULE_CLASS := SHARED_LIBRARIES
LOCAL_MODULE_PATH := $(TARGET_OUT_VENDOR)/etc
include $(BUILD_PREBUILT)

add the following lines to the Android.mk


Now check:
vendor/samsung/maguro/device-partial.mk

If it doesn't have this line:
Code: 
sirfgps \
in device-partial.mk then add that line after
Code: 
PRODUCT_PACKAGES := \
...

Build again..
 
  • Like
Reactions: quantan
You must log in or register to reply here.

Similar threads

Romanbb
  • Locked
[ROM] Android Open Kang Project - maguro - JB
Replies
15K
Views
3M
Mikey
Mikey
franciscofranco
[KERNEL] [GPL] [GN] franco.Kernel r398
Replies
45K
Views
8M
C
Ctzokas
mmuzzy
  • Locked
[ROM] [AOSP] MMuzzyROM for Toro - Jelly Bean 4.3 - JSS15J
Replies
10K
Views
2M
RW-1
RW-1
DariosF
[ROM] [GPL] [JB 4.3 JWR66Y] [Linaro gcc 4.8] ♦ PURITY ROM ♦ (Maguro) 31/10
Replies
7K
Views
1M
crisis_trustee
crisis_trustee
M
[ROM][5.0.2/LRX22G][AOSP][LINARO/OPTIMIZED] FML: Fork My Life (2015/01/08)
Replies
3K
Views
986K
ramosroger
ramosroger

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 118
    shenye
    shenye
    Quite a few people have asked about compiling ROMs from source, so here's a guide.

    This guide is directed mainly at compiling JB or ICS for the GSM Galaxy Nexus.

    It will show you how to set up the building environment really quickly with a few simple commands in the Terminal, then show you how to sync up with the repository and compile a ROM.

    http://www.freeyourandroid.com/guide/compile-ics

    It can also be done in a Virtual Machine.

    Thanks Nathan (nprussell) for the write up!



    My XDA TV Video Guide:

    http://www.youtube.com/watch?v=H_ReU-0w4IE&feature=g-u&context=G2a40714FUAAAAAAAZAA


    ---




    Here are the steps:
    (There are additional things you can do via the link above).



    ======================

    4star.png



    IMPORTANT NOTES:

    - For the purposes of this guide, you MUST be running 64-bit Ubuntu. This can be set up on a VM (it will compile if set correctly).
    - If using a VM, ensure you give it at LEAST 2gb RAM and 2xCores (it'll take 3-4 hours at best)
    - The source download is approximately 6gb.. you're going to need 25gb HD space for a single build.

    To learn how to setup a Ubuntu 64bit VM on your Windows PC, use THIS GUIDE. I recommend using 10.04.

    So... let's assume you're running Ubuntu 64 bit for the first time, and start right from the beginning.

    NOTE : You're probably better of copying and pasting these commands, as some are quite long! All commands are in RED!


    ======================


    1. Preparing your development environment

    The very first thing you're going to need to do, is ensure you're working in a root terminal. Much like when using your Android phone, you'll want the # and not the $. In order to do this, open TERMINAL, and type:

    sudo -i

    Then type in your password. From this point forward, all of the commands in this guide assume you have root priviliges (saves typing sudo *superuser do* before everything!)

    Next, we need to add a repository so that apt-get knows where to look for Java JDK:

    add-apt-repository "deb http://archive.canonical.com/ lucid partner"

    After that, you'll need to update the repository with the following command:

    apt-get update

    Now that your repository has been updated, you can proceed with installing the required packages to make building Android from source possible. The first thing you're going to need is the Java Development Kit 6:

    apt-get install sun-java6-jdk

    Followed by (and this may already be installed depending on which version of Ubuntu you went for):

    apt-get install python

    Now you're going to need Git. Git is the revision control system.

    apt-get install git-core

    Now, you're going to pull in all the required packages needed for the build process. As I have stated already, this guide is for 64 bit ONLY. Some of these will not work on 32-bit, so if you're using 32 bit, you're reading the wrong guide (sorry)!

    apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils

    IF YOU'RE USING UBUNTU 11.10, TYPE THIS COMMAND (if not, ignore this next one)

    ln -s /usr/lib/i386-linux-gnu/libX11.so.6 /usr/lib/i386-linux-gnu/libX11.so

    Congratulations; you now have all the required packages to proceed with the next step!


    ======================


    2. Installing and initialising the repo

    Now we need to download repo, add it to our path and set the permissions . Please note that if you close terminal, you'll have to do this again. Type each command on a new line, pressing enter after each:

    mkdir ~/bin
    PATH=~/bin:$PATH
    curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
    chmod a+x ~/bin/repo

    Now we need to create a directory for where our source is going to be pulled to, and change directory to it:

    mkdir ICS_SOURCE
    cd ICS_SOURCE

    Next, you'll need to initialize the repo. There are two commands below; the top one initializes the specific branch, and the bottom is the master.

    ONLY USE ONE OF THE FOLLOWING COMMANDS (recommended - TOP)

    ICS: repo init -u https://android.googlesource.com/platform/manifest -b android-4.0.4_r1
    Jellybean: repo init -u https://android.googlesource.com/platform/manifest -b android-4.1.2_r1

    OR:

    repo init -u https://android.googlesource.com/platform/manifest

    You will now be prompted to provide your name and email address. Please give it real details; that way you can use the gerrit code review tool if your email is connected with a Google account.


    ======================


    3. Downloading the source (sync)

    This is probably the most simple part, but depending on your connection speed, it could take a while. I am on 40mb download/10mb up, and it took about 25 mins. If you're on a typical DSL connection, expect to be waiting 60-120 minutes.

    repo sync


    ======================


    4. Obtaining proprietary binaries

    New for ICS, Android cannot just be compiled from source code only. It requires additional hardware-related proprietary libraries to run, specifically for graphics acceleration (and GSM/LTE).

    The binaries must first be downloaded from here

    Each set of binaries comes as a self-extracting script in a compressed archive. After uncompressing each archive, run the included self-extracting script from the root of the source tree, confirm that you agree to the terms of the enclosed license agreement, and the binaries and their matching makefiles will get installed in the vendor/ hierarchy of the source tree. For example... after extracting one of the files, you will have 'extract-imgtech-maguro.sh'. Simply run:

    sh extract-imgtech-maguro.sh

    From your ICS_Source directory.

    IMPORTANT NOTE : If you are building for the Nexus S, you will need the Nexus S binaries.


    ======================


    5. It's build time!

    If you're a JAVA developer, feel free to have a play with the source and make any changes you want to make at this stage. Be careful though, adding rubbish/old syntax code to the source (formatting is slightly different to gingerbread) will cause the build to fail.

    Assuming that you just want to get on with building ICS, set the build environment up with:

    source build/envsetup.sh

    Next, you'll need to lunch. I don't mean go and have a sandwich, I mean... select which device you're building for.

    NOTE - you can add other devices to this list PRIOR to proceeding with this step. If you're NOT building for the GNexus, go to the bottom of this guide and look at how to add devices to the list.

    As previously stated, we're going to assume you're building for the Galaxy nexus, so type:

    lunch

    You'll be presented with a number of options (full-eng, etc).
    ASlBF.png


    If you're building for the Galaxy Nexus (codename: Maguro), type:

    8

    (7 for Nexus S and 6 for Nexus S 4G)


    and hit enter. Now, we're ready to set the compile in motion, ladies and gentlemen. There's a lot of debate over the next bit. the -j part of the below command is technically not needed, but I have had MUCH more success compiling on a virtual machine with the -j1 added. Could be random... who knows...

    Anyway, to set your build in motion, you now have TWO options. The first option will output the build as img files. The second option will output a flashable .zip file. I recommend the latter if you intent to use CWM over fastboot.

    make -j1

    or

    make -j1 otapackage

    Congratulations - in a few hours, you should have a working AOSP build for the Galaxy Nexus!
    View
    8
    P
    PaulW21781
    Treken said:
    Ok, here's what I'm doing...I downloaded the aosp source tree and compile for the toro build. I created a repo in github and pushed the frameworks/base/ to it so I can make edits and compile based from those edits. A friend told me to just repo what I want to edit. So my question is, how do I implement my repo in the build when compiling but yet pull the rest of the things I didn't change from the aosp repos? Another friend told me the default.xml but I don't know where to look for that. Any help in this matter would be most appreciated.
    Click to expand...
    Click to collapse

    Are you literally making a new project and uploading to it? Or are you going to github.com/android and forking the platform_frameworks_base from there into your git and then modyfying your own fork?

    Personally, best practice is to fork projects from github.com/android into your own repo by pressing the
    repostat_forks.png
    Fork button, then clone your own repo

    Within there, you then want to add the upstream branch, eg:

    git clone git@github.com:YourUserName/platform_manifest.git
    cd platform_manifest
    git remote add upstream git://github.com/android/platform_manifest.git
    git fetch upstream
    git merge upstream/master

    (note, I use Master branch, hence upstream/master. For other branches, simply replace master for the branch)

    Same for other projects (frameworks_base) that way, to keep up to date with google's commits too, you simply go into the folder and type:

    git fetch upstream
    git merge upstream/master

    :)

    Also, fork your own copy of github.com/android/platform_manifest

    Then to pull your own repo from git instead of Androids, edit the file platform_manifest/default.xml and include the following:

    Where it says this:
    Code: 
      <remote  name="aosp"
           fetch=".."
           review="https://android-review.googlesource.com/" />
  <default revision="master"
           remote="aosp"
           sync-j="4" />

    Change it to this
    Code: 
      <remote  name="aosp"
           fetch="https://android.googlesource.com/"
           review="https://android-review.googlesource.com/" />
           
  <remote  name="gh"
           fetch="git://github.com/"
           revision="master" />

  <default revision="master"
           remote="aosp"
           sync-j="4" />

    Then to pull your own packages (for instance, your own platform_frameworks_base, do this change:

    From
    Code: 
      <project path="frameworks/base" name="platform/frameworks/base" />

    To
    Code: 
      <project path="frameworks/base" remote="gh" name="PaulW/platform_frameworks_base" />

    (Change PaulW to whatever the username of your github account is)

    Hope this helps a little!
    View
    5
    shenye
    shenye
    @sbice try this http://www.javahotchocolate.com/tutorials/setup-eclipse.html#64-bit
    View
    5
    D
    dave_t321
    Snylter said:
    Where do I find these proprietary blobs to include?
    I only have the google-supplied extract sh-scripts..
    This explains why my gps won't work..
    Click to expand...
    Click to collapse

    You've got 2 options:

    Git clone a vendor/samsung repository into your [built root]/vendor directory.

    or

    install a working 4.0.3 rom from here plug your phone into your computer and do this:

    Code: 
    cd [build root]/vendor
rm -rf samsung
rm -rf imgtec
cd [build root]/device/samsung/[maguro or toro]
./extract-files.sh

    That'll pull the proprietary files from the working build into your vendor directory. They'll all be in vendor/samsung rather than split between vendor/samsung and vendor/imgtec but they'll all be there.

    Might be a good idea to make clean before you build again after that.
    View
    4
    P
    PaulW21781
    dave_t321 said:
    Has anyone managed to build the android-4.0.1_r1.2 branch with Ubuntu 11.10?

    I know it works on the master branch and the r1 branch supposedly didn't support it but have the build tools been updated this one?

    Just wanted to check before commiting to a massive download!
    Click to expand...
    Click to collapse

    The only thing to note with 11.10, is when you install all the build libraries, one of them is incorrect (no longer available in 11.10). Instead of installing lib32readline5-dev you need to install lib32readline-dev instead.

    Code: 
    $ sudo apt-get install git-core gnupg flex bison gperf build-essential \
  zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \
  x11proto-core-dev libx11-dev lib32readline-dev lib32z-dev \
  libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
  libxml2-utils
    View

New posts