Database Info

[Guide]Make your own rom(CM9/EVERVOLV) and kernel from source code | Advanced users

I think many want to know how this stuff is actually done,so....read
Kernel Development
U need Linux or Mac OS .The End
I can confirm the below method works on Ubuntu 11.10,32 bit(or other linux distros/mac u need different packages)
1)Open terminal and download these packages(for both 32/64 bit)
Code:
apt-get install git-core gnupg sun-java6-jdk flex bison gperf libsdl-dev libesd0-dev libwxgtk2.6-dev build-essential zip curl libncurses5-dev zlib1g-dev
For 64 bit ,install more packages,otherwise leave
Code:
ia32-libs lib32z1-dev lib32ncurses5-dev gcc-multilib g++-multilib
2)Download kernel source code for pico ,which u will compile,from www.htcdev.com (if u want to compile kernel for ics/jb,use lirokoa's source code from www.github.com/lirokoa/htc_pico_kernel )
Extract the archive somewhere safe
3)Download toolchain needed to compile the kernel from www.github.com/sakindia123/android_toolchains
We'll use arm-eabi-4.4.3 for pico

Now let's assume u have correctly set up your machine
extract the sources and everything else u downloaded....then go into the top directory
Code:
cd Kernel
u enter into the root of the kernel directory with this
then type :
Code:
gedit Makefile
The Make file will open.........look out for this and change CROSS_COMPILE= "your toolchain path"
EXAMPLE:
Code:
CROSS_COMPILE ?= /home/sarthak/Downloads/Toolchains/arm-eabi-4.4.3/bin/arm-eabi-
This will open up the Makefile in a gedit,and the changed values will correspond to wherever u placed your toolchain...
Make the kernel config
Code:
make msm7627a_defconfig
NOTE- Do "make htc_pico_defconfig" is making ics/jb kernel
This will make a working kernel config acc. to the source code
Now,make the necessary changes in your source.When you are done,type:
Code:
make -jX
,where X=no.op cpu threads multiplied by 1 or 2.
Sit down and have a smoke!
The resulting kernel will be in Kernel/arch/arm/boot/zImage
Easy,ain't it?
Remember,this guide doesnt teach u how to make particular changes,it just helps u setting up your build environment and compiling from a given source.

Packaging kernel for flashing on target device
- Take a stock boot.img(or any boot.img that works with the rom)
- Downloads boot image tools from -> https://github.com/sakindia123/boot-image-tools and keep them somewhere
- Place boot.img in source_img folder inside the boot.img-tools folder(create if not there)
- Enter the boot tools directory
- Unpack:
Code:
$ mkdir -p unpack
$ tools/unpackbootimg -i source_img/boot.img -o unpack
-Extracting boot.img-ramdisk.gz
Code:
$ mkdir -p boot
$ cd boot
$ gzip -dc ../unpack/boot.img-ramdisk.gz | cpio -i
$ cd ../
Packing a new ramdisk:
Code:
$ tools/mkbootfs boot | gzip > unpack/boot.img-ramdisk-new.gz
Create a new boot.img:
Code:
$ mkdir -p target_img
$ tools/mkbootimg --kernel unpack/boot.img-zImage --ramdisk unpack/boot.img-ramdisk-new.gz -o target_img/boot.img --base `cat unpack/boot.img-base`
Done!
Now take the boot.img from target_img folder and flash via fastboot.Also push the compiled modules or else wifi wont work
Code:
fastboot flash boot boot.img && fastboot reboot
adb push drivers/net/wireless/bcmdhd/bcmdhd.ko /system/lib/modules
adb push drivers/net/kineto_gan.ko /system/lib/modules
NOTE: If u are compiling kernel for stock/sense roms,wifi module will be found in drivers/net/wireless/bcm4330b2/bcm4330.ko
Enjoy !

Compile rom from source
1) Make your own CyanogenMod9 nightly
So cant wait for the developer to release the next build?gettin' itchy?
Compile on your own!
- Packages
For 64-bit systems(For ICS and above,u need 64 bit and above)
Code:
apt-get install git-core gnupg flex bison gperf build-essential zip curl libc6-dev libncurses5-dev:i386 x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-dev:i386 g++-multilib mingw32 openjdk-6-jdk pngcrush schedtool tofrodos python-markdown libxml2-utils xsltproc zlib1g-dev:i386
- Create working directories for the build environment:
mkdir -p ~/bin
mkdir -p ~/android/system
- Get Google's repo tool
Code:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
Reboot
- Sync the Repository
Code:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b ics
repo sync -j16
NOTE- USe -j4 if u have slow net connection!
Wait for a few hours depending upon your net connection,it will download 4-5 GB or more
Then ,after syncing finishes,in the root of the source,open the hidden folder ".repo"
create a file local_manifest.xml and put this xml code to sync relevant repos for compiling cm9 for pico
PHP:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="lirokoa/android_device_htc_pico_ics" path="device/htc/pico" revision="ics" />
<project name="sakindia123/ics-vendor-pico" path="vendor/htc/pico" revision="master" />
</manifest>
then save and do "repo sync " again
- Compile the actual rom
This is fun bit.Make changes to the sourc code if u want to fix bugs or experiment,then,in the root of working directory,type
Code:
. build/envsetup.sh
brunch pico -jX
NOTE- REPLACE X with the no. of cores on your computer,do not enter X
Wait for it to compile(depends on how crap the computer is)
When it finishes compiling,output will be in out/target/product/pico/cm9-UNOFFICIAL-xxxxxxxx.zip
Flash the zip via recovery
Enjoy

Compile Evervolv Nightly
SO u dont want cm9,u want to compile evervolv,eh?
Follow the setups upto "Get Google's repo tool" in cm9 guide,but instead of cm9 source ,sync this
Code:
cd ~/android/system/
repo init -u git://github.com/cm2pico/android.git -b ics
repo sync -j16
After syncing,do this
Code:
nano vendor/ev/vendorsetup.sh
in the text editor that opens up,type
[/CODE]add_lunch_combo ev_pico-eng[/CODE]
Then to compile,
Code:
. build/envsetup.sh
lunch
Select pico in menu and type
Code:
make -jX otapackage
Replace X with no. of cores on pc!
pico up output zip from out/target/product/pico/Evervolv-2.2.0.zip

Nice think I might try this. I'm running osx is there different tools avalible or am I better off installing win or Linux in a vm
Sent from my HTC Explorer A310e using xda app-developers app
---------- Post added at 01:48 PM ---------- Previous post was at 01:45 PM ----------
Sorry just read the op properly and seen my question answered
Sent from my HTC Explorer A310e using xda app-developers app

May I use cygwin software to use this on windows to emulate properties of Linux? I heard so!

Nice to see new how to threads...
Sent from my Galaxy Nexus using Tapatalk 2

arunsai123 said:
May I use cygwin software to use this on windows to emulate properties of Linux? I heard so!
Click to expand...
Click to collapse
Not really..there are some things that cant be properly emulated..u need a native install or Virtual MAchine

BUMP- Kernel part of the tut has been completed.Hope u guys are successfully in making your own kernel

dude wheres the tutorial for ROM developement!!

updated with instruction to compile own CM9 and evervolv kang

Great Tutorial dude ...
Great Tutorial dude ... ... very clearly explained .... :laugh: :good: :fingers-crossed:

Great I'm going to compile aokp from its source
Sent from my HTC Explorer A310 using xda premium

time to download
well i have airtel broadband connection(unlimited) on 256 kbps, i get a downloading speed of 30-40 kbps.
so, i wanted to ask you all the size of all the sources/data required to compile a single ROM and time taken to download all those things.

siddharth1102 said:
well i have airtel broadband connection(unlimited) on 256 kbps, i get a downloading speed of 30-40 kbps.
so, i wanted to ask you all the size of all the sources/data required to compile a single ROM and time taken to download all those things.
Click to expand...
Click to collapse
cm9 about 4-5gb, evervolv ics about 6-6.5gb
unlike cm7 where you had to download all supported devices which added additional size to main source (16gb or so) cm9 (by default) and evervolv (from sakindia123 that includes device tree and vendor prop files) both only download the main source only which makes the downloads less in size...........for you it would take a long time to download afew hours (i have 15mbps or 1.5meg a sec so didnt take long) once all setup and synced a single cm9 build takes me just over 1hr and evervolv slightly more, all depends on your hardware ie ram, processor etc.....have fun

LiVeRpOoL-FaN said:
cm9 about 4-5gb, evervolv ics about 6-6.5gb
unlike cm7 where you had to download all supported devices which added additional size to main source (16gb or so) cm9 (by default) and evervolv (from sakindia123 that includes device tree and vendor prop files) both only download the main source only which makes the downloads less in size...........for you it would take a long time to download afew hours (i have 15mbps or 1.5meg a sec so didnt take long) once all setup and synced a single cm9 build takes me just over 1hr and evervolv slightly more, all depends on your hardware ie ram, processor etc.....have fun
Click to expand...
Click to collapse
Can i download these things in installments?

siddharth1102 said:
Can i download these things in installments?
Click to expand...
Click to collapse
really the best way is to fully download in 1 go but in terminal you press Ctrl + z (on Ubuntu) to stop the process and then carry it on later, although it wont sync the whole project until all source is downloaded............

LiVeRpOoL-FaN said:
really the best way is to fully download in 1 go but in terminal you press Ctrl + z (on Ubuntu) to stop the process and then carry it on later, although it wont sync the whole project until all source is downloaded............
Click to expand...
Click to collapse
While learning to compile i found that compiling jelly bean on ubuntu 12.04 is it experimental mode. So, i wanted to ask won't it compile properly and will it work i do so?

siddharth1102 said:
While learning to compile i found that compiling jelly bean on ubuntu 12.04 is it experimental mode. So, i wanted to ask won't it compile properly and will it work i do so?
Click to expand...
Click to collapse
i`ve not used 12.04 for anything, i used 11.10 for cm7 and cm9 but found had to use 10.04.4 (lucid) for evervolv ics (aosp code, not cm modified code) i think jb aosp was compiled on 10.04.4 by android aosp team

[HowTo] Instructions for compiling RootBox on Htc One S

This is a step by step guide to compiling Rootbox on your computer.
Requirements:
willingness to learn as you go
Ubuntu 12.04 64bit, dual-booted or virtual machine
some space on your Ubuntu partition, I'd say about 50GB to be very safe
an internet connection
You will need to setup the android environment on your computer first. The next step will depend on what version of ubuntu you use. The steps are laid out for version 12.10 of Ubuntu. If you have 12.04 you will have to search to make sure the files you are installing are the same version. I use a program called synaptic package manager to check to make sure the correct files are being installed. Most Ubuntu OS do not install it by default. To install it type this into a terminal:
Code:
sudo apt-get install synaptic
enter this command into the terminal.
Code:
sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.8-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev pngcrush schedtool g++-multilib lib32z1-dev lib32ncurses5-dev lib32readline6-dev gcc-4.7-multilib g++-4.7-multilib libxml2-utils libxml2 xsltproc
After that is all installed you will need to get rid of any java installed on your system.
to get rid of it type this into the terminal
Code:
sudo apt-get remove openjdk* icedtea* default-jre
This should remove all instances of java. Now to get the java that you want.
to get java add this ppa.
Code:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java6-installer
Now to start building the rom.
in terminal type
Code:
mkdir ~/android/rootbox/
then type
Code:
cd ~/android/rootbox
in terminal type
Code:
repo init -u git://github.com/Root-Box/platform_manifest.git -b jb-mr1
in terminal type
Code:
gedit .repo/local_manifest.xml
place this inside file and save file
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/htc/ville" name="atrus5/device_htc_ville" remote="gh" revision="master" />
<project name="android_kernel_htc_msm8960" path="kernel/htc/msm8960" remote="cm" revision="cm-10.1" />
<project path="device/htc/msm8960-common" name="android_device_htc_msm8960-common" remote="cm" revision="cm-10.1" />
<project path="vendor/htc/ville" name="atrus5/vendor_htc_ville" remote="gh" revision="master" />
</manifest>
in terminal type
Code:
repo sync
Go have some food, maybe watch a movie, go golfing, whatever you want to do cause this will take quite awhile. When that is done in terminal type
Code:
gedit vendor/rootbox/vendorsetup.sh
add this to end of file and save
Code:
add_lunch_combo rootbox_ville-userdebug
in terminal type
Code:
gedit vendor/rootbox/products/ville.mk
add this to file and save
Code:
# Specify phone tech before including full_phone
$(call inherit-product, vendor/rootbox/configs/gsm.mk)
PRODUCT_RELEASE_NAME := ville
# Boot animation
TARGET_SCREEN_HEIGHT := 960
TARGET_SCREEN_WIDTH := 540
# Inherit some common CM stuff.
$(call inherit-product, vendor/rootbox/configs/common.mk)
# Inherit device configuration
$(call inherit-product, device/htc/ville/device_ville.mk)
# Ville Overlay
PRODUCT_PACKAGE_OVERLAYS += vendor/rootbox/overlay/common
# PA OVERLAY_TARGET
OVERLAY_TARGET := pa_hdpi
# Setup device specific product configuration.
PRODUCT_DEVICE := ville
PRODUCT_NAME := rootbox_ville
PRODUCT_BRAND := HTC
PRODUCT_MODEL := HTC One S
PRODUCT_MANUFACTURER := HTC
# Copy Bootanimation
PRODUCT_COPY_FILES += \
vendor/rootbox/prebuilt/hdpi/bootanimation.zip:system/media/bootanimation.zip
in terminal type
Code:
gedit vendor/rootbox/products/AndroidProducts.mk
add this to end of file and save. (note: you will need to add a ' \' to the line before it, without the quotations. that is a space before the \). For example here is what my last two lines look like. $(LOCAL_DIR)/t0lte.mk \
$(LOCAL_DIR)/ville.mk
Code:
$(LOCAL_DIR)/ville.mk
This part is optional. I do these steps just to make sure that I have all the necessary files to compile the rom.
plug in your phone
in terminal type
Code:
cd device/htc/ville
and
Code:
./extract-files.sh
Ok now back to building the rom. You don't have to do the above steps, it's just to make sure.
in terminal type
Code:
cd ~/android/rootbox
or wherever you have placed your rootbox build. This is where I store mine.
in terminal type
Code:
./build_rootbox.sh ville
This should compile the rom and you can flash the nightly build onto your phone. The file is in the out/target/product/ville directory.
I hope this helps.

Why not just share what you build?
Or are we not allowed to share what we build, like what happened for the Baked Black Bean ROM?
Sent from my HTC One S using Tapatalk 2

RockR172 said:
Why not just share what you build?
Or are we not allowed to share what we build, like what happened for the Baked Black Bean ROM?
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
Good point. I will ask them and see if I can.

atrus5 said:
Good point. I will ask them and see if I can.
Click to expand...
Click to collapse
I am going to try this right after Baked!

Bowmanspeer said:
I am going to try this right after Baked!
Click to expand...
Click to collapse
I'm guessing permissions were granted...

Bowmanspeer said:
I'm guessing permissions were granted...
Click to expand...
Click to collapse
Rootbox is being built by $droyd$ now. If you want the rom without having to build it you can go to the one s development section and download it from there. I know that you will not be able to get the files needed from the proprietary repo as well as the device/htc/ville repo. If you need them let me know.

atrus5 said:
Rootbox is being built by $droyd$ now. If you want the rom without having to build it you can go to the one s development section and download it from there. I know that you will not be able to get the files needed from the proprietary repo as well as the device/htc/ville repo. If you need them let me know.
Click to expand...
Click to collapse
Yeah. I actually tried and it aborted because of errors. I just want to learn.
I did Build Baked from the other How to. Its a little different when build it yourself... But I want to know more...

Bowmanspeer said:
Yeah. I actually tried and it aborted because of errors. I just want to learn.
I did Build Baked from the other How to. Its a little different when build it yourself... But I want to know more...
Click to expand...
Click to collapse
What were the errors? I felt the same way when trying to compile roms too. Got a lot of errors but struggled through it.
Sent from my One S using xda premium

atrus5 said:
What were the errors? I felt the same way when trying to compile roms too. Got a lot of errors but struggled through it.
Click to expand...
Click to collapse
2 main sources wouldn't download. One was a 404 page not found and the other had to do with permissions I think. I've closed the terminal so its gone. I didn't have this problem when I did Baked. The problem there was something to do with the Lunch menu till $droyd$ stepped in and provided a different command that compiled and produced the flashable zip and boot.img.

Bowmanspeer said:
2 main sources wouldn't download. One was a 404 page not found and the other had to do with permissions I think. I've closed the terminal so its gone. I didn't have this problem when I did Baked. The problem there was something to do with the Lunch menu till $droyd$ stepped in and provided a different command that compiled and produced the flashable zip and boot.img.
Click to expand...
Click to collapse
I have switched the post to reflect the changes needed for the error, or at least what I think is the error. These are changes to the local_manifest.xml file.

Thanks. I'll give it another whirl.
Sent.

Another one trying to compile...
Hello artus5,
thanks for your guide!! As I would like to learn how to build Roms from Source too, I just tested your manual.
Unfortunatelly I ran into problems, wright from the start. I got this error and don't know how to get over it...
HTML:
Lunching your device
build/core/product_config.mk:234: *** Can not locate config makefile for product "rootbox_". Schluss.
** Don't have a product spec for: 'rootbox_'
** Do you have the right repo manifest?
Starting RootBox build for
including vendor/rootbox/vendorsetup.sh
build/core/product_config.mk:234: *** Can not locate config makefile for product "rootbox_". Schluss.
** Don't have a product spec for: 'rootbox_'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Maybe you could help me with that.
Thanks and happy eastern!

rum0s said:
Hello artus5,
thanks for your guide!! As I would like to learn how to build Roms from Source too, I just tested your manual.
Unfortunatelly I ran into problems, wright from the start. I got this error and don't know how to get over it...
HTML:
Lunching your device
build/core/product_config.mk:234: *** Can not locate config makefile for product "rootbox_". Schluss.
** Don't have a product spec for: 'rootbox_'
** Do you have the right repo manifest?
Starting RootBox build for
including vendor/rootbox/vendorsetup.sh
build/core/product_config.mk:234: *** Can not locate config makefile for product "rootbox_". Schluss.
** Don't have a product spec for: 'rootbox_'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
Maybe you could help me with that.
Thanks and happy eastern!
Click to expand...
Click to collapse
What are you typing for the command to start it? I have made some changes to the tutorial. Could you please reread it and tell me if you have typed anything wrong. I just tested it on mine and everything worked for me. It sounds like you have entered something wrong in the ville.mk file or else you typed ./build-rootbox.sh rootbox_ville instead of just ville. I also didn't put how to set up the android environment into the tutorial. I should probably do that as well.

atrus5 said:
It sounds like you have entered something wrong in the ville.mk file or else you typed ./build-rootbox.sh rootbox_ville instead of just ville. I also didn't put how to set up the android environment into the tutorial. I should probably do that as well.
Click to expand...
Click to collapse
Oh my fault... I entered ./build_rootbox.sh instead of ./build_rootbox.sh ville. Sorry!
As I'm very new to this and would really like to learn it, enhancing your tutorial would be very much appreciated :laugh:
Therefore I have a question.
The part where I add the local_manifest.xml. Is it for getting the devices files that are not included in the rootbox git repository as my device is not supported? Why do I have then to extract files from my device with the ./extract-files.sh script?

rum0s said:
Oh my fault... I entered ./build_rootbox.sh instead of ./build_rootbox.sh ville. Sorry!
As I'm very new to this and would really like to learn it, enhancing your tutorial would be very much appreciated :laugh:
Therefore I have a question.
The part where I add the local_manifest.xml. Is it for getting the devices files that are not included in the rootbox git repository as my device is not supported? Why do I have then to extract files from my device with the ./extract-files.sh script?
Click to expand...
Click to collapse
I did this just to make sure that all the files that were needed were taken from the phone. I don't like to leave anything out of the rom. I will change that to reflect the fact that all the files are already added. Thank you. I have changed to tutorial to be a full tutorial.
edit: thank you for making this into a better tutorial.
edit: the extra lines added to the local_manifest.xml file is for your device kernel as well as any device files that your phone will need.

@atrus5: you got PM and thanks

ok here's another question, as the compiling process has been aborted
it tells me something like (my terminal is in german):
HTML:
make: *** no rule to make target »vendor/rootbox/prebuilt/rootbox_ville.conf«,
from »/media/..../rootbox/out/target/product/ville/system/etc/paranoid/properties.conf«. end.
make: *** Waiting for processes not yet finished...
I couldn't find a file called rootbox_ville.conf in the prebuilt folder. Is this the problem?
Futhermore there were some files not found but the message was just skipped without any interuption/problem...
HTML:
find: "../../vendor/unbundled_google/libs/gcm/gcm-client/src": file or folder not found
find: "../../vendor/unbundled_google/libs/gcm/gcm-server/src": file or folder not found
find: "../../vendor/unbundled_google/libs/gcm/gcm-client/src": file or folder not found
find: "../../vendor/unbundled_google/libs/gcm/gcm-server/src": file or folder not found

rum0s said:
ok here's another question, as the compiling process has been aborted
it tells me something like (my terminal is in german):
HTML:
make: *** no rule to make target »vendor/rootbox/prebuilt/rootbox_ville.conf«,
from »/media/..../rootbox/out/target/product/ville/system/etc/paranoid/properties.conf«. end.
make: *** Waiting for processes not yet finished...
I couldn't find a file called rootbox_ville.conf in the prebuilt folder. Is this the problem?
Futhermore there were some files not found but the message was just skipped without any interuption/problem...
HTML:
find: "../../vendor/unbundled_google/libs/gcm/gcm-client/src": file or folder not found
find: "../../vendor/unbundled_google/libs/gcm/gcm-server/src": file or folder not found
find: "../../vendor/unbundled_google/libs/gcm/gcm-client/src": file or folder not found
find: "../../vendor/unbundled_google/libs/gcm/gcm-server/src": file or folder not found
Click to expand...
Click to collapse
That looks like something that rootbox has just added to there files in the last 9 hours. I don't know how to fix that yet. I will see what I can do.

rum0s said:
ok here's another question, as the compiling process has been aborted
it tells me something like (my terminal is in german):
HTML:
make: *** no rule to make target »vendor/rootbox/prebuilt/rootbox_ville.conf«,
from »/media/..../rootbox/out/target/product/ville/system/etc/paranoid/properties.conf«. end.
make: *** Waiting for processes not yet finished...
I couldn't find a file called rootbox_ville.conf in the prebuilt folder. Is this the problem?
Futhermore there were some files not found but the message was just skipped without any interuption/problem...
HTML:
find: "../../vendor/unbundled_google/libs/gcm/gcm-client/src": file or folder not found
find: "../../vendor/unbundled_google/libs/gcm/gcm-server/src": file or folder not found
find: "../../vendor/unbundled_google/libs/gcm/gcm-client/src": file or folder not found
find: "../../vendor/unbundled_google/libs/gcm/gcm-server/src": file or folder not found
Click to expand...
Click to collapse
You will need to change your ville.mk file to this as they have made changes onto the rootbox build. Replace everything in your ville.mk file with this.
Code:
# Specify phone tech before including full_phone
$(call inherit-product, vendor/rootbox/configs/gsm.mk)
PRODUCT_RELEASE_NAME := ville
# Boot animation
TARGET_SCREEN_HEIGHT := 960
TARGET_SCREEN_WIDTH := 540
# Inherit some common CM stuff.
$(call inherit-product, vendor/rootbox/configs/common.mk)
# Inherit device configuration
$(call inherit-product, device/htc/ville/device_ville.mk)
# Ville Overlay
PRODUCT_PACKAGE_OVERLAYS += vendor/rootbox/overlay/common
# PA OVERLAY_TARGET
OVERLAY_TARGET := pa_hdpi
# Setup device specific product configuration.
PRODUCT_DEVICE := ville
PRODUCT_NAME := rootbox_ville
PRODUCT_BRAND := HTC
PRODUCT_MODEL := HTC One S
PRODUCT_MANUFACTURER := HTC
# Copy Bootanimation
PRODUCT_COPY_FILES += \
vendor/rootbox/prebuilt/hdpi/bootanimation.zip:system/media/bootanimation.zip
edit: I would do a repo sync after changing the ville.mk file and also type in the terminal:
Code:
rm -rf out
This will start the build process all over again.

Okay fantastic, thanks for your immediate answer! compiling has been started again
So how did you figure it out, what the problem was? As I can see, there has been inserted an overlay...I just looked into the pa_hdpi.conf it's telling the system how various apps shall look like in terms of DPI. Was this the missing part? Or has an "old overlay" been removed?
Moreover I created a directory for the local_manifets.xml file in the .repo folder, as the compilier told me to do that. Maybe you could add this to your OP too.

[DEV][Porting] Ubuntu Touch on Galaxy Note II (GT-N7100)

Currently I'm trying to run Ubuntu Touch Developer Preview on my Note II
So far Ubuntu touch based on cm-10.1 it is quite simple to port to any device supported by cm.
For beginning there are some useful guides:
Ubuntu Touch Developer Preview - Porting Guide
How to Build CyanogenMod for Galaxy Note 2
And here we go:
First of all prepare the Build Environment
Code:
sudo apt-get install git gnupg flex bison gperf build-essential \
zip bzr curl libc6-dev libncurses5-dev:i386 x11proto-core-dev \
libx11-dev:i386 libreadline6-dev:i386 libgl1-mesa-glx:i386 \
libgl1-mesa-dev g++-multilib mingw32 tofrodos \
python-markdown libxml2-utils xsltproc zlib1g-dev:i386 schedtool
Install phablet-tools
Code:
sudo apt-add-repository ppa:phablet-team/tools
sudo apt-get update
sudo apt-get install phablet-tools
To get the source code do bootstrap, it takes a looooong time and need about 15 GB of disk space
Code:
phablet-dev-bootstrap -j 4 ubuntu-touch
Code:
cd ubuntu-touch
Now we need to grab the n7100 specific git repositories.
In general we use CyanogenMode repositories with some changes made for ubuntu phone
For the moment I'm not sure whether it is all changes what we need, therefore I have fork them on git hub,
so just create a new file .repo/local_manifest.xml with content:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="drapalyuk/android_device_samsung_n7100" path="device/samsung/n7100" remote="github" revision="phablet-10.1" />
<project name="drapalyuk/android_device_samsung_smdk4412-common" path="device/samsung/smdk4412-common" remote="github" revision="phablet-10.1" />
<project name="drapalyuk/android_kernel_samsung_smdk4412" path="kernel/samsung/smdk4412" remote="github" revision="phablet-10.1" />
<project name="drapalyuk/android_hardware_samsung" path="hardware/samsung" remote="github" revision="phablet-10.1" />
</manifest>
Code:
repo sync -j4
Extract proprietary blobs, expected you have all ready installed CM-10 on your phone, if not Install CM for n7100
Code:
cd device/samsung/n7100
./extract-files.sh
If you want to speed up subsequent builds after this one
Turn on caching
Code:
export USE_CCACHE=1
Start the build
Code:
. build/envsetup.sh
brunch n7100
After successfully build N7100 zip installer will be placed into out/target/product/n7100/cm-10.1-<date>-UNOFFICIAL-n7100.zip
Installation instructions:
reboot in recovery
wipe
install the N7100 specific installer
install the Ubuntu 12.10 Touch Preview, daily build quantal-preinstalled-phablet-armhf.zip
reboot
DISCLAIMER: this is development preview do not install if you don't know exactly what you are doing
Latest N7100 specific image Here
To Be Continued...

Progress

could we use this on the tmobile note 2 also

Hi, i'm porting ubuntu touch on SGS3 i9300 (international) but i'm having issues addressed to a segfault of surfaceflinger not finding libandroid_runtime.so: any errors like this?

Flashing this ROM already work Unbuntu into N7100?
Thanks, I took several days trying to download the repo but always fails.

allenjthomsen said:
could we use this on the tmobile note 2 also
Click to expand...
Click to collapse
I've never seen a straightforward answer to how to convert a n7100 rom to a t889 rom... Something to do with copy the kernel image out of a working t889 rom and into the n7100 rom? But I've also heard that some people get bricks trying!
If this rom doesn't work for a t889, could the same steps be followed, substituting in t889 where applicable, to make the right rom? I would just try it, but my phone is away for warranty repair :crying:

gianguido said:
Hi, i'm porting ubuntu touch on SGS3 i9300 (international) but i'm having issues addressed to a segfault of surfaceflinger not finding libandroid_runtime.so: any errors like this?
Click to expand...
Click to collapse
Exynos GPU Mali lib*_mali.so need libandroid_runtime.so
BoRoU said:
Flashing this ROM already work Unbuntu into N7100?
Click to expand...
Click to collapse
not completely I get console and can chroot into ubuntu, but no gui yet
but I'm working on

drapalyuk said:
Exynos GPU Mali lib*_mali.so need libandroid_runtime.so
not completely I get console and can chroot into ubuntu, but no gui yet
but I'm working on
Click to expand...
Click to collapse
How did you get the Android part to build, I have been trying for two days and I just got it to even start compiling yesterday. Here is a link to my paste bin, I have the T-Mobile Note II so I am using t0lte (GT-N7105).
Also if you want I have a guid i was putting together until I hit this snag yesterday.I will upload it and let you look at it if you want to further edit your OP. Where did you fork your android_hardware_samsung folder ? I could not find one in the CM repositories I had to use another repository I found.

Are your CM sources older then the 24th ? On the 23 they fixed the MALI render issued and memory leak in CM 10.1.
Sent from my GT-N7100 using xda app-developers app

lgstoian said:
Are your CM sources older then the 24th ? On the 23 they fixed the MALI render issued and memory leak in CM 10.1.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Ha yeah they are from the 23 that is when i finished my repo sync and cloned my device files. I guess I need to re sync and redo my edits then try again. Also does this require the linaro toolchain?
I got past my above problem by going to device/samsung/t0lte/t0lte and taking out the following from it.
Code:
# Product specific Packages
PRODUCT_PACKAGES += \
GalaxyNote2Settings
But I am still having troubles.
Edit: This is now my issue, got to find where to disable this.
Code:
make: *** No rule to make target `/home/tmacgnolia/UPP/out/target/product/t0lte/obj/SHARED_LIBRARIES/libTVOut_intermediates/export_includes', needed by `/home/tmacgnolia/UPP/out/target/product/t0lte/obj/EXECUTABLES/mediaserver_intermediates/import_includes'. Stop.

I try to start with phablet-dev-bootstrap-c ubuntu-touch and always short. I get this error:
INFOhablet-dev-bootstrap:Changing to workdir /home/borou/ubuntu-touch
INFOhablet-dev-bootstrap:Initializing repository
Your identity is: BoRoU <[email protected]>
If you want to change this, please re-run 'repo init' with --config-name
repo has been initialized in /home/borou
If this is not the directory in which you want to initialize repo, please run:
rm -r /home/borou/.repo
and try again.
Fetching projects: 20% (28/136) fatal: The remote end hung up unexpectedly
Fetching projects: 37% (51/136) fatal: read error: Conexi?n reinicializada por la m?quina remota

Is i directly flash quantal-preinstalled-phablet-armhf.zip on galaxy note 2? and Is it work properly?

manish.t92 said:
Is i directly flash quantal-preinstalled-phablet-armhf.zip on galaxy note 2? and Is it work properly?
Click to expand...
Click to collapse
read the thread. (1 page) the op answered that question yesterday. and this section is developer talk only.

BoRoU said:
I try to start with phablet-dev-bootstrap-c ubuntu-touch and always short. I get this error:
INFOhablet-dev-bootstrap:Changing to workdir /home/borou/ubuntu-touch
INFOhablet-dev-bootstrap:Initializing repository
Your identity is: BoRoU <[email protected]>
If you want to change this, please re-run 'repo init' with --config-name
repo has been initialized in /home/borouosal
If this is not the directory in which you want to initialize repo, please run:
rm -r /home/borou/.repo
and try again.
Fetching projects: 20% (28/136) fatal: The remote end hung up unexpectedly
Fetching projects: 37% (51/136) fatal: read error: Conexi?n reinicializada por la m?quina remota
Click to expand...
Click to collapse
The repo sync took me forever so I ad to restart it several times. It would give the " fatal: The remote end hung up unexpectedly" every time.
Edit: I need hardware/samsung/exynose/multimedia/openmax/include/osal. I do not have it for some reason.

Someone asked about porting N7100 ROM's. Try this guide
http://forum.xda-developers.com/showthread.php?t=2018411
Sent from my Samsung Galaxy SIII LTE GT-I9305 using XDA Premium HD

weeo said:
Someone asked about porting N7100 ROM's. Try this guide
http://forum.xda-developers.com/showthread.php?t=2018411
Sent from my Samsung Galaxy SIII LTE GT-I9305 using XDA Premium HD
Click to expand...
Click to collapse
Thanks for the link but unfortunately that guide really has little relevance to the work going on here. This has to be built from source so any device specific files need to be in the source which means cloning them from a repository or added manually as well as adding lines to the appropriate .mk or config files. Now this guide does have some usefulness but just not a whole lot.

T-Macgnolia said:
Thanks for the link but unfortunately that guide really has little relevance to the work going on here. This has to be built from source so any device specific files need to be in the source which means cloning them from a repository or added manually as well as adding lines to the appropriate .mk or config files. Now this guide does have some usefulness but just not a whole lot.
Click to expand...
Click to collapse
Ah i see. My bad... I thought it wasnt relevant... But then someone told me Ubuntu was based on CM10.1 (i thought it was the same as building cm10.1) so i thought it had the same ROM format. So i was guessing that wouls work. Sorry my bad. Forgive me
Sent from my Samsung Galaxy Note 10.1 using XDA Premium HD app

current progress
finally get the gui starting
working:
camera (both), flash
sound (at least by tacking a photo)
microphone (by voice input)
pen
known issues:
font rendering artifacts
no gsm
no wifi
to be continued...

drapalyuk said:
current progress
finally get the gui starting
working:
camera (both), flash
sound (at least by tacking a photo)
microphone (by voice input)
pen
known issues:
font rendering artifacts
no gsm
no wifi
to be continued...
Click to expand...
Click to collapse
i did : Brunch n7100 and there is no zip file created ( out/target/product/n7100 )

any outputs in console?

[GUIDE][CM10/CM10.1] ROM Building From Source for GT-i9003 SL

Only Intention of This Guide More and More People Learn How to Build CM from Source.
Note ::
New Suggestion are welcome to make this guide more easy and perfect.Post any problem related to build in this thread. I will reply as soons as possible.:fingers-crossed:
What You will Require :-
1) PC Running Ubuntu 12.10x64 Bit System
2) Good Internet Connection Speed.
3) Patience
4) Samsung Galaxy SL
I will Distribute Building CM into Several Parts for Comfortable
(1) Setup Linux and Build Environment
(2) Source Sync & Download Pre-builts Files
(3) Setup Device tree
(4) Patching and cherry-picking
(5) Building ROM
(6) Installing ROM
(1) Setup Linux and Build Environment
Setup Linux
You will need Linux distros to build any ROM because windows system is not completely supported yet. you could possibly build ROMs on any Linux platform
but I recommended Ubuntu 12.10 64-bit System.And also this guide is written on base of pure clean Ubuntu 12.10 system.
You can setup dual boot with Windows.You can Google it how to Dual boot windows and Ubuntu.
or
you can use virtual machine like vmware player (http://www.vmware.com/products/player/ ) or Virtual Box (https://www.virtualbox.org/) they all are freeware software. But to use virtual machine you will need Higher Specification for best experience.
You could download Ubuntu 12.10 ISO from here : http://www.ubuntu.com/download
and make it bootable Pen Drive or CD to install it or Direct use in Virtual machine Software to Install it.
When You complete with installing Ubuntu proceed to setup build environment.
Build Environment
To build ROM from any source you will need several tools
Open Terminal,
1) Java Development Kit 6/Java Development Kit 7
If you are first time Installing JDK than procedded to installing step or first delete all previous version using this commands
Code:
sudo apt-get purge openjdk-\* icedtea-\* icedtea6-\*
sudo apt-get purge sun-java
Method 1 :: Install Latest JDK 6
Open terminal and type this :
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 12.10/13.04.it’s self updating, so you don’t have to redownload binaries everytime they release a new version.
Next,install the package.
Code:
sudo apt-get update && sudo apt-get install oracle-java6-installer
Follow the onscreen instructions. You have to Accept the Licensing Agreement.
Once that is completed successfully to make sure the correct version of Java is installed, run the following at the Terminal prompt:
java -version
Click to expand...
Click to collapse
You should see something like the following:
java version “1.6.0_37″
Java(TM) SE Runtime Environment (build 1.6.0_37-b06)
Java HotSpot(TM) 64-Bit Server VM (build 20.12-b01, mixed mode)
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Method 2 :: Install All Java tools
Its another method to install every JDK 6 tools automatically.
now to install JDK-6
Code:
mkdir ~/src
cd ~/src
git clone [url]https://github.com/flexiondotorg/oab-java6.git[/url]
cd ~/src/oab-java6
sudo ./oab-java.sh
Then when its finished, install java:
Code:
sudo apt-get install sun-java6-plugin sun-java6-jre sun-java6-bin sun-java6-jdk
You can follow the downloading process status of java package using this command in different terminal:
Code:
tail -f ~/src/oab-java6/oab-java.sh.log
You can check java veriosn using
Code:
java -version
Click to expand...
Click to collapse
2) Install dependencies
Code:
sudo apt-get install git-core gnupg flex bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 libc6-dev lib32ncurses5-dev ia32-libs 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
Code:
sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
3) Android SDK (Optinal)
Download LINK :: http://developer.android.com/sdk/index.html
After Downloading Extract it at your desire directory as example : home/android/
it will be extracted with name : android-sdk-linux
Now go to that location using Terminal
Code:
cd ~/android/android-sdk-linux/tools
./android
than install adb driver and other platform tools. No need to download any API for now eiether you want to make android app.
To access adb command from anywhere in terminal you have to add its path to Bourne Again Shell (bash)
use any editor from below. (nano or gedit) to modify bash.
Code:
sudo nano ~/.bashrc
OR
Code:
sudo gedit ~/.bashrc
Than at the end of the file add this lines.
Code:
export PATH=${PATH}:<sdk>/tools:<sdk>/platform-tools
replace <sdk> with folder address.in My case i extracted it on /home directory
Code:
export PATH=${PATH}:/home/nics/android-sdk-linux/platform-tools/
Save the file. Then open a new Terminal. The adb command should now be available.
That's it. ADB (Android Debug Bridge) will have you debug ROM as well as application also.
(2) Source Sync & Download Prebuilts
1)Downloading Repository Binary
The binary for 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 https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo && chmod a+x ~/bin/repo
Use your favorite text editor to open ~/.bashrc
use nano:
Code:
sudo nano ~/.bashrc
At bottom add this 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
2) Initialize The Repository
First Close current terminal and reopen again New
Code:
mkdir ~/cm10.1 ## you can use any name on behalf cm10.1
cd ~/cm10.1
Now to build Jellybena 4.1.2 you need to initialize CM10 repo
Code:
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
or
If you want to build Jellybean 4.2.2 initialize CM10.1 repo below.
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
Now begin Download Source
Code:
repo sync
(It will take time depending on your internet speed. Downloading Source will download around 8.2 GB approaxmatiely or mare than that)
TIPS :: you can use "repo sync -j3" or "repo sync -j5" command also. It means it will download simantueosly 3 or 5 projects default threads are set to 16. this code are used to decreased it to whatever you want it only require when you have problem of syncin source on low speed.
3) Download Prebuilts
after completing repo sync Download pre-builts
go into :: ~/cm10.1/vendor/cm
Code:
cd ~/cm10.1/vendor/cm/
and run this
Code:
./get-prebuilts

(3) setup Device tree
In terminal
Code:
cd ~/cm10.1/.repo
Code:
mkdir local_manifests && cd local_manifests
gedit roomservice.xml
For CM10 with Kernel 3.0 copy below manifests and save & close roomservice.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="dhiru1602/android_device_samsung_galaxysl" path="device/samsung/galaxysl" remote="github" revision="jellybean-3.0" />
<project name="dhiru1602/android_vendor_samsung_galaxysl" path="vendor/samsung/galaxysl" remote="github" revision="jellybean-3.0" />
<project name="dhiru1602/android_kernel_samsung_latona" path="kernel/samsung/latona" remote="github" revision="latona-sandbox-3.0" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="jellybean"/>
</manifest>
For CM10.1 with kernel 3.0 copy and paste below manifest to roomservice.xml and save and close it.
CM10 with CM10.1 with Kernel 2.6 manifests will be added soon Here.
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="dhiru1602/android_device_samsung_galaxysl" path="device/samsung/galaxysl" remote="github" revision="cm-10.1" />
<project name="dhiru1602/android_vendor_samsung_galaxysl" path="vendor/samsung/galaxysl" remote="github" revision="cm-10.1" />
<project name="dhiru1602/android_kernel_samsung_latona" path="kernel/samsung/latona" remote="github" revision="cm-10.1" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-10.1" />
</manifest>
close and ope new terminal and navigate in source folder and do again repo sync it will download device tree as per in roomservice.xml
Code:
cd cm10.1
repo sync
(4) Patching and cherry-picking
No Patching Required for CM10 and CM10.1 with kernel 3.0
(5) Building ROM
Before Building New ROM every time its wise idea to update source with mainstream. You need to just sync reporosity again.
Code:
repo sync
Now for Building ROM
Code:
. build/envsetup.sh
brunch galaxysl
It will take time depends on your processor and RAM of your machine & will create output in /out/target/product/galaxysl/cm-10-XXXXX-UNOFFICIAL-galaxysl.zip
It will look like this in the End
View attachment 2082696
(6) Installing
To install newly build ROM you need to Copy it to you SD card. Reboot into CWM Recovery Mode
Wipe Cache and Dalvik-cache if you are on CM10/CM10.1 with Kernel 3.0 or Do full wipe and Install it.
reboot phone and check everything is working. and than reboot again in Recovery Mode and install Gapps.
Gapps :: http://goo.im/gapps/
Reboot phone and Enjoy
Happy ROM BuildinG.:laugh:

Reserved for Description

Reserved for Patch Discussion

Reserved for FAQs

It is Seperate Guide for Kernel Building. Its Just Reference Guide So its require some understing. Will modify and update it to make easier when i will get time.
Kernel Building is different than ROM building. In ROM building Kernel is already build while ROM cooking by Android Build System.You will not require CM10 or CM10.1 source for this.
What you will Require
1) PC with Ubuntu 12.10/13.04 x64
2) Toolchain #Software to compile Kernel
3) One Kernel already build.
4) Some tools
1) get git tool
Code:
sudo apt-get git
2) Get toolchain.
Our Dear dev adipat has put sevaral toolchain in his git repo.
I recommand to use arm-eabi-4.4.3
now to download toolchain.
(1)mkdir Toolchains && cd Toolchains
(2) git clone -b arm-eabi-4.4.3 git://github.com/AdiPat/Android_Toolchains.git
I am showing here how to build CM10.1 Kernel 3.0 so dont get confused.
you can build different kernel as same as here. you will require some understanding of git commands and about our Kernel Source.
Code:
mkdir kernel_sl ## you can take any name instead of kernel_sl
cd kernel_sl
git clone -b cm-10.1 https://github.com/dhiru1602/android_kernel_samsung_latona.git ## it will download Kernel 3.0 Source of CM10.1 branch from Dheeraj's Repo.
after finishing go into android_kernel_samsung_latona
Code:
cd android_kernel_samsung_latona
make output folder for kernel.
default output of zimage is "arch/arm/boot/zImage" inside kernel source
change it your desire location.
Download build.sh.zip provided in the post and extract it and put build.sh in android_kernel_samsung_latona dir,
open it and change path of toolchain and output directory as per your setting.
Set it as per you prefernce.
I am using toolchain already in cm10.1 source. you can use it if you have source. or change path as per toolchain you downloaded from upper provided repo or any other website.
save it.
now give it permission to execute.
Code:
sudo chmod +x build.sh
to start building kernel.
Actually build.sh is line of commands to start building Kernel by putting them in one file and by executing we dont need to run every command manually. You can also type or copy & paste command manually to learn meanings of code.
Code:
./build.sh
Now download this :: http://d-h.st/ncR
unpack-repack tool by our dear Dev loSconosciuto.
now make new_kernel folder into kernel_out and extract unpack-repack tools there.
grab boot.img from our CM10.1 RoM
put it in /home/nics/kernel_out/new_kernel/unpack-repack
run in terminal
Code:
./unpack.pl
it will create directory named out containing boot.img and zimage.
just replace zimage with newely builed zimage.
and run
Code:
./repack.sh
it will create boot.img and updater-zip in out directory.
that's it boot.img is your new kernel.
take this boot.img and make updater.zip and flash it or replace it in CM10.1 ROM zip and flash it. that's most easiest way to flash and make Kernel.

Source
# frapeti's Guide for CM9 Here
# HP touchpad CM building Guide
# http://wiki.cyanogenmod.org/w/Template:Cm10_build
# http://soupdawg.wordpress.com/
Credits
Special thanks to dhiru1602,loSconosciuto & adi_pat
LoLaTiOn,rodero95
alfrix,TheDarkLord1997,frapeti
Our SL Senior Members & Recognized Contributors and every Developer who have contributed on SL Development.
HP touchpad CM building Guide authors
CyanogenMod Team

build cm10.1 kernel with 2.6 ?§!
Code:
mkdir -p ~/bin
PATH=~/bin:$PATH
Code:
sudo apt-get install curl
curl [url]https://dl-ssl.google.com/dl/googlesource/git-repo/repo[/url] > ~/bin/repo
chmod a+x ~/bin/repo
Code:
cd '/home/[COLOR="DarkOrange"]users[/COLOR]/cm10.1'
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
Code:
repo sync
other method the cloning party source !
Code:
mkdir -p ~/cm10.1/vendor/samsung
cd '/home/[COLOR="DarkOrange"]users[/COLOR]/cm10.1/vendor/samsung'
git clone https://github.com/rodero95/android_vendor_samsung_galaxysl
Code:
mkdir -p ~/cm10.1/device/samsung
cd '/home/[COLOR="DarkOrange"]users[/COLOR]/cm10.1/device/samsung'
git clone https://github.com/rodero95/android_device_samsung_galaxysl
Code:
mkdir -p ~/cm10.1/kernel/samsung
cd '/home/[COLOR="DarkOrange"]users[/COLOR]/cm10.1/kernel/samsung'
git clone https://github.com/rodero95/android_kernel_samsung_latona_legacy
Rename "android_kernel_samsung_latona_legacy" in "latona" like "roomservice.xml"
check the device and vendor directory has the same like "roomservice.xml"
Code:
mkdir local_manifests
cd local_manifests
gedit roomservice.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="rodero95/android_device_samsung_galaxysl" path="device/samsung/galaxysl" remote="github" revision="jellybean" />
<project name="rodero95/android_vendor_samsung_galaxysl" path="vendor/samsung/galaxysl" remote="github" revision="cm-10.1" />
<project name="rodero95/android_kernel_samsung_latona_legacy" path="kernel/samsung/latona" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-10.1" />
</manifest>

Lola after first time source downloaded. you need to go in '.repo' folder in source folder. and in that create dir named 'local_manifests' and inside it create roomservice.xml file. in this file copy above code which i put in device tree section. for CM10.1 use CM10.1 manifests. Dont modify above commands 'bin' is folder where repo tool downloaded not source. dont clone any source manually instead just write that project name in roomservice.xml and when ever you do repo sync it will download that device tree as well as up date source. just follow above guide.

Hey!
Great to know more people get interested on android development!
Just if you want some help, all my scripts, manifests and patches I use are published as gists on my github account
http://gist.github.com/rodero95
Some of them may be outdated or non-working as some days I introduce some changes but don't finish them, so look for the different revisions of one does not work (I think the only broken script right now is the ROM building script).
Good luck and happy development!
Sent from my GT-I9003 using xda premium

