I'm new to rom building. While I was trying to build roms on ubuntu 18.04, some errors occurred. I've cloned device, vendor, kernel and etc of z2 in the building directory and I've recynced the source code ofroms many times. Could anyone tell me what's wrong? Thx very much
And here's the screenshot:
Related
Hello Guys,
I've been building find7 for one year (for crdroid tteam mainly) and since yesterday i'm facing a strange issue building:
error message:
----- Making boot image ------
error: could not load device tree image '/home/jejecule/crdroid2/out/target/product/find7/dt.img'
make: *** [/home/jejecule/crdroid2/out/target/product/find7/boot.img] Error 1
I downloaded pure cm12.1 source, made the same test and exactly the same error
Reverted last sepolicy cm-vendor commits, same issue, changed kernel, same issue...
Anyone facing the same with cm based rom with this device?
Thanks guys
cm is changing a lot of things right now. they seperated the oneplus one from msm8974-common,
and the find7 has a new kernel too..
suraj.das said:
cm is changing a lot of things right now. they seperated the oneplus one from msm8974-common,
and the find7 has a new kernel too..
Click to expand...
Click to collapse
Hey my friend, did not notice that Find7 had his own kernel...maybe it's why...
How are you? and you tipsy builds?
See U soon.
Cheers
Jerome
Oppo find7 can running cm ROM based use caf kernel and caf ROM?
Sorry for my English.
I don't know what's the issue with my setup or kernel tree (Alberto97's git) that I'm getting these errors all the time when I try to compile any rom
1) rmnetctl library conflict. There's always this error in all roms and states that "shared libraries is already defined" in rmnetctl folder in device tree hence stopping the build at the begenning. I got past the issue by deleting the rmnetctl folder in device tree but is it the right way to do it?
2) Sepolicy error. Even after I delete above folder, the build stopped after it reaches about 34%, I don't know what it's called but I'm getting this error every time I try to compile any rom. This time while building aosp extended https://hastebin.com/yomepicili.sql
I'm a noob so pardon any lack of knowledge. I am trying to learn to compile here. Also, I'm using oreo-mr1 branch device tree and kernel and oreo-mr1-addison branch for vendor.
Trying to get a build going for 16.0, using lineage sources. Had one error that I was able to resolve, but this second error is giving me problems. Might just be an easy solution that I'm overlooking. Maybe someone else can have a look at it.
Here's the error:
https://pastebin.com/K79yhwkX
Are you able to share the steps you've taken to get this far?
I compile private builds of NitrogenOS but would like LOS16 too.
I am after some help in building LineageOS 15.1 for Samsung S6 (zerofltexx) and S6 Edge (zeroltexx). I know it isn't officially supported (only 14.1 is official), however there are unofficial builds and apparently all the sources required are on GitHub.
I have tried LOTS of times to build this but each build has the same issues when flashed to the S6 Edge I have to test with.
I have followed the guide here - https://wiki.lineageos.org/devices/zeroltexx/build which officially covers building Lineage 14.1. I have wiped an i7 PC with 24GB RAM and 2 * 1TB disks. I installed Ubuntu 18.04 desktop, installed all updates, added all the required components listed in the guide (I also needed to add python that wasn't listed). I changed the repo sync command to be 'repo init -u https://github.com/LineageOS/android.git -b lineage-15.1'. I then pulled in the 'zero.xml' repo manifest from here - https://github.com/Exynos7420/local_manifests and added it to /.repo/local_manifests/ and then built the ROM.
It appears to build OK - there are lots of errors in the log, however I think this is correct? It takes about 37-minutes and it outputs a .zip file in the out/product/zeroltexx directory. This installs OK to the S6 Edge, however there is an error at the start of it booting about selinux (small red text at the top of the screen for a couple of seconds). Once booted the audio doesn't work and neither does the RIL. This is compared to the unofficial ROM that Enes Uzun has created.
I have asked (and asked...) for help on the telegram group, however I keep getting told I am not doing anything wrong. If this is the case then I am doing something wrong in creating my build environment - i.e. Ubuntu or the Lineage build parts.
I am hoping someone on here has had a similar experience and managed to solve the issues or can point me in the right direction as I am stumped. I have wiped the machine and rebuilt Ubuntu 18.04 desktop 3 times so far. Following the build the results are the same each time so whatever I am doing wrong I am doing it each time.
Any help is really appreciated.
Andy
Help....
In my continuing failed attempts at building this I have now wiped another PC - Intel Core 2 Quad-Core Dell XPS with 16GB RAM and 2 * 640GB hard drives, installed Ubuntu 18.04, followed the guide etc etc etc and have hit EXACTLY the same issue so I am definitely doing something wrong.
I found this guide - https://forum.xda-developers.com/android/software-hacking/guide-how-to-build-lineageos-15-1-t3750175 which is for Lineage 16.0, however there is a link to this - https://web.archive.org/web/2018061...ng/guide-how-to-build-lineageos-15-1-t3750175 which is for Lineage 15.1.
So I wiped the original i7 24GB machine and installed Windows 10 Insider Preview 18290, enabled WSL and then added Ubuntu 18.04 from the microsoft store and then followed the guide TO THE LETTER and added the zero.xml from https://github.com/Exynos7420/local_manifests to the /.repo/local_manifests folder, did a 'repo sync' etc etc. Guess what? same f'cking issue..
Help please anyone? I just want to build my own Lineage 15.1 for Samsung S6 (zerofltexx) and S6 Edge (zeroltexx) so that I am not reliant on someone else releasing randomly periodic ROMs that are likely to stop when the developer stops building Lineage 15.1.
Help...
Fixed it....
The zeroltexx sources were incomplete. They were missing some files and a couple of files were wrong. These have now been updated by the maintainer (https://github.com/Exynos7420/android_device_samsung_zeroltexx), however these haven't been pushed to the official Lineage repositories yet (https://github.com/LineageOS/android_device_samsung_zeroltexx). Therefore if you are going to build it yourself you will need to use the Exynos7420 repositories (for the S6 Edge zeroltexx that is - the S6 zerofltexx has the right stuff).
Andy
Hi ADB100,
many thanks! I will try the same, after my lovely S5 get's the black-screen-of-death.
My colleague gave my an old S6, but I had lerned to love los 16.
My problem was to know howto add additional sources to the los 16 sources. Here your thread gave my some important tips.
I started to learn a build with the official sources of los 14.1, but it failed of less ram on my computer and an out of memory error message.
So I grabbed 6 gb of an old pc to give it a next try next week. If it will work I will tdy los16.
I'm not a developer, but familiar with Linux. My problem is to add all sources and to manage git and repo.
Additional to use the zero.xml. I put it on your mentioned folder, but "breakfast zero" or "breakfast zeroltexx" sent me a nothing found!
Do you have a good tutorial which I can follow?
I spent a lot af time to search for it, but all tutorials was for official build, same like the los build guide.
After a lot of googling around and like 50 open chrome tabs I tried making own device tree so I used old cm makedevice.sh script and updated it with help of current lineage bacon device tree and some brcm_rpi3 device tree, here you go *"*"https://github.com/honzapatCZ/android_device_amlogic_mk8080bplus"*"* vendor is not currently setup so Iam building just recovery, but I get an error:
HTML:
23:00:34 Could not create module-finder: finder encountered 1 errors: [/mnt/d/Dev/ANDROID/lineage/android/lineage/external/swiftshader/tests/unittests: lstat /mnt/d/Dev/ANDROID/lineage/android/lineage/external/swiftshader/tests/unittests: no such file or directory]
Any idea what it is? How to fix it? Iam gonna do more research about rpi3 device tree as its the closetst thing I know about features.
Thanks