yashsingh1/xdaforums huggingface dataset:
[Android] guyzz6370:
I've already closed the terminal, how do I get the log back so I could post to pastebin?

I'm building LineageOS, xiaomi mi 8 (dipper) device. I'm following both this guide and also the guide provided by LineageOS >>> https://wiki.lineageos.org/devices/dipper/build

I've setup my dependencies and everything, downloaded source, repo sync, etc.

Finally i just run brunch dipper

And it runs, the final result is what I posted in the screenshot, with the error
[Android] DiamondJohn:
You cant.

Just rerun brunch, and keep the log. Personally I keep all the output of my builds for posting questions, as well as for other reasons. See https://xdaforums.com/showpost.php?p=79797126&postcount=9417 you will need to install "tee", but it will tell you what to do, when you try.

I've never had your error so someone else here would know more, and there may be more info in the rest of your log. But it explicitly tells you what it thinks you should try as a starting point. Rebuild with ART_BOOT_IMAGE_EXTRA_ARGS=--runtime-arg -verbose:verifier to see verification errors.

=================Edit=======================

Did you even try a web search? That's the first step after getting an error.

https://blog.csdn.net/qq_37968132/article/details/80656831 (translate to English)

source build/envsetup.sh;

lunch XXXXXXXXXX

brunch XXXXXXXXXXX
[Android] guyzz6370:
yes i did it all in the same shell ..and same directory..

ok, I noticed most guides suggest Ubuntu 14.04, I'll just download 14.04 and just set up my system again...

I'll post back the final build if any errors..
[Android] quake73:
Search in your device tree for a line that says smtg like: PRODUCT_BOOT_JARS += WfdCommon

...and comment it or simply delete it.

I looked at the LOS dev.tree for 'dipper' and found that line in https://github.com/LineageOS/android_device_xiaomi_sdm845-common/blob/lineage-16.0/sdm845.mk
[Android] guyzz6370:
but why would the code contain a line that would cause headaches?
[Android] DiamondJohn:
I personally build Pie on Ubuntu 18.04

Its a common / shared component, it may be required for other devices or ROMs that use that same repository. To build my currently chosen Pie ROM for my device, I have to blank out two make files. Mine is an official device for the ROM.
[Android] gipsy.danger:
there are several devices that could be using the device tree, you have to make changes accordingly for your device.

a simple word can cause headaches building rom.

---------- Post added at 12:18 PM ---------- Previous post was at 12:17 PM ----------

why use so old version, either use 16.04 LTS or 18.04 LTS .

i personally use 18.04
[Android] guyzz6370:
Ok, I'll download 18.04 instead..

So I plan to start fresh...i'll be following the guide by LOS https://wiki.lineageos.org/devices/dipper/build

I will surely post back when I'v done everything (setup, download and build source) ...

Really thanks to you and [MENTION=5417899]DiamondJohn[/MENTION]
[Android] DiamondJohn:
I keep my source on a different partition/drive. By doing so, I can move the 30+gb source code between OS's.

NB: I am running VBox, so the different partitions are actually simply different files which reside on different drives, including USB portable hard drives.

First step of my build process is to mount the partition into the appropriate folder. I have built multiple ROMs in the past eg if I were building LOS:

sudo mount -t ext4 /dev/sdg /home/diamondjohndroid/android/lineage -o errors=remount-ro,noatime;
sudo mount -t ext4 /dev/sdc /home/diamondjohndroid/android/lineage/out -o errors=remount-ro,noatime;

This way I don't have to re-download the source if I re-build my OS. By keeping different parts (Source, Out, Swap, CCache, OS) on different drives also means that I have parallel reads and writes ie much faster builds.
[Android] guyzz6370:
Used pastebin this time..

Ok, so everything is fresh now, using ubuntu 18.04 and I followed this guide by LOS https://wiki.lineageos.org/devices/dipper/build

Their guide told me to install these packages:

For java, I installed using sudo apt-get install openjdk-11-jdk -y

The pastebin is here https://pastebin.com/3y4LVkLg

Everything seems fine, all fresh and everything..?? What's with the javalib.jar ?
[Android] DiamondJohn:
From memory, Ununtu 18.04 comes pre-installed with a working java. I think you have gone out on a limb by installing openjdk-11-jdk. I am not saying its the cause of your current issue, just that it was an unnecessary step, that is not listed in the instructions, that may cause issues.

The instructions you said you followed, explicitly state
[Android] guyzz6370:
yes i saw that...okay that was a stupid move..what do i do now remove the openjdk11? please guide me on this..

EDIT: or just backup the LOS source..and then flash a new Ubuntu and then setup system again..this time not installing java..and then copying back the LOS source so no need to download again? this seems easier and guaranteed it is clean ..what do you think?

EDIT2: I've flashed a new Ubuntu again..this time not installing java
[Android] gipsy.danger:
sudo apt-get remove openjdk*

you shouldn't install anything apart from given in instructions.

the build environment setup is almost same for all rom development.
[Android] guyzz6370:
I'm running into some big problem now...I flash the TWRP...did a wipe of cache ,system, dalvik, and internal. Then flash the PE ROM (i wanted to try PE) and now it just stucks in fastboot!

omg..please help

i can't get out of fastboot
[Android] DiamondJohn:
well, the cup is half full.By the sounds, the ROM built successfully.:highfive:

Thats not good:(, and its never happened to me. It sounds very much like a device specific issue. I would be posting your issue on a device specific thread.

Random thought:confused:, fastboot would mean on my devices, that it is ready to flash the OEM firmware; ie the stock ROM. to recover the phone.

====edit====

have you tried explicitly booting to TWRP using the hardware key combination? Then flash a working ROM zip file.
[Android] gipsy.danger:
did you built PE yourself?
[Android] guyzz6370:
Oh no, the cup is still empty, I wanted to have a working zip first, I'll continue the build later on

I posted it here too https://xdaforums.com/mi-8/help/mi-8-stuck-fastboot-mode-t3957464

really? then i'll just download miui and try that too if nothing works..

yes, I go into TWRP via volume up + power button, wiped everything and then flash the zip file, reboot, and it goes to fastboot!

EDIT: I think i'll see if anything works over at the thread i created in the mi 8 forum https://xdaforums.com/mi-8/help/mi-8-stuck-fastboot-mode-t3957464

---------- Post added at 02:47 PM ---------- Previous post was at 02:46 PM ----------

nope, I downloaded the zip from PE, I wanted something working first, I'll build later on :)

EDIT: IT'S FIXED! refer to my post here https://xdaforums.com/mi-8/help/mi-8-stuck-fastboot-mode-t3957464#post80071311
[Android] guyzz6370:
Now it's time to get back to building the ROM!

[MENTION=5417899]DiamondJohn[/MENTION]

We were here on the build...I'll continue from here

Now i'm going to do everything again, not installing java this time

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

Now it's time to get back to building the ROM!

[MENTION=5417899]DiamondJohn[/MENTION]

We were here on the build...I'll continue from here

Now i'm going to do everything again, not installing java this time
[Android] DiamondJohn:
There is no need to single me out with a mention, considering this thread is read by people a LOT more skilled than I, and are more than likely building a device more akin to your.
[Android] guyzz6370:
Hmm yeah but , you're among the few who reply..nobody else is replying..so it makes sense to mention you ;)
[Android] DiamondJohn:
Because you single me out, it makes people less inclined to step in. And I get bombarded with notices
[Android] guyzz6370:
:eek: okok, so to anyone who might be reading this, please feel welcome to join in ;)
[Android] guyzz6370:
Same error again! This time I didn't even touch java and its a fresh install of ubuntu 18.04 with all the needed packages for compiling installed as per LOS instructions https://wiki.lineageos.org/devices/dipper/build

Pastebin output again https://pastebin.com/R6aAEwqZ
[Android] ripee:
I'll run a dipper build myself later on my Ubuntu 18.04.3 to narrow it down. I mostly run Samsung builds but Java is used the same.

In the meantime, take a look at my scripts repo on github and see if you installed all the packages in build_environment.sh
[Android] guyzz6370:
Wow thanks! But before you do that, I have one last thing to add (if it helps)

When you run repo init, it will give you a python not found error...

And ubuntu 18.04 has python3 preinstalled on it and then repo init doesn't work with python3 (as far as my computer goes), so what I did to make repo init work was to go into the repo script and edited the shebang line from

#!/usr/bin/env python to >> #!/usr/bin/env python2

and then I installed python just by sudo apt-get install python -y

and I read what it installed, it will install ..python2.7, python-dev, and other python stuff

...and then repo init now works..

So that's all the information I have, I'm really eager for you to try building yourself..and post your findings ..thanks really :good::good:

EDIT:

I didn't check everything but I know I didn't install openjdk-8-jdk (because the LOS guide didn't tell me to do it)

the LOS guide I followed had the following packages:

there isn't a openjdk-8-jdk included in their guide

PS...why do different people/guides have different instructions? why isn't the build packages needed exactly the same across all ROMs? wouldn't that make life easier for people like me who are less pro?

and then maybe xda would have less posts like mine..:laugh:

again..awaiting your input :)
[Android] gipsy.danger:
i don't follow lineage wiki now, when i started building i used to follow it and run into issues later. better follow guides on xda and look for dependencies.

also you sure all the packages installed without any error?

these are the packages that should be installed, at least that's what i have and never run into such issues

openjdk-8-jdk android-tools-adb bc bison build-essential curl flex g++-multilib gcc-multilib gnupg gperf imagemagick lib32ncurses5-dev lib32readline-dev lib32z1-dev libesd0-dev liblz4-tool libncurses5-dev libsdl1.2-dev libssl-dev libwxgtk3.0-dev libxml2 libxml2-utils lzop pngcrush rsync schedtool squashfs-tools xsltproc yasm zip zlib1g-dev git-core python
[Android] DiamondJohn:
Change it back! and resync. Newer is not always better. It could have some compatibility issues.

The following is an example of what i have been using for a few years to resynch.

cd ~/android/havoc_pie/;

repo forall -c git reset --hard;
repo forall -c git clean -fdx;
repo forall -c git checkout -f;
repo sync -fc -j2 --force-sync --force-broken --no-clone-bundle --no-tags;

The following is NOT a guide, but simply a (part of the) log I took for my own benefit in case I needed to do it again, of most of what I did to build my working environment to build Pie Havoc-OS successfully. I ran each line individually to interactively check and handle any errors.

https://hastebin.com/levesusama.nginx

Notice that python is the "old" version.

The "moreutils" is simply because I use the "tee" function in bash to do logging

The bash.rc changes were added when I had issues, and search the web or this thread,or used in previous build boxes. I have 12GB assigned to a VBox. You may not need all or any of the changes I made.

---------- Post added at 23:45 ---------- Previous post was at 23:33 ----------

Simply an FYI;) I checked your list against the LOS list, and you had the following extra packages. The non-bold ones I added to the LOS list.

android-tools-adb

openjdk-8-jdk

python

yasm

I have a working build-box for Pie Havoc-OS, which I built using the LOS list of packages (+1 or two), but the one that stands out as not being in my list is "yasm", and "android-tools-adb". But I use VBox and connect to my phone via ADB directly from the Win host. So "yasm" to me is the dark-horse.
[Android] guyzz6370:
yes they all installed with errors

---------- Post added at 02:49 PM ---------- Previous post was at 02:43 PM ----------

oh..repo init is now working...don't know what happened ..but yeah I change it back and did the repo init again and then repo sync

---------- Post added at 03:24 PM ---------- Previous post was at 02:49 PM ----------

Hmm..I'll be waiting for [MENTION=6005084]ripee[/MENTION] to attempt a build ..but if anyone is interested to attempt a build too, that'd be great!

So i changed the shebang back to python instead of python2..and did repo sync

Then I also installed the openjdk-8-jdk package..

Still javalib error...

I'm just going to wait patiently , because I don't know what else to do...
[Android] ripee:
[MENTION=10068584]guyzz6370[/MENTION], I cannot attempt a build of dipper without a copy of the blobs, which have been taken down from GitHub due to DMCA.
[Android] NepoRood:
Java Error

[MENTION=10068584]guyzz6370[/MENTION]

ninja: error: '/home/abc/android/LOS/out/target/common/obj/JAVA_LIBRARIES/[B][COLOR="Red"]WfdCommon[/COLOR][/B]_intermediates/javalib.jar', needed by '/home/abc/android/LOS/out/target/product/dipper/dex_bootjars/system/framework/boot.prof', missing and no known rule to make it

As suggested by [MENTION=5366380]quake73[/MENTION], in this post, I figure the line is still commented or removed from your device tree...
[Android] ripee:
duplicate post
[Android] guyzz6370:
ok, I didn't try that...but when I did..the results were positive! It seems to compile now ! Take a look!

when I changed the sdm845.mk (which is in the directory android/lineage/device/xiaomi/sdm845-common/sdm845.mk) the terminal says that sdm845.mk was modified..then regenerated

and then..it started compiling!

and now it's almost done..hopefully it will build till the end
[Android] guyzz6370:
Proud moment! It is finally done!

Ok, so the fix was to uncomment this line at the very bottom of sdm845.mk file located here >> android/lineage/device/xiaomi/sdm845-common/sdm845.mk

PRODUCT_BOOT_JARS += \

WfdCommon

Now, the final question for this is, why didn't the LOS devs uncomment this line for the mi 8 ?

Is there a way to make a change to the repo on github or let the LOS devs know about this?

I'm pretty sure that there will be more threads in the future asking the exact same thing that had troubled me for days now...

I think that..I posted so many and had received so many replies that this deserves its own thread :)

My god...you guys who reply on XDA when people need help, really thanks to all of you who stuck with me on this! :)

EDIT: but it doesn't end here! though LOS is now built successfully, I may also be interested in building other ROMs too! Like the PE ROM, but I won't yet, because the proprietary xiaomi vendor blobs are taken down by DMCA :( I'll just have to download PE zips for now until they are restored in the future :)
[Android] gipsy.danger:
that line you commented out could be needed by other devices. you forgot you are using a common sd845 device not your specific device tree.

congratulations on building it successfully, did it boot successfully?
[Android] guyzz6370:
not my specific device tree? what does that mean?

did it boot correctly..i assume it would.. as crazy as it sounds, I'm not flashing it because i am now using a PE ROM and i don't want to clean my device and then flash and then reflash back to PE..

but why wouldn't it boot? i assume that when it compiles then everything is already worry free?...:fingers-crossed:

EDIT: but if you are curious if it boots or not, or anybody else is curious and wants me to flash it, I will do it anyway, because there's been so much hassle to build the ROM already, I agree it seems like a waste not to flash it...and you've all been helpful so flashing it to satisfy your curiosity is the least I can do :) I have already made a TWRP backup of my current PE ROM, if anything happens, I'll just reflash this backup and I should be fine again :)

So yeah, tell me if you want me to flash it!
[Android] gipsy.danger:
that is a common device tree for snapdragon 845 devices where developers can make specific changes to it and use it for building specific roms.

phone manufacturers nowadays releases specific device resources for developers. however they don't do it for all their devices only for few.

build successful doesn't mean it will boot and everything will work.

i have had so much issues when started building aosp for my device.

on my first build it refused to even flash in twrp, on 10 th build sensors didn't work.

then i took break and started researching after 2 months i finally managed to build another and there sim won't be detected.

after another month of asking help all over xda and anyone i knew was building for my device i finally managed to build a working ROM. even then there were few issues. noe i have some issue with boot image but i am working on it.

yeah of course you should flash it and check if everything works. you did so much hard work..you should make sure the build was worth.

good luck.
[Android] guyzz6370:
never knew building was soooo involved and causes migraines ?

I'll flash it some time soon, I'll post back..but judging from what you've said... I'm not confident it'll just work..?
[Android] DiamondJohn:
Does your device have an official thread on XDA for this ROM. If so, PM the OP and ask if you could offer your build test (via PM). This is a development site, not a release site. If not, then start your own thread making it VERY clear its an experimental build you haven't personally tested/flashed. I have release more than one experimental builds on XDA, and people are eager to test for me, and my experimental/blind build of TWRP for one device works and is usable by others.
[Android] guyzz6370:
Ok..so I've tried the build and no, it didn't boot! It will be stuck at the mi logo indefinitely, restarted the phone, still the same..looks like my building nightmares aren't over yet :crying:

But its actually because of lack of proprietary xiaomi vendors files..(taken down by DMCA) ...I'm pretty sure if I could get a copy of the xiaomi vendors files...and rebuild ..it may just finally work..
[Android] tribual:
For what phone you need?

Gesendet von meinem MI Note 2 mit Tapatalk
[Android] guyzz6370:
xiaomi mi 8 (dipper)
[Android] tribual:
Check PM...

Gesendet von meinem MI Note 2 mit Tapatalk
[Android] DiamondJohn:
GIT Question

I know this may be a little OT, but I posted the same question almost 15 months ago in what I thought would be the appropriate thread, but I have gotten no response.:( https://xdaforums.com/showpost.php?p=76303226&postcount=61

Basically I am confused by the dates the web interface to git is presenting for the dates of changes :confused:

If I browse to the root of the resoitory for Havoc-OS at https://github.com/Havoc-OS it reports the latest commits as occurring 13 hours ago.

However, if I click on that repository (https://github.com/Havoc-OS/android_frameworks_av) the commit date shows as occurring 14 days ahgo:eek::confused:

And if I click on the commits within that repository, the date shows as being 14 days ago:confused:

https://github.com/Havoc-OS/android_frameworks_av/commits/pie

Is there an explanation why the root page shows a different date to the other pages?

I use the first page to help me decide if there are enough significant changes to warrant doing a new build. Usually the dates align between pages, but now and then (usually when its been a while since the last actual commit) they disagree. I think the original question posted shows a case where it flips back and forth between the dates :silly:

Can someone explain the logic?
[Android] thafath:
There is commit date and merge date, commits can be done on some dates, some branches, then those branches get merged in others.
[Android] gipsy.danger:
the commit and merge dates maybe different depending upon the admin who pushes it and later merges it after code review.
[Android] alphamale:
Any seen this https://del.dog/asucunuhek.sql. for msm xtended. Taimen
[Android] Rortiz2:
Hey anyone can help me? When it almost finishes the build, it gives my this error:

building image from target_files RECOVERY...
building image from target_files BOOT...
Traceback (most recent call last):
File "./build/tools/releasetools/make_recovery_patch", line 53, in <module>
main(sys.argv[1:])
File "./build/tools/releasetools/make_recovery_patch", line 49, in main
common.MakeRecoveryPatch(input_dir, output_sink, recovery_img, boot_img)
File "/home/r0rtiz2/cm12.1/build/tools/releasetools/common.py", line 1289, in MakeRecoveryPatch
td_pair = GetTypeAndDevice("/boot", info_dict)
File "/home/r0rtiz2/cm12.1/build/tools/releasetools/common.py", line 1240, in GetTypeAndDevice
return PARTITION_TYPES[fstab[mount_point].fs_type], fstab[mount_point].device
KeyError: '/boot'
build/core/Makefile:1498: recipe for target '/home/r0rtiz2/cm12.1/out/target/product/douglas/obj/PACKAGING/target_files_intermediates/cm_douglas-target_files-355f323cf9.zip' failed
make: *** [/home/r0rtiz2/cm12.1/out/target/product/douglas/obj/PACKAGING/target_files_intermediates/cm_douglas-target_files-355f323cf9.zip] Error 1
make: Leaving directory '/home/r0rtiz2/cm12.1'

Any ideas?

Building cm12.1.

It created the system.img but not the ROM.zip.
[Android] gipsy.danger:
why don't you guys post whole build log?
[Android] secretwolf98:
Help. I'm getting errors on compiling the recovery stage. I'm trying to compile CyanogenMod 11. I got Ubuntu 14.04 on a VM. On this VM, I do have Oracle sun JDK 6 installed properly.
[Android] AmirHRC:
what i need to know if iam building omnirom with lineage os device and kernel trees i heard that i need tom clone some repos from lineage os
[Android] Marcelo_RJ:
Motorola Sanders - Havoc 2.8

Hi, I'm trying to compile Havoc-OS for Motorola Sanders.

Found several bugs, most typos, but now I can't find a solution for this error:

https://del.dog/mupenamiti

It's the my first ROM,so I'm really a NOOB.

Please, if anyone can point me some directions, I'd apreciate it.

P.S. sorry for my bad english.
[Android] secretwolf98:
You need to disable ninja.
[Android] gipsy.danger:
you sure?

as far as i know we need ninja to build.

also log says org.lineageos.platform.internal missing.
[Android] DiamondJohn:
No. You can build without ninja.

I am no gun ROM developer, but I checked the manifest files within Pie Havoc-os, and there is no explicit reference to that repository. I actually searched the whole of Havoc-OS.

https://github.com/Havoc-OS/android...l&unscoped_q=org.lineageos.platform.internalb

So chances are its being included by something in your specific device or vendor or kernel. Search within those for that string.

If its part of your Doze, I build havoc OS for a different device, and I blank out the Doze project.

echo "# dummy" > device/samsung/qcom-common/doze/Android.mk;

This "common" repository is re-used for other ROMs and devices, but is not used to build Havoc-OS ROM, for my device. The resulting ROM doze's well:good:

Also compare it against other devices at https://github.com/Havoc-Devices

https://github.com/search?q=org:Hav...al&unscoped_q=org.lineageos.platform.internal

Also check how it is added to LOS devices

https://github.com/search?q=org:LineageOS+org.lineageos.platform.internal&type=Commits

Maybe you need to simply add the repository to your local manifest.