yashsingh1/xdaforums huggingface dataset:
[Android General] Rawwrius01:
[MENTION=7026648]AlaskaLinuxUser[/MENTION] thanks for the reply. I can change the settings for other modules from build in to module except the qualcom wifi. I will try the dmesg txt. Sadly i wasnt able to find the firmware.

[MENTION=8017005]srgrusso[/MENTION] can i use this kernel source to build for my device ? i Thought there weren't all files included I need for my device? I use the stock defconfig which comes with the source. in system/lib/modules is the only ko file the ansi_cprng.ko even with the stock kernel. i can find the qca_cld_wlan.ko in system/sbin/.core/mirror/system/lib/modules but i tried to backup them and place em back after flashing my kernel it no luck.

Okay. i used valeras source Compile and flash the kernel. Same as before but this time i put the old wifi.ko modules (qca_cld_wlan.ko and wifi.ko) in system/lib/modules and insmod them. Checking with lsmod show that i can load the qca module but wifi still stuck at turning on.
[Android General] IvanHephaestus:
Thank you bro, you helped a lot of people and I want you to help me. Few days ago google released android Pie sources I want to build aosp 9.0 and I have device tree for oreo, how to upgrade my device tree to boot on newer version of android. I think that video of such instructions will be very helpful for many people.
[Android General] AlaskaLinuxUser:
Great question!

That would fall under "advanced" topics. This series only covers basic to intermediate material. I do have a more advanced series and thread (link in op). Currently it is under development, so the only thing in it right now is building a device from scratch. Once I'm done with that, I plan on adding to that with how to upgrade from one version to another.

So yes, great idea, and it is in the works. ;)
[Android General] manushamil:
Okay thanks for the help :D
[Android General] rajesh@xda:
Yeah I got my bluetooth error fixed to some extent. I missed some library files.

Have a look at this for addressing selinux denials. I have asked this doubt here few month ago.!

https://gist.github.com/MSF-Jarvis/ec52b48eb2df1688b7cbe32bcd39ee5f

Need some more clarification

:good:
[Android General] AlaskaLinuxUser:
Sounds like a file system loading issue, does your fstab have all of the right drives? (compared with stock fstab?) Does adb work during this hanging process?
[Android General] Akhil Vijayan:
It would be very nice if you can make a video on building Paranoid Android ROM. :)
[Android General] psychem:
after downloading fresh source and rebuilding got this error

[4/153] including bootable/recovery/Android.mk ...
/bin/bash: line 0: test: -ge: unary operator expected
/bin/bash: line 0: test: -ge: unary operator expected
[133/153] including system/core/Android.mk ...
sed: can't read development/sdk/plat_tools_source.prop_template: No such file or directory
sed: can't read development/sdk/plat_tools_source.prop_template: No such file or directory
build/make/core/base_rules.mk:260: error: system/core/toolbox: MODULE.TARGET.EXECUTABLES.toolbox_recovery already defined by system/core/toolbox.
23:21:52 ckati failed with: exit status 1

#### failed to build some targets (21 seconds) ####
[Android General] AlaskaLinuxUser:
Yes, so it is calling for the onyx/root/init.recovery.*.rc files, but cannot find them. Do you have any in your device tree folder? :confused:

So this file: hardware/qcom/data/ipacfg-mgr/msm8998/ipanat/src/../inc/ipa_nat_drvi.h, line 38, space 10, calls for this file: 'linux/msm_ipa.h' but cannot find it.

So you could search to find it, and then put the full path in this file to make sure it can find it. Does this file exist when you search your source folder? :confused:

I'll keep that on the back-burner for when I'm done with these other series. :good:

Ah, so this is a tough one. This says that MODULE.TARGET.EXECUTABLES.toolbox_recovery is esentially declared twice. So in system/core/toolbox, it already tells the build machine how to make MODULE.TARGET.EXECUTABLES.toolbox_recovery, but somewhere in your device trees, you are telling it how to make it again. You need to search your device folder files for lines about this and remove the offender. You can only declare something once, otherwise it is confused on which one to use. :good:
[Android General] AlaskaLinuxUser:
For the group, a note that I wrote on the YouTube channel, in case you didn't see it:

Some new videos on GitLab include the LG Urbane smartwatch, developing, unlocking, flashing TWRP, building TWRP, and stopping OTA updates, all of which I recommend you check out, or you can wait for them to appear on YouTube later this month, while I'm gone will be more of the BLU Life XL upgrade series, so hopefully you are all enjoying that! :cool:
[Android General] Rohit Shelke:
https://del.dog/obafiyilug

Can you help me this error please
[Android General] Warrior1988:
Razer has released the Kernel source for Razer phone 2 on their site. Could we use that to build twrp for android 8.1? The recovery is built in the boot.img device is a/b partition.
[Android General] Nathan Miguel:
device error not found in the breakfast command.

I'm the guy that asked the question in your last video on youtube, I'll explain step by step what's happening.

1. I followed your tutorial step by step to where you teach how to add a device with the "breakfast" command, but in the huson branch of the OS lineage was not showing my "LENOVO A6020" device. I tried the version of the branch cm14.1 (this version already had official support for my device) and lineage 16.

2. Now I'm trying with the pixel expirience, in the PIE version, and it gave the same error as in the branch lineage not to be found.
[Android General] Nathan Miguel:
I'm having difficulty compiling the custom rom for my Vibe k5 plus "Lenovo A6020"

1. I started with lineage, first with cm14.1, which was where my device had an official compilation and then it was with lineage 16, but I realized that in the hudson branch (lineage) my device was not listed.

2. Then I tried with the pix expirience pixel "pie" but I noticed that I also had the same error when adding my device.

NOTE: I followed your tutorial to add the device with the "breakfast" command and in this part it appears that the android.mk of the device was not found and that neither github synchronizes the device
[Android General] AlaskaLinuxUser:
Does the 14.1 mb version work when you flash it? It will not be TWRP, but rather just CM/Lineage recovery, but does it work when you flash it? If it does then that narrows your problems down a bit. Because if it works, you could download the proper TWRP bootable/recovery folder and put it in your Lineage tree, and just build it there. :cowboy:

So, when we search logs for problems, we always look for "failed" and "error". Your issue is an sepolicy problem. You need to look in your sepolicy files and search for this line:

u:object_r:adsprpc_prop:s0

and when you find it, either delete it or change it so it works. If you set selinux to permissive, you can delete it for now and come back to it later to work on. The issue is that "type adsprpc_prop is not defined", so to fix that, you need to define it. Or remove it for now and come back to it later. :good:

You certainly could. I recommend the video series on building a TWRP tree from scratch. :cool:

Can you give me the step by step of what you typed? I just want to make sure that I understand fully exactly where you are. Also, please site which specific video you are watching. (I have several :D ) Did you add your device to the manifest, like in this video: https://www.youtube.com/watch?v=qZzA4Au4Q2o&list=PLRJ9-cX1yE1m8k9gztsQnnXDg1G4X1f6z&index=9

Sometimes, you can just type breakfast, and it will download it for you. If not, you need to add it to the manifest. Hope that helps! :fingers-crossed:
[Android General] Rohit Shelke:
Thank you very much for the reply, I'm grateful.:svetius:
[Android General] leqacy:
Thanks for your quick reply! Putting the full path in the file worked and the build completed. However, it does not seem like good practice to edit the include in this way, as paths may be different on other machines. So it would become a problem when sharing sources with others and probably while updating sources/rebasing as well.

What would be a better way to configure the include paths? I already tried CFLAGS oder editing make files, but probably didn't hit the right one.

The path is the following: $working_dir/android/lineage/kernel/google/wahoo/include/uapi/linux

Also, I flashed the zip and the LineageOS logo appears on boot. After around 10 minutes the phone reboots and a menu comes up that says the data may be corrupt, Try again or factory reset. Not sure how to proceed from here without any logs.
[Android General] AlaskaLinuxUser:
Great questions. Is this the first stock rom you put on this phone? Sometimes the data may need to be formatted in TWRP prior to rom flashing, if the encryption is enabled and the rom/kernel doesn't support it. Often this is one of those first time things one must do after moving from stock.

As for logs, you can do two things:

#1. After the reboot, go straight into twrp and look at /data/tombstones or cat /sys/fs/pstore/console-ramoops or cat /proc/last_kmesg for old logs from the previous boot.

#2. You can follow my video where in TWRP I add the options for ADB to work in the rom, then reboot to rom and pull logs while booting.

https://www.youtube.com/watch?v=E7evKGTgLk4&index=5&list=PLRJ9-cX1yE1lQwh_NHLAzcZsW5lMerXby

Or this whole playlist is good for your needs:

https://www.youtube.com/watch?v=wHTPymSwv2E&list=PLRJ9-cX1yE1lQwh_NHLAzcZsW5lMerXby
[Android General] AlaskaLinuxUser:
You are making good progress. :highfive:

Glad to hear formatting did cure the previous error.

Now, as for your logs.... I would need more logs to help you. Can you post all of it on pastebin, or as an attachment here?
[Android General] leqacy:
Of course. Here is the logcat, the file was bigger, but cannot upload more than 512kb. Also, a lot of the messages later in the file looked repetitive:

https://vomitb.in/4CXK80HeaR

Looks like I may need to do something like this:

https://source.android.com/devices/tech/config/perms-whitelist

Edit: Yep, I set ro.control_privapp_permissions=log (from enforce) and the boot completed!!!
[Android General] AlaskaLinuxUser:
Well done! :highfive:
[Android General] Nathan Miguel:
was in this video, but I also do not find the dependencies of the k5 vibe to manually add
[Android General] AlaskaLinuxUser:
Here is the official guide to build for the k5 vibe:

https://wiki.lineageos.org/devices/A6020/build

Notice that the codename is a6020, so you run breakfast lineage_a6020-eng

But you can check out the guide I linked above for more info. :good:
[Android General] manushamil:
[MENTION=7026648]AlaskaLinuxUser[/MENTION]

I get this error TheMuppets/proprietary_vendor_samsung/tree/cm-14.1 is not a valid repository name

But when i add TheMuppets/proprietary_vendor_samsung it works just fine. I don't wanna sync the whole repo just for a device that i am building for.:crying:
[Android General] raystef66:
[MENTION=7026648]AlaskaLinuxUser[/MENTION] great vids !

Problem though...was building arrow 8.1.0 for a7 and was 6% from end till this : https://del.dog/fixoridoli

Any help would be appreciated ;)
[Android General] leqacy:
It seems like a lot of things are working with the build: camera, wifi, audio etc.

One thing that does not work is mobile data. When navigating to Settings->Network & Internet, after clicking on "Mobile Network" the screen goes blank and the Activity with MobileNetworkSettings does not open.

This is the log after clicking the Mobile Networks Settings:

https://vomitb.in/hufuxbKvf3

I am not sure what exactly is causing the crash. Whether the following warning is a problem or not:

VoiceInteractionManagerService( 1130): no available voice interaction services found for user 0

I also tried finding the tombstones that was written to, but the contents of /system/bin/tombstoned is not humand readable mostly. The other directories mentioned in your videos regarding tombstones are empty, even after rebooting.

Any ideas on how to track this one down? Haven't found anything relevant when searching.

Also right after booting the device I get this stack trace every few seconds:

https://vomitb.in/Id7QKzl8jn

Could be that the origin for both of these errors is the same.

/system/framework/telephony-common.jar and com.qualcomm.ims.vt.LowBatteryHandler do not seem to fit together.

Edit: Fixed. This commit fixes the problem, but is not yet merged.

https://review.lineageos.org/c/Line.../org/codeaurora/ims/utils/QtiImsExtUtils.java
[Android General] psychem:
yes it works fine. you mean losTWRP/bootable/recovery folder needs to replace the /android/lineage/bootable/recovery folder? i tried it and it failed to build.

[267/1031] including frameworks/av/camera/Android.mk ...
frameworks/av/camera/cameraserver/Android.mk:18: warning: Target has integrated cameraserver into mediaserver. This is weakening security measures introduced in 7.0
[617/1031] including system/sepolicy/Android.mk ...
system/sepolicy/Android.mk:88: warning: Be careful when using the SELINUX_IGNORE_NEVERALLOWS flag. It does not work in user builds and using it will not stop you from failing CTS.
[1031/1031] including vendor/qcom/opensource/dataservices/Android.mk ...
build/make/core/base_rules.mk:412: warning: overriding commands for target `/root/android/lineage/out/target/product/onyx/recovery/root/etc/mke2fs.conf'
build/make/core/base_rules.mk:412: warning: ignoring old commands for target `/root/android/lineage/out/target/product/onyx/recovery/root/etc/mke2fs.conf'
build/make/core/base_rules.mk:412: warning: overriding commands for target `/root/android/lineage/out/target/product/onyx/system/xbin/wget'
external/busybox/Android.mk:171: warning: ignoring old commands for target `/root/android/lineage/out/target/product/onyx/system/xbin/wget'
ninja: error: '/root/android/lineage/out/target/product/onyx/system/lib/libclang_rt.ubsan_standalone-aarch64-android.so', needed by '/root/android/lineage/out/target/product/onyx/obj/SHARED_LIBRARIES/libbmlutils_intermediates/teamwin', missing and no known rule to make it
18:47:03 ninja failed with: exit status 1

#### failed to build some targets (56 seconds) ####

root@mx:~/android/lineage#
[Android General] Nathan Miguel:
[MENTION=7026648]AlaskaLinuxUser[/MENTION]

to be more precise I'm getting this error when typing the command

build/make/core/product_config.mk:234: error: Can not locate config makefile for product "a6020".
12:43:32 dumpvars failed with: exit status 1
Device a6020 not found. Attempting to retrieve device repository from PixelExperience-Devices Github (http://github.com/PixelExperience-Devices).
Repository for a6020 not found in the PixelExperience-Devices Github repository list.
If this is in error, you may need to manually add it to your .repo/local_manifests/pixel.xml
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "a6020".
12:43:34 dumpvars failed with: exit status 1
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "a6020".
12:43:35 dumpvars failed with: exit status 1

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

---------- Post added at 02:48 PM ---------- Previous post was at 02:48 PM ----------

[/COLOR [MENTION=7026648]AlaskaLinuxUser[/MENTION]

to be more precise I'm getting this error when typing the command

build/make/core/product_config.mk:234: error: Can not locate config makefile for product "a6020".
12:43:32 dumpvars failed with: exit status 1
Device a6020 not found. Attempting to retrieve device repository from PixelExperience-Devices Github (http://github.com/PixelExperience-Devices).
Repository for a6020 not found in the PixelExperience-Devices Github repository list.
If this is in error, you may need to manually add it to your .repo/local_manifests/pixel.xml
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "a6020".
12:43:34 dumpvars failed with: exit status 1
build/make/core/product_config.mk:234: error: Can not locate config makefile for product "a6020".
12:43:35 dumpvars failed with: exit status 1

** Don't have a product spec for: 'a6020'
** Do you have the right repo manifest?
[Android General] leqacy:
I guess you are referring to the breakfast command?

If you want to build lineageOS for your device you can do the following:

lunch lineage_a6020-userdebug

followed by

mka bacon
[Android General] leqacy:
You need to run

lunch

before you run

mka bacon

in order to set the environment variables required for mka.
[Android General] krishV:
Oh my goodness, Muppets git having all vendors in one folder so you can't download for particular Samsung model

Thank you

KrishV

Best luck ,beautify your build;)

---------- Post added at 06:22 PM ---------- Previous post was at 06:08 PM ----------

For which device are you going to build?

Do you have all device tree, kernel tree and vendor tree?
[Android General] Techguy777:
Hello anyone working on lineage 16 pie? I have tried for the last 5 days or more to build lineage pie for the gts210vewifi its not officially supported yet so im having trouble. I did find a github for all the files vendor, device tree, kernel. Still im getting this error.

/home/thisguy/lineage_pie/out/build-lineage_gts210vewifi.ninja is missing, regenerating...

[113/1114] including device/samsung/msm8976-common/Android.mk ...

build/make/core/binary.mk:1528: error: device/samsung/msm8976-common/recovery/Android.mk: librecovery_updater_samsung: C_INCLUDES must be under the source or output directories: /edify/include /otautil/include /updater/include.

14:24:40 ckati failed with: exit status 1

#### failed to build some targets (46 seconds) ####

I looked online its something to do with recovery mk file it needed a couple lines added ive done that and redone that still no good I dont get it. Anyone else having trouble?
[Android General] DJABHipHop:
Simple Disable that file know then come back to it later if that's case that you need the file fo the device to work properly
[Android General] manushamil:
Thanks for the reply i guess ill just download the whole repo then.
[Android General] Techguy777:
Thanks I'm going to try that.
[Android General] AlaskaLinuxUser:
Do you have the hardware/qcom/display folder, and the device/qcom/common folders? You need these for those missing dependencies. :good:
[Android General] AlaskaLinuxUser:
Great work! Glad you fixed it! :highfive:

Is this an 8.0 kernel? Has this been built before? Did you make any customization to the kernel? It can't build that module because those things have not been defined. I need a few more details to be more helpful. :good:
[Android General] AlaskaLinuxUser:
Did you follow this guide?

https://wiki.lineageos.org/devices/A6020/build

I ask because none of the commands you are posting look like the commands in this guide, which is a guide specific to build your device. :confused:
[Android General] AlaskaLinuxUser:
Odd, I'll have to think on that one.

By the way, you should not be building as the root user. You should build as a normal user, because of permission issues. Just a tip. :good:
[Android General] krishV:
Sir, actually I have created a ctosp ( https://GitHub.com/ctosp ) ROM based on Pixel experience so in that git it doesn't have device/qcom/common

And if I have allowing missing dependencies true

I getting sap-api-java-static in (JAVA_LIBRARIES android-arm)
[Android General] raystef66:
Thnx for replying.

Based on LOS15.1

https://github.com/LineageOS/android_device_zte_axon7/tree/lineage-15.1

https://github.com/LineageOS/android_kernel_zte_msm8996/tree/lineage-15.1

https://github.com/TheMuppets/proprietary_vendor_zte/tree/lineage-15.1

and arrow 8.1.0 : https://github.com/ArrowOS/android_manifest/tree/arrow-8.x

There are no modifications made. Btw, with these los15.1 trees I succesfully build the crdroid 8.1.0.

In building there was only 1 error in the beginning. Had to remove the Doze folder to continue (as I did on crDroid)

And as mentioned, at 6% from the end I had this problem : https://del.dog/fixoridoli.sql

Compressed the 2 files external/e2fsprogs/misc/mke2fs.c and external/e2fsprogs/lib/support/plausible.c : https://www.sendspace.com/file/ypd66t

Perhaps it has some use.

Hope you can figure out what's wrong :good:
[Android General] Nathan Miguel:
I am synchronizing with Lineage 14.1, which was the only version I found in the branches of my device in Lineage, I will start over again. Already the question of the commands I already tried until of this forum and gave the same error. I wanted to compile direct from Android pie but by the time I realized the vib k5 plus survived support until nogaut, so can you tell me if I have a future upgrade from Lineage 14.1 to 16?
[Android General] AlaskaLinuxUser:
I see, but is there the hardware/qcom/display and display-caf folder? Where these files are built?

Also, you should never use allow missing dependencies unless you are building twrp. It will mean that your build will be missing important things that make it work. You may not notice right away, but it will give you problems in the long run. :good:

OK, so what is wrong is building ext2 tools, the tools used to work with ext2 filesystem's.

Question: does this build in lineage os? On your machine? What is your PC you are building with, operating system, etc.?

Because this is the kind of problem you can get from the wrong GCC, or linker tools. It can also happen when using a different tool chain, which arrow may use rather than lineage.

So, I recommend you build lineage first, if it bulls on your machine, you can rule out your setup. Your setup will be good. Then you can look at the toolchains used. :good:

Or you can disable ext2 support, but that will give you problems later, as ext3 and 4 are likely to be affected.

Or you can fix the links, but I don't think you should have to change anything, as it is likely the tools used, not the source. :fingers-crossed:

Yes, you should follow the guide and build 14.1, then follow my playlist for upgrading android versions. Of you want Oreo or pie, you will have to build it. It will be difficult, but you do have the videos and helpful people on this thread to ask when you have questions. :cowboy:
[Android General] raystef66:
We have had this problem before on 2 different machines. One on Linux Mint, ubuntu 18.04 and 16.04 and another W10 on VM virtualbox running 16.04. In both cases this problems occurs and we have no clue why as we made other builds using the los15.1 trees with the same setup....
[Android General] AlaskaLinuxUser:
Good, so it dies work under what condition? When building lineage, right? And does not work under what conditions? When building something else?

Sounds like a tool chain issue, which is in the prebuilt folder. That's where I would look. :good:
[Android General] anshumanxda:
[CUSTOM ROM PROBLEM]

So I was trying to build on my local machine , and it built successfully but when I flash it , sim never gets detected . Till now I have tried around 4-5 different ROMs , none of them detects sim card but here is the thing , when I compile it through google cloud platform everything works fine . I follow same steps while compling in local machine too. But local machine's build never detects the sim card . I can't have google cloud platform forever so please help
[Android General] anshumanxda:
Sir how to remove apps from source and install our custom apps .

There's ROM name DOTos , it has some gliding problem in keyboard , so is there anyway we could remove that aosp keyboard and put gboard in place of it ?

Thanks already for teaching all this , you really doing a great job .:svetius: