yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] i42o:
What would you say is different of this room compared to dirty unicorn
[Android Builders Collective] Roger.T:
Okay, guys.

Somehow the album with the ABC wallpapers disappeared...:confused:

I made a new one with the old wallpapers and some new ones for you....:laugh:

Please enjoy it :good::cool:

https://photos.app.goo.gl/izqAY5gRRrkG4Zzu5
[Android Builders Collective] ezio84:
Thanks bro! :victory:
[Android Builders Collective] VictorLapin:
Dude, ping me if you will start to make live wallpapers, I can wrap it in the apk :D:D
[Android Builders Collective] Roger.T:
I hadn't planned until now...[emoji6]

Gesendet von meinem SM-G975F mit Tapatalk
[Android Builders Collective] efan3719:
whoa. very quiet in here. hope everyone is doing well in these crazy times.
[Android Builders Collective] ezio84:
This, i hope all you guys are doing well :highfive:

In the meantime, abc source is always up to date if you have some free time to build :cowboy:
[Android Builders Collective] chrisexv6:
I have some credits on Azure, was able to setup a Linux VM out there and want to use it to build ABC/Android10 for my Pixel 3XL.

Is there a how-to (or even a place to start) somewhere in this thread? 2350 pages, I guess Im too lazy to try and dig it up :)

Thanks in advance.

-Chris
[Android Builders Collective] NYCHitman1:
https://back2basics.io/2020/05/creating-a-android-aosp-build-machine-on-ubuntu-20-04/
[Android Builders Collective] chrisexv6:
Thanks!

I got that far and successfully pulled the Q branch of the repo.

My issue is the missing crosshatch device....do I just grab it from the DU github?

Im not sure if there are any mods done to the device tree for ABC use (I see taimen and bonito are already there in the ABC repo but I wanted to build for 3XL).

Thanks again.
[Android Builders Collective] NYCHitman1:
You could use the DU repos for that, yeah -- then you'll have to add it to ABC's vendorsetup.sh to initialize it.
[Android Builders Collective] chrisexv6:
Thanks....that was the piece I was looking for. How to get it to show up on the "lunch combo" menu.

Using ezios build script it looks like it doesnt matter if its on the lunch menu, but I felt better making it show up like bonito and taimen.

Finally got it at least starting to build....will babysit it and see how far it gets.

Thanks again.

-Chris
[Android Builders Collective] chrisexv6:
Build is running (has been for almost 2 hours).

Slow going but it is going.....kernel seems to take a long time to build!
[Android Builders Collective] chrisexv6:
OK - it looks like the build got almost all the way to the end, but failed. Could not find the vendor image. Any suggestions?:

++++ radio ++++

Traceback (most recent call last):
File "build/make/tools/releasetools/add_img_to_target_files", line 949, in <module>
main(sys.argv[1:])
File "build/make/tools/releasetools/add_img_to_target_files", line 943, in main
AddImagesToTargetFiles(args[0])
File "build/make/tools/releasetools/add_img_to_target_files", line 893, in AddImagesToTargetFiles
CheckAbOtaImages(output_zip, ab_partitions)
File "build/make/tools/releasetools/add_img_to_target_files", line 562, in CheckAbOtaImages
assert available, "Failed to find " + img_name
AssertionError: Failed to find vendor.img
ninja: build stopped: subcommand failed.
05:26:29 ninja failed with: exit status 1
build/make/core/main.mk:21: recipe for target 'run_soong_ui' failed
make: *** [run_soong_ui] Error 1
[Android Builders Collective] fKm:
https://git.dirtyunicorns.com/DirtyUnicorns/android_vendor_images
[Android Builders Collective] chrisexv6:
It doesn't need to get built?

I figured it did as part of the build process.
[Android Builders Collective] fKm:
Just clone into vendor/images and you are fine.
[Android Builders Collective] chrisexv6:
Got the build to complete...have not flashed the output file yet, because I had a question:

https://back2basics.io/2020/05/creating-a-android-aosp-build-machine-on-ubuntu-20-04/ mentions to grab the driver binaries. Is that necessary, or is that covered by the DU device tree?

I did not download the Google binaries....it built fine, but I wanted to make sure Im not missing important hardware files or drivers before I try to flash it.

Thanks.
[Android Builders Collective] fKm:
You dont need the driver binaries, that is only needed for pure AOSP. Just make sure you have this repo in vendor/codeaurora/telephony:

https://github.com/DirtyUnicorns/android_vendor_codeaurora_telephony

Otherwise you are not able to receive SMS.
[Android Builders Collective] chrisexv6:
Thanks again. It looks like I did not, but (another) question -

Is that repo compiled into vendor.img? Im currently using a prebuilt vendor.img from DU, so Im not actually building vendor.img (could never figure out why its not hitting the make target for vendor, so I just grab it already done from DU)

Thanks.
[Android Builders Collective] NYCHitman1:
When you use prebuilt, like we do -- you aren't building any vendor images. Instead, it just gets copied into the product out dir.
[Android Builders Collective] chrisexv6:
Got that part.

So is the codeaurora vendor repo unnecessary? Because vendor is a prebuilt?
[Android Builders Collective] NYCHitman1:
That repo isn't necessary for Pixel 3.
[Android Builders Collective] chrisexv6:
Perfect, thanks!

I think the build is good, I dont think I flashed it correctly though. I didnt do any factory wiping so it looks like I have remnants of the ROM before this.

Will do reset(s) and reflash and see if it works.
[Android Builders Collective] fKm:
Hey guys, I am trying to compile PixelDust CAF (https://github.com/pixeldust-project-caf) for Op8Pro with this device tree: https://github.com/fKm86/android_device_oneplus_oneplus8/tree/test

I get this strange sdclang error: https://del.dog/arebaningu.txt

Can someone help please?
[Android Builders Collective] Roger.T:
Pretty quiet here...[emoji16]

Gesendet von meinem ONEPLUS 6 mit Tapatalk
[Android Builders Collective] indian84:
Yea. Has been for a while.

Was one of the most active threads on XDA..
[Android Builders Collective] VictorLapin:
Everyone moved on, it seems :)
[Android Builders Collective] a g bell:
Still waiting for ABC caf?
[Android Builders Collective] NYCHitman1:
I would suggest not holding your breath for that one lol
[Android Builders Collective] a g bell:
?Lol
[Android Builders Collective] letmedanz:
You can do it, AG!
[Android Builders Collective] ezio84:
Legend says Doctor Strange looked at all 14 million different futures and... nope, none of them had a Caf ABC :D
[Android Builders Collective] a g bell:
Hmm maybe tomorrow ??

---------- Post added at 07:54 AM ---------- Previous post was at 07:51 AM ----------

Not one???
[Android Builders Collective] Surge1223:
Ahem, correction 14,000,605 futures.

These rookie marvel movie watchers are killing me
[Android Builders Collective] ezio84:
#blameGoogleSearch :D
[Android Builders Collective] a g bell:
Aha there is still hope ?
[Android Builders Collective] colt2x:
Hi,

Sorry if the question is dumb.

I just finished a test build for LG L70 (w5), from official Lineage 14.1, based on the official documentation . Booted successfully, and i see that security string is 2020-10-05.

It's strange as Android 7 is not supported by Google, is not updated.

Where is this string come from? I have seen that the default mk file is containing it, but the question is that is only a value, or it has really pulled some patches from the Google repos?

Another, where can i find any information about Android version support periods? (How long will be 8.x supported with security patches?)

Thanks for any clarification :)
[Android Builders Collective] ipdev:
LineageOS (cm 14.1)

review.lineageos.org Link

November is not merged yet. ;)

Android Security Bulletins

source.android.com Link

Cheers. :cowboy:
[Android Builders Collective] colt2x:
Thanks! :)

Wow. I haven't known that CM14.1 is still maintained by LineageOS team :) But i asked because i know that Android 7 is no longer maintained. In the meantime i discovered that the last patch for 7.x was in 2019 summer, am i right? So regardless to the security pack, the build is not up to date by security viewpoint. (So i'm going to port 8 to my device :S )

I have seen the security bulletin page but i'm curious about how long Google releases security patches for each version?
[Android Builders Collective] ezio84:
Like ipdev linked, even if Android 7 doesn't get any update from Google, Lineage still adds the main security patches to the old source.

It's not like having a fully updated Q or R source (blobs and other stuff are old on those devices), but from a security perspective you can still feel pretty safe.
[Android Builders Collective] colt2x:
Thanks,

Where can i found that how long the code will be maintained? Lineage 14.1 on my phone is not under official support anymore.
[Android Builders Collective] ezio84:
I don't know, don't think there's a timeline for those old sources.
[Android Builders Collective] colt2x:
This is why i'm began to do the build of a more recent kernel and Android version for my L70, but i'm stuck that there is no usable description of how to compile a kernel for any "non-existing" device. Offical Google guides are not applicable.
[Android Builders Collective] ipdev:
A little late but..

Merry Christmas

Wish goodwill to all in this crazy year.

Cheers.🎅
[Android Builders Collective] ezio84:
Merry Christmas everyone!
[Android Builders Collective] ipdev:
It seems that Google left (or added back) the 2-button navigation in stock Android 11 for bonito.

bonito-rq1a.210205.004

Would it be feasible to add 2-Button navigation into abc 11? :unsure:

Cheers all. :cowboy:
[Android Builders Collective] Meowdib:
https://xdaforums.com/t/module-2-button-navigation-mode.4204779/ try this
[Android Builders Collective] ipdev:
Thank you. (y)

Not quite what I was looking for but, a nice work-around. ;)

If the overlay is added (incorporated) into abc, then no root/Magisk needed. :)

Cheers. :cowboy:
[Android Builders Collective] ezio84:
Sorry, big nope on this :p

I love full gesture nav (even more with those few custom actions on abc), and anyway the 2 buttons is going to be killed soon by Google (for me they can even kill 3 buttons lol).
[Android Builders Collective] ipdev:
I have no problem with 3 button going away. :p

Guess I will have to get use to gestures. :)

Cheers all. :cowboy:
[Android Builders Collective] wrongway213:
ABC ROM for Pixel 4XL aka Coral

ROM, boot img, dtbo: https://drive.google.com/drive/folders/1C_VVma9fyqvdFUP3nZCqzXunzwmS3NuE?usp=sharing

Source: https://github.com/ezio84

Device, kernel & vendor: https://github.com/ABCP4XL

Enjoy!
[Android Builders Collective] ezio84:
Nice job mate! :D

As a reminder for all, here are all the custom commits for R:

scripts/My_mods-commits_and_tips/Commits-list-with-links ANDROID 11.txt at r · ezio84/scripts

Build scripts, tip and tricks, custom commits list, vendor blobs extraction - ezio84/scripts

github.com

And the actual abc R manifest:

GitHub - ezio84/abc_manifest

Contribute to ezio84/abc_manifest development by creating an account on GitHub.

github.com
[Android Builders Collective] wrongway213:
ABC ROM for Pixel 4XL aka Coral 02-15

ROM, boot img, dtbo: https://drive.google.com/drive/folders/1C_VVma9fyqvdFUP3nZCqzXunzwmS3NuE?usp=sharing

Source: https://github.com/ezio84

Device, kernel & vendor: https://github.com/ABCP4XL

Changelog: Built with Sultan Kernel inline

Enjoy!
[Android Builders Collective] PabloHostiaPuta:
Is anyone still with the ABCRom project for Taimen? Do you update frequently? If it is send me this link please
[Android Builders Collective] wrongway213:
ABC ROM for Pixel 4XL aka Coral 03-11

ROM, boot img, dtbo: https://drive.google.com/drive/folders/1C_VVma9fyqvdFUP3nZCqzXunzwmS3NuE?usp=sharing

Source: https://github.com/ezio84

Device, kernel & vendor: https://github.com/ABCP4XL

Changelog: March update

Enjoy!
[Android Builders Collective] buffal0b1ll:
The source is updated monthly and up to date on March security patch. It's sync and build ready. https://github.com/ezio84/abc_manifest
[Android Builders Collective] buffal0b1ll:
Go to this telegram chat Google Pixel 2/XL | Chat™

Google Pixel 2 & Pixel 2 XL | Official Telegram Group

Our Channel: @Pixel2Updates

Google Pixel 1 Channel: @Pixel1Updates

Google Pixel 1 Group: @Pixel1Chat

Google Pixel 2/XL | Chat

ℹ️ Google Pixel 2 & 2 XL Group Chat | Channel: @Pixel2Updates	👥 Our Community	• Google Internal: @GoogleInternal	• MY Theme: @MaterialYouTheme	• Pixel Hub: @PixelHubUpdates	• Pixel 1: @Pixel1Updates	• Pixel 5: @Pixel5Channel	• Pixel 6: @Pixel6Updates

t.me

I put a taimen build up there
[Android Builders Collective] el_Lechu:
Hello,

I'm trying to compile and run AOSP v11 for Pixel3. Compiling and running for unsigning build is OK. But when I'm trying to sign built, it fails to complile. After compiling and generating keys, I'm trying to run "sign_target_files_apks" and getting error:

2021-03-17 09:30:14 - build_super_image.py - WARNING : Skip building super image
because the following images are missing from target files:
/tmp/targetfiles-7BesPD/IMAGES/vendor.img
Traceback (most recent call last):
File "/root/android-11.0.0_r29/out/soong/host/linux-x86/bin/sign_target_files_
apks/internal/stdlib/runpy.py", line 174, in _run_module_as_main
File "/root/android-11.0.0_r29/out/soong/host/linux-x86/bin/sign_target_files_
apks/internal/stdlib/runpy.py", line 72, in _run_code
File "/root/android-11.0.0_r29/out/soong/host/linux-x86/bin/sign_target_files_
apks/__main__.py", line 12, in <module>
File "/root/android-11.0.0_r29/out/soong/host/linux-x86/bin/sign_target_files_
apks/internal/stdlib/runpy.py", line 174, in _run_module_as_main
File "/root/android-11.0.0_r29/out/soong/host/linux-x86/bin/sign_target_files_
apks/internal/stdlib/runpy.py", line 72, in _run_code
File "/root/android-11.0.0_r29/out/soong/host/linux-x86/bin/sign_target_files_
apks/__main__.py", line 12, in <module>
File "/root/android-11.0.0_r29/out/soong/host/linux-x86/bin/sign_target_files_
apks/internal/stdlib/runpy.py", line 174, in _run_module_as_main
File "/root/android-11.0.0_r29/out/soong/host/linux-x86/bin/sign_target_files_
apks/internal/stdlib/runpy.py", line 72, in _run_code
File "/root/android-11.0.0_r29/out/soong/host/linux-x86/bin/sign_target_files_
apks/sign_target_files_apks.py", line 1348, in <module>
File "/root/android-11.0.0_r29/out/soong/host/linux-x86/bin/sign_target_files_apks/sign_target_files_apks.py", line 1341, in main
File "/root/android-11.0.0_r29/out/soong/host/linux-x86/bin/sign_target_files_apks/add_img_to_target_files.py", line 993, in main
File "/root/android-11.0.0_r29/out/soong/host/linux-x86/bin/sign_target_files_apks/add_img_to_target_files.py", line 943, in AddImagesToTargetFiles
File "/root/android-11.0.0_r29/out/soong/host/linux-x86/bin/sign_target_files_apks/add_img_to_target_files.py", line 572, in CheckAbOtaImages
AssertionError: Failed to find vendor.img

I have downloaded drivers and vendor image from "https://developers.google.com/android/drivers" and I have unpacked it before compiling so vendor.img is OK and is present in "aosp_blueline-target_files-eng.root.zip".

What I'm doing wrong that "sign_target_files_apks" not seeing vendor.img?
[Android Builders Collective] fKm:
Hey guys, I am trying a bringup of OnePlus 8 Pro for PixelDust but I am having a hard time with one error:

Starting compilation

============================================
PIXELDUST_VERSION=PixelDust-Eleven-aosp-instantnoodlep-user-20210330-1212
TARGET_BUILD_VARIANT=user
TARGET_ARCH=arm64
TARGET_ARCH_VARIANT=armv8-a
TARGET_CPU_VARIANT=generic
BUILD_ID=RQ2A.210305.006
PRODUCT_SOONG_NAMESPACES=device/oneplus/instantnoodlep vendor/oneplus/sm8250-common device/oneplus/sm8250-common device/oneplus/common vendor/oneplus/instantnoodlep vendor/pixeldust/apex
============================================
Environment variable BUILD_NUMBER was modified (f24fe94d0d => 5e6dff2e0e), regenerating...
[100% 31/31] initializing build system ...
Disabling ART_BUILD_TARGET_DEBUG
Disabling ART_BUILD_HOST_DEBUG
[ 97% 37/38] finishing build rules ...
FAILED:
device/oneplus/sm8250-common/audio_amplifier/Android.mk: error: "audio_amplifier.kona (SHARED_LIBRARIES android-arm64) missing audio.primary.kona (SHARED_LIBRARIES android-arm64)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
device/oneplus/sm8250-common/audio_amplifier/Android.mk: error: "audio_amplifier.kona (SHARED_LIBRARIES android-arm) missing audio.primary.kona (SHARED_LIBRARIES android-arm)"
You can set ALLOW_MISSING_DEPENDENCIES=true in your environment if this is intentional, but that may defer real problems until later in the build.
build/make/core/main.mk:963: error: exiting from previous errors.
12:18:04 ckati failed with: exit status 1

#### failed to build some targets (05:23 (mm:ss)) ####

Build failed!

I don't understand why the error occurs because audio_amplifier.kona is built here: https://github.com/fKm86/android_de...964ec7a62f7b74a8b6683e8b1f77c7/common.mk#L131

I guess I am missing some repo or stuff but I have no clue which one. Maybe someone can help me out here.
[Android Builders Collective] Lowxorx:
Same problem here with the K30 Pro. Have you found a solution ?
[Android Builders Collective] fKm:
No. The only "solution" was to delete the whole audio_amplifier folder from device tree.

After I got rid or that error I got some others and I was not able to fix them. Seems like PixelDust is not ready for CAF and it won't be ready in this Android cycle. In A12 it will be different.
[Android Builders Collective] 73sydney:
Any chance you could also pop a link in this thread going forward, for those of us Pixel 2XL folks who dont use Telegram ?

TIA

p.s. RCS chat is broken (chat features unavailable for this device) for my Pixel 2XL here in Australia. First ROM ive ever had it fail on.

update: I have to apologise, i have a Google account back end problem Google are looking into,

the symptoms being RCS wont enable and my Google pay is totally dead. Google is currently working on it.

Having a great end of week here :)
[Android Builders Collective] ninjasumit:
Link for taimen: https://www.dropbox.com/sh/pwh7kvui6k0w133/AAAQDX5iUEwX2g7J_AVXlN7pa?dl=0

Updated link: https://androidfilehost.com/?w=files&flid=323959
[Android Builders Collective] 73sydney:
Just a quick report in on the latest Taimen build: abc_taimen-v11-20210620-1024-OFFICIAL

RCS (Chat features) still broken in ROM despite correct APN and even VoLTE settings correctly picked up. Not a dealbreaker.

ROM seems to allow me to use my banking apps, Samsung Pay, Google Pay with the exact same Magisk (& Riru/Riru-Momohider) setup and restored apps as other ROM i usually use as a daily. Very few ROMS pass this test :) I think this is only the 3rd ROM...

Last time i tested i had a Google backend issue caused by my previous bank spewing false data at my Google Pay account...so this is refreshing :)

My thanks to @buffal0b1ll and @ninjasumit
[Android Builders Collective] buffal0b1ll:
Chat features should work. It works for me on abc sunfish. If you didn't disable chat features on the previous build you used that could be the problem. You can go on a PC and disable chat features in this portal and then try to set it up again on the phone. https://www-howtogeek-com.cdn.amppr...onnect-your-phone-number-from-rcs-on-android/
[Android Builders Collective] 73sydney:
It a weird one, ive only ever seen it on one other ROM (Havoc for my device), and only just recently

Funny thing is when i flash back to a known working ROM, it works again.

So i dont think its some sort of stuck session. Nevertheless i have visited the manual RCS cutoff page linked, and done the number and code steps. So far no change at all , screen shows the same message, before and after

Will update if it changes, hiostory tells em it wont. Like i said, not a deal breaker.

ROM is fantastic otherwise
[Android Builders Collective] 73sydney:
Update:

Just now received a Carrier Services update from Google...guess what's working again....RCS

Looks like I can't of been the only person with the issue :)
[Android Builders Collective] 73sydney:
New ABC for Walleye (Pixel 2)/Taimen (Pixel 2XL) builds up thanks to @buffal0b1ll & @ezio84

ABCrom v11 - OFFICIAL | Android 11

Updated: 20/8/2021 walleye, 23/08/2021 taimen

Changelog:

• Upstream kernel 4.4.281

Notes:

• Installation instructions in readme.txt in link above

• Feature list for ABCrom

(https://github.com/ezio84/scripts/blob/r/My_mods-commits_and_tips/Commits-list-with-links%20ANDROID%2011.txt)• SafetyNet passes with or without Magisk

• Includes gapps and vendor

Download:

Walleye (Pixel 2): https://androidfilehost.com/?w=files&flid=288005

Taimen (Pixel 2XL): https://androidfilehost.com/?w=files&flid=323959
[Android Builders Collective] ezio84:
Glad someone still likes old beloved Pixels! :D
[Android Builders Collective] 73sydney:
Luckily i dont suffer from the aspirational technology cancer thats infected so many, thanks to primarily Apple, i dont need a new device every 6 months...

Still works a treat, the old Pixel 2XL...only just out of official support, and theyre about to release the 6, which is good, but people like yourself and Bill have extended its life even further...good luck getting that kind of usage out of a CrApple product

p.s. Im also still rocking my old Core i7-4790 - still cranks...recently played Sniper Ghost Warrior Contracts 2 on it, using the ancient (2012) ATI HD7870 attached to it. Didnt skip a beat....who needs a $1,000 video card :)
[Android Builders Collective] 73sydney:
New ABC for Walleye (Pixel 2)/Taimen (Pixel 2XL) builds up thanks to @buffal0b1ll & @ezio84

ABCrom v11 - OFFICIAL | Android 11

Updated: 27/8/2021

Changelog:

• Upstream unicornblood kernel to 4.4.282

Notes:

• Installation instructions in readme.txt in link above

• Feature list for ABCrom

(https://github.com/ezio84/scripts/b...d_tips/Commits-list-with-links ANDROID 11.txt)

• SafetyNet passes with or without Magisk

• Includes gapps and vendor

Walleye (Pixel 2): https://androidfilehost.com/?w=files&flid=288005

Taimen (Pixel 2XL): https://androidfilehost.com/?w=files&flid=323959
[Android Builders Collective] 73sydney:
New ABC for Walleye (Pixel 2)/Taimen (Pixel 2XL) builds up thanks to @buffal0b1ll & @ezio84

ABCrom v11 - OFFICIAL | Android 11

Updated: 7/9/2021

Changelog:

• Upstream unicornblood kernel to 4.4.283

Notes:

• Installation instructions in readme.txt in link above

• Feature list for ABCrom

(https://github.com/ezio84/scripts/blob/r/My_mods-commits_and_tips/Commits-list-with-links ANDROID 11.txt)

• SafetyNet passes with or without Magisk

• Includes gapps and vendor

Walleye (Pixel 2): https://androidfilehost.com/?w=files&flid=288005

Taimen (Pixel 2XL): https://androidfilehost.com/?w=files&flid=323959
[Android Builders Collective] 73sydney:
And a day later, more goodness was to come unto us, that are the faithful...

New ABC for Walleye (Pixel 2)/Taimen (Pixel 2XL) builds up thanks to @buffal0b1ll & @ezio84

ABCrom v11 - OFFICIAL | Android 11

Updated: 8/9/2021

Changelog:

• September patch

Notes:

• Installation instructions in readme.txt in link above

• Feature list for ABCrom

(https://github.com/ezio84/scripts/blob/r/My_mods-commits_and_tips/Commits-list-with-links ANDROID 11.txt)

• SafetyNet passes with or without Magisk

• Includes gapps and vendor

Walleye (Pixel 2): https://androidfilehost.com/?w=files&flid=288005

Taimen (Pixel 2XL): https://androidfilehost.com/?w=files&flid=323959