Database Users

[Q] Attempting to build Cyanogenmod 11 from source, odd error

Hi, figured this was the best place to post this as I can't post in the CM maintainers thread yet.
I'm experimenting with building Cyanogenmod 11 from source for my Note 3 (hlte), with the ultimate aim of learning to contribute to CM. I've been following along with the CM wiki page for building for hlte but have hit a bit of a roadblock.
About 10 minutes into the brunch hlte make process, I'm getting a weird error:
make: No rule to make target `vendor/samsung/hlte/proprietary/lib/cdma/libsec-ril.so',
needed by `/home/user/CM11/system/out/target/product/hlte/system/lib/cdma/libsec-ril.so'. Stop.
I ran the extract-files.sh to get the proprietary blobs, twice, so I'm fairly certain that isn't the problem. My phone model is the international variant (hltexx) though and I think the error might be something to do with my phone possibly not having the CDMA blobs required for the build to complete. Does anyone know how I can work around this? My phone was/is running CM11 when I extracted the proprietary blobs.

i have this exact problem. i have the tmobile note 3 and am following the CM wiki to build
http://wiki.cyanogenmod.org/w/Build_for_hlte

You can just pull the necessary files from TheMuppets repo in github. No need to extract from your phone.

That wiki page needs to be updated to mention this error. It still occurs even after running extract-propietary.sh on my hlte running the 18/4 nightly. Also, the repo init command incorrectly specifies to use the cm10.2 branch rather than the cm11.0 branch. I cannot figure out how to edit the page though, only add comments Thanks jisoo I'm going to clone that repo for the time being and I'll report back if it works

jisoo is right. Pull from TheMuppets:
https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-11.0/hlte
I am a noob aswell but intend to create a local_manifest file with the following:
<manifest>
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
</manifest>
It will download all the proprietary blobs (I hope that is the right terminology), then you can use the hlte one. I don't know git enough to get it to just download the hlte folder, if anyone does and can help I would be grateful?

[GUIDE] How to make your own CM-11.0 for your S4 mini

