yashsingh1/xdaforums huggingface dataset:
[G3 Android Development] secret.animal:
I'm trying to do this for my LS980 Sprint LG G2.

But I'm getting this in the build

build/core/base_rules.mk:550: warning: ignoring old commands for target `/home/chris/android/system/out/target/product/ls980/system/lib/drm/libfwdlockengine.so'

build/core/Makefile:46: warning: overriding commands for target `/home/chris/android/system/out/target/product/ls980/system/lib/libcnefeatureconfig.so'

build/core/base_rules.mk:550: warning: ignoring old commands for target `/home/chris/android/system/out/target/product/ls980/system/lib/libcnefeatureconfig.so'

build/core/Makefile:46: warning: overriding commands for target `/home/chris/android/system/out/target/product/ls980/system/vendor/lib/mediadrm/libdrmclearkeyplugin.so'

build/core/base_rules.mk:550: warning: ignoring old commands for target `/home/chris/android/system/out/target/product/ls980/system/vendor/lib/mediadrm/libdrmclearkeyplugin.so'

No private recovery resources for TARGET_DEVICE ls980

build/core/tasks/kernel.mk:63: ***************************************************************

build/core/tasks/kernel.mk:64: * Using prebuilt kernel binary instead of source *

build/core/tasks/kernel.mk:65: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *

build/core/tasks/kernel.mk:66: * Please configure your device to download the kernel *

build/core/tasks/kernel.mk:67: * source repository to kernel/lge/msm8974

build/core/tasks/kernel.mk:68: * See http://wiki.cyanogenmod.org/w/Doc:_integrated_kernel_building

build/core/tasks/kernel.mk:69: * for more information *

build/core/tasks/kernel.mk:70: ***************************************************************

make: *** No rule to make target `/home/chris/android/system/out/target/product/ls980/kernel', needed by `/home/chris/android/system/out/target/product/ls980/boot.img'. Stop.

Not sure what I am doing wrong.
[G3 Android Development] tobitege:
http://wiki.cyanogenmod.org/w/Build_for_ls980
[G3 Android Development] secret.animal:
I've followed that before. But had an issue somewhere and figured this would fix any issue I had before. I'll try again and thank you so much.

I'm still learning this part of the process. Long time user, first time port. No way a developer, b?
[G3 Android Development] purian23:
Two Zip builds?

Hello,

Is it normal that the system generates two builds of the exact same size in different names, each time I build?

Example: In my target/product/vs985 I get cm_vs985-ota-7d06ff15d6.zip and cm-12-20150107-UNOFFICIAL-vs985.zip in that folder. Again both the same size. Maybe this is why it's taking 2 1/2 - 3hrs on each make clean to build? I tried enabling cCache and it seemed to make no difference in speed, but it seems redundant if it's making two builds.

Thank you!
[G3 Android Development] tobitege:
That's normal at the end (ccache is only for compilation), one is used as reference for the other, something about signing, I think.
[G3 Android Development] Neurom707:
Edit fixed
[G3 Android Development] zichichi:
Do you know how to patch the kernel for multirooms?
[G3 Android Development] manups4e:
no i don't
[G3 Android Development] Neurom707:
Cm built fine 3rd time lucky :p :p

Now for beanstalk
[G3 Android Development] Neurom707:
Never mind
[G3 Android Development] Enddo:
Could anyone assist me in a step by step way about how to go about building CM12 for my device with a custom kernel? So, instead of the build process compiling the stock CM12 kernel, it would compile Rin's custom kernel(https://github.com/tectas/android_kernel_lge_msm8974ac/tree/rin-lollipop)

Do I only I need to change the kernel line in the local manifest to Rin's above, and then sync+build or is there more to it than that?

I apologize if it is too much to ask. I simply do not know enough about building ROMs. I have recently setup a build environment and I've compiled a couple of nightlies that work properly. I'm just looking to learn how I can incorporate a custom kernel directly in the build/compile process
[G3 Android Development] hua3354:
mark ,may be used someday
[G3 Android Development] manups4e:
you can't build rin kernel on cm12... you can build it but rom will never boot.. rin kernel is for STOCK LG roms it means all the roms made by lg and not aosp like cyanogenmod
[G3 Android Development] Enddo:
Rin released an AOSP version a week or two ago :p

http://xdaforums.com/att-lg-g3/development/kernel-rin-kernel-1-6-t3002487/
[G3 Android Development] manups4e:
that's only for d850 :) if you have other variants (like d855) it won't work... anyway just replace kernel sources into kernel/lge/g3 and let the build begin :D
[G3 Android Development] tschmid:
For D855:

http://xdaforums.com/showthread.php?t=3001540

