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?

[Q] How to compile from source a S3Neo ROM?

Hi all,
I've already read all the useful posts on XDA to build up a ROM, I've built rom for P990 with success some times ago.
Now I'm trying to build a CM12 rom and kernel for our S3 Neo but something goes wrong.
Anyone of our developers could explain me what kinds of commands we need to write to build up with success?
this is my first test on a Samsung and I already hate it, not an help or tutorial on a samsung devs forum (stupid forum, of course).
I've tried to build up only a kernel with Google chains 4.6 with those commands:
Code:
make ARCH=arm CROSS_COMPILE=pathofmycompiler
next:
Code:
make msm8226_defconfig VARIANT_DEFCONFIG=msm8226-sec_s3ve3g_defconfig
It builds a config files:
Next i lauch:
Code:
make -j4
and lots of error... ok, fix it, make a clean and retry... build a zimage, test it and.. doesn't work.
Where I'm wrong? Anyone could post a complete tutorial to build from source for our phone? :crying:

sev3n1985 said:
Hi all,
I've already read all the useful posts on XDA to build up a ROM, I've built rom for P990 with success some times ago.
Now I'm trying to build a CM12 rom and kernel for our S3 Neo but something goes wrong.
Anyone of our developers could explain me what kinds of commands we need to write to build up with success?
this is my first test on a Samsung and I already hate it, not an help or tutorial on a samsung devs forum (stupid forum, of course).
I've tried to build up only a kernel with Google chains 4.6 with those commands:
Code:
make ARCH=arm CROSS_COMPILE=pathofmycompiler
next:
Code:
make msm8226_defconfig VARIANT_DEFCONFIG=msm8226-sec_s3ve3g_defconfig
It builds a config files:
Next i lauch:
Code:
make -j4
and lots of error... ok, fix it, make a clean and retry... build a zimage, test it and.. doesn't work.
Where I'm wrong? Anyone could post a complete tutorial to build from source for our phone? :crying:
Click to expand...
Click to collapse
You have dowloaded cm12 right with all s3 neo specific?
to run buld go :
source build/envsetup.sh
breakfast "device code name chose one from list"
for full build chose : brunch grouper
for kernel only with ramdisk(to make boot.img) : make bootimage
fi you need more contact me

n1kolaa said:
You have dowloaded cm12 right with all s3 neo specific?
to run buld go :
source build/envsetup.sh
breakfast "device code name chose one from list"
for full build chose : brunch grouper
for kernel only with ramdisk(to make boot.img) : make bootimage
fi you need more contact me
Click to expand...
Click to collapse
Tnks man, i would compile only kernel because i haven't ever compiled a CM and i know only something about kernel modding.
So i need to compile all?

sev3n1985 said:
Tnks man, i would compile only kernel because i haven't ever compiled a CM and i know only something about kernel modding.
So i need to compile all?
Click to expand...
Click to collapse
no. if you have cm mainfest i tell you how to compile only kernel and that is easyest whay and best whay

ok, after 7 hours now i have cm12 source code, i've launched breakfast the code name but obviously not found.
So i need to create the local_manifest.xml under .repo/local_manifest.xml :
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="MSM8226-Samsung/android_kernel_samsung_s3ve3g.git" path="/kernel/samsung/s3ve3g" remote="github" revision="cm-12.0"/>
<project name="MSM8226-Samsung/android_device_samsung_s3ve3g.git" path="/device/samsung/s3ve3g" remote="github" revision="cm12.0" />
<project name="MSM8226-Samsung/android_device_samsung_msm8226-common.git" path="/device/samsung/msm8226-common" remote="github" revision="cm12.0"/>
<project name="MSM8226-Samsung/android_vendor_samsung_s3ve3g.git" path="/vendor/samsung/s3ve3g" remote="github" revision="cm-12.0"/>
<project name="MSM8226-Samsung/proprietary_vendor_samsung.git" path="vendor/samsung" remote="github" revision="cm12.0"/>
</manifest>
I've some problems to identify the correct paths, could you see if all are correctly?
Compiled but when make the zimage a stupid error
Export includes file: external/compiler-rt/Android.mk -- /home/antonio/cm12/out/target/product/s3ve3g/obj/STATIC_LIBRARIES/libcompiler_rt-extras_intermediates/export_includes
make: *** Nessuna regola per generare l'obiettivo "/home/antonio/cm12/out/target/product/s3ve3g/obj/STATIC_LIBRARIES/libinit_msm_intermediates/export_includes", necessario per "/home/antonio/cm12/out/target/product/s3ve3g/obj/EXECUTABLES/init_intermediates/import_includes". Arresto.
#### make failed to build some targets (30:53 (mm:ss)) ####
Any solution?