Hello friends!!!
I have been compiling and making roms since 2 yrs now.
I am posting here the building and compiling guide of s4 mini.
There are already similar guides for other phones on XDA.
This guide has following parts
A.Preparation
B.Downloading the source
C.Compiling and building
A. Preparation
First and foremost is use 64bit operating system
you can use UBUNTU 14.04LTS, MINT, BBQLINUX or any variant of Ubuntu or debian .
I use UBUNTU 14.04LTS and BBQ LINUX
this guide is based on ubuntu 14.04 lts
I assume that you are familiar with linux and its basic commands.
Things to be done before downloading actual android source code. (to be done once only!!!!)
1. Installing Proper version of java
Open terminal, type and install following
Code:
sudo apt-get purge openjdk-\* icedtea-\* icedtea6-\*
This will remove current java installations
2. Install oracle java 6 by following command (say OK to prompts)
Code:
sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update && sudo apt-get install oracle-java6-installer
java -version
3.After that we need to install developer utilities for building android source
Code:
sudo apt-get install git gnupg ccache lzop flex bison gperf build-essential zip curl zlib1g-dev zlib1g-dev:i386 libc6-dev lib32bz2-1.0 lib32ncurses5-dev x11proto-core-dev libx11-dev:i386 libreadline6-dev:i386 lib32z1-dev libgl1-mesa-glx:i386 libgl1-mesa-dev g++-multilib mingw32 tofrodos python-markdown libxml2-utils xsltproc libreadline6-dev lib32readline-gplv2-dev libncurses5-dev bzip2 libbz2-dev libbz2-1.0 libghc-bzlib-dev lib32bz2-dev squashfs-tools pngcrush schedtool dpkg-dev
4. After installation of above do following
Code:
sudo ln -s /usr/lib/i386-linux-gnu/mesa/libGL.so.1 /usr/lib/i386-linux-gnu/libGL.so
5. Install repo
Repo is a program which downloads and helps in syncing the source
Code:
mkdir ~/bin && curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo && chmod a+x ~/bin/repo
6.Use your favorite text editor to open ~/.bashrc - I like nano:
Code:
sudo nano ~/.bashrc
7. At the very bottom (use the Page Down key) paste this code to a new (empty) line:
Code:
export PATH=~/bin:$PATH
8. Save it. In nano that would be Ctrl-O and then Enter. Then Ctrl-X to exit back to a prompt. Restart bash:
Code:
source ~/.bashrc
B. Downloading the source
We are now going to download the source code for cyanogenmod kitkat cm-11.0
1. make a directory where you want to download the code
for guide purpose i use cm11
Code:
mkdir ~/cm11 && cd ~/cm11
2. initialise the repo for cm-11.0
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
3. make local manifest for downloading extra repositories for building for s4 mini
Code:
cd .repo
mkdir local_manifests
sudo nano s4mini.xml
copy and paste following to s4mini.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_msm8930-common" path="device/samsung/msm8930-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_serrano-common" path="device/samsung/serrano-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_serrano3gxx" path="device/samsung/serrano3gxx" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_serranoltexx" path="device/samsung/serranoltexx" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_kernel_samsung_msm8930-common" path="kernel/samsung/msm8930-common" remote="github" revision="cm-11.0" />
<project name="k2wl/android_device_samsung_serranodsdd" path="device/samsung/serranodsdd" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-11.0" />
<project name="CyanogenMod/android_hardware_qcom_fm" path="hardware/qcom/fm" remote="github" revision="cm-11.0" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
</manifest>
Save it. In nano that would be Ctrl-O and then Enter. Then Ctrl-X to exit back to a prompt.
now its time to download the sources
4. Syncing the sources
Code:
repo sync
now sit back and enjoy all the other things.
the source is around 12 to 15 gb.
so it is going to be a while before it gets downloaded.
(recommended 2mbps and above net speed for this)
you can speed up the process by adding following remove.xml in your local_manifests folder along with s4mini.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<!-- Useless Stuff -->
<remove-project name="platform/prebuilts/clang/darwin-x86/3.1"/>
<remove-project name="platform/prebuilts/clang/darwin-x86/3.2"/>
<remove-project name="platform/prebuilts/clang/darwin-x86/arm/3.3"/>
<remove-project name="platform/prebuilts/clang/darwin-x86/host/3.3"/>
<remove-project name="platform/prebuilts/clang/darwin-x86/mips/3.3"/>
<remove-project name="platform/prebuilts/clang/darwin-x86/x86/3.3"/>
<remove-project name="platform/prebuilts/gcc/darwin-x86/x86/x86_64-linux-android-4.7"/>
<remove-project name="platform/prebuilts/gcc/darwin-x86/arm/arm-eabi-4.6"/>
<remove-project name="platform/prebuilts/gcc/darwin-x86/arm/arm-eabi-4.7"/>
<remove-project name="platform/prebuilts/gcc/darwin-x86/arm/arm-linux-androideabi-4.6"/>
<remove-project name="platform/prebuilts/gcc/darwin-x86/arm/arm-linux-androideabi-4.7"/>
<remove-project name="platform/prebuilts/gcc/darwin-x86/host/headers"/>
<remove-project name="platform/prebuilts/gcc/darwin-x86/host/i686-apple-darwin-4.2.1"/>
<remove-project name="platform/prebuilts/gcc/darwin-x86/mips/mipsel-linux-android-4.6"/>
<remove-project name="platform/prebuilts/gcc/darwin-x86/mips/mipsel-linux-android-4.7"/>
<remove-project name="platform/prebuilts/gcc/darwin-x86/x86/i686-linux-android-4.6"/>
<remove-project name="platform/prebuilts/gcc/darwin-x86/x86/i686-linux-android-4.7"/>
<remove-project name="platform/prebuilts/python/darwin-x86/2.7.5"/>
</manifest>
this will remove mac related prebuilts from downloading. so saving the time and bandwidth.
During initialising repo the repo tool may ask you your name and email
make one username with github
this will be your name and [email protected] is your email address.
C. compiling and building from source
Now you have all the source you want for building your own cm-11.0 for your s4mini.
Open terminal in cm11 directory.
1.building for serrano3gxx i9190
Code:
. build/envsetup.sh && brunch serrano3gxx
2.building for serranoltexx i9195
Code:
. build/envsetup.sh && brunch serranoltexx
3.building for serranodsdd i9192
for this we need to patch some things for ril and other things to work.
Code:
cd device/samsung/serranodsdd/patches
./install-all.sh
cd
. build/envsetup.sh && brunch serranodsdd
happy building
post your queries here .
i will keep updating this thread for some more tips and tricks.

reserved1

reserved2

Reserved3

Excellent guide, thank you!

This is my first time compiling an android ROM. This is not my first time developing or compiling software. I am trying to compile the latest cm11 for my Sprint Galaxy S4 mini SPH-L520 serranoltespr using these repositories:
github (dot) com (slash) 0be/android_device_samsung_serranoltespr
github (dot) com (slash) s0be/android_vendor_samsung_serranoltespr
Is there anything else I would need to swap out in order to compile cm11 for this device properly?
Thanks!
Its so sad that there is absolutely NO development for my device. Guess I have to bite the bullet and do it myself.

