yashsingh1/xdaforums huggingface dataset:
[Android] lamp216:
hello, im trying to make a 8.1 rom build for kiwi and i get this error

hardware/qcom/audio-caf/msm8916/mm-audio/aenc-aac/qdsp6/Android.mk: error: mm-aenc-omxaac-test (EXECUTABLES android-arm64) missing libaudioalsa (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.
hardware/qcom/audio-caf/msm8916/mm-audio/aenc-amrnb/qdsp6/Android.mk: error: mm-aenc-omxamr-test (EXECUTABLES android-arm64) missing libaudioalsa (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.
hardware/qcom/audio-caf/msm8916/mm-audio/aenc-evrc/qdsp6/Android.mk: error: mm-aenc-omxevrc-test (EXECUTABLES android-arm64) missing libaudioalsa (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.
hardware/qcom/audio-caf/msm8916/mm-audio/aenc-qcelp13/qdsp6/Android.mk: error: mm-aenc-omxqcelp13-test (EXECUTABLES android-arm64) missing libaudioalsa (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.
build/core/main.mk:746: error: exiting from previous errors.
22:16:38 ckati failed with: exit status 1

i dont get where the compiler is looking for the lib, hope somebody can help me, my sources

KERNEL = https://github.com/lamp216/android_kernel_huawei_kiwi

DEVICE = https://github.com/lamp216/android_device_huawei_kiwi

VENDOR = https://github.com/lamp216/proprietary_vendor_huawei
[Android] karthik km:
Just set

ALLOW_MISSING_DEPENDENCIES=true

In your BoardConfig.mk file

Located at ( device/vendor_name/device_code)
[Android] aoleary:
I had the same error before for a different device. You need this: https://review.lineageos.org/#/c/202346/

cd hardware/qcom/audio-caf/msm8916
git fetch https://github.com/LineageOS/android_hardware_qcom_audio refs/changes/46/202346/4 && git cherry-pick FETCH_HEAD
[Android] albertoduqe:
Hi!

I apologize for insisting but I have one main missing piece of the puzzle to make a bootable Oreo Aimrom for Lithium (I think). It might be that sorting this out it still won't boot, but this is what's missing for sure right now.

I have used lineageos sources for lithium and msm8996-common devices, floppy kernel sources for kernel (already used those for several nougat builds, no problems). Modified devices trees for aosp compatibility (got rid of xiaomi doze, etc.) and building gets one error:

[986/986] including ./vendor/xiaomi/msm8996-common/Android.mk ...
[B]device/xiaomi/msm8996-common/configpanel/Android.mk: [B][COLOR="Red"]error:[/COLOR][/B] ConfigPanel (APPS android-arm64) missing org.lineage.platform.internal (JAVA_LIBRARIES android-arm64)[/B]
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.
[B][COLOR="red"]build/core/main.mk:730: error: exiting from previous errors.[/COLOR][/B]
09:56:34 ckati failed with: exit status 1

I've compared working trees with those of the nougat roms I have working ok, and there, in the same file, the call is to "org.cyanogenmod.platform.internal", but searching those dirs I do not find any location like "...../org/cyanogenmod/platform/internal/"...

Also searched around and only hint I get is that a library with that name should be included in LineageOS/android_lineage-sdk, which I find in their source for lineage-15.0... So in the case of nougat roms, source of library should be LineageOS/cm_platform_sdk... I find that in LegendRom's sources, but not in many others, but they still work perfectly, compile, and everything.

So... Can anyone please help? What am I missing here???

Thanks a lot :)
[Android] xenreon:
That's not a solution.

Either remove configpanel or edit them to point to lineage instead of cm, it's asking for the sdk that was rebranded in Oreo from cmsdk to lineagesdk.
[Android] albertoduqe:
Would you care to elaborate just a little bit on that?

How do I exactly edit that to point the right way? I mean, in what file/s? And where is the library that should be pointed to?

THANKS!
[Android] xenreon:
Check this as a reference.
[Android] yuyureka:
build/core/tasks/kernel.mk:109: error: BOARD_KERNEL_IMAGE_NAME not defined

I am buildings nos 8.1 and getting this error

---------- Post added at 11:04 AM ---------- Previous post was at 10:49 AM ----------

https://hastebin.com/pasazuhela.makefile

Any help
[Android] albertoduqe:
Thanks.

That is the repo I have synced to my working tree and those commits are merged, and that's what I do not understand: that is supposed to be already sorted out, the rebrand done...

Anyway thanks a lot for replies. I'll keep searching...
[Android] xenreon:
You have lineagesdk synced?
[Android] albertoduqe:
I do:

<project path="lineage/sdk" name="LineageOS/android_lineage-sdk" remote="github" revision="staging/lineage-15.1" />

Not sure if it's the right path becasue it's the first time I have to manually add it...

And most of all: no idea of how it's going to work just like that.

Anyway, after syncing it tried another build and failed too. This time the error was:

build/core/droiddoc.mk:132: error: FindEmulator: find: `vendor/lineage/build/tools/droiddoc/templates-lineage-sdk': No such file or directory

So I synced vendor/lineage.

Then build showed new errors: some files were conflicting between vendor/aim and vendor/lineage, which was to be expected. Renamed them in vendor/lineage and brunched again.

And same spot: build stopped with same original error about org.lineage.platform.internal.

I have done sgrep org.cyanogenmod.platform and there are no results, from which I understand the rebrand is complete.

Still, obviously something I am getting wrong here...
[Android] lamp216:
set

BOARD_KERNEL_IMAGE_NAME = Image

inside your BoardConfig.mk device tree
[Android] xenreon:
The path should be /lineage-sdk. Don't confuse up - with _ as it's only the latter (at least in Lineage) that's used for guiding path.
[Android] albertoduqe:
You are totally right. I knew about it but hadn't even seen it.

Made the change and repo synced again.

By the way: I found the problem :) Your link was very useful. For some reason, no idea why, in my device/xiaomi/msm8996-common/configpanel/Android.mk, the library was defined as "org.lineage.platform.internal" when it should have been "org.lineageos.platform.internal". Don't understand why was that but changed it and building doesn't give me the error anymore :)

Now it gives me others... Strange because yesterday when build succeeded I didn't get any kernel errors but now...

[ 2% 15/620] build /home/albertoduqe/...get/product/lithium/obj/KERNEL_OBJ/usr
FAILED: /home/albertoduqe/aimromo/out/target/product/lithium/obj/KERNEL_OBJ/usr
/bin/bash -c "(echo \"Depending on /home/albertoduqe/aimromo/out/target/product/lithium/obj/KERNEL_OBJ/usr is deprecated.\" 1>&2 ) && (echo \"Use INSTALLED_KERNEL_HEADERS instead.\" 1>&2 ) && (exit 1 )"
Depending on /home/albertoduqe/aimromo/out/target/product/lithium/obj/KERNEL_OBJ/usr is deprecated.
Use INSTALLED_KERNEL_HEADERS instead.

Build continues one more step but fails soon after.

Of course no idea about that, first time I find it, but I'll search.

Thanks for help!
[Android] xenreon:
It's defined as lineageos in the original repo, you probably edited wrong or something? Anyway post the full log alongside your modified sources.
[Android] lamp216:
hi, i have problems again while building slim 8.1 for kiwi i get this error, https://pastebin.com/Vc4gt4m0 i had like 2 hour searching for a solution, a this point i dont know what to do
[Android] albertoduqe:
Honestly: I'd swear I didn't touch it but yes, I see it ok in the the repo so I must have.

I will come back with full log and the rest.

From the little I know, the FAIL I am getting now cannot mean that I have to change all of the occurrences of "KERNEL_OBJ/usr" for
"INSTALLED_KERNEL_HEADERS"... I mean there are hundreds, maybe thousands of those in the whole source and roms are already out with it. If it was the case it's a change that'd be already merged... I guess. So the issue must be somewhere else.

I'll keep digging.
[Android] xenreon:
Well this looks pretty useful, before posting here it's better to search in-depth (Google/github/gerrits/XDA).
[Android] albertoduqe:
I do try to search thoroughly :) and actually I did find that one. And yeah some instances of that occurrence are changed but only in camera and dataservices... ?

Precisely following that lead I did the sgrep and there are hundreds of occurrences in the whole source... So I guess it only has to be changed whenever it appears within device tree... Doesn't make much sense to me but well what would I know? :)

I'll try that and keep working on it.

Sorry for spamming the thread and thanks again.
[Android] karthik km:
My device having kernel source for nougat (msm8916)

Can any one tell me about

How to make my kernel source compatible with Oreo?

Any help highly appreciated

If the questions is already asked

Then please provide me a link

Thanks
[Android] Jay_B:
Error solved
[Android] alphamale:
Build error

Looking for help with this error https://hastebin.com/ecelenuwuv.coffeescript
[Android] GamingDevilsCC:
I'm having an error during the build process of AOSP_Extended on a lg g3, d852. Specifically all the warnings, and this error.

ninja: error: '/home/ubuntu/aex/out/target/common/obj/JAVA_LIBRARIES/org.lineageos.platform.internal_intermediates/classes.jack', needed by '/home/ubuntu/aex/out/target/common/obj/APPS/FlipFlap_intermediates/with-local/classes.dex', missing and no known rule to make it
01:16:34 ninja failed with: exit status 1

Here's the full log that includes the warnings.

https://pastebin.com/C8C8XYRt
[Android] Jay_B:
Hi guys,

I was able to compile a XenonHD ROM for my Mi Max2.

When I flash the ROM it get stuck at MI logo...

What needs to be done here. Sorry no idea how to take a log file hence didn't attach here.

Any help will be appreciated a lot. Thank you.
[Android] NepoRood:
Power off the device, connect it to PC, launch terminal...

Power on the device, type in terminal:

adb logcat -d > logcat.txt

The log will be in whichever directory you typed the adb command...
[Android] Jay_B:
Thank you for the info.

Will do it in the morning and update here. Appreciate the help.
[Android] sscsps:
No, you need to get last_kmsg.

Mi logo is the splash screen, not the boot animation
[Android] antariksh:
Advice from one beginner to another. Whenever you get 'out of your understanding' replies, pick up the keywords from the post and search on 'Git', you'll various commits regarding it. It really helps.

If you wanna port Oreo to your device, find out some similar device tree's and go through their commit history. Also go through the device tree of Google Pixel if it's a msm8996 device you are porting for.

For example: https://github.com/search?utf8=✓&q=lineage+sdk&type=Commits

Look for the commits similar to what you have read from his post. cmsdk to lineagesdk
[Android] NepoRood:
Ok, I miss read it, lol, for that use:

cat /proc/last_kmsg > lastkmsg.txt
[Android] Jay_B:
Thank you for the update.

Can you please give the steps. I tried it on my PC following the guide https://xdaforums.com/showthread.php?t=1520508

However nothing is happening.

Thank you.
[Android] albertoduqe:
Right. Gave some answers too quick. I usually first search git and reviews and I actually had gone through other devices' commits regarding oreo porting, but not thoroughly enough.

Thanks for the reply and the advice.
[Android] xenreon:
Sync lineagesdk (search on this if you don't know what that is).

It'll require a eng build (a bit of searching will tell you about that).
[Android] Jay_B:
Hmm guess userdebug will not help...

I gues the issue is coming because of defconfig ...

Checked all available sources some are using oxygen_user_defconfig some using mido_defconfig and some msm8953_defconfig...

The released source code has mido_defconfig but no oxygen_defconfig.

Tried to build with all of them... The ROM compiles but boots to Mi logo splash screen and then turns off.
[Android] NepoRood:
If you're flashing with TWRP, you can get logs from it:

Advanced/Copy Log (check the "Include Kernel Log" box) then swipe, it'll copy recovery and dmsg logs to storage
[Android] Jay_B:
That's great will do that and post it here thanks a lot.. Appreciate you time and help.
[Android] xenreon:
You actually will have to pull the console-ramoops (Google this) not the traditional last_kmsg (this slipped out of my mind). Also mido sources aren't going to work out of the box with oxygen so it's better to grab actual oxygen sources and try to update them for Oreo instead, can use mido and other similar device's sources as a reference for that.
[Android] alphamale:
Can someone look at my twrp log. I built a lineage based ROM it won't boot past splash screen https://www.dropbox.com/s/3chuhqr8cb45eej/recovery[1].log?dl=0
[Android] GamingDevilsCC:
I've been avoiding syncing that this whole time since I thought you're not suppose to do this on an AOSP rom.

I'll give it a shot and report back, thank you so much! :)
[Android] ZVNexus:
Getting this when trying to repo sync Nitrogen OS

File "/home/nexus/nitrogen/.repo/repo/main.py", line 531, in <module>

_Main(sys.argv[1:])

File "/home/nexus/nitrogen/.repo/repo/main.py", line 507, in _Main

result = repo._Run(argv) or 0

File "/home/nexus/nitrogen/.repo/repo/main.py", line 180, in _Run

result = cmd.Execute(copts, cargs)

File "/home/nexus/nitrogen/.repo/repo/subcmds/sync.py", line 821, in Execute

project.Sync_LocalHalf(syncbuf, force_sync=opt.force_sync)

File "/home/nexus/nitrogen/.repo/repo/project.py", line 1363, in Sync_LocalHalf

lost = self._revlist(not_rev(revid), HEAD)

File "/home/nexus/nitrogen/.repo/repo/project.py", line 2501, in _revlist

return self.work_git.rev_list(*a, **kw)

File "/home/nexus/nitrogen/.repo/repo/project.py", line 2700, in rev_list

(self._project.name, str(args), p.stderr))

error.GitError: arm rev-list ('^eaef2798bf835a09fa94bf0b0fc23195d64ca4a5', 'HEAD', '--'): fatal: bad object HEAD
[Android] dungphp:
I have a problem with VoLTE, please help.

In the vendor if I set

LOCAL_CERTIFICATE: = PRESIGNED

ROM will run but VoLTE mode error

I know that mandatory set

LOCAL_CERTIFICATE: = platform

The new VoLTE works, but in fact the rom is not running but bootloop

Who help me this problem? Thank you very much !
[Android] Jay_B:
Any help with this guys.

Thank u.
[Android] xenreon:
Lineage sdk is to be synced in /lineage-sdk not in the vendor directory, resync and then clean build.
[Android] Jay_B:
Ok I was finally able to compile the ROM xenonhd.

The phone boots however no sound and fingerprint sensor not working and the screen brightness is very very low any suggestions...

Oh building for Mi Max Oxygen.

Thank you guys..
[Android] albertoduqe:
Dear all,

I succeeded building Cosmic Oreo for Lithium :)

With some problems of course... Thing is, when rom is flashed on its own it feels great, fast and smooth and wifi and bluetooth connect and work quickly (haven't tried nothing else yet). But when gapps get flashed on top of it, it boots and setup is possible, but it immediately gets extremely laggy. I have to skip connecting to wifi because it stays at "looking for backups" and when it finally boots it's a pain to open any app, etc.

I have a log dump of one of those boots:

https://pastebin.com/ttZNpgVX

In the time of the logs, I tried opening play store like twice and settings maybe, not much else...

If anyone encountered similar problems and fixed them or see key lines to look for fixes in my source, it will be of great help.

Thanks!
[Android] Infect_Ed:
Build with gapps included
[Android] albertoduqe:
I did and it was a bootloop...

Also compiled Atomic and exactly same thing.

I will keep looking at logs and see if I can find the main problems and fix them.
[Android] alphamale:
I built a lineage based ROM for my device google pixel 2xl. I can't get it to boot. I noticed this in recovery log ERROR:process.cc(303)] Exec of /postinstall/system/bin/otapreopt_script failed:: No such file or directory. Could this missing directory be the cause of why it won't boot?
[Android] heisenberg33:
hi, i have problems while building Nitrogen 8.1 for cheeseburger get this error, i had like 2 hour searching for a solution, a this point i dont know what to do.

https://hastebin.com/zupebasebo.vbs
[Android] quake73:
Add this line at the bottom of build/core/config.mk:

$(call project-set-path-variant,recovery,RECOVERY_VARIANT,bootable/recovery)
[Android] heisenberg33:
Thank you very much for the quick help :)

still same error with this line :confused:
[Android] quake73:
add these lines at the bottom of build/core/pathmap.mk:

https://pastebin.com/9kT5w55Q
[Android] heisenberg33:
I think that worked but now I have a similar error with the camera :p

https://hastebin.com/qipupabelu.vbs
[Android] quake73:
Get qcom-target and qcom-utils from here: https://github.com/LineageOS/androi...neage-15.1/build/core.....................put them in the build/core folder

then...

add these 2 lines to build/core/config.mk:

include $(BUILD_SYSTEM)/qcom_utils.mk

include $(BUILD_SYSTEM)/qcom_target.mk
[Android] heisenberg33:
hmm..still same error with qcom-target and qcom-utils
[Android] quake73:
there's an error in the url....here are the links:

https://github.com/LineageOS/androi...taging/lineage-15.1/build/core/qcom_target.mk

https://github.com/LineageOS/androi...staging/lineage-15.1/build/core/qcom_utils.mk

Put them in build/core. (create a new text file and copy/paste the contents)
[Android] heisenberg33:
I had already done that and and I changed that, I hope that's right

# Bring in Qualcomm helper macros

include vendor/lineage/build/core/qcom_utils.mk to include build/core/qcom_utils.mk
[Android] MOAMEN123:
thanks this is so helpful

---------- Post added at 12:22 AM ---------- Previous post was at 12:21 AM ----------

thanks this is so helpful
[Android] albertoduqe:
Hi everyone!

I keep working on several oreo builds for Lithium. One of them stuck in bootloop.

I have tried all kinds of swapping of projects related to hardware, as I deemed, from logs, that the cause is there. Still no success.

This is a paste of one of the bootloops:

https://pastebin.com/4fzkjrGr

Te main problem I believe resides at the end, where the same two/three lines repeat over and over... I have searched for the same kind of errors and haven't found an answer. Some stuff I find seems to point at qualcomm signature but not sure...

Any ideas will be most welcome!!!
[Android] rajeshdubey293:
build 14.1 from 15.1 source code

i have synced 15.1 lineage OS source code and built 15.1 ROM successfully for my phone. now what if i want to make 14.1 ROM for my device ? should i download whole source code for 14.1 tree ? please guide me.
[Android] aoleary:
Yes. To its own build folder. Don't mix them
[Android] rajeshdubey293:
can i do as you have mentioned in this post..i.e for AOGP or slim ROM. i meant downloading whole source in minute using --reference flag. Will it work for 14.1 tree?
[Android] aoleary:
No. You are using two completely different versions.

For example, files that have the same name would be different to account for the differences between the two versions.
[Android] karthik km:
I have built AOKP 8.1 ROM

Everything is working except

there is "no in call sound"

How to fix this issue

Can any one help me ?

Any commits on github to fix this issue ?

Thanks
[Android] rajeshdubey293:
OK. thank you for guiding me.
[Android] antariksh:
Analyze the logs and dmesg, refer to similar device tree's. (same chipset)

and make a better post next time (link to device tree, link to commits, link to logs). Basically provide as much information as possible. Simply posting a question won't give you a solution.
[Android] karthik km:
Thanks
[Android] antariksh:
You didn't link your device tree, so am assuming you don't have this already present: First thing you can do is add 'ro.aos.display.version' in system.prop of your device tree. You might find the value for that prop in stock ROM or any other custom ROM.

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

you will find a manifest.xml file in your device tree. Match the version of the Sensor and Power HAL you are building in device.mk to the one's you are specified in manifest.xml. (check other entries too, just in case)

Or try to build the rom without extra HAL entries in manifest.xml, have a look at this, keep your entries to this minimum and try to boot the ROM.

P.S: Add your git username (only username not entire link) in you XDA Profile.
[Android] albertoduqe:
Dear friend: thanks for your reply :)

And apologies for failing to point out my device sources: they are msm8996-common and lithium from PsyMan47.

The vendor.img/treble-support problems I have more or less sorted out, although in each rom I am working on the behavior is different. A lot of factors involved I guess. Atomic gets built only if vendorimage stuff is disabled. Gzosp gets built no problems, etc.

I still haven't tried what you suggest though, and I will. I mean, I checked the files that state how that particular prop is created, or some of them, and all was in place and shouldn't be affected, as far as I know, by what changes I was making to build/core/Makefile. But of course, how should I know? I will try what you say.

And I am looking right now at what you say about the other issue, HALs and all...

THANKS!
[Android] antariksh:
No back camera found.

Am trying to port Oreo for Moto X Style (clark) running SD808 (msm8992) chipset.

I was able to clear all the major bugs except back camera. It's kinda like a roadblock where the back camera just don't want to be found.

Things I have tried:

Clean build without any addition libshims or HAL's. Basically all the camera blobs from stock ROM and camera.device@1.0, camera.provider@2.4 from source. No luck.

Building with CameraWrapper (various versions) used for msm8992 and other motorola devices, and just the necessary libshims (MediaCodec) which had errors in log.

Device tree and vendor tree for wrapper. Logs for same

Building with OSS Camera HAL (imported from CAF repo). with dozens of changes to be able to compile and build it.

But the same error. No back camera found.

Device Tree and Vendor tree. and the latest Logs.

I have literally spent an entire month to make camera work (am new to this). Tried various combinations of HALs (legacy and non-legacy camera.device@1.0), commits, scripts. :(

I even reworked entire device tree from Nougat.

Kernel that am using is already up streamed to 3.10.108 but if you have any changes for it, please report. Am willing to learn, if it's difficult (or out of my league), still post, i'll try to understand as much as possible.

Also all the other services are running perfectly in dmesg logs.

Whats working is the Front camera (in OpenCamera app). Taking pictures, video recording, even the front facing flash works.

What I haven't tried is:

Kang any blobs from other devices (HAX'ed few of them to work on Oreo)

Moved bin files to vendor directory (I read somewhere that it's only to match qcom sepolicy path's)

ROM Thread.

Any kind of suggestion is highly appreciated. Thanks in advance.