yashsingh1/xdaforums huggingface dataset:
[Android] Simon1511:
First, thanks for your reply :)

The repo commands I used were

repo init --depth=1 -u https://github.com/omnirom/android.git -b android-9.0

and

repo sync -f --force-sync --no-clone-bundle --no-tags -j12

so I only had to sync around 30 GB.

My local_manifest looks like this:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/samsung/a5y17lte" name="LineageOS/android_device_samsung_a5y17lte" remote="github" revision="lineage-16.0" />
<project path="device/samsung/universal7880-common" name="LineageOS/android_device_samsung_universal7880-common" remote="github" revision="lineage-16.0" />
<project path="hardware/samsung" name="LineageOS/android_hardware_samsung" remote="github" revision="lineage-16.0" />
<project path="hardware/samsung_slsi/exynos5" name="LineageOS/android_hardware_samsung_slsi-cm_exynos5" remote="github" revision="lineage-16.0" />
<project path="hardware/samsung_slsi/openmax" name="LineageOS/android_hardware_samsung_slsi-cm_openmax" remote="github" revision="lineage-16.0" />
<project path="hardware/samsung_slsi/exynos" name="LineageOS/android_hardware_samsung_slsi-cm_exynos" remote="github" revision="lineage-16.0" />
<project path="kernel/samsung/universal7880" name="LineageOS/android_kernel_samsung_universal7880" remote="github" revision="lineage-16.0" />
<project path="vendor/samsung/universal7880-common" name="TheMuppets/proprietary_vendor_samsung" remote="github" revision="lineage-16.0" />
</manifest>

At this moment my phone has bootloader and modem from february, but I will try updating to a newer version.

The output zip is 503 MB large, took around 2h 30min to compile.

Yes, I modified the device tree from lineage to omni to make it work.

Hope this helps :)
[Android] DiamondJohn:
Newer is not necessarily better. The device tree will be built with specific binaries which usually align to a specific bootloader and modem. Maybe look at the commits to see if there are any comments on the commit detailing exactly which modem and bootloader it is built for.

I used to have an older phone where the newer binaries ONLY worked in KitKat BootLoader ROMs (ie the ROM acted exactly like yours), and the JellyBean Bootloader only worked in JBBL ROM's; I was building Nougat ROMs using a JBBL. I had another device that once you upgraded the Bootloader, downgrading it caused a hard brick:mad: I think it would be rare, but just beware.
[Android] Rortiz2:
Hi all,

I'm compiling CM13 for BQ Aquaris M8 but I'm facing an issue when it almost finishes... IDK how I can fix that error. Can anyone help me?:

target Executable: ssh (/root/android/system/out/target/product/aquaris_m8/obj/EXECUTABLES/ssh_intermediates/LINKED/ssh)
clang: error: linker command failed with exit code 1 (use -v to see invocation)
build/core/shared_library_internal.mk:80: recipe for target '/root/android/system/out/target/product/aquaris_m8/obj_arm/SHARED_LIBRARIES/libLLVM_intermediates/LINKED/libLLVM.so' failed
make: [/root/android/system/out/target/product/aquaris_m8/obj_arm/SHARED_LIBRARIES/libLLVM_intermediates/LINKED/libLLVM.so] Error 1
make: Waiting for unfinished jobs....
make: Leaving directory '/root/android/system'

Thanks!
[Android] srgrusso:
Hey, It's me again. This time I'm buildeing RevengeOS for the SM-T820 Galaxy Tab S3. I'm getting the following error.

error: lineage-sdk/Android.bp:106:1: "org.lineageos.platform.internal" depends on undefined module "telephony-ext"

Which repo do I need to add to get this? I tried adding "<project name="LineageOS/android_hardware_lineage_telephony" path="hardware/lineage/telephony" remote="github" revision="lineage-16.0" />" but I'm still getting this error. This is a wifi only tablet. So do I really need this or is there a way to avoid building this?