dddbtc said:
This is my first time compiling an android ROM. This is not my first time developing or compiling software. I am trying to compile the latest cm11 for my Sprint Galaxy S4 mini SPH-L520 serranoltespr using these repositories:
github (dot) com (slash) 0be/android_device_samsung_serranoltespr
github (dot) com (slash) s0be/android_vendor_samsung_serranoltespr
Is there anything else I would need to swap out in order to compile cm11 for this device properly?
Thanks!
Its so sad that there is absolutely NO development for my device. Guess I have to bite the bullet and do it myself.
Click to expand...
Click to collapse
i will help in that..
i will look into repositories for the device you mentioned above...and tell you anything more can be done or not...
http://forum.xda-developers.com/showthread.php?t=2669991
this above thread shows it has cm11 already.
you can take references from that.

Hi,
How to create your own ROM in Windows ?
Thanks in advance !
Envoyé de mon iPod touch à l'aide de Tapatalk

k2wl said:
Code:
sudo apt-get purge openjdk...
Click to expand...
Click to collapse
The cm wiki suggests to use openjdk, although it seems Android doesn't really support it: http://www.javaworld.com/article/20...source-java-for-android--don-t-bet-on-it.html
Have you had experience building with openjdk?
Does it have to be Java 6?
Will old Sun versions do as well? (I see there still is 6u26 in the squeeze repo)

sun java 6 is needed to build from source upto kitkat.
i have experienced openjdk building while jb...it is hopless....too many errors....better to stick for java6.
it has been said that from android L mostly google will support openjdk 7
i dont know that yet for sure.
@darckmin93100 for building on windows u need virtual machine with 8 gb ram atleast 30gb swap space and 200gb virtual hdd configured for linux guest.
if you have that much on your pc then go ahead...make a virtual machine of that configuration and build.

k2wl said:
Code:
...
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-11.0" />
...
Click to expand...
Click to collapse
Does this equal to extracting proprietary blobs?
Anything else to regard when using extract-files.sh instead of the repo?

And another one:
k2wl said:
Code:
...
<project name="CyanogenMod/... remote="github" revision="cm-11.0" />
...
Click to expand...
Click to collapse
Does revision "cm-11.0" refer to the nightly branch and "stable/cm-11.0" to the M snapshot releases?

aguaz said:
Does this equal to extracting proprietary blobs?
Anything else to regard when using extract-files.sh instead of the repo?
Click to expand...
Click to collapse
yes it represents equal to extracting libs from device with extract-riles.sh
aguaz said:
And another one:
Does revision "cm-11.0" refer to the nightly branch and "stable/cm-11.0" to the M snapshot releases?
Click to expand...
Click to collapse
mostly...cm-11.0 referred to current branch i.e. nightly releases build on this and there are release branches in tags in cyanogenmod repo those are snapshots.
stable/cm-11.0 is a snapshot release branch.
shipping/cm-11.0 is final stable branch.

k2wl said:
stable/cm-11.0 is a snapshot release branch.
Click to expand...
Click to collapse
While the project tree remains the same for stable/cm-11.0 in between M releases, I witnessed changes to some projects themselves. What are those changes? Bug fixes?
And as there are changes, I assume it is impossible to build a replica of an M release if you haven't fetched the sources in the very right moment of the release!?

aguaz said:
While the project tree remains the same for stable/cm-11.0 in between M releases, I witnessed changes to some projects themselves. What are those changes? Bug fixes?
And as there are changes, I assume it is impossible to build a replica of an M release if you haven't fetched the sources in the very right moment of the release!?
Click to expand...
Click to collapse
now cm is in m release mode i.e m for monthly stable builds.
so for if you build in that month then it is still that month's m release

k2wl said:
so for if you build in that month then it is still that month's m release
Click to expand...
Click to collapse
Not exactly. As mentioned above, the project tree does not change (no additions or removals), but projects themselves do get updates.
Is there a snapshot that refers to the actual release?

@aguaz
i am not understanding what exactly your point???
look in cm projects..there is branch called stable/cm-11.0 it is snapshot release branch as far as i know.
it almost get updated every month. look in the history of the branches..
like in the manifest.xml
in stable branch
<default revision="refs/heads/stable/cm-11.0" remote="github" sync-c="true" sync-j="4" />
Click to expand...
Click to collapse
and in regular cm-11.0
<default revision="refs/heads/cm-11.0" remote="github" sync-c="true" sync-j="4" />
Click to expand...
Click to collapse
that way stable releases are on stable branches and nightlies are in cm-11.0 current branch.
i hope i make my point clear..

