[Guide][Video Tutorial] How to build Custom ROMs and Kernels![10,P,O,N,M,L]

[widi aprianto]

yes stick in all in yore device repo and always try to keep the board repo as generic as possible avoide other problem when adding other devices that use the same board as your device but do have the same Display, Camera,Sencore, or a Torch Hope this fixes your problem.
Sidenote the overlay xml can also be used to remove unused quick setting toggle there for simplfing the ui and giving you a more oem type look.

Device/board not exist

 

[DJABHipHop]

Device/board not exist

Sorry but I meant to say device or board repo, But the overlay goes on your device folder with the exact folder structure I posted earlier and torch goes in device folder board make or your devices board folder board make but that all depending on how your device tree is setup.

also have a look in /frameworks/base/packages/SystemUI/res/values/config.xml in your LineageOS folder or whatever folder you rom & device source are stored as you may want to see all the available quick setting toggle, you may also want edit my config.xml as my it will work on your device but may not have the all quick setting toggle in the order you want or necessary quick setting toggle visible for your device specification as my config.xml is setup of a device without no torch, nfc and some other thing. Hope this helps you out.

 

[kush57]

There's a kernel for oreo rom for onyx i want to use it for building pie rom. What specific kernel source changes do we need to make it compatible for pie rom
Thanks for the help in advance

 

[lukaspieper]

Well done. A good step getting to the boot animation. :highfive:
Now you need logcat or tombstones to see the next problem. If you get into adb shell, while booting you can run this from your computer:

$ adb shell mount |tee mymounts.text

Which will make a text file on your computer that should have a list of mounted partitions. Is every important thing there?



Pstore is "persistent storage" a defined kernel option to save small amounts of data with the kernel.

Also I fully recommend that no developer flash gapps until they are done fixing everything they want to fix in a ROM. Once you flash gapps, SuperSU, magisk, closed, or anything to the ROM, you change the parameters and the environment. So you should always troubleshoot before flashing anything else. :good:

I'm glad you corrected me on pstore.

I managed to get a logcat (tombstones are not available). I searched for the keywords error, failed, failure. Exception is also a very good search term. Probably the most noticeable error can be found under "BOOT FAILURE" (android.security.IKeystoreService). According to my research it has something to do with Android's credential storage. Somewhere it was recommended to remove the keystore.msm8953.so, that didn't bring me any success.

The other matches about exceptions also seem important to me (otherwise there are some errors about camera and very often avc: denied occurs).

Here is the whole log, some things are repeated frequently, I have no knowledge how to get good logcats.

https://paste.ubuntu.com/p/VFFCCW96hx/

Thanks already.

 

[DJABHipHop]

I'm glad you corrected me on pstore.

I managed to get a logcat (tombstones are not available). I searched for the keywords error, failed, failure. Exception is also a very good search term. Probably the most noticeable error can be found under "BOOT FAILURE" (android.security.IKeystoreService). According to my research it has something to do with Android's credential storage. Somewhere it was recommended to remove the keystore.msm8953.so, that didn't bring me any success.

The other matches about exceptions also seem important to me (otherwise there are some errors about camera and very often avc: denied occurs).

Here is the whole log, some things are repeated frequently, I have no knowledge how to get good logcats.

https://paste.ubuntu.com/p/VFFCCW96hx/

Thanks already.

Try this for clean logcats.

All =  adb logcat >> Locat.txt
Debug =  adb logcat *:D >> Debug\ Logcat.txt
Info =  adb logcat *:I >> Info\ Logcat.txt
Warning =  adb logcat *:W  >>Warning\ Logcat.txt
Error =  adb logcat *:E  >> Error\ Logcat.txt
Fatal =  adb logcat *:F  >> Fatal\ Logcat.txt

Use everything after the equal sign.
Hope this helps you out.

 

[Techguy777]

That is why I made these videos and this thread. About 4 years ago I rated this journey and received very little help, until I meet bubor and steadfasterx. Even then it was an uphill battle.

So, I put this together to answer all of those questions.

So, have you watched this playlist:
https://www.youtube.com/playlist?list=PLRJ9-cX1yE1l6eu-vkgsj61U-Zv3fjzwZ&app=desktop

It is not HD video. And people complain and complain about the low quality, but it is very informative and answers all of your questions if you watch it in order from start to finish.

And a bonus for you: I use the shamu as my example for the entire lollipop portion. You could literally build alongside me in the video series. :laugh:

I'm starting to watch the series right now. I've downloaded the vendor file off the Muppets for cm14.1 branch because I'm trying to build twrp Omni 7.1 if I get that built Ill try 8 or 9. I really guess I need to learn how to use the Google binaries and vendor files I downloaded 7.1.1 files look inside it's a extract moto shamu.sh. How do I use that? Also the final piece of the puzzle is kernel source I've read you need it and you don't any input? I'm going to continue to watch the rest of your videos and search Google. The Muppets vendor file I changed the name and put them in my twrp folder.

Edit I figured out how to extract the Google package with vendor files. You open terminal and and type a command and run the shell. I also found yes you do need a kernel because the recovery and rom both have kernel that way the recovery can boot if you screw up your system. Now then the question is what kernel do you use? Do I use stock 7.1 cause I can't find source for that or do I use Franco or ElementalX or something for nougat?

 

[mafianet]

SD Card Booting

@AlaskaLinuxUser

Thanks for your time.

Just to be sure, "Busybox" will mount all necessary partition on sdcard, change that I need to make on the "ramdisk" scripts after extracted the boot.img from my build.

3 questions if I may;

1. Isn't there a way to make those change before building my AOSP code, considering I will anyways build the code?
2. Correct me if I am wrong, but I will still need the boot.img on my physical HDD in the phone, to mount all partition on sdcard. Isn't there a way to boot directly from other drive than the one on the phone?
2.5 So, if I can't change the heart of phone booting sequence, do you think I can remove all other partition from (except from boot.img and recovery.img) then keep booting on the sdcard?
3. Or, is there a way to make a "if.... else" statement in the init script to check "IF there is a sdcard... mount the sdcard... ELSE mount the HDD normally"

Thanks again for your time, I appreciate.

 

[widi aprianto]

Sorry but I meant to say device or board repo, But the overlay goes on your device folder with the exact folder structure I posted earlier and torch goes in device folder board make or your devices board folder board make but that all depending on how your device tree is setup.

also have a look in /frameworks/base/packages/SystemUI/res/values/config.xml in your LineageOS folder or whatever folder you rom & device source are stored as you may want to see all the available quick setting toggle, you may also want edit my config.xml as my it will work on your device but may not have the all quick setting toggle in the order you want or necessary quick setting toggle visible for your device specification as my config.xml is setup of a device without no torch, nfc and some other thing. Hope this helps you out.

ok. now how to generate kernel config/defconfig?

 

[AlaskaLinuxUser]

Awesome that's going to be watched tomorrow if you used Shamu. No I haven't watched all the videos yet. It kills me cause I know that it's really like 5 minutes to compile a twrp but you have to Know every little thing to setup and get it running but once you do it's like man this is easy. Well I'm not there with building but I remember when I first started rooting I had a Dell venue tablet and they put fastboot flash unlock bin and I'm not kidding I rooted thing not knowing that the unlock bin was for my bootloader and I could have flashed the custom recovery and rooted no problem.

Thanks I'll check it out tomorrow are all the videos on YouTube or do you have more on your website or GitHub?

There are more videos on gitlab than on YouTube. All the gitlab ones end up on YouTube. Often they are a work in progress, but you can certainly check them out. :good:

Is there any guide on selinux denials and fixes..? I have compiled the ROM (lineage 15.1) on enforcing mode by default . My proximity sensor and button backlight works only when selinux is permissive. How to overcome this issue and make that two things to work on enforcing mode.
Any suggestions

I'll have to keep that on the back burners. Good suggestion.

I am succes built los 15 but doesnt have flash light toogle on notif panel, any solution?

Does the camera flash work? :fingers-crossed:

 

[widi aprianto]

There are more videos on gitlab than on YouTube. All the gitlab ones end up on YouTube. Often they are a work in progress, but you can certainly check them out. :good:



I'll have to keep that on the back burners. Good suggestion.



Does the camera flash work? :fingers-crossed:

Ok then how to generate kernel defconfig?

 

[kush57]

There's a kernel for oreo rom for onyx i want to use it for building pie rom. What specific kernel source changes do we need to make it compatible for pie rom
Thanks for the help in advance

@AlaskaLinuxUser help needed

 

[AlaskaLinuxUser]

I am not sure I understand what you are suggesting.

The problem with building using the Omni 7.1 branch is that phones that were encrypted by an Android 8.0 installation or higher cannot be decrypted by TWRP. To work around this, I want to build TWRP using an 8.1 device tree. I am not sure that building with 8.1 would be of any value.

Perhaps you should consider the alternate recoveries, such as Redd wolf or orange fox. I have videos for that. They are based on 8.1. :good:

There's a kernel for oreo rom for onyx i want to use it for building pie rom. What specific kernel source changes do we need to make it compatible for pie rom
Thanks for the help in advance

When you find out, you let is know.

What I mean is, there isn't such a list. If there was, this would be much easier. Your best bet is to compare the kernel of a similar device that went from Oreo to pie, and see what they had to change.

Since every device has a different kernel version or patch level, and every device has different drivers, it is very difficult to know what pieces may need added or changed between android versions. All you can do is compare similar device to see what you need, or compile as is and see what crops up. :good:

 

[AlaskaLinuxUser]

I'm glad you corrected me on pstore.

I managed to get a logcat (tombstones are not available). I searched for the keywords error, failed, failure. Exception is also a very good search term. Probably the most noticeable error can be found under "BOOT FAILURE" (android.security.IKeystoreService). According to my research it has something to do with Android's credential storage. Somewhere it was recommended to remove the keystore.msm8953.so, that didn't bring me any success.

The other matches about exceptions also seem important to me (otherwise there are some errors about camera and very often avc: denied occurs).

Here is the whole log, some things are repeated frequently, I have no knowledge how to get good logcats.

https://paste.ubuntu.com/p/VFFCCW96hx/

Thanks already.

When I load the link to your paste bin, it is blank. Perhaps you could upload it again. ( see pic).

I'm starting to watch the series right now. I've downloaded the vendor file off the Muppets for cm14.1 branch because I'm trying to build twrp Omni 7.1 if I get that built Ill try 8 or 9. I really guess I need to learn how to use the Google binaries and vendor files I downloaded 7.1.1 files look inside it's a extract moto shamu.sh. How do I use that? Also the final piece of the puzzle is kernel source I've read you need it and you don't any input? I'm going to continue to watch the rest of your videos and search Google. The Muppets vendor file I changed the name and put them in my twrp folder.

Edit I figured out how to extract the Google package with vendor files. You open terminal and and type a command and run the shell. I also found yes you do need a kernel because the recovery and rom both have kernel that way the recovery can boot if you screw up your system. Now then the question is what kernel do you use? Do I use stock 7.1 cause I can't find source for that or do I use Franco or ElementalX or something for nougat?

If you want to build Oreo, you need to find a repo with an Oreo kernel, or you will need to upgrade the nougat one. If this is your first build, I recommend you build nougat first to get the hang of things. :good:

@AlaskaLinuxUser

Thanks for your time.

Just to be sure, "Busybox" will mount all necessary partition on sdcard, change that I need to make on the "ramdisk" scripts after extracted the boot.img from my build.

3 questions if I may;

1. Isn't there a way to make those change before building my AOSP code, considering I will anyways build the code?
2. Correct me if I am wrong, but I will still need the boot.img on my physical HDD in the phone, to mount all partition on sdcard. Isn't there a way to boot directly from other drive than the one on the phone?
2.5 So, if I can't change the heart of phone booting sequence, do you think I can remove all other partition from (except from boot.img and recovery.img) then keep booting on the sdcard?
3. Or, is there a way to make a "if.... else" statement in the init script to check "IF there is a sdcard... mount the sdcard... ELSE mount the HDD normally"

Thanks again for your time, I appreciate.

You can do anything you want to your phone. That's the beauty of android development. However it may not work anymore when it is done.....

Correct me if I am wrong, but I will still need the boot.img on my physical HDD in the phone, to mount all partition on sdcard. Isn't there a way to boot directly from other drive than the one on the phone?
2.5 So, if I can't change the heart of phone booting sequence, do you think I can remove all other partition from (except from boot.img and recovery.img) then keep booting on the sdcard?

The chip in the phone, the SoC, comes programmed from the board manufacturer to load about, then boot partitions. You can't change this. Well, you can, but if you knew how, you would not be asking for my help, you'd be teaching the class!

So you will always need the about and boot partitions. As for the others, well, that depends on how good you are and how brave you are. :laugh:

 

[AlaskaLinuxUser]

Here is what I get when I try to load the log cat link.

 

[lukaspieper]

Here is what I get when I try to load the log cat link.

The Ubuntu page is very slow, have you tried leaving it open for a minute vor two?

Else I will upload a cleaner version when I am back at home. Thanks.

 

[DJABHipHop]

Quick question how would I add a folder that a user to add custom Ringtones without having to use twrp or root to flash new ringtones or does that function already exists in LineageOS. either way can that be moved over to the external sd card along with photo,movie,music,document,downloads & application data like setting, to save space to older or low storage capacity devices 16GB & under in the LineageOS Source or for that matter any Android base rom Nougat or newer.
I know there thing like expandable storage & probably some root method or exposed tweak for that but i'd rather not deal with that at all if possible and use the full capacity of the external sd card.

 

[widi aprianto]

There are more videos on gitlab than on YouTube. All the gitlab ones end up on YouTube. Often they are a work in progress, but you can certainly check them out. :good:



I'll have to keep that on the back burners. Good suggestion.



Does the camera flash work? :fingers-crossed:

Back camera work with flash, but when switched to camera with flash is error, cannot take picture

 

[AlaskaLinuxUser]

The Ubuntu page is very slow, have you tried leaving it open for a minute vor two?

Else I will upload a cleaner version when I am back at home. Thanks.

Got it. Well, it never loaded, but there is the "download as text" button, so I used that and got it that way.

So, here is your problem:

01-02 07:10:24.257  1175  1175 E TelephonyProvider: dbh.selectConflictingRow: Expected 1 but found 0 matching rows found for cv password=EUSKALTEL mnc=08 sub_id=-1 bearer_bitmask=0 mmsc= proxy= numeric=21408 name=Euskaltel Internet port= mcc=214 apn=internet.euskaltel.mobi type=default,supl user=CLIENTE
--------- beginning of crash
01-02 07:10:24.257   790   790 E AndroidRuntime: *** FATAL EXCEPTION IN SYSTEM PROCESS: main
01-02 07:10:24.257   790   790 E AndroidRuntime: java.lang.RuntimeException: Error receiving broadcast Intent { act=android.intent.action.USER_STARTED flg=0x50000010 (has extras) } in com.android.server.ConnectivityService$3@f57d12c
01-02 07:10:24.257   790   790 E AndroidRuntime: 	at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:1132)
01-02 07:10:24.257   790   790 E AndroidRuntime: 	at android.os.Handler.handleCallback(Handler.java:751)
01-02 07:10:24.257   790   790 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:95)
01-02 07:10:24.257   790   790 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:154)
01-02 07:10:24.257   790   790 E AndroidRuntime: 	at com.android.server.SystemServer.run(SystemServer.java:383)
01-02 07:10:24.257   790   790 E AndroidRuntime: 	at com.android.server.SystemServer.main(SystemServer.java:237)
01-02 07:10:24.257   790   790 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
01-02 07:10:24.257   790   790 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:889)
01-02 07:10:24.257   790   790 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:779)
01-02 07:10:24.257   790   790 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke interface method 'int android.security.IKeystoreService.exist(java.lang.String, int)' on a null object reference
01-02 07:10:24.257   790   790 E AndroidRuntime: 	at android.security.KeyStore.contains(KeyStore.java:200)
01-02 07:10:24.257   790   790 E AndroidRuntime: 	at android.security.KeyStore.contains(KeyStore.java:208)
01-02 07:10:24.257   790   790 E AndroidRuntime: 	at com.android.server.net.LockdownVpnTracker.isEnabled(LockdownVpnTracker.java:90)
01-02 07:10:24.257   790   790 E AndroidRuntime: 	at com.android.server.ConnectivityService.onUserStart(ConnectivityService.java:4006)
01-02 07:10:24.257   790   790 E AndroidRuntime: 	at com.android.server.ConnectivityService.-wrap28(ConnectivityService.java)
01-02 07:10:24.257   790   790 E AndroidRuntime: 	at com.android.server.ConnectivityService$3.onReceive(ConnectivityService.java:4060)
01-02 07:10:24.257   790   790 E AndroidRuntime: 	at android.app.LoadedApk$ReceiverDispatcher$Args.run(LoadedApk.java:1122)
01-02 07:10:24.257   790   790 E AndroidRuntime: 	... 8 more
01-02 07:10:24.259  1175  1175 E TelephonyProvider: dbh.selectConflictingRow: Expected 1 but found 0 matching rows found for cv password=EUSKALTEL sub_id=-1 bearer_bitmask=0 numeric=21408 mmsc=http://mms.euskaltel.mobi user=MMS mnc=08 mmsport=8080 proxy= mmsproxy=172.16.18.74 name=Euskaltel MMS port= mcc=214 apn=euskaltelmms.euskaltel.mobi type=mms