Gesendet von meinem LG-D855 mit Tapatalk
[G3 Android Development] Enddo:
I have the D850 though :)

What do you mean by replace the kernel sources. Where? In the local_manifest file? Replace it with what exactly?

I'm sorry if I'm asking too many questions. I'm definitely a noob at compiling ROMs. I've only done a few builds and it was only because of incredible step by step guides like the one in the original post

I am eager to learn though(which is why I'm asking questions)
[G3 Android Development] manups4e:
delete kernel/lge/g3 folder and replace kernel source address into local_manifest, when you'll sync it will doenload rin kernel sources.. then just run brunch d855 and you'll be ok :D
[G3 Android Development] Enddo:
Has anyone been able to repo sync CM12 tonight? I've been trying for the past 4 hours or so and I keep getting fetch errors. I've even tried the 'repo sync -f' command and it still gives me a generic 'error: Exited sync due to fetch errors' error and quits

I'm noticing a lot of "Failed to connect to android.googlesource.com port 443: No route to host" errors while it's trying to sync

edit - the error I see before it immediately stops the sync is

"error: in `sync -f`: revision refs/tags/android-5.0.2_r1 in platform/developers/build not found"

double edit - I think it was due to how I was connected to the internet. Connecting directly to the router helped to resolve this issue
[G3 Android Development] Bcreed26:
I am getting the same error however I am unable to figure out the issue. Could you please explain what you did to fix this. Thanks...

I am using Ubuntu...
[G3 Android Development] purian23:
I was using the wrong manifests in my local_manifests folder XML inside of it.

Try the following in your local_manifest XML file and then repo sync again afterwards. 100% credit goes to [MENTION=2385005]invisiblek[/MENTION] for helping direct me to this source.

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/lge/g3-common" name="CyanogenMod/android_device_lge_g3-common" remote="github" revision="cm-12.0" />
<project path="device/lge/vs985" name="CyanogenMod/android_device_lge_vs985" remote="github" revision="cm-12.0" />
<project path="kernel/lge/g3" name="CyanogenMod/android_kernel_lge_g3" remote="github" revision="cm-12.0" />
<project path="vendor/lge" name="TheMuppets/proprietary_vendor_lge" remote="github" revision="cm-12.0" />
<project path="device/qcom_common" name="CyanogenMod/android_device_qcom_common" remote="github" revision="cm-12.0" />
</manifest>
[G3 Android Development] Bcreed26:
Damn... I knew it was manifest related and I tried everything. TheMuppets/proprietary is what was getting me. Thanks a ton! Making the changes now.
[G3 Android Development] gdonanthony:
hi can someone here make a guide building with Linaro or SM prebuilts ? i google many guides but im confused... i hope someone will help me step by step
[G3 Android Development] MuS3SbElLaMy:
So once initial repo sync is done if I want multiple devices can I just duplicate the folder and its contents for each device as opposed to downloading separately for each device?

I'm assuming so, just wanting to check for any reasons I may be unaware of
[G3 Android Development] tobitege:
Do not copy foders just like that because they contain usually github/version control information folders!
[G3 Android Development] MuS3SbElLaMy:
ok so for each seperate device i need to download all again?

or is there a way of doing multiple devices using one repo sync? (i'm assuming not)

maybe that is just running before i can walk?
[G3 Android Development] tobitege:
Within your device tree you can have many entries for different devices where e.g. an individual phone/tablet etc. is usually requiring a repository for the device itself as a base and most likey a separate kernel repository (often even more per phone).

Repo sync will have to download those for you and you have to keep an eye on the target paths in order to not have any duplicates.

For more info building roms you could also read up on this illustrated and really detailed guide:

http://xdaforums.com/chef-central/android/guide-android-rom-development-t2814763/

Also, sources can be huge, like 30 to 50GB(!) but you eventually have to let repo download those, either in one swoop or over multiple days (basically aborting the sync and let if figure out what is missing the next run etc.)
[G3 Android Development] MuS3SbElLaMy:
Awesome thanks I had some issues on my desktop bit its mostly likely to be because of the Ubuntu version its currently running

This is something I've been interested in for a long time Just a little concerned about not having a testing device

My laptop should be sufficient to do this that guide mixed with this one should give me all I need sorry for the dumb question but where do we get the repo URL from? Is it the main branch URL on github?

Also interested in cherry picking but that's for the future for now building cm for my device is a step in the right direction

Thanks for your help and advice
[G3 Android Development] tobitege:
Example for repo init is in post 1 as well as a local_manifest.xml file so you should be able to identify what you need. For repositories open CyanogenMod on github, tab Repositories.
[G3 Android Development] MuS3SbElLaMy:
Sorry I'm back again

So as far as local_manifest.xml files go is this the correct/ current one ? During my first build attempt I got and error at kernel stage

Is there anyway to put the terminal output into a text file for an easier way to check errors (a bit like when using adb)?

xml version="1.0" encoding="UTF-8"?> <manifest> <project path="device/lge/g3-common" name="sooti/android_device_lge_g3-common" remote="github" revision="cm-12.0" /> <project path="device/lge/d855" name="sooti/android_device_lge_d855" remote="github" revision="cm-12.0" /> <project path="kernel/lge/g3" name="sooti/android_kernel_lge_g3" remote="github" revision="cm-12.0" /> <project path="vendor/lge" name="sooti/proprietary_vendor_lge" remote="github" revision="cm-12.0" /> <project path="device/qcom_common" name="cyanogenmod/android_device_qcom_common" remote="github" revision="cm-12.0" /> </manifest>
[G3 Android Development] tobitege:
Your "Code" excerpt is empty? :)

I guess somehow one could pipe the output to file like "brunch d855 > build.log" or something.
[G3 Android Development] MuS3SbElLaMy:
still fails at kernel stage for me

this is the message i get after each build attempt

target thumb C++: components_webdata_common_gyp <= external/chromium_org/components/webdata/common/web_database_service.cc
OBJCOPY arch/arm/boot/Image
Kernel: arch/arm/boot/Image is ready
AS arch/arm/boot/compressed/head.o
L/bin/sh: 1: lz4c: not foundZ4 arch/arm/boot/compressed/piggy.lz4
/bin/sh: 1: lz4c: not found
/home/darrell/android/system/kernel/lge/g3/arch/arm/boot/compressed/Makefile:194: recipe for target 'arch/arm/boot/compressed/piggy.lz4' failed
make[4]: *** [arch/arm/boot/compressed/piggy.lz4] Error 1
/home/darrell/android/system/kernel/lge/g3/arch/arm/boot/Makefile:61: recipe for target 'arch/arm/boot/compressed/vmlinux' failed
make[3]: *** [arch/arm/boot/compressed/vmlinux] Error 2
/home/darrell/android/system/kernel/lge/g3/arch/arm/Makefile:300: recipe for target 'zImage' failed
make[2]: *** [zImage] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/home/darrell/android/system/kernel/lge/g3'
build/core/tasks/kernel.mk:209: recipe for target 'TARGET_KERNEL_BINARIES' failed
make: *** [TARGET_KERNEL_BINARIES] Error 2
make: *** Waiting for unfinished jobs....

sorry about the code tags being empty fixed that now

as far as i can make out it is a missing package required for compressing the linux kernel when i finish work i'll look into it

did this

sudo apt-get install liblz4-dev liblz4-tool

That appears to have fixed it now rom build completes /boots and seems pretty much stable :good:
[G3 Android Development] rhystagram:
hm, just synced source after sometime not doing it.

it will build but now gets stuck at the LG logo, wont continue onto bootanimation?

did something change?

[MENTION=4120529]MuS3SbElLaMy[/MENTION]

"Fixing 'lz4c' not found:

Due to new lossless kernel compression (LZ4), the lz4c binary is needed until properly implemented in the rom tree. This can be installed by following the steps below:

wget http://lz4.googlecode.com/files/lz4-r112.tar.gz

tar -xf lz4-r112.tar.gz

cd lz4-r112

make

sudo make install" found when googled
[G3 Android Development] MuS3SbElLaMy:
well it's built and boots everything seems fine :good:

thanks for the help and the guide :)

Now for more studying ................................. any suggestions?
[G3 Android Development] woodykr:
but you can not change the layout of the physical buttons?
[G3 Android Development] MuS3SbElLaMy:
where would i find local_manifest.xml files ? for particular roms that have already been ported ?

(i.e aospa-legacy)

i have the sources which i got using

repo init --reference=~/android/system -u https://github.com/AOSPA-legacy/manifest -b lollipop

and the other parts i need are here ( amongst others)

https://github.com/AOSPA-legacy?query=lg

i read the manifests information in xda university and i was none the wiser to be honest is there a guide to making a local_manifest or something sorry if this is off topic just wasn't sure where to ask if here is wrong then if someone could point me in the direction of the correct forum or documentation that'd be great

think i sorted it ....... strangely i deleted the local_manifest and typed

./rom-build.sh d855

it seemed to do everything automatically anyway apologies for OT
[G3 Android Development] 500L:
[MENTION=2849215]manups4e[/MENTION] thanks for this guide.

I'm planning to build fm radio module into cm kernel (like in 777 kernel).

Any ideas?

Regards.
[G3 Android Development] manups4e:
if you don't know how to do it.. ask someone who already did it ^^ ask the 777 kernel creator
[G3 Android Development] ivankolev:
Hi,

Could you help me with instructions how to remove packages prior build process?

For instance /packages/apps/Calculator

How to remove and not build it?
[G3 Android Development] jazzista88:
Hi all

I wanna start to build my own cyanogenmod release, but the problem is that i don't have lg g3 but Samsung Galaxy note 2 N7100.

How should i change the instructions in order to reach the same result on my phone?

Thanks to all.
[G3 Android Development] tobitege:
Most importantly get the correct device tree together for your device. Search on e.g. github for repositories and add these to your local_manifests.xml file if appropriate.

If your device did get cm11 nightlies, it would make it easier for you, because cm would already have those repos on their github account.

---------- Post added at 03:00 ---------- Previous post was at 02:54 ----------

Follow also this thread which goes into tricky details frequently: http://xdaforums.com/showthread.php?t=2814763
[G3 Android Development] LOGMD:
build kernel only

Is there a way to download just the kernel source part for the g3, and then compile the official cm12 kernel. I use multi Rom a lot and the latest kernels are about 2-3 weeks off and don't work with the latest nightlies.

So will try making kexec hardboot patched stock cm12 kernel
[G3 Android Development] Skin1980:
You don't need a kexec hardboot patch for the 2nd kernel, only the main must have it.

BTW if you want build the kernel just get the source from here

https://github.com/CyanogenMod/android_kernel_lge_g3
[G3 Android Development] LOGMD:
Thanks skin, then what do the kernels need to be multirom compatible as a second Rom? I've always seen boot loops and kernel panics from the stock cm kernels?

(Kernels like furnace seem to either inject, modify or re create the boot image)
[G3 Android Development] Pannam:
Do we have a CM11 device tree ? if so will the device tree of D855 work for other variants ?
[G3 Android Development] tobitege:
I think, that this is just a misunderstanding: there's no special requirement for MultiRom secondaries' kernels and recent CM kernel commits (causing problems with cm-based kernels in roms) just required a MultiRom update. Depending on the device, there may of course be other constraints, like different memory mgmt. or compression method etc.

---------- Post added at 13:32 ---------- Previous post was at 13:29 ----------

There are of course old JB and KK branches within the repositories. But that is what you use the '-b' parameter in 'repo init' for and thus get a corresponding manifest.xml in your .repo folder.
[G3 Android Development] LOGMD:
I see, I'm going to attempt building a kernel in the next few days, any specific way to ensure it works on multirom? maybe ill check over at the other kernel threads which already support it. ill have a look into it :)
[G3 Android Development] Pannam:
will this guide work for f460k lg g3 variant ? anything i will have to edit in local manifest as its for d855. i just want to make a custom recovery for kitkat. this guide is for cm 12 will it work?
[G3 Android Development] tobitege:
Custom recovery is similar I guess, but I haven't tried that.

---------- Post added at 07:39 ---------- Previous post was at 07:37 ----------

If you plan to use it on primary rom, your kernel must at least have the kexec_hardboot patch. But on G3 it can get tricky afaik due to kernel size and compression, watch out for that. :)
[G3 Android Development] Joeisgood99:
Hey [MENTION=4927685]Neurom707[/MENTION] when you got the error from base rule 154 of " module-script already defined in device tree" type error did the advice you were given to delete it from (example) /build/extras/ work for you or did you run in to problems later on. Im getting the same error where various parts of code are duplicated in my source code and just wondering which one to delete, if thats the fix. The code in my device folder or build/core/whatever. this is my error.

build/core/copy_headers.mk:15: warning: ignoring old recipe for target 'out/target/product/m7/obj/include/qcom/display/c2d2.h'
build/core/base_rules.mk:154: *** hardware/qcom/display/msm8960/liblight: MODULE.TARGET.SHARED_LIBRARIES.lights.msm8960 already defined by device/htc/msm8960-common/liblights. Stop.

Please let me know if deleting already defined code from "/main/source-code" worked as apposed to from "/my-device/folder"

Thanks!
[G3 Android Development] quevon24:
Help, i cant run correctly mkvendor.sh to generate the device tree

I run this:

./build/tools/device/mkvendor.sh dell yellowtail ~/boot.img

And i got this:

Arguments: dell yellowtail /home/quevon24/boot.img
Output will be in /home/quevon24/android/system/cm12/device/dell/yellowtail
gzip: ../boot.img-ramdisk.gz: No such file or directory
cpio: premature end of archive
cat: /tmp/quevon24/bootimg/boot.img-base: No such file or directory
cat: /tmp/quevon24/bootimg/boot.img-cmdline: No such file or directory
cat: /tmp/quevon24/bootimg/boot.img-pagesize: No such file or directory
cp: cannot stat
«/tmp/quevon24/bootimg/boot.img-zImage»: No such file or directory
Creating initial git repository.
~/android/system/cm12/device/dell/yellowtail ~/android/system/cm12
Reinitialized existing Git repository in /home/quevon24/android/system/cm12/device/dell/yellowtail/.git/
On master branch
nothing to commit, working directory clean
~/android/system/cm12
Done!
[G3 Android Development] manups4e:
this is the G3 forum.. not the Dell yellowtail one ^^ you should ask into your device's section
[G3 Android Development] reepje123:
Hey guys, I'm trying to compile CM13 just for testing. (No, I'm not a dev)

I hope it's OK to post here, because it's not CM12.

I'm getting this error everytime:

device/lge/g3-common/sepolicy/init_shell.te:2:ERROR 'unknown type init_shell' at token ';' on line 26607:
allow init_shell baseband_prop:property_service set;
#line 1 "device/lge/g3-common/sepolicy/init_shell.te"
checkpolicy: error(s) encountered while parsing configuration
make: *** [/home/reepje123/android/system/out/target/product/d855/obj/ETC/sepolicy_intermediates/sepolicy] Fehler 1
make: *** Auf noch nicht beendete Prozesse wird gewartet …

I already checked the init_shell.te file, but it is exactly the same as on github.

init_shell.te:

allow init_shell baseband_prop:property_service set;
allow init_shell mmc_block_device:blk_file r_file_perms;

Does anybody know how to fix it, or should I comment it out with an #?

Edit:

After some heavy out-commenting (if that is a word) and manually inserting needed files, I finally got a (at least in theory) flashable zip file :)

The filesize is around 300mb, which seems a little too big to me.

My bad, ubuntu showed 300MB, but it is 286MB.
[G3 Android Development] gendon:
hello everyone...

its really interesting reading this thread from the first page...

and since there are so many people succeded to built CM for their devices by their own, that makes me so much excited.

since i was looking this guide from google, but actually looking for D838 (G Pro 2)

and since there arent any developers try to developing CM for D838, i was really interested to try to make CM for D838.

My question is, whats the differences for the sources i will need to make CM for D838 ? and how do i get it?

i'm totally blank about coding n programing.

Thx.
[G3 Android Development] nagi_007pk:
Try a different development forum. This is exclusively for G3 and your device isn't officially supported by cm.

Here's the link to the G Pro 2 forum

http://xdaforums.com/lg-g-pro-2/development
[G3 Android Development] michaelvu1811:
can i do this on htc desire 510
[G3 Android Development] manups4e:
look into your device section
[G3 Android Development] michaelvu1811:
mine isnt in the device section. is there anyway for me to make it for my device
[G3 Android Development] manups4e:
it could be.. i will look for your device in the afternoon ok?
[G3 Android Development] michaelvu1811:
ok
[G3 Android Development] applesaw:
hey there good sir can you please post a me a link where i can get a step by step guide to build a Marshmallow rom for my LG G3 D855.
[G3 Android Development] manups4e:
look at lineageos wiki it's all explained there just use lineageos 13
[G3 Android Development] manups4e:
nono that recovery folder is not important :) the only thing is that first boot remains at boot LG logo for some minutes is normal :) how much did you wait?
[G3 Android Development] BoRoU:
Yessssssssssssss I have finally been able to finish !!!!!

I'll try to see if it works. : D

thank you very much manups4e
[G3 Android Development] TheMorpheus:
5 minutes give or take... I've waited much longer than I had updating your build.

Also the size are different
[G3 Android Development] manups4e:
this is very strange ^^ i'm using the same sources as you are ^^ my boot.img is 7.1 MB which size is your?
[G3 Android Development] TheMorpheus:
boot.img is 7.1 MB and the System folder is 368.7 MB
[G3 Android Development] manups4e:
got it :) did you sync the vendor lge folder into vendor folder?? check the OP in the manifest section and update your manifest with the sooti/proprietary_vendor_lge link :) it is not booting because it's missing its proprietary files
[G3 Android Development] TheMorpheus:
All right, I'll try now. Thanks!!
[G3 Android Development] manups4e:
your welcome :)
[G3 Android Development] BoRoU:
First test same results as the companion TheMorpheus

I keep trying.
[G3 Android Development] manups4e:
the same issue i think :) rebuild with the new vendor/lge folder :) it will be fine :D