OK, I try to make myself more clear:
I'm solely talking about the release tree "stable/cm-11.0". Every blue moon or so a new stable tree is merged and an "M" snapshot build and released. That tree does not change until the next release in terms of that there are no additions or removals of projects.
However projects themselves do receive updates during that time. See for example the ongoing commits to android_frameworks_base. I assume those are only bug fixes!?
For whatever reason the builds are not updated, but the source is.
So I was wondering if there is a snapshot of the stable/cm-11.0 tree available that actually refers to the state of the release.

@aguaz
ya bug fixes are coming in all the time.
to get the snapshot tree at that given time go in the releases tab on github and sync that
like https://github.com/CyanogenMod/android/releases

k2wl said:
to get the snapshot tree at that given time go in the releases tab on github and sync that
like https://github.com/CyanogenMod/android/releases
Click to expand...
Click to collapse
Those refer to the shipping/cm-11.0 tree, but this branch also got updated after the build release. Not even all cm projects have a shipping branch!? Also there are just 3 releases for cm-11.0, but meanwhile M10 has already been merged!
Not sure what the shipping tree is good for, but it doesn't seem to refer to the snapshot of the M releases.
Have you used repo's snapshot function? I'm wondering if such a snapshot is taken when the M releases are build and if they are available.
Another topic:
I see you've removed "patches/common/device_samsung_serrano-common" stating it has been added in main source. Which source are you referring to? It doesn't seem to be CyanogenMod/android_device_samsung_serrano-common itself.

{need testers} DOT OS DUMPLING (ROM)

im just a normal guy with no code experience which read some errors in english lol and compiled dot os for dumpling.
im going to test it later tonight but thought to share it. I dont know if it boots thats why i need yous.
I used gzosp sources and vendor from here
https://github.com/LiquidRemix-Devices/proprietary_vendor_oneplus/tree/oc-mr2/dumpling
Oh btw flash kernel is built in. Thanks tk nathanchance because his kernel is my favourite
. (if it boots ill fix the thread with proper credits) (maybe ob5 firmware or ob6???)
You most likely need to be decypted.
Can you please share the firmware and if you were decrypted or not. ill be testing it later today too on my device.
here:
https://www.androidfilehost.com/?fid=890278863836283024

Gonna give it a try my friend... downloading now...
Edit: doesnt boot so far

alewis2k12 said:
Gonna give it a try my friend... downloading now...
Edit: doesnt boot so far
Click to expand...
Click to collapse
Yep doesn't boot. Noooo wanted it to work so badly. I'll try with linesge sources but I'm getting errors atm

heres my roomservice.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="nathanchance/op5" path="kernel/oneplus/msm8998" remote="github" revision="8.1.0-unified" />
<project name="TheMuppets/proprietary_vendor_oneplus" path="vendor/oneplus" remote="github" revision="lineage-15.1" />
<project name="GZOSP-Devices/device_oneplus_dumpling" path="device/oneplus/dumpling" remote="github" revision="8.1" />
<project name="GZOSP-Devices/device_oneplus_msm8998-common" path="device/oneplus/msm8998-common" remote="github" revision="8.1" />
<project name="AospExtended-Devices/android_device_oppo_common" path="device/oppo/common" remote="github" revision="7.x" />
<project clone-depth="1" groups="pdk" name="platform/prebuilts/clang/host/linux-x86" path="prebuilts/clang/host/linux-x86/clang7" revision="master" />
</manifest>
with some edits it compiles but doesnt boot.
any suggestions guys on how to fix it? or what to add for this? ive tried lineage sources but keep keeping live display issues, missing this that. idk what to do

Wish I knew how to help, but I can confirm that it didn't boot for me either. Decrypted after flashing it with a few different firmwares and the no verity zip.

Jamie_oppo said:
heres my roomservice.xml
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="nathanchance/op5" path="kernel/oneplus/msm8998" remote="github" revision="8.1.0-unified" />
<project name="TheMuppets/proprietary_vendor_oneplus" path="vendor/oneplus" remote="github" revision="lineage-15.1" />
<project name="GZOSP-Devices/device_oneplus_dumpling" path="device/oneplus/dumpling" remote="github" revision="8.1" />
<project name="GZOSP-Devices/device_oneplus_msm8998-common" path="device/oneplus/msm8998-common" remote="github" revision="8.1" />
<project name="AospExtended-Devices/android_device_oppo_common" path="device/oppo/common" remote="github" revision="7.x" />
<project clone-depth="1" groups="pdk" name="platform/prebuilts/clang/host/linux-x86" path="prebuilts/clang/host/linux-x86/clang7" revision="master" />
</manifest>
with some edits it compiles but doesnt boot.
any suggestions guys on how to fix it? or what to add for this? ive tried lineage sources but keep keeping live display issues, missing this that. idk what to do
Click to expand...
Click to collapse
Are you sure that flash kernel will work on aosp base roms? If it works then there's something wrong with your building or else just try to include some other kernel which supports aosp base.

