Difference between revisions of "ROM Android: Compile dari source"

From OnnoWiki
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
−
Getting Started: Building a Kernel from source
 
−
- By Droidzone
 
−
What is a Kernel?
 
  
−
The operating system of a device is the part of the device responsible for basic use and administration. This includes the kernel and device drivers, boot loader, command shell or other user interface, and basic file and system utilities. Whereas the user interface is the outermost portition of the operating system, kernel is the innermost. It is the core internals, the software that provides basic services for all other parts of the system, manages hardware and distributes system resources.
+
Before we start, just thought I would mention that "$" symbolizes a new line of code. Most of this information can be found on Building the System | Android Open Source
  
−
Typical components of a kernel are interrupt handlers to service interrupt requests, a scheduler to share processor time among multiple processes, a memory management system to manage process address spaces, and system services like networking and inter-process communication. On modern systems with protected memory management units, the kernel typically resides in an elevated system state as compared to normal user applications. This includes a protected memory space and full access to hardware. This system state and memory space is collectively referred to as kernel-space. Conversely, user applications reside in user-space.
+
1) Make sure you have Ubuntu 10.04 installed on your computer.
  
−
Applications running on the system communicate with the kernel via system calls. An application typically calls functions in a library-Eg The C library–that in turn rely on the system call interface to instruct the kernel to carry out tasks on the application’s behalf.
+
2) Download the newest Android SDK for Linux here: http://developer.android.com/sdk/index.html
  
−
Our central theme is of course the Android device (a phone, or tablet or any other device), and here, Android is the Operating System. An Android Kernel is essentially a modified Linux Kernel with specific modifications to support the device architecture. I won’t bore you any further with the theoretical aspects of a kernel, and if you’re interested in knowing more about a kernel, read the book, Linux Kernel development, authored by Robert Love.
+
3) Extract the insides into /<username>/android/sdk/ (create these directories)
  
−
Without much further ado, let me jump into the topic proper, which is about how to compile an Android Kernel. For this, you’re expected to be familiar with the Linux command line, and know some basic file copying and moving commands. Though a working knowledge of Git would be beneficial, in this tutorial, I will be feeding you with the essential commands on a platter.
+
4) Open up a Terminal. Type:
 +
Code:
 +
 
 +
  $ cd android/sdk/tools
 +
 
 +
  $ ./android
 +
 
 +
5) The Android SDK Manager will now pop up, make sure you have platform-tools and Android 4.0.3 checked. Then click Install '#' packages. Make sure to Accept All then select "Install". After a few minutes, it will finish and you can close the window.
 +
 
 +
6) Go back into Terminal. Type:
 +
Code:
 +
 
 +
$ cd
 +
 
 +
$ sudo gedit .bashrc (make sure to give it your password)
 +
 
 +
7) A new window will pop-up with words you will not understand. Just make sure to scroll all the way to the bottom on a blank line and enter this: export PATH=${PATH}:~/android/sdk/platform-tools | Save and close the file.
 +
 
 +
8) Now, time to install the Java 6 JDK. Open Terminal and type everything as follows:
 +
Code:
 +
 
 +
$ sudo add-apt-repository "deb [U]http://archive.canonical.com[/U][URL="http://archive.canonical.com/"]/[/URL] lucid partner"
 +
 
 +
$ sudo apt-get update
 +
 
 +
$ sudo apt-get install sun-java6-jdk
  
−
I will describe compilation of the HTC Desire Kernel which works with Gingerbread Sense Roms. However the process applies with minor modifications to any Android Device and kernel. The specifics may be variable in how the kernel gets packaged, or flashed.
+
9) This next code will install a lot of stuff that is critical to building Android. In Terminal copy and paste all of this and then simply hit enter:
−
What you need:
+
Code:
  
−
    A Linux installation (a PC on which a linux distro is installed) or Linux box (May be a live cd or vmware like box). Any linux distro will do, but I assume an Ubuntu installation to simplify the explanation.
+
$ sudo apt-get install git-core gnupg flex bison gperf build-essential \
−
    A toolchain-Either the Android NDK, or your own toolchain
+
zip curl zlib1g-dev libc6-dev lib32ncurses5-dev ia32-libs \
−
    Android kernel source code for your device. This tutorial descibes instructions for both the Htc Desire and Samsung Galaxy Note N7100. With minor differences, the method is practically the same for any Android device.
+
x11proto-core-dev libx11-dev lib32readline5-dev lib32z-dev \
−
    Familiarity with the linux shell and basic linux commands.
+
libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \
 +
libxml2-utils xsltproc
  
−
Each step will be explained as we proceed, so if terms like “toolchain” bother you, don’t worry. It will be explained in detail later. Even if you’re a linux newbie, don’t worry. Almost all commands you need to master this tutorial will be dictated to you. Just make sure you either copy and paste the commands exactly as described here, preserving case (meaning you shouldnt type out “Cp” when the command is given as “cp”. Linux shells are case sensitive.
+
10) For this next part, we will be configuring USB Access for your Android device. Open Terminal and type:
−
Introduction to the command line for newbies:
+
Code:
  
−
As you proceed through this tutorial, you will see various commands in boxes, which may be typed out on your command shell, preserving case and spaces as they appear. As an example, the following is given:
+
$ gksu nautilus (enter your password if asked)
−
ls -l ~/android
 
−
1
 
−
 
−
ls -l ~/android
 
  
−
In this case, the code in the box is a command which should be typed out on the shell (or console).
+
11) This will open up File Browser with root abilities. Find the directory /etc/udev/rules.d/ | Create a new file called 51-android.rules and open it. It will be blank so copy and paste this:
  
−
Common mistakes include typing the following:
+
    # adb protocol on passion (Nexus One)
 +
    SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e12", MODE="0600", OWNER="<username>"
 +
    # fastboot protocol on passion (Nexus One)
 +
    SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0fff", MODE="0600", OWNER="<username>"
 +
    # adb protocol on crespo/crespo4g (Nexus S)
 +
    SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e22", MODE="0600", OWNER="<username>"
 +
    # fastboot protocol on crespo/crespo4g (Nexus S)
 +
    SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e20", MODE="0600", OWNER="<username>"
 +
    # adb protocol on stingray/wingray (Xoom)
 +
    SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="70a9", MODE="0600", OWNER="<username>"
 +
    # fastboot protocol on stingray/wingray (Xoom)
 +
    SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="708c", MODE="0600", OWNER="<username>"
 +
    # adb protocol on maguro/toro (Galaxy Nexus)
 +
    SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="<username>"
 +
    # fastboot protocol on maguro/toro (Galaxy Nexus)
 +
    SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="<username>"
 +
    # adb protocol on panda (PandaBoard)
 +
    SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d101", MODE="0600", OWNER="<username>"
 +
    # fastboot protocol on panda (PandaBoard)
 +
    SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d022", MODE="0600", OWNER="<username>"
 +
    Click to expand...
  
−
(i) LS -L ~/android
+
12) Still in the file, go to Search --> Replace. In "Search for" enter <username> (yes, include the <>). For "Replace with" enter your computer's username (the one you set up Ubuntu with). Click "Replace All" then save and exit the file.
  
−
wont work as LS and ls are different
+
13) Open Terminal once again and type:
 +
Code:
  
−
(ii) ls -l ~\android
+
$ cd
  
−
On Linux, “\” the backslash has no role on the command line (An exception is its use in regular expressions and strings, as a means of escaping characters. This won’t be described in this tutorial though, as it’s rather out of scope of our discussion). You need to use “/” or the forward slash.
+
$ mkdir bin
  
−
(iii) ls -l ~\ANDROID
+
$ sudo gedit .bashrc
  
−
won’t again work, as ANDROID and android are two different files (or directories).
+
14) In the file that pops up, scroll to the bottom and enter the following on a blank line: export PATH=${PATH}:~/bin | Save and exit the file.
  
−
Ok, now that you have a feel for what it’s like, using the linux console, let’s begin the tutorial proper.
+
15) Back in the Terminal window, type:
−
1. Getting the source code
+
Code:
  
−
At this point, you need to download the source code for your kernel. There are generally, two ways to get kernel source code:
+
$ cd bin
  
−
(a) From a compressed archive uploaded by the manufacturer of the device.
+
$ curl [URL]https://dl-ssl.google.com/dl/googlesource/git-repo/repo[/URL] > ~/bin/repo
  
−
(b) From a git repository of another developer.
+
$ chmod a+x ~/bin/repo
  
−
The tutorial will use the first method.
+
16) You just installed the repo command into the bin folder we created recently. Now we need to use that command to access the android source code. Back in the same Terminal window, type:
 +
Code:
  
−
The HTC Desire source is available from two kinds of resources-you can either get it from htcdevs.com (official HTC Dev site), or from source code uploaded from someone else. For the purpose of this tutorial, I’ll assume we’re working on the official HTC GB source code. So download bravo_2.6.35_gb-mr.tar.gz from htcdevs.com.
+
$ cd ~/android
  
−
In case, you’re working on a Samsung kernel, you can get your source code here.
+
$ mkdir source
  
−
In many cases, you may find it much easier to reuse another developer’s source code. For this, visit their XDA kernel thread, and search for instructions regarding where they’ve shared their source code. As an example of this method, let’s look at developer g.lewarne‘s source code. His kernel is titled Note2Core Kernel for Galaxy Note II N7100 / N7105 (LTE), and can be found here. If you read the thread, you will see that he has shared his source code at github here. I will describe how to use this, later.
+
$ cd source
−
2. Setting up the host PC and preparing source code
 
−
2.1 Install some essential linux packages from the Linux terminal:
 
  
−
sudo apt-get install libncurses5-dev
+
$ repo init -u [URL]https://android.googlesource.com/platform/manifest[/URL] -b android-4.0.3_r1
−
1
+
 
−
 
−
sudo apt-get install libncurses5-dev
 
  
−
2.2 Extract the source code
+
17) After running the last command, it should prompt you to type in your name and e-mail address. Please enter in your REAL Gmail's name and e-mail address.
  
−
The file you downloaded is a tar archive (like a zip file), so you need to extract it to a convenient location. Let’s hit the linux shell-open a terminal window in linux (Accessories->Terminal)
+
18) This next step will take possibly anywhere from 1-4 hours depending on your computer. In your Terminal window, type:
 +
Code:
  
−
Let’s start off in our home directory:
+
$ cd
−
cd ~/
 
−
1
 
−
 
−
cd ~/
 
  
−
Now, create the directories for our kernel compilation box:
+
$ cd android/source
−
mkdir -p ~/android/kernel
 
−
1
 
−
 
−
mkdir -p ~/android/kernel
 
  
−
Now you need to copy the tar.gz file from wherever you downloaded it to, to this dir. You can use a file explorer GUI like Nautilus or Dolphin.
+
$ repo sync   
  
−
Extract the archive:
+
19) After the "repo sync" finishes, in the same Terminal window, you will want to verify the Git Tags by typing:
−
tar -xvf ~/android/kernel/bravo_2.6.35_gb-mr.tar.gz cd ~/android/kernel/bravo_2.6.35_gb-mr
+
Code:
−
1
 
−
2
 
−
 
−
tar -xvf ~/android/kernel/bravo_2.6.35_gb-mr.tar.gz
 
−
cd ~/android/kernel/bravo_2.6.35_gb-mr
 
  
−
Now we can view the extracted files within the directory: ~/android/kernel/bravo_2.6.35_gb-mr/
+
$ gpg --import (nothing will happen, that's okay)
−
2.3 Set up the toolchain
 
  
−
A toolchain is a set of programs which allow you to compile source code (any source code, not just kernels). The toolchain is specific for the processor and hardware, so we need a toolchain specific for Android and especially the Desire. If you’re a semiadvanced-pro user, you may consider compiling your own toolchain (See theGanymedes’ guide for doing so). If compilation of kernels is all that you require, fortunately for you, there is an easy way-the Android NDK – v7 (latest as of now) is available here
+
20) Copy and paste this into Terminal then click CTRL+D to enter:
  
−
Get the NDK for Linux – android-ndk-r7-linux-x86.tar.bz2
+
    -----BEGIN PGP PUBLIC KEY BLOCK-----
−
mkdir -p ~/android/ndk
+
    Version: GnuPG v1.4.2.2 (GNU/Linux)
−
1
 
−
 
−
mkdir -p ~/android/ndk
 
  
−
Now copy the NDK file to: ~/android/ndk
+
    mQGiBEnnWD4RBACt9/h4v9xnnGDou13y3dvOx6/t43LPPIxeJ8eX9WB+8LLuROSV
 +
    lFhpHawsVAcFlmi7f7jdSRF+OvtZL9ShPKdLfwBJMNkU66/TZmPewS4m782ndtw7
 +
    8tR1cXb197Ob8kOfQB3A9yk2XZ4ei4ZC3i6wVdqHLRxABdncwu5hOF9KXwCgkxMD
 +
    u4PVgChaAJzTYJ1EG+UYBIUEAJmfearb0qRAN7dEoff0FeXsEaUA6U90sEoVks0Z
 +
    wNj96SA8BL+a1OoEUUfpMhiHyLuQSftxisJxTh+2QclzDviDyaTrkANjdYY7p2cq
 +
    /HMdOY7LJlHaqtXmZxXjjtw5Uc2QG8UY8aziU3IE9nTjSwCXeJnuyvoizl9/I1S5
 +
    jU5SA/9WwIps4SC84ielIXiGWEqq6i6/sk4I9q1YemZF2XVVKnmI1F4iCMtNKsR4
 +
    MGSa1gA8s4iQbsKNWPgp7M3a51JCVCu6l/8zTpA+uUGapw4tWCp4o0dpIvDPBEa9
 +
    b/aF/ygcR8mh5hgUfpF9IpXdknOsbKCvM9lSSfRciETykZc4wrRCVGhlIEFuZHJv
 +
    aWQgT3BlbiBTb3VyY2UgUHJvamVjdCA8aW5pdGlhbC1jb250cmlidXRpb25AYW5k
 +
    cm9pZC5jb20+iGAEExECACAFAknnWD4CGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIX
 +
    gAAKCRDorT+BmrEOeNr+AJ42Xy6tEW7r3KzrJxnRX8mij9z8tgCdFfQYiHpYngkI
 +
    2t09Ed+9Bm4gmEO5Ag0ESedYRBAIAKVW1JcMBWvV/0Bo9WiByJ9WJ5swMN36/vAl
 +
    QN4mWRhfzDOk/Rosdb0csAO/l8Kz0gKQPOfObtyYjvI8JMC3rmi+LIvSUT9806Up
 +
    hisyEmmHv6U8gUb/xHLIanXGxwhYzjgeuAXVCsv+EvoPIHbY4L/KvP5x+oCJIDbk
 +
    C2b1TvVk9PryzmE4BPIQL/NtgR1oLWm/uWR9zRUFtBnE411aMAN3qnAHBBMZzKMX
 +
    LWBGWE0znfRrnczI5p49i2YZJAjyX1P2WzmScK49CV82dzLo71MnrF6fj+Udtb5+
 +
    OgTg7Cow+8PRaTkJEW5Y2JIZpnRUq0CYxAmHYX79EMKHDSThf/8AAwUIAJPWsB/M
 +
    pK+KMs/s3r6nJrnYLTfdZhtmQXimpoDMJg1zxmL8UfNUKiQZ6esoAWtDgpqt7Y7s
 +
    KZ8laHRARonte394hidZzM5nb6hQvpPjt2OlPRsyqVxw4c/KsjADtAuKW9/d8phb
 +
    N8bTyOJo856qg4oOEzKG9eeF7oaZTYBy33BTL0408sEBxiMior6b8LrZrAhkqDjA
 +
    vUXRwm/fFKgpsOysxC6xi553CxBUCH2omNV6Ka1LNMwzSp9ILz8jEGqmUtkBszwo
 +
    G1S8fXgE0Lq3cdDM/GJ4QXP/p6LiwNF99faDMTV3+2SAOGvytOX6KjKVzKOSsfJQ
 +
    hN0DlsIw8hqJc0WISQQYEQIACQUCSedYRAIbDAAKCRDorT+BmrEOeCUOAJ9qmR0l
 +
    EXzeoxcdoafxqf6gZlJZlACgkWF7wi2YLW3Oa+jv2QSTlrx4KLM=
 +
    =Wi5D
 +
    -----END PGP PUBLIC KEY BLOCK-----
 +
    Click to expand...
  
−
Whenever I say copy, you have to manually copy the file with any file manager. Nautilus comes with Ubuntu, and Dolphin with Kubuntu. You may also use the shell of course with
+
21) Go to Binaries for Nexus Phones and Flagship Devices - Google Support for Nexus Phones and Flagship Devices - Google Code and download the proper Nexus binaries, for Verizon you want to locate "Galaxy Nexus (CDMA/LTE)" and download the Graphics Component. After it finishes, open the imgtech-toro-iml74k.tgz and you will see a .sh file. Copy it and paste it into /android/source/. Do not put it in any other folders.
−
cp [sourcefile] [destination]
 
−
1
 
−
 
−
cp [sourcefile] [destination]
 
  
−
Extract it:
+
22) Locate "extract-imgtec-toro.sh" in the directory just listed and double click it. Select "Run in Terminal". Keep clicking enter until you get to the end of the License. Then type I ACCEPT and enter. You just created a new folder inside of the Android source called "vendor".
−
tar -jvxf android-ndk-r7-linux-x86.tar.bz2
 
−
1
 
−
 
−
tar -jvxf android-ndk-r7-linux-x86.tar.bz2
 
  
−
Now add the path for your toolchain to the env variable:
+
23) In your File Browser window, locate /android/source/device/samsung/toro. In "toro", you should see a file called extract-files.sh. Open this file with gedit. When it opens up, go to Search --> Replace. In "Search for" enter adb pull | In "Replace with" enter ./adb pull | Select "Replace All" then save and exit the file.
−
gedit ~/.bashrc
 
−
1
 
−
 
−
gedit ~/.bashrc
 
  
−
At the end of the file, add this line:
+
24) Back in the File Browser, locate /android/sdk/platform-tools. You should see a file called "adb". Right click it, select copy, then back into /android/source/device/samsung/toro right click and paste "adb". At this point, you will want to plug in your device and make sure USB Debugging is enabled.
  
 +
25) Open a Terminal window and type:
 
Code:
 
Code:
−
PATH=$PATH:~/android/ndk/android-ndk-r7-linux-x86/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin
 
−
1
 
−
 
−
PATH=$PATH:~/android/ndk/android-ndk-r7-linux-x86/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin
 
  
−
3. Setting up kernel parameters
+
$ cd ~/android/source/device/samsung/toro
  
−
Kernels are compiled with a program called gnu make, and use a set of configuration options specified within a file called Makefile.
+
$ ./adb devices (it should now show your device is attached)
  
−
A vital point to note is that kernels are compiled with a program called gcc (basically the gnu C compiler), and our NDK itself has its own optimized version of gcc. While compiling, we’re actually cross compiling it (meaning compiling a binary package on a system which is different from the actual system which is meant to run it- you’re compiling it on your PC while it’s actually meant to run on your Desire)
+
$ ./extract-files.sh
  
−
This means that when you compile it, you have to make sure that you compile it with the NDK’s version of gcc instead of the system version. Otherwise you end up with a kernel meant to run on your pc, duh! Specifying which gcc to use is by the CROSS_COMPILE variable. You can set it up with this command:
+
26) The last command we just entered extracted files such as CDMA/LTE radios from your phone and stuck them into the source. YOU CAN NOT BE ON A CUSTOM ROM OR THIS WILL NOT WORK. PLEASE BE ON ANDROID 4.0.2 OTA ROOTED (if you are on a custom ROM and don't feel like reverting to stock... please read the second post in this thread explaining a different way to do it)! We are now at the point where we can compile the final product.
  
 +
27) In Terminal, type:
 
