Database Users

[Q] CM12 Build for S5 Primeg 906l (WIP)

Im having this errors while trying to port cm12 . this will be my first time. please guide me so I will be able to port cm12 to my device and share it to other users..
https://github.com/blhf/android_device_samsung_lentislte
https://github.com/blhf/android_device_samsung_lentislte-common
https://github.com/blhf/android_kernel_samsung_lentislte
I forked it from Note 4 since S5 prime has same specs(s805,gpu,ram,QHD) and change device name and some commits base from my build.prop
btw I already change my roomservice.xml to this
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="blhf/android_device_samsung_lentislte" path="device/samsung/lentislte" remote="github" />
<project name="blhf/android_device_samsung_lentislte-common" path="device/samsung/lentislte-common" remote="github" />
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom/common" remote="github" />
<project name="CyanogenMod/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" />
<project name="blhf/android_kernel_samsung_lentislte
" path="kernel/samsung/lentislte" remote="github" />
</manifest>

Thanks for trying, SungHun might be able to help out, or you guys even work together? :highfive:

Hey, just like you I'd wanna port resurrection remix to our device, but I couldn't even get pass the download... wanna work together on RR instead of CM?
I'm newbie as well. 
 @sktjdgns1189 is it possible for you to help us?

Device Tree needed.
Weild Hayn said:
Hey, just like you I'd wanna port resurrection remix to our device, but I couldn't even get pass the download... wanna work together on RR instead of CM?
I'm newbie as well.
@sktjdgns1189 is it possible for you to help us?
Click to expand...
Click to collapse
Audioboxer said:
Thanks for trying, SungHun might be able to help out, or you guys even work together? :highfive:
Click to expand...
Click to collapse
I have all sources of RR I just need the devices tree for S5 LTE-A X3 hope @Sunghun Park can make cm12 official so we can easily sync sources since RR is cm12 based.

Now that lollipop sources is available, will you be able to build resurrection remix? ?

[Discussion] Project CM12.1 for LG G4. Absolutly Alpha!! Dont ask for ETA Or Download

after a small look i have found CM12.1 Repos for our H815 and i think we start now Tests to get workable Builds... Think, the first way are dirty but who cares
https://github.com/lg-devs
i have nothing to do with this and this is not my three so the credits and thanks are given to LG-Devs
think this are the Devicetree what we need:
https://github.com/lg-devs/proprietary_vendor_lge
https://github.com/lg-devs/android_device_lge_g4-common
https://github.com/lg-devs/android_device_lge_h815
https://github.com/lg-devs/android_kernel_lge_msm8994
lets get start united

Interesting, hope we get UB, and root soon

I've had this building since Friday but unfortunately it gets stuck at the LG screen. I'm going to play around again this afternoon and see where I can get to.
Although the Github description for the msm8994 kernel says "G4", the H815 needs the msm8992 kernel. Also the partition sizes in g4-common aren't correct for the H815, they need to be
Code:
BOARD_SYSTEMIMAGE_PARTITION_SIZE := 4341104640
BOARD_USERDATAIMAGE_PARTITION_SIZE := 24897388544
This is the local manifest I've been using
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom_common" remote="github" revision="cm-12.1" />
<project name="lg-devs/android_device_lge_g4-common" path="device/lge/g4-common" remote="github" revision="cm-12.1" />
<project name="lg-devs/android_device_lge_h815" path="device/lge/h815" remote="github" revision="cm-12.1" />
<project name="lg-devs/android_kernel_lge_msm8992" path="kernel/lge/msm8992" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_hardware_qcom_audio" path="hardware/qcom/audio-caf/msm8992" remote="github" revision="cm-12.1-caf-8994" />
<project name="CyanogenMod/android_hardware_qcom_display" path="hardware/qcom/display-caf/msm8992" remote="github" revision="cm-12.1-caf-8994" />
<project name="CyanogenMod/android_hardware_qcom_media" path="hardware/qcom/media-caf/msm8992" remote="github" revision="cm-12.1-caf-8994" />
<project name="lg-devs/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-12.1-caf" />
</manifest>

I also tried to build CM and working with AOSP preview M1 ( source from LG devs ) but it fails. I will play with them later tonight. Hopefully find a way to solve it.
Sent from my LG-H815 using Tapatalk 2

PLEASE
We need Logcatfiles... this help another
command: adb logcat -d > logcat.txt

xadet said:
Although the Github description for the msm8994 kernel says "G4", the H815 needs the msm8992 kernel. Also the partition sizes in g4-common aren't correct for the H815, they need to be
Click to expand...
Click to collapse
In github is description for the msm8992 kernel:

Is it possible cm ROM from single SIM it can work on dual SIM by changes kernal ?

I hope someone of you guys will get it working! :good:
Thank you!

It will work sooner or later!
It's already a great news to see the start of work of CM 12.1 on G4, I just hope the camera app of stock rom can be ported

CM mods actually use the muppets repository, which the G4 isn't on yet...
https://github.com/TheMuppets/proprietary_vendor_lge
EDIT: Never mind, read above :S

We are all excited about CM12.1 coming on our smartphone, best thing to do now is just wait for the official rom to come out, which hopefully will be soon. Just be patient guys ; )

let's hope that there soon finally CM for our G4

aydinbahadir88 said:
let's hope that there soon finally CM for our G4
Click to expand...
Click to collapse
And you would have to say bye-bye to the very good LG camera...

bleuxeon said:
And you would have to say bye-bye to the very good LG camera...
Click to expand...
Click to collapse
with a hoping good port we must not say good bye
Surely, the Camera is great, but we have good alternative.. such as U-Cam

I successfully build ROM + kernel but fails to flash. Some thing to do with............" failed to mount /dev/blocl/bootdevice/by-name/system......"I also tried to flash the kernel over the stock ROM and it seems to boot fine.
update: Ummm it seems to be fine with twrp-2.8.7.0-h815.img. I can see the CM boot animation..keep fingers crossing.

Very nice @janjan!
Keep us updated please! Maybe you can make a fork with your changes if you got it running?

Let me know if any one want to play with my build and kernel. I am going to upload it incase any one want to work with it. I will continue my work as well. Going to play with AOSP later tonight or tomorrow. I think we are close to fix all the issues with CM build.
Sent from my LG-H815 using Tapatalk 2

@janjan I could be interested of your repositories.. at the moment I could not even build for h815.
Inviato dal mio LG-H815 utilizzando Tapatalk

Acutally you can use the one from the #1.... It should work..
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_qcom_common" path="device/qcom_common" remote="github" revision="cm-12.1" />
<project name="lg-devs/android_device_lge_g4-common" path="device/lge/g4-common" remote="github" revision="cm-12.1" />
<project name="lg-devs/android_device_lge_h815" path="device/lge/h815" remote="github" revision="cm-12.1" />
<project name="lg-devs/android_kernel_lge_msm8992" path="kernel/lge/msm8992" remote="github" revision="cm-12.1" />
<project name="CyanogenMod/android_hardware_qcom_audio" path="hardware/qcom/audio-caf/msm8992" remote="github" revision="cm-12.1-caf-8994" />
<project name="CyanogenMod/android_hardware_qcom_display" path="hardware/qcom/display-caf/msm8992" remote="github" revision="cm-12.1-caf-8994" />
<project name="CyanogenMod/android_hardware_qcom_media" path="hardware/qcom/media-caf/msm8992" remote="github" revision="cm-12.1-caf-8994" />
<project name="lg-devs/proprietary_vendor_lge" path="vendor/lge" remote="github" revision="cm-12.1-caf" />
</manifest>
[/QUOTE]

@janjan: can you upload some screenshots? It sounds too good to be true

[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.

[GUIDE] [mini] CM13 for Z4/Z3+ build

In a nutshell you do the steps
- unlock your bootloader
- backup your DRM (if available and possible on the Z4/Z3+)
You follow steps 4 to 4.6 of
https://wiki.cyanogenmod.org/w/Build_for_angler#Build_CyanogenMod_and_CyanogenMod_Recovery
(that is the entry for the Nexus 6P)
you go into ~/android/system/
or the folder you named it
Code:
cd .repo
mkdir local_manifests
copy over the lines from
https://github.com/SonyAosp/device_sony_ivy/blob/e97659de9c044e56fabe25cf1dfdac44b27131de/README.md
into e.g.
ivy.xml
Code:
<?xml version="1.0" encoding="UTF-8"?>
<!--Please do not manually edit this file-->
<manifest>
<project name="SonyAosp/device-sony-ivy" path="device/sony/ivy" remote="github" revision="cm-13.0" />
<project name="SonyAosp/device-sony-kitakami" path="device/sony/kitakami" remote="github" revision="cm-13.0" />
<project name="SonyAosp/device-sony-common" path="device/sony/common" remote="github" revision="cm-13.0" />
<project name="SonyAosp/camera" path="hardware/sony/camera" remote="github" revision="cm-13.0" />
<project name="SonyAosp/kernel" path="kernel/sony/msm" remote="github" revision="mm-6.0" />
<project name="sonyxperiadev/thermanager" path="hardware/sony/thermanager" remote="github" revision="master" />
<project name="sonyxperiadev/timekeep" path="hardware/sony/timekeep" remote="github" revision="master" />
<project name="sonyxperiadev/macaddrsetup" path="hardware/sony/macaddrsetup" remote="github" revision="master" />
<project name="SonyAosp/platform_hardware_sony_init" path="hardware/sony/init" remote="github" revision="mm-6.0" />
<project name="SonyAosp/vendor_qcom_opensource_dataservices" path="hardware/sony/opensource/dataservices" remote="github" revision="mm-6.0" />
<project name="SonyAosp/platform_vendor_qcom" path="vendor/qcom" remote="github" revision="mm-6.0" />
<project name="SonyAosp/platform_vendor_sony" path="vendor/sony" remote="github" revision="mm-6.0" />
<project name="SonyAosp/platform_vendor_qcom_proprietary" path="vendor/qcom/proprietary" remote="github" revision="mm-6.0" />
</manifest>
then do a
Code:
repo sync
again
and you should be good to go with something like
Code:
source build/envsetup.sh
lunch cm_ivy-userdebug
mka clobber && mka bacon
Troubleshooting:
Running Python >=2.7 ?
install python 2.7
then
Code:
export EPYTHON=python2.7
Running a Linux distribution with "Umlauts" and other European gibberish locale (de, fr, etc.)
Code:
export LC_ALL=C
Running a bleeding edge Linux distribution which only has ncurses >=6.0 ?
extract and/or build ncurses 5.9 (64bit) locally and copy it e.g. to ~/aosp/ncurses/lib64/
then
Code:
export LD_LIBRARY_PATH=~/aosp/ncurses/lib64/
Have a nice day

I am waiting for my device from repair, motherboard is going to be changed. Not sure I will be able to unlock bootloader or not but surely would love to try this and run an aosp rom on my device.
Thanks for this guide.

I followed your guide and building the ROM worked like a charm (compiling took like 2:15h in an Ubuntu 15.10 VM). Installing also worked without any problems so far, thank you soooooo much for this!
I tried following the guide on the Sony page, which always made problems for me (either compiling didn't work or the ROM wouldn't boot).

Thomas231 said:
I followed your guide and building the ROM worked like a charm (compiling took like 2:15h in an Ubuntu 15.10 VM). Installing also worked without any problems so far, thank you soooooo much for this!
I tried following the guide on the Sony page, which always made problems for me (either compiling didn't work or the ROM wouldn't boot).
Click to expand...
Click to collapse
Glad it worked flawless

What is the ROM status ? Working and not working list plz ?
Thanks

Right now the only issue I know of is the camera issue which is present on all AOSP-based ROMs using the open source driver (and even the stock ROM, at least for me).

I'm trying to build cm-13 using this manifest doesn't work. mm-6.0 is not present on some of the sony repos. Anyone face this issue ? repo sync fails.

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: