yashsingh1/xdaforums huggingface dataset:
[Android] aoleary:
Try this technique to analyse the error:

Its taken from the Android builders telegram channel: https://t.me/AndroidBuildingHelp

From Nathan Chancellor
SOLVING MISSING TARGET AND NO RULE TO MAKE IT ERRORS

1. Figure out what the module is. You do this by taking what's between the "/" and "_intermediates".

2. Find out what module requires it, as this means that there is a shared library or dependency that you are missing. You can do this via mgrep after using build/envsetup.sh. Example:

mgrep "<module_name_from_step_1>"

3. Figure out what repo it is by using source from another ROM that you know works. Same thing as step 2 BUT you need to find the actual local module.

mgrep "LOCAL_MODULE := <module_name_from_step_1>"

After that, add the repo to your dependencies or local manifest and try again.
[Android] alphamale:
What was your solution
[Android] KeTuRr74:
Deleting sepolicy folder in device tree let me skip this error but i think after that if the build finish successfully you will face problems with selinux ☹
[Android] dungphp:
My problems when compiling Oreo 8.1:

packages/apps/FMRadio/Android.mk: error: FMRadio (APPS android-arm64) missing libfmjni (SHARED_LIBRARIES android-arm64)

You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.

Who can help me ? Thankssssssssss
[Android] NepoRood:
If it were me, I'd remove the offending package, especially if it's not "essential" to the build :good:

rm -rf packages/apps/FMRadio
[Android] quake73:
I'd do that, too :)

Anyway, libfmjni is in vendor/qcom/opensource/fm..
[Android] dungphp:
Thank you !

Pixel 8.1 can build but LOS 15.1 or Cardinal no

I removed complate its

And here again:
[Android] LexX-V:
Help me please to solve the first problem in development while compiling. Then maybe I'll understand how to make it in future. I'm newbee.

./system/sepolicy/Android.mk:111: warning: BOARD_SEPOLICY_VERS not specified, assuming current platform version

Trying to port official omni nougat to oreo build.
[Android] NepoRood:
That's not an error...
[Android] LexX-V:
Hmm.:eek: I have got 13 warnings and ninja ends without needed zip-file. The next warning is this:

platform_testing/build/tasks/tests/instrumentation_metric_test_list.mk: warning: continuous_instrumentation_metric_tests: Unknown installed file for module perf-setup.sh

Where can I find the errors? There are warnings only.
[Android] NepoRood:
Look for the word FAILED or error (red on my machine) or just put the whole log on pastebin or something
[Android] LexX-V:
As I see there is only one error: Pastebin.

ninja: error: 'vendor/omni/prebuilt/bootanimation/res/1440x814.zip', needed by '/home/lexx-v/android/omni/out/target/product/manta/system/media/bootanimation.zip', missing and no known rule to make it

How can I resolve this?
[Android] NepoRood:
You need that zip file: vendor/omni/prebuilt/bootanimation/res/1440x814.zip

Follow the path, you may need to pull it in from older source...
[Android] LexX-V:
Yes, I found plenty of zip-files with different resolutions, one of which was 1440p.zip. Just renamed it and ninja could start building. Now I've got new error (fatal) and it's in red color now:

frameworks/native/include/binder/Parcel.h:23:10: fatal error: 'android-base/unique_fd.h' file not found

I'll try to google for it.
[Android] tdukazudon:
LOS15.0 and 15.0

I'm trying to build Lineage 15.0 and 15.1 for Google nexus 5.

Build completed and working well,however sound not working.I tried to solve to read logcat ,but I can't found where to fix.Please tell me solution to fix.

Here is logcat.

https://pastebin.com/XRZmX6PN
[Android] George_Jetson:
Stock Lg Source --Build Fails

Hi I have been trying to build the firmware for Lg K3

i have read every tut, been over and over the source and still it doesn't finish building...

Any Suggestions?
[Android] alphamale:
I have a couple of stupid questions. Im new to ROM building. Trying to build 8.1 ROM. The kernel source is missing a file. Can I take the file from 8.0 kernel source? If so how? Could I create a text file and copy contents into it, or is there more to it than that? Would another possibility be just to use kernel source 8.0 to build 8.1 ROM?
[Android] karthik km:
can anyone help me with this ?

ninja: error: '/home/karthik/pure/out/target/product/wt88047/dt.img', needed by '/home/karthik/pure/out/target/product/wt88047/boot.img', missing and no known rule to make it
build/core/ninja.mk:157: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
[Android] alphamale:
Can some one help me with this error
[Android] albertoduqe:
Hi again!

I have been trying some more approaches to my build but no luck with the camera. The rom has some other issues but this one is the main one to fix in orther to make it usable.

So here is a logcat: https://mega.nz/#!RP52FabA!IvVLaN0pWh13h_3SW-4k3sZ43H25A6nxZ-xkiW_YJJ0

I see several camera errors (starting in line 9986 aprox) but do not really know what they are, which ones are the crucial ones causing the camera to shut down after like a second of image, and of course how to fix them.

Any help will be greatly appreciated!!

Thanks.
[Android] aoleary:
Add support for dt.img to ROM

Hi.

I would like to add support for building the dt.img to a ROM that doesnt have it, and I see the following two commits at the top of the list in the CypherOS gihub (CypherOS supports the G3).

https://github.com/search?q=org:CypherOS+dt_image.mk&type=Commits

9f32980d7ca07eea0f807edf3caeabccb4edb5ff

7c3972db9c92a7ea5b90f20dfb4f78c445983f79

dt.img is required by the LG G3 devices to be able to boot up properly.

My question is how do I import any other commits that they might also need?

Coz I can see many parent commits, so I was wondering if there was a way to just import all dependent commits plus those commits I posted above..

TIA for any help you can provide..
[Android] Qiangong2:
Are there any guides on bringing an Android kernel up? Like from 3.18.19 to 3.18.30?
[Android] mosimchah:
Yeah, and the latest is 3.18.88 by the way https://xdaforums.com/android/software-hacking/reference-how-to-upstream-android-kernel-t3626913/
[Android] Qiangong2:
Another question, if I find a kernel source for my processor (mt6580) that is higher up, how would I go about using that source with my device? I have the kernel source for my device already.
[Android] DiamondJohn:
The specific kernel for your device is normally specified in your local_manifest. Specify a different branch/source in your local_manifest. I was lucky as it was a direct replacement.

eg, i changed the following line (for a cm-13.0 build/default revision) from:

<project name="LineageOS/android_kernel_motorola_msm8960-common" path="kernel/motorola/msm8960-common" remote="github" />

to (scroll to the end of the line):

<project name="LineageOS/android_kernel_motorola_msm8960-common" path="kernel/motorola/msm8960-common" remote="github" [COLOR="Blue"]revision="cm-14.1"[/COLOR] />
[Android] Qiangong2:
Sorry, I didn't make it clear. I would like to port a kernel source to my device.
[Android] dungphp:
Please help me in Lineage 15.1:

the hardware/qcom/audio-caf/msm8952 worked in Experience

Thanks
[Android] ahmed gamal 1m:
Can I use Samsung stock kernel source to compile AOSP 7.1.2 rom
[Android] albertoduqe:
I know there's a lot of activity in this thread but if anyone can have a look at my logcat and give me any hint on what can be the cause of crashes and fatals, it would be really helpful :)

Thanks guys!
[Android] TimSchumi:
If you put it somewhere else than on Mega (as many people don't like those file-sharing services).

I for example can't open files from there on my phone.

Try for example Hastebin, Pastebin, etc. as they are much more suited for text files.
[Android] tribual:
Hi!

Maybe someone here could help me or does have any idea for this problem:

We develop AOKP Nougat for Elephone P9000 (MTK Device)

We had problems with video recording. Now found some patches from great user [MENTION=7739639]Zormax[/MENTION].

Applied them and it fixed video recording!

THX for that! Will give proper credits for you [MENTION=7739639]Zormax[/MENTION]!!

Only problem when use the patches:

Audio is buggy:

Music (mp3) - not working

Ringtone - not working

Notification Tone - not working

Lock/Unlock sound - WORKING (funny, isn't it?)

Tap on screen notification - WORKING (funny, isn't it?)

misterious...

Hopefully you could help or do have any idea?

Here my sources:

Device:

https://github.com/tribual/android_device_elephone_p9000/tree/cm-14.1-MMBASE

Vendor:

https://github.com/tribual/android_vendor_elephone_p9000/tree/aokp7-av-test

Kernel:

https://github.com/tribual/android_kernel_elephone_p9000/tree/open-sourcerce

THX anyway!

Greetz

tribual
[Android] albertoduqe:
Yeah you are totally right, thanks!

I will provide it through some other platform asap.
[Android] albertoduqe:
Here it is finally! :)

https://pastebin.com/cXekvDYQ

I had to cut a whole lot of it because I do not have a pro account yet. I believe I managed to leave all of the fatals except for the first one, which was related to bootanimation and it is repeated at the end.

Well then, I hope some of you guys can have a look and give me some idea, anything will help.

Thanks!
[Android] TimSchumi:
There was a SIGSEGV, which seems to come from libjpeg.so, is that a vendor file?

Also, SELinux might influence things. Try setting it into permissive mode and check it again.

Apply this patch to the root of your source to hack it into a permanent permissive mode: https://github.com/SiniTurk/android_patch/blob/cm-13.0/permissive_selinux.diff

PS: You can append "*:W" to the logcat command to make it only print warnings or higher, which can help finding a crash fast and you don't have to cut down the log yourself. The same works with F (Fatals), E (Errors), I (Information), D (Debug) and V (Verbose)
[Android] albertoduqe:
Thanks!

That was very helpful.

BitObsession told me to look into the Selinux status also so that I will do asap.
[Android] PraneethMv:
Can anyone help me with this error:

https://drive.google.com/open?id=1FxZuuXJ3IsQd1aSd_a9sQc_psMnq3thC

I'm trying to build PA for A7010a48.
[Android] Uvneshkumar:
Hi. Thanks for this good tutorial.

I synced Lineage 14.1 rom, made some local changes in the code and build the ROM and everything went fine. But when I tried to sync the ROM again, it showed me some errors regarding file conflicts. I was already told that I need to push them to the github. But I don't know exactly how to do it. Can you please help me by proving list of commands to upload my source to github, sync changes from lineage os and again the code in my local machine should have all my changes. Please help me what to do.
[Android] Qiangong2:
Is there an Android 6.0 ROM that runs fast on 512mb RAM device?
[Android] turnert:
I have a nokia 521 running Android 7.1 with 512mb of ram. I wouldnt say it runs slow but it definitely doesn't run fast and can't handle gapps or really any games.
[Android] Qiangong2:
I already know that it runs pretty slow, android is no longer designed to run on 512mb RAM devices. I want to know if there is a marshmallow ROM that you can build from source, that is optimized for low end devices.
[Android] DodoGTA:
Android 8.1 Go edition FTW!
[Android] tripLr:
Yes try Android 8.1 Go edition . It's going to be for small devices
[Android] Qiangong2:
You aren't understanding. the ROM needs to run on Android 6.0
[Android] hdorius:
any help on this ?

hardware/qcom/keymaster/keymaster_qcom.cpp:227:19: error: no member named 'heap_id_mask' in 'ion_allocation_data'; did you mean 'heap_mask'?

ion_alloc_data.ION_HEAP_MASK = ION_HEAP(ION_QSECOM_HEAP_ID);
[Android] tathanhlam66:
Apply this patch https://review.lineageos.org/#/c/186045/
[Android] ahmed gamal 1m:
Can I use Samsung stock kitkat kernel to build AOSP 7.1.2

someone answers please
[Android] DodoGTA:
Yes, but you'll need to modify it (most likely heavily) by improving the way the kernel builds (improving the Makefiles etc.), making the kernel build and work with a newer toolchain, removing various Samsung kernel restrictions, some legacy Android drivers and adding things like uid_cputime, setns support for the mount namespace etc.
[Android] ahmed gamal 1m:
Are there any thread to modify kernel to make it compatible with the source :good:
[Android] MYEUHD:
Hi there,

I'm trying to build OmniRom 7.1 for the Samsung Galaxy S I9000 (the code name is galaxysmtd)

However, I'm getting a weird error as soon as I start the build:

MYEUHD@MYEUHD-X541UAK /media/MYEUHD/32085D0A085CCF0B/Roms/omni 7.1 $ . build/envsetup.sh
including device/samsung/galaxysmtd/vendorsetup.sh
including sdk/bash_completion/adb.bash

MYEUHD@MYEUHD-X541UAK /media/MYEUHD/32085D0A085CCF0B/Roms/omni 7.1 $ brunch galaxysmtd
cat: /media/MYEUHD/32085D0A085CCF0B/Roms/omni: Is a directory
cat: 7.1/build/envsetup.sh: No such file or directory
cat: /media/MYEUHD/32085D0A085CCF0B/Roms/omni: Is a directory
cat: 7.1/build/envsetup.sh: No such file or directory
make: build/core/config.mk: No such file or directory
make: *** No rule to make target 'build/core/config.mk'. Stop.
bash: build/tools/roomservice.py: No such file or directory
make: build/core/config.mk: No such file or directory
make: *** No rule to make target 'build/core/config.mk'. Stop.

** Don't have a product spec for: 'omni_galaxysmtd'
** Do you have the right repo manifest?

No such item in brunch menu. Try 'breakfast'

MYEUHD@MYEUHD-X541UAK /media/MYEUHD/32085D0A085CCF0B/Roms/omni 7.1 $ breakfast galaxysmtd
cat: /media/MYEUHD/32085D0A085CCF0B/Roms/omni: Is a directory
cat: 7.1/build/envsetup.sh: No such file or directory
cat: /media/MYEUHD/32085D0A085CCF0B/Roms/omni: Is a directory
cat: 7.1/build/envsetup.sh: No such file or directory
make: build/core/config.mk: No such file or directory
make: *** No rule to make target 'build/core/config.mk'. Stop.
bash: build/tools/roomservice.py: No such file or directory
make: build/core/config.mk: No such file or directory
make: *** No rule to make target 'build/core/config.mk'. Stop.

** Don't have a product spec for: 'omni_galaxysmtd'
** Do you have the right repo manifest?

I have followed all the instructions, including the post #9. Then I tried to follow the Official Omni documentation to Make the device trees compatible with Omni but the same error appeared!

Any help will be appreciated. Thanks in advance!
[Android] DodoGTA:
Remove the space from the folder where you synced the source
[Android] KeTuRr74:
Hi guys, facing this error building Nexus 8.0.

https://hastebin.com/uvaweboyot.xml

Thanks for your help
[Android] karthik km:
Anyone help me with this ?

I currently having AOSP branch android-7.1.2_r27 (work tree)

How to update. This source tree to latest AOSP branch android-7.1.2_r33

Any help appreciated
[Android] MYEUHD:
Thanks! That solved it! However, I'm getting this error at 34% of the build:

MYEUHD/32085D0A085CCF0B/Roms/omni-7.1/out/target/product/galaxysmtd/obj/EXECUTABLES/linker_intermediates/linker.P; rm -f /media/MYEUHD/32085D0A085CCF0B/Roms/omni-7.1/out/target/product/galaxysmtd/obj/EXECUTABLES/linker_intermediates/linker.d )"
bionic/linker/linker.cpp:3151:18: error: use of undeclared identifier 'si'
if ((si->flags & FLAG_EXE) == 0) {
^
bionic/linker/linker.cpp:3163:80: error: use of undeclared identifier 'si'
DL_ERR("%s R_ARM_COPY relocations only supported for ET_EXEC", si->name);
^
bionic/linker/linker.cpp:3170:73: error: use of undeclared identifier 'needed'
ElfW(Sym)* src = soinfo_do_lookup(NULL, sym_name, &lsi, needed);
^
bionic/linker/linker.cpp:3173:82: error: use of undeclared identifier 'si'
DL_ERR("%s R_ARM_COPY relocation source cannot be resolved", si->name);
^
bionic/linker/linker.cpp:3178:82: error: no member named 'name' in 'soinfo'
"library %s (built with -Bsymbolic?)", si->name, lsi->name);
~~~ ^
bionic/linker/linker.h:49:94: note: expanded from macro 'DL_ERR'
__libc_format_buffer(linker_get_error_buffer(), linker_get_error_buffer_size(), fmt, ##x); \
^
bionic/linker/linker.cpp:3178:67: error: use of undeclared identifier 'si'
"library %s (built with -Bsymbolic?)", si->name, lsi->name);
^
bionic/linker/linker.cpp:3183:28: error: use of undeclared identifier 'si'
si->name, s->st_size, src->st_size);
^
bionic/linker/linker.cpp:3189:78: error: use of undeclared identifier 'si'
DL_ERR("%s R_ARM_COPY relocation target cannot be resolved", si->name);
^
8 errors generated.
[ 34% 10505/30326] target thumb C++: linker <= bionic/linker/linker_phdr.cpp
ninja: build stopped: subcommand failed.
build/core/ninja.mk:157: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1

real	84m52.122s
user	206m38.768s
sys	14m40.760s

On a side note, the thread mentions that I should build a first time, apply the patches and then build again.

Is it okay to apply the patches before doing the first build?

The whole log is attached in case it is needed.

Thanks in advance!
[Android] TimSchumi:
Just run the repo init command again, with r33 instead of r27
[Android] grumpycoder100:
Hi, so I was just wondering: Would it still be possible to compile LineageOS with a custom toolchain, like Linaro? Been trying to do it for days but to no avail. Tried the editing the envsetup.sh to include linaro 4.9 as well, but no go for building. Any ideas?
[Android] sub77:
first match searching for custom toolchain

https://xdaforums.com/chef-central/android/guide-switching-to-custom-toolchain-t2927662
[Android] dungphp:
Can anybody answer me the problem without simcard (signal) when compile 8.1 Oreo. With 8.0 there is a normal signal. What changes between 8.0 and 8.1?

Thanks

Logcat from my rom:
[Android] poppy22:
make[1]: Leaving directory '/home/ubuntu/omni/out/target/product/ocm/obj/KERNEL_OBJ'

make: Leaving directory '/home/ubuntu/omni/kernel/htc/kernel'

make: Entering directory '/home/ubuntu/omni/kernel/htc/kernel'

make[1]: Entering directory '/home/ubuntu/omni/out/target/product/ocm/obj/KERNEL_OBJ'

INSTALL drivers/media/platform/msm/broadcast/tspp.ko

INSTALL drivers/char/rdbg.ko

INSTALL drivers/media/platform/msm/dvb/adapter/mpq-adapter.ko

INSTALL drivers/media/platform/msm/dvb/demux/mpq-dmx-hw-plugin.ko

INSTALL drivers/video/backlight/lcd.ko

INSTALL net/bridge/br_netfilter.ko

DEPMOD 4.4.84-Poppy-kernel-1.0-gc71546f

make[1]: Leaving directory '/home/ubuntu/omni/out/target/product/ocm/obj/KERNEL_OBJ'

make: Leaving directory '/home/ubuntu/omni/kernel/htc/kernel'

ninja: build stopped: subcommand failed.

14:35:08 ninja failed with: exit status 1

#### failed to build some targets (31:01 (mm:ss)) ####

Can someone help me?

Thank you
[Android] TimSchumi:
Get the last ~500 lines of log output, put them on hastebin and post the link here.
[Android] rubitryofficial:
[MENTION=5216756]jackeagle[/MENTION] can we use ubuntu 16.04 or 17.10? Or is it that u recommend 13?
[Android] NepoRood:
Recommend using the latest LTS release of Ubuntu, at the least. I'm currently using 17.10 myself...
[Android] rubitryofficial:
I have another doubt.

Whenever i port a rom I get that error 7. I manage to fix it and the rom flashes. But it never boots. It gets stuck at the logo itself. What is the problem there?
[Android] Bidyadhar:
Please help me!!

How do i fix this??

https://hastebin.com/kuzajolulo.sql
[Android] karthik km:
Do

Make clean && make clobber

It may be help you
[Android] albertoduqe:
Hi again!

As I keep struggling with Xenon for Lithium with no luck on the camera side, I am also trying to build some nice other rom(s), primarily to practice and get more knowledge and partly to see if with any of them camera works.

Thing is I could only build Lineage successfully because Lithium is supported. With DU or Nitrogen and others I am having no luck. I follow manifests' instructions and search google and github for ideas but I cannot make the build even start for an unsupported device.

The lunch & mka combo does not work, in lunch menu you need to choose one of the supported devices. Brunch does not work either. With Nitrogen it goes as far as entering ninja and then stops saying that it couldn't find device in some config somewhere. DU does not even go that far.

I of course pulled lithium's device, kernel and vendor as I did for Xenon and modified the mk files in device/xiaomi/lithium...

What's the trick there? Doesn't this work with local_manifest and editing device's mk files as is explained at the beginning of this guide? It did work for Xenon (despite camera).

Any ideas, tips, links to useful resources will be of great help.

Thanks guys!
[Android] quake73:
I'm getting these "vtable" errors in external/webrtc:

https://hastebin.com/ralareqete.sm

https://hastebin.com/gexulifeso.sql

Any ideas/suggestions/directions?
[Android] DiamondJohn:
Are you building OR "porting"? This thread is about building from source.
[Android] poppy22:
[ATTACH[/ATTACH]

This is my compilation log. Thanks

device tree：

https://github.com/poppy1/android_device_htc_ocm.git branch or8.1

View attachment build.log
[Android] quake73:
There is an error with vendor/htc/ocm/proprietary/etc/data/netmgr_config.xml. The error is, <?xml version="1.0" encoding="UTF-8"?> is at line 8 when it should be the first.

Do you have some comments or empty lines at the beginning of that file? Try moving <?xml version="1.0" encoding="UTF-8"?> to the top.
[Android] poppy22:
Thank you
[Android] quake73:
Well, the message tells you what you can try :)

Either try running "make update-api" in terminal which seems easier but most of the time it didn't help me much (when I had encountered this error).....

Or add these line in front of each of the 4 offending methods (I found them defined in frameworks/base/telephony/java/android/telephony/SmsManager.java)

/** [MENTION=278736]hide[/MENTION] */

For example:

private void sendMultipartTextMessageInternal(

turns into:

/** [MENTION=278736]hide[/MENTION] */

private void sendMultipartTextMessageInternal(
[Android] Lucchetto00:
Hi, guys. I'm trying to build PixelExperience 8.1.0 but I'm stuck in this error, what I can do ?

frameworks/native/libs/ui/include/ui/ANativeObjectBase.h:22:10: fatal error: './frameworks/nativelibs/nativebase/nativebase/nativebase.h' file not found
#include <nativebase/nativebase.h>
[Android] MYEUHD:
I'm compiling Omnirom 7.1 for the samsung galaxy S I9000 and I'm getting the following error:

[ 66% 1423/2132] target Pack Relocations: utility_erase_image (/media/MYEUHD/3208...smtd/obj/UTILITY_EXECUTABLES/utility_erase_image_intermediates/PACKED/erase_image)
FAILED: /bin/bash -c "(/media/MYEUHD/32085D0A085CCF0B/Roms/omni-7.1/out/host/linux-x86/bin/acp -fp /media/MYEUHD/32085D0A085CCF0B/Roms/omni-7.1/out/target/product/galaxysmtd/obj/UTILITY_EXECUTABLES/utility_erase_image_intermediates/LINKED/erase_image /media/MYEUHD/32085D0A085CCF0B/Roms/omni-7.1/out/target/product/galaxysmtd/obj/UTILITY_EXECUTABLES/utility_erase_image_intermediates/PACKED/erase_image ) && (prebuilts/misc/linux-x86/relocation_packer/relocation_packer /media/MYEUHD/32085D0A085CCF0B/Roms/omni-7.1/out/target/product/galaxysmtd/obj/UTILITY_EXECUTABLES/utility_erase_image_intermediates/PACKED/erase_image )"
ERROR: ELF file is not a shared object
ERROR: Failed to load as ELF
ERROR: /media/MYEUHD/32085D0A085CCF0B/Roms/omni-7.1/out/target/product/galaxysmtd/obj/UTILITY_EXECUTABLES/utility_erase_image_intermediates/PACKED/erase_image: failed to pack/unpack file
[ 66% 1423/2132] target StaticExecutable: static_busybox (/media/MYEUHD/32085D0A0...ct/galaxysmtd/obj/UTILITY_EXECUTABLES/static_busybox_intermediates/LINKED/busybox)
ninja: build stopped: subcommand failed.
build/core/ninja.mk:157: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1

real	19m29.921s
user	6m46.696s
sys	4m14.728s

Can somebody please help me? Thanks!