Code:
 
Code:
−
CROSS_COMPILE=arm-linux-androideabi-
 
−
1
 
−
 
−
CROSS_COMPILE=arm-linux-androideabi-
 
  
−
Note the hyphen (-) at the end, and do not forget to include it! At compilation time, system will actually use this variable to find all the programs it needs. Eg: The path for gcc will become arm-linux-androideabi-gcc
+
$ cd ~/android/source
 +
 
 +
$ lunch (it will now give you options, find "full_toro-userdebug" and type the number next to it and hit enter)
 +
 
 +
$ make -j4 otapackage
 +
 
 +
28) The last command we just ran can take up to 5 hours, depending on the speed of your computer. If you have a quad-core, I recommend running make -j8 otapackage. It will take less time. After it completes, we will give it root access, and disable the automatic flashing back to stock recovery.
 +
 
 +
29) Congratulations! You just compiled your first ROM. Now we must make last minute edits to ensure success. To see your final product, locate /android/source/out/target/product/toro. There should be one .zip file in the directory. Copy and paste it to your Desktop.
 +
 
 +
30) We will now add root access. To do so, first go here to download Superuser.apk and the su binary I put together in a zip file: Galaxy Nexus Root by droseum20.zip | After downloading, open up the .zip until you see two folders, app and bin. Open "app" and you will see "Superuser.apk". Then, open your compiled ROM from your desktop. Go to System --> app. copy and paste Superuser.apk from one .zip to the other. Now go to System --> bin in both .zips. Take "su" and drag and drop it into the "bin" folder in your compiled ROM. Now it should have full root access.
 +
 
 +
31) When compiling a ROM, it will automatically stick the stock recovery in there and we want to keep ClockworkMod, so we will do as follows. First. you will want to delete the recovery folder that is in your ROM. Next, from your ROM go to /META-INF/com/google/android/ and open updater-script. From here, not only we will delete flashing the OG recovery, we will also add some next text when any users flash our ROM.
 +
 
 +
32) Now that you have the updater-script opened, Go to Search --> Search. Type in search for recovery. It will bring you to a line that says, "package_extract_dir("recovery", "/system")". Completely delete this line. If you want to give the users who flash your ROM some nice text while it is in the boring process of flashing, keep reading to 33. If you don't care and just want to finish this long process, skip to 34 (I advise reading 33 though).
 +
 
 +
33) Still in the updater-script file, scroll all the way to the top. Make a new, blank, top line. Type ui_print("and then whatever you want. At the end of each line, you must include"); If you are confused, here is an example: ui_print("This is an example"); Now, if you want to make almost a design by using multiple lines, you can do that as well.
  
−
We can compile kernels with many different options, like with ext4 support, or without; ext4 support as part of the kernel zImage (in which case it makes the kernel larger), or as a loadable module (of the form somename.ko, which is loaded at init.d/init.rc with the command insmod modulename.ko)
+
34) After you save and exit the updater-script file, you may move on to this. Here I will show you how to either have Google Apps built into your ROM, or have Google Apps and your ROM flash separately. For this section, I give full credit to @Kejar31, the creator of GummyNex. Download his Google Apps from this ROM thread over at RootzWiki: [ROM][AOSP][4.0.3][CDMA] GummyNex 0.5.0 - 01/10/12 - RootzWiki After downloading, it will come out in a .zip package. Simply drag and drop it to your desktop.
  
−
We specify the exact options we require with the help of a useful configuration program called menuconfig (which as the name suggests, is a menu for configuration of make options).
+
35) Now, you have Google Apps downloaded, but not baked inside of your ROM. To do this, we will open the GAPPS.zip file. Simply drag and drop the data folder from his GAPPS package into your ROM (not in any folder). Now, drag and drop the signed folder from one to the other. In the GAPPS pacakge, go to System, then app. Copy and paste all of them into the /System/app/ folder in your ROM. Then open the System --> etc from GAPPS and your /System/etc/. Open permissions on both, then copy and paste all the permissions from GAPPS into your ROM. Now copy and paste all the contents from /systesm/framework/ to your ROM. Open, /System/lib/ on both and once again copy and paste the contents from GAPPS into your ROM. Lastly, go to /System/Vendor/ and copy and paste the folder inside vendor (called pitpatt) into /System/vendor/ in your ROM.
  
−
An important thing to note is that as far as kernel compilation is concerned, there are a vast amount of options to setup, and unless you’re thorough with kernel compilation, you wont be able to set up the options correctly and get your kernel to boot. Fortunately for us, the kernel source already comes with a default set of parameters which can be easily set up.
+
36) Okay, now you are ready to flash the ROM onto your phone to make sure all goes well. Simply transfer the full_toro-ota-eng.<username>.zip onto your phone however you usuaully would. Flash clockworkmod recovery if you already have not, wipe data/factory reset, wipe cache, then dalvik cache, install from zip on sd card, find the ROM and click "Yes" to install. Reboot your phone and make sure everything worked as expected! Run into a problem? Just read the second post or contact me via Google Talk (droseum20@gmail.com).
  
−
Note that all make commands must be executed within the directory bravo_2.6.35_gb-mr. Let’s go there now:
 
−
cd ~/android/kernel/bravo_2.6.35_gb-mr make ARCH=arm CROSS_COMPILE=arm-linux-androideabi- bravo_defconfig
 
−
1
 
−
2
 
−
 
−
cd ~/android/kernel/bravo_2.6.35_gb-mr
 
−
make ARCH=arm CROSS_COMPILE=arm-linux-androideabi- bravo_defconfig
 
  
−
This produces a .config file (used by the menuconfig) containing essential parameters to produce a booting kernel for the Desire.
 
  
−
In case you’re not working on the HTC Desire, but a different device, you need to run the defconfig of your device. For this, you need to know the name of the script which runs defconfig. You can get the name by inspecting the names of the files in [kernel source folder]/arch/arm/configs. In fact each file located there is a renamed .config file. Eg: For the Note 2, you will find the file t0_04_defconfig. So to run a defconfig for Note2, you would type:
 
−
make ARCH=arm CROSS_COMPILE=arm-linux-androideabi- t0_04_defconfig
 
−
1
 
−
 
−
make ARCH=arm CROSS_COMPILE=arm-linux-androideabi- t0_04_defconfig
 
  
−
Note: There is a simpler way to get the basic .config file, and this is to get it from a running kernel built by someone else. You can extract the .config from a running kernel with these commands:
 
−
cd ~/android/kernel/bravo_2.6.35_gb-mr adb pull /proc/config.gz zcat config.gz &gt; .config
 
−
1
 
−
2
 
−
3
 
−
 
−
cd ~/android/kernel/bravo_2.6.35_gb-mr
 
−
adb pull /proc/config.gz
 
−
zcat config.gz &gt; .config
 
  
−
Note that not every kernel include a config.gz. Your kernel developer needs to have included this option while compiling his kernel
 
  
−
Now we can open menuconfig and add anything we need in addition:
 
−
make ARCH=arm CROSS_COMPILE=arm-linux-androideabi- menuconfig
 
−
1
 
−
 
−
make ARCH=arm CROSS_COMPILE=arm-linux-androideabi- menuconfig
 
  
−
Advanced: You can view the huge amount of options available in menuconfig, pick and choose the ones you want. As a general word of caution, in your initial compilation, you shouldnt try to modify anything. Just pick the default .config, and compile once. If it succeeds, try booting your system with the kernel, and any default modules like the Wifi module. Once you’ve confirmed that it boots without any bootloops or hangups, you should enable Wifi and confirm that it works. This two stage check is a confirmation that you can compile a default (or stock) kernel, and also successfully compile modules. Once you can, save your .config to a safe location. If you’re using a git version control system (which you should), at this stage, you could also commit your changes, and label them as “Initial commit”. Now, you can go ahead and add changes to the kernel.
 
  
−
You can add ext4 support for example.
 
−
Once you’re done choosing options, you can exit menuconfig.
 
  
−
Tip: Once you’ve done menuconfig once, and find that you’re always using ARCH=arm and the same CROSS_COMPILE prefix regularly, you can hardcode these options into the main Makefile so you can just type ‘make’ each time for compiling the kernel. Another option is to “export” the prefices before compiling.
 
  
−
Advanced: In fact, once you’ve made your first successful compile, edit your main Makefile (the Makefile that resides in the root folder of the kernel source tree), and change the CROSS_COMPILE variable to point to your toolchain. The Makefile also has a variable for ARCH, which by default is arm. Once you set both of these, you can compile by simply executing:
 
−
<span style="font-family: 'courier new', courier">make</span>
 
−
1
 
−
 
−
<span style="font-family: 'courier new', courier">make</span>
 
  
−
   
+
  Compile Android Operating System Program
−
4. Compiling it
 
  
−
This is simple. The basic command is:
+
1. Install java jdk 5
−
make -j4 ARCH=arm CROSS_COMPILE=arm-linux-androideabi-
 
−
1
 
−
 
−
make -j4 ARCH=arm CROSS_COMPILE=arm-linux-androideabi-
 
  
−
The -j4 specifies the number of jobs to execute per operation. This is typically equal to the processor cores in your system. If you’re on a VPS with a fair usage policy, you had better keep it a notch below the maximum allowable CPU load.
+
Open /etc/apt/sources.list with a text editor like gedit:
  
−
During compilation, you will see all sorts of messages, which may include warnings too. In most cases, its safe to ignore warnings. If there are errors, the compilation will stop, and you will have to fix the issues.
+
sudo gedit /etc/apt/sources.list
  
−
If you’ve modified your Makefile to include ARCH and CROSS_COMPILE variables as described in the previous section, you can compile simply by running:
+
Add the following lines to the end of the file then save it and close:
−
make
 
−
1
 
−
 
−
make
 
  
−
+
## For sun-java5-jdk
−
5. Distributing your kernel to users
 
  
−
At the end of compilation, it generates files named zImage, and various .ko files.
+
deb http://us.archive.ubuntu.com/ubuntu/ jaunty multiverse
  
−
You have to copy them from their default location to a zip file. The best way is to use my variant of koush’s Anykernel, and copy the files to it. Then, you can zip the whole folder and lo and behold-you have your flashable kernel zip which you can distribute to others.
+
deb http://us.archive.ubuntu.com/ubuntu/ jaunty-updates multiverse
  
−
You can also remove the zImage and the modules from /system/lib/modules of any kernel zip available with you, and copy over your files to it, at the correct location.
+
Update the packages lists and install sun-java5-jdk:
  
−
So, let’s say that you have extracted an existing kernel zip to the location ~/flashable, then the file structure should be like this:
+
sudo apt-get update
  
−
I’ll include my flashable zip directory along with this post. Download file kernel_flashable.tar.bz2.zip to ~/
+
sudo apt-get install sun-java5-jdk
−
(Note: I’ll include this file later)
 
−
cd ~/ tar -jvxf kernel_flashable.tar.bz2.zip
 
−
1
 
−
2
 
−
 
−
cd ~/
 
−
tar -jvxf kernel_flashable.tar.bz2.zip
 
  
−
This will create the directory structure outlined above.
 
  
−
Now after every compilation of the kernel, execute these commands from where you executed make:
+
2. Setup the environment variables for Java
−
cp arch/arm/boot/zImage ~/kernel_flashable find . -name '*ko' -exec cp '{}' ~/kernel_flashable/system/lib/modules/ \; cd ~/kernel_flashable zip -r mykernel ./
 
−
1
 
−
2
 
−
3
 
−
4
 
−
5
 
−
6
 
−
7
 
−
 
−
cp arch/arm/boot/zImage ~/kernel_flashable
 
−
 
−
find . -name '*ko' -exec cp '{}' ~/kernel_flashable/system/lib/modules/ \;
 
−
 
−
cd ~/kernel_flashable
 
−
 
−
zip -r mykernel ./
 
  
−
This will create mykernel.zip at ~/kernel_flashable. You can distribute this to your users to flash. Make sure you edit updater-script before though.
+
sudo gedit ~/.bashrc
−
6. Some kernel compilation errors:
 
  
−
Treat warnings as errors-Solved by removing the string “-Werror” from all Makefiles of the file which failed to compile. Some people had said that the real error (Array out of bounds warning) was because of gcc optimizations. But putting -O2 to -O0 didnt do a thing.
+
add the following to the end of the file:
  
−
No of jobs - ought not to exceed 50.
+
export JAVA_HOME=/usr/lib/jvm/java-1.5.0-sun
−
“warning: variable set but not used [-Wunused-but-set-variable]“-Look at KBUILD_CFLAGS in the main Makefile. Add -Wno-error=unused-but-set-variable to the existing set of flags.
 
−
Note the following from gcc manual:
 
  
−
-WerrorMake all warnings into hard errors. Source code which triggers warnings will be rejected.
+
export JRE_HOME=${JAVA_HOME}/jre
  
−
-w Inhibit all warning messages. If you’re familiar with C code and like to fix stuff, rather than ignoring potential bugs, use this only as a last resort- A ‘brahmastram’ (most powerful weapon in your time of gravest need) as the epics would say.
+
export JAVA_PATH=${JAVA_HOME}/bin:${JRE_HOME}/bin
  
−
-WerrorMake all warnings into errors.
+
export ANDROID_JAVA_HOME=${JAVA_HOME}
  
−
-Werror=Make the specified warning into an error. The specifier for a warning is appended, for example -Werror=switch turns the warnings controlled by -Wswitch into errors. This switch takes a negative form, to be used to negate -Werror for specific warnings, for example -Wno-error=switch makes -Wswitch warnings not be errors, even when -Werror is in effect. You can use the -fdiagnostics-show-option option to have each controllable warning amended with the option which controls it, to determine what to use with this option.
+
export HOME_BIN=~/bin
  
−
So what I did to suppress errors was to add:
+
export PATH=${PATH}:${JAVA_PATH}:${HOME_BIN}
−
KBUILD_CFLAGS += -w KBUILD_CFLAGS += -Wno-error=unused-but-set-variable
 
−
1
 
−
2
 
−
 
−
KBUILD_CFLAGS += -w
 
−
KBUILD_CFLAGS += -Wno-error=unused-but-set-variable
 
  
−
Though the -Wunused-but-set-variable is not a real issue in itself, it generates so much “noise” that you may miss actual make errors.
+
export CLASSPATH=.:$CLASSPATH:${JAVA_HOME}/lib:${JRE_HOME}/lib
  
−
This is the error what I was talking about:
+
close the file, and update the list with the following command:
−
drivers/net/wireless/bcm4329_204/wl_iw.c: In function 'wl_iw_set_pmksa': drivers/net/wireless/bcm4329_204/wl_iw.c:5075:5: error: array subscript is above array bounds [-Werror=array-bounds] drivers/net/wireless/bcm4329_204/wl_iw.c:5078:5: error: array subscript is above array bounds [-Werror=array-bounds]
 
−
1
 
−
2
 
−
3
 
−
 
−
drivers/net/wireless/bcm4329_204/wl_iw.c: In function 'wl_iw_set_pmksa':
 
−
drivers/net/wireless/bcm4329_204/wl_iw.c:5075:5: error: array subscript is above array bounds [-Werror=array-bounds]
 
−
drivers/net/wireless/bcm4329_204/wl_iw.c:5078:5: error: array subscript is above array bounds [-Werror=array-bounds]
 
  
−
Solution:
+
source ~/.bashrc
  
−
Edit drivers/net/wireless/bcm4329_204/Makefile
+
to check the variables, use echo command or env, for example:
  
−
Locate -Werror within DHDCFLAGS, and delete it.
+
echo $JAVA_HOME
−
DHDCFLAGS = -DLINUX -DBCMDRIVER -DBCMDONGLEHOST -DDHDTHREAD -DBCMWPA2 \ -DUNRELEASEDCHIP -Dlinux -DDHD_SDALIGN=64 -DMAX_HDR_READ=64 \ -DDHD_FIRSTREAD=64 -DDHD_GPL -DDHD_SCHED -DBDC -DTOE -DDHD_BCMEVENTS \ -DSHOW_EVENTS -DBCMSDIO -DDHD_GPL -DBCMLXSDMMC -DBCMPLATFORM_BUS \ -Wall -Wstrict-prototypes -Werror -DOOB_INTR_ONLY -DCUSTOMER_HW2 \ -DDHD_USE_STATIC_BUF -DMMC_SDIO_ABORT -DWLAN_PFN -DWLAN_PROTECT \ -DBCMWAPI_WPI \
 
−
1
 
−
2
 
−
3
 
−
4
 
−
5
 
−
6
 
−
7
 
−
 
−
DHDCFLAGS = -DLINUX -DBCMDRIVER -DBCMDONGLEHOST -DDHDTHREAD -DBCMWPA2 \
 
−
-DUNRELEASEDCHIP -Dlinux -DDHD_SDALIGN=64 -DMAX_HDR_READ=64 \
 
−
-DDHD_FIRSTREAD=64 -DDHD_GPL -DDHD_SCHED -DBDC -DTOE -DDHD_BCMEVENTS \
 
−
-DSHOW_EVENTS -DBCMSDIO -DDHD_GPL -DBCMLXSDMMC -DBCMPLATFORM_BUS \
 
−
-Wall -Wstrict-prototypes -Werror -DOOB_INTR_ONLY -DCUSTOMER_HW2 \
 
−
-DDHD_USE_STATIC_BUF -DMMC_SDIO_ABORT -DWLAN_PFN -DWLAN_PROTECT \
 
−
-DBCMWAPI_WPI \
 
  
−
This will prevent gcc from treating mere warnings as errors.
+
env
−
7. Modifying Kernel source code on the fly – Applying Kernel Patches
 
  
−
Ok, you have compiled a simple stock kernel. Now what? Would you like to add fixes/mods developed by other kernel devs? This post explains patches and how exactly to do this.
+
To alter the javadoc link to java 5 version, use the following command:
 +
cd /etc/alternatives
  
−
Patches to the kernel are applied via patch files. Patch files are simple text files generated by the linux diff program which takes two text files, compares them and writes the differences (hence called diff) to another text file which by convention has the extension .patch
+
sudo rm javadoc.1.gz
−
7.1 Example patch
 
  
−
Following is a patch containing my “Extended battery” fix with Sibere’s battfix. I’ll explain patching with this. Let’s understand the patch file. Open it up in any text editor.
+
sudo rm javadoc
−
diff -rupN -X /home/droidzone/android/kernel/exclude.opts bravo_2.6.35_gb-mr/drivers/power/ds2784_battery.c bravo_2.6.35_gb-mr.main//drivers/power/ds2784_battery.c --- bravo_2.6.35_gb-mr/drivers/power/ds2784_battery.c 2011-08-25 13:16:53.000000000 +0530 +++ bravo_2.6.35_gb-mr.main//drivers/power/ds2784_battery.c 2011-11-06 16:43:21.544317342 +0530 @@ -118,8 +118,11 @@ PS. 0 or other battery ID use the same p /* Battery ID = 1: HT-E/Formosa 1400mAh */ #define BATT_ID_A 1 #define BATT_FULL_MAH_A 1400 - #define BATT_FULL_MAH_DEFAULT 1500 +#define BATT_FULL_MAH_CAMERONSINO 2400 +#define BATT_ID_CAMERONSINO +#define BATT_TYPE 0 +
 
−
1
 
−
2
 
−
3
 
−
4
 
−
5
 
−
6
 
−
7
 
−
8
 
−
9
 
−
10
 
−
11
 
−
12
 
−
13
 
−
 
−
diff -rupN -X /home/droidzone/android/kernel/exclude.opts bravo_2.6.35_gb-mr/drivers/power/ds2784_battery.c bravo_2.6.35_gb-mr.main//drivers/power/ds2784_battery.c
 
−
--- bravo_2.6.35_gb-mr/drivers/power/ds2784_battery.c    2011-08-25 13:16:53.000000000 +0530
 
−
+++ bravo_2.6.35_gb-mr.main//drivers/power/ds2784_battery.c    2011-11-06 16:43:21.544317342 +0530
 
−
@@ -118,8 +118,11 @@ PS. 0 or other battery ID use the same p
 
−
/* Battery ID = 1: HT-E/Formosa 1400mAh */
 
−
#define BATT_ID_A                1
 
−
#define BATT_FULL_MAH_A            1400
 
−
-
 
−
#define BATT_FULL_MAH_DEFAULT    1500
 
−
+#define BATT_FULL_MAH_CAMERONSINO    2400
 
−
+#define BATT_ID_CAMERONSINO
 
−
+#define BATT_TYPE 0
 
−
+
 
  
−
Note the first line:
+
sudo ln -s /usr/lib/jvm/java-1.5.0-sun/man/man1/javadoc.1.gz javadoc.1.gz
−
diff -rupN -X /home/droidzone/android/kernel/exclude.opts bravo_2.6.35_gb-mr/drivers/power/ds2784_battery.c bravo_2.6.35_gb-mr.main//drivers/power/ds2784_battery.c
 
−
1
 
−
 
−
diff -rupN -X /home/droidzone/android/kernel/exclude.opts bravo_2.6.35_gb-mr/drivers/power/ds2784_battery.c bravo_2.6.35_gb-mr.main//drivers/power/ds2784_battery.c
 
  
−
diff -rupN basically describes the command that was used to generate this patch. The -u means that the patch file is something called a universal patch
+
sudo ln -s /usr/lib/jvm/java-1.5.0-sun/bin/javadoc javadoc
  
−
bravo_2.6.35_gb-mr/drivers/power/ds2784_battery.c was the original file, and bravo_2.6.35_gb-mr.main//drivers/power/ds2784_battery.c was the target file or file which contains the mod.
+
if something is still wrong, you can also change the javac/java link to java 5 version:
−
7.2 How to apply patch files
 
  
−
The command depends on where your current directory is. If you’re in ~/android/kernel/bravo_2.6.35_gb-mr/ and your current directory contains the directory ‘drivers’, you can apply this patch with this command:
+
sudo ln -s /usr/lib/jvm/java-1.5.0-sun/bin/javac javac
−
patch -p1&lt;extended_battfix.patch
 
−
1
 
−
 
−
patch -p1&lt;extended_battfix.patch
 
  
−
If you’re within drivers, then you have to modify the command like this:
+
sudo ln -s /usr/lib/jvm/java-1.5.0-sun/bin/java java
−
patch -p2&lt;extended_battfix.patch
 
−
1
 
−
 
−
patch -p2&lt;extended_battfix.patch
 
  
−
Hope you get the gist. Basically, as you move into the source tree, you have to increment the patch level by the number of directories you’ve moved down into. Very simple, isnt it?
+
If you install more than one java version, use can use the following command to choose the right one.
−
8. Sharing and Collaborating – Using Github and Commits
+
sudo update-alternatives --install /usr/bin/java java /usr/lib/jvm/java-1.5.0-sun/bin/java 300
  
−
Kernel compilation is a group effort (at least it ought to be). When different devs work on different parts of the code and create their own mods, development progresses. For this purpose, it is important that you share your code with other devs. The best way to do this to upload your sources to github.
+
sudo update-alternatives --install /usr/bin/javac javac /usr/lib/jvm/java-1.5.0-sun/bin/javac 300
  
−
First, create a github account.
+
sudo update-alternatives --config java
  
−
Next you can view other devs’ github sources and examine their commits. Commits are basically patches applies to the previous source uploaded. Github commits use the universal patch format and can be viewed directly, downloaded as patch files, and applied to your code. You can also choose to download the whole source tree uploaded by another dev and examine it.
+
To see the java version, use:
  
 +
java -version
  
 +
3. Install necessary tools
  
 +
sudo apt-get install git-core gnupg sun-java5-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev
  
 +
If something is wrong, you may find the following commands helpful:
  
 +
sudo apt-get install make
  
−
Tech Blog Mobile Android DIY: Compile Android ROM from Source Code
+
sudo apt-get install gcc
−
DIY: Compile Android ROM from Source Code
 
  
−
Author: Shaunak Guharay  5 Comments    Short URL: http://techli.la/H5FlVs 
+
sudo apt-get install g++
  
−
Android is the most widely used mobile operating system in the world. And the best part, it’s completely open source, which in layman terms, means that the Source Code, the actual program is available openly for everyone to download, customize and build their own ROMs.
+
sudo apt-get install libc6-dev
 +
sudo apt-get install patch
  
−
Compile Android ROM
+
sudo apt-get install texinfo
 +
sudo apt-get install zlib1g-dev
  
−
There are lots of custom Android Distributions available out there, with the popular ones being CyanogenMod ,SlimROM , Paranoid Android, AOKP , Liquid Smooth , MIUI , Xylon, Ice Cold Jelly etc.
+
sudo apt-get install valgrind
  
−
For today’s guide, we will compile CyanogenMod 10.2, the most popular Android aftermarket ROM. The procedure is 99% same for all custom ROMs out there, so this guide can be used as a reference to compile other ROMs too.
+
sudo apt-get install python2.6
−
Pre-requisites
 
  
−
    An Android Phone with readily available Kernel and Device Source, already rooted and with a custom recovery installed.
 
−
    64 bit Linux Distribution (We prefer Ubuntu).
 
−
    At Least 100GB free on your Hard Disk.
 
−
    Working knowledge of Linux Terminal Commands.
 
−
    Reasonably fast internet connection.
 
  
−
Point to note: 64 bit Linux OS is a must, and it must be a native installation, not a Virtual Machine.
+
4. Install repo ( to update android source)
−
Set Up Your Build Machine
 
  
−
1. Install the Linux OS of your choice: 64 bit version, according to the official instructions. (The guide will assume that we are running Ubuntu 13.04). Keep a partition of at least 100GB with 16GB Swap Partition.
+
cd ~ && mkdir bin
  
−
2. Install the following list of packages: Open Terminal app, and type ‘sudo apt-get install ’, press enter and it will prompt you for your password.
+
curl http://android.git.kernel.org/repo >~/bin/repo
−
Package List
 
−
1 git-core
 
−
2 gnupg
 
−
3 flex
 
−
4 bison
 
−
5 python
 
−
6 rar
 
−
7 original-awk
 
−
8 gawk
 
−
9 p7zip-full
 
−
10 gperf
 
−
11 libsdl1.2-dev
 
−
12 libesd0-dev
 
−
13 libwxgtk2.6-dev
 
−
14 squashfs-tools
 
−
15 build-essential
 
−
16 zip
 
−
17 curl
 
−
18 libncurses5-dev
 
−
19 zlib1g-dev
 
−
20 pngcrush
 
−
21 schedtool
 
−
22 libc6-dev
 
−
23 x11proto-core-dev
 
−
24 libx11-dev
 
−
25 libg11-mesa-dev
 
−
26 mingw32
 
−
27 tofrodos
 
−
28 python-markdown
 
−
29 libxml2-utils
 
−
30 g++-multilib
 
−
31 lib32z1-dev
 
−
32 ia32-libs
 
−
33 lib32ncurses5-dev
 
−
34 lib32readline-gplv2-dev
 
−
35 gcc-multilib
 
−
36 g++-multilib
 
−
37 xsltproc
 
  
−
3. Install Java JDK 1.6 for Linux 64-bit: File name should be jdk-6u##-linux-x64.bin, ## are version numbers. Move the downloaded package to your home directory. Open Terminal app and run the following set of commands:
+
chmod a+x ~/bin/repo
−
1 sudo apt-get purge openjdk-\* icedtea-\* icedtea6-\*
 
−
2 sudo mkdir –p /opt/java/64/
 
−
3 sudo cp jdk-6u##-linux-x64.bin /opt/java/64
 
−
4 sudo su –
 
−
5 cd /opt/java/64
 
−
6 chmod a+x jdk-6u##-linux-x64.bin
 
−
7 ./jdk-6u##-linux-x64.bin
 
−
8 exit
 
  
−
Now, we must add JDK Path to .bashrc
+
Then initialize repo
−
1 sudo gedit ~/.bashrc
 
  
−
Add these lines in the ending of the text file
+
mkdir android && cd android
−
1 # Java Path
 
−
2 export JAVA_HOME=/opt/java/64/jdk1.6.0_##
 
−
3 export PATH=$PATH:$JAVA_HOME/bin
 
  
−
4. Install Android SDK: Open Terminal App
+
repo init -u git://android.git.kernel.org/platform/manifest.git
−
1 cd ~
 
−
2 mkdir android && cd android
 
−
3 mkdir sdk
 
  
−
Download Android SDK from http://developer.android.com/sdk/index.html. Extract the package contents to ~/android/sdk We must add Android SDK path to .bashrc
+
During this process, you will be asked to enter your name and email.  
−
1 sudo gedit ~/.bashrc
 
  
−
Add these lines to the ending of the text file:
+
If it succeed, it will show like:
−
1 # Android SDK Path
 
−
2 export PATH=$PATH:~/android/sdk
 
−
3 export PATH=$PATH:~/android/sdk/platform-tools
 
−
4 export PATH=$PATH:~/android/sdk/tools
 
  
−
Now, install Android SDK Tools by typing
+
repo initialized in /android
−
1 android
 
  
−
5. Set up your github account and remote repo: You can skip this step if CyanogenMod supports your phone officially. Go to github.com, and make an account for yourself. For this guide, I am considering your username as ‘user’.
 
  
−
Visit ‘github.com/CyanogenMod/android’, press Fork. The remote manifest will be forked, and available in your personal repo.
+
5. Get the source
  
−
Now, go to ‘github.com/user/android’. Open the file default.xml, press Edit. Find this line:
+
Use the following cmd to get the code, it will take very very long time, so you can go and have a snap.
−
1 <project path="android" name="CyanogenMod/android" />
 
  
−
And replace this with
+
repo sync
−
1 <project path="android" name="user/android" />
 
  
−
I am considering your device’s kernel source, device source and vendor libs for Android 4.3 to be at
 
−
1 github.com/user2/kernel_source
 
−
2 github.com/user2/device_source
 
−
3 github.com/user2/device-common_source
 
−
4 github.com/user2/vendor
 
  
−
I am assuming the branch to be named ‘jb4.3’. You can find the exact name in the actual repo. Then, at the end of the file, add these lines, modifying them according to your device’s source code.
+
6. Compile android source code
−
1 <project path="kernel/your_company/your_device" name="user2/kernel_source" remote="github" revision="jb4.3" />
 
−
2 <project path="device/your_company/your_device" name="user2/device_source" remote="github" revision="jb4.3" />
 
−
3 <project path="device/your_company/your_device-common" name="user2/device-common_source" remote="github" revision="jb4.3" />
 
−
4 <project path="vendor/your_company" name="user2/vendor" remote="github" revision="jb4.3" />
 
  
−
Commit your changes. Your remote manifest is ready to be deployed.
+
You will get the output files in ~/android/out directory
  
−
6. Install Repo Command: Open Terminal and type
+
cd ~/andoird
−
1 cd ~
 
−
2 mkdir ~/bin
 
−
3 curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
 
−
4 chmod a+x ~/bin/repo
 
  
−
We must add Repo path to .bashrc
+
make
−
1 sudo gedit ~/.bashrc
 
  
−
Add this line to the end of the text file
+
well, another snap.
−
1 export PATH=$PATH:~/bin
 
  
−
7. Fetch the ROM source code: Open Terminal and type
 
−
1 mkdir ~/android/cm
 
−
2 cd ~/android/cm
 
  
−
If you needed Step 5 , then type
+
7. run img using emulator
−
1 repo init –u git://github.com/user/android.git –b cm-10.2
 
  
−
If your device supports CyanogenMod 10.2 officially, then type
+
emulator is under ~/android/out/host/linux-x86/bin,
−
1 repo init –u git://github.com/CyanogenMod/android.git –b cm-10.2
 
  
−
Now run
+
ramdisk.img, system.img and userdata.img are under ~/android/out/target/product/generic
−
1 repo sync –j16
 
  
−
Go grab a coffee, or a meal, it’s gonna take a long time. The source code is well over 10GB in size, so it will take quite some time.
+
add the following variables:
 +
export ANDROID_PRODUCT_OUT=~/android/out/target/product/generic
  
−
Fetching Source
+
ANDROID_PRODUCT_OUT_BIN=~/android/out/host/linux-x86/binexport PATH=${PATH}:${ANDROID_PRODUCT_OUT_BIN}:${ANDROID_PRODUCT_OUT};
  
−
8. Set up the Device Specific Stuff: If your device supports CyanogenMod 10.2 officially, then open Terminal and type
+
update:
−
1 cd ~/android/cm
 
−
2 . build/envsetup.sh && breakfast <device_codename>
 
  
−
It will take some time, the device source is about 3GB in size. Then, you need to have official CM10.2 installed on your phone, connect it to your PC in USB Debugging mode, and run the following commands:
+
source ~/.bashrc
−
1 adb root
 
−
2 cd ~/android/cm/device/<your_company>/<your_device>/
 
−
3 ./extract-files.sh
 
  
−
If your device does not support CyanogenMod 10.2 officially, then you got nothing to do in this step, the sources are already waiting for you.
+
then, try to use emulator to load the img
  
−
9. Download Prebuilt Stuff and set up Toolchain: Open Terminal and type
+
cd ~/android/out/target/product/generic
−
1 cd ~/android/cm/vendor/cm
 
−
2 sh ./get-prebuilts
 
  
−
Now, we must add the Toolchain PATH to ./bashrc
+
emulator -system system.img -data userdata.img -ramdisk ramdisk.img
−
1 cd ~/android/cm
 
−
2 sudo gedit ~/.bashrc
 
  
−
Add these lines to the end of the text file
+
if you see the android GUI, congratulations!
−
1 # Android Toolchain
 
−
2 export ARCH=arm
 
−
3 export CCOMPILE=$CROSS_COMPILE
 
−
4 export CROSS_COMPILE=arm-eabi-
 
−
5 export PATH=$PATH:~/android/cm/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin
 
  
−
10. Build your ROM: So, everything is all right and ready. It’s time to build the ROM. Open Terminal and type
+
8. make a rom
−
1 cd ~/android/cm
 
−
2 . build/envsetup.sh
 
−
3 brunch <device_codename>
 
  
−
Time to go take a nap. It will take a zillion years to build the ROM on an average computer. Well, that was exaggeration, but on my home PC (Core i5 2nd gen with 8GB RAM), it takes over 3 hours to build from scratch. Hopefully, there will be no errors, and the build will complete fine. You will get the output package in
+
zip -r update.zip .
−
1 ~/android/cm/out/target/product/<your_device>/cm-10.2-something-UNOFFICIAL-<your_device>.zip
 
  
−
It’s time to install your newly compiled ROM on your phone. Download Google Apps package from “www.goo.im/gapps” for the appropriate Android version. Put both those packages in your phone, and flash them in recovery mode. Voila, your own compiled ROM is now running your device.
+
sign the file (under java 6 version)
  
−
Well, so you learnt how to compile a ROM. So, now what?
+
export JAVA_HOME=/usr/lib/jvm/java-6-sun
−
Update Your Source ROM
 
  
−
To fetch new source code updates to your locally downloaded source code, open Terminal and type
+
export JRE_HOME=${JAVA_HOME}/jre
−
1 cd ~/android/cm
 
−
2 repo sync –j16
 
  
−
To build your ROM, after updating source code, open terminal and type
+
export JAVA_PATH=${JAVA_HOME}/bin:${JRE_HOME}/bin
−
1 cd ~/android/cm
 
−
2 make installclean
 
−
3 find ./out/ -name ‘build.prop’ | xargsrm
 
−
4 find ./out/ -name ‘cm_<your_device>-target_files-eng.*.zip’ | xargsrm
 
−
5 . build/envsetup.sh
 
−
6 brunch <your_device>
 
  
−
Since you are not re-building from scratch, but re-building as it is, it will take significantly less time, only about 15-30 mins in most cases. You should sync your local source every week or so, to keep your local source fresh.
+
sudo update-alternatives --config java
−
Clean Your Working Directory
 
  
−
To clean your working directory completely (read: return your source folder to stock condition), open Terminal and type the following commands.
+
java -version
−
1 cd ~/android/cm
+
If you are using java 6 now, put the autosign.jar under the folder
−
2 make installclean
 
−
3 make clobber
 
  
−
Bear in mind, that after running these commands, all your output data will be removed, so the next build will take 3-4 hours again, as everything is re-built from scratch. If your Hard Disk partition is small, say around 100GB, you should clean your working directory about once every 4 builds, or else, you will run out of Hard Disk space.
+
java -jar autosign.jar update.zip update_signed.zip
−
Speed up your build by CCACHE
 
  
−
Building a ROM takes a lot of time. But the time can be cut down by about 30-45% by using CCACHE. CCACHE stands for compiler cache, it caches the compilation output from your earlier builds, so that it can be re-used in later builds.
 
  
−
Note that CCACHE needs a lot of space on your Hard Disk for caching the content, so its recommended if and only if your Hard Disk partition is somewhere in the vicinity of 200GB or higher. To set up CCACHE, open Terminal and type:
+
Reference: http://hi.baidu.com/garnetttt/blog/item/13426d222f72b3ae4623e8f3.html
−
1 cd ~/android/cm
 
−
2 export USE_CCACHE=1
 
−
3 export CACHE_DIR=~/.ccache
 
−
4 prebuilts/misc/linux-x86/ccache/ccache –M 50G
 
  
−
You can change the maximum size allocation to CCACHE from 50GB to whatever you want, but a minimum of around 30GB should be used for good results.
 
−
Fetch Commits from Other ROMs
 
  
−
You can cherry-pick features from other ROMs source code. Say for example, I want to pick Feature A , with commit ID “12345” from repository “github.com/user/reporepo”.
 
  
−
You navigate to the package in your local source code and run these in Terminal.
 
−
1 cd ~/<path_to_reporepo_packages>
 
−
2 git fetch https://github.com/user/reporepo
 
−
3 git cherry-pick 12345
 
−
Source Code Links of Famous Android Custom ROM Distributions
 
  
−
CyanogenMod – https://github.com/CyanogenMod
 
−
SlimROM – https://github.com/SlimRoms
 
−
ParanoidAndroid – https://github.com/ParanoidAndroid
 
−
AOKP – https://github.com/AOKP
 
−
LiquidSmooth – https://github.com/liquidsmooth
 
−
Xylon ROM – https://github.com/xyaosp
 
−
Ice Cold Jelly – https://github.com/IceColdJelly
 
  
−
So, there you go guys, a simple, straightforward guide to compile virtually any Android AOSP based ROM in 10 simple steps. While my guide focuses on CyanogenMod, you can compile pretty much every AOSP ROM out there, by just modifying the repository links. Or, you can just pick features, commit them, modify stuff and create your own personalized ROM, maybe share your ROM online too?
 
  
  
Line 649: Line 414:
 
* http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source
 
* http://xda-university.com/as-a-developer/getting-started-building-a-kernel-from-source
 
* http://www.techlila.com/compile-android-rom-from-source-code/
 
* http://www.techlila.com/compile-android-rom-from-source-code/
 +
* http://forums.androidcentral.com/verizon-galaxy-nexus-rooting-roms-hacks/189699-guide-ubuntu-compiling-android-source.html
 +
* http://www.droidforums.net/threads/how-to-build-your-own-custom-rom.193651/
 +
* http://hi.baidu.com/garnetttt/blog/item/13426d222f72b3ae4623e8f3.html
 +
* http://www.cnblogs.com/linht/archive/2010/09/24/1833798.html

Latest revision as of 08:54, 10 November 2014

Before we start, just thought I would mention that "$" symbolizes a new line of code. Most of this information can be found on Building the System | Android Open Source

1) Make sure you have Ubuntu 10.04 installed on your computer.

2) Download the newest Android SDK for Linux here: http://developer.android.com/sdk/index.html

3) Extract the insides into /<username>/android/sdk/ (create these directories)

4) Open up a Terminal. Type: Code: 

 $ cd android/sdk/tools 

 $ ./android

5) The Android SDK Manager will now pop up, make sure you have platform-tools and Android 4.0.3 checked. Then click Install '#' packages. Make sure to Accept All then select "Install". After a few minutes, it will finish and you can close the window.

6) Go back into Terminal. Type: Code: 

$ cd

$ sudo gedit .bashrc (make sure to give it your password)

7) A new window will pop-up with words you will not understand. Just make sure to scroll all the way to the bottom on a blank line and enter this: export PATH=${PATH}:~/android/sdk/platform-tools | Save and close the file.

8) Now, time to install the Java 6 JDK. Open Terminal and type everything as follows: Code: 

$ sudo add-apt-repository "deb [U]http://archive.canonical.com[/U][URL="http://archive.canonical.com/"]/[/URL] lucid partner"

$ sudo apt-get update

$ sudo apt-get install sun-java6-jdk

9) This next code will install a lot of stuff that is critical to building Android. In Terminal copy and paste all of this and then simply hit enter: 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 lib32readline5-dev lib32z-dev \ libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown \ libxml2-utils xsltproc

10) For this next part, we will be configuring USB Access for your Android device. Open Terminal and type: Code: 

$ gksu nautilus (enter your password if asked)

11) This will open up File Browser with root abilities. Find the directory /etc/udev/rules.d/ | Create a new file called 51-android.rules and open it. It will be blank so copy and paste this: 

   # adb protocol on passion (Nexus One)
   SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e12", MODE="0600", OWNER="<username>"
   # fastboot protocol on passion (Nexus One)
   SUBSYSTEM=="usb", ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0fff", MODE="0600", OWNER="<username>"
   # adb protocol on crespo/crespo4g (Nexus S)
   SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e22", MODE="0600", OWNER="<username>"
   # fastboot protocol on crespo/crespo4g (Nexus S)
   SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e20", MODE="0600", OWNER="<username>"
   # adb protocol on stingray/wingray (Xoom)
   SUBSYSTEM=="usb", ATTR{idVendor}=="22b8", ATTR{idProduct}=="70a9", MODE="0600", OWNER="<username>"
   # fastboot protocol on stingray/wingray (Xoom)
   SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="708c", MODE="0600", OWNER="<username>"
   # adb protocol on maguro/toro (Galaxy Nexus)
   SUBSYSTEM=="usb", ATTR{idVendor}=="04e8", ATTR{idProduct}=="6860", MODE="0600", OWNER="<username>"
   # fastboot protocol on maguro/toro (Galaxy Nexus)
   SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", ATTR{idProduct}=="4e30", MODE="0600", OWNER="<username>"
   # adb protocol on panda (PandaBoard)
   SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d101", MODE="0600", OWNER="<username>"
   # fastboot protocol on panda (PandaBoard)
   SUBSYSTEM=="usb", ATTR{idVendor}=="0451", ATTR{idProduct}=="d022", MODE="0600", OWNER="<username>"
   Click to expand...

12) Still in the file, go to Search --> Replace. In "Search for" enter <username> (yes, include the <>). For "Replace with" enter your computer's username (the one you set up Ubuntu with). Click "Replace All" then save and exit the file.

13) Open Terminal once again and type: Code: 

$ cd

$ mkdir bin

$ sudo gedit .bashrc

14) In the file that pops up, scroll to the bottom and enter the following on a blank line: export PATH=${PATH}:~/bin | Save and exit the file.

15) Back in the Terminal window, type: Code: 

$ cd bin

$ curl [URL]https://dl-ssl.google.com/dl/googlesource/git-repo/repo[/URL] > ~/bin/repo

$ chmod a+x ~/bin/repo

16) You just installed the repo command into the bin folder we created recently. Now we need to use that command to access the android source code. Back in the same Terminal window, type: Code: 

$ cd ~/android

$ mkdir source

$ cd source

$ repo init -u [URL]https://android.googlesource.com/platform/manifest[/URL] -b android-4.0.3_r1

17) After running the last command, it should prompt you to type in your name and e-mail address. Please enter in your REAL Gmail's name and e-mail address.

18) This next step will take possibly anywhere from 1-4 hours depending on your computer. In your Terminal window, type: Code: 

$ cd

$ cd android/source

$ repo sync

19) After the "repo sync" finishes, in the same Terminal window, you will want to verify the Git Tags by typing: Code: 

$ gpg --import (nothing will happen, that's okay)

20) Copy and paste this into Terminal then click CTRL+D to enter: 

   -----BEGIN PGP PUBLIC KEY BLOCK-----
   Version: GnuPG v1.4.2.2 (GNU/Linux)

   mQGiBEnnWD4RBACt9/h4v9xnnGDou13y3dvOx6/t43LPPIxeJ8eX9WB+8LLuROSV
   lFhpHawsVAcFlmi7f7jdSRF+OvtZL9ShPKdLfwBJMNkU66/TZmPewS4m782ndtw7
   8tR1cXb197Ob8kOfQB3A9yk2XZ4ei4ZC3i6wVdqHLRxABdncwu5hOF9KXwCgkxMD
   u4PVgChaAJzTYJ1EG+UYBIUEAJmfearb0qRAN7dEoff0FeXsEaUA6U90sEoVks0Z
   wNj96SA8BL+a1OoEUUfpMhiHyLuQSftxisJxTh+2QclzDviDyaTrkANjdYY7p2cq
   /HMdOY7LJlHaqtXmZxXjjtw5Uc2QG8UY8aziU3IE9nTjSwCXeJnuyvoizl9/I1S5
   jU5SA/9WwIps4SC84ielIXiGWEqq6i6/sk4I9q1YemZF2XVVKnmI1F4iCMtNKsR4
   MGSa1gA8s4iQbsKNWPgp7M3a51JCVCu6l/8zTpA+uUGapw4tWCp4o0dpIvDPBEa9
   b/aF/ygcR8mh5hgUfpF9IpXdknOsbKCvM9lSSfRciETykZc4wrRCVGhlIEFuZHJv
   aWQgT3BlbiBTb3VyY2UgUHJvamVjdCA8aW5pdGlhbC1jb250cmlidXRpb25AYW5k
   cm9pZC5jb20+iGAEExECACAFAknnWD4CGwMGCwkIBwMCBBUCCAMEFgIDAQIeAQIX
   gAAKCRDorT+BmrEOeNr+AJ42Xy6tEW7r3KzrJxnRX8mij9z8tgCdFfQYiHpYngkI
   2t09Ed+9Bm4gmEO5Ag0ESedYRBAIAKVW1JcMBWvV/0Bo9WiByJ9WJ5swMN36/vAl
   QN4mWRhfzDOk/Rosdb0csAO/l8Kz0gKQPOfObtyYjvI8JMC3rmi+LIvSUT9806Up
   hisyEmmHv6U8gUb/xHLIanXGxwhYzjgeuAXVCsv+EvoPIHbY4L/KvP5x+oCJIDbk
   C2b1TvVk9PryzmE4BPIQL/NtgR1oLWm/uWR9zRUFtBnE411aMAN3qnAHBBMZzKMX
   LWBGWE0znfRrnczI5p49i2YZJAjyX1P2WzmScK49CV82dzLo71MnrF6fj+Udtb5+
   OgTg7Cow+8PRaTkJEW5Y2JIZpnRUq0CYxAmHYX79EMKHDSThf/8AAwUIAJPWsB/M
   pK+KMs/s3r6nJrnYLTfdZhtmQXimpoDMJg1zxmL8UfNUKiQZ6esoAWtDgpqt7Y7s
   KZ8laHRARonte394hidZzM5nb6hQvpPjt2OlPRsyqVxw4c/KsjADtAuKW9/d8phb
   N8bTyOJo856qg4oOEzKG9eeF7oaZTYBy33BTL0408sEBxiMior6b8LrZrAhkqDjA
   vUXRwm/fFKgpsOysxC6xi553CxBUCH2omNV6Ka1LNMwzSp9ILz8jEGqmUtkBszwo
   G1S8fXgE0Lq3cdDM/GJ4QXP/p6LiwNF99faDMTV3+2SAOGvytOX6KjKVzKOSsfJQ
   hN0DlsIw8hqJc0WISQQYEQIACQUCSedYRAIbDAAKCRDorT+BmrEOeCUOAJ9qmR0l
   EXzeoxcdoafxqf6gZlJZlACgkWF7wi2YLW3Oa+jv2QSTlrx4KLM=
   =Wi5D
   -----END PGP PUBLIC KEY BLOCK-----
   Click to expand...

21) Go to Binaries for Nexus Phones and Flagship Devices - Google Support for Nexus Phones and Flagship Devices - Google Code and download the proper Nexus binaries, for Verizon you want to locate "Galaxy Nexus (CDMA/LTE)" and download the Graphics Component. After it finishes, open the imgtech-toro-iml74k.tgz and you will see a .sh file. Copy it and paste it into /android/source/. Do not put it in any other folders.

22) Locate "extract-imgtec-toro.sh" in the directory just listed and double click it. Select "Run in Terminal". Keep clicking enter until you get to the end of the License. Then type I ACCEPT and enter. You just created a new folder inside of the Android source called "vendor".

23) In your File Browser window, locate /android/source/device/samsung/toro. In "toro", you should see a file called extract-files.sh. Open this file with gedit. When it opens up, go to Search --> Replace. In "Search for" enter adb pull | In "Replace with" enter ./adb pull | Select "Replace All" then save and exit the file.

24) Back in the File Browser, locate /android/sdk/platform-tools. You should see a file called "adb". Right click it, select copy, then back into /android/source/device/samsung/toro right click and paste "adb". At this point, you will want to plug in your device and make sure USB Debugging is enabled.

25) Open a Terminal window and type: Code:

$ cd ~/android/source/device/samsung/toro

$ ./adb devices (it should now show your device is attached)

$ ./extract-files.sh

26) The last command we just entered extracted files such as CDMA/LTE radios from your phone and stuck them into the source. YOU CAN NOT BE ON A CUSTOM ROM OR THIS WILL NOT WORK. PLEASE BE ON ANDROID 4.0.2 OTA ROOTED (if you are on a custom ROM and don't feel like reverting to stock... please read the second post in this thread explaining a different way to do it)! We are now at the point where we can compile the final product.

27) In Terminal, type: Code: 

$ cd ~/android/source

$ lunch (it will now give you options, find "full_toro-userdebug" and type the number next to it and hit enter)

$ make -j4 otapackage

28) The last command we just ran can take up to 5 hours, depending on the speed of your computer. If you have a quad-core, I recommend running make -j8 otapackage. It will take less time. After it completes, we will give it root access, and disable the automatic flashing back to stock recovery.

29) Congratulations! You just compiled your first ROM. Now we must make last minute edits to ensure success. To see your final product, locate /android/source/out/target/product/toro. There should be one .zip file in the directory. Copy and paste it to your Desktop.

30) We will now add root access. To do so, first go here to download Superuser.apk and the su binary I put together in a zip file: Galaxy Nexus Root by droseum20.zip | After downloading, open up the .zip until you see two folders, app and bin. Open "app" and you will see "Superuser.apk". Then, open your compiled ROM from your desktop. Go to System --> app. copy and paste Superuser.apk from one .zip to the other. Now go to System --> bin in both .zips. Take "su" and drag and drop it into the "bin" folder in your compiled ROM. Now it should have full root access.

31) When compiling a ROM, it will automatically stick the stock recovery in there and we want to keep ClockworkMod, so we will do as follows. First. you will want to delete the recovery folder that is in your ROM. Next, from your ROM go to /META-INF/com/google/android/ and open updater-script. From here, not only we will delete flashing the OG recovery, we will also add some next text when any users flash our ROM.

32) Now that you have the updater-script opened, Go to Search --> Search. Type in search for recovery. It will bring you to a line that says, "package_extract_dir("recovery", "/system")". Completely delete this line. If you want to give the users who flash your ROM some nice text while it is in the boring process of flashing, keep reading to 33. If you don't care and just want to finish this long process, skip to 34 (I advise reading 33 though).

33) Still in the updater-script file, scroll all the way to the top. Make a new, blank, top line. Type ui_print("and then whatever you want. At the end of each line, you must include"); If you are confused, here is an example: ui_print("This is an example"); Now, if you want to make almost a design by using multiple lines, you can do that as well.

34) After you save and exit the updater-script file, you may move on to this. Here I will show you how to either have Google Apps built into your ROM, or have Google Apps and your ROM flash separately. For this section, I give full credit to @Kejar31, the creator of GummyNex. Download his Google Apps from this ROM thread over at RootzWiki: [ROM][AOSP][4.0.3][CDMA] GummyNex 0.5.0 - 01/10/12 - RootzWiki After downloading, it will come out in a .zip package. Simply drag and drop it to your desktop.

35) Now, you have Google Apps downloaded, but not baked inside of your ROM. To do this, we will open the GAPPS.zip file. Simply drag and drop the data folder from his GAPPS package into your ROM (not in any folder). Now, drag and drop the signed folder from one to the other. In the GAPPS pacakge, go to System, then app. Copy and paste all of them into the /System/app/ folder in your ROM. Then open the System --> etc from GAPPS and your /System/etc/. Open permissions on both, then copy and paste all the permissions from GAPPS into your ROM. Now copy and paste all the contents from /systesm/framework/ to your ROM. Open, /System/lib/ on both and once again copy and paste the contents from GAPPS into your ROM. Lastly, go to /System/Vendor/ and copy and paste the folder inside vendor (called pitpatt) into /System/vendor/ in your ROM.

36) Okay, now you are ready to flash the ROM onto your phone to make sure all goes well. Simply transfer the full_toro-ota-eng.<username>.zip onto your phone however you usuaully would. Flash clockworkmod recovery if you already have not, wipe data/factory reset, wipe cache, then dalvik cache, install from zip on sd card, find the ROM and click "Yes" to install. Reboot your phone and make sure everything worked as expected! Run into a problem? Just read the second post or contact me via Google Talk (droseum20@gmail.com). 






Compile Android Operating System Program

1. Install java jdk 5

Open /etc/apt/sources.list with a text editor like gedit:

sudo gedit /etc/apt/sources.list

Add the following lines to the end of the file then save it and close:

    1. For sun-java5-jdk

deb http://us.archive.ubuntu.com/ubuntu/ jaunty multiverse 

deb http://us.archive.ubuntu.com/ubuntu/ jaunty-updates multiverse

Update the packages lists and install sun-java5-jdk:

sudo apt-get update

sudo apt-get install sun-java5-jdk


2. Setup the environment variables for Java

sudo gedit ~/.bashrc

add the following to the end of the file:

export JAVA_HOME=/usr/lib/jvm/java-1.5.0-sun

export JRE_HOME=${JAVA_HOME}/jre

export JAVA_PATH=${JAVA_HOME}/bin:${JRE_HOME}/bin

export ANDROID_JAVA_HOME=${JAVA_HOME}

export HOME_BIN=~/bin

export PATH=${PATH}:${JAVA_PATH}:${HOME_BIN}

export CLASSPATH=.:$CLASSPATH:${JAVA_HOME}/lib:${JRE_HOME}/lib

close the file, and update the list with the following command:

source ~/.bashrc

to check the variables, use echo command or env, for example:

echo $JAVA_HOME

env

To alter the javadoc link to java 5 version, use the following command: cd /etc/alternatives

sudo rm javadoc.1.gz

sudo rm javadoc

sudo ln -s /usr/lib/jvm/java-1.5.0-sun/man/man1/javadoc.1.gz javadoc.1.gz

sudo ln -s /usr/lib/jvm/java-1.5.0-sun/bin/javadoc javadoc

if something is still wrong, you can also change the javac/java link to java 5 version:

sudo ln -s /usr/lib/jvm/java-1.5.0-sun/bin/javac javac

sudo ln -s /usr/lib/jvm/java-1.5.0-sun/bin/java java

If you install more than one java version, use can use the following command to choose the right one. sudo update-alternatives --install /usr/bin/java java /usr/lib/jvm/java-1.5.0-sun/bin/java 300

sudo update-alternatives --install /usr/bin/javac javac /usr/lib/jvm/java-1.5.0-sun/bin/javac 300

sudo update-alternatives --config java

To see the java version, use:

java -version

3. Install necessary tools

sudo apt-get install git-core gnupg sun-java5-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev

If something is wrong, you may find the following commands helpful:

sudo apt-get install make

sudo apt-get install gcc

sudo apt-get install g++

sudo apt-get install libc6-dev sudo apt-get install patch

sudo apt-get install texinfo sudo apt-get install zlib1g-dev

sudo apt-get install valgrind

sudo apt-get install python2.6


4. Install repo ( to update android source)

cd ~ && mkdir bin

curl http://android.git.kernel.org/repo >~/bin/repo

chmod a+x ~/bin/repo

Then initialize repo

mkdir android && cd android

repo init -u git://android.git.kernel.org/platform/manifest.git

During this process, you will be asked to enter your name and email.

If it succeed, it will show like:

repo initialized in /android


5. Get the source

Use the following cmd to get the code, it will take very very long time, so you can go and have a snap.

repo sync


6. Compile android source code

You will get the output files in ~/android/out directory

cd ~/andoird

make

well, another snap.


7. run img using emulator

emulator is under ~/android/out/host/linux-x86/bin,

ramdisk.img, system.img and userdata.img are under ~/android/out/target/product/generic

add the following variables: export ANDROID_PRODUCT_OUT=~/android/out/target/product/generic

ANDROID_PRODUCT_OUT_BIN=~/android/out/host/linux-x86/binexport PATH=${PATH}:${ANDROID_PRODUCT_OUT_BIN}:${ANDROID_PRODUCT_OUT};

update:

source ~/.bashrc

then, try to use emulator to load the img

cd ~/android/out/target/product/generic

emulator -system system.img -data userdata.img -ramdisk ramdisk.img

if you see the android GUI, congratulations!

8. make a rom

zip -r update.zip . 

sign the file (under java 6 version)

export JAVA_HOME=/usr/lib/jvm/java-6-sun

export JRE_HOME=${JAVA_HOME}/jre

export JAVA_PATH=${JAVA_HOME}/bin:${JRE_HOME}/bin

sudo update-alternatives --config java

java -version If you are using java 6 now, put the autosign.jar under the folder

java -jar autosign.jar update.zip update_signed.zip


Reference: http://hi.baidu.com/garnetttt/blog/item/13426d222f72b3ae4623e8f3.html






Referensi

Retrieved from "https://onnocenter.or.id/wiki/index.php?title=ROM_Android:_Compile_dari_source&oldid=41268"