yashsingh1/xdaforums huggingface dataset:
[Android] arnabJ:
I know it should be in out/target/product/<DEVICE>/ but the zip is not there.

I have these files and directories only:

build_fingerprint.txt

clean_steps.mk

current_build_config.mk

obj [Dir.]

previous_build_config.mk

system [Dir.]

[MENTION=5417899]DiamondJohn[/MENTION] , I also thought that 11k lines are very less.

Any idea what could be the reason?
[Android] darjwx:
In Oreo arm is about 50-60k and arm64 about 70k iirc.

Maybe you are missing some stuff in the build repos. (build, build_kati, build_soong.)

Did you picked the topic I told you about?
[Android] arnabJ:
I just changed cpu type to generic that time.

Will try to pick and retry.
[Android] CZ Eddie:
I'm needing a new temp phone and also wanting to learn to dev and port features from one ROM to another ROM/device.

The Nexus 6P is probably the way to go. But I like the Moto X Pure MUCH better (for various reasons not important on this thread).

From ease of learning perspective, will it be much smarter to get the Nexus 6P instead? Or will they be about the same to learn/dev on?

I'm not interested in Nougat or Oreo and will be sticking to developing/learning Lollipop (and maybe Marshmallow).
[Android] arnabJ:
I picked these :

Add kryo support.

soong: use optimal FPU on Kryo targets

Add support for an armv7 variant for Kryo

libc: Add kryo specific memcpy

Add arm neon and mips dspr2 arch features

Do I need to cherry-pick all of the changes present there? I will only buld for OP3 and its armv7-neon kryo

and got these errors:

[38/38] bootstrap out/soong/.minibootstrap/build.ninja.in
[4/4] cp out/soong/.bootstrap/bin/bpglob
[619/620] glob vendor/*/*/Android.bp
[39/40] soong_build docs out/soong/.bootstrap/docs/soong_build.html
FAILED: out/soong/.bootstrap/docs/soong_build.html
out/soong/.bootstrap/bin/soong_build -t -b out/soong --docs out/soong/.bootstrap/docs/soong_build.html ./Android.bp
error: bionic/libc/Android.bp:625:17: unrecognized property "arch.arm.kryo"
error: bionic/libc/Android.bp:1018:17: unrecognized property "arch.arm.kryo"
error: bionic/libc/Android.bp:1090:23: unrecognized property "arch.arm64.cortex_a73"
error: bionic/libc/Android.bp:1098:17: unrecognized property "arch.arm64.kryo"
[40/40] out/soong/.bootstrap/bin/soong_build out/soong/build.ninja
FAILED: out/soong/build.ninja
out/soong/.bootstrap/bin/soong_build -t -b out/soong -d out/soong/build.ninja.d -o out/soong/build.ninja Android.bp
error: bionic/libc/Android.bp:625:17: unrecognized property "arch.arm.kryo"
error: bionic/libc/Android.bp:1090:23: unrecognized property "arch.arm64.cortex_a73"
error: bionic/libc/Android.bp:1018:17: unrecognized property "arch.arm.kryo"
error: bionic/libc/Android.bp:1098:17: unrecognized property "arch.arm64.kryo"
ninja: build stopped: subcommand failed.
20:58:17 soong bootstrap failed with: exit status 1
build/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1

#### make failed to build some targets (15 seconds) ####
[Android] darjwx:
You probably don't need all those commits. But you can just do

repopick -t kryo-libc

and it will cherry pick all the topic automatically.

To use repopick you have to do first:

. build/envsetup.sh

I guess you missed a commit on the topic adding support, so it fails.
[Android] arnabJ:
Ok, so I deleted my bionic directory and did repo sync so that I can have unaltered bionic directory again.

Once it gets completed, I just cd to it and run the above command you gave?

I don't need to provide LineageOS URL as in cherry picking?

---------- Post added at 09:43 PM ---------- Previous post was at 09:26 PM ----------

I am trying to build AOSP and not LineageOS in particular.

So, repopick doesn't works.
[Android] darjwx:
Oh, I thought you were building lineage. You have to add some stuff to be able to use the repopick command of lineage for aosp.

Just pick manually the topic then.

EDIT: forgive me... Yeah, you are building aosp. I don't sleep much these days, blame university :P
[Android] arnabJ:
No problem. You are at least helping me when I need it.

I will try now to pick as I did earlier.

Edit: I picked this one only: libc: Add kryo specific memcpy

This time I got 2 errors:

error: bionic/libc/Android.bp:1090:23: unrecognized property "arch.arm64.cortex_a73"
error: bionic/libc/Android.bp:1098:17: unrecognized property "arch.arm64.kryo"

I will try fresh tomorrow.

I also haven't slept soundly for quite some time now.
[Android] albertoduqe:
Hi again people :)

Well I tried another build with a different approach at obtaining device sources (synced Lineage repo, breakfasted lithium and then manually copied device, kernel and vendor appropriate folders to xenon working folder/s), edited mk and dependencies files as necessary (adding suggested lines for bootanimation, thanks again) and compiled using brunch again.

Building was successful but gave me a partial rom zip, just 200mb instead of 500 and something. When I flashid it, it went through but then twrp said "erasing incomplete rom" or something similar, and unable to unpack ramdisk (or something similar).

I am sorry for not providing logs but didn't have time to do so when I shut down computer...

Any ideas as to why and how a build could go through and be successful but give an incomplete rom zip with some ramdisk issues? I mean, base the rom was untouched respect the one used yesterday for a full although issued rom...

The only thing I did not do was syncing xenon repo again, but I do not see how that can affect if repo was synced just the day before and all the files were supposed to be there in local...

Searched but couldn't find references to this issue...

Sorry for the length and thanks in advance!
[Android] DiamondJohn:
Not building ODEX?

I am building crDroid for an xt897, Nougat, using a slightly modified device tree from LineageOS. NB: the build is also permissive and I have also done a pass at the SEPolicies.

