Database Info

[DEV] How to build cm7 for galaxy y (GT-S5360) ! Ubuntu 32 bits !

Requirements :
OS linux Ubuntu 12.04 32bits
2Gb RAM with 3Gb swap or above
Processor dual core or above
120Gb Harddisk or above
Fast internet connection ( i have no this )
First download this file
Installer SDK and Build packages by squadzone modified for me
you will get installerBuildRomGalmin.sh , run this file via Terminal on Ubuntu!
Code:
chmod a+x ~/installerBuildpackages.sh
installerBuildpackages.sh
Create the Directories
You will need to set up some directories in your build environment.
To create them:
mkdir -p ~/bin
mkdir -p ~/android/system
Install the Repository
Enter the following to download make executable the "repo" binary:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
NOTE: You may need to reboot for these changes to take effect.
Now enter the following to initialize the repository:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b gingerbread
repo sync -j16
Device repo !
clone its
choose branch master
put on device tree or replace totoro folder on device tree
(/device/samsung/totoro)
Vender folder clone its
pu on vendor folder !
(/vendor/samsung/totoro)
Download RomManager
NOTE: This only needs to be done when an update to RomManager is released. If you are-up-to date, you may skip to Building CyanogenMod.
Download RomManager which is needed by the build:
~/android/system/vendor/cyanogen/get-rommanager
Configure Build & Compile
Now, the environment must be configured to build and the ROM compiled, from code, for the Galaxys2.
. build/envsetup.sh && brunch totoro
Notes :
based on tutorial for galaxy mini by squadzone
the device repo created for me ( add credits if you use its )
sorry bad english !
changelog :
1.0
-initial tutorial for cm7 galaxy y ( may need some modifications! )

reserved for more updates if necessary !

Thanks for this buddy :good:
OFF : Any news about CM9 ?

wow.. reserved sir whitexp.. long time no post? D

I WIIL TRY IT BOR
By SOMKLL

But this Cyanogen has the same bugs,right?

whitexp what about cm9 ? when will u continue xD
and great guide
This message is COPYRIGHTED to me and stolen from:My post

Cyanogen 7/9 only get developed again when the gpu driver become released

Awesome tutorial sir...

Just one question...if we still have GPU restrictions while compiling CM7/9/10, then what is the use of the tutorial? Is there any update I should be aware of?
I'm not at all disrespecting OP's efforts...I respect him...he is doing commendable job for this device..hat's off! this question is just out of curiosity!

everyone needs brodcom drivers,without it nothing is possible.

PREMOLIKES said:
everyone needs brodcom drivers,without it nothing is possible.
Click to expand...
Click to collapse
Well it's still possible to boot it, so yeah. It's a handy tutorial, LEARN to appreciate guys! That's the reason why SGY devs are leaving, 1 by 1, because of you people that whine! Thank them for the effort!

PREMOLIKES said:
everyone needs brodcom drivers,without it nothing is possible.
Click to expand...
Click to collapse
Without this kind of tutorial and with gpu drivers will you make cm7 for sgy????

Awesome tutorial sir!!

Tutotial is good.no doubt.I said drivers are a stumbling block.

PREMOLIKES said:
Tutotial is good.no doubt.I said drivers are a stumbling block.
Click to expand...
Click to collapse
Drivers will be here soon! I am gettin ready already!
Sent from my GT-S5360 using XDA

Mohamed.Anwar said:
Thanks for this buddy :good:
OFF : Any news about CM9 ?
Click to expand...
Click to collapse
what gaming rom r using

Exellent tut buddy.:thumbup::thumbup:
sent while doin' some burnouts

hell_lock said:
Drivers will be here soon! I am gettin ready already!
Sent from my GT-S5360 using XDA
Click to expand...
Click to collapse
really?
broadcom will release their drivers or are you just joking around because i just installed windows again on my pc ...

cosminx13 said:
really?
broadcom will release their drivers or are you just joking around because i just installed windows again on my pc ...
Click to expand...
Click to collapse
A suggestion from me.you can use both os like dualboot.for info about this try google
MANY GREEEEETZ!!!

[Guide][cm7] How to build cyanmobile from source

Hello guys i'm here with my first guide of how to build cyanmobile from source for galaxy fit ......
As you all might know cyanmobile went opensource thanks to squadzone now we can compile it from source with our own modifiactions.....
Requirements
1)Linux machine (recommended 64bit and ubuntu) with atleast 50gb free space
2)Common sense of how to use google and fix errors
3)Basic knowledge of git and its commands
4)A possibilty of bricking your fit
5)A fast and stable internet connection
now lets get started
Assuming we have linux installed
installing required build packages
from terminal
HTML:
sudo apt-get install git-core gnupg flex bison gperf libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools build-essential zip curl libncurses5-dev zlib1g-dev sun-java6-jdk pngcrush schedtool
Note:- All the packages are important dont skip any of them
now making the directories to download the source
HTML:
mkdir -p ~/bin
mkdir -p ~/android/system
here mkdir stands for make directory
~ refers to your home folder (incase if you are a beginner)
Next
making the repo command executable
copy paste this terminal
HTML:
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
Reboot your system after executing this
This defines the repo command or the repo command usable on your machine
chmod is giving permissions to the folder a+x is the permissions given don't go deep into this.
Next
Downloading the source
i will be referring execute to copy pasting in the terminal
HTML:
repo init -u git://github.com/CyanMobile/android_cyanmobile.git -b gingerbread
now
repo sync
alternatives
repo sync -jx
here x can be anything depends on your internet speed ther will x number of simultaneous download if you use the arguement
like if you use
repo sync -j4
There will 4 downloads going on simulatneously
Next after the source has been downloaded you will find someting like this...
syncing working tree 100
now you have the source downloaded
Preparing the build environment
install java jdk6 or jdk 5 using this tutorial
http://codingforme.wordpress.com/2012/05/14/installing-oracle-java-jdk-6-or-7-on-ubuntu-12-04/
Install the android sdk following this tutorial
http://www.howtoforge.com/setting-up-an-android-app-build-environment-with-eclipse-android-sdk-phonegap-ubuntu-11.04
not testsed on jdk 7 so better use 6 or 5
fix its path using "export PATH=$PATH:"ur sdk path""
ur sdk path depends on where you install it
install adb using this guide
http://forum.xda-developers.com/showthread.php?t=921169
Connect your phone with usb debugging enabled and execute this
preferable do this when you are on a cm based rom ..
HTML:
adb devices
if you see something like this its working for you
HTML:
List of devices attached
S5670efac482b device
now go to device > samsung > beni execute extract-files.sh as root use sudo and drag that to terminal and hit enter
now cd into the root of your source folder
HTML:
cd ~/android/system
then
HTML:
source buid/envsetup.sh
HTML:
lunch
you will see all the build properties something like this
HTML:
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=2.3.8
TARGET_PRODUCT=cyanogen_beni
TARGET_BUILD_VARIANT=eng
TARGET_SIMULATOR=false
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv6-vfp
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=GINGERBREAD
now type make -jx otapackage
x depends on your hardware more it is faster the build
you will find the built one in out/samsung/beni /cm--xxx.zip
Flash it and enjoy
credits
wilfredcool007
vishwanthptl
sakindia123
yajnab
ravi h basawa
adit_pat
squadzone
google
xda
without these guys it wouldnt be possible pree thanks for them plz

1 st reserved

Thumbs up
Nice guide ajay :good:

Its same as the building of cyanogenmod. But to continue this thread u have to first build a copy too for promoting this and the errors while building , so start repo syncing. I am syncing the jelleybean now.
Best of luck for this thread

yajnab said:
Its same as the building of cyanogenmod. But to continue this thread u have to first build a copy too for promoting this and the errors while building , so start repo syncing. I am syncing the jelleybean now.
Best of luck for this thread
Click to expand...
Click to collapse
i am too doing a list of common errors encountered and will update the op

speed_bot said:
i am too doing a list of common errors encountered and will update the op
Click to expand...
Click to collapse
I'm on a low bandwidth. Can u please make a highly compressed .uha or Uharc compression package of the cyanmobile so that i can also help u in building this. not having the cm7 sources too. It cn be a grat sart for making a more modified cyanombile than squadzone.

yajnab said:
I'm on a low bandwidth. Can u please make a highly compressed .uha or Uharc compression package of the cyanmobile so that i can also help u in building this. not having the cm7 sources too. It cn be a grat sart for making a more modified cyanombile than squadzone.
Click to expand...
Click to collapse
dude do this remove all devices and sync only beni and tass the source is small and use aosps prebuilt the download is only 3gb bro...and can plz upload the prebuilt directory for me i will upload frameworks and devices by tmrw for you..........plz i need the prebuilt directory

You rock man, keep up the good work.. thank you..

praveen_kalasa said:
You rock man, keep up the good work.. thank you..
Click to expand...
Click to collapse
thanks bro..

Nice Work
Very useful Guide for Begineers. Keep this thread updated

RishabhAd said:
Very useful Guide for Begineers. Keep this thread updated
Click to expand...
Click to collapse
but only few people responded to it so what can i update with
??

hi.i am trying to build from your how to...will report ...thank you for this...

desalesouche said:
hi.i am trying to build from your how to...will report ...thank you for this...
Click to expand...
Click to collapse
im already compiling for your device

How to build cyanmobile x from source for p500?
thanks

x-dira said:
How to build cyanmobile x from source for p500?
thanks
Click to expand...
Click to collapse
just choose p500 during lunch

building for huawei u8800pro and u8860
hi can i build with 3.0.87 kernel?
or should i use a 2.6.35 one?
can we build only gingerbread or is there possibility to build 4.2.2?
thank you

Nice guide :thumbup:
I'll try it for GalaxyW

desalesouche said:
hi can i build with 3.0.87 kernel?
or should i use a 2.6.35 one?
can we build only gingerbread or is there possibility to build 4.2.2?
thank you
Click to expand...
Click to collapse
u need kernel 2.6 for gb 3.x supports only ics and above.android 4.2.2 is buildable provided u have all drivers and other binaries

K_TECH said:
Nice guide :thumbup:
I'll try it for GalaxyW
Click to expand...
Click to collapse
dude this guide is for galaxy fit but u can build it for w or any device by using the tress specific for that device.

Bump
I wanna try to port this ROM to the LG e739, but I have no idea what to do at this point. I downloaded the sources, but the device tree I have from cm7.2 is just plain, it lacks everything else the other devices have and to be honest I'm overwhelmed. Any help is greatly appreciated

[GUIDE] Compile CM from source, source basics & FAQ - Very detailed and noob friendly

[GUIDE] Compile CM from source, source basics & FAQ - Very detailed and noob friendly
Hey guys, I know there is already a tutorial about compiling CyanogenMod by sakindia123 but it requires basic Linux knowdlegde and he missed some things. I wrote this tutorial very detailed and simple.
This Guide have 4 parts:
1. How to compile CyanogenMod from source
2. Hardware Requirments and using SWAP memory
3. CyanogenMod source and device tree basics
4. FAQ
Click to expand...
Click to collapse
Before we start, I would like to thank these guys:
sakindia123, derefas, lirokoa, cute_prince - for amazing work on CM7-10.1 and Kernel 3.0
Nihar G. and bhargz16 that never refused to help me
How to compile CyanogenMod from source​
Lets assume you are new in Linux world and you just installed a fresh Ubuntu installation.
I will use:
- Ubuntu 12.10 64bit
- CyanogenMod 10.1 (sakindia123 device tree) - because its newest, and currently WIP, so its exciting to get new bulid with something fixed before release!
- Kernel 3.0.16 for Pico (sakindia123 github tree)
Lets get it started.
1. Open the Terminal (Press CTRL+ALT+T).
2. Get rid of administrator permissions ****.
Type:
sudo su
then type your password you set up during Ubuntu installation (password will be invisible) and hit enter
Click to expand...
Click to collapse
3. Download, install and setup Java:
add-apt-repository ppa:webupd8team/java
apt-get update
apt-get install oracle-java6-installer
apt-get install oracle-java6-set-default
Click to expand...
Click to collapse
4. Install a needed packages:
apt-get install git-core gnupg flex bison gperf build-essential \
zip curl zlib1g-dev libc6-dev libncurses5-dev x11proto-core-dev \
libx11-dev libreadline6-dev libgl1-mesa-dev tofrodos python-markdown \
libxml2-utils xsltproc pngcrush gcc-multilib lib32z1 schedtool
Click to expand...
Click to collapse
5. Download a Google Repo tool. Type these commands:
mkdir ~/bin
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
Click to expand...
Click to collapse
6. Reboot your computer. (No need for sudo su after reboot)
If you are building for HTC Explorer
7. Initalize the CyanogenMod 10.1 repository (with included pico stuff):
mkdir -p ~/CM10.1/android/system
cd ~/CM10.1/android/system
PATH=~/bin:$PATH
repo init -u git://github.com/TeamPico/manifest -b cm-10.1
Click to expand...
Click to collapse
8. Start source downloading (repository syncing):
repo sync
Click to expand...
Click to collapse
9. Get Terminal Emulator prebulit APK:
cd ~/CM10.1/android/system/vendor/cm/
./get-prebuilts
Click to expand...
Click to collapse
10. Start compiling bulid!
. build/envsetup.sh
brunch cm_pico-userdebug -jX
X is a number of your CPU cores + 1 or 2
Click to expand...
Click to collapse
Your bulid will be located at /CM10.1/android/system/out as cm-10.1-year/month/date-UNOFFICIAL-pico.zip
If you are building for other devices
7. Initalize the CyanogenMod 10.1 repository:
mkdir -p ~/CM10.1/android/system
cd ~/CM10.1/android/system
PATH=~/bin:$PATH
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.1
Click to expand...
Click to collapse
8. Start source downloading (repository syncing):
repo sync
Click to expand...
Click to collapse
9. Get Terminal Emulator prebulit APK:
cd ~/CM10.1/android/system/vendor/cm/
./get-prebuilts
Click to expand...
Click to collapse
How to get vendor, kernel, and device tree - search for developers github, its ofter mentioned on dev-thread or his xda profile..
manufacturer - htc, samsung,lge...
codename - device model codename (codename you can easily find on name of github repos of device tree,vendor and kernel)
Examples:
Explorer - pico
Desire - bravo
Galaxy Mini - tass
Galaxy Mini 2 - jena
Nexus 4 - mako
For some devices, example some LGs it can be model number like LG Optimus Me - p350
10. Setup a vendor tree:
Download the vendor tree and extract proprietary folder inside <something>-master folder in archive to /CM10.1/android/system/vendor/manufacturer/codename (you need to manually create folders)
Click to expand...
Click to collapse
11. Setup a device tree:
Download the device tree and extract files and folders inside <something>-master folder in archive to /CM10.1/android/system/device/manufacturer/codename (you will need to manually create folders)
Click to expand...
Click to collapse
12. Setup a kernel source:
Download the kernel source and extract files and folders inside <something>-master folder in archive to /CM10.1/android/system/kernel/manufacturer/codename (you will need to manually create folders)
Click to expand...
Click to collapse
13. If you are building for older device you will probably need to add display legacy support, as it's dropped in CM10.1:
Download the legacy display zip and extract files and folders inside android_hardware_qcom_display-legacy-cm-10.1 folder in archive to /CM10.1/android/system/hardware/qcom/display-legacy folder (you will need to manually create folder)
Click to expand...
Click to collapse
14, If you are building qualcomm (msm) device, apply singleton.h patch
Type in Terminal:
cd ~/CM10.1/android/system/frameworks/native
git fetch http ://review.cyanogenmod.org/CyanogenMod/android_frameworks_native/refs/changes/69/30269/1 && git format-patch -1 --stdout FETCH_HEAD
(delete space between http and :
Click to expand...
Click to collapse
15. Start compiling bulid!
. build/envsetup.sh
brunch cm_codename-userdebug -jX
X is a number of your CPU cores + 1 or 2
Click to expand...
Click to collapse
Your bulid will be located at /CM10.1/android/system/out as cm-10.1-year/month/date-UNOFFICIAL-codename.zip
If I missed something, feel free to report!

Hardware Requirments and using SWAP Memory​
Compiling uses alot of CPU power, but when you run out of RAM memory, you will get "Killed." error. No, you dont need to buy more RAM. You can use SWAP. Quickest and easiest way is to format USB drive to linux-swap and enable SWAP.
Less than 4GB of RAM - You will need SWAP
4GB - Just enough, but if you want to do something other on PC during compiling, its recommemend to make SWAP, just in case.
More than 4GB - You dont need SWAP.
1. Optionally, Copy your USB files to PC as a backup.
2. Go to GParted (preinstalled on Ubuntu)
3. Right-click on your USB drive -> Format -> linux-swap
4. Right-click on your USB drive -> Swap-on
5. Done!
After you are done right-click on your USB drive -> Swap-off, reformat your partition to FAT32 or NTFS and restore data you copied before (if you have any)

CyanogenMod Source and Device Tree basics​
Basic source folders:
/packages - apps
/frameworks - framework (UI look)
/kernel - kernel source folder when using inline kernel buliding (can be changed in BoardConfig.mk, and I'm going to explain that later in this post)
/device - device config
/hardware - drivers for display. audio etc...
What is BoardConfig?
It's a file where you setup pathes to files and enable/disable stuff, its very easy to understand - https://github.com/sakindia123/cm10.1_htc_pico/blob/master/BoardConfig.mk
--
How to use prebulit kernel:
1. Unpack boot.img using boot image tools (check sakindia123's compiling tutorial for step-by-step unpacking boot.img)
2. Rename zimage to 'kernel'
3. Put it in any folder u like you like (example: /prebulitkernel)
4. In BoardConfig.mk add this:
TARGET_PREBUILT_KERNEL := /prebulitkernel/kernel
and comment out these lines:
TARGET_KERNEL_SOURCE := kernel/htc/pico
TARGET_KERNEL_CONFIG := pico_defconfig
TARGET_KERNEL_CUSTOM_TOOLCHAIN := arm-eabi-4.4.3
Click to expand...
Click to collapse
5. Done!
--
How to remove ringtones, video editor, CM wallpapers from bulid:
1. Go to device/releasetools/extras.txt
2. Delete anything you don't want/doesn't need. So easy
--
Where are "bulid.prop tweaks"?
bulid.prop settings is located in device/system.prop
--
What is pico.mk?
In pico.mk (device/pico.mk) you can:
- define what libs (drivers) will be compiled (PRODUCT_PACKAGES)
- add prebulits (PRODUCT_COPY_FILES)
you add them in format: path-to-file-in-source: path-to file in compiled bulid (zip),
example: device/htc/pico/prebuilt/etc/media_codecs.xml:system/etc/media_codecs.xml
- change some usb settings (ADDITIONAL_DEFAULT_PROPERTIES)
- play with some "misc" settings (PRODUCT_PROPERTY_OVERRIDES)
- Set default resolution (PRODUCT_AAPT_CONFIG := ... and PRODUCT_AAPT_PREF_CONFIG := ...)
I'm not an expert, If I made some mistake, feel free to report, or tell if you have something interesting I can add!

FAQ
Frequently asked questions​
Q: What's the repository size?
A: CM9 - 4.9GB
CM10 - 9.6GB
CM10.1 - cca. 16GB
Q: Can I compile any other ROM than CyanogenMod with this tutorial?
A: Yes, you will need to, of course, repo init other repo, and maybe change few things in device tree, and probably you can skip part with adding legacy display and patching singleton.
Q: I have "_____ command not found error."
A: Make sure you done all steps, are you in right directory, and did you downloaded all packages.
Q: I have "Killed." error during compiling.
A: Check if you met have enough RAM (read 2nd post of this thread)
Q: I have any other error during compiling
A: Post your problem on this thread

Re: [TUT][REMAKE] Compile CyanogenMod from source
Nice work bro...
Sent from my Nexus 7

Re: [TUT][REMAKE] Compile CyanogenMod from source - Very detailed and noob friendly
Great work bro, very helpfull! :thumbup:
Sent from my HTC Explorer A310e using xda app-developers app

Re: [TUT][REMAKE] Compile CyanogenMod from source - Very detailed and noob friendly
Cm10 will complile on 32 bit system?
Sent from my HTC Explorer A310e using xda app-developers app

Re: [TUT][REMAKE] Compile CyanogenMod from source - Very detailed and noob friendly
wmapt said:
Cm10 will complile on 32 bit system?
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
no rom will compile on 32 bit system... you can only compile kernels on 32 bit systems..
Sent from my Nexus 7

Re: [TUT][REMAKE] Compile CyanogenMod from source - Very detailed and noob friendly
Awesome work bro. Glued to this thread. BTW ICS and higher require 64 bit right ?
Sent from my HTC Explorer A310e using xda app-developers app

Re: [TUT][REMAKE] Compile CyanogenMod from source - Very detailed and noob friendly
akshat.shenoy said:
Awesome work bro. Glued to this thread. BTW ICS and higher require 64 bit right ?
Sent from my HTC Explorer A310e using xda app-developers app
Click to expand...
Click to collapse
Tnx. AFAIK Yes.
Sent from a chocolate cake.

Re: [TUT][REMAKE] Compile CyanogenMod from source - Very detailed and noob friendly
+1 brooo,
How much size of the stuffs like repository and other things u mention to download in various steps....based on that I can manage to download.....
Sent from my HTC Explorer A310e using xda premium

Re: [TUT][REMAKE] Compile CyanogenMod from source - Very detailed and noob friendly
galaxyfreak said:
Hey guys, I know there is already a tutorial about compiling CyanogenMod by sakindia123 but it requires basic Linux knowdlegde and he missed some things. I wrote this tutorial very detailed and simple.
Before we start, I would like to thank these guys:
sakindia123, derefas, lirokoa, cute_prince - for amazing work on CM7-10.1 and Kernel 3.0
Nihar G. and bhargz16 that never refused to help me
Lets assume you are new in Linux world and you just installed a fresh Ubuntu installation.
I will use:
- Ubuntu 12.10 64bit
- CyanogenMod 10.1 (sakindia123 device tree) - because its newest, and currently WIP, so its exciting to get new bulid with something fixed before release!
- Kernel 3.0.16 for Pico (sakindia123 github tree)
Lets get it started.
1. Open the Terminal (Unity Dash Search, just type terminal and hit enter)
2. Get rid of administrator permissions ****.
Type:
3. Install a needed packages:
4. Download a Google Repo tool. Type these commands:
5. Reboot your computer.
6. Initalize the CyanogenMod 10.1 repository:
7. Start source downloading (repository syncing):
9. Get Terminal Emulator prebulit APK:
10. Setup a vendor tree:
11. Setup a device tree:
12. Setup a kernel source:
13. Add display legacy support, as it's dropped in CM10.1:
14. Start compiling bulid!
Your bulid will be located at /android/out as cm-10.1-year/month/date-UNOFFICIAL-pico.zip
If I missed something, feel free to report!
Click to expand...
Click to collapse
Plzz provide link to download Ubuntu n every single thing required to compile then it will be noon friendly
Sent from my HTC Explorer A310e using xda premium

Re: [TUT][REMAKE] Compile CyanogenMod from source - Very detailed and noob friendly
abhiparmar92 said:
+1 brooo,
How much size of the stuffs like repository and other things u mention to download in various steps....based on that I can manage to download.....
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse
the sources all vary in size... Ics sources are generally limited anywhere upto 10gb.. Cm9 is 4. 9..
Cm10 onwards, the source sizes go upto 15 gb...
Sent from my Nexus 7
---------- Post added at 10:04 AM ---------- Previous post was at 10:03 AM ----------
maxy! said:
Plzz provide link to download Ubuntu n every single thing required to compile then it will be noon friendly
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse
i dont think it was meant to be noob friendly..
But anyways, you can dowload ubuntu over ar ubuntu.com..
whichever version you download, just make sure its 64 bit..
Sent from my Nexus 7

Re: [TUT][REMAKE] Compile CyanogenMod from source - Very detailed and noob friendly
Really gr8 work bro !!!
Sent from my HTC Explorer A310e using xda premium

Re: [TUT][REMAKE] Compile CyanogenMod from source - Very detailed and noob friendly
bhargz16 said:
the sources all vary in size... Ics sources are generally limited anywhere upto 10gb.. Cm9 is 4. 9..
Cm10 onwards, the source sizes go upto 15 gb...
Sent from my Nexus 7
---------- Post added at 10:04 AM ---------- Previous post was at 10:03 AM ----------
i dont think it was meant to be noob friendly..
But anyways, you can dowload ubuntu over ar ubuntu.com..
whichever version you download, just make sure its 64 bit..
Sent from my Nexus 7
Click to expand...
Click to collapse
Not necessarily my friend i read somewhere 32 bit can also be used but will req a little more things to do the same job
Sent from my HTC Explorer A310e using xda premium

Re: [TUT][REMAKE] Compile CyanogenMod from source - Very detailed and noob friendly
immortal_yash said:
Not necessarily my friend i read somewhere 32 bit can also be used but will req a little more things to do the same job
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse
but thats only for upto froyo.. For gb and above, 32 bit cant handle it..
Sent from my Nexus 7

Re: [TUT][REMAKE] Compile CyanogenMod from source - Very detailed and noob friendly
bhargz16 said:
but thats only for upto froyo.. For gb and above, 32 bit cant handle it..
Sent from my Nexus 7
Click to expand...
Click to collapse
Dude i was building mini cm 9 on Ubuntu 11.10 32 bit and everything worked except when there was a motherboard failure
Sent from my HTC Explorer A310e using xda premium

Re: [TUT][REMAKE] Compile CyanogenMod from source - Very detailed and noob friendly
immortal_yash said:
Dude i was building mini cm 9 on Ubuntu 11.10 32 bit and everything worked except when there was a motherboard failure
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse
hmmmm... Thats weird..
Coz google themselves recommend 64 bit for gb n above
Sent from my Nexus 7

Re: [TUT][REMAKE] Compile CyanogenMod from source - Very detailed and noob friendly
bhargz16 said:
hmmmm... Thats weird..
Coz google themselves recommend 64 bit for gb n above
Sent from my Nexus 7
Click to expand...
Click to collapse
They recommend but we can use 32 bit as well just a little more downloading will be req
Sent from my HTC Explorer A310e using xda premium

Re: [TUT][REMAKE] Compile CyanogenMod from source - Very detailed and noob friendly
immortal_yash said:
They recommend but we can use 32 bit as well just a little more downloading will be req
Sent from my HTC Explorer A310e using xda premium
Click to expand...
Click to collapse
i've never tried 32 for rom compiling..
Get that info here.. So op can add it..
Sent from my Nexus 7

Kernel compilation error

almost compiled but one error????
make[1]: Nothing to be done for 'dtbs'
any solution...
and
zImage is not there. only "Image" and "Image.gz" present there
is "Image" is zImage? how to check that??
Thank you..
kernel source - Xiaomi mi4i official source
toolchain- NDK version 4.9
Ubuntu 64 bit?

[email protected] said:
OP
Click to expand...
Click to collapse
Change module to be y at defconfig
Also image it's the kernel
Image vs zImage ... You can google it
Also ,micode source code it's full of bugs

faizauthar12 said:
Change module to be y at defconfig
Also image it's the kernel
Image vs zImage ... You can google it
Also ,micode source code it's full of bugs
Click to expand...
Click to collapse
Yeah what he said. Checkout these repos if you need to compile a kernel:
http://gitlab.com/webhaikal/SenseiFerrari
http://github.com/Ferrari-Dev-Team/android_kernel_xiaomi_ferrari

haikalizz said:
Yeah what he said. Checkout these repos if you need to compile a kernel:
[url]http://gitlab.com/webhaikal/SenseiFerrari[/URL]
[url]http://github.com/Ferrari-Dev-Team/android_kernel_xiaomi_ferrari[/URL]
Click to expand...
Click to collapse
yeah i gone through your sensie kernel repo and found that i have to use dtbToolCM to make boot.img so i did it and stuck here...
DTB combiner:
Input directory: '/home/rushabh/KernelDevelopment/Xiaomi_Kernel_OpenSource-ferrari-l-oss/arch/arm64/boot/dts/'
Output file: '/home/rushabh/KernelDevelopment/Xiaomi_Kernel_OpenSource-ferrari-l-oss/arch/arm64/boot/dt.img'
Searching subdir: /home/rushabh/KernelDevelopment/Xiaomi_Kernel_OpenSource-ferrari-l-oss/arch/arm64/boot/dts/include/ ...
=> Found 0 unique DTB(s)
as i have read various threads but can not able to fix this. i have used dtbToolCm and dtbtool (version -3 and -2) also same result..
Really i should had not start making my first kernel with MI...
or it will make me learn more and more..
hahahaha:silly:

the easy steps to make a new kernel
use the entirely CM source code
then just type "make bootimage"

[REFERENCE] LineageOS with full Substratum support - Closed until Oreo

Introduction
Hello everyone! I am one of the members of the Substratum team and we constantly have people asking how to add support to ROMs. I have made a repo regarding all of our documentation here, in which I include steps to add support. Normally, it is easy to add support to most ROMs; however, Lineage has made some underlying changes to AssetManager and PackageManager that makes adding the patches a little difficult if you do not have some solid programming background. To help people who are familiar with building and git but not necessarily Java and C, I have created a series of reference repos that you can use to cherry pick the commits into your forks or local builds to easily have theme support! Please read this entire thread, I go over a lot of info and I will be upset if you do not read it all enjoy!
Information
Substratum currently uses OMS (Overlay Manager Service), Sony's theming framework, that allows for real time swapping of resources via overlays. This is accomplished through a series of commits, which include the core OMS framework, exposures so themes can overlay hardcoded resources, and a second set of framework commits to allow Substratum to do all of its operations without root access. You can read more about this in the main Substratum thread. We have made it so that it is easy to merge OMS and all of our exposures on AOSP or close to AOSP ROMs. Lineage is not one of those ROMs as they have based on CAF, which modifies AOSP to suit a large range of devices. Lineage has also modified core components like Package Manager for security reasons and some of those changes will conflict with OMS changes. I have merged the changes on top of Lineage and verified everything has worked properly. I will continue to maintain this as long as time permits. I plan to try and rebase the changes every day on Lineage updates but I may need to do it weekly depending on how much free time I have.
What do I have to do?
All you need to do is merge the changes from our repos into yours! Link: https://github.com/LineageOMS
This can be done in one of four ways (ONLY ONE):
1. Cherry-pick our changes
This will be the best option if you have forked Lineage and made any changes (basically basing a ROM on Lineage). Once you have merged these changes, you can track our progress on Gerrit and merge patches as they come down. The patches you need to pick will be either "committed with nathanchance" or "nathanchance committed".
Code:
git fetch <url> cm-14.1
git cherry-pick <first_sha1>^..<second_sha1>
Example:
Code:
git fetch https://github.com/LineageOMS/android_frameworks_base cm-14.1
git cherry-pick d6b3f93bec61769fab7ebf31e78bf0acb42bb2e6^..1e00bba63c5b6facec5a8beef1bb39863b251183
2. Pull our changes
This will be a good option if you have either forked Lineage and made no changes or do straight builds from their repos, as this will fetch and merge automatically. You can still cherry-pick if you want but this should result in no conflicts (basically a clean merge).
Code:
git pull <url> cm-14.1
Example:
Code:
git pull https://github.com/LineageOMS/android_frameworks_base cm-14.1
3. Sync using our manifest
This is good if you are just building straight from Lineage's sources. The one issue with this is you will be fully reliant on me for updates; Lineage often merges patches across a few repos and you may run into errors if ALL repos are not up to date.
From the top of your Lineage repo folder:
Code:
mkdir LineageOMS && cd LineageOMS
repo init -u https://github.com/LineageOMS/android -b cm-14.1 --no-clone-bundle --depth=1
repo sync -j$( nproc --all ) --force-sync -c --no-clone-bundle --no-tags --optimized-fetch --prune
4. Use the provided local manifest
This is good if you are just building straight from Lineage's sources. As with the above option, you MAY run into errors if a patch is merged across several repos and I have not update my repos with the proper changes.
From the top of your Lineage repo folder:
Code:
cd .repo
mkdir -p local_manifests
cd local_manifests
wget https://raw.githubusercontent.com/LineageOMS/local_manifest/master/substratum.xml
cd ../..
repo sync --force-sync
4. Use the provided local manifest
I would only recommend doing this if you are building straight from Lineage's sources and willing to build only when I rebase my changes. Lineage often merges patches across several repos and without every repo being up to date, you may get build errors.
From the top of your Lineage repo folder:
Code:
cd .repo
mkdir -p local_manifests
cd local_manifests
wget https://raw.githubusercontent.com/LineageOMS/local_manifest/master/substratum.xml
cd ../..
repo sync --force-sync
That's it! Super easy as it should be.
Support
If you run into any issues with merging patches, ask in this thread.
If you PM me on XDA... I will ignore you.
If you PM me on Hangouts... I will ignore you.
If you PM me on Telegram... I will ignore you.
See a pattern? This thread is the place for support, nowhere else.
If you run into issues with using Substratum itself, ask in the main thread.

Great!

This is great!

wew...this is great bro

This is great!

Wow, great :laugh:

Awesome!

Awesome, build successfully. Thx.
Finding beautiful themes now.
通过我的 Mi 5s Plus 上的 Tapatalk发言

Great it can't be easier thn this.

Is it possible to do for this build. Can anyone HELP me with video tutorial plz..
---------- Post added at 06:56 AM ---------- Previous post was at 06:41 AM ----------
akhilnarang said:
Great!
Click to expand...
Click to collapse
Iam using HTC desire 816.i have flash this build cm14.1-20161120-unofficial-a5dwg can u plz help me to how to do this.

actually i didn't understand......can anyone explain it in simple words.......am not a tech guy, am just a beginner in this world of custom ROM.

nareshnani142 said:
Is it possible to do for this build. Can anyone HELP me with video tutorial plz..
---------- Post added at 06:56 AM ---------- Previous post was at 06:41 AM ----------
Iam using HTC desire 816.i have flash this build cm14.1-20161120-unofficial-a5dwg can u plz help me to how to do this.
Click to expand...
Click to collapse
You need to build for yourself, you cannot do this to an already compiled build.
Sachin ET said:
actually i didn't understand......can anyone explain it in simple words.......am not a tech guy, am just a beginner in this world of custom ROM.
Click to expand...
Click to collapse
Unfortunately, if you cannot understand what I wrote, you need to do a lot of research into the world of git and custom ROMs, I cannot provide that to you in this thread. A good place to start would be my guide on how to compile from source: https://github.com/nathanchance/Android-Tools/raw/master/Guides/Building_AOSP.txt

I made my own manifest to build lineage with OMS here: https://github.com/DespairFactor/android

@cvxda @xamio

Sachin ET said:
actually i didn't understand......can anyone explain it in simple words.......am not a tech guy, am just a beginner in this world of custom ROM.
Click to expand...
Click to collapse
Bro lets wait our dev will do this for us,,,,

Thanks
[Thanks bro!!]
[¡Gracias, viejo!]

Firstly thanks for this guide. I followed the THIRD way to add Substratum Support in my ROM and I'm getting some error Permissive domains not allowed and the make fails. I am building LineageOS for Moto G4 Plus (athene). Error: https://hastebin.com/keyacadezi.vbs
Full output: https://paste.ee/p/GvyYN Anyone who can help in this, I'd be thankful
Device tree: https://github.com/tywinlannister7/android_device_motorola_athene
Kernel tree: https://github.com/LineageOS/android_kernel_motorola_msm8952

tywinlannister7 said:
Firstly thanks for this guide. I followed the THIRD way to add Substratum Support in my ROM and I'm getting some error Permissive domains not allowed and the make fails. I am building LineageOS for Moto G4 Plus (athene). Error: https://hastebin.com/keyacadezi.vbs
Full output: https://paste.ee/p/GvyYN Anyone who can help in this, I'd be thankful
Device tree: https://github.com/tywinlannister7/android_device_motorola_athene
Kernel tree: https://github.com/LineageOS/android_kernel_motorola_msm8952
Click to expand...
Click to collapse
Delete the file "sepolicy/themeservice_app.te" in your device tree. I removed CMTE's sepolicy as ours conflicts.

dont work with touchwiz roms or?

gtaelbordo said:
dont work with touchwiz roms or?
Click to expand...
Click to collapse
Are TouchWiz ROMs LineageOS? Then no, this is not applicable for TouchWiz ROMs. If you mean Substratum as a whole, probably not as TouchWiz is nowhere close to stock Android and this should be asked in the main Substratum thread.
Sent from my Nexus 6P using XDA Labs