Notice the phrase: "beginning of crash".
Keep in mind that whatever went bad is right before it. So notice all of these errors:

01-02 07:10:24.259  1175  1175 E TelephonyProvider: dbh.selectConflictingRow: Expected 1 but found 0 matching rows found for cv password=EUSKALTEL sub_id=-1 bearer_bitmask=0 numeric=21408 mmsc=http://mms.euskaltel.mobi user=MMS mnc=08 mmsport=8080 proxy= mmsproxy=172.16.18.74 name=Euskaltel MMS port= mcc=214 apn=euskaltelmms.euskaltel.mobi type=mms

I've seen this before. These errors come from an inability for the telephony package to read the pre set APN settings. In every phone, they ship it with lots of pre set APN settings so the phone can guess your APN settings based on what cell tower it hooks up to and what sim card you have. So either your telephony package is messed up and can't read it properly, or the apn settings are somehow malformed. A typo in the APN settings files can cause this, although that's not always the problem. You can check the APN files by opening the lineageOS source folder you build from, and search for "apn". You should see several XML files pop up. You can then remove the offenders (the ones listed in your errors), by searching in those files for the ones listed in your log. Keep in mind they may be in multiple files. :good:

Quick question how would I add a folder that a user to add custom Ringtones without having to use twrp or root to flash new ringtones or does that function already exists in LineageOS. either way can that be moved over to the external sd card along with photo,movie,music,document,downloads & application data like setting, to save space to older or low storage capacity devices 16GB & under in the LineageOS Source or for that matter any Android base rom Nougat or newer.
I know there thing like expandable storage & probably some root method or exposed tweak for that but i'd rather not deal with that at all if possible and use the full capacity of the external sd card.

With some tinkering, anything is possible, but I don't know the answer for you off of the top of my head. I would suggest that you look in the "settings" app, and find out when it loads the list of ringtones, if you can specify it check multiple places. If so, then add your sdcard, etc... to that list. :good:

Back camera work with flash, but when switched to camera with flash is error, cannot take picture

And what do the logs say if you pull a logcat while doing these things? and dmesg? :good:


For the group:

I'm almost out of internet at present, so I'm using my phone a lot to answer questions. Please forgive the typos, and if I suddenly drop off, I'll be back when the internet get's renewed. :laugh:

Remember to check out my GitLab, there are lots of videos there that are works in progress, about 30+ videos ahead of Youtube. And remember to check the YouTube regularly, new videos are edited and uploaded and will come out pretty much daily during the week.

Logs. Logs. Logs...... It's not voodoo magic, it's a science. The answers are usually right there in the logs. :good:

 

[lucki1000]

Hello,
shortly before finish by building LineageOS16 for cedric(moto g5), I have a mistake:

lineage-sdk/sdk/src/java/lineageos/preference/ConstraintsHelper.java:43: error: package lineageos.platform does not exist
import lineageos.platform.R;
                         ^
lineage-sdk/sdk/src/java/lineageos/preference/RemotePreferenceManager.java:36: error: package lineageos.platform does not exist
import lineageos.platform.Manifest;
                         ^
lineage-sdk/sdk/src/java/lineageos/preference/RemotePreferenceUpdater.java:28: error: package lineageos.platform does not exist
import lineageos.platform.Manifest;
                         ^
lineage-sdk/sdk/src/java/lineageos/preference/ConstraintsHelper.java:77: error: package R does not exist
                R.styleable.lineage_SelfRemovingPreference);
                 ^
lineage-sdk/sdk/src/java/lineageos/preference/ConstraintsHelper.java:78: error: package R does not exist
        mSummaryMinLines = a.getInteger(R.styleable.lineage_SelfRemovingPreference_minSummaryLines, -1);
                                         ^
lineage-sdk/sdk/src/java/lineageos/preference/ConstraintsHelper.java:79: error: package R does not exist
        mReplacesKey = a.getString(R.styleable.lineage_SelfRemovingPreference_replacesKey);
                                    ^
lineage-sdk/sdk/src/java/lineageos/preference/ConstraintsHelper.java:138: error: package R does not exist
                R.styleable.lineage_SelfRemovingPreference);
                 ^
lineage-sdk/sdk/src/java/lineageos/preference/ConstraintsHelper.java:143: error: package R does not exist
            boolean rOwner = a.getBoolean(R.styleable.lineage_SelfRemovingPreference_requiresOwner, false);
                                           ^
lineage-sdk/sdk/src/java/lineageos/preference/ConstraintsHelper.java:149: error: package R does not exist
            String rPackage = a.getString(R.styleable.lineage_SelfRemovingPreference_requiresPackage);
                                           ^
lineage-sdk/sdk/src/java/lineageos/preference/ConstraintsHelper.java:162: error: package R does not exist
            String rAction = a.getString(R.styleable.lineage_SelfRemovingPreference_requiresAction);
                                          ^
lineage-sdk/sdk/src/java/lineageos/preference/ConstraintsHelper.java:175: error: package R does not exist
            String rFeature = a.getString(R.styleable.lineage_SelfRemovingPreference_requiresFeature);
                                           ^
lineage-sdk/sdk/src/java/lineageos/preference/ConstraintsHelper.java:191: error: package R does not exist
            String rProperty = a.getString(R.styleable.lineage_SelfRemovingPreference_requiresProperty);
                                            ^
lineage-sdk/sdk/src/java/lineageos/preference/ConstraintsHelper.java:211: error: package R does not exist
            TypedValue tv = a.peekValue(R.styleable.lineage_SelfRemovingPreference_requiresConfig);
                                         ^
lineage-sdk/sdk/src/java/lineageos/preference/ConstraintsHelper.java:220: error: package R does not exist
                            R.styleable.lineage_SelfRemovingPreference_requiresConfigMask, -1);
                             ^
lineage-sdk/sdk/src/java/lineageos/preference/RemotePreferenceManager.java:104: error: package Manifest does not exist
                                Manifest.permission.MANAGE_REMOTE_PREFERENCES, mHandler);
                                        ^
lineage-sdk/sdk/src/java/lineageos/preference/RemotePreferenceManager.java:135: error: package Manifest does not exist
                    Manifest.permission.MANAGE_REMOTE_PREFERENCES,
                            ^
lineage-sdk/sdk/src/java/lineageos/preference/RemotePreferenceUpdater.java:127: error: package Manifest does not exist
                UserHandle.CURRENT, Manifest.permission.MANAGE_REMOTE_PREFERENCES);
                                            ^
17 errors
[ 22% 297/1317] Building Kernel

 

[widi aprianto]

ask

build/make/core/base_rules.mk:412: warning: ignoring old commands for target `/home/wufix/android/system/out/target/product/vince/vendor/lib64/camera.device@1.0-impl.so'
build/make/core/Makefile:28: warning: overriding commands for target `/home/wufix/android/system/out/target/product/vince/vendor/lib64/camera.device@3.2-impl.so'
build/make/core/base_rules.mk:412: warning: ignoring old commands for target `/home/wufix/android/system/out/target/product/vince/vendor/lib64/camera.device@3.2-impl.so'
build/make/core/Makefile:28: warning: overriding commands for target `/home/wufix/android/system/out/target/product/vince/vendor/lib64/camera.device@3.3-impl.so'
build/make/core/base_rules.mk:412: warning: ignoring old commands for target `/home/wufix/android/system/out/target/product/vince/vendor/lib64/camera.device@3.3-impl.so'
build/make/core/Makefile:28: warning: overriding commands for target `/home/wufix/android/system/out/target/product/vince/vendor/lib64/hw/android.hardware.camera.provider@2.4-impl.so'
build/make/core/base_rules.mk:412: warning: ignoring old commands for target `/home/wufix/android/system/out/target/product/vince/vendor/lib64/hw/android.hardware.camera.provider@2.4-impl.so'
build/make/core/Makefile:28: warning: overriding commands for target `/home/wufix/android/system/out/target/product/vince/vendor/lib64/hw/consumerir.default.so'
build/make/core/base_rules.mk:412: warning: ignoring old commands for target `/home/wufix/android/system/out/target/product/vince/vendor/lib64/hw/consumerir.default.so'
build/make/core/Makefile:28: warning: overriding commands for target `/home/wufix/android/system/out/target/product/vince/vendor/lib64/hw/fingerprint.default.so'
build/make/core/base_rules.mk:412: warning: ignoring old commands for target `/home/wufix/android/system/out/target/product/vince/vendor/lib64/hw/fingerprint.default.so'
ninja: error: '/home/wufix/android/system/out/target/common/obj/JAVA_LIBRARIES/WfdCommon_intermediates/javalib.jar', needed by '/home/wufix/android/system/out/target/product/vince/dex_bootjars/system/framework/boot.prof', missing and no known rule to make it
09:06:17 ninja failed with: exit status 1

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

get error like this when build lineage os 16, whats wrong?