It all builds, flashes and boots OK, but after running a little while, it all starts to get a FC on nearly every app (calendar seems immune).:(

After a little research, I checked the logs and it says it cant find the class (see also above post: https://xdaforums.com/showpost.php?p=73670347&postcount=7455), looking in the APK etc etc etc. However, I have now noticed that there are no ODEX files (eg /system/app/LatinIME/oat/arm/LatinIME.odex) being built and stored while another (AOSP) nougat build (on different phone) does create ODEX files.:confused:

Here is my last_kmsg: https://www.hastebin.com/aqudomabew.sql

and my logcat:https://clicknupload.org/9nncefqx65es 8mb expanded from zip:o

NB: in my logcat I added some of my own logging. It will have "System : DEBUG: " as a prefix.:o

Anyone have any ideas what may cause this behavior? Or where I should start looking?:confused:
[Android] Xaif:
Always use Hastebin to share your error
[Android] darjwx:
There are ambit supported overlays in your device tree. Think about overlays more or less like something that defines some of the features that your device will have in the rom.

In the actual Oreo state, there's a lot of features and commits missing in repos like base and settings, so a lot of those definitions are broken.

For now, just remove the lines that are failing.
[Android] nikhilpal2705:
Navigation Bar Problem

Build successfully halogenOS 7.1 but Navigation bar not automatically enabling on first boot.

I have to manually turn it on from settings.

How to fix this so that Navigation bar get automatically enabled on first boot?

Device: MotoG3

Rom: halogenOS 7.1

Edit: After following below answer it's working.

Thanks [MENTION=6168349]darjwx[/MENTION]
[Android] darjwx:
Add this overlay to your device tree.

<bool name="config_defaultToNavigationBar">true</bool>

In: overlay/framework/base/core/res/res/values/config.xml
[Android] desalesouche:
Hi all!

I would like to ask how to add a device definition to this:

#elif defined(CONFIG_MACH_HUAWEI)

i wanna add CONFIG_MACH_SCALE

so they are both working for each device needed.

thanks!
[Android] Arjun KalyanRam:
Installantion of jdk and required tools gives me error plz help !
[Android] YedanyXD:
Obviously, that is and old version of the tools, you must have to download the latest.
[Android] Arjun KalyanRam:
Okey .can u plz give me the code .am new to these stuffs !
[Android] YedanyXD:
Are you using Ubuntu? Which version?
[Android] Arjun KalyanRam:
Ubuntu 17.04
[Android] dungphp:
I have problem when compiling Nitrogen Oreo:

qcom/sepolicy ? My phone is msm8952 (caf)

Who can help me ? Thanks
[Android] Arjun KalyanRam:
I was downloading platform source codes today and unfortunately the repo sync stoped .will the sync continue or will it start fresh when i again use the repo sync -j

Anyone help plz !
[Android] DiamondJohn:
I think your error is actually

device/xiaomi/hydrogen/sepolicy/perfd.te:2:ERROR 'unknown type perfd' at token ';' on line 44146:
allow perfd mpctl_socket:dir { { open getattr read search ioctl lock } { open search write add_name remove_name lock } };
[COLOR="Red"]#line 1 "device/xiaomi/hydrogen/sepolicy/perfd.te"[/COLOR]

And in the future, please use www.hastebin.com

There will be some overlap, but it will be minimal just to ensure it picks up from the correct point; ie where it stopped.

---------- Post added at 07:55 PM ---------- Previous post was at 07:44 PM ----------

I have a build that boots, but when I have taken the last_kmsg, I notice the following near the end

[ 942.275446,0] SysRq : Emergency Remount R/O
[ 942.285182,0] EXT4-fs (mmcblk0p38): re-mounted. Opts: (null)
[ 942.314390,0] EXT4-fs (mmcblk0p22): re-mounted. Opts: (null)
[ 942.317137,0] Emergency Remount complete

Full log: https://www.hastebin.com/qahajoquwo.md

mmcblk0p38 is the /data partition

mmcblk0p22 is the /persist

Should I be concerned? and does anyone see anything else in the log hinting at what the problem was? I think this was from the first boot after a flash, with a full wipe (inc internal storage)
[Android] savsir:
Mi5 android o compile

system/core/init/log.h:20:10: fatal error: 'android-base/logging.h' file not found
[Android] DiamondJohn:
Not sure if your asking me a question, but I think it "FAILED" because of the error in "#line 1 "device/xiaomi/hydrogen/sepolicy/perfd.te"

Fix that, and restart the build.
[Android] Arjun KalyanRam:
Help plz cant do repo sync
[Android] quake73:
Looks like some previous sync failed at a bad moment. Just delete that gradle-plugin.git/shallow.lock file and sync again.
[Android] Qiangong2:
I'm trying to build sudamod 3.1 for my jfltetmo and I get this error:

https://hastebin.com/zotisihuda.pas

My trees: https://github.com/alaskalinuxuser

https://github.com/TheMuppets/proprietary_vendor_samsung/tree/cm-14.1
[Android] Cakzemprongzzz:
I new at this.. I have 4GB ram and AMD A6.. Better to use ubuntu 13.40 or lastest? K thanks
[Android] NepoRood:
I use Ubuntu 16.04, but just about any Linux will work, as long as you are running the correct version of Java for the source you're building

---------- Post added at 05:58 PM ---------- Previous post was at 05:55 PM ----------

You need This
[Android] mukesh22584:
Any guide or link for " How to build on top of custom kernel ?" If answered before please refer to the post, I've searched but not found...
[Android] neonkat:
you mean compiling a build with a custom kernel?

if yes,then just track the custom kernel repo,make a few changes accordingly(if it uses diff. defconfig,ramdisk modification)in device tree.a higher gcc tc might create issues.
[Android] mukesh22584:
I'm new in building also no technical background, So things are not so easy to understand for me, But a lot of helping hands are here in XDA, I've build for my OP5 after few troubles, I'm able to made everything with default setup like default device tree/kernel etc. Now I want to know building with custom kernel and I've searched a lot in XDA but couldn't find any detailed guide, I've tried with custom kernel and made changes in defconfig file, But that build failed, because I don't know where and how make changes for that, Anyway thanks for your reply, My search is still going on.....

Self compiled RR
[Android] neonkat:
if you are using a localmanifest for tracking the kernel,just need to make one change,i.e,instead of tracking the default los kernel,track the custom kernel' git and the specific branch.you can find the custom kernel source on their xda page.

it may happen that the dev. changes the defconfig name in their kernel,for that find:

TARGET_KERNEL_CONFIG :=

in your boardconifg.mk and change it to whatever the custom kernel uses.these changes should be enough.

also custom kernels use custom ramdisks(mostly the tunings and other stuffs),you can add those in your device tree.you can add them or modify it in init.qcom.rc or others(in devicetree/rootdir/etc/*).

also you may find that custom kernels use higher gcc toolchain to build the kernel.check my commit for reference on how to do it.change the location accordingly with yours.

post your issues here,maybe we can help.:)
[Android] savsir:
I have this file but same error continue
[Android] DiamondJohn:
If I understand your question, you have two main choices.

1. Find a pre-coded custom kernel for your device-ROM and replace it with your current kernel, once you find the Kernel source

2. Customize the existing kernel yourself.

For 1 I think you have a brief explanation above

For 2, see this thread https://xdaforums.com/showthread.php?t=1748297
[Android] mukesh22584:
[MENTION=5991747]neonkat[/MENTION] [MENTION=5417899]DiamondJohn[/MENTION] Thanks a lot, That is why I had written in my previous post " XDA has many helping hands" Both of you're one of them, I'm learning and as I've said I've no technical background but person like both of you always meet me in front of row to teach, My pleasure that both of you give me a new direction to learn, Thanks mates....[emoji120]

Self compiled RR
[Android] Arjun KalyanRam:
What to do !

This is waht i get on lunch command
[Android] darjwx:
Have you modified the tree to support viper?

If your tree is up on github I can have a look.
[Android] Arjun KalyanRam:
Ya i modified the .mk files
[Android] darjwx:
You maybe missed something. But I can not help much without taking a look at your tree.
[Android] Arjun KalyanRam:
I cleared that but stuck over here

Faild to build some targets
[Android] darjwx:
Copy the log into hastebin for example please.
[Android] Arjun KalyanRam:
Use hastebin.com and paste the link. Do not paste the whole output directly in xda.

About the error, the problem is that libinit_ghost is defined at the same time in your device and kernel. Are you using a device and kernel from two different roms?[/QUOTE]

No just viper os
[Android] NepoRood:
make clean, re-sync and try the build again
[Android] Arjun KalyanRam:
50 gb of data bruh [emoji24]
[Android] mukesh22584:
No it's doesn't download 50 GB again, after make clean command it's just check all Downloaded repo, and will download if something missing..

Self compiled RR
[Android] DiamondJohn:
If you already have the code, then a resynch will basically only download the differences. ie only MB's depending on how much has changed at source and what you have changed.

Make clean simply clears your out directory. ie local files, no web data.
[Android] Arjun KalyanRam:
So i have to do a repo init and a repo sync again thats it right ?
[Android] mukesh22584:
No repo init just "repo sync -f --force-sync" (without quote)..

Self compiled RR
[Android] xenreon:
rm -rf everything except the .repo folder, then repo sync (I believe you've already learned the commends).
[Android] Arjun KalyanRam:
Actualy i dont !
[Android] NepoRood:
I wasn't actually quoting you, lol, but, since we're on it, "cd" into your build directory and:

rm -rf *

Will remove everything from your folder, then follow it with a sync command

repo sync -c -f --force-sync --no-tags

As long as you don't delete the .repo/projects folder, sync shouldn't take all that long (depends on your internet connection), either way, you won't be downloading the whole source again.
[Android] savsir:
Still same
[Android] DiamondJohn:
I personally use the following to automatically remove anything that should not be there,and hence get repo to do the "dangerous" rm (ie avoid an oops moment)

[B][COLOR="Blue"]repo forall -c git clean -fdx[/COLOR][/B];
repo forall -c git reset --hard;
repo forall -c git checkout -f;
repo sync -fc --force-sync --force-broken;

and if that has failures, read the log (checking for lock files), and also try

repo --trace sync -l -fc --force-sync --force-broken;

for more info of why it fails, if it does that is.
[Android] Ripudamankaushik:
Hey friends whenever I include qcom/common.mk in my makefile I run into this error

ninja: error: 'out/target/product/athene/obj/SHARED_LIBRARIES/libqdutils_intermediates/export_includes', needed by 'out/target/product/athene/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/import_includes', missing and no known rule to make it

build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed

BTW I am using display,audio and media folders in hardware/qcom from cm-14.1-caf repo. and I am using Aosp-caf device tree and kernel..........Plz help me out
[Android] neonkat:
did you sync them in correct folder?the current branch for your soc?it should go in:

hardware/qcom/display-caf

hardware/qcom/media-caf

hardware/qcom/audio-caf
[Android] SanketMohapatra:
I am here from lyf flame 8 development community we have progressed a bit in our booting process so we compile a recovery by the help of the device tree which we got successful in making but after that we encountered a security error which told us that the bootloader of the phone is locked and we are not able to proceed there after

After that we decided to analyse the problem with the help of the dump image of the boot file and we got some shocking results as you can see from screenshot

Even many of the fastboot commands are returning unknown command error so we think that the device maker has restricted many of the commands

Our phone is one of the another Snapdragon 210

So please anybody having some idea please help us with it and I definitely think that I will get some help in this forum which is already achieved milestones in the development
[Android] santosh61:
Help me got this error.
[Android] neonkat:
1.please don't upload the log here.either upload in a text file(there was no point of posting again)or just use hastebin(crtl+c and crtl+v,as simple as that).

2.the error has been posted many times,try to use the search option or just a google search will help you.

check my post

https://xdaforums.com/chef-central/android/guide-android-rom-development-t2814763/post73673261
[Android] santosh61:
it didnt solve the problem. errors are still same.
[Android] neonkat:
[MENTION=6041288]santosh61[/MENTION]

from your previous error:

/bin/bash: +make: command not found

you sure you setup the environment correctly?

sudo apt-get install build-essential (will install make)

weird that the error is same.(external/apache-http error shouldn't be there)
[Android] santosh61:
yeah I am sure. I alredy buid viper and aokp rom in this pc.
[Android] mukesh22584:
I've made changes in my boardconfig.mk also in dependencies file but below issue got...
[Android] Ripudamankaushik:
Well all the folders were in d right positions but I still got the same error so i replaced the entire hardware/qcom folder with the one from CM repo.......As a result i didint get the previous error but this one

ninja: error: 'out/target/product/athene/obj/STATIC_LIBRARIES/lib_driver_cmd_qcwcn_intermediates/export_includes', needed by 'out/target/product/athene/obj/EXECUTABLES/hostapd_intermediates/import_includes', missing and no known rule to make it
[Android] arnabJ:
Anyone can help me through this:

ninja: error: '/home/arnabj/Android/AOSP/LineageOS15/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.internal_intermediates/classes.jack', needed by '/home/arnabj/Android/AOSP/LineageOS15/out/target/common/obj/JAVA_LIBRARIES/com.cyanogenmod.keyhandler_intermediates/with-local/classes.dex', missing and no known rule to make it
15:55:33 ninja failed with: exit status 1
build/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1
make: Leaving directory '/home/arnabj/Android/AOSP/LineageOS15'

#### make failed to build some targets (15:02 (mm:ss)) ####
[Android] adithya2306:
Hi,

I'm trying to build Legendrom for Yuphoria (lettuce)

I am always getting this error:

FAILED: /bin/bash -c "(rm -f /home/adithya/android/system/out/target/product/lettuce/obj/STATIC_LIBRARIES/libcompiler_rt-extras_intermediates/libcompiler_rt-extras.a ) && (prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-ar crsPD /home/adithya/android/system/out/target/product/lettuce/obj/STATIC_LIBRARIES/libcompiler_rt-extras_intermediates/libcompiler_rt-extras.a /home/adithya/android/system/out/target/product/lettuce/obj/STATIC_LIBRARIES/libcompiler_rt-extras_intermediates/lib/builtins/mulodi4.o )"
prebuilts/gcc/linux-x86/aarch64/aarch64-linux-android-4.9/bin/aarch64-linux-android-ar: error while loading shared libraries: /usr/lib/x86_64-linux-gnu/libfl.so.2: invalid ELF header

This is the full log:

https://hastebin.com/noqoxaruvi.sql

Any help would be appreciated. Thanks

EDIT: I fixed the issue :)

The issue was with my host pc (ubuntu)

The libfl.so.2 in PC, was just a bloody text file instead of a library

I downloaded a working libfl.so from here: https://opensuse.pkgs.org/tumbleweed/opensuse-oss/libfl2-2.6.4-2.1.x86_64.rpm.html and replaced it with the libfl.so.2 in my PC

and it worked like a charm :D
[Android] Infect_Ed:
It's because the toolchain was made on arch Linux. I was going to link the same url lol
[Android] xenreon:
I believe this has been discussed here before. If you search in this thread and Google before posting than you'll not only save others, but yourself too a bunch of time.

Either sync cmsdk or remove the stuff that's asking for it.
[Android] Manish Salian:
Hello friends I m new here..Thanks a lot for this lovely guide ..I want to build a Lollipop CM ROM for HTC desire X but I couldn't find a device tree infact I found a one for CM11 so can I use that to build lollipop ROM or do I have to build a device tree for it..if yes is there any guide to do soo ?
[Android] xenreon:
No you can't use cm11 (or any KitKat) device sources to build a different version of Android, you'll need to change stuff accordingly to make it compatible with the version of Android you're building. No direct guide as it varies from device to device. Best bet is trying to find a similar device that has both KitKat and lollipop sources open, studying the differences there then trying to emulate that with a combination of trial and error.
[Android] mukesh22584:
Will anyone help me please, Building for oneplus 5 with custom kernel, I've made nessasry changes in defconfig file but got error, I assume it's some package missing, I'm not able to understand please help me....

https://drive.google.com/file/d/0B10hHGFnGhD2OG91MjBtR2gxZzQ/view?usp=drivesdk

Self compiled RR
[Android] DEVILOPS 007:
Maybe use hastebin in the future? Also, it looks like those commits are missing so if you remove the lines that are having issues and try again then it should hopefully work. I'm no expert so I'm not too sure other than that.
[Android] matteo0026:
Hi guys, I did another LineageOS 15 build, but gives error 6 on TWRP, here is my updater-script.

https://hastebin.com/fidijesale.sql

Can anyone help me? Thanks!

EDIT: I resolved with these 2 commits:

https://review.lineageos.org/#/c/186286/

https://review.lineageos.org/#/c/187372/
[Android] Ripudamankaushik:
Sorry for my lack of information sir, I tried searching first but didn't get any satiable solution .......plz if u can direct me to the right place....I shall be grateful