Thanks and as always your help is greatly appreciated
[Android] quake73:
You need vendor/codeaurora/telephony.
[Android] Simon1511:
So I updated to newest bootloader and modem, still not booting :(
[Android] abhijiths362:
home/abhivarma362/sky/out/target/product/beryllium/obj/HEADER_LIBRARIES/generated_kernel_headers_intermediates/export_includes', needed by '/home/abhivarma362/sky/out/target/product/beryllium/obj/SHARED_LIBRARIES/power.qcom_intermediates/import_includes', missing and no known rule to make it

plz seomeone help me
[Android] ParanoidNemo:
Getting this error while building AOSP 9 (r44) for suzu (Sony Xperia X). I know that it's already there and I'm following the instruction on the sony open source project but it's mainly a learning experience for me and I want to understand how to solve those problem so that I could learn where to look and maybe in some time start to porting some other ROM.

https://pastebin.com/HD1zLrnb

Thanks for your time.
[Android] NepoRood:
You're getting the "flex" error, need to export a variable:

In .bashrc:

export LANG=C

or

export LC_ALL=C

Either will work, but, I recommend the first :good:

Make that edit, then source your bashrc and try the build again
[Android] ParanoidNemo:
Thanks for your reply. I'd already tried it but with no fortune. Maybe because I'm in a python virtualenv?

--EDIT--

Followed this: https://github.com/sonyxperiadev/bug_tracker/issues/136. The problem was indeed with flex but it was the "version" shipped within prebuild that wasn't correct. Rebuilding it before compiling seems to have done the trick. Now at 98% :fingercrossed:
[Android] DiamondJohn:
I am building on a win7 64b PC running VBox. Within the VBox I am running Ubuntu. I found that because I have many drives on the host, I could get a performance boost by partitioning off components/drive space within the build environment off to different physical hard drives from the host.

So, basically I have the following residing on different drives and being mounted by my FStab file within Ubantu:

The OS - Ubuntu 18 System drive

CCache

Build Out

ROM Source

Swap File

Using the above, from within the windows (ie the host) resource monitor, I can see logically how the ROM source is being read in parallel to the resulting compilation being written to the build out. CCache pretty much operates as expected with mostly writes the first time I build and mostly reads on subsequent builds. The swap file residing on the swap partition is hardly touched until near the end of the build. All this occurs in parallel and does not cause extreme disk thrashing.

What I do not understand is why there are times of high writes occurring to my System Drive???

And is there an equivalent tool like windows resource monitor but for linux (preferably graphical), which shows the io by file and be able to sort the results descending?

Its not causing any issues. The build completes, and it only takes about 50min. It just confuses me when I see it occur, and not understanding annoys me.

------edit------------

In case I wasn't clear what I meant by windows resource monitor. The following image shows whats going on while the OS is booting. And as logically expected, there are 100 times more reads than writes.
[Android] srgrusso:
Ok I'm back to this error.

FAILED: /mnt/UserData/Projects/Android-Source/Syberia-9.0/out/soong/build.ninja
/mnt/UserData/Projects/Android-Source/Syberia-9.0/out/soong/.bootstrap/bin/soong_build -t -l /mnt/UserData/Projects/Android-Source/Syberia-9.0/out/.module_paths/Android.bp.list -b /mnt/UserData/Projects/Android-Source/Syberia-9.0/out/soong -n /mnt/UserData/Projects/Android-Source/Syberia-9.0/out -d /mnt/UserData/Projects/Android-Source/Syberia-9.0/out/soong/build.ninja.d -o /mnt/UserData/Projects/Android-Source/Syberia-9.0/out/soong/build.ninja Android.bp
(0x8ff800,0xc420136a20)error: frameworks/native/services/surfaceflinger/Android.bp:148:1: "libsurfaceflinger" depends on undefined module "display_intf_headers"
Module "libsurfaceflinger" is defined in namespace "." which can read these 1 namespaces: ["."]
Module "display_intf_headers" can be found in these namespaces: ["hardware/qcom/display-caf/msm8996"]
error: frameworks/native/services/surfaceflinger/Android.bp:148:1: "libsurfaceflinger" depends on undefined module "libqdMetaData.system"
Module "libsurfaceflinger" is defined in namespace "." which can read these 1 namespaces: ["."]
Module "libqdMetaData.system" can be found in these namespaces: ["hardware/qcom/display-caf/msm8996" "hardware/qcom/display/msm8909" "hardware/qcom/sdm710"]
error: frameworks/native/services/surfaceflinger/tests/unittests/Android.bp:15:1: "libsurfaceflinger_unittest" depends on undefined module "display_intf_headers"
Module "libsurfaceflinger_unittest" is defined in namespace "." which can read these 1 namespaces: ["."]
Module "display_intf_headers" can be found in these namespaces: ["hardware/qcom/display-caf/msm8996"]
error: frameworks/native/services/surfaceflinger/tests/unittests/Android.bp:15:1: "libsurfaceflinger_unittest" depends on undefined module "libqdMetaData.system"
Module "libsurfaceflinger_unittest" is defined in namespace "." which can read these 1 namespaces: ["."]
Module "libqdMetaData.system" can be found in these namespaces: ["hardware/qcom/display-caf/msm8996" "hardware/qcom/display/msm8909" "hardware/qcom/sdm710"]
ninja: build stopped: subcommand failed.

I have imported these 3 repos:

<project name="LineageOS/android_hardware_qcom_audio" path="hardware/qcom/audio-caf/msm8996" remote="github" revision="lineage-16.0-caf-8996" />

<project name="LineageOS/android_hardware_qcom_display" path="hardware/qcom/display-caf/msm8996" remote="github" revision="lineage-16.0-caf-8996" />

<project name="LineageOS/android_hardware_qcom_media" path="hardware/qcom/media-caf/msm8996" remote="github" revision="lineage-16.0-caf-8996" />

I have this in my BoardConfig.mk:

# CAF HALs

TARGET_QCOM_MEDIA_VARIANT := caf-msm8996

TARGET_QCOM_DISPLAY_VARIANT := caf-msm8996

PRODUCT_SOONG_NAMESPACES += \

hardware/qcom/display-$(TARGET_QCOM_DISPLAY_VARIANT) \

hardware/qcom/media-$(TARGET_QCOM_MEDIA_VARIANT)

I'm not sure what I am doing wrong.
[Android] dungphp:
Hardwares named as: audio-caf-msm8996, display-caf-msm8996, media-caf-msm8996

in hardware/qcom/
[Android] ArcherTanu:
Guyzz how solve this error im getting this for libwifi.qcom_intermefiates for aosip build

Problem solve.. Gsi/treble build problem.. :)
[Android] kylek389:
Compiling phhusson aosp90 Treble

I'm attempting to build phhusson's vanilla aosp90 Treble ROM using provided "../build-dakkar.sh aosp90 arm64-aonly-vanilla-su" script, however it is failing at 51% mark, it still fails at same spot after I manually try to restart the build:

kyle@pop-os:~/treble_experimentations/MYROM$ rom_fp="$(date +%y%m%d)"
kyle@pop-os:~/treble_experimentations/MYROM$ make BUILD_NUMBER="$rom_fp" -j 12 systemimage
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=9
TARGET_PRODUCT=aosp_arm
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=generic
HOST_ARCH=x86_64
HOST_2ND_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-5.0.0-21-generic-x86_64-Pop!_OS-19.04
HOST_CROSS_OS=windows
HOST_CROSS_ARCH=x86
HOST_CROSS_2ND_ARCH=x86_64
HOST_BUILD_TYPE=release
BUILD_ID=PQ3B.190705.003
OUT_DIR=out
============================================
ninja: no work to do.
ninja: no work to do.
wildcard(out/target/product/generic/clean_steps.mk) was changed, regenerating...
$(file <out/build_number.txt) was changed, regenerating...
[25/1151] including development/build/Android.mk ...
development/build/build_android_stubs.mk:43: warning: android_stubs_current
development/build/build_android_stubs.mk:43: warning: metalava_android_stubs_current metalava_android_stubs_current
development/build/build_android_stubs.mk:43: warning: android_system_stubs_current
development/build/build_android_stubs.mk:43: warning: android_test_stubs_current
development/build/build_android_stubs.mk:43: warning: metalava_android_system_stubs_current metalava_android_system_stubs_current
development/build/build_android_stubs.mk:43: warning: metalava_android_test_stubs_current metalava_android_test_stubs_current
[571/1151] including system/sepolicy/Android.mk ...
system/sepolicy/Android.mk:79: warning: BOARD_SEPOLICY_VERS not specified, assuming current platform version
[1151/1151] including vendor/vndk-tests/Android.mk ...
[ 0% 8/39579] //frameworks/base/core/res:framework-res aapt2 compile frameworks/base/core/res/res 75
FAILED: out/soong/.intermediates/frameworks/base/core/res/framework-res/android_common/aapt2/frameworks/base/core/res/res/raw_nodomain.html.flat out/soong/.intermediates/...
...
...
error: invalid file path 'frameworks/base/core/res/res/values/config.xml.orig'.
[ 0% 19/39579] //prebuilts/sdk/current/extras/material-design:android-support-design-dialog aapt2 link
ninja: build stopped: subcommand failed.
23:48:36 ninja failed with: exit status 1

#### failed to build some targets (35 seconds) ####

The file "frameworks/base/core/res/res/values/config.xml.orig" is present.
[Android] Soumy1234:
Did you add some sort of extra patch? I ask because I once added signature spoofing to my ROM using a patch file and it created extra .orig files that caused conflicts during build. Look for all .orig files in frameworks/base and move them somewhere else or delete them.
[Android] nicesoni_ash:
Always upload the full log to some external site like pastebin, just showing an error doesn't always help. This file shouldn't even be there.

Sent from my "1+2" powered by Delight Oreo

Compiled by myself
[Android] kylek389:
That was it! I'm glad you saw my post and replied, I was hesitating to even ask thinking nobody would help. Yes I patched in Signature Spoofing functionality, this is the 1 and only change I made to the source code, the whole reason behind compiling my own phhusson Treble aosp9.0 is because I want a better functioning microG that I install using NanoDroid. The "frameworks/base/core/res/res/values/config.xml.orig" file is a backup that "patch" utility made. It all makes sense now. I reran the compile at got to 97% mark, now I'm stuck on:

[ 97% 38767/39589] Target Java: out/target/common/obj/APPS/Bluetooth_intermediates/classes-full-debug.jar
FAILED: out/target/common/obj/APPS/Bluetooth_intermediates/classes-full-debug.jar
...
packages/apps/Bluetooth/src/com/android/bluetooth/hearingaid/HearingAidService.java:611: error: cannot find symbol
mAudioManager.setHearingAidDeviceConnectionState(mPreviousAudioDevice,

Full log here, fails at 97% mark. Thanks. I'm using Ubuntu 19.04 and followed phhusson's wiki guide: How to build a GSI?
[Android] nicesoni_ash:
I doubt that you had made any changes to bluetooth repo since you only tried to add microg patches but it look likes there's some issues with your Bluetooth repo. Either try to sync it again with official sources or try it to fix it yourself. Compiler is not able to find setHearingAidDeviceConnectionState reference.

Sent from my "1+2" powered by Delight Oreo

Compiled by myself
[Android] ArcherTanu:
Im successfuly compile and boot in to aosip and aex builds but my wifi is not starting (tougles not working)both of them.. Here is my device matlog. Please some one help..

This is matlog..https://pastebin.com/ptpigDGE
[Android] gipsy.danger:
line 229

create a sepolicy to address the denied service.
[Android] ArcherTanu:
Problem solve... Thnx man
[Android] alphamale:
Getting following error with stag os for taimen. https://del.dog/sopibifija.sql
[Android] guyzz6370:
How do the developers do it? How is gapps or any apk bundled together and when you install the final .zip , all the bundled apps are there? I want to do the same thing, just not adding apps but selectively removing certain apps i don't want. Seems very simple..just don't know where to look
[Android] SubwayChamp:
It doesn't seem and is not at all a simple thing you would need to learn from the start how to build from the source to include/exclude some system app and the link posted above is a good example of a thread to start with.

In previous Android versions was more easy to mod a rom including some apps just inside the zip usually in data or vendor/data and with the proper script but this is not build from the source, is just modify a rom that is already made.
[Android] guyzz6370:
How do I modify a ROM that is already made? I have the zip file, what do to with it? Where are the APKs?

You've been very helpful, so thanks a lot, I hope I'm not asking you too many questions :D
[Android] ArcherTanu:
I think u r missing sone dependences.
[Android] DiamondJohn:
OK, so if you are compiling the ROM from source, then commonly, included pre-compiled APK's will be included in the ROMs custom vendor make files. For example, I compile Havoc-OS and you can see that the first batch of commands includes the calculator apk.

https://github.com/Havoc-OS/android_vendor_havoc/blob/pie/prebuilt/common/Android.mk

Or for projects built as part of the process

https://github.com/Havoc-OS/android_vendor_havoc/blob/pie/config/common.mk

You can see the lines "PRODUCT_PACKAGES += "

If building from source, you will also get more help from the thread https://xdaforums.com/chef-central/android/guide-android-rom-development-t2814763

See above for modifying what gets compiled in. I haven't checked PE specifically, but generally speaking, custom ROMs require you to flash your chosen GApps, which controls what GApps are included. If you flash OpenGApps, there is also a text file you can create to selectively exclude packages.

https://xdaforums.com/android/software/pa-gapps-continuation-t3098071

Now you are asking a completely different question. Again, I don't know PE explicitly, but if its like most other custom ROMs, then the zip will contain a file which I think can be mounted in Linux and modified...and rebuilt... WAAAAY too much effort. To modify the ROM its much easier to simply flash the ROM (and GApps) and then flash your own custom ZIP that removes (or adds) components. These ZIPs are all based on "Edify" scripts. You will see an example in the ROM zip under

META-INF\com\google\android\updater-script

But to remove or replace you will need to learn Edify scripting.
[Android] SubwayChamp:
This kind of things to be honest aren´t not common at all i.e. that to achieve what you want doesn´t worth the effort. I´ll explain briefly just in a general way; to modify an oreo/pie rom (till nougat probably there were more tools) you would need to know/be familiar with some things about at less Python, scripts to can decompile/recompile brotli/payload files (already available on GitHub) and just to push/erase some apks and then flash the zip ONLY on your device so this kind of works can not/may not be shared to a communnity cause is a work that modifies an original work really no sense to it at all.

[MENTION=5417899]DiamondJohn[/MENTION]

I was trying to guess what exactly the member wanted and ever realized that they don´t want compile from source, they just want to look inside the zip and push/pull some apk/mod. Thanks for your explanations, just few times I saw a developer explaining with such clarity and documentation based.
[Android] guyzz6370:
Sorry for all the confusion, but yeah this was a great answer, the one I was looking for..really helped to answer my question.

Ok, now i'm setting up everything to build the rom from source

the PE ROM includes gapps package, how do i know which package they used? was it pico or nano, etc?
[Android] DiamondJohn:
The one link I forgot to include was the actual help thread for building from source.:o You will probably find many people building PE there.

https://xdaforums.com/chef-central/android/guide-android-rom-development-t2814763

When I started, I started with LOS because it had a great resource for building. I found it on https://webchat.freenode.net/?channels=lineageos-dev

Theres probably also one for PE.

I'm surprised it includes GApps.

As you are building from source, they will be pre-builts, so you will find something like the calculator.apk example I showed above, and then modify it as you need.

The github web site also can search within PE. Just know that the pre-builts may be renamed as part of the build.

we both were, I just covered my bases with multiple guesses.;)

You can thank just getting home from a night out and knowing I was going to suffer from insomnia.
[Android] guyzz6370:
Ok, i'm following the guide and the PE sources are downloading as we speak!

Another thing, how do you apply updates yourself? I mean those monthly security updates that google releases every month, like the july 2019, the september 2019, etc..

I noticed the updates are out in the android security bulletin, but sometimes the devs take a long time to update with the patch installed..

I want to install those security updates myself, what needs to be done? I know a patch is just deleting and adding new lines of code to fix bugs. I imagine its simple to do, like a cut and paste kinda thing..?
[Android] DiamondJohn:
WEEEeeeellll beyond the scope of this thread, or most others I would guess. It would be a thread in itself. Try the other thread specific for ROM dev I linked above for a start. Maybe a start would be repo picks, never did it myself. Not a small undertaking.
[Android] guyzz6370:
Ok, so I'm having trouble while syncing, take a look at the vendor_xiaomi repo https://github.com/PixelExperience-Devices/vendor_xiaomi

It is taken down by DMCA..so that's a real bummer..And because of this, I can't complete the build process :(

How do I proceed?
[Android] xunholyx:
That's not the only one that will be taken down.

SenseTime requested a DMCA takedown of 454 Xiaomi vendor repos

https://github.com/github/dmca/blob/master/2019/08/2019-08-09-SenseTime-5.md
[Android] alphamale:
Getting following error with stag oss. Using du trees. For taimen

https://del.dog/ruhayeceye.pl
[Android] guyzz6370:
can't believe this is happening..does this mean I won't be able to proceed with the build? and that nobody is able to build in the future?

there must be a way around this :crying:
[Android] DiamondJohn:
My guess is that the DMCA is specific to a selected portion of the repository, not every single file. As such, if someone finds out what it is that is infringing their copyright, it could be selectively removed, and the rest of the code could be public again. for example without any understanding on my part, this "SenseTime" appears to be likely source of contention. Once its removed, it could be published again, and a build may succeed. I used to own a Moto X, and no custom ROMs could take advantage of their secondary low power CPU's, only the manufacturers firmware could. I would guess because of similar issues.

Also, I haven't done it myself, but I have seen there is a process to retrieve hardware/device/vendor blobs directly from the device.

again, the following thread would get you a lot more visibility with people dealing with the same issues, and possibly have a work-around: https://xdaforums.com/chef-central/android/guide-android-rom-development-t2814763

eg using a different, but similar device vendor tree.
[Android] DiamondJohn:
Just had a thought to check Havoc-Devices https://github.com/Havoc-Devices/proprietary_vendor_xiaomi

also, as I mentioned, the search of github is very useful https://github.com/search?q=vendor_xiaomi
[Android] guyzz6370:
but those are oreo ones, not pie :(

---------- Post added at 08:50 AM ---------- Previous post was at 08:14 AM ----------

Hey! I found this guide >> https://wiki.lineageos.org/extracti...acting-proprietary-blobs-from-file-based-otas

I've followed that guide and managed to obtain a mountable system.img!

And the mount looks like this:

Now the last step is to >>

Here, i don't understand what is meant by

move to the root directory of the sources of your device

I tried the command ./extract-files.sh ~/android/system_dump/ and I got this error:

Need help on this last step..
[Android] guyzz6370:
I'm getting the above error, how do I fix this?

I've been trying for a few days and I'm so excited now that it's 99%...after fixing this the ROM will finally be done
[Android] DiamondJohn:
Use a text host and post more of your log. Something like hastebin.com or del.dog or pastebin.com

It may also help others to help you, if you include links to which device, vendor, kernel and ROM you have used. To be honest, I personally don't read screen shots.