Database Users

CM10 Building guide + Linux + troubleshooting

Guide to build cm10 for the n7000. It works for sure on linux.
If you want to build for another samsung phone replace all n700's with the new model number
First of all u need to:
Initialize you're build environment.
Follow the steps descibed here: Linux is at the top.
http://source.android.com/source/initializing.html //if you're on ubuntu 12.04 or higher skip the Installing the JDK part
Now do sudo apt-get install libsdl1.2-dev libesd0-dev libwxgtk2.6-dev squashfs-tools pngcrush schedtool
Setting up android tools:
cd ~
mkdir android-SDK
cd android-SDK
wget http://dl.google.com/android/android-sdk_r20.0.3-linux.tgz
tar -xvzf android-sdk_r20.0.3-linux.tgz
cd tools
./android update sdk -u --filter platform-tools,android-16,extra-android-support
export PATH=$PATH:~/android-SDK/android-sdk-linux/platform-tools
export PATH=$PATH:~/android-SDK/android-sdk-linux/tools
Now add the 2 lines above to ~/.bashrc using your favourite text editor
Getting the source:
mkdir -p ~/bin
mkdir -p ~/android/system
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
export PATH=$PATH:~/bin
Now add the line above to ~/.bashrc using your favourite text editor
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
create ~/android/system/.repo/local_manifest.xml using this content: //If you want the latest kernel read the bottum of post 3 or read the comments.
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="teamhacksung/buildscripts" path="buildscripts" remote="github" revision="jellybean">
<copyfile dest="build.sh" src="samsung/build.sh" />
</project>
<project name="CyanogenMod/android_device_samsung_n7000" path="device/samsung/n7000" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_device_samsung_galaxys2-common" path="device/samsung/galaxys2-common" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_kernel_samsung_smdk4210" path="kernel/samsung/smdk4210" remote="github" revision="jellybean" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="jellybean" />
</manifest>
cd ~/android/system/
repo sync -j16
cd ~/android/system/device/samsung/n7000/
Connect your galaxy note to the PC
./proprietary-files.sh
If you want to change the boot animation to the CM10 one or a different one read the last lines of post 3.
Building:
If you want to built android with a costum kernel you can use: export TARGET_PREBUILT_KERNEL=<path to zImage>/zImage
cd ~/android/system
repo sync -j16
./build.sh n7000
updating source:
repo sync -j16

Troubleshooting
Possible problems:
error: project –j16 not found
The – is a non unicode character. You can type the command by hand on you're keyboard instead of copy-pasting to fix this.
If that doesn't work use repo sync
Repo sync general error fix:
rm -r the directory it complains about
cd ~/android/system
repo sync -d -j16
Error nvram_net.txt_AU is missing or just in general and nvram_net.txt_ file:
open the file vendor/samsung/n7000/n7000-vendor-blobs.mk
and remove these lines:
vendor/samsung/n7000/proprietary/system/etc/wifi/nvram_net.txt_AU:system/etc/wifi/nvram_net.txt_AU \
vendor/samsung/n7000/proprietary/system/etc/wifi/nvram_net.txt_IL:system/etc/wifi/nvram_net.txt_IL \
vendor/samsung/n7000/proprietary/system/etc/wifi/nvram_net.txt_SG:system/etc/wifi/nvram_net.txt_SG \
vendor/samsung/n7000/proprietary/system/etc/wifi/nvram_net.txt_TN:system/etc/wifi/nvram_net.txt_TN \
vendor/samsung/n7000/proprietary/system/etc/wifi/nvram_net.txt_murata_AU:system/etc/wifi/nvram_net.txt_murata_AU \
vendor/samsung/n7000/proprietary/system/etc/wifi/nvram_net.txt_murata_IL:system/etc/wifi/nvram_net.txt_murata_IL \
vendor/samsung/n7000/proprietary/system/etc/wifi/nvram_net.txt_murata_SG:system/etc/wifi/nvram_net.txt_murata_SG \
vendor/samsung/n7000/proprietary/system/etc/wifi/nvram_net.txt_murata_TN:system/etc/wifi/nvram_net.txt_murata_TN \
Also open the file
device\samsung\n7000/proprietary-n7000-files.txt
and remove all lines containing:
nvram_net.txt_murata_*
nvram_net.txt_*

Tips & Trics
Removing CM apps:
To remove roms manager terms or torch:
Edit the file: vendor\cm\config\common.mk
And remove
vendor/cm/proprietary/<App Name>.apk:system/app/<App name>.apk \
Removing other apps:
Edit the file : build\target\product\core.mk
Edit the file : build\target\product\full_base.mk
Edit the file : build\target\product\generic_no_telephony.mk
To change the name of the zip and some info:
Edit the file: vendor\cm\config\common.mk
And change the else part in the file:
ifdef CM_RELEASE
CM_VERSION := $(PRODUCT_VERSION_MAJOR).$(PRODUCT_VERSION_MINOR).$(PRODUCT_VERSION_MAINTENANCE)$(PRODUCT_VERSION_DEVICE_SPECIFIC)-$(CM_BUILD)
else
CM_VERSION := <Enter new zip name here>
endif
Editing LCD density:
Edit the file device\samsung\n7000\n7000.mk
And change ro.sf.lcd_density to whatever you like.
a hint 320 is default
213 is nexus 7 mode
160 is tablet mode
Editing Trebuchet Settings:
Edit the file packages\apps\Trebuchet\res\values\config.xml
Edditing normal Settings:
Edit the file packages\apps\Settings\res\values\bools.xml
Finding out what went wrong:
./build.sh n7000 2> error.log
This means all errors and warnings will be logged to error.log
To find the actual error, you could use "grep -ins error error.log"
Moving the source:
Copy all the files to there new location.
This can be done with cp -rf old location new loaction
The force option is to avoid can't find .git errors
Warning the next part requires to be done all together without interuptions!!!
On the new loaction use rm -rf to remove the files. // I know this will delete the files. Force option is to avois sym link errors.
Now curl the repo to the new location using the steps in the first post.
Repo init as described in the first post.
Repo sync -j16 //The tric is it will restore all files that are still usable and redownload all corrput files
Changing to new kernel thanks to utacka:
local_manifest.xml - to use the latest 9100 kernel update // this file can be found in the .repo dir
change from teamhacksung/android_kernel_samsung_smdk4210 to teamhacksung/android_kernel_samsung_smdk4210_new
Also you may temporarily need to remove it from cm.dependencies in device/samsung/n7000, it'll do weird stuff (like syncing two different kernel repos to the same place) if you don't make that change.
Changing bootanimation:
Copy your new bootanimation zip file to: vendor\cm\prebuilt\common\bootanimation\<Your zip file>
Now make this change in vendor/cm/config/common.mk: //this wil be around line 46
PRODUCT_COPY_FILES += \
vendor/cm/prebuilt/common/bootanimation/<Your zip file>:system/media/bootanimation.zip
endif
The Cm10 bootanimation can be found here: http://goo.gl/x2KC8

Building time
My building time just to give you a heads up on what to expect:
System spec:
6 GB ddr3 ram
Core i5-2500 processor
2tb SATA6 samsung HDD
128GB vertex 2 SSD
Motherboard DH67CL intel
Graphic crad Radeon HD 6870 extreme edtion
VM-Ware workstation Ubuntu 12.04 64 bit headless with image on hdd and workstation on SSD with 4.5 GB ram and windows 8 release preview 64 bit as host OS.
Building after clean 53 min
Building after update 6 min.
Native Lubuntu 12.04 64 bit installed on HDD:
Building after clean 58 min
Building after update 12 min.

Just curious if you have any tips on building on OSX?? I have tried several times and cm10 just will not compile..
I commented out the quemu stuff.. but I still end up failing somewhere along the road. No problems at all on ubuntu VM, just takes 150+ minutes :crying:

madbuda said:
Just curious if you have any tips on building on OSX?? I have tried several times and cm10 just will not compile..
I commented out the quemu stuff.. but I still end up failing somewhere along the road. No problems at all on ubuntu VM, just takes 150+ minutes :crying:
Click to expand...
Click to collapse
I can't really help if i don't know the issue. The problem is most likely related to missing packages.
Could you try building with ./build.sh n7000 2> error.log
And then uploading/posting the contents of the error.log file.
The 2 means log all errors and warnings to the error.log file.
Some VM advise for the best speed:
Use a headless ubuntu server. Login trough ssh. \\The ssh part does not increase speed, but it allows copy pasting.
Give it all you're cores and a lot of memory in the VM settings.
Finally don't use the computer while building it slows the building down

Thanks, didn't even think about how many CPUs I gave to my VM.
Clean built in less than an hour now
Sent from my SCH-I535 using xda app-developers app

Thanks for the guide.. It was really helpfull to me, but I faced some problems, so I think it need an update in the following areas:
1 - Your config builds using the old Kernel... To build with the new one (Preview#4), you need to edit local_manifest.xml , and change teamhacksung/android_kernel_samsung_smdk4210 to teamhacksung/android_kernel_samsung_smdk4210_new . You also need to edit cm.dependencies in device/samsung/n7000 , the same way...
2 - Sun Java is no longer in Ubuntu repositories, so the instructions in: http://source.android.com/source/initializing.html will not work properly, and by following them you will end up building with OpenJDK, It will probably work, but is highly experimental and can result in inexpected problems.

mundano said:
Thanks for the guide.. It was really helpfull to me, but I faced some problems, so I think it need an update in the following areas:
1 - Your config builds using the old Kernel... To build with the new one (Preview#4), you need to edit local_manifest.xml , and change teamhacksung/android_kernel_samsung_smdk4210 to teamhacksung/android_kernel_samsung_smdk4210_new . You also need to edit cm.dependencies in device/samsung/n7000 , the same way...
2 - Sun Java is no longer in Ubuntu repositories, so the instructions in: http://source.android.com/source/initializing.html will not work properly, and by following them you will end up building with OpenJDK, It will probably work, but is highly experimental and can result in inexpected problems.
Click to expand...
Click to collapse
Thats the official building manual from google which also states that openJDK is not expermental for ICS and JB (different page).
This is also confirmed in the android-building group ...
Also OpenJDK 6 builds CM10 without any issues.
The sun java 6 can't be installed headless (if not in repository) because you need to click accept at the official download side....
Kernel is at 3th post bottum (Tips and Trics):
It will not be in the official manual because if it gets stable enough it will get merged in the CM10 repo

mnm1992 said:
Kernel is at 3th post bottum (Tips and Trics):
It will not be in the official manual because if it gets stable enough it will get merged in the CM10 repo
Click to expand...
Click to collapse
ooppss... Didn't saw that one..
I will try OpenJDK.

Thank you mnm1992, you really helped me, it is an all-in-one guide :laugh:.

Hi mnm1992, the manifest have changed to new ones since codeworkx have merged it into main streamline, check this: http://forum.xda-developers.com/showthread.php?p=31166205
Skickat från min GT-N7000 via Tapatalk 2

Need help from dev ! Maybe I will be one of you ?

Hello, all.
First, I know that thread shoud be in "G2 Q&A, Help & Troubleshooting" but I affraid that no one reply...
I'm learning how to "port from source" a ROM for our device.
My choose is the PSX ROM from the Nexus 4 and soon for the Nexus 5.
I have the authorization from the owner @ctfrommn, thank you to him, but I'm starting to bother him a lot with my questions...
So I hope that someone can have a lot and try to help me to learn.
This what I have done since now but I have a error that I don't know how to solve.
ANY idea, information, teaching is really welcome !
Thank you.
*repo sync :
repo init -u https://github.com/PSX-PureSpeed/android_manifest.git -b kk-4.4
*I have added that to the manifest for my LG G2 :
<project path="device/lge/g2-common" name="CyanogenMod/android_device_lge_g2-common" remote="cm" revision="cm-10.2" />
<project path="device/lge/d802" name="CyanogenMod/android_device_lge_d802" remote="cm" revision="cm-10.2" />
<project path="hardware/qcom/display-mdss" name="CyanogenMod/android_hardware_qcom_display-mdss" remote="cm" revision="cm-10.2" />
<project path="hardware/qcom/media-v4l2" name="CyanogenMod/android_hardware_qcom_media-v4l2" remote="cm" revision="cm-10.2" />
<project path="kernel/lge/msm8974" name="CyanogenMod/android_kernel_lge_msm8974" remote="cm" revision="cm-10.2" />
*So there, I have all stuffs to work.
*Under "psx/vendor/psx" I have edit the "vendorsetup.sh"
Add : add_lunch_combo d802-user
* Under "psx/vendor/psx/products" I have create a "d802.mk" file with that :
# Inherit AOSP device configuration for hammerhead.
$(call inherit-product, device/lge/d802/d802.mk)
# Inherit common product files.
$(call inherit-product, vendor/psx/products/common.mk)
# Setup device specific product configuration.
PRODUCT_NAME := d802
PRODUCT_BRAND := LGE
PRODUCT_DEVICE := d802
PRODUCT_MODEL := LG G2
PRODUCT_MANUFACTURER := LGE
PRODUCT_BUILD_PROP_OVERRIDES += PRODUCT_NAME=hammerhead BUILD_FINGERPRINT="google/hammerhead/hammerhead:4.4/KRT16M/893803:user/release-keys" PRIVATE_BUILD_DESC="hammerhead-user 4.4 KRT16M 893803 release-keys"
*I have create a folder "d802" under psx/vendor/lge and add that :
https://github.com/rohanmathur/vendor_lge_d802
*I have edit the file "AndroidProducts.mk" under "psx/vendor/psx" to get that :
PRODUCT_MAKEFILES := \
$(LOCAL_DIR)/psx_emulator.mk \
$(LOCAL_DIR)/psx_mako.mk \
$(LOCAL_DIR)/psx_hammerhead.mk \
$(LOCAL_DIR)/d802.mk \
$(LOCAL_DIR)/psx_flo.mk
*I have edit the file "d802.mk" under "psx/device/lge/d802" and rename :
PRODUCT_NAME := full_d802
to
PRODUCT_NAME := d802
*in a terminal under "psx/" I do :
. build/envsetup.sh
lunch
*And choose "13" that is my "d802-user"
*This is the terminal return :
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[vendor/psx/products/d802.mk]]: "frameworks/native/build/phone-xxhdpi-2048-dalvik-heap.mk" does not exist. Stop.
** Don't have a product spec for: 'd802'
** Do you have the right repo manifest?
*So I have add " phone-xxhdpi-2048-dalvik-heap.mk" in " frameworks/native/build/"
*in a terminal under "psx/" I do :
. build/envsetup.sh
lunch
*And choose "13" that is my "d802-user"
*This is the terminal return :
build/core/product_config.mk:227: *** _nic.PRODUCTS.[[vendor/psx/products/d802.mk]]: "frameworks/native/build/phone-xxhdpi-2048-hwui-memory.mk" does not exist. Stop.
** Don't have a product spec for: 'd802'
** Do you have the right repo manifest?
*So I have add " phone-xxhdpi-2048-hwui-memory.mk" in " frameworks/native/build/"
*in a terminal under "psx/" I do :
. build/envsetup.sh
lunch
*And choose "13" that is my "d802-user"
*There is no more error !"
make otapackage -j8
*And the terminal return :
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4
TARGET_PRODUCT=d802
TARGET_BUILD_VARIANT=user
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=krait
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.11.0-13-generic-x86_64-with-Ubuntu-13.10-saucy
HOST_BUILD_TYPE=release
BUILD_ID=KRT16M
OUT_DIR=out
============================================
Checking build tools versions...
build/core/binary.mk:427: target `out/target/product/d802/obj/EXECUTABLES/skia_test_intermediates/MatrixTest.o' given more than once in the same rule.
find: `src': No such file or directory
frameworks/uiautomator/Android.mk:82: warning: overriding commands for target `out/target/common/obj/PACKAGING/uiautomator-checkapi-last-timestamp'
frameworks/testing/uiautomator/library/Android.mk:82: warning: ignoring old commands for target `out/target/common/obj/PACKAGING/uiautomator-checkapi-last-timestamp'
frameworks/uiautomator/Android.mk:99: warning: overriding commands for target `out/target/common/obj/PACKAGING/uiautomator-checkapi-current-timestamp'
frameworks/testing/uiautomator/library/Android.mk:99: warning: ignoring old commands for target `out/target/common/obj/PACKAGING/uiautomator-checkapi-current-timestamp'
frameworks/uiautomator/Android.mk:111: warning: overriding commands for target `update-uiautomator-api'
frameworks/testing/uiautomator/library/Android.mk:111: warning: ignoring old commands for target `update-uiautomator-api'
make: *** hardware/qcom/: Is a directory. Stop.
*I have no idea on how to solve it...

perhaps there is a space in the include file path check in the MK file similar error:silly:

defcomg said:
perhaps there is a space in the include file path check in the MK file similar error:silly:
Click to expand...
Click to collapse
Sorry, it's probably a stupid question but where can I find this Make file ?
Thank you

Well, I am trying to port 4.4 to the G2 too and I had tried something new yesterday.
At first, I was trying to use a N5 4.4 kernel to boot on a N5 rom, but that was a big mess, and didn't work. Now, I am trying to compile CM11 with the hammerhead kernel (CM11) and all the proprietary stuff and g2 common stuff coming from CM10.2. I still have to fix some errors but it seems to be a lot cleaner.
I see that you have some hammerhead references left in some manifests, make sure that it doesn't make you build some N5 related stuff.
This, means that you are building a CM10.2 kernel (4.3), I am not sure that it will work with a 4.4 rom, I don't know.
<project path="kernel/lge/msm8974" name="CyanogenMod/android_kernel_lge_msm8974" remote="cm" revision="cm-10.2"
This is my first android build, so I am not really the best person to help. In my opinion, it is easier to build with CM, the documentation is really good, but it still requires some build experience and a lot a patience and logic to debug.

Hello,
Thank you about thoses informations.
I will have a look about the kernel once I have solve my current errors.
It can be a pleasure to share our experience, win, fail, and bugs that we have solve.
Do you prefer to continue posting there or have a easier contact with Hangout or Skype, or both !
Do you think that the theory that I have done bout the device tree is OK ?

Hello,
I go a "make" error without more information.
Do someone know hos to solve it ?
Please explaine, I'm learning.
Thank you.
Checking build tools versions...
find: `src': No such file or directory
frameworks/uiautomator/Android.mk:82: warning: overriding commands for target `out/target/common/obj/PACKAGING/uiautomator-checkapi-last-timestamp'
frameworks/testing/uiautomator/library/Android.mk:82: warning: ignoring old commands for target `out/target/common/obj/PACKAGING/uiautomator-checkapi-last-timestamp'
frameworks/uiautomator/Android.mk:99: warning: overriding commands for target `out/target/common/obj/PACKAGING/uiautomator-checkapi-current-timestamp'
frameworks/testing/uiautomator/library/Android.mk:99: warning: ignoring old commands for target `out/target/common/obj/PACKAGING/uiautomator-checkapi-current-timestamp'
frameworks/uiautomator/Android.mk:111: warning: overriding commands for target `update-uiautomator-api'
frameworks/testing/uiautomator/library/Android.mk:111: warning: ignoring old commands for target `update-uiautomator-api'
make: *** hardware/qcom/: Is a directory. Stop.

[Guide] How to compile and install Unofficial Stable CM11 for vibrant SGH-T959

This guide is an adaptation/update of the following guides:
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=231246620
http://forum.xda-developers.com/nexus-4/general/guide-cm11-how-to-build-cyanogenmod-11-t2515305
Disclaimer
My linux skills are not very good but following a few of guides I could compile a very stable and functional ROM. Everything written here is tested by me several times and works, but I am not responsible for any damage.
Requirements:
Linux - Ubuntu 14.04 - 64bit (AFAIK, a 64 bit host is needed to compile KK)
An SGH-T959 with cm11 compile with this guide or cm-10.1-2014xxxx-NIGHTLY-vibrantmtd already installed - Get the latest nightly here: http://get.cm/?device=vibrantmtd
About 14GB of storage for the repository plus about 15GB for building
1 - Install Ubuntu Packages
Terminal
Code:
sudo apt-get install bison build-essential curl flex \
g++-multilib gcc-multilib git-core gnupg gperf \
lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev \
libesd0-dev libncurses5-dev libsdl1.2-dev \
libwxgtk2.8-dev libxml2 libxml2-utils lzop \
pngcrush schedtool \
squashfs-tools xsltproc zip zlib1g-dev
2 - Install JAVA
2.1 Download Java JDK for Linux 64-bit from: http://ghaffarian.net/downloads/Java/JDK/jdk-6u45-linux-x64.bin
2.2 Move jdk-6u45-linux-x64.bin to your home directory
2.3 Remove any other java packages from system:
Code:
sudo apt-get purge openjdk-\* icedtea-\* icedtea6-\*
2.4 Install Java JDK:
Code:
sudo mkdir -p /opt/java/64/
sudo cp jdk-6u45-linux-x64.bin /opt/java/64
sudo su -
cd /opt/java/64
chmod +x jdk-6u45-linux-x64.bin
./jdk-6u45-linux-x64.bin
exit
2.5 Add JDK PATH to .bashrc:
Code:
gedit ~/.bashrc
Add these lines to .bashrc:
Code:
# Java PATHs
export JAVA_HOME=/opt/java/64/jdk1.6.0_45
export PATH=$PATH:$JAVA_HOME/bin
3 - Install Android SDK
3.1 Setup directories:
Code:
cd ~
mkdir android
cd android
mkdir sdk
3.2 Download Android SDK from http://developer.android.com/sdk/index.html
3.3 Extract SDK contents to ~/android/sdk
3.4 Add Android SDK Path:
Code:
gedit ~/.bashrc
Add these lines to .bashrc:
Code:
#Android PATH
export PATH=$PATH:~/android/sdk
export PATH=$PATH:~/android/sdk/platform-tools
export PATH=$PATH:~/android/sdk/tools
4 - Install Repository
4.1 Download Repo:
Code:
mkdir -p ~/bin
mkdir -p ~/android/system
curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
4.2 Add Repo Path:
Code:
gedit ~/.bashrc
Add these lines to .bashrc:
Code:
export PATH=$PATH:~/bin
4.3 Close and open new terminal.
4.4 Initialize Repository:
Code:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b stable/cm-11.0
5 - Download the specific code for Vibrant SGH-T959
Code:
mkdir ~/android/system/.repo/local_manifests && touch ~/android/system/.repo/local_manifests/vibrantmtd.xml && gedit ~/android/system/.repo/local_manifests/vibrantmtd.xml
Copy the following path and save the file:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/samsung/vibrantmtd" name="CyanogenMod/android_device_samsung_vibrantmtd" remote="github" revision="cm-10.2" />
<project path="device/samsung/aries-common" name="CyanogenMod/android_device_samsung_aries-common" remote="github" revision="cm-11.0" />
<project path="packages/apps/SamsungServiceMode" name="CyanogenMod/android_packages_apps_SamsungServiceMode" remote="github" revision="cm-11.0" />
<project path="kernel/samsung/aries" name="CyanogenMod/android_kernel_samsung_aries" remote="github" revision="cm-11.0" />
<project path="hardware/samsung" name="CyanogenMod/android_hardware_samsung" remote="github" revision="cm-11.0" />
</manifest>
Note: For specific code for vibrant, aries and samsung does not use the stable branch to have the latest fixes available
6 - Sync. the Repository
Code:
cd ~/android/system/
repo sync
NOTE: When finished, run the repo sync command again to be sure there are no errors.
7 - Edit a one file from vibrant.
When you finished the download the Repository you need edit a vibrant file or it will not compile.
Code:
gedit ~/android/system/device/samsung/vibrantmtd/recovery/recovery_keys.c
Delete all code and replace it and save the file.
Replace with this code:
Code:
#include <linux/input.h>
#include "recovery_ui.h"
#include "common.h"
#include "extendedcommands.h"
int device_handle_key(int key_code, int visible) {
if (visible) {
switch (key_code) {
case KEY_VOLUMEDOWN:
case 217: // SEARCH
return HIGHLIGHT_DOWN;
case KEY_VOLUMEUP:
case 139: // MENU
return HIGHLIGHT_UP;
case KEY_POWER:
case 158: // HOME
return SELECT_ITEM;
case 102: // BACK
return GO_BACK;
default:
return NO_ACTION;
}
}
return NO_ACTION;
}
8 - Extract files from phone:
NOTE: You need to have cm10.1 (or cm11 compile with this guide) installed on the phone and the phone has to be in usb debugging.
Connect phone to pc and in terminal type:
Code:
adb root
cd ~/android/system/device/samsung/vibrantmtd/
./extract-files.sh
9 - Download Extra Files
Code:
~/android/system/vendor/cm/get-prebuilts
10 - Building Android
Code:
cd ~/android/system
. build/envsetup.sh && brunch vibrantmtd
11 - Install on Phone
11.1 Copy your .zip file from ~/android/system/out/target/product/vibrantmtd/cm-11-XXXXXXXXX-UNOFFICIAL-vibrantmtd.zip to the root of the SD card.
11.2 Optional: Download Google Apps for KitKat from http://goo.im/gapps and place it on the root of the SD card.
11.3 Flash both of these .zip files from recovery.
Note: I put this guide in general because I do not have the necessary permission to put in the development area. If any Administrator can put in the dev. area would be helpful.

Huge thanks. This will come in handy. :good:

@stinga11 - One question. I've read compiling with Linaro yields better results for performance. Are there any special steps in order to compile CM for Vibrant with that?

nirogu325 said:
@stinga11 - One question. I've read compiling with Linaro yields better results for performance. Are there any special steps in order to compile CM for Vibrant with that?
Click to expand...
Click to collapse
Yes with Linaro you have a better performance, but I read that is a bit unstable. Honestly, I do not know how to compile this rom with Linaro if you know how to do and want to contribute, I will gladly I edit the main post and add the steps on how to do.

stinga11 said:
Yes with Linaro you have a better performance, but I read that is a bit unstable. Honestly, I do not know how to compile this rom with Linaro if you know how to do and want to contribute, I will gladly I edit the main post and add the steps on how to do.
Click to expand...
Click to collapse
So far I think @sada23 is the only one left in our community with that knowledge. It would help tremendously in case @sada23 wants to lend someone the torch eventually.

I'd like to take on that challenge of compiling CM11 with Linaro. As a matter of fact, I was looking for a way to compile CM for the vibrant so I could test compiling with Linaro 4.9.2 and maybe add some optimizations, so thank you for this!
Does anyone know any downsides to using the cm-10.2 vibrant device branch? And I'd like to get a consensus for this, I already have an S4 ROM based on the CM stable branch, compiled with SaberMod and a couple of cherry-picks to add on to CM11. How many people would want this?

Synergy510 said:
Does anyone know any downsides to using the cm-10.2 vibrant device branch?
Click to expand...
Click to collapse
The official CM11 releases for galaxy s, galaxy s B, and captivate(They share most of the code with the vibrant.) do not have received any changes from 10.2 branch. In other words, for these device also used the 10.2 branch.:angel:

stinga11 said:
The official CM11 releases for galaxy s, galaxy s B, and captivate(They share most of the code with the vibrant.) do not have received any changes from 10.2 branch. In other words, for these device also used the 10.2 branch.:angel:
Click to expand...
Click to collapse
Cool, thanks for the info. I'm downloading the source right now and I'll try to have a build up as soon as I can. It'll be compiled with some combination of Linaro toolchains. Does anyone know if sada's cm11 is built with this guide (just wanna know because I'm too lazy to install cm-10.1)

Synergy510 said:
Cool, thanks for the info. I'm downloading the source right now and I'll try to have a build up as soon as I can. It'll be compiled with some combination of Linaro toolchains. Does anyone know if sada's cm11 is built with this guide (just wanna know because I'm too lazy to install cm-10.1)
Click to expand...
Click to collapse
No, I do not think sada23 has used this guide to create his ROM, since it was created long before I made this guide. If you can compile with Linaro maybe you want to share the guide on how to do/

stinga11 said:
No, I do not think sada23 has used this guide to create his ROM, since it was created long before I made this guide. If you can compile with Linaro maybe you want to share the guide on how to do/
Click to expand...
Click to collapse
I'll see if I can. I know a fairly simple, a little on the hack-ish side, way to declare which toolchain you want to use.
How come the vibrant has to be running cm-10.1? Which part of the build process dictates that we have to do that? Because we are using the 10.2 branch? If nothing has change with the other Galaxy S variants in their device githubs, then I don't think it should matter which CM the vibrant currently runs since there is no dependency on cm10.1 in extract-files.sh

Synergy510 said:
I'll see if I can. I know a fairly simple, a little on the hack-ish side, way to declare which toolchain you want to use.
How come the vibrant has to be running cm-10.1? Which part of the build process dictates that we have to do that? Because we are using the 10.2 branch? If nothing has change with the other Galaxy S variants in their device githubs, then I don't think it should matter which CM the vibrant currently runs since there is no dependency on cm10.1 in extract-files.sh
Click to expand...
Click to collapse
For the vibrant never was released an official CM-10.2. The coder created the branch but any reason never was released. Is necessary that you have installed an official CM for extract the vibrant drivers. I use CM-10.1 because is the last official release for the vibrant.

stinga11 said:
For the vibrant never was released an official CM-10.2. The coder created the branch but any reason never was released. Is necessary that you have installed an official CM for extract the vibrant drivers. I use CM-10.1 because is the last official release for the vibrant.
Click to expand...
Click to collapse
Gotcha, that makes sense. I've downloaded the source and I'll make some changes to certain things. Maybe after I get a build going I'll make another post on how to build with another toolchain

How to use another toolchain
Okay, I'm going to explain how to compile with different toolchains, namely SaberMod or Linaro. This may not be *the exact way*, but this is what works for me
1) First locate the toolchain you want to use and find it's github. Here are two examples:
Linaro provided by JustArchi: https://github.com/archidroid/toolchain
SaberMod provided by kykdev (optimized for arm cortex architecture): https://github.com/kykdev?tab=repositories
Two notes about toolchains:arm-eabi == kernel toolchain
arm-linux-androideabi == ROM toolchain​
2) Once you've located it, add it to your roomservice.xml (or in the case of this thread vibrantmtd.xml)
When you add something to your roomservice/vibrant.xml, repo sync will gather these files from github for you and place there where you specify
A generic example of adding the toolchain:
from: https://github.com/SOME_USER/THEIR_REPO
Code:
<project name="SOME_USER/THEIR_REPO" path="prebuilts/gcc/linux-x86/arm/arm-eabi-SOME_SPECIAL_NAME" remote="github" revision= "BRANCH" />
By SOME_SPECIAL_NAME, I mean name it what it is. Linaro-4.9.2 or SaberMod-4.8.4 etc etc
By BRANCH, the user's THEIR_REPO might contain both the arm-eabi and arm-linux-androideabi
Example 1:
Looking at kykdev's github, each repo is it's own toolchain, so there is no BRANCH you have to declare. So do this:
Code:
<project name="kykdev/sabermod-arm-cortex_a15-eabi-4.9" path="prebuilts/gcc/linux-x86/arm/arm-eabi-SM-Combo" remote="github" revision="master" />
<project name="kykdev/sabermod-arm-cortex_a15-linux-androideabi-4.8" path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-SM-Combo" remote="github" revision="master" />
Notice how I grab what I needed, see the "project name" and see where they go:
path="prebuilts/gcc/linux-x86/arm/arm-eabi-SM-Combo"
path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-SM-Combo"​The underlined part must stay as it is, but the bold part is the SOME_SPECIAL_NAME. This is going to come handy later when you tell the ROM which toolchain to use. This is why I use "4.8" in both the ROM and kernel toolchains although the kernel toolchain is labeled as 4.9. Since there are no branches here, you declare BRANCH as "master" or whatever the default branch name is on the github repo
Example 2:
Lookin at JustArchi's repo, everything is listed under his "Toolchain" repo.
Code:
<project name="ArchiDroid/Toolchain" path="prebuilts/gcc/linux-x86/arm/arm-eabi-Linaro-4.9.2" remote="github" revision="linaro-4.9-arm-eabi" />
<project name="ArchiDroid/Toolchain" path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-Linaro-4.9.2" remote="github" revision="linaro-4.9-arm-linux-androideabi" />
Nothing the "project name" is the same, so this means we need to specify a BRANCH to get the proper toolchain
revision="linaro-4.9-arm-eabi"
revision="linaro-4.9-arm-linux-androideabi"​
Notice! The "path" stays the same with same SOME_SPECIAL_NAME
path="prebuilts/gcc/linux-x86/arm/arm-eabi-Linaro-4.9.2"
path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-Linaro-4.9.2"​
Now when you repo sync, your toolchains will be in your build environment
3) How to tell the build which toolchain to use
Locate the file: ~/android/system/core/combo/TARGET_linux-arm.mk
In this find the line that says:
Code:
TARGET_GCC_VERSION :=
After the " := " You're going to remove what was already there, probably "4.7" and change it to your SOME_SPECIAL_NAME, so:
Code:
TARGET_GCC_VERSION := SOME_SPECIAL_NAME
example:
TARGET_GCC_VERSION := Linaro-4.9.2
4) If you already made a build with the default toolchain
You should not build immediately after following these steps because you have pre-compiled packages in your build directory and you MUST clean it out whenever you switch toolchains so everything is compiled with the same toolchain. So you must use these commands after changing the toolchain and before making the build:
Code:
cd ~/android/system/
rm -rf ~/.ccache
make clean
make clobber
That's it! You can now brunch vibrantmtd and watch it compile!
Notes
You can mix and match toolchains, but your mileage may vary
Not every toolchain is guaranteed to work. You MAY run into some errors
Try to keep your ROM and kernel toolchains to the same type of toolchain (Linaro, SaberMod, Google)
I think I touched on everything I do with this post, if I missed something or if it doesn't work for you, let me know!

Synergy510 said:
Okay, I'm going to explain how to compile with different toolchains, namely SaberMod or Linaro.
Click to expand...
Click to collapse
Amazing man, thanks a lot for this guide when I have time I will try.

nirogu325 said:
@stinga11 - One question. I've read compiling with Linaro yields better results for performance. Are there any special steps in order to compile CM for Vibrant with that?
Click to expand...
Click to collapse
Now finally there is a guide on how to compile with the Linaro toolchain by Synergy510
http://forum.xda-developers.com/showpost.php?p=55416425&postcount=13

Amazing info, thanks!

hey i followed your guide and zip is ready but when i flashed it through cwm i got this error while flashing
Code:
set_metadata_recursive
here is my device tree https://github.com/Grace5921/device_samsung_kyleve

[Guide][Lollipop] How to Compile Your own ROM's for the Zenfone 2 Z00A/Z008

Well I've been getting a lot of questions on how users can take development into their own hands and start compiling your very own builds of your favorite ROM's. Because of this I have decided to write up a guide that will explain all the steps you need to take to compile a ROM.
NOTE: if your problem is that you cant get your build booting but you already know how to compile ROM's then skip to step 5
Step 1: Install A linux distribution
you will need to be on a linux distribution such as Ubuntu to compile android from source. You can do it on OSX as well but I don't have instructions for that because I haven't done it. So if you aren't on a linux distribution that will be the first thing you need to do. there's thousands of guides online on how to do that so go do that
Step 2: set up the build environment
you will need a lot of packages installed to successfully compile without any errors which ill list here
if you're using ubuntu or another debian based distro then type this in your terminal
Code:
sudo apt-get install bison build-essential curl flex git 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 g++-multilib gcc-multilib lib32ncurses5-dev lib32readline-gplv2-dev lib32z1-dev openjdk-7-jdk android androidsdk-uiautomatorviewer android-copyright android-src-vendor android-emulator android-tools-adb android-headers android-tools-adbd androidsdk-ddms android-tools-fastboot androidsdk-hierarchyviewer android-tools-fsutils androidsdk-traceview yasm
you probably dont need all of those installed but its better to have one extra package then one missing package.
now that you have all the packages needed. its time to set up repo so you are able to sync the sources. type this into your terminal
Code:
mkdir -p ~/bin
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
Step 3: getting the ROM sources
time to play the waiting game! For this part of the guide I will explain how to fetch cyanogenmod's sources.
in your home folder, make a folder called cyanogenmod. Now open the folder and open a terminal inside of it.
inside the terminal type
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
now you might get an error that says something like "Error, tell me who you are!" so you are going to want to type
Code:
git config --global user.email [email protected]
then
Code:
git config --global user.name YourGithubName
you can use fake credentials but i recommend making a git and using your real information.
now run the command once more
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
now it will properly set up the repository. After that type in
Code:
repo sync
and wait for all the sources to download. It will probably take a few hours so I suggest you go do something else and come back later.
If you get any errors while syncing type
Code:
repo sync -j1 -f
Step 4: set up Zenfone specific sources
now that you have cyanogenmods sources downloaded you will need to add zenfones sources.
you can find the zenfone sources here:
https://github.com/CM-zenfone2
for now go into the .repo folder inside your cyanogenmod folder. you may have to enable "show hidden folders" in your file managers settings to see it. inside of this folder create another one called local_manifests . inside this folder create a file called local_manifest.xml .
now open that xml file with a text editor and paste this into it
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- REMOVE AOSP PROJECTS -->
<remove-project name="platform/hardware/intel/common/libmix" path="hardware/intel/common/libmix" />
<remove-project name="platform/hardware/intel/common/libstagefrighthw" path="hardware/intel/common/libstagefrighthw" />
<remove-project name="platform/hardware/intel/common/libva" path="hardware/intel/common/libva" />
<remove-project name="platform/hardware/intel/common/omx-components" path="hardware/intel/common/omx-components" />
<remove-project name="platform/hardware/intel/common/utils" path="hardware/intel/common/utils" />
<remove-project name="platform/hardware/intel/common/wrs_omxil_core" path="hardware/intel/common/wrs_omxil_core" />
<remove-project name="platform/hardware/intel/img/hwcomposer" path="hardware/intel/img/hwcomposer" />
<remove-project name="platform/hardware/intel/img/libdrm" path="hardware/intel/img/libdrm" />
<remove-project name="platform/hardware/intel/img/psb_video" path="hardware/intel/img/psb_video" />
<!-- ADD CM-ZENFONE2 PROJECTS -->
<project name="CM-zenfone2/android_hardware_intel_common_libmix" path="hardware/intel/common/libmix" remote="github" />
<project name="CM-zenfone2/android_hardware_intel_common_libstagefrighthw" path="hardware/intel/common/libstagefrighthw" remote="github" />
<project name="CM-zenfone2/android_hardware_intel_common_libva" path="hardware/intel/common/libva" remote="github" />
<project name="CM-zenfone2/android_hardware_intel_common_omx-components" path="hardware/intel/common/omx-components" remote="github" />
<project name="CM-zenfone2/android_hardware_intel_common_utils" path="hardware/intel/common/utils" remote="github" />
<project name="CM-zenfone2/android_hardware_intel_common_wrs_omxil_core" path="hardware/intel/common/wrs_omxil_core" remote="github" />
<project name="CM-zenfone2/android_hardware_intel_img_hwcomposer" path="hardware/intel/img/hwcomposer" remote="github" />
<project name="CM-zenfone2/android_hardware_intel_img_libdrm" path="hardware/intel/img/libdrm" remote="github" />
<project name="CM-zenfone2/android_hardware_intel_img_psb_video" path="hardware/intel/img/psb_video" remote="github" />
<!-- CM-ZENFONE2 DEVICE PROJECTS -->
<project name="CM-zenfone2/android_device_asus_Z00A" path="device/asus/Z00A" remote="github" />
<project name="CM-zenfone2/android_device_asus_Z008" path="device/asus/Z008" remote="github" />
<project name="CM-zenfone2/android_device_asus_mofd-common" path="device/asus/mofd-common" remote="github" />
<project name="CM-zenfone2/android_kernel_asus_moorefield" path="kernel/asus/moorefield" remote="github" />
<project name="CM-zenfone2/proprietary_vendor_asus" path="vendor/asus" remote="github" />
</manifest>
now save and close that xml file. go back to your terminal in the cyanogenmod folder and run
Code:
repo sync -j1 --force-sync
this will now pull in the zenfone files you need.
Zenfone sources are now synced into the official CM github so these steps aren't needed. the only extra thing to do now is:
in your vendor folder
Code:
git clone https://github.com/TheMuppets/proprietary_vendor_asus.git -b cm-12.1
then rename the folder to "asus"
Step 5: adding device specific commits
this is probably the step that most people don't do and therefore get builds that won't boot. You need to add 4 A bunch of very important commits to get your ROM properly booting.
commit 1
go inside of your external/tinyalsa folder and open a terminal then type in:
Code:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_external_tinyalsa refs/changes/43/103343/1 && git cherry-pick FETCH_HEAD
now close the terminal and go to the folder hardware/intel/img/hwcomposer and open a terminal. type this in:
Code:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_hardware_intel_img_hwcomposer refs/changes/82/117182/1 && git cherry-pick FETCH_HEAD
and
Code:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_hardware_intel_img_hwcomposer refs/changes/83/117183/1 && git cherry-pick FETCH_HEAD
open up hardware/intel/img/libdrm and paste this in the terminal:
Code:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_hardware_intel_img_libdrm refs/changes/01/117201/1 && git cherry-pick FETCH_HEAD
put this in hardware/intel/common/libmix
Code:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_hardware_intel_common_libmix refs/changes/91/117191/1 && git cherry-pick FETCH_HEAD
now go into the folder hardware/ril. Open the terminal and type:
Code:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_hardware_ril refs/changes/25/102725/2 && git cherry-pick FETCH_HEAD
now open the frameworks/native folder and type in the terminal:
Code:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_native refs/changes/36/108636/2 && git cherry-pick FETCH_HEAD
these are the 4 commits that those commands are adding for anybody interested:
https://github.com/TeamEOS/system_core/commit/870fff040f14f4a659807d74419300ef0f223a30
https://github.com/TeamEOS/system_core/commit/7fb271f606394692cbf303f3e7d4889e4ff04369
https://github.com/TeamEOS/hardware_ril/commit/bb9b4e567e5bba35ae380ee0a56833ba385af654
https://github.com/TeamEOS/external_tinyalsa/commit/3bba475d5ad4db3f813ff121ff3d195043307f46
NOTE:New commits for the quick charging UI have been added that you need to add. check post 3 for them
now we have set everything we need properly to build the rom!
Step 6: Start the build
finally, time to start building! open a terminal in the cyanogenmod folder and type
Code:
. build/envsetup.sh
now type
Code:
brunch Z00A
for Z00A or
Code:
brunch Z008
for Z008.
this will also take a while depending on your computers specs (around 4 hours).
When its done you will find the zip in the folder out/target/product/Z00A (or Z008).
you can now put this zip on your device and flash away
to update sources and make a new build you can do repo sync and step 5 and 6 again
I hope this guide can help motivate people interested in building to give it a go as well as help grow the community even more then it already is! feel free to post any questions you have here and I will help to the best of my ability.

reserved
I will expand on this more but to build a rom other then cyanogenmod, (for example EOS) you would go into the device/asus/Z00A folder and change the cm.mk file to eos.mk as well as everything inside that file that refers to cyanogenmod to eos. most ROM's you do something similar to that but instead of changing to eos you change it to the rom you are building. Refer to other device sources of the ROM you want to build as a guide to what to do

For quick charging UI
paste this command into your frameworks/native folder
Code:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_native refs/changes/64/109364/3 && git cherry-pick FETCH_HEAD
then paste this into your frameworks/base folder
Code:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_frameworks_base refs/changes/66/109366/7 && git cherry-pick FETCH_HEAD
and lastly paste this into system/core
Code:
git fetch http://review.cyanogenmod.org/CyanogenMod/android_system_core refs/changes/65/109365/6 && git cherry-pick FETCH_HEAD

Thanks bro, I started this but I'm very noob xD

Hebelm16 said:
Thanks bro, I started this but I'm very noob xD
Enviado desde mi ASUS_Z00AD mediante Tapatalk
Click to expand...
Click to collapse
Nice! No worries we all start somewhere

Great bro thanks

Good Job Bro Thanks

Niropa said:
Nice! No worries we all start somewhere
Click to expand...
Click to collapse
I swear I was looking for this type of teacher from a very very long time..
And when you said it will take a long time, how much is the data to be downloaded? Actually the speed differs here so I will estimate myself how much time it will take

S#@DY said:
I swear I was looking for this type of teacher from a very very long time..
And when you said it will take a long time, how much is the data to be downloaded? Actually the speed differs here so I will estimate myself how much time it will take
Click to expand...
Click to collapse
Generally its changing but i downloaded 40gb for blisspop know i downloading euphoria os repo we will see the size

S#@DY said:
I swear I was looking for this type of teacher from a very very long time..
And when you said it will take a long time, how much is the data to be downloaded? Actually the speed differs here so I will estimate myself how much time it will take
Click to expand...
Click to collapse
It will be around 50gb so compare that to your internet speed

Niropa said:
It will be around 50gb so compare that to your internet speed
Click to expand...
Click to collapse
That would take 2 days

If I have any free time next month am going to try to learn all this rom compiling etc and build a temasek based rom.

GGL-Daz said:
If I have any free time next month am going to try to learn all this rom compiling etc and build a temasek based rom.
Click to expand...
Click to collapse
Great to hear! Temasek is actually very easy, you would follow this guide exactly but instead of syncing cyanogenmods sources you would sync temaseks which you can find on his github

Sorry @Niropa how add source? (step 4)

Hebelm16 said:
Sorry @Niropa how add source? (step 4)
Click to expand...
Click to collapse
what are you having trouble with?
also there might be an issue with the steps I showed to cherry-pick the commits so im going to update it right now

Code:
. build/envsetup.sh
lunch <rom name>_<device model>-userdebug
make bacon -j8
This works as well and eats your cpu little less compared to brunch. You could add in the OP @Niropa

Vatsal said:
Code:
. build/envsetup.sh
lunch <rom name>_<device model>-userdebug
make bacon -j8
This works as well and eats your cpu little less compared to brunch. You could add in the OP @Niropa
Click to expand...
Click to collapse
right because brunch uses mka instead of make. mka uses all cores/threads available so your build will finish faster

hi noob here..
i have following steps in the first post.
however, i got error like below:
device/asus/mofd-common/libhealthd/healthd_board_mofd_v1.cpp: In function 'int mapBatteryStatusString(const char*)':
device/asus/mofd-common/libhealthd/healthd_board_mofd_v1.cpp:26:12: error: 'HEALTHD_MAP_CONTINUE_SEARCH' was not declared in this scope
return HEALTHD_MAP_CONTINUE_SEARCH;
^
device/asus/mofd-common/libhealthd/healthd_board_mofd_v1.cpp: In function 'int mapChargeRateString(const char*)':
device/asus/mofd-common/libhealthd/healthd_board_mofd_v1.cpp:32:16: error: 'BATTERY_CHARGE_RATE_FAST_CHARGING' is not a member of 'android'
return android::BATTERY_CHARGE_RATE_FAST_CHARGING;
^
device/asus/mofd-common/libhealthd/healthd_board_mofd_v1.cpp:34:16: error: 'BATTERY_CHARGE_RATE_UNKNOWN' is not a member of 'android'
return android::BATTERY_CHARGE_RATE_UNKNOWN;
^
device/asus/mofd-common/libhealthd/healthd_board_mofd_v1.cpp: In function 'void healthd_board_init(healthd_config*)':
device/asus/mofd-common/libhealthd/healthd_board_mofd_v1.cpp:39:13: error: 'struct healthd_config' has no member named 'batteryChargeRatePath'
config->batteryChargeRatePath = "/sys/class/power_supply/battery/status";
^
device/asus/mofd-common/libhealthd/healthd_board_mofd_v1.cpp:40:13: error: 'struct healthd_config' has no member named 'mapBatteryStatusString'
config->mapBatteryStatusString = mapBatteryStatusString;
^
device/asus/mofd-common/libhealthd/healthd_board_mofd_v1.cpp:41:13: error: 'struct healthd_config' has no member named 'mapChargeRateString'
config->mapChargeRateString = mapChargeRateString;
^
make: *** [/home/myusuf1810/cyanogenmod/out/target/product/Z00A/obj/STATIC_LIBRARIES/libhealthd.mofd_v1_intermediates/healthd_board_mofd_v1.o] Error 1
make: *** Waiting for unfinished jobs....
#### make failed to build some targets (03:29 (mm:ss)) ####
Click to expand...
Click to collapse
i retried the whole steps on new folder, get the same result.
is it the code or my mistake for missing some steps?

ucupsz said:
hi noob here..
i have following steps in the first post.
however, i got error like below:
i retried the whole steps on new folder, get the same result.
is it the code or my mistake for missing some steps?
Click to expand...
Click to collapse
hey! no worries you did nothing wrong. because of the new quick charging UI the cm zenfone team added theres a few new things you have to cherry-pick.
paste this command into your frameworks/native folder
Code:
git fetch http://review.teameos.org/frameworks_native refs/changes/14/914/1 && git cherry-pick FETCH_HEAD
then paste this into your frameworks/base folder
Code:
git fetch http://review.teameos.org/frameworks_base refs/changes/16/916/1 && git cherry-pick FETCH_HEAD
and lastly paste this into system/core
Code:
git fetch http://review.teameos.org/system_core refs/changes/15/915/1 && git cherry-pick FETCH_HEAD

wow!! thanks so much Niropa! it works!
took 3 hrs on my rig )
so, i try to go to review.teameos.org and searching for libhealthd which is shown in error message. and get to the changes you shown. (914-916).
however, i'm a bit lost on how to get the link "refs/changes/14/914/1" "refs/changes/15/915/1" and "refs/changes/16/916/1" to be inputted to the command line.
from the searching, what i found was numbering 914, 915 and 916.
so if i had similar error (some update on the code), can you show me how i can get to "refs/changes......"

[GUIDE] build lineageOS for titan in ubuntu 16.04 (or Debian 8) environment

LineageOS is in an official state, so that's for the ones with no patience, like me. I want my nightlies!! So DIY!!
This is not about flashing. Only how to build a ROM in an Ubuntu (meanwhile Debian 8) environment! So I have nothing to do with what you do with the finished Zip-file.
I am not responsible for your phone or your computer! Everything you read here resulting in taking action is at your own risk!
All credits go to all devs and supporters here on XDA, CyanogenMod / LineageOS for all their work they provide for free on github. We just take thankful the benefit!! Mainly LuK1337 provided the best hints and informations!
## These sites will help you:
http://wiki.lineageos.org/titan_build.html
http://web.archive.org/web/20160722172103/http://wiki.cyanogenmod.org/w/Envsetup_help
http://web.archive.org/web/20160421170720/http://wiki.cyanogenmod.org/w/Build_for_titan
http://gojira.tokyo/?building_cyanogenmod_14_from_source
http://source.android.com/source/initializing.html
## GIT and repos
https://forum.xda-developers.com/showthread.php?t=2329228
## SET UP THE ENVIRONMENT
## Install (in VMware Player or Virtualbox?) 64-bit-Ubuntu 16.04.1 LTS / 8GB RAM / 100GB HDD
## All following is done in a terminal
## These are the packets you need (if you use debian some will fail (e.g. JAVA) -take them out of the list manually):
Code:
sudo apt-get install android-tools-adb automake bc bison build-essential bzip2 ccache curl dpkg-dev flex git gnupg gperf libbz2-1.0 libesd0-dev libghc-bzlib-dev liblz4-tool libncurses5-dev libsdl1.2-dev libwxgtk2.8-dev libxml2 libxml2-utils lzop make maven openjdk-8-jdk pngcrush python-networkx schedtool squashfs-tools xsltproc zip zlib1g-dev g++-multilib gcc-multilib lib32ncurses5-dev lib32z1-dev lib32readline6 lib32readline6-dev
## To install JAVA 8 in Debian:
Code:
echo "deb http://ppa.launchpad.net/webupd8team/java/ubuntu xenial main" | tee /etc/apt/sources.list.d/webupd8team-java.list
echo "deb-src http://ppa.launchpad.net/webupd8team/java/ubuntu xenial main" | tee -a /etc/apt/sources.list.d/webupd8team-java.list
apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys EEA14886
apt-get update
apt-get install oracle-java8-installer
## Add all needed paths and the ccache command (following two lines) to the end of ~/.bashrc
## copy the whole box to your terminal and the lines will be added...
Code:
echo "export PATH=~/bin:~/android/lineageos/toolchain:~/android/lineageos/external/v8/build/toolchain:~/android/lineageos/prebuilts/sdk/tools:$PATH
export USE_CCACHE=1" >> ~/.bashrc
## Maybe here is a good point to restart the Ubuntu machine once...
## I'm not sure if necessary you need an account at https://github.com but it complains when not...
Code:
git config --global user.email "your-GIT-REG-email"
git config --global user.name "your-GIT-REG-username"
Code:
mkdir -p ~/bin
mkdir -p ~/android/lineageos/
mkdir -p ~/android/lineageos/.repo/local_manifests
## get the repo command
Code:
curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
chmod a+x ~/bin/repo
## The right git-repos to sync are in: ~/android/lineageos/.repo/local_manifests/roomservice.xml
## copy the whole box into the terminal and the roomservice.xml will be written:
Code:
echo "<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remote fetch="ssh://[email protected]" name="bitbucket" />
<remote fetch="ssh://[email protected]" name="gitlab" />
<remote fetch="git://codeaurora.org/" name="caf" review="codeaurora.org" sync-c="true" />
<project name="LineageOS/android_device_motorola_titan" path="device/motorola/titan" remote="github" />
<project name="LineageOS/android_device_motorola_thea" path="device/motorola/thea" remote="github" />
<project name="LineageOS/android_device_motorola_msm8226-common" path="device/motorola/msm8226-common" remote="github" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="LineageOS/android_kernel_motorola_msm8226" path="kernel/motorola/msm8226" remote="github" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" />
<project name="TheMuppets/proprietary_vendor_qcom_binaries" path="vendor/qcom/binaries" remote="github" />
<project name="TheMuppets/proprietary_vendor_asus" path="vendor/asus" remote="github" />
</manifest>" > ~/android/lineageos/.repo/local_manifests/roomservice.xml
## Get the github to the machine
Code:
repo init -u git://github.com/lineageos/android.git -b cm-14.1
## additional folders to put the repos and binaries for building
## O.K. lets start the first try
Code:
cd ~/android/lineageos/
source build/envsetup.sh
Code:
repo sync
## Wait VERY LONG (really hours) and IF STUCKS, press "ctrl+C" and once more "repo sync" again.
## Then Extract proprietary blobs from the phone
## the device must be connected via USB cable (adb has to be functional) and go to the TITAN directory:
Code:
cd ~/android/lineageos/device/motorola/titan
## and
Code:
./extract-files.sh
## and maybe (only once before the first time of building) configure the CCACHE, which makes compiling much faster:
Code:
prebuilts/misc/linux-x86/ccache/ccache -M 50G
##WHEN ALL IS DONE
## we now can forget all steps before! ...Until we run in trouble - then look at the bottom or restart from scratch.
## In my experience now it shows, that the compiling processes recompiles and replaces "new synced packets" in the out-directory and leave the untouched untouched. So we can (nearly) always restart a broken build process... maybe the devs will VETO this. Some delete the whole out-directory every time - I think you can easily start over
## However, what we should do everytime before we start building is:
Code:
cd ~/android/lineageos/
source build/envsetup.sh
repo sync
## OKAY, lets build.... Nooooooo! Not yet!
## The most Important question now:
## "Do you want to have a ROOTED phone?" If yes, then you have to
Code:
export WITH_SU=true
## If you don't want root then just start with:
Code:
brunch titan
## Now you can wait again for hours and hopefully got finished
## ~/android/lineageos/out/target/product/titan/lineage-14.1-2017****-UNOFFICIAL-titan.zip
------------------------------------------------------------------------
------------------------------------------------------------------------
## TROUBLE with compilation stops / stucks with error:
## JACK-SERVER error:
## reinstall the Jack Server
Code:
cd ~/android/lineageos/prebuilts/sdk/tools
jack-admin kill-server
jack-admin uninstall-server
jack-admin install-server jack-launcher.jar jack-server-4.8.ALPHA.jar
## sometimes a permission problem:
Code:
chmod 700 ~/.jack-server
find ~/.jack-server -type f -print0 | xargs -0 chmod 600
chmod 664 ~/.jack-settings
##Also helpful if Java stops compiling is to limit the usage of RAM:
Code:
export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
##NINJA error:
## increase RAM of VM, or you cant put
Code:
export USE_NINJA=false
command to the .bashrc
## APPS/org.cyanogenmod.platform-res_intermediates error:
Code:
javac: file not found: ~android/lineageos/out/target/common/obj/APPS/org.cyanogenmod.platform-res_intermediates/src/cyanogenmod/platform/Manifest.java
Usage: javac <options> <source files>
use -help for a list of possible options
ninja: build stopped: subcommand failed.
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
make: Leaving directory '~/android/lineageos'
#### make failed to build some targets (25:19 (mm:ss)) ####
When this happens, give a:
Code:
mka org.cyanogenmod.platform-res
This also works for most other Errors, which stop the process... Find the line with "****_intermediate" and give the "mka ****" WITHOUT the "_intermediate".
After compiling of the single package is finished - once more:
Code:
brunch titan
## New one: *** This repo is now deprecated. Move your blobs to your device's vendor repo..
Code:
find: "~/android/lineageos/out/target/common/obj/SHARED_LIBRARIES/libwifi-hal-mock_intermediates": Datei oder Verzeichnis nicht gefunden
build/core/package_internal.mk:143: Empty argument supplied to find-subdir-assets
./vendor/qcom/binaries/Android.mk:1: *** This repo is now deprecated. Move your blobs to your device's vendor repo..
The solution is given here by mirkosrc:
Code:
~/android/lineageos$ mv vendor/qcom/binaries/Android.mk vendor/qcom/binaries/Android.mk.bak
Now we have the proper solution given by kessaras in post #37 (thanks a lot!!):
the solution is not to rename the .mk or even remove that repo since we ignore it by renaming the .mk.
The proper solution is to edit the .mk and remove the 1st line that redirects to an error on purpose because its depricated (old).
This way, IF the .mk is needed during the build, it will get called.
If its not needed , then the compiler will just not use it.
At least thats my point of view here. We dont just remove things by renaming. We add them properly in case they r needed. If they are not needed then they wont be used.
Click to expand...
Click to collapse
## LAST OPTION:
When nothing works at all anymore you can delete the whole content of the out-folder:
Code:
rm -rf ~/android/lineageos/out/*
But then the first compiling last very long again...
## If the DISK runs full,
look into android/lineageos/out/target/product/titan/obj/PACKAGING/target_files_intermediates and delete the files...
## repo sync crashes with error:
Code:
repo sync -j1 -f --force-sync
------------------------------------------------------------------------

Thank you for this guide. I'll try to build CM14.1 here

Danilo-Sanchez said:
Thank you for this guide. I'll try to build CM14.1 here
Click to expand...
Click to collapse
Ah, great keep me informed, so I can make it better. Try myself from the scratch and have found some issues in the chronological order... is getting better. So look out for changes

mankokoma said:
Ah, great keep me informed, so I can make it better. Try myself from the scratch and have found some issues in the chronological order... is getting better. So look out for changes
Click to expand...
Click to collapse
Ok. As soon as I try I'll let you know

For the Ninja error:
export USE_NINJA=false

Has been asked for RAM usage. Battery life is as CM always have been - not the best, could be worse, so what?

mankokoma said:
Has been asked for RAM usage. Battery life is as CM always have been - not the best, could be worse, so what?
Click to expand...
Click to collapse
Thank you
It's almost the same RAM usage as CM13.

i will also try to build the rom from ur guide........really thanks.......so much for the guide

:laugh:Thank you for share!!!:good:

@mankokoma Can I extract proprietary files even if I'm not using CM14.1?

Danilo-Sanchez said:
@mankokoma Can I extract proprietary files even if I'm not using CM14.1?
Click to expand...
Click to collapse
Why not? As far as I can follow the scripts, the files will be extracted (in our case) to ~/android/lineageos/vendor/motorola/titan/proprietary/... (and maybe also to /android/lineageos/vendor/motorola/msm8226-common/proprietary...) I'm not sure if they are always the same for the different Android Versions, but I assume: Yes.

I put some more order in the guide and cleaned the chaos in case there is still interest in building LineageOS yourself. In fact preparing of the environment and the first setup and building of the ZIP lasts really (annoying) long but the following building processes are done within ONE and a HALF hours. So I enjoy immediately the last build when there has something good changed in the Repos: https://www.cmxlog.com/14.1/titan/
Have a lot of fun!

mankokoma said:
I put some more order in the guide and cleaned the chaos in case there is still interest in building LineageOS yourself. In fact preparing of the environment and the first setup and building of the ZIP lasts really (annoying) long but the following building processes are done within ONE and a HALF hours. So I enjoy immediately the last build when there has something good changed in the Repos: https://www.cmxlog.com/14.1/titan/
Have a lot of fun!
Click to expand...
Click to collapse
Did you managed to build Lineage OS 13.0?
I've tried to build Lineage OS 13.0 but unfortunately it didn't work.

Danilo-Sanchez said:
Did you managed to build Lineage OS 13.0?
I've tried to build Lineage OS 13.0 but unfortunately it didn't work.
Click to expand...
Click to collapse
No, I didn't. "Shoot from the hip": Downgrade Java to 1.7 first. Maybe it's easier to building up Ubuntu 14.x environment as I don't know about gcc or other libs-things for CM13

mankokoma said:
No, I didn't. "Shoot from the hip": Downgrade Java to 1.7 first. Maybe it's easier to building up Ubuntu 14.x environment as I don't know about gcc or other libs-things for CM13
Click to expand...
Click to collapse
Did you managed to include OMS support in Lineage 14.1?

Danilo-Sanchez said:
Did you managed to include OMS support in Lineage 14.1?
Click to expand...
Click to collapse
No, didn't have any efforts, though a dark notification panel would be nice.
I just take, what comes from the "normal" repositories.

@mankokoma any idea?
Makefile:795: *** multiple target patterns. Stop.

hashroot said:
@mankokoma any idea?
Makefile:795: *** multiple target patterns. Stop.
Click to expand...
Click to collapse
I'm sorry, have only very little time these days... can you provide some more lines before this error occurs?
Are you using Ubuntu or Debian?
I have read something about cleaning the "obj" folder could help

Hi, I am building klte version of CrdroidAndroid ( a LineageOS based ROM) on a ubuntu 16.04 LTS VM.
I am getting the following error. I am not sure what to do here. I have been cleaning the build folder and ccache and trying to build. I keep ending at this error. Any help to solve this issue is greatly appreciated.
----------------------------------
/usr/bin/x86_64-linux-gnu-ld: /home/sadanand/crdroid/android/system/out/host/linux-x86/obj/SHARED_LIBRARIES/libart_intermediates/base/allocator.o: relocation R_X86_64_PC32 against protected symbol `_ZN3art18g_malloc_allocatorE' can not be used when making a shared object
/usr/bin/x86_64-linux-gnu-ld: final link failed: Bad value
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
-----------------------------------------------------------
Thanks

Did you try just "mka libart" to compile only the package with the error?
Usually then it's finishing without errors and you can brunch again.