rodero95 said:
Hey!
Great to know more people get interested on android development!
Just if you want some help, all my scripts, manifests and patches I use are published as gists on my github account
http://gist.github.com/rodero95
Some of them may be outdated or non-working as some days I introduce some changes but don't finish them, so look for the different revisions of one does not work (I think the only broken script right now is the ROM building script).
Good luck and happy development!
Sent from my GT-I9003 using xda premium
Click to expand...
Click to collapse
Thanks rodero.
I will update thread soon currently my semester's final exam are running and will finish next week. I will update thread with remaining guide description, manifests for CM10/CM10.1 with 2.6 kernel , dependency for new ubuntu 13.04 'Raring Ring Tail'.

hello
nicsptl said:
Reserved for FAQs
i have a question sir CYNOGENMOD working dual sim phones or not?
Click to expand...
Click to collapse

paras357 said:
nicsptl said:
Reserved for FAQs
i have a question sir CYNOGENMOD working dual sim phones or not?
Click to expand...
Click to collapse
Ans is Yes.
As CynogenMod is based on ASOP Source and AOSP source does support Dual Sim. But to complete support of Dual Sim on CM it requires complete Kernel source as well Device source. And most company do not release device specific dual sim source. That makes very difficult to implement Dual Sim support properly on CM. If i am not wrong than fewer device have Dual sim support on non-official CM Roms/Ports.
Click to expand...
Click to collapse

Ans is Yes.
As CynogenMod is based on ASOP Source and AOSP source does support Dual Sim. But to complete support of Dual Sim on CM it requires complete Kernel source as well Device source. And most company do not release device specific dual sim source. That makes very difficult to implement Dual Sim support properly on CM. If i am not wrong than fewer device have Dual sim support on non-official CM Roms/Ports.[/QUOTE]
ok but a dev create cm10.1 rom for MIcromx A110 but it not booting i also want create CM10.1 rom for MIcromax A110
can u help me to create cm10.1 rom plz

paras357 said:
ok but a dev create cm10.1 rom for MIcromx A110 but it not booting i also want create CM10.1 rom for MIcromax A110
can u help me to create cm10.1 rom plz
Click to expand...
Click to collapse
Sorry Buddy, I am not expert in Developing Device. But for working CM builds your Devs has to setup first Device Tree and Kernel Tree and than
need to debug where is problem and what causes bootloops in ROM and need to eliminate step by step problems.

nicsptl said:
Sorry Buddy, I am not expert in Developing Device. But for working CM builds your Devs has to setup first Device Tree and Kernel Tree and than
need to debug where is problem and what causes bootloops in ROM and need to eliminate step by step problems.
Click to expand...
Click to collapse
do u have facebook account Then i will tell u all errors if u have then plz send me and ics device tree are released.......:laugh::good:

paras357 said:
do u have facebook account Then i will tell u all errors if u have then plz send me and ics device tree are released.......:laugh::good:
Click to expand...
Click to collapse
I told you buddy i will not able to help to that much and i dont owe that phone either. you just cant build CM from another device source. it required its particular device specific code. Thats good thing that USB and ADB is working which will help Devs to debug more. (http://forum.xda-developers.com/showthread.php?t=2292308).

nicsptl said:
I told you buddy i will not able to help to that much and i dont owe that phone either. you just cant build CM from another device source. it required its particular device specific code. Thats good thing that USB and ADB is working which will help Devs to debug more. (http://forum.xda-developers.com/showthread.php?t=2292308).
Click to expand...
Click to collapse
ok sir.

@nicsptl
how big size is the cm10.1 prebuild download ?

chongns said:
@nicsptl
how big size is the cm10.1 prebuild download ?
Click to expand...
Click to collapse
did you mean source or prebuilt (prebuilt apk and libs i.e. term.apk) ??
source size is about 8.2 GB may be it varies to 10 GB to download and after extracting it will become 15 GB. and with device tree and kernel source it requires 15-20 GB. and after build rom completed it will it will acquire around 30 GB.
and prebuilt is only about 5 MB.

Building any rom for One XL

Do you know about a ROM that it's not builded for your beloved One XL? Do you want to port it for your device? This easy guide will help you.
Requirements:
A One XL.
A relatively recent computer (Linux, OS X, or Windows) w/a reasonable amount of RAM and about 35 GB of free storage. The less RAM you have, the longer the build will take. Using SSDs results in faster builds than traditional hard drives.
A micro USB cable.
A decent Internet connection & reliable electricity
Some familiarity with basic Android operation and terminology. It would help if you’ve installed custom roms on other devices and are familiar with what a recovery image such as ClockworkMod is, for example. It may also be useful to know some basic command line concepts such as cd for “change directory”, the concept of directory hierarchies, that in Linux they are separated by /, etc.
​HERE IS THE GUIDE.
Installing Build Packages
Open the terminal and type: (for 64-bit&32-bit)
Code:
sudo apt-get install bison build-essential curl flex git-core gnupg gperf libesd0-dev libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop openjdk-6-jdk openjdk-6-jre pngcrush schedtool squashfs-tools xsltproc zip zlib1g-dev
In addition to the above, for 64-bit systems:
Code:
sudo apt-get install g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev
Creating Directories
In order to start building ROMs you'll need to create some directories
Code:
mkdir -p ~/bin
mkdir -p ~/yourworkingdirectory
Installing the REPO command
Enter the following to download the "repo" binary:
Code:
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
Now lets give this the proper permissions to make it runnable:
Code:
chmod a+x ~/bin/repo
Put the ~/bin directory in your path of execution
Make sure that the ~/bin directory you just created is in your path of execution so that you can easily run the repo command even when you're not in ~/bin.
Code:
export PATH=${PATH}:~/bin
Initialize the source repository
Code:
cd yourworkingdirectory
Now you'll need the repo init related to the rom you'd like to build. Here i will insert some of the I used. Anyway to find this you can go the rom's github and search for the manifest (android or platform-manifest).Just choose the right branch.
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
repo init -u git://github.com/LiquidSmooth/android.git -b kitkat
repo init -u git://github.com/SlimRoms/platform_manifest.git -b kk4.4-caf
Download the source code
This will download all the source code to your computer.Prepare to wait a long time while the source code downloads.
Code:
repo sync
Download device,kernel and vendor tree for Liquid
We will use CM ones. Thanks a lot.
Basically we need to add some projects to the download list. To do this we'll need a local_manifest.
Go in the .repo folder in your working directory(it's an hidden folder press ctrl+h). Create a new folder called "local manifests" then double click on it. Now you'll have to create a roomservice.xml file for the most of the ROMs and a slim_manifest.xml for SlimRoms, it's the same thing just the name it's different.
Open this file and paste this inside:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote name="github"
fetch="git://github.com/" />
<project name="CyanogenMod/android_device_htc_evita" path="device/htc/ville" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_htc_s4-common" path="device/htc/s4-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_htc_msm8960-common" path="device/htc/msm8960-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_kernel_htc_msm8960" path="kernel/htc/msm8960" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_htc" path="vendor/htc" remote="github" revision="cm-11.0" />
</manifest>
Now give another:
Code:
repo sync
and wait.
Do some modifications to the .mk files
Since we are using CM device tree we need to modify them for the choosen ROM.
Go into the device folder(device/htc/ville) and do some modifications. I will explain you what i mean using LiquidSmooth as example.
1) Create a new file called vendorsetup.sh . Open it and inside you'll have to write a script to add it to the lunch list.
Code:
add_lunch_combo liquid_evita-userdebug
You can choose if you want an userdebug version of the rom or an eng one just by writing eng instead of userdebug.
2) Now rename cm.mk into liquid.mk(for other ROMs this file should be renamed in a different way. Use an existing device tree to see the correct naming.)
3) Open the .mk file. You'll find something like this:
Code:
# Release name
PRODUCT_RELEASE_NAME := evita
# Boot animation
TARGET_SCREEN_HEIGHT := 960
TARGET_SCREEN_WIDTH := 540
# Inherit some common CM stuff.
$(call inherit-product, vendor/cm/config/common_full_phone.mk)
# Inherit device configuration
$(call inherit-product, device/htc/ville/device_evita.mk)
# Device naming
PRODUCT_DEVICE := evita
PRODUCT_NAME := cm_evita
PRODUCT_BRAND := htc
PRODUCT_MODEL := One XL
PRODUCT_MANUFACTURER := HTC
# Set build fingerprint / ID / Product Name ect.
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=htc_ville BUILD_FINGERPRINT=htc_europe/ville/ville:4.1.1/JRO03C/128506.8:user/release-keys PRIVATE_BUILD
You need to modify some things to make it buildable:
Code:
# Inherit some common CM stuff.
$(call inherit-product, vendor/cm/config/common_full_phone.mk)
becomes:
Code:
# Inherit some common LiquidSmooth stuff.
$(call inherit-product, vendor/liquid/config/common_phone.mk)
To understand the changes you'll have to go in the vendor folder searching the rom specific vendor and open the config folder to see what .mk file you need.
This:
Code:
PRODUCT_NAME := cm_evita
becomes:
Code:
PRODUCT_NAME := liquid_evita
4) Now rename cm.dependencies in liquid.dependencies(SlimRoms does not require this step for unsupported devices.)
Start the build
Code:
source build/envsetup.sh
If you created the vendorsetup.sh in the right way you will read the evita folder.
Code:
lunch
Now you have to choose the number near the evita in the list of the supported devices.
If you have done all in the correct way in your terminal you'll see a page like this:
View attachment 2470228
Build
After lunching you have to start the build using the right command:
For liquid:
Code:
time mka liquid
For others:
Code:
make bacon
make
brunch devicename
Wait some time till the build ends hopefully with no errors.​
Credits: http://wiki.cyanogenmod.org/w/Build_for_ville
and all the experience i got in this 2 months of building.

For most ROMS you'll have some overlays errors.
Just go in the overlay folder linked in the error and open config.xml. Just delete the lines in the error or search in the folder history the commit that you have to revert.
To revert a commit:
Code:
cd intheinteressedfolder
git revert thenumberofthecommit
Here is a screenshot of the what the number/name of the commit is:
View attachment 2470242
Enjoy.

Thank you so much for this guide! I can't tell you how frustrated I was yesterday when I tried to set up Git
For setting up the build packages, can I run that in the bash she'll of Git? I'm on Windows 8, so I don't think cmd will be able to run it
Sent from my One X

pandasa123 said:
Thank you so much for this guide! I can't tell you how frustrated I was yesterday when I tried to set up Git
For setting up the build packages, can I run that in the bash she'll of Git? I'm on Windows 8, so I don't think cmd will be able to run it
Sent from my One X
Click to expand...
Click to collapse
i don't know about this! Yo could try with a Virtual Machine or using jenkins.

Hopefully experienced dev will start work on MIUI AOSP or Touchwiz ROM /Xperia port using this steps ....
Really glad to see this steps for attempted dev..
Thanks Phoenixita
Sent from my One X using XDA Premium 4 mobile app

pandasa123 said:
Thank you so much for this guide! I can't tell you how frustrated I was yesterday when I tried to set up Git
For setting up the build packages, can I run that in the bash she'll of Git? I'm on Windows 8, so I don't think cmd will be able to run it
Sent from my One X
Click to expand...
Click to collapse
Step one if you want to get serious setup dual boot w/ubuntu. Don't even look at doing a VM....just wasting time
Sent from my One X using Tapatalk

jrior001 said:
Step one if you want to get serious setup dual boot w/ubuntu. Don't even look at doing a VM....just wasting time
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
Definitely have to second this! Also, as mentioned in the op, make sure you have enough RAM. CM recommends 4GB. You can do it with less, but it will take a long time... Seriously long time. You would also most likely have to increase your Swap partition size as well with less than 4GB (or create a swap file).
Sent from my One X using XDA Premium 4 mobile app

This is pretty cool and I've seen a few guides before. I've been toying around with this idea for some time. I just need the free time to do it right. I totally agree with the dual boot as well. So much easier than messing around with VM.

Thanks! Now I wish this was out before I made two page text files of notes.
But I moved it to the cloud storage so I am using this whenever I set up build enviroment. I just have to do a little more since I am using Arch based linux.
---------- Post added at 01:10 AM ---------- Previous post was at 01:03 AM ----------
jrior001 said:
Step one if you want to get serious setup dual boot w/ubuntu. Don't even look at doing a VM....just wasting time
Sent from my One X using Tapatalk
Click to expand...
Click to collapse
Or even more serious.
I am dual booting
Windows 8.1 (250 GBs SSD)
+
(arch based Linux on 1TB HDD)
8 GBs ram
i7 3610CQM
Nvididia geforce gtx 660m
Yes i am syncing on a notebook I have used -j30's no problem
I needed help with the local manifest I forgot so thanks as well to guide creator.

right now, I'm installing ubuntu 13.10 on my laptop and I'm looking forward to it...but i was wondering, while installing it on my laptop, it would be nice to see an ubuntu ROM...i don't have the skill set to make one, but I'm just saying

pandasa123 said:
right now, I'm installing ubuntu 13.10 on my laptop and I'm looking forward to it...but i was wondering, while installing it on my laptop, it would be nice to see an ubuntu ROM...i don't have the skill set to make one, but I'm just saying
Click to expand...
Click to collapse
I know rohan32 had at one time attempted it but idk how far he got. I doubt our HTC mess would play nice.
Sent from my One X using Tapatalk

All right, so I think we should say what ROM we want to compile. Just so we don't get like 2 PA
Maybe I'll go back for round 2 with PA. This time from sources, instead of porting it with Windows explorer
Sent from my One X

pandasa123 said:
right now, I'm installing ubuntu 13.10 on my laptop and I'm looking forward to it...but i was wondering, while installing it on my laptop, it would be nice to see an ubuntu ROM...i don't have the skill set to make one, but I'm just saying
Click to expand...
Click to collapse
Here is a good place to start: (primarily for Nexus devices, but gives a great overview of how partitions work with Android and Ubuntu)
https://wiki.ubuntu.com/Touch/DualBootInstallation
And another:
https://wiki.ubuntu.com/Touch/Porting
Please note, I have not personally attempted these builds. With that being said, however, I believe that they will provide you with a good place to start. And by stating that they're good places to start, I mean that you should start reading there. In particular, with the first link, as it goes into detail about modifying partitions.
Very good write ups nonetheless.
Sent from my One X using XDA Premium 4 mobile app

@phoenixita i get this error ....
@brotherross
@jrior001
Which would you like? [aosp_arm-eng] 38
build/core/product_config.mk:238: *** _nic.PRODUCTS.[[
.mk]]: "device/htc/evita/device.mk" does not exist. Stop.
** Don't have a product spec for: 'secret_evita'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
[email protected]:~/android/evita/<secret>$
I found device-vendor.mk and renmaed it to device.mk and still not working
Edit-----
-------
Ok changed it back and went to terminals location and changed it from device-evita.mk to device.mk and now it works lol. oops

Techinstein said:
[email protected]:~/android/evita/<secret>$
:~/android/evita/<secret>$
Click to expand...
Click to collapse
your directories look so out of whack...
if anything it should be secret/device/htc/evita . ...and thats if youre working from within your device folder
youre gonna need to build from your rom directory man..
should be more like
[email protected]:~/<secret>$ . build/envsetup.sh && lunch/brunch/breakfast (whichever the rom uses) && mka bacon (if the rom build needs it)
but thats not even the error. keep messing with names of your make files and make sure the contents within the files lines up properly.

Techinstein said:
@phoenixita i get this error ....
@brotherross
@jrior001
Which would you like? [aosp_arm-eng] 38
build/core/product_config.mk:238: *** _nic.PRODUCTS.[[
.mk]]: "device/htc/evita/device.mk" does not exist. Stop.
** Don't have a product spec for: 'secret_evita'
** Do you have the right repo manifest?
No such item in brunch menu. Try 'breakfast'
[email protected]:~/android/evita/<secret>$
I found device-vendor.mk and renmaed it to device.mk and still not working
Edit-----
-------
Ok changed it back and went to terminals location and changed it from device-evita.mk to device.mk and now it works lol. oops
Click to expand...
Click to collapse
rename device_evita.mk in device.mk.
Edit: ops you did it.

i am trying to compile liquid and getting this error
Which would you like? [aosp_arm-eng] 1
build/core/product_config.mk:250: *** No matches for product "liquid_evita". Stop.
** Don't have a product spec for: 'liquid_evita'
** Do you have the right repo manifest?
thanks

This guy is good.