[ROM][6.0.1][UNOFFICIAL][WIP] Cyanogenmod 13.0 - SM-T700

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.​
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
Important information:
This thread is for Unofficial CyanogenMod 13.0 builds for klimtwifi (SM-T700). The following will not be supported here:
Custom kernels
Mods
Xposed
I don't support Xposed and any logcat which includes a Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Installation
First time flashing CyanogenMod 13.0 on your device, or coming from another ROM?
Download the zip(s)
Install a compatible Recovery
Make sure you are on the latest bootloader (Download below)
Perform a nandroid backup of your current ROM (Optional)
Wipe data/factory reset
Flash CyanogenMod
Install the Google Apps addon package (Optional)
Reboot
Other issues?
Before posting in this thread, make sure of a few things:
You used the search function of the forums.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread.
Logs! You can use this: https://play.google.com/store/apps/d....tortel.syslog
Downloads
CyanogenMod:
2/08 Build
2/10 Build
4/4 Build
4/11 Build
5/14 Build
Google Apps:
http://opengapps.org/- thanks to the OpenGapps team!
Latest T700 bootloader (Thanks @Schischu)
Here
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Source:
Kernel: https://github.com/CM-Tab-S/android_kernel_samsung_klimtwifi
Device Tree: https://github.com/CM-Tab-S/android_device_samsung_klimtwifi
Credits:
@Barracuda77777 (For helping along the way)
@UpInTheAir for his kernel magic and misc fixes
@crpalmer (for picassowifi device and kernel gits - the base @Barracuda77777 and @nvertigo67 started of from)
@eousphoros (for his device git)
@nvertigo67 (for his work on chagallwifi)
@Nexorrr (for his work on chagalllte)

Bugs:
Camera
My Local manifest this will allow you to build any of the tab s variants
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CM-Tab-S/android_device_samsung_klimtwifi" path="device/samsung/klimtwifi" remote="github" />
<project name="CM-Tab-S/android_device_samsung_klimtlte" path="device/samsung/klimtlte" remote="github" />
<project name="CM-Tab-S/android_device_samsung_chagallwifi" path="device/samsung/chagallwifi" remote="github" />
<project name="CM-Tab-S/android_device_samsung_chagalllte" path="device/samsung/chagalllte" remote="github" />
<project name="CM-Tab-S/android_device_samsung_chagallltetmo" path="device/samsung/chagallltetmo" remote="github" />
<project name="CM-Tab-S/android_kernel_samsung_klimtwifi" path="kernel/samsung/klimtwifi" remote="github" revision="deathly_cm-13.0" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos" path="hardware/samsung_slsi-cm/exynos" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_exynos5" path="hardware/samsung_slsi-cm/exynos5" remote="github" />
<project name="CM-Tab-S/android_hardware_samsung_slsi-cm_exynos5420" path="hardware/samsung_slsi-cm/exynos5420" remote="github" />
<project name="CyanogenMod/android_hardware_samsung_slsi-cm_openmax" path="hardware/samsung_slsi-cm/openmax" remote="github" />
<project name="CyanogenMod/android_external_stlport" path="external/stlport" remote="github" />
<project name="deadman96385/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="cm-13.0-common" />
<remove-project name="platform/prebuilts/qemu-kernel" />
<project path="prebuilts/qemu-kernel" name="platform/prebuilts/qemu-kernel" clone-depth="1" remote="aosp" revision="refs/tags/android-6.0.1_r31" />
</manifest>

Reserved

Enable rotation on the homescreen:
Long press on the homescreen select the up arrow and select allow rotation

Sweet. Will try this evening.

When do you plan making a build for the T705 (klimtlte)? I already tried my luck with building. The kernel booted, but I didn't boot completely up. This is my new device tree which I unfortunately can not test, because I have to redownload the sources: https://github.com/haimann951/android_device_samsung_klimtlte

oh yeah!
i will give it a try!

Thanks for this man ! Will try to install and will report back in a few minutes @deadman96385

haimann95 said:
When do you plan making a build for the T705 (klimtlte)? I already tried my luck with building. The kernel booted, but I didn't boot completely up. This is my new device tree which I unfortunately can not test, because I have to redownload the sources: https://github.com/haimann951/android_device_samsung_klimtlte
Click to expand...
Click to collapse
Soon, i have a klimtlte being shipped to me now. Once it arrives i will release a build.

I installed the rom and i said "WOW!"
its not 100% smooth but it is very good for a first build.
one question: how can i change the background in lock screen?

Thanks dead man, been waiting on a cm13 for the tab s. Judging on your other work I bet this is great. Downloading as I write

Does heat issue in gaming and dast battery drain stil presist in cm13 because it was in cm12.1 and thats the only thjng that kept mi away from CM

rookie12 said:
Does heat issue in gaming and dast battery drain stil presist in cm13 because it was in cm12.1 and thats the only thjng that kept mi away from CM
Click to expand...
Click to collapse
Currently there is a wakelock issue but before i had that bug there was no heating or battery drain issues.

deadman96385 said:
Currently there is a wakelock issue but before i had that bug there was no heating or battery drain issues.
Click to expand...
Click to collapse
So 40•C is normal when playing games and battery drains from 100 t0 p in 1 or 2 hours?

rookie12 said:
So 40•C is normal when playing games and battery drains from 100 t0 p in 1 or 2 hours?
Click to expand...
Click to collapse
Chill man i mean't on cm-13.0 on builds that i did not release, so once this wakelock bug is fixed your heating and power problems will be solved.

Bootloop when installing Beta-SuperSU 2.50.
Installed CM13 and Gaps, booted to android. configured first time. Rebooted to recovery and installed SuperSU, bootlooping....
Update:
Solved by installing UPDATE-SuperSU-v2.65-20151226141550.zip

Venzent said:
Bootloop when installing Beta-SuperSU 2.50.
Installed CM13 and Gaps, booted to android. configured first time. Rebooted to recovery and installed SuperSU, bootlooping....
Update:
Solved by installing UPDATE-SuperSU-v2.65-20151226141550.zip
Click to expand...
Click to collapse
Why flash supersu when there is root built in?

deadman96385 said:
Why flash supersu when there is root built in?
Click to expand...
Click to collapse
Maybe my lack of knowledge, I'm not that deep into custom builds, but I thought SuperSU is always needed to provide root access when apps requesting it? (the always allow or ask again within 15 minutes question).

Venzent said:
Maybe my lack of knowledge, I'm not that deep into custom builds, but I thought SuperSU is always needed to provide root access when apps requesting it? (the always allow or ask again within 15 minutes question).
Click to expand...
Click to collapse
If you unlock developer settings by tapping the build number in about tablet and then go to developer settings find the Root access option and select Apps only and you will have the same option as supersu it will prompt you when somthing wants to have root with an option to always allow it.

deadman96385 said:
If you unlock developer settings by tapping the build number in about tablet and then go to developer settings find the Root access option and select Apps only and you will have the same option as supersu it will prompt you when somthing wants to have root with an option to always allow it.
Click to expand...
Click to collapse
Thanks, didn't know that.....
And thanks for the ROM also of course
---------- Post added at 08:31 PM ---------- Previous post was at 08:03 PM ----------
Ok,
(very) first findings.
ROM is fast, smooth, no problems so far, heating and/or battery drain must be waited for in the upcoming days (if exists).
2 issues, Facebook FC's, directly at startup, and when an app that uses FB starts, it gives the CF error as well (like Candy Crush).
KPN iTV online (local televison provider, streaming application), gives black screen in app instead of the stream 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: