yashsingh1/xdaforums huggingface dataset:
[Android General] omercicek43:
I added my trees manually but don't know how to past this weird problem. I know it's looking for the trees but they're already there.

brunch omni_jason-userdebug
build/core/product_config.mk:227: *** Can not locate config makefile for product "omni_jason". Durdu.
WARNING: Trying to fetch a device that's already there
Traceback (most recent call last):
File "vendor/omni/build/tools/roomservice.py", line 355, in <module>
fetch_device(device)
File "vendor/omni/build/tools/roomservice.py", line 323, in fetch_device
git_data = search_gerrit_for_device(device)
File "vendor/omni/build/tools/roomservice.py", line 81, in search_gerrit_for_device
device_data = check_repo_exists(git_data, device)
File "vendor/omni/build/tools/roomservice.py", line 58, in check_repo_exists
"exiting roomservice".format(device=device))
Exception: jason not found,exiting roomservice
build/core/product_config.mk:227: *** Can not locate config makefile for product "omni_jason". Durdu.

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

No such item in brunch menu. Try 'breakfast'

/ Okay, solved the one above. there was a missing ")" in the omni make file.

But now this came...

[113/965] including ./device/xiaomi/jason/Android.mk ...
build/core/base_rules.mk:238: error: device/xiaomi/jason/init: MODULE.TARGET.SHARED_LIBRARIES.android.hidl.base@1.0 already defined by system/libhidl/transport/base/1.0.
04:18:54 ckati failed with: exit status 1
[Android General] Orbital_Logic:
Are the device trees from specific vendors actually located on the website for AOSP??? Somehow I thought they were proprietary drivers and something that you'd have to get from a TWRP backup or something like that.
[Android General] ankk98:
Great Job !
[Android General] omercicek43:
Sorry I didn't understand your question.
[Android General] Orbital_Logic:
Well, how do get the device tree for your specific device? I have a tab s3 and theres no official aosp rom for it. Do you extract it from a twrp back up? Or are all devices available from the aosp website?
[Android General] omercicek43:
If there isn't a working device tree then you have to make one. Go into AlaskaLinuxUser' YT channel and there you can find it under advanced tutorial playlist.
[Android General] J2A9:
[MENTION=7026648]AlaskaLinuxUser[/MENTION] Hi I am trying to build omni rom 8.1 for POCO F1 using the video tutorial.

But omni rom git up page doesn't have poco f1 (beryllium) device tree.

Also. As this is a new device. Most custom ROMs don't have this poco F1 device tree. In this case what should I do to build any custom ROM for this device

Poco F1 Device Tree ( https://gitlab.com/xiaomi-sdm845 )

Poco F1 Kernel source ( https://t.co/K1rjB83J0Y )

So how do i proceed building now.

i have completed the repo sync and got the source . now due to device tree i am stuck . kindly help

Thanks in advance
[Android General] AlaskaLinuxUser:
Great question. Without looking too deep into it, I can tell you this: When it says "already defined" then your tree and the Android source code (in this case Omni) both specify the same thing. So, look at system/libhidl/transport/base/1.0. and then look at your tree, and take out any duplicates. :good:
[Android General] AlaskaLinuxUser:
Yes, that is correct. :good: And please slap [MENTION=5417180]omercicek43[/MENTION] 's thanks button for taking the time to answer your questions. :good:
[Android General] AlaskaLinuxUser:
It looks like you have everything you need to build LineageOS 15.1, and you would like to build Omni oreo.

If you've never built before, I'd recommend that you start by building LineageOS 15.1 for your device and make sure that you understand the build process and that the sources work good.

Then, you can follow my video tutorials and add your tree to the Omni local manifest, download the material, and edit it to build for Omni instead of Lineage. You will likely have some errors along the way, several of my videos cover various errors, and my website also covers numerous errors that you might encounter.

That's the general idea, but you can get more details from the videos. :good:
[Android General] J2A9:
Great. Thanks for the instant reply sir.

Yes the lineage os is already having the beryllium device tree. i am following your nougat video guide

I have started the repo sync for the same. is there any way to find the ETA for this download or size of the repo sync file.

I am running the repo sync for Los 15.1. can i build Los 16 following the same steps.

which video should i follow for adding device tree to local manifest of a custom rom.

Thanks in advance for this great knowledge sharing you are doing,
[Android General] AlaskaLinuxUser:
As for the size of the downloads, the repository is quite large, about 15-20 GB of space, not counting the device trees, kernels, or vendor files.

Yes, you can follow the same steps for Los 16 as for 15. I have several videos about adding to the local manifests, here are some highlights:

https://www.youtube.com/watch?v=LpzHZVbla4E

https://www.youtube.com/watch?v=wIlsBAb14lQ

https://www.youtube.com/watch?v=qZzA4Au4Q2o

https://www.youtube.com/watch?v=CyTM77AgPNk

Hope that helps!
[Android General] rhutik:
Help please
[Android General] J2A9:
sorry to bother you again.

While i did repo sync for omni rom. there were power failure twice and i used repo sync command to restart the process. is this wrong ? whats the right thing to do when there is interruption during repo sync download. how do we start it again from where it was left. Omni rom repo sync costed 60GB space. is this normal size.

2. oops only folder is created, nothing is inside it in lineage os (https://github.com/LineageOS/android_device_xiaomi_beryllium). what should i do now,

My lineageos repo sync is already past 14gb now.
[Android General] lucki1000:
I have 2 questions:

I will build my own rom this is the right place for it either?

And it is possible to build your own rom without any stock and custom rom for the device?

Thanks for all answers

Regards lucki1000
[Android General] AlaskaLinuxUser:
This is normal. In some of the videos I point out that while it is syncing, no files will show in the main folder. They are temporarily in a hidden folder. Press Ctrl h to see the repo folder, in it is jibberish files that will turn into the files you need when the download is complete.

Also, if you lose connection due to power outages or dropped internet, that is okay, just repo sync again, it will pick up where it left off.
[Android General] AlaskaLinuxUser:
Looks like the files needed as shared libraries are missing. Since they are shared libraries, it can be built without them, but probably will not work.

I recommend that you find those shared libraries on your phone and download them, then add them to the vendor files. :good:

I also recommend in the future that you copy/paste the logs instead of a screenshot. :D
[Android General] rhutik:
Sorry ,

But sir everything is present, the files includes some other folder, instead of my device folder
[Android General] J2A9:
Yes i saw that ctrl h in your videos . my question was not that.

Now i have completed repo sync of los 15.1.

When i run brunch command . my device is not listed.

I am trying to build for XIAOMI POCO F1 ( BERYLLIUM ).

I am stuck here.

Poco F1 Device Tree ( https://gitlab.com/xiaomi-sdm845 )

Poco F1 Kernel source ( https://t.co/K1rjB83J0Y )

So how do i proceed building now.
[Android General] AlaskaLinuxUser:
I think you should check the hardware/qcom folder, does that exist? If so, search in there for the missing libraries, because that is where they are built from. :good:
[Android General] AlaskaLinuxUser:
You bet. So, download your source trees and kernel.

Unzip them if they came zipped.

Make a folder under device called xiaomi, and then put your device tree in it. Rename it something like beryllium. Do the same in the kernel directory, make a folder called xiaomi there, and pit your kernel source in it. Now you can do the same for the vendor files. Then build. :good:
[Android General] AlaskaLinuxUser:
Yes, you came to the right place. I recommend that you watch all the videos before you begin. But it is up to you.

Yes you can build for a device that has never been built before, but it is advanced. I recommend you build a few regular already built devices first, then you should watch my advanced videos for building a device tree from scratch. :good:
[Android General] rhutik:
Sir but why is it including vendor/xiaomi/msm8953-common/android.mk

It should include vendor/xiaomi/mido/android.mk

My device is mido

It requires two trees

Mido and msm8953-common
[Android General] AlaskaLinuxUser:
OK. So here is your problem:

r.cpp"

device/xiaomi/jason/recovery/recovery_updater.cpp:35:10: fatal error: 'edify/expr.h' file not found

#include "edify/expr.h

Be sure to search your logs when you make them, look for failed, error, and fatal. Then use a web search engine to try to figure out what is wrong.

In this case, you r file device/xiaomi/jason/recovery/recovery_updater.cpp on line 35, space 10, is asking to include this file edify/expr.h, but it cannot find it. So you need to find that file and or put it in the right place so you can continue. :good:
[Android General] AlaskaLinuxUser:
Great question!

Because your phone has a msm8953 chip in it:

https://m.gsmarena.com/xiaomi_redmi_note_4-8531.php

So all xiaomi phones with that chip share some common files, so it gets them from the common tree.
[Android General] rhutik:
Thanks sir

Sir sir it should include mido folder from vendor thn msm8953-common

Right?
[Android General] lucki1000:
Thanks for the answer, I don't have any other devices but I watch all your Videos (If I have time) :good:
[Android General] J2A9:
Sir, I made a folder xiaomi in device, kernel, & Vendor.

Inside device folder i placed 2 folders. beryllium and sdm845-common

Inside kernel and vendor placed the respective folders and renamed it to beryllium.

Now when i run the command : brunch beryllium.

I get the following error.

janardhanan@moi:~/lineageos_o$ brunch beryllium

including vendor/lineage/vendorsetup.sh

Command 'make' not found, but can be installed with:

sudo apt install make

sudo apt install make-guile

Device beryllium not found. Attempting to retrieve device repository from LineageOS Github (http://github.com/LineageOS).

Found repository: android_device_xiaomi_beryllium

Default revision: lineage-15.1

Checking branch info

Default revision lineage-15.1 not found in android_device_xiaomi_beryllium. Bailing.

Branches found:

Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.

Command 'make' not found, but can be installed with:

sudo apt install make

sudo apt install make-guile

Command 'make' not found, but can be installed with:

sudo apt install make

sudo apt install make-guile

** Don't have a product spec for: 'lineage_beryllium'

** Do you have the right repo manifest?

No such item in brunch menu. Try 'breakfast'

janardhanan@moi:~/lineageos_o$
[Android General] AlaskaLinuxUser:
It depends. Typically, the developer who built the tree will link to the appropriate files. So, if this has been built before, I would recommend you let it build as it is. It may be that there is a call to those vendor files later in the build process, or it may be that for the version of Android that you are building, they only used the common tree, and not the specific tree. Not all files are always needed, depending on the build. It may be the mido vendor tree is specifically used in say, omni, but not lineage, so it depends.

You can always build for the emulator with the generic arm version. I have several videos on that. :D It will help you understand what a build looks like and how it works. :good:
[Android General] AlaskaLinuxUser:
janajackie, you need to go back to the videos and what setting up your build environment. You forgot to install the tools needed for building, such as "make". :good:

https://www.youtube.com/watch?v=QRjeJqVxw_s&list=PLRJ9-cX1yE1m8k9gztsQnnXDg1G4X1f6z

https://www.youtube.com/watch?v=_OXI2N62Atk&index=8&list=PLRJ9-cX1yE1m8k9gztsQnnXDg1G4X1f6z
[Android General] AlaskaLinuxUser:
Hey everybody!

New HD videos are out and posted to the OP. These videos re-cover the old non-HD video series on using GitHub as well as add GitLab, from the command line to the web interface and with GitKraken. There is also a video about adding GitLab to your repo manifest and local manifest files.

Thanks!
[Android General] zhunynho:
O need some help with proprietary blobs. How you did this? Some tips. ?
[Android General] AlaskaLinuxUser:
Sure, what is your question? Please be specific. :good:
[Android General] dargonswim:
In first, thank you

make to teach those of us who have no idea how to compile a rom.

I get in touch to try to solve some problem I have when compiling. I'm starting with OmniRom Nougar for Xiami MiPad with codename mocha.

At the time of compiling I get the following error

including ./bootable/recovery/Android.mk ...

/bin/bash: line 0: test: -ge: an unario operator was expected

bootable/recovery/gui/Android.mk:162:

************************************************** **************************

Could not find ui.xml for TW_THEME:

Set TARGET_SCREEN_WIDTH and TARGET_SCREEN_HEIGHT to automatically select

an appropriate theme, or set TW_THEME to one of the following:

landscape_hdpi landscape_mdpi portrait_hdpi portrait_mdpi watch_mdpi

************************************************** **************************

bootable/recovery/gui/Android.mk:163: *** Theme selection failed; exiting.

build/core/ninja.mk:172: recipe for target '/home/dargons10/omni_n/out/build-aosp_arm.ninja' failed

make: *** [/home/dargons10/omni_n/out/build-aosp_arm.ninja] Error 1

How can I fix it?

Thank you again
[Android General] zhunynho:
How to know what is really necessary in vendor folder. How to find the necessary libs, bin and configs.
[Android General] AlaskaLinuxUser:
You bet! Glad to help. This one is easy. Add this line to your BoardConfig.mk file:

TW_THEME := portrait_hdpi

You should always use a web search tool and paste in your error from your terminal to try to see if someone else had this problem before. It will help you a lot on your journey. :good:

Great question.

Partly experience, partly trial and error. A good idea to figure out what is needed is to look at a device tree from a similar phone, like one with the same SoC as a guide. :good:
[Android General] srgrusso:
I don't know if you found what you are looking for but this link might help if you have the lte version [SM-T825]

https://xdaforums.com/galaxy-tab-s3/development/rom-lineageos-15-1-android-8-1-20180423-t3781470

[MENTION=2047373]Valera1978[/MENTION] posted links to his device tree, vendor tree, and kernel source. These can be used to build Oreo based roms. (with modification)

Device forum link: https://xdaforums.com/galaxy-tab-s3
[Android General] Orbital_Logic:
Alas, I have the T 820... the unofficial TWRP recovery guy for both models has a listing for a device tree, but no active link. And the guy who was building an unofficial lineage OS for the t820 broke or lost his device and gave up. I have attempted contacting them both, looked at their GitHub repos with no luck. I appreciate the heads up though.

The whole carrier problem in the US is a train wreck. And Samsung agreeing to offer exclusive LTE deals to specific carriers some form of highway robbery. Why can't we just get the t825 that the rest of the world gets? Who wouldn't want an LTE model? Is the t820 even available in Europe or Asia?
[Android General] dargonswim:
Thanks for the help I got. Now I have the error that I leave below. I searched in google but found a similar error not the same.

ninja: error: '/home/dargons10/omni_n/out/host/common/obj/JAVA_LIBRARIES/platform-test-annotations-host_intermediates/javalib.jar', needed by '/home/dargons10/omni_n/out/host/common/obj/JAVA_LIBRARIES/compatibility-common-util-hostsidelib_intermediates/classes-full-debug.jar', missing and no known rule to make it

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

make: *** [ninja_wrapper] Error 1
[Android General] omercicek43:
Well, the build is complete but it doesn't boot. :D
[Android General] AlaskaLinuxUser:
Hmmm... That is an odd one. Essentially it has some problem in the Android.mk file for that target. (Not your device tree, but in the source.) What are you building? Lineage? What version?

That happens to the best of us! A couple of thoughts:

a. Does it get past the device logo (samsung/lg/etc.) and bootloops on the boot animation for your rom? If so, then you need to enable adb in your build and pull logs to see what is wrong. I can help you with this if you need more explanation, see this vid: https://www.youtube.com/watch?v=E7evKGTgLk4&index=39&list=PLRJ9-cX1yE1nnhWBrZtuVz5YC2OPfQVVp

b. Does it just show the device logo, then buzz and reboot? If so, likely an issue with either the kernel, or the fstab/mount points for device. After it reboots from failing, jump into TWRP and look for

/sys/fs/pstore/console-ramoops

or

/proc/last_kmsg

or

/data/tombstones/ <tombstone numbers>

To see what went wrong. :good:

Ok, so using a prebuilt kernel used to be the "in" thing to do. It saved time on compiling and could be built with fancy toolchains, etc. Nowadays, it is better for your kernel and source code to be built with the same tool chain, so they depreciated using prebuilt kernels. But, your tree doesn't have a prebuilt kernel, but that is the default if it can't find your kernel folder.

In your device tree, is there a file BoardConfig.mk, it says this:

-include device/xiaomi/sdm845-common/BoardConfigCommon.mk

so it reads that file, which says this:

TARGET_KERNEL_SOURCE := kernel/xiaomi/sdm845

So, is your in your kernel folder, do you have a xiaomi folder? and in that folder, a folder called sdm845? Remember capitalization matters, so these should be all lowercase. :good:
[Android General] dargonswim:
No im compiling omnirom Nougat.

Enviado desde mi MI 6 mediante Tapatalk

---------- Post added at 06:30 PM ---------- Previous post was at 06:00 PM ----------

Im compiling Omnirom Nougat

Enviado desde mi MI 6 mediante Tapatalk
[Android General] AlaskaLinuxUser:
Right, sorry, I've been helping so many people I lose track of who is doing what.... :D

So, where did you get the tree and stuff from? Does it compile properly when you build LineageOS, or dotOS? The error is saying that you need to modify the Android.mk file for the source code for that particular function/app, but typically you don't want to edit the source code, as it will change every time you repo sync. So either that particular part/function is not working properly in Omni Oreo, or you have a problem with your java setup. Did you get the tree from Lineage? if so, what version? Nougat?
[Android General] J2A9:
Sir, thanks for the clarification. as its a new device, there is no prebuilt kernel available as of now.

I downloaded the kernel source and placed it inside kernel/xiaomi/beryllium

is side xiaomi folder no sdm845 folder is available. as i dint get such a folder when i downloaded the kernel source zip file from git hub.

now The last line of the log reads ( ckati failed with: signal: killed ) and it stops there. so what should i do now to proceed building, kindly guide me
[Android General] omercicek43:
It stucks on logo. I've used the same kernel I've used with LOS.
[Android General] AlaskaLinuxUser:
Then you need to change the boardcommonconfig.mk file line from this:

TARGET_KERNEL_SOURCE := kernel/xiaomi/sdm845

to this:

TARGET_KERNEL_SOURCE := kernel/xiaomi/beryllium

Because it is looking in the wrong place. :good:

Did you look in TWRP for those files I mentioned? Could you find them? What did they say? :confused:
[Android General] dargonswim:
Thanks for your answer. The files in the device tree are aex Nougat taken from another developer who let me use them. They are Nougat and they work correctly in aex, and roms derived from aosp. This is also a modification of a lineage repository to which it works. The branch is Nougat 7.1.2

Enviado desde mi MI 6 mediante Tapatalk
[Android General] AlaskaLinuxUser:
Well, I'm not sure about that error. I'd recommend that you ask the developer who let you use his material why you get that error. :good:
[Android General] srgrusso:
I found out for my galaxy tab a 10.1 tablet that I was able to boot a rom built for the lte version. The only problem that I had was it told me that I didn't have my sim card inserted other than that everything worked. You might want to try using the SM-T825 device tree and vendor tree and see if it works. I would think it would at least get you close.
[Android General] AlaskaLinuxUser:
Okay, so off topic, but there is a baby moose sleeping in my yard..... Just thought I'd share. :p

Alaska Linux user, it's not just a name. :D
[Android General] Nevermindthelabel:
How educational can one thread get?! Compiling and wildlife living in harmony.
[Android General] Orbital_Logic:
That's all well and good, but there exists an unofficial Los build for the t 825. This is could just install that version and deal with the notification. But I'd like to experience, I know my way around the command line, and I like to do this for the tablet. Of my warranty isn't even over yet so I won't be installing it on my tablet for at least another few months. And I'm currently getting the annoying moisture detection warning every few days or so so I need to take it in for Servicing but I don't want to do that until I get myself some kind of Android device to use in the meantime. That doesn't mean that other people can't test it for me. Right now I'm dealing with space issues on my desktop, so I haven't even started but I'm looking for a solution to that as we speak.
[Android General] dargonswim:
I asked to developer and he told me how fix it.

Testing module in android source, so check .repo/manifest.xml, if there already have such module, like:

<project path="platform_testing" name="platform/platform_testing" groups="pdk-fs,pdk-cw-fs,cts" remote="aosp" />

the path is platform_testing, then you can just execute 'repo sync platform_testing', it will sync to platform_testing folder.

if it's not exist, you need to add to .repo/local_manifests/roomservice.xml (different system may use different name)

But i have new problems

Note: Some input files use unchecked or unsafe operations.

Note: Recompile with -Xlint:unchecked for details.

/bin/bash: jar: orden no encontrada

[ 0% 106/31880] host C++: libc++_static <= external/libcxx/src/locale.cpp

ninja: build stopped: subcommand failed.

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

make: *** [ninja_wrapper] Error 1
[Android General] AlaskaLinuxUser:
Uhm, did you install jdk 8?

I had to translate, but I think this says command not found for the command of "jar".
[Android General] AlaskaLinuxUser:
Well, to be honest, I have no idea what is wrong with your tree/source/setup. It appears that this device requires some extra source files that the other developer had you add. I would recommend that you post a thread in your devices q&a and try to get some device specific help, perhaps by using the @ symbol to mention the developers who helped you this far with the previous info. Be sure to be polite, and also hit their thanks buttons if they try to help you with your questions. But I'm afraid I don't have the knowledge you need for that platform. :confused:
[Android General] omercicek43:
Here's the tombstone folder; https://drive.google.com/drive/folders/1AAtEjV3b9x47U3_vj48aOe08MdVkGtNq?usp=sharing

last_kmsg was empty but I got this; https://drive.google.com/file/d/127jdE-oBGADEPfQ_yy3WC2cDGpXXM-Na/view

The other one was also empty.