Develop Bugs

[Q] Building CM10.2.0 For S4 Mini LTE

Hello All,
This may be in the wrong place so if it is, I am sorry, anyway to my question I'm trying to build CM for my S4 Mini LTE Serranoltexx everything was going fine until I got this message after running extract-files.sh
Code:
Extracting /system/lib/egl/libGLESv2S3D_adreno200.so ...
remote object '/system/lib/egl/libGLESv2S3D_adreno200.so' does not exist
Now after adding "libGLESv2S3D_adreno200.so" (if you search Google for it it's the top github link) I managed to get it to build the actual .zip and it does flash properly but it doesn't seem to have the correct graphics drivers (I thought this process wouldn't work and I was right), the guide on the how to build it doesn't help with this problem either so any help would be extremely appreciated
I've attached the logcat for reference (if it's needed) as a .docx file as the .txt file was 1.1mb and because I don't have a pro account on pastebin.

The problem with newer Android versions is that if often require new libraries which are not available in stock rom, so the extract method is actually not very useful unless we have a stock rom of the same version we are building for. To bypass this issue we use libraries from other phones that have the matching Android version. I suggest using the blobs that's on TheMuppets github, as those are up to date.
https://github.com/TheMuppets/proprietary_vendor_samsung

[HELP BUILDING ROM] - How to add device tree, vendor and kernel to my build setup?

Hi,
I decided to build Carbon Gee, since the last available version for gee is from July.
All the pre-requisites went fine, the build environment, etc, without any issues.
I couldn't find a detailed guide for carbon rom specifically, so I did a repo sync with carbon dev before adding vendor, device tree and kernel stuff.
Th repo sync tool all night!!! brrrr
Now, my poblem is, how do I proceed from here?
This is my first time trying to build a ROM, can anyone with more knowledge guide me a little?
I want to use Jollaman's device, vendor and kernel (bc it has stock camera drivers ported for gee) and is generally a great kernel.
Does Carbon require anything else specific to it? I can't find any info on this.
If I'm successful, I promise to relase updates at least weekly.
Thank you.
EDIT: I successfully added all that by the local_manifest.xml thing... now, my problem is, carbon supposes some files, (like carbon.dependencies) and stuff, and I'm only seeing cm related ones in the device folder... Can I just rename cm to carbon everywhere? I don't think that's how it works... :s
It won't start building. Later today, when I get home, I'l post the specific error messages.

Did you find the guide ? I am also looking for some ...
Sent from my HTCSensation using XDA Free mobile app

Blobs and a kernel build

Hello,
I am trying my first kernel build, and there is one item I am not understanding, and I cannot seem to find a definitive answer on the web.
I cannot figure out how device blobs are incorporated into the kernel build. Are they required for functionality, or does the device specific kernel source code on GitHub already contain them?
I tried the kernel build described in CM, however that was unsuccessful for me, I was unable to make it through the 'installboot' command.
Therefore, I have been watching, and reading, all the guides on how to build a kernel but none of them (at least that I could find) mention what to do with the device blobs. What am I missing? It seems that if I do not add them I will lose functionality?
I am new to this so maybe I am missing something obvious.

Erik63 said:
Hello,
I am trying my first kernel build, and there is one item I am not understanding, and I cannot seem to find a definitive answer on the web.
I cannot figure out how device blobs are incorporated into the kernel build. Are they required for functionality, or does the device specific kernel source code on GitHub already contain them?
I tried the kernel build described in CM, however that was unsuccessful for me, I was unable to make it through the 'installboot' command.
Therefore, I have been watching, and reading, all the guides on how to build a kernel but none of them (at least that I could find) mention what to do with the device blobs. What am I missing? It seems that if I do not add them I will lose functionality?
I am new to this so maybe I am missing something obvious.
Click to expand...
Click to collapse
Hello,
Please tell us the make and model of the device you building for.
Regards
Vatsal,
Forum Moderator.

Hi,
This is for an LG V500 tablet. Thanks!

Uses the code fefifofum as a base, but asks permission from him before

edsmat said:
Uses the code fefifofum as a base, but asks permission from him before
Click to expand...
Click to collapse
Thanks edsmat. sorry, but I am a little confused, does the code from fefifofum contain the blobs? Actually, I have the blobs, grabbed them from he V500. What I am confused about is how these blobs are incorporated into the kernel build (I have the kernel source from github).

Device Tree for Oreo?

Hello
I want to build a resurrection remix Oreo ROM for my d2can/d2att but I can't seem to find the proper device tree and kernel tree for Oreo. Is there a way to either port the nougat trees or make my own tree compatible for Oreo?

It is but you are going to go through literal hell learning how to do so. i am working on the same thing and have some stuff figured out but getting help has been next to impossible. you have to read countless websites piecing the information together and trying things until it works. you can go into the lineageOS IRC but they dont talk too much, and like answering questions even less. What i learned was a bit easier then using the lineage repos for everything was just to sync lineage 15.1 or 16.0 and then to google around for a device tree and kernel. they usually still come from github but have different names. for example our s3 here goes by more names then d2att for example. SGH-i747 is another variant of s3. if you look for the other variants you will find more device trees. you can get lunch to show them to you by adding them to the vendor folder before you attempt to run the envsetup.sh as for the boot.img you will need to again google around a bunch and learn about mkbootimg and the tools needed to extract and repack them, if you use superrs-kitchen you will extract and see the files bot many will have a lock, and you cant edit the init.rc. you can extract your boot from your device directly via adb, or download a rom and unzip it n grab that boot.img if you use a rom you know works. you can change the OS version and all necessary info in the files to tell the phone its android 8.1 and whatnot. but as i said its not a short process. ive spent many many night getting frustrated because lunch fails partway into a build, or i flash a kernel i complied and it doesn't work. getting Pie 9.0 and Oreo 8.1 to boot on my s6 edge plus was a nightmare and a half, and the s6 files are all readily available to me from lineage to use as a base. the s3 was really popular however, and i know lineage has a nougat rom for it, so they must have repos with trees
---------- Post added at 03:44 AM ---------- Previous post was at 03:42 AM ----------
https://github.com/Bdaman80/SGH-I747
device tree.
https://github.com/sgs3/SGH-I747M_Kernel
kernel

[ROM][UNOFFICIAL][10] e/OS 0.22 q for Motorola One xt1941-4

Following this thread, I recently built e/OS 0.22q for Motorola One xt1941-4 (deen). Please refer to https://e.foundation/e-os/ to learn more about e/OS.
After several weeks of usage this ROM seems to be very useful. Find the zip file with the images of the Andoid 10 version here. Unzip and flash using adb and fastboot. Please use at your own risk!
I used the following repos in my local manifest:
https://github.com/electimon/device_motorola_deen, branch Lineage-17.1
https://github.com/electimon/vendor_motorola_deen, branch Lineage-17.1
https://github.com/100Daisy/android_kernel_motorola_deen, branch android-10-release-qpks30.54-22-13
In addition, I included
https://github.com/LineageOS/android_system_qcom, branch Lineage-17.1
which is obviously needed by some stuff from vendor. Vendor files are from 2019, so if someone could provide a more recent repo, I would be glad to know (last stock rom provided by Motorola is from October 2021)
All credits go to the creators of the LineageOS 17.1 port (link to thread at the top of this post)! Very good job guys!

Works just fine, thanks.

LSV12 said:
Works just fine, thanks.
Click to expand...
Click to collapse
Thanks!

Hi! can you make a tutorial to install this rom? i'm new at the custom roms and idk how to install, and sorry for my bad english, i'm brazillian

01nick07 said:
Hi! can you make a tutorial to install this rom? i'm new at the custom roms and idk how to install, and sorry for my bad english, i'm brazillian
Click to expand...
Click to collapse
I'm sorry, but I have no time and I am not good at making tutorials at all. Please refer to the thread referenced at the beginning of the initial post. There you should find all necessary information. If this is not enough, do some more searching and reading on XDA. If you still feel uncomfortable, stay with the stock rom.

Nice work. You succeeded where I failed
I'm trying to build on top of Q to build a e/os 0.23-R version (I see you actually managed to do this). Are you willing to share your sources (here/github) or just a hint on how to build it?
I tried to compile, but I'm stopped at the beginning of the repo-sync for a duplicate manifest.xml
Thank you.
PS: One thing I stumbled upon and managed to fix is the new way e/os manages the prebuilt apk with git lfs
The build will fail unless these apks are downloaded in a separate step. Here's the relevant info from the docs:
Those building using traditional repo sync method refer android_prebuilts_prebuiltapks_lfs 3
You will have to install git-lfs
sudo apt-get install git-lfs
After completing a repo sync, you will have to run
repo forall -c 'git lfs pull'

xdadevc said:
Nice work. You succeeded where I failed
I'm trying to build on top of Q to build a e/os 0.23-R version (I see you actually managed to do this). Are you willing to share your sources (here/github) or just a hint on how to build it?
I tried to compile, but I'm stopped at the beginning of the repo-sync for a duplicate manifest.xml
Thank you.
PS: One thing I stumbled upon and managed to fix is the new way e/os manages the prebuilt apk with git lfs
The build will fail unless these apks are downloaded in a separate step. Here's the relevant info from the docs:
Those building using traditional repo sync method refer android_prebuilts_prebuiltapks_lfs 3
You will have to install git-lfs
sudo apt-get install git-lfs
After completing a repo sync, you will have to run
repo forall -c 'git lfs pull'
Click to expand...
Click to collapse
Thanks! I wrote a report on the endeavour, where you will find almost everything of what I know.
Motorola One (xt1941-4) „deen“: How to build e/OS 0.22 – Herr Elling
fusselbart.de
Please note that I am not a ROM programmer, nor maintainer, and most of the build process is black box to me. However, I will try to build e/os 1.x after summer...

HerrElling said:
Thanks! I wrote a report on the endeavour, where you will find almost everything of what I know.
Motorola One (xt1941-4) „deen“: How to build e/OS 0.22 – Herr Elling
fusselbart.de
Please note that I am not a ROM programmer, nor maintainer, and most of the build process is black box to me. However, I will try to build e/os 1.x after summer...
Click to expand...
Click to collapse
I read your article and managed to follow it and compile my own e/os. I'm also not an android developer. I did some kernel work in the early days, around Android 2.0 but my path diverged and now I'm completely lost.
Let's keep in touch. If you restart your efforts, I'll be happy to contribute. Meanwhile I'll try my best to get some info from the e/os forums and (pray) the lineageos residual devs.