yashsingh1/xdaforums huggingface dataset:
[Android General] Einfach_Yannic:
Einfach_Yannic,

I say this with the utmost of respect and kindness. I am not at your beckon call, I have a wife, three children, and a job. I cannot drop everything to help you with a one on one chat. ;)

Building a device from scratch is hard. I recommend that you watch ALL of my videos so that you will learn how things work. I then recommend that you build for at least one device that has already been built before, even if only the generic and run it in the emulator. Then after you have that valuable experience under your belt, then you can attempt to build a device from scratch. It takes a lot of knowledge, a lot of time, a lot of patience, and a lot of trial and error. It took me almost 5 years to get to this point, and you cannot learn it all in one day. I am doing the best that I can to help the many new builders here by making these video guides and answering questions here, in hopes that in 6 months to a year, you might be better at this than me, but it will take effort on your part. :laugh:

As for the errors with repo sync, what exactly did the errors say. We can help you here, but you have to post the exact errors for us so that we can point you in the right direction. :good:[/QUOTE]

OK,sorry that i requested so much from you,maybe tommorow i will try the repo synch stuff again,i'm sry but i can't built a Rom for a device that other people built for in the past because this phone (huawei p8 lite smart) is my only phone.

Today (or tommorow[when i have time]) i will watch some more videos on your channel so i might can help out my self.
[Android General] zelendel:
OK,sorry that i requested so much from you,maybe tommorow i will try the repo synch stuff again,i'm sry but i can't built a Rom for a device that other people built for in the past because this phone (huawei p8 lite smart) is my only phone.

Today (or tommorow[when i have time]) i will watch some more videos on your channel so i might can help out my self.[/QUOTE]

To be honest you most likely should have watched his videos before you even started. Let alone for a device that is a nightmare to work with. Now with the Xmas season in full swing in the states I would say to watch the videos and spend the next week reading up. You will need it. Also because of the device you are using. Make sure to bone up on your Chinese.
[Android General] MrRob0t:
gahh, you're too kind. Things like what key words to search for in output are invaluable. I know a little bit of smali, so java looks, somewhat familiar but I'm very lost. Like with anything the little about smali i do know really took a lot of trial and error, but so many times I'd run into something I didn't know how to do and had to stop because I just couldn't figure it out and back then there weren't any guides (haven't looked about time recent), esp nothing like this!

Ok, so I have just a really strange question. So I first downloaded Lineage source, as I deleted it for space, and ends up that downloadprovider folder was the exact same except for Index in .git folder. I tried with it anyway, but no go.Tested that Lineage built again, and it did. So I downloaded Res Remix N source as it was the other ROM I had built. Same folder, same index file only difference again. However RR ALSO didn't build and gave the same error, as I kind of expected at this point, lol.

So I have a build from crdroid as recent as 11/26 i think, recent though. would anything in that rom be of help. I know there is a DownloadProvider.apk

I am really quite baffled to be honest. The last thing I am going to do is trying the reference flag, repo init --reference=~/android/lineage -u https://github.com/crdroidandroid/android -b 7.1. This was my setup before on ubuntu 16.04 and since I already had lineage downloaded. (I know I didn't have to delete that file, and am pretty sure it will result in some issue once booted, pertaining to downloading, but could be wrong. I'll keep playing with it, although java is just a blur pretty much right now. I actually just picked up "Java Programming 8th edition" 2 days ago, so I'll be reading that, and hoping I can get through it!) I don't think it will build, but will see. What's very strange is no edits, that i can see have been made to either rom for nougat for awhile now, and hard to believe they'd leave it non-working like that, esp both roms?

Thank you!

edit: reference flag, same error. :crying::confused:

in the meantime, let's try AICP. :)

I think i'd give up without you. not that I expect you to keep spoon feeding me in a sense, it's just so great to have someone who can help me save a lot of head banging. So, please, take your time with responding. Enjoy Christmas! (if you celebrate it), regardless, enjoy some family time!
[Android General] Einfach_Yannic:
[IMG="Ez"]https://photos.app.goo.gl/wAUp7DZ55kjvWZgm9[/IMG]
[Android General] zelendel:
Sure you may think so but keep in mind that the best developers on this site who were given free devices from this OEM refused to work on it due to how much of the kernel code is in chinese and cant really be translated.
[Android General] rajesh@xda:
Thank you:highfive: Merry christmas .
[Android General] MrRob0t:
That's too cool! I checked out on google and that has to be really fun for the whole family! esp the kids, :D

Merry Christmas, ALL!
[Android General] DJABHipHop:
What does this mean, I've google it but no answer?

12-23 17:19:04.724 579 759 E Sensors : Accelerometer: unknown code (code=7)
12-23 17:19:04.724 579 759 E Sensors : Accelerometer: unknown code (code=9)
12-23 17:19:04.791 579 759 E Sensors : Accelerometer: unknown code (code=7)
12-23 17:19:04.791 579 759 E Sensors : Accelerometer: unknown code (code=9)
12-23 17:19:04.857 579 759 E Sensors : Accelerometer: unknown code (code=7)
12-23 17:19:04.857 579 759 E Sensors : Accelerometer: unknown code (code=9)
12-23 17:19:04.924 579 759 E Sensors : Accelerometer: unknown code (code=7)
12-23 17:19:04.924 579 759 E Sensors : Accelerometer: unknown code (code=9)
12-23 17:19:04.991 579 759 E Sensors : Accelerometer: unknown code (code=7)
12-23 17:19:04.991 579 759 E Sensors : Accelerometer: unknown code (code=9)
12-23 17:19:05.057 579 759 E Sensors : Accelerometer: unknown code (code=7)
12-23 17:19:05.057 579 759 E Sensors : Accelerometer: unknown code (code=9)
12-23 17:19:05.124 579 759 E Sensors : Accelerometer: unknown code (code=7)
12-23 17:19:05.124 579 759 E Sensors : Accelerometer: unknown code (code=9)
12-23 17:19:05.191 579 759 E Sensors : Accelerometer: unknown code (code=7)
12-23 17:19:05.191 579 759 E Sensors : Accelerometer: unknown code (code=9)
12-23 17:19:05.257 579 759 E Sensors : Accelerometer: unknown code (code=7)
12-23 17:19:05.258 579 759 E Sensors : Accelerometer: unknown code (code=9)
12-23 17:19:05.324 579 759 E Sensors : Accelerometer: unknown code (code=7)
12-23 17:19:05.324 579 759 E Sensors : Accelerometer: unknown code (code=9)
12-23 17:19:05.391 579 759 E Sensors : Accelerometer: unknown code (code=7)
12-23 17:19:05.391 579 759 E Sensors : Accelerometer: unknown code (code=9)
12-23 17:19:05.458 579 759 E Sensors : Accelerometer: unknown code (code=7)
12-23 17:19:05.458 579 759 E Sensors : Accelerometer: unknown code (code=9)
12-23 17:19:05.524 579 759 E Sensors : Accelerometer: unknown code (code=7)
12-23 17:19:05.524 579 759 E Sensors : Accelerometer: unknown code (code=9)
12-23 17:19:05.591 579 759 E Sensors : Accelerometer: unknown code (code=7)
12-23 17:19:05.591 579 759 E Sensors : Accelerometer: unknown code (code=9)
12-23 17:19:05.657 579 759 E Sensors : Accelerometer: unknown code (code=7)
12-23 17:19:05.657 579 759 E Sensors : Accelerometer: unknown code (code=9)
[Android General] krishV:
auto booting while setuping

sir i have sucessfully booted but at some time while setuping it auto booting

View attachment logcat.zip

please can you tell where i did wrong sir:(
[Android General] MrRob0t:
[MENTION=7026648]AlaskaLinuxUser[/MENTION] I've learned more from your videos and your help than I had in months.

Thank you so much my friend!

I found this:

https://github.com/LineageOS/androi...mmit/715c24acbe82ab1cc0dfe6be60dd0487d111dc46

and edited: DownloadManager.java, SearchViewUiTest.java, DirectoryListBot.java, SQLiteQueryBuilder.java, SQLiteDatabase.java

Now I have a build of Nougat crdroid, res remix and aicp!!

Going to try N Omni, then it's on to either O or P.

but not gunna bite off more than I can chew.

:highfive:
[Android General] fugee279:
I'm just trying to build TWRP so I can root I don't wanna install any custom roms
[Android General] rohitsinha12:
error:https://del.dog/owezirogac.sql

Rom Source : https://github.com/Havoc-OS

device tree : https://github.com/dev-harsh1998/android_device_lenovo_a6000

kernel source : https://github.com/dev-harsh1998/android_kernel_lenovo_msm8916

vendor : https://github.com/dev-harsh1998/proprietary_vendor_lenovo

Fixed other bugs related to HALs

tried different HALs but can't get solution for this

[MENTION=7026648]AlaskaLinuxUser[/MENTION] AKLU plz take a look
[Android General] mssadewa:
Thank you!

Will try it, as soon!! :D
[Android General] DJABHipHop:
How would one deal with a delay wifi connection in a custom rom on boot or after reboot or is that just normal?
[Android General] atttoush:
[MENTION=7026648]AlaskaLinuxUser[/MENTION] Thanks a lot for your series! I'm still watching them but I have few questions.

1. When I want to build TWRP, which device tree should I choose? For my device dipper, it's not included in the omni repository, but there are ROMs for the device and device tree. How can I know which version of the device tree should I choose? (Some device tree from roms with Lineage some with PixelExperience).

2. And would the device tree for Pie be different for Oreo, and would that matter for building TWRP?
[Android General] Amit Kumar R:
Lineage OS for LS-5502

I have ported a nougat ROM for my LYF WIND 3 from LYF WIND 1

Both have same specs except the screen size mine one is 5'5 but the LYF WIND 1 has 5'0.

The ROM is lineage 14.1.

It starts with its boot animation and after completing the boot animation it reboots.this process is going on and on.

Edit: mine LYF WIND 3 as well as LYF WIND 1 has the same Android lollipop 5.1.1.

I'm trying to port a nougat based ROM for my LYF WIND 3.

Can you please tell me what's is the problem?

I'm trying on my own for around a month.

Please help me to port the nougat ROM.

Please please please please please please please please please please please please please please!
[Android General] lightwars:
See if you can get a logcat via ADB and post it via a service like hastebin or so...

It would be good to look the Video about tombstones, get them and look for missing libs or bins. Show them also, if you want to get help.
[Android General] lucki1000:
Hello Amit Kumar R,

Do you have ported the boot.img too?

And which guide have you used to port?
[Android General] Amit Kumar R:
Lineage OS for LS-5502

Thanks for reply!

But whenever I try to port boot.img goes to bootloop,boots to recovery,or remains at the splash screen.

But when I didn't port the boot.img it shows the boot animation which I think is not related to boot.img

Since the bother phone LYF WIND 3 and LYF WIND 1 have the same Android version and also the same chipset and most importantly the same partitions.

So I thought it to be waste of time by trying to port boot.img.

Moreover I'm trying for about a month and hadn't any success.

I used some of the porting tutorials on the XDA site and some experience of mine from past

I'm not very specific about the tutorial.

Here is the video where I got the port ROM

https://youtu.be/zdVcPSANIrQ

And:----->

https://youtu.be/rhiXQyegryA

Thanks!
[Android General] AlaskaLinuxUser:
Typically, this means that there is a sensor for which it does not know what it is. E.g., like an acceleraometer, but it doesn't know what drivers make it work, or what model it is, etc..... I'd look at your accelerometer source code (if from source) and see if there is anything you could change. If you have upgraded from one version of Android to another, the old style of comms for the accel may not be right for the version on which you are running now. Or if the accelerometer is run from a proprietary blob, see if you can find an up to date one from another similar phone.

Great question. I have looked at the log and I see a (if not the) problem. But I want to help you best, not by giving you the answer, but by asking a question:

Have you searched your log for the key words "failed" "error" and "crash"? Notice that when the phone bootloops, you get this phrase in your logs: "beginning of crash". What do you see?

Great work! This is what these videos are for! Bravo! :highfive:

Starting next week, I will be releasing a video series about building TWRP device trees from scratch. I recommend that you watch my other videos about building TWRP to get familiar with the process, and perhaps even build for a device you don't have so you can see the process. Then, watch my new video series and do likewise. :good:

Okay, I see exactly what is wrong here. But I want to help you learn. So, what is the error your log tells you? If it says that it is missing, where could you get it?

What do the logs say? Are there WiFi errors or warnings that are slowing it down?

Usually, just search the name of your device like this:

Google/DuckDuckGo/Other search engine: github device_brand_codename TWRP

First try brought up this tree:

https://github.com/geoleonsh/android_device_xiaomi_dipper

Hope that helps! :good:

[MENTION=3076261]lightwars[/MENTION] and [MENTION=8438555]lucki1000[/MENTION] have some good points. Without logs, we cannot help you. I am not omniscient, so I can't know what is causing your phone to reboot without logs! :laugh:

Another question, when you say port, do you mean porting an already built rom, or did you edit the device tree and compile it? Not to be rude, but this thread is about compiling, not porting. You are welcome to talk about porting here, but I will not be able to help you much with that.

Thanks guys for chiming in! I highly encourage everyone on this thread to try to answer other's questions if you have ideas of what they could do! That's what makes XDA a community! :good: :highfive:
[Android General] lucki1000:
You have only install this rom for wind 1 on your wind 3 or?

But I think this going on, because you ported your bootimg not if you have a bootloop I have used this tip in the past: https://xdaforums.com/chef-central/android/guide-how-to-fix-bugs-bootloop-ported-t3310214/page1

By me not worked with all ported roms, but you can try it.

---------- Post added at 04:37 PM ---------- Previous post was at 03:58 PM ----------

@AlaskaLinuxUser

I need your help, when i'm tried to build pixel experience (aosp) I have download the source code of pixel exp. (oreo) and copied the vendor tree, kernel and device tree, and i have created an pixel manifest xml and now after successfullylunch aosp_cedric, I typed make -j2 and it give's me this failure:

lucki1000@PC:/aosp$make
build/core/product_config.mk:256: *** No matches for product "aosp_arm". Schluss.
21:12:24 Error dumping make vars: exit status 2

#### failed to build some targets (2 seconds) ####
[Android General] AlaskaLinuxUser:
I don't think what you think is happening is actually taking place. Try this:

$ . build/envsetup.sh && lunch aosp_cedric-eng && make -j2
[Android General] lucki1000:
Thanks it worked.

and now i get after 1:46 minutes compile this error:

[500/1075] including ./hardware/qcom/thermal/Android.mk ...
build/core/base_rules.mk:238: error: hardware/qcom/thermal: MODULE.TARGET.SHARED_LIBRARIES.thermal.msm8937 already defined by device/motorola/cedric/thermal.
17:10:18 ckati failed with: exit status 1
[Android General] rohitsinha12:
[MENTION=7026648]AlaskaLinuxUser[/MENTION] By seeing the error I understood that it is missing a shared library LibqdMetaData and I know some HALs which I have not tried yet but I think I should clone display-caf and media-caf which is suitable for my phone and i have to sync -caf branch bcz my device uses -caf and camera HAL is already present in my device tree .

Thanks for suggesting

---------- Post added at 07:25 PM ---------- Previous post was at 07:21 PM ----------

Delete the thermal folder from either your device tree or hardware bcz it is already defined in two places .so,you should remove one of them.I prefer you should delete it from your device tree
[Android General] lucki1000:
Thanks,

And now i get this failure:

/media/lucki1000/lucki1000/AndroidSource/aosp/prebuilts/gcc/linux-x86/a64/a64-linaro-7.2/bin/a64-linux-gnu-gcc: No such file or directory
/media/lucki1000/lucki1000/AndroidSource/aosp/kernel/motorola/msm8937/scripts/Makefile.build:257: recipe for target 'scripts/mod/empty.o' failed
/media/lucki1000/lucki1000/AndroidSource/aosp/kernel/motorola/msm8937/scripts/Makefile.build:402: recipe for target 'scripts/mod' failed
/media/lucki1000/lucki1000/AndroidSource/aosp/kernel/motorola/msm8937/Makefile:564: recipe for target 'scripts' failed
Makefile:150: recipe for target 'sub-make' failed
ninja: build stopped: subcommand failed.
21:08:27 ninja failed with: exit status 1

Have I forgot anything to download with the sourcecode? or why files missing?
[Android General] rohitsinha12:
You don't have gcc

Your error:

/media/lucki1000/lucki1000/AndroidSource/aosp/prebuilts/gcc/linux-x86/a64/a64-linaro-7.2/bin/a64-linux-gnu-gcc: No such file or directory
[Android General] lucki1000:
How can I install them?

My Ubuntu has gcc.
[Android General] AlaskaLinuxUser:
More specifically, you have gcc, and in your android source folder is a prebuilt folder with gcc in it. However, your device tree is requesting a custom toolchain, called linaro. You need to web search the linaro tool chain and install it. Here is an older video I made about tool chains:

https://www.youtube.com/watch?v=Z4ghGQ398rM&t=0s&list=PLRJ9-cX1yE1l6eu-vkgsj61U-Zv3fjzwZ&index=15
[Android General] DJABHipHop:
how would make a rom's selinux permissive not just on boot
[Android General] beast97:
what are the files to be compared when comparing two different device tree??
[Android General] rohitsinha12:
In your device tree ,there should be a file named BoardConfig.mk .inside that there should be a line like this

KERNEL_TOOLCHAIN := /media/lucki1000/lucki1000/AndroidSource/aosp/prebuilts/gcc/linux-x86/a64/a64-linaro-7.2/bin/a64-linux-gnu-gcc

Change the kernel toolchain location to the location where you have the GCC

OR

Download the GCC which your device tree Needs ,that is linaro 7.2
[Android General] lucki1000:
Can I use linaro 7.3 too?
[Android General] rohitsinha12:
You can try. But don't forget to change the path in BoardConfig.mk
[Android General] lucki1000:
Thanks, it's clear.

---------- Post added at 10:42 AM ---------- Previous post was at 10:18 AM ----------

ninja: no work to do.
ninja: no work to do.
/media/.../AndroidSource/aosp/out/build-aosp_arm.ninja is missing, regenerating...
[675/1075] including ./system/sepolicy/Android.mk ...
./system/sepolicy/Android.mk:99: warning: BOARD_SEPOLICY_VERS not specified, assuming current platform version
[1075/1075] including ./vendor/themes/Android.mk ...
PRODUCT_COPY_FILES device/generic/goldfish/fstab.ranchu:root/fstab.ranchu ignored.
PRODUCT_COPY_FILES device/generic/goldfish/fstab.ranchu.early:root/fstab.ranchu.early ignored.
platform_testing/build/tasks/tests/instrumentation_test_list.mk: warning: continuous_instrumentation_tests: Unknown installed file for module SystemUITests
ninja: error: 'device/generic/goldfish/compatibility_matrix.xml', needed by '/media/.../AndroidSource/aosp/out/target/product/generic/gen/ETC/compatibility_matrix.xml_intermediates/compatibility_matrix.xml', missing and no known rule to make it
11:37:42 ninja failed with: exit status 1
build/core/main.mk:21: recipe for target 'run_soong_ui' failed

how I get or generate compatibility_matrix.xml?
[Android General] AlaskaLinuxUser:
From a terminal on the phone, or ADB, you can set it to permissive with this:

# setenforce 0

Or to enforcing with this:

# setenforce 1

Notice that you need root or super user permission to do this.... :good:

All of them. :laugh:

[MENTION=8680598]rohitsinha12[/MENTION] is right. You can try a different linaro version, but be careful, custom tool chains often require custom editing to your kernel source. It would be better for you to stick with what you know they used, since it should work. Then, when you get more experience, you can try other tool chains. :cowboy:

Lucki,

Every time, you need to specify what you want to build. You keep typing make or something without choosing to build your device, so it is trying to build generic (goldfish). You need to run this command so you can build your device:

$ . build/envsetup.sh && lunch aosp_cedric-eng && make -j2

If need be, run it every time to make sure you are building for your device, not the generic one. :good:
[Android General] lucki1000:
I still get an error:

Lex: applypatch <= bootable/recovery/edify/lexer.ll
flex-2.5.39: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
/bin/bash: Zeile 1: 13407 abort (memory deduction)
make[1]: Verzeichnis „/media/.../AndroidSource/aosp/out/target/product/cedric/obj/KERNEL_OBJ“ wird verlassen
make: Verzeichnis „/media/.../AndroidSource/aosp/kernel/motorola/msm8937“ wird verlassen
make: Verzeichnis „/media/.../AndroidSource/aosp/kernel/motorola/msm8937“ wird betreten
make[1]: Verzeichnis „/media/.../AndroidSource/aosp/out/target/product/cedric/obj/KERNEL_OBJ“ wird betreten
GEN ./Makefile
scripts/kconfig/conf --savedefconfig=defconfig Kconfig
drivers/soc/qcom/Kconfig:380:warning: choice value used outside its choice group
drivers/soc/qcom/Kconfig:385:warning: choice value used outside its choice group
warning: (SND_SOC_APQ8084 && SND_SOC_MSM8994 && SND_SOC_MSM8996 && SND_SOC_MSM8X16 && SND_SOC_MDM9607 && SND_SOC_MDM9640) selects SND_SOC_WCD9330 which has unmet direct dependencies (SOUND && !M68K && !UML && SND && SND_SOC && WCD9330_CODEC)
warning: (SND_SOC_APQ8084 && SND_SOC_MSM8994 && SND_SOC_MSM8996 && SND_SOC_MSM8X16 && SND_SOC_MDM9607 && SND_SOC_MDM9640) selects SND_SOC_WCD9330 which has unmet direct dependencies (SOUND && !M68K && !UML && SND && SND_SOC && WCD9330_CODEC)
make[1]: Verzeichnis „/media/.../AndroidSource/aosp/out/target/product/cedric/obj/KERNEL_OBJ“ wird verlassen
make: Verzeichnis „/media/.../AndroidSource/aosp/kernel/motorola/msm8937“ wird verlassen
ninja: build stopped: subcommand failed.
17:52:24 ninja failed with: exit status 1

#### failed to build some targets (02:53 (mm:ss)) ####

sorry if I spaming with errors.
[Android General] DJABHipHop:
Try this and see if it helps export LC_ALL=C or add it to you .bashrc file if you don't want to type it every time you want build.