Maybe this will help someone..
I'll be visiting this thread occasionally in case someone needs help. But I'd be glad if people and future devs also helped each other. :good:
If you compile a running build with these instructions, feel free to share it with people in this thread. Maybe development for these phones is not over yet! :fingers-crossed:
Soo.. Let's start!
What you need:
- Basic coding skills
- A GitHub account and some skills on how to use git.
- A computer with decent specs. (using an i5-4670k and 8gb ram here)
- LOTS of free storage. I recommend at least 100-200GB. The more, the better.
- A linux VM with all neccesary tools to build android. I recommend BBQLinux.
Initial Steps:
1. Grab the CM12.1 source by typing the following in your VM's Terminal:
Code:
mkdir cm12
cd cm12
repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
repo sync
This will take some hours. Just wait.
2. Create a file called roomservice.xml in /home/yourusername/cm12/.repo/local_manifests directory, containing the following:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<remove-project name="CyanogenMod/android_bootable_recovery" />
<remove-project name="CyanogenMod/android_build" />
<remove-project name="CyanogenMod/android_external_bluetooth_bluedroid" />
<remove-project name="CyanogenMod/android_frameworks_av" />
<remove-project name="CyanogenMod/android_frameworks_base" />
<remove-project name="CyanogenMod/android_hardware_qcom_display" />
<remove-project name="CyanogenMod/android_libcore" />
<remove-project name="platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" />
<remove-project name="platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8" />
<project name="ArchiDroid/Toolchain" path="prebuilts/gcc/linux-x86/arm/arm-eabi-4.8" remote="github" revision="architoolchain-4.9-arm-linux-gnueabihf-cortex_a9_neon" />
<project name="ArchiDroid/Toolchain" path="prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.8" remote="github" revision="sabermod-4.9-arm-linux-androideabi" />
<project name="CyanogenMod/android_device_sony_common" path="device/sony/common" remote="github" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_hardware_sony_DASH" path="hardware/sony/DASH" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_kernel_sony_msm8x60" path="kernel/sony/msm8x60" remote="github" />
<project name="WhiteNeo-/android_bootable_recovery" path="bootable/recovery" remote="github" revision="android-5.1" />
<project name="WhiteNeo-/android_build" path="build" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/android_external_bluetooth_bluedroid" path="external/bluetooth/bluedroid" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/android_frameworks_av" path="frameworks/av" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/android_frameworks_base" path="frameworks/base" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/android_hardware_qcom_display" path="hardware/qcom/display-caf/msm8960" remote="github" revision="cm-12.1-caf-8960" />
<project name="WhiteNeo-/android_libcore" path="libcore" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/android_device_sony_blue-common" path="device/sony/blue-common" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/android_device_sony_mint" path="device/sony/mint" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/android_device_sony_hayabusa" path="device/sony/hayabusa" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/android_device_sony_msm8960-common" path="device/sony/msm8960-common" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/android_device_sony_tsubasa" path="device/sony/tsubasa" remote="github" revision="cm-12.1" />
<project name="WhiteNeo-/kernel-msm" path="kernel/sony/msm8960" remote="github" revision="master" />
<project name="WhiteNeo-/proprietary_vendor_sony" path="vendor/sony" remote="github" revision="cm-12.1" />
</manifest>
3. Find all the lines containing "WhiteNeo-", fork those repositories at GitHub and replace "WhiteNeo-" with your GitHub name. (Important!)
Then copy the related repositories to your local drive with the "git clone" command.
4. Some sources are still old and need to be updated before we start to compile. These are:
android_bootable_recovery
android_build
android_external_bluetooth_bluedroid
android_frameworks_av
android_frameworks_base
android_hardware_qcom_display
android_libcore
These sources have to be updated like the example below.
Just remember that not all branches are named cm-12.1, so replace "cm-12.1" with the revision from roomservice.xml (look above)
Code:
cd android_build
git pull https://github.com/CyanogenMod/android_build.git cm-12.1
git push https://github.com/WhiteNeo-/android_build.git cm-12.1
The recovery sources are updated differently:
Code:
cd android_bootable_recovery
git pull https://github.com/omnirom/android_bootable_recovery.git android-5.1
git push https://github.com/WhiteNeo-/android_bootable_recovery.git android-5.1
5. Once more do a repo sync in your cm12 directory, to synchronize our updated repositories with the ones in CM12 directory.
6. Start the build with the following terminal commands:
Code:
cd cm12
. build/envsetup.sh
brunch yourdevicename
(Replace "yourdevicename" with your phone's manufacturer name: tsubasa = Xperia V // mint = Xperia T // hayabusa = Xperia TX)
If there are no issues, you'll find the finished ROM zip in cm12/out/target/product/yourdevicename directory.
Copy the META-INF folder from my latest NEO build over to the new zip and flash. Done.
Future builds:
Just repeat steps 4 to 6.
Troubleshooting:
If you run into toolchain errors, grab the libraries from the following link and install them in your virtual machine.
http://sabermod.com/Prebuilt-libs (DEV ONLY)/ROM-Kernel/
Hey, I need some help with a kernel build. Ive got a zimage and I cant compile it into a boot.img and doomkernerls tutorial is only for jelly bean
Can it be done with ScriBt?
Related
Hey There,
Can anybody change the following so it will work on our device ? :laugh:
Thank you in advance
Quote:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="teamhacksung/buildscripts" path="buildscripts" remote="github" revision="jellybean">
<copyfile dest="build.sh" src="build.sh" />
</project>
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="jellybean" />
<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="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="jellybean" />
</manifest>
Hi everyone. Not sure if this has been posted,but I wanted to just share with newest CMW 6.0.3.2 Touch version,the installation procedure is usual. Tested on my L7 P700 CM10
1) Connect phone to PC ins USB Debugging mode(You can enable it in developer tools)
2) Download this https://www.dropbox.com/s/89u7kui5u7jtqua/Flash+boot_cwm.rar and extract it to folder and I suggest locating folder for example in C:/new folder.
3)The launch flash_bootloader.bat and wait for phone to restart.
4)Then Flash_Recovery.bat,wait for it to restart and you're done.
CMW Flashable 6.0.3.2 Touch - http://www.sendspace.com/file/i3see9
For L7 or L5/L3??
Sent from my LG-P700 using xda premium
ubuntuh said:
For L7 or L5/L3??
Sent from my LG-P700 using xda premium
Click to expand...
Click to collapse
Tested on my L7 ,not sure about other devices.
Lukijs said:
2) Download this ... and extract it to folder and I suggest locating folder
Click to expand...
Click to collapse
The link doesn't work, could you upload it again ?
Dead link, refresh it.
Will it work on lg Optimus l7 710?
Upgrade I must doing as a install??
regards
cr3pt
Someone tested it in L5?
Sent from my LG-E610 using xda app-developers app
If anybody is interested in CWM 6.0.4.0 Advanced Edition / PhilZ Touch 5.16.6, please forward this message to PhilZ thread, since I'm some posts short to post in dev section.
Please add support for LG Optimus L7 (cm_p700) (should fit p705 too).
Android.mk:
#LG Optimus L7 (p700/p705)
else ifeq ($(TARGET_PRODUCT), cm_p700)
TARGET_COMMON_NAME := lge_p700
BOARD_USE_NTFS_3G := false
BOARD_USE_EXFAT_FUSE := false
LOCAL_CFLAGS += -DTARGET_DEVICE_P700
Official device files on CyanogenMod have only "jellybean" branch, so I used TeamHackLG repo.
On cm-10.1:
<project path="device/lge/e610" name="TeamHackLG/android_device_lge_e610" remote="github" revision="cm-10.1" />
<project path="device/lge/msm7x27a-common" name="TeamHackLG/android_device_lge_msm7x27a-common" remote="github" revision="cm-10.1" />
<project path="device/lge/p700" name="TeamHackLG/android_device_lge_p700" remote="github" revision="cm-10.1" />
<project path="kernel/lge/msm7x27a-common" name="TeamHackLG/lge-kernel-lproj" remote="github" revision="android-msm-3.4-jb42" />
<remove-project name="CyanogenMod/android_bootable_recovery" />
<project path="bootable/recovery" name="PhilZ-cwm6/philz_touch_cwm6" remote="github" revision="cm-10.1" />
On cm-10.2:
<project path="device/lge/e610" name="TeamHackLG/android_device_lge_e610" remote="github" revision="cm-10.2" />
<project path="device/lge/msm7x27a-common" name="TeamHackLG/android_device_lge_msm7x27a-common" remote="github" revision="cm-10.2" />
<project path="device/lge/p700" name="TeamHackLG/android_device_lge_p700" remote="github" revision="cm-10.2" />
<project path="kernel/lge/msm7x27a-common" name="TeamHackLG/lge-kernel-lproj" remote="github" revision="android-msm-3.4-jb4.3" />
<remove-project name="CyanogenMod/android_bootable_recovery" />
<project path="bootable/recovery" name="PhilZ-cwm6/philz_touch_cwm6" remote="github" revision="cm-10.2" />
Builds without errors, flashes and works.
Recovery and boot images from stock p700 v20e (P70020e-EUR-XX, Android 4.1.2, kernel 3.4.0)
P.S. Aroma File Manager has picture rotated by 180 deg, while touch areas are correctly oriented,
Seems this is due ro.sf.hwrotation=180 for p700.
ADambi said:
If anybody is interested in CWM 6.0.4.0 Advanced Edition / PhilZ Touch 5.16.6, please forward this message to PhilZ thread, since I'm some posts short to post in dev section.
Please add support for LG Optimus L7 (cm_p700) (should fit p705 too).
Android.mk:
#LG Optimus L7 (p700/p705)
else ifeq ($(TARGET_PRODUCT), cm_p700)
TARGET_COMMON_NAME := lge_p700
BOARD_USE_NTFS_3G := false
BOARD_USE_EXFAT_FUSE := false
LOCAL_CFLAGS += -DTARGET_DEVICE_P700
Official device files on CyanogenMod have only "jellybean" branch, so I used TeamHackLG repo.
On cm-10.1:
<project path="device/lge/e610" name="TeamHackLG/android_device_lge_e610" remote="github" revision="cm-10.1" />
<project path="device/lge/msm7x27a-common" name="TeamHackLG/android_device_lge_msm7x27a-common" remote="github" revision="cm-10.1" />
<project path="device/lge/p700" name="TeamHackLG/android_device_lge_p700" remote="github" revision="cm-10.1" />
<project path="kernel/lge/msm7x27a-common" name="TeamHackLG/lge-kernel-lproj" remote="github" revision="android-msm-3.4-jb42" />
<remove-project name="CyanogenMod/android_bootable_recovery" />
<project path="bootable/recovery" name="PhilZ-cwm6/philz_touch_cwm6" remote="github" revision="cm-10.1" />
On cm-10.2:
<project path="device/lge/e610" name="TeamHackLG/android_device_lge_e610" remote="github" revision="cm-10.2" />
<project path="device/lge/msm7x27a-common" name="TeamHackLG/android_device_lge_msm7x27a-common" remote="github" revision="cm-10.2" />
<project path="device/lge/p700" name="TeamHackLG/android_device_lge_p700" remote="github" revision="cm-10.2" />
<project path="kernel/lge/msm7x27a-common" name="TeamHackLG/lge-kernel-lproj" remote="github" revision="android-msm-3.4-jb4.3" />
<remove-project name="CyanogenMod/android_bootable_recovery" />
<project path="bootable/recovery" name="PhilZ-cwm6/philz_touch_cwm6" remote="github" revision="cm-10.2" />
Builds without errors, flashes and works.
Recovery and boot images from stock p700 v20e (P70020e-EUR-XX, Android 4.1.2, kernel 3.4.0)
P.S. Aroma File Manager has picture rotated by 180 deg, while touch areas are correctly oriented,
Seems this is due ro.sf.hwrotation=180 for p700.
Click to expand...
Click to collapse
Anybody tried this?
from LG-P705G w/ Vanir Rom Weeklies
Here's safe CMW 6.0.3.2 Touch flashable http://www.sendspace.com/file/i3see9
bootloader link is dead
dead link bro
Fetching projects: 99% (407/411) Fetching project platform/developers/docs
error: Cannot fetch androidarmv6/android_kernel_goldfish
warn: --force-broken, continuing to sync
Fetching projects: 100% (411/411), done.
Syncing work tree: 69% (284/411) error: revision cm-10.1_2.6.29 in androidarmv6/android_kernel_goldfish not found
[email protected]:~/armv6$
How to solve this error?
Edit: I have seen in androidarmv6 github, there is no android_kernel_goldfish project...but my roomservice.xml points to that project....if i remove it, then there are lots of errors....how to get past that error @androidarmv6, @A_U anna... @erikcas, @yajnab
This is my roomservice.xml:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="androidarmv6/android_kernel_goldfish" path="kernel/goldfish" remote="github" revision="cm-10.1_2.6.29" />
<project name="androidarmv6/android_device_samsung_tass" path="device/samsung/tass" remote="github" />
<project name="androidarmv6/android_kernel_samsung_msm" path="kernel/samsung/msm" remote="github" revision="jb_chocolate-samsung" />
<project name="androidarmv6/android_kernel_samsung_msm7x27" path="kernel/samsung/msm7x27" remote="github" />
<project name="androidarmv6/android_device_qcom_msm7x27" path="device/qcom/msm7x27" remote="github" />
<project name="androidarmv6/android_device_samsung_msm7x27-common" path="device/samsung/msm7x27-common" remote="github" />
<project name="androidarmv6/android_vendor_samsung" path="vendor/samsung" remote="github" />
<project name="androidarmv6/android_vendor_qcom_msm7x27" path="vendor/qcom/msm7x27" remote="github" />
<project name="androidarmv6/android_hardware_atheros_ath6kl-compat" path="hardware/atheros/ath6kl-compat" remote="github" />
<project name="androidarmv6/android_hardware_atheros_wifi_libs" path="hardware/atheros/wifi/libs" remote="github" />
<project name="androidarmv6/android_hardware_broadcom_fmradio" path="hardware/broadcom/fmradio" remote="github" />
</manifest>
Venkatesh said:
Fetching projects: 99% (407/411) Fetching project platform/developers/docs
error: Cannot fetch androidarmv6/android_kernel_goldfish
warn: --force-broken, continuing to sync
Fetching projects: 100% (411/411), done.
Syncing work tree: 69% (284/411) error: revision cm-10.1_2.6.29 in androidarmv6/android_kernel_goldfish not found
[email protected]:~/armv6$
How to solve this error?
Edit: I have seen in androidarmv6 github, there is no android_kernel_goldfish project...but my roomservice.xml points to that project....if i remove it, then there are lots of errors....how to get past that error @androidarmv6, @A_U anna... @erikcas, @yajnab
This is my roomservice.xml:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="androidarmv6/android_kernel_goldfish" path="kernel/goldfish" remote="github" revision="cm-10.1_2.6.29" />
<project name="androidarmv6/android_device_samsung_tass" path="device/samsung/tass" remote="github" />
<project name="androidarmv6/android_kernel_samsung_msm" path="kernel/samsung/msm" remote="github" revision="jb_chocolate-samsung" />
<project name="androidarmv6/android_kernel_samsung_msm7x27" path="kernel/samsung/msm7x27" remote="github" />
<project name="androidarmv6/android_device_qcom_msm7x27" path="device/qcom/msm7x27" remote="github" />
<project name="androidarmv6/android_device_samsung_msm7x27-common" path="device/samsung/msm7x27-common" remote="github" />
<project name="androidarmv6/android_vendor_samsung" path="vendor/samsung" remote="github" />
<project name="androidarmv6/android_vendor_qcom_msm7x27" path="vendor/qcom/msm7x27" remote="github" />
<project name="androidarmv6/android_hardware_atheros_ath6kl-compat" path="hardware/atheros/ath6kl-compat" remote="github" />
<project name="androidarmv6/android_hardware_atheros_wifi_libs" path="hardware/atheros/wifi/libs" remote="github" />
<project name="androidarmv6/android_hardware_broadcom_fmradio" path="hardware/broadcom/fmradio" remote="github" />
</manifest>
Click to expand...
Click to collapse
Remove the roomservice.xml and resync
yajnab said:
Remove the roomservice.xml and resync
Click to expand...
Click to collapse
Thanks yajnab...but i din't fix..produced more errors....nevermind fixed it already...what i did is created another directory and referencing previous directory intialized repo in newly created directory and did repo sync....already compiled a build for my mini also....everything working except camera.... din't applied camera force close hack...
yajnab said:
Remove the roomservice.xml and resync
Click to expand...
Click to collapse
this is what happened after removing roomservice.xml
Syncing work tree: 99% (396/400) Traceback (most recent call last):
File "/home/venkatesh/armv6/.repo/repo/main.py", line 418, in <module>
_Main(sys.argv[1:])
File "/home/venkatesh/armv6/.repo/repo/main.py", line 394, in _Main
result = repo._Run(argv) or 0
File "/home/venkatesh/armv6/.repo/repo/main.py", line 142, in _Run
result = cmd.Execute(copts, cargs)
File "/home/venkatesh/armv6/.repo/repo/subcmds/sync.py", line 657, in Execute
project.Sync_LocalHalf(syncbuf)
File "/home/venkatesh/armv6/.repo/repo/project.py", line 1106, in Sync_LocalHalf
lost = self._revlist(not_rev(revid), HEAD)
File "/home/venkatesh/armv6/.repo/repo/project.py", line 2074, in _revlist
return self.work_git.rev_list(*a, **kw)
File "/home/venkatesh/armv6/.repo/repo/project.py", line 2227, in rev_list
p.stderr))
error.GitError: CyanogenMod/android_vendor_qcom_opensource_v8 rev-list ('^ed6baff3b8971fe968a30c0c7dc631be1f31fd5c', 'HEAD', '--'): fatal: bad object HEAD
Hi everybody,
I've found a thread about [GUIDE][AOSPA:v3.+] How to Compile AOSPA from Source : + Support and Maintenance . So with help from @Kevinjoa im start building ubuntu 13.10 machine for compiling.
Now i've problem with local_manifest.xml which last night attempt i got Error : fetch from source.
My local_manifest.xml :
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="Kevindeving/android_device_samsung_golden" path="device/samsung/golden" />
<project name="Kevindeving/android_kernel_samsung_golden" path="kernel/samsung/golden" />
<project name="OliverG96/android_vendor_samsung_golden" path="vendor/samsung/golden" />
</manifest>
Click to expand...
Click to collapse
From the tutorial it shows like this :
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="ParanoidAndroid/android_device_samsung_i9300" path="device/samsung/i9300" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_kernel_samsung_smdk4412" path="kernel/samsung/smdk4412" remote="github" revision="cm-10.2" />
<project name="ParanoidAndroid/android_device_samsung_smdk4412-common" path="device/samsung/smdk4412-common" remote="github" revision="cm-10.2" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-10.2" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-10.2" />
</manifest>
Click to expand...
Click to collapse
My question is, what should i replace in :
<project name="ParanoidAndroid/android_device_samsung_i9300" path="device/samsung/i9300" remote="github" revision="cm-10.2" />
<project name="ParanoidAndroid/android_device_samsung_smdk4412-common" path="device/samsung/smdk4412-common" remote="github" revision="cm-10.2" />
Click to expand...
Click to collapse
Thanks in advance!
Hi there!
I'm receiving some pm about users that want to learn how to build LineageOS for the Galaxy Note 4 (snapdragon), so here is a quick guide:
Only supported device for now are trltexx/trltedt (N910F/N910G) and trltetmo/trltecan (N910T/N910W8)
I suggest to use a LTS version of ubuntu, in this guide I'll be using Ubuntu 16.04
Let's start with a bit of cleaning:
Code:
sudo apt-get remove openjdk-* icedtea-* icedtea6-*
Install java8:
Code:
sudo add-apt-repository ppa:openjdk-r/ppa
sudo apt-get update && sudo apt-get install openjdk-8-jdk
Install build tools:
Code:
sudo apt-get install git ccache automake lzop bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 g++-multilib python-networkx libxml2-utils bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev squashfs-tools pngcrush schedtool dpkg-dev liblz4-tool make optipng maven
Install repo:
Code:
mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
Edit ~/.bashrc (in this exaple I'm using gedit to do it):
Code:
gedit ~/.bashrc
Add those 2 lines at the bottom of the file (we are going to add also ccache to speed up our build time):
Code:
export PATH=~/bin:$PATH
export USE_CCACHE=1
Save it, close gedit and run:
Code:
source ~/.bashrc
Let's create some folders where we'll be doing the magic:
Code:
mkdir ~/android && cd ~/android
mkdir lineageos && cd lineageos
Initialize the local repo and download the source:
Code:
repo init -u git://github.com/LineageOS/android.git -b cm-14.1
repo sync --force-sync
It'll take quite some time, depends on your internet connection.
Once it's done downloading and checking out the files:
Code:
cd .repo
mkdir local_manifests && cd local_manifests
Now create a new file in this folder, name it "roomservice.xml" and add this into it:
For trltexx/trltedt:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="underscoremone/android_kernel_samsung_trlte" path="kernel/samsung/trlte" remote="github" revision="cm-14.1" />
<project name="underscoremone/android_device_samsung_trlte-common" path="device/samsung/trlte-common" remote="github" revision="cm-14.1" />
<project name="underscoremone/android_device_samsung_trltexx" path="device/samsung/trltexx" remote="github" revision="cm-14.1" />
<project name="underscoremone/proprietary_vendor_samsung_trlte" path="vendor/samsung" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.1" />
</manifest>
For trltetmo/trltecan:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="underscoremone/android_kernel_samsung_trlte" path="kernel/samsung/trlte" remote="github" revision="cm-14.1" />
<project name="underscoremone/android_device_samsung_trlte-common" path="device/samsung/trlte-common" remote="github" revision="cm-14.1" />
<project name="fat-tire/android_device_samsung_trltetmo" path="device/samsung/trltetmo" remote="github" revision="cm-14.1" />
<project name="underscoremone/proprietary_vendor_samsung_trlte" path="vendor/samsung" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.1" />
</manifest>
Now go back to the root of the source ("lineageos" folder) and repo sync again
Code:
cd ../..
repo sync
It'll now download the specific repositories for your device.
Then run
for trltexx/trltedt
Code:
. build/envsetup.sh && brunch trltexx
or for trltetmo/trltecan
Code:
. build/envsetup.sh && brunch trltetmo
And your build will start.
Once done you'll find your flashable rom.zip file in out/target/product/trlte**/
Congratulations you've successfully compiled LineageOS 14.1 for your device.
Remember to "make clean" every now and then.
------
Sometimes you'll get some errors, try to google the error and if you can not find a solution ask for help here at xda.
------
Hopefully I didn't forget anything.. if you have any trouble following this guide reply to this thread; myself or someone else will try to help you as soon as possible.
If you like to have the keyboard with the extra numbers row add this (before "</manifest>") to your roomservice.xml:
Code:
<remove-project name="LineageOS/android_packages_inputmethods_LatinIME" />
<project name="underscoremone/android_packages_inputmethods_LatinIME" path="packages/inputmethods/LatinIME" remote="github" revision="_cm-14.1" />
-----------------------------------------------------------------------------------------
If you want to include su to your builds you have to run
Code:
export WITH_SU=true
before starting the build.
If you want to always include it you can add the same line to your .bashrc (remember to run "source ~/.bashrc" after you modify .bashrc)
Hello,
First of all thank you for sharing this guide.
I haven't yet compiled with success but so far one of the errors I've encountered is that i need to include the following in my local manifest:
Code:
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-14.1" />
or else I'm getting an error about missing macloader.h
Running a compile now so i will return once that finished
Diload said:
Hello,
First of all thank you for sharing this guide.
I haven't yet compiled with success but so far one of the errors I've encountered is that i need to include the following in my local manifest:
Code:
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-14.1" />
or else I'm getting an error about missing macloader.h
Running a compile now so i will return once that finished
Click to expand...
Click to collapse
Yep, you're right; I've missed it. I've updated the op.
Edit:
Actually I thought it was going to be downloaded automatically because it is included in the dependencies of "android_device_samsung_qcom-common".. maybe I'm wrong. Anyway I've added it to the guide's trltexx.xml, you may want to be aware that we still need "android_packages_resources_devicesettings" "android_packages_apps_FlipFlap" and "android_hardware_sony_timekeep", they should be automatically added to your roomservice.xml (because they are included in our lineage.dependencies) but if it doesn't happen you probably want to add it to your trltexx.xml.
How are things different if I want to build for TMO? How much disk space you need?
Sent from my SM-N910T using Tapatalk
rob_z11 said:
How are things different if I want to build for TMO? How much disk space you need?
Sent from my SM-N910T using Tapatalk
Click to expand...
Click to collapse
I've updated the op with the changes needed for trltetmo/trltecan.
You need approximately 60gb, but I would go with more if you can.
hi can you show me how to build for the n910w8 ?
outstanding
Sent from my SM-N9300 using Tapatalk
Okay so i finally got a working build compiled, got a lot of issues with java compiler and javadoc using too much memory,
if anyone is interested it is fixed by setting
Code:
$ export ANDROID_JACK_VM_ARGS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4G"
Just edit the 4G in the end to the amount of ram you would allow the java compiler to run, be aware that you would still need about an additional of 4,5 gigs of ram available other than what you specify here, at least that was the case for me, since the java compiler doesn't clear out when other stuff is processed during the compile (like c, c++ and javadoc compilation)
_mone said:
Yep, you're right; I've missed it. I've updated the op.
Edit:
Actually I thought it was going to be downloaded automatically because it is included in the dependencies of "android_device_samsung_qcom-common".. maybe I'm wrong. Anyway I've added it to the guide's trltexx.xml, you may want to be aware that we still need "android_packages_resources_devicesettings" "android_packages_apps_FlipFlap" and "android_hardware_sony_timekeep", they should be automatically added to your roomservice.xml (because they are included in our lineage.dependencies) but if it doesn't happen you probably want to add it to your trltexx.xml.
Click to expand...
Click to collapse
I don't know, when I run brunch it doesn't create the roomservice.xml file, i think that it gets done with the breakfast command, but that would create instances in my roomservice.xml that conflicted with the trltexx repos pulled from another source from the other local manifest.
So i ended up with this local manifest (i.e. trltexx.xml)
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/samsung/trlte-common" name="Diload/android_device_samsung_trlte-common" remote="github" revision="cm-14.1" />
<project path="kernel/samsung/trlte" name="Diload/android_kernel_samsung_trlte" remote="github" revision="cm-14.1" />
<project path="device/samsung/trltexx" name="Diload/android_device_samsung_trltexx" remote="github" revision="cm-14.1" />
<project path="vendor/samsung" name="Diload/proprietary_vendor_samsung_trlte" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_packages_apps_FlipFlap" path="packages/apps/FlipFlap" remote="github" revision="cm-14.1" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" revision="cm-14.1" />
</manifest>
And it is now running on my phone
Well done @Diload :good:
elitedz said:
hi can you show me how to build for the n910w8 ?
Click to expand...
Click to collapse
If you want build for trltecan (N910W8) follow this guide and make the changes described for trltetmo. trltetmo and trltecan, like trltexx and trltedt can share the same ROM.
_mone said:
If you want build for trltecan (N910W8) follow this guide and make the changes described for trltetmo. trltetmo and trltecan, like trltexx and trltedt can share the same ROM.
Click to expand...
Click to collapse
thank you
how about some love for the N910V ???
hi! I how about NOTE 4 DUOS N9100 which has two sim? Now only one sim works，wifi and another sim donot work. how solve it？Thanks!
Nice clear info!
Thanks!
Especially the part about local manifest, other guides I've read in past never touch on that part. Thank you.
N910V never gets any love
ok so what would I have to do to make one strictly for the N910V ? id just change it to trltevzw ?
happy2472 said:
N910V never gets any love
ok so what would I have to do to make one strictly for the N910V ? id just change it to trltevzw ?
Click to expand...
Click to collapse
For trltevzw you may want to have a look at the verzion forum and ask the recognized developers that are building LineageOS to share their source. Good luck with that!
_mone said:
For trltevzw you may want to have a look at the verzion forum and ask the recognized developers that are building LineageOS to share their source. Good luck with that!
Click to expand...
Click to collapse
Im guessing thats like gold??
What's the point installing lineageos on note4?
Not trolling... Just curious.
I bet we will lose everything this phone is great about (s pen menu etc.).
Thanks!
bat0nas said:
What's the point installing lineageos on note4?.
Click to expand...
Click to collapse
This is probably not the right place for such a discussion as this is about building LineageOS yourself, based on the the guide that _mone has very kindly provided. I suggest opening a new thread yourself inviting discussion/advice, or maybe look around the various LineageOS dev threads to see what people are saying. The known issues / missing functionality is pretty well documented, but I'm sure people will be happy let you know in a thread where it is appropriate