{Guide} [HOW TO]Building CM11 from source for i9082/L

[k2wl]

Here are the steps to build your own kernel from source. This guide is showing you how to build your first the stock kernel on your own..... It is kick start for making things on your own way....

This guide applies to i9082/i9082L and general devices also.:laugh:

This guide assumes you have basic knowledge of linux and linux system configuration.

Prerequisites
Quote:

1. Ubuntu 13.10 / BBQLINUX (I personally use this)
2. patience...lots and lots of patience.

Here starts the fun:-

1. Installing ubuntu 13.10.

Quote:

This can be done in 3 ways and I am not gonna cover it all.
- along with windows ,i.e dual boot
- in virtualbox within windows
- as a windows application installation with "wubi" installer

For starting user i think second option, i.e installing in virtualbox is best.
here's starting tutorials
http://www.youtube.com/watch?v=tDDRFiwHujg

NOTE - you should have atleast 100 Gb partion for virtualbox.

2. Setting up building environment.

THIS ALL BELOW STEPS ARE NOT NEEDED IF YOU HAVE INSTALLED BBQLINUX, BUILDING ENVIRONMENT IS SET IN BBQLINUX BY DEFAULT. IT WORKS OUT-OF-THE-BOX.

Initializing a fresh Android Build Environment in Ubuntu 13.10 sucks, right? The instructions at the AOSP page are outdated and inaccurate. Near as I can tell, they try to have you install 2 JDKs, the first one not even being the correct link for Saucy Salamander, and the second being OpenJDK. Which might work. But I dunno about all that, I’d rather have Oracle’s official stamp when it comes to building for Android.
Currently most of the guides are up to 12.04 LTS, which is fine and dandy, but being on the cutting edge is nice too.
This guide applies to all variations of Ubuntu 13.10 Saucy Salamander 64 bit. Do not use the 32 Bit version. Also, PAY CLOSE ATTENTION when to use “sudo” and when to not. It can make things funky if you do something as root that you shouldn’t.
Much thanks goes out to Google, ProTekk, Canonical, and everyone else that I read a random paragraph here and snippet there.

First, let’s set up the correct JDK.

Many of you probably have some kind of wrong Java installed unless you’re starting with a fresh Ubuntu base, and even then maybe.

Let’s get rid of that. Copy and paste this into a Terminal window:

Code:

sudo apt-get purge openjdk-\* icedtea-\* icedtea6-\*

Follow the instructions to remove OpenJDK.

If you must keep it, it’s possible. But I’m not going to tell you how to do it here. I don’t want any chance of confusion or mistake.

Now copy and paste the following into the Terminal:

Code:

sudo add-apt-repository ppa:webupd8team/java

This will add the correct PPA to your system for updated builds of Java 6 JDK that are compatible with 13.10.

No more unrecognized Java version errors! And it will update automatically with the rest of your system.

Next, we actually need to install the package. More copy-paste:

Code:

sudo apt-get update && sudo apt-get install oracle-java6-installer

Follow the on-screen instructions. You have to Accept the Licensing Agreement to complete the install. Hopefully no human centipede clauses.

Let’s make sure the correct version of Java is activated, run the following Terminal command:

Code:

 java -version

You should see something like the following:

Code:

 java version “1.6.0_45″ Java(TM) SE Runtime Environment (build 1.6.0_45-b06) Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01, mixed mode)

Ok, back to a fresh Terminal prompt. Time for installing the guts to build stuff in Ubuntu:

Code:

sudo apt-get install git-core gnupg ccache lzop flex bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 libc6-dev lib32ncurses5 lib32z1 lib32bz2-1.0 lib32ncurses5-dev x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 lib32z-dev libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc readline-common libreadline6-dev libreadline6 lib32readline-gplv2-dev libncurses5-dev lib32readline5 lib32readline6 libreadline-dev libreadline6-dev:i386 libreadline6:i386 bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev lib32bz2-dev libsdl1.2-dev libesd0-dev squashfs-tools pngcrush schedtool libwxgtk2.8-dev python

When that is done installing, run the following command in your Terminal window:

Code:

sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so

That’s it on the package side of things.

You guessed it, time for more Terminal. This really is the easiest way, seriously. And it’s totally worth it when you’re basking in the glory of a bunch of people on XDA.

The binary for a program called “repo” will let you talk to git servers and download all that precious source code. That second part after the && allows it to be executable:

Code:

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

Use your favorite text editor to open ~/.bashrc

I like nano:

Code:

sudo nano ~/.bashrc

At the very bottom, add the following line:

Code:

 export PATH=~/bin:$PATH

Save it. In nano that would be Ctrl-O and then Enter. Then Ctrl-X to exit back to a prompt. Restart bash:

Code:

 source ~/.bashrc

That should be everything. Now you’re ready to build Android the right way. Luck!

3. Downloading source

Open terminal
To initialize your local repository using the CyanogenMod trees, use a command like this:

mkdir cm11
cd cm11
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0

Create local_manifest.xml in .repo folder.

cd .repo
nano local_manifest.xml

Paste following into the terminal

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
  <project path="device/samsung/i9082" name="pawitp/android_device_samsung_i9082" remote="github" revision="cm-11.0" />
  <project path="vendor/samsung/i9082" name="k2wl/android_vendor_samsung_i9082" remote="github" revision="master" />
  <project path="kernel/samsung/i9082" name="pawitp/android_kernel_samsung_i9082" remote="github" revision="cm-11.0" />
</manifest>

Save it. In nano that would be Ctrl-O and then Enter. Then Ctrl-X to exit back to a prompt. Restart bash.

Then to sync up:

repo sync -j#

# is number of jobs you want to give for your downloading source. I use 2.

Download gonna be huge. Approx 12-15 GB.
So its gonna take while depending upon your internet connection.
You may get errors while downloading, like

Sync exited due to fetch errors

Just restart download by

repo sync

4. Starting Building process

. build/envsetup.sh && time brunch i9082 -j#

Again # is meant for No. of CPU cores you have.


Building gonna take time, depending upon your computer configuration.
Any errors, post here.
I will try my best to solve problems .
Start building your own CM11...

Any suggestion welcome.

 

[k2wl]

reserved for future use.

 

[k2wl]

one more

 

[k2wl]

Just last in case

 

[android.zealot.fervor]

THANKS K2wl for this amazing guide.

 

[iceyhotguy]

Here starts the fun

Wow that's a really good guide.
You make building from a ROM/Kernel from source much simpler than it should be.

I just replaced my 12.04 LTS with 13.10 last night, was wondering if I shouldn't have, but if it's working good for your development, think I'll keep it for a while. And yes, building a fresh android build environment sucks

I'm new to android development, but so far the linux, java and php code seems mostly regular. Gonna start with kernel first, then maybe try my hand on building a ROM. Thank you for the guide! :good:

 

[k2wl]

Wow that's a really good guide.
You make building from a ROM/Kernel from source much simpler than it should be.

I just replaced my 12.04 LTS with 13.10 last night, was wondering if I shouldn't have, but if it's working good for your development, think I'll keep it for a while. And yes, building a fresh android build environment sucks

I'm new to android development, but so far the linux, java and php code seems mostly regular. Gonna start with kernel first, then maybe try my hand on building a ROM. Thank you for the guide! :good:

Good. Thats the spirit.
keep 13.10. its good.
i switched to BBQLINUX just few days, until earlier i was using 13.10.
kernel develpment is not much hussle.
just be sure...dont add features which make kernel unstable.
i statred with kernel development only...:good::laugh:
and then come to ROM development.
best luck..
if any queries regarding kernel or ROM development, just ask me...i am here to help.

 

[RVR]

this can be used to build other roms too right .... by just changing the github repo to the rom u wanna build

 

[black87]

One more question, how to apply patches?

 

[##W4TCH0UT##]

But, k2wl.
This method builds an Odin flashable file.
How to make flashable zips, which can be flashed through custom recoveries.????


Sent from my iPhone using Tapatalk

 

[k2wl]

this can be used to build other roms too right .... by just changing the github repo to the rom u wanna build

yes its gonna be useful to build other AOSP based roms. like PA,AOKP,OMNI,AICP etc... just need few modifications according to respective roms.

One more question, how to apply patches?

copy the patch file to respective directory and apply patch with following command.

patch -p1 < patch.diff

eg. if you want to apply bluetooth patch and ur patch name is fixbluetooth.diff
then

cd hardware/broadcom/libbt/
git checkout .
patch -p1 < fixbluetooth.diff

if any problems plz tell me..

But, k2wl.
This method builds an Odin flashable file.
How to make flashable zips, which can be flashed through custom recoveries.????


Sent from my iPhone using Tapatalk

It builds flashable zips only ......with CWM or any other....

 

[RVR]

@k2wl im getting this error http://pastebin.com/uLy1MGew

 

[##W4TCH0UT##]

@k2wl im getting this error http://pastebin.com/uLy1MGew

check slimrom's github source. instructions are given there.
also @k2wl said that you have to make some other modifications.

Did you try the breakfast command???

 

[k2wl]

@k2wl im getting this error http://pastebin.com/uLy1MGew

1. [email protected]:~/slimrom$ . build/envsetup.sh && time brunch i9082 -j4
   including device/generic/armv7-a-neon/vendorsetup.sh
   including device/generic/x86/vendorsetup.sh
   including device/generic/mips/vendorsetup.sh
   including vendor/slim/vendorsetup.sh
   including sdk/bash_completion/adb.bash
   including vendor/slim/vendorsetup.sh
   ls: cannot access device/*/i9082/slim.mk: No such file or directory
   build/core/product_config.mk:231: *** Can not locate config makefile for product "slim_i9082". Stop.
   Device i9082 not found. Attempting to retrieve device repository from SlimRoms Github (http://github.com/SlimRoms).
   Repository for i9082 not found in the SlimRoms Github repository list. If this is in error, you may need to manually add it to .repo/local_manifests/slim_manifest.xml
   ls: cannot access device/*/i9082/slim.mk: No such file or directory
   build/core/product_config.mk:231: *** Can not locate config makefile for product "slim_i9082". Stop.
   
   ** Don't have a product spec for: 'slim_i9082'
   ** Do you have the right repo manifest?
   
   No such item in brunch menu. Try 'breakfast'
   
   real 0m22.876s
   user 0m0.219s
   sys 0m0.087s

your device folder points to device named cm_i9082, not slim_i9082. thats why.
jst open cm.mk file in device/samsung/i9082 cm.mk and edit its content to slim.
means
if it says in the line cm_i9082 change it to slim_i9082.
save it.
rename the file to slim.mk

and change one more file which will point to slim.mk
i.e androidproducts.mk
change the

PRODUCT_MAKEFILES := \    $(LOCAL_DIR)/device_i9082.mk

to

PRODUCT_MAKEFILES := \    $(LOCAL_DIR)/slim.mk

after that one more file to be created.
slim.dependencies.
just rename cm.dependencies to slim.dependencies.

and then try that command again.

i am attaching files for you.
jst replace them. or edit as you like.


---------------------------------------------------------------------------------------------------------------------

good to know some one started something.
you downloaded source. thats great....keep up... i will help you as much as i can....

 

[xenon92]

@k2wl im getting this error http://pastebin.com/uLy1MGew

Or simply use i9082 device tree for SlimROMs from my Github. I have made all the necessary changes.

 

[k2wl]

Or simply use i9082 device tree for SlimROMs from my Github. I have made all the necessary changes.

yep....that will do....
but i think untill and unless he do it himself, he wont understand....

 

[RVR]

@xenon92 as k2wl is saying.. Il try on my own first otherwise I'll use ur device tree if I'm not able to do it at all... Thanx fr the reply.

Sent from my GT-I9082 using XDA Premium 4 mobile app



EDIT: ITS STARTED BUILDING ..THANX FR THE SUPPORT

 

[k2wl]

@xenon92 as k2wl is saying.. Il try on my own first otherwise I'll use ur device tree if I'm not able to do it at all... Thanx fr the reply.

Sent from my GT-I9082 using XDA Premium 4 mobile app



EDIT: ITS STARTED BUILDING ..THANX FR THE SUPPORT

thats the spirit of learning...keep up...

 

[RVR]

one more error http://pastebin.com/wcuPHsi0 ..pl help

 

[k2wl]

device/samsung/i9082/overlay/frameworks/base/core/res/res/values/config.xml


just edit this file and delete line number 34,199,205. and save it.

just restart building again.