chinnu07 said:
Are you sure that flash kernel will work on aosp base roms? If it works then there's something wrong with your building or else just try to include some other kernel which supports aosp base.
Click to expand...
Click to collapse
well if its kernel problem. We should try. Flash the rom then flash a kernel on top. What kernel would u try. I dont think its that. Heaps of custom roms and even the cheeseburger build has the flash kernel. Thanks for replying

updater script would be my guess

benny3 said:
updater script would be my guess
Click to expand...
Click to collapse
What abt the updater script is what could be making it not boot.

guys new rom built form more lineage based source. if anyone wants to test. im hoping this will boot. i used liquid device treeanad aicp vendor. use ;atest firmware
https://www.androidfilehost.com/?fid=746163614322263400
ill test later too

Jamie_oppo said:
guys new rom built form more lineage based source. if anyone wants to test. im hoping this will boot. i used liquid device treeanad aicp vendor. use ;atest firmware
https://www.androidfilehost.com/?fid=746163614322263400
ill test later too
Click to expand...
Click to collapse
Can't get the dang thing to boot :crying:

chesstopher said:
Can't get the dang thing to boot :crying:
Click to expand...
Click to collapse
doesnt boot, stuck on op logo!

Ok ill try a clean build. That build was from before and i just changed the parts i need like device tree and msm common. And compiled. It started from 36k not the usually 100k. Ill make clean and do a clean build.
It takes 6 hrs to compile arhh
Because this local_manifest worked for the cheeseburger.
It should build to 100% without errors

Jamie_oppo said:
Ok ill try a clean build. That build was from before and i just changed the parts i need like device tree and msm common. And compiled. It started from 36k not the usually 100k. Ill make clean and do a clean build.
It takes 6 hrs to compile arhh
Because this local_manifest worked for the cheeseburger.
It should build to 100% without errors
Click to expand...
Click to collapse
Thanks man, I appreciate your efforts. dotOS seems really cool!

Just hope it doesnt error

new build. Fresh. make clean. with these source and a couple edits. only edits made were for slim in device oppo common. (shouldnt affect anything ) and the removing smart pixels from an overlay becuase that was giving errors.
this is my roomservice
<?xml version="1.0" encoding="UTF-8"?>
<!--Please do not manually edit this file-->
<manifest>
<project name="LiquidRemix-Devices/android_device_oneplus_dumpling" path="device/oneplus/dumpling" remote="github" revision="oc-mr1" />
<project name="LiquidRemix-Devices/android_device_oneplus_msm8998-common" path="device/oneplus/msm8998-common" remote="github" revision="oc-mr1" />
<project name="LiquidRemix-Devices/android_device_oppo_common" path="device/oppo/common" remote="github" revision="oc-mr1" />
<project name="LiquidRemix-Devices/proprietary_vendor_oneplus" path="vendor/oneplus" remote="github" revision="oc-mr1" />
<project name="nathanchance/op5" path="kernel/oneplus/msm8998" remote="github" revision="8.1.0-unified" />
<project clone-depth="1" groups="pdk" name="platform/prebuilts/clang/host/linux-x86" path="prebuilts/clang/host/linux-x86/clang7" revision="master" />
<project name="LineageOS/android_lineage-sdk" path="lineage-sdk" remote="github" revision="lineage-15.1" />
</manifest>
if this doesnt boot then idk what will. But it should. it did for the cheeseburger.
heres the link. make sure u have a full backup and test if its decrypted or encrypted. i have no time today. i have work and school. ill test in 24hrs if someone hasnt already.
i hope it gets to the boot animation this time lol.
https://www.androidfilehost.com/?fid=962339331458991494

Just tested it decryoted. Didnt boot. I give up lol

Jamie_oppo said:
Just tested it decryoted. Didnt boot. I give up lol
Click to expand...
Click to collapse
:crying::crying:

Jamie_oppo said:
Just tested it decryoted. Didnt boot. I give up lol
Click to expand...
Click to collapse
Hi. I was the one who built dotOS successfully for cheeseburger and it was smooth.
But as i was maintaining AospExtended ROM for cheeseburger, i didnt find it useful to continue dotOS builds.
Currently I'm Officially maintaining AEX for cheeseburger.
Coming to dotOS for dumpling,
1) does the build process gives you any error??
2)If yes what did you try to overcome it?
3) Does the flash kernel work well for dumpling too??
If you think everything is well with above questions, then get a log from adb while your phone fails to boot and attach it. I will look into it. Thanx..

drpradsms said:
Hi. I was the one who built dotOS successfully for cheeseburger and it was smooth.
But as i was maintaining AospExtended ROM for cheeseburger, i didnt find it useful to continue dotOS builds.
Currently I'm Officially maintaining AEX for cheeseburger.
Coming to dotOS for dumpling,
1) does the build process gives you any error??
2)If yes what did you try to overcome it?
3) Does the flash kernel work well for dumpling too??
If you think everything is well with above questions, then get a log from adb while your phone fails to boot and attach it. I will look into it. Thanx..
Click to expand...
Click to collapse
OK. Yes flash kernel does work well.
Next week or so. I'll start fresh with ur roomservice.
I'll get up to the errors and tell you what I did to overcome it.
From what I remember I had errors with device oppo common and for slim ( not being able to made or something)
Obviously had to edit liquid. Mk and inside common. Mk and liquid to dot. And change the boardconfig for flash kernel.
Also other other one I remember was in msm8998 common (overlay) Where smart pixels and always on display was creating errors. So I removed the troubled lines.
If it requires too much coding experience for me to do. Don't worry about it. Ive got no experience. I'm playing around with it and learning at school rn.
Thanks for your consideration

Help Building Lineage OS

I've tried compiling a lineageos 16 rom from source for the H990ds, but it is stuck at the bootlogo. I was wondering if any of you could help me enable the kernel log/console on the screen (console=tty0) or via the usb ((serial) console=ttyMSM2,115200n8). A few links: http://bootloader.wikidot.com/linux:android:serial
https://forum.xda-developers.com/showthread.php?t=829817
I tried a few things, but this is what I have now:
Code:
CONFIG_CMDLINE_FORCE=y
CONFIG_CMDLINE="console=tty0 console=ttyMSM2,115200n8"
CONFIG_SERIAL_MSM=y
CONFIG_SERIAL_MSM_CONSOLE=y
CONFIG_LOGO_LINUX_MONO=y
CONFIG_FONTS=y
CONFIG_FONT_8x8=y
CONFIG_FONT_8x16=y
CONFIG_VT=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE_DETECT_PRIMARY=y
CONFIG_FRAMEBUFFER_CONSOLE_ROTATION=y
and commenting out this line:
Code:
CONFIG_CMDLINE="console=ttyAMA0"
in the arch/arm64/configs/defconfig file, but all with no success.
I was hoping I could get some more information on why it won't boot via the console, but now I'm stuck.
I tried cat /proc/cmdline to see if it anything happened at all there, but it hasn't changed a thing after adding those lines above.
cmdline:
Code:
androidboot.bl_unlock_complete=false androidboot.authorized_kernel=true sched_enable_hmp=1 sched_enable_power_aware=1 app_setting.use_32bit_app_setting=1 kpti=1 console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 user_debug=31 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 [email protected] androidboot.hardware=elsa androidboot.bootdevice=624000.ufshc androidboot.selinux=permissive buildvariant=eng lge.rev=rev_10 model.name=LG-H990 lge.bootreason=recovery cc_mode=0 kswitch lge.bootreasoncode=0x77665502 bootcable.type=400MA lge.battid=SW3800_VC1 androidboot.dlcomplete=0 androidboot.ddr_size=4294967296 androidboot.ddr_info=0x1 lge.crash_handler=on lge.hreset=off boot_cpus=0-3 androidboot.revision=12 androidboot.verifiedbootstate=green androidboot.rpmb_state=1 androidboot.bootdevice=624000.ufshc androidboot.serialno=LGH990be84e8c0 qpnp-power-on.warm_boot=1 gpt lge.signed_image=true androidboot.baseband=msm mdss_mdp.panel=1:dsi:0:qcom,mdss_dsi_sw49407_dsc_qhd_cmd:config1:1:none:cfg:single_dsi
As you can see, it still says "console=ttyHSL0,115200,n8"
I guess I'm doing something wrong here?
I'm an amature and am completely unfamiliar with kernel coding.
Edit: I'm using the "default" msm8996 Lineage 16.0 kernel.
Edit 2: Pstore could be an alternative to what I am trying to achieve here, but yet again, I have no idea how and where to enable that. I found this https://github.com/CyanogenMod/andr...mmit/17a8ee52fac02b9ec4e8c958ed1ec70bcf2156eb but it's also a mystery to me.
BTW. How would you normally debug a build of a rom or kernel if the system does not boot?

Where did you get the source for Lineage 16 on the H990DS? From my knowledge the only LG device that has it is the G3(though I might be wrong). But in any case, you might want to ask @x86cpu since he's probably the most familiar here with building Lineage on this phone.

Ak7J4 said:
Where did you get the source for Lineage 16 on the H990DS? From my knowledge the only LG device that has it is the G3(though I might be wrong). But in any case, you might want to ask @x86cpu since he's probably the most familiar here with building Lineage on this phone.
Click to expand...
Click to collapse
All I did was initialise my dir with branch lineage-16.0 with fallback branch lineage-15.1
This is my local_manifest.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_lge_h990" path="device/lge/h990" remote="github" revision="lineage-15.1" />
<project name="LineageOS/android_device_lge_v20-common" path="device/lge/v20-common" remote="github" revision="lineage-15.1" />
<project name="LineageOS/android_device_lge_msm8996-common" path="device/lge/msm8996-common" remote="github" />
<project name="LineageOS/android_device_lge_common" path="device/lge/common" remote="github" />
<project name="LineageOS/android_kernel_lge_msm8996" path="kernel/lge/msm8996" remote="github" />
<project name="TheMuppets/proprietary_vendor_lge" path="vendor/lge" remote="github" />
</manifest>
You are right that the h990 and v20-common repo's don't have a 16.0 branch yet. I noticed that aswell, but you never know for sure that it won't work until you try.
I have commented stuff out, and added/moved lines/files to get at least a 'successful' build.
All the changes made to the source are in the attached diff.txt.

Migush said:
All I did was initialise my dir with branch lineage-16.0 with fallback branch lineage-15.1
This is my local_manifest.xml
You are right that the h990 and v20-common repo's don't have a 16.0 branch yet. I noticed that aswell, but you never know for sure that it won't work until you try.
I have commented stuff out, and added/moved lines/files to get at least a 'successful' build.
All the changes made to the source are in the attached diff.txt.
Click to expand...
Click to collapse
All devices have a lineage-16.0 branch. I created them Monday. If it gets sucks at the boot logo, it's something in the kernel in the .dtsi area. Also you cannot upgrade from 15.1 without wiping. There are also changes in 16.0 that you have to pick since they are not merged yet, they stay un-merged until it's validated they work.
You shouldn't have to comment anything out. I do know there are changes for lineage-16.0 needed for the msm8996-common area to even get past the initial make. I had to upgrade my entire build environment due to changes in the pie compiles. Still working on getting a first build.

Surprising
To see someone actually building android pie for the LG V20 is surprising, just wanted to say thanks for all your effort into making this a possibility.

That's the command line from the recovery kernel, not the one you built.
Code:
lge.bootreason=recovery
I've never tried to build lineage or debug an android kernel, but I don't think your kernel is getting loaded. Having console output probably isn't going to help you, unless you can get it from aboot.
If you want to read console output just for fun once your kernel boots, you could try ' CONFIG_CMDLINE="console=tty0 console=ttyAMA0" ' and hope it prints to the screen. Also, the serial console isn't going to help unless you have the phone opened up with probes for UART, a serial cable, etc. I don't know if qualcomm drivers support serial over USB, but that would be the way to go if they do. You could also try using netconsole, though it requires a little bit of extra setup.

x86cpu said:
Still working on getting a first build.
Click to expand...
Click to collapse
This. This makes me very happy :highfive:

Lineage 15.1 Build For Athene: Multiple Errors

Hello developers!
I am a newbie to XDA and also a newbie to ROM development, so if I am doing anything wrong, please do tell me. I own a Motorola Moto G4 Plus and I am very ready to invest as much time as needed in building and creating ROMs for this phone.
I am currently building LineageOS for this phone, and once that is done, I want to try my hand at porting Lineage 16 to this device. I had recently successfully built the cm-14.1 branch for this device (which seems to be the only official build for athene, see the LineageOS Wiki https:// wiki.lineageos.org/ devices/athene/ build#initialize-the-lineageos-source-repository). Now, I downloaded the code for LineageOS 15.1 onto my Linux computer (running Ubuntu 19.04) and have tried to build it.
Steps I took to build -
- Initialised repo with repo init.
- Synced the repository to my Linux computer with
Code:
repo sync -c --no-tags --no-clone-bundle -j24
- Created .repo/local_manifests/roomservice.xml for the device tree, kernel, etc. with the following content:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="LineageOS/android_device_motorola_athene" path="device/motorola/athene" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_kernel_motorola_msm8952" path="kernel/motorola/msm8952" remote="github" revision="lineage-15.0" />
<project name="TheMuppets/proprietary_vendor_motorola" path="vendor/motorola" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_device_qcom_common" path="device/qcom/common" remote="github" revision="lineage-15.0" />
<project name="LineageOS/android_external_bson" path="external/bson" remote="github" />
<project name="LineageOS/android_external_stlport" path="external/stlport" remote="github" />
<project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" remote="github" />
</manifest>
- Ran
Code:
repo sync -c -j24
- Then ran
Code:
export ROOMSERVICE_BRANCHES="lineage-15.0"
to specify a fallback branch
- Ran
Code:
source build/envsetup.sh
- Ran
Code:
breakfast athene
The command ran successfully, no errors until now.
- Then ran
Code:
brunch athene
This is where the problems started popping up. I got errors while building in the following places -
(Treat .(dot) as my source dir)
ERROR 1 - In out/soong/make-vars(don't remember correct file name) - Still get it after
Code:
make clobber[\CODE], I have to always comment line 692 which throws the my-check error to suppress it.
ERROR 2 - Couple of old CyanogenMod dependencies and packages which I managed to get past after messing about with the ./device/motorola/athene/BoardConfig.mk file.
ERROR 3 - Errored out because BOARD_KERNEL_IMAGE_NAME was not defined, finally found an old XDA thread for the 15.1 ROM that told me that I had to set that to zImage in device/motorola/athene/BoardConfig.mk
ERROR 4 - In file ./system/core/init/init.h - Could not find <android-base/chrono_utils.h>, Could not find <selinux/label.h> - Got rid of it by putting in relative file paths and also modifying the ./system/core/init/Android.mk's LOCAL_C_INCLUDES to have relative file paths.
ERROR 5 - In file system/core/adb/daemon/main.cpp, system/core/base/include/android-base/macros.h: Cannot identify arraysize(groups).
ERROR 6 - In file system/core/adb/daemon/main.cpp - Use of undeclared identifier 'AID_UHID'
I can try to fix these errors, but I feel that there must be some branch/fork of the LOS15.1 code that must have all these issues fixed. If anyone has any pointers regarding this or the errors, I would be very grateful.
Thanks in advance,
gamemaker1

I don't believe Lineage 15 or 15.1 ever made it to official status. LOS 14.1 was the last official rom for athene that I know of. You might take a look at this roomservice file and other noteworthy things.
https://forum.xda-developers.com/showpost.php?p=81772343&postcount=348
I've just started building myself and have built LOS 14.1 for a couple unsupported devices (atrix hd and razr hd). Also just started trying to build 16.0 for the old Razr HD but have quite a task ahead of me. Hope the link helps and good luck.

Wheels564 said:
I don't believe Lineage 15 or 15.1 ever made it to official status. LOS 14.1 was the last official rom for athene that I know of. You might take a look at this roomservice file and other noteworthy things.
https://forum.xda-developers.com/showpost.php?p=81772343&postcount=348
I've just started building myself and have built LOS 14.1 for a couple unsupported devices (atrix hd and razr hd). Also just started trying to build 16.0 for the old Razr HD but have quite a task ahead of me. Hope the link helps and good luck.
Click to expand...
Click to collapse
Ok, thanks! I just saw the link, it seems good. Will try it out today and let you know the result.

@Wheels564 Thanks a lot! You really made my day - the extra dependencies in the roomservice.xml got my build done in less than 40 minutes.
From here, I want to get (LOS 15.1 with some extra features of mine, maybe I could cherry pick some features from HavocOS or AEX) an official build out, maybe become an official contributor. If you have any tips about this, please do let me know.
Once again, thanks a ton for your timely help!
Regards,
gamemaker1

gamemaker1 said:
@Wheels564 Thanks a lot! You really made my day - the extra dependencies in the roomservice.xml got my build done in less than 40 minutes.
From here, I want to get (LOS 15.1 with some extra features of mine, maybe I could cherry pick some features from HavocOS or AEX) an official build out, maybe become an official contributor. If you have any tips about this, please do let me know.
Once again, thanks a ton for your timely help!
Regards,
gamemaker1
Click to expand...
Click to collapse
No problem at all. The only thing about LOS 15.1 is that Lineage will never make it official. They've dumped all the rest of the phone on 15.1 because of repo changes I believe. Check here: https://review.lineageos.org/269773
I'm sure they will continue to submit security patches just like 14.1. Looks like the only way to become official is to jump to 16.1. It looks like developers have had issues with athene on LOS 16.1. Glad you were able to build the rom and good luck with future projects.