yashsingh1/xdaforums huggingface dataset:
[Android Builders Collective] fKm:
Don't really what you mean?!

Someone knows how to fix this one?

//external/libpng:libpng header-abi-diff libpng.so.abidiff
FAILED: /root/Android/Havoc-OS/out/soong/.intermediates/external/libpng/libpng/android_arm64_armv8-a_cortex-a73_vendor_shared/libpng.so.abidiff
(prebuilts/clang-tools/linux-x86/bin/header-abi-diff -allow-unreferenced-changes -allow-unreferenced-elf-symbol-changes -lib libpng -arch arm64 -o /root/Android/Havoc-OS/out/soong/.intermediates/external/libpng/libpng/android_arm64_armv)
******************************************************
error: VNDK library: libpng's ABI has INCOMPATIBLE CHANGES Please check compatiblity report at : /root/Android/Havoc-OS/out/soong/.intermediates/external/libpng/libpng/android_arm64_armv8-a_cortex-a73_vendor_shared/libpng.so.abidiff
******************************************************
---- Please update abi references by running platform/development/vndk/tools/header-checker/utils/create_reference_dumps.py -l libpng ----

When I do bash development/vndk/tools/header-checker/utils/create_reference_dumps.py -l libpng as it says I only get this:

import-im6.q16: unable to open X server `' @ error/import.c/ImportImageCommand/358.
import-im6.q16: unable to open X server `' @ error/import.c/ImportImageCommand/358.
import-im6.q16: unable to open X server `' @ error/import.c/ImportImageCommand/358.
import-im6.q16: unable to open X server `' @ error/import.c/ImportImageCommand/358.
import-im6.q16: unable to open X server `' @ error/import.c/ImportImageCommand/358.
import-im6.q16: unable to open X server `' @ error/import.c/ImportImageCommand/358.
bash: Android/Havoc-OS/development/vndk/tools/header-checker/utils/create_reference_dumps.py: line 10: syntax error near unexpected token `('
bash: Android/Havoc-OS/development/vndk/tools/header-checker/utils/create_reference_dumps.py: line 10: `from utils import (make_libraries, make_tree, find_lib_lsdumps,'
[Android Builders Collective] kantjer:
I'm running an encrypted (fbe) Pie on angler
[Android Builders Collective] VictorLapin:
Wreaking havoc to Flasher development in the process :D:D
[Android Builders Collective] icxj1:
It is not giving much of a clue on what to look for.
[Android Builders Collective] M1911:
Hi.

I'm om ABC 8.1.0-20180420 and looking forward to pie rom.

Is it a good idea to update to latest oreo before moving to pie (when it comes)?
[Android Builders Collective] buffal0b1ll:
It shouldn't really matter. 8.1 is 8.1

I'd be more concerned with getting your bootloader and radio and TWRP up to date
[Android Builders Collective] neekless:
Which rom? I saw a few pie rom threads on the taimen forum and I've read that they cannot be encrypted. maybe it's a taimen thing?

---------- Post added at 02:54 PM ---------- Previous post was at 02:51 PM ----------

I read some threads for pie roms on taimen and they all said encryption is impossible. Does your abc pie for taimen support encryption?
[Android Builders Collective] fKm:
I still don't know what you mean [MENTION=6014314]neekless[/MENTION]. As I said I haven't tested the taimen build yet but I don't have any problem with encryption or anything else with my taimen and custom rom builds. In which thread was that mentioned? Or do you mean encryption at TWRP? That is possible with the latest TWRP version but has nothing to do with the ROM.
[Android Builders Collective] neekless:
Hmm I think I only saw it in liquidremix telegram chat.. my mistake. What rom are you running on your taimen now? Pixel dust? Are you encrypted?
[Android Builders Collective] fKm:
I am on my BenzoRom build for taimen. Works good though.

With encryption do you mean a pin lock/fingerprint? Then yes. And flashing with the latest TWRP and the pin lock/fingerprint works without any problems.
[Android Builders Collective] neekless:
Actually I mean encryption in settings (shown in attachment). It's different from pin lock/fingerprint as you can still have pin lock/fingerprint while decrypted.

It's ok, I'll try your abc soon (already downloaded it). I know you haven't tested it, but do you know of any issues? Like camera not working etc.
[Android Builders Collective] fKm:
I used the same device tree and blobs (DU) as with BenzoRom so I don't think there are any problems.

Edit: Settings say my phone is encrypted, so no problems with that.
[Android Builders Collective] neekless:
Just flashed your abc but I'm not sure if I'm on abc. 'About phone' doesn't show me abc version (8.1 does). There's no 'Advanced' section in the menu where all the abc settings are. But the bootanimation is abc.
[Android Builders Collective] ezio84:
To clarify, abc "p" branch is just vanilla aosp with a working build tree and framework, no custom features yet.

I won't add anything till i get a solid berkeley device tree bring up on top of emui P vendor.img (atm there are some big issues: no fingerprint enroll, random reboots, no dual sim).

I'm still on Oreo abc :P
[Android Builders Collective] neekless:
OK I'm dumb haha time to go back to oreo
[Android Builders Collective] icxj1:
here is the build breaker.

https://github.com/PiXeN-OS/build_make/commit/b7f00ed2afbd804906a8336dfef62ed10a74d0ef

revert it for a temp fix to get build going again. not sure what the outcome yet.

https://github.com/PiXeN-OS/build_make/commit/4a2926a44e5e9ff208f3a0290ebfc13bb6f26cfd
[Android Builders Collective] greenmasser:
Still having issues with consistent cell service, and messaging. Cell with just drop and not come back until reboot
[Android Builders Collective] alryder:
Does this happen in multiple locations? I did some traveling around Michigan today and did not have any issues with cell service. I'm just wondering if it might be due to the location you are in.
[Android Builders Collective] crypt0kiddie:
Oh snap! There is an Oct build of 8.1 for N6? I'll have to give that a try! Also in Michigan btw. Let you guys know what I find.

Looking forward to Pie too! That being worked on?
[Android Builders Collective] greenmasser:
Interested to hear how it works. Same thing this summer, so he had to revert to Beltz trees in the build. Same location I usually go.
[Android Builders Collective] miksontije:
I cant find option to hide brightness bar from status bar. I did not do clean flash long time, and done it now bcouse little cores start to work 100% and i cant find what is triggering them,phone start to be hot. I try with bbs to find what is it, kernel wakelock, or something else, but everything look normal. Thats why i done clean flash. N5X, buffal0b1II.
[Android Builders Collective] ezio84:
If you're talking about qs panel brightness slider, no, abc never had an option to hide it. It's just useless.
[Android Builders Collective] KelevrA_8:
[MENTION=4118860]davall[/MENTION] do you know if anyone has figured out the Sprint data issues on Taimen? Every ROM I've tried hasn't worked correctly, I remember [MENTION=2095315]ezio84[/MENTION] had a commit on Angler that helped with data https://github.com/ezio84/abc_vendor_huawei/commit/fe561fc50168ca1a0e23029844d3be104c04caa1

Just wondering if this type of thing was still being implemented.
[Android Builders Collective] davall:
No, I'm afraid I don't.

Are you on Oreo or Pie? And what kind of data issues you have?
[Android Builders Collective] KelevrA_8:
Both Oreo and Pie, every ROM I've tried has trouble connecting to LTE, and sending/receiving MMS. Sprint stock has a setting in Mobile Netwrok called carrier settings (connected to SprintDM) that initiates data on Sprint phones, which always crashes on custom ROMs. Back on Angler that same thing was happening and the commit I posted fixed those issues.
[Android Builders Collective] davall:
Ok, thanks. When i've some spare time i will commit the [MENTION=2095315]ezio84[/MENTION] changes from angler to the taimen vendor tree and send you a taimen pie build to test the changes.

---------- Post added at 03:17 PM ---------- Previous post was at 02:51 PM ----------

I already looked at the taimen vendor files.

Android.mk looks ok:

****

include $(CLEAR_VARS)

LOCAL_MODULE := SprintDM

LOCAL_MODULE_OWNER := google

LOCAL_SRC_FILES := proprietary/priv-app/SprintDM/SprintDM.apk

LOCAL_CERTIFICATE := platform

LOCAL_MODULE_TAGS := optional

LOCAL_MODULE_CLASS := APPS

LOCAL_DEX_PREOPT := false

LOCAL_MODULE_SUFFIX := .apk

LOCAL_PRIVILEGED_MODULE := true

include $(BUILD_PREBUILT)

***

For SprintHM it looks the same.

So in my opinion there is nothing to do, sorry.
[Android Builders Collective] ezio84:
Try also to set it like this:

LOCAL_CERTIFICATE := PRESIGNED
[Android Builders Collective] KelevrA_8:
Hey [MENTION=2095315]ezio84[/MENTION] was wondering if you could take a look at this error log I attached maybe you can figure out the issues with Sprint. [MENTION=4118860]davall[/MENTION] has done a great job of helping me out up until this point.
[Android Builders Collective] ezio84:
Hard to say for me, i'd check in the stock factory image if there's some additional qualcomm lib or apk that must be added to the build (or copied from vendor to system).
[Android Builders Collective] linusdan:
Hello

I am trying to port the Dirty Unicorns ROM to my old i9100, however when putting the properties in 'android_build_soong' they are not being recognized.

I put what you need in variable.go and build/make/core/soong_config. mk

What could be happening?

Thank you for anyone who can give me a light.
[Android Builders Collective] davall:
What i miss on my AOSP taimen pie rom is an ongoing notification from the download manager, when i download (huge) files from my doogle drive.

Any of you have had the same experiences on other pie roms? I tried a few with the same result of not showing an ongoing notification.

I think I remember that stock pie android displayed the download progress on google drive downlaods?
[Android Builders Collective] kantjer:
Disabling "Data Transfer Tool" seems to fix that.

Worked for many Pie users on angler
[Android Builders Collective] davall:
That did the trick with a following reboot. Thank you very much :good:
[Android Builders Collective] alryder:
This seems to be corrected with version 3.7.052 released on October 26.
[Android Builders Collective] Phrodini:
Senor, ezio84... Do you use any sound mod?
[Android Builders Collective] ezio84:
Never used them :P
[Android Builders Collective] resarfekim:
Nitin @ Nitrogen ROM was able to get Sprint LTE going by "Syncing APNs with PixelDust ROM".

Though the MMS/SMS issue and "Carrier Properties" crashing still persist.
[Android Builders Collective] Topse:
I have also a old phenom.

I get the same error buidling pie (ubuntu Mate 18.04).

Did you find a solution?
[Android Builders Collective] reference2myself:
Nope, I haven't really messed with it since then. I figured it was because I use Arch and just didn't have the right versions of packages or something configured different from Ubuntu.
[Android Builders Collective] icxj1:
Still in progress, but fixes error. There is also issue with dexpreopt art-profile & boot-profile illegal instructions on Ubuntu.

https://github.com/devil1804/android_build/commit/6a038d662b235c560c54a7da0650037726d44d6b
[Android Builders Collective] fraz14:
This fixed your hidden.api error?

You only picked this one commit?
[Android Builders Collective] icxj1:
I think there is more to come, commit has only been out a week. But yes it fixes that error. Add the flag in your boardconfig.mk.
[Android Builders Collective] fraz14:
Will try.
[Android Builders Collective] wavedashdoc:
So not sure if anyone here would know but we in the shamu thread are unable to get VoLTE to work in Pie. With the new IMS implementation of Pie we've been SOL. Here's the error when entering the hidden phone menu. We've gotten the IMS registered through updating all the paths in the IMS.apk, but yet were still blocked here.

D/RadioInfo(2183): setImsVolteProvisioned state: on

E/RadioInfo(2183): setImsConfigProvisioned() exception:

E/RadioInfo(2183): com.android.ims.ImsException: getConfigInterface()(131)

E/RadioInfo(2183): at com.android.ims.ImsManager.getConfigInterface(ImsManager.java:1809)

E/RadioInfo(2183): at com.android.settings.RadioInfo$15.run(RadioInfo.java:1292)

E/RadioInfo(2183): at android.app.QueuedWork.processPendingWork(QueuedWork.java:258)

E/RadioInfo(2183): at android.app.QueuedWork.access$000(QueuedWork.java:49)

E/RadioInfo(2183): at android.app.QueuedWork$QueuedWorkHandler.handleMessage(QueuedWork.java:278)
[Android Builders Collective] kantjer:
Same for Angler, for now we disabled IMS to at least get cals through
[Android Builders Collective] wavedashdoc:
Yeah and no thanks to Google, they've provided next to no documentation on how the new implementation works. What [MENTION=4450173]camcory[/MENTION] did on the N6 thread was decompile the IMS.apk and update a few paths to fit the new IMS location in the smali folder. Specifically ImsService.

I then tried my hand at it and went through every file to make sure all paths were correct. But still resulted with the same errors.

Edit: decompiled and then recompiled easily using APKTool.
[Android Builders Collective] aoleary:
Did this work for you?

I have the hiddenapi error, and the commit link doesn't work anymore..
[Android Builders Collective] fraz14:
Nope. It doesnt work for me.
[Android Builders Collective] fraz14:
No idea if someone has a solution for this issue
[Android Builders Collective] stifmaster81:
abc rom there is also rom for pixel xl? If so, can you give me a link? Thanks
[Android Builders Collective] fKm:
No but you can build it yourself. If you have questions then just ask here.
[Android Builders Collective] aoleary:
Can you share the commit with me if you still have it. The original doesn't exist anymore..
[Android Builders Collective] fraz14:
Its from googlesource master branch.

https://github.com/aosp-mirror/plat...0b6f8de#diff-798c350a5c08efb019b5a0ec14d1d476
[Android Builders Collective] aoleary:
I'll try it anyway to see if it might work for me..

Do you know what the flag in BoardConfig.mk is?
[Android Builders Collective] fraz14:
I think

UNSAFE_DISABLE_HIDDENAPI_FLAGS := true

but not sure.
[Android Builders Collective] icxj1:
you can just use this commit & remove hiddenapi for the time being. https://github.com/aosp-mirror/plat...6f26cfd#diff-798c350a5c08efb019b5a0ec14d1d476

---------- Post added at 11:32 PM ---------- Previous post was at 11:23 PM ----------

you need the whole commit, not just the flag. it would be easiest just to remove hiddenapi for now with this commit.

https://github.com/aosp-mirror/plat...6f26cfd#diff-798c350a5c08efb019b5a0ec14d1d476

you will have more errors to come anyway. apache boot.jar, wifi service.jar & frameworks all give error on art-profile & bootimage-profile. "illegal instruction core dumped" leaves you with incomplete boot image.
[Android Builders Collective] aoleary:
Hi.

Yeah, I realised that the commit was also needed..

So basically the commit is no use to us since it ****s the boot image..

Have to hope Google correct the issue..

Don't have the budget right now to go off and buy myself a new CPU..

---------- Post added at 23:52 ---------- Previous post was at 23:40 ----------

Contacted one of the developers that had a hiddenapi commit to his name.

Probably a waste of time but I thought "what the hell" ;)

Probably won't reply

---------- Post added at 23:52 ---------- Previous post was at 23:52 ----------
[Android Builders Collective] fKm:
Hey guys, I need your help again. I am trying to compile BenzoRom for taimen. It worked easily in the past and builds ran very good. Since some days I get this error while compiling: https://del.dog/repujizome.coffeescript

I've never seen something like that before but it seems to be a kernel issue. Does someone know what's happening there? Maybe Mr. [MENTION=6842057]nathanchance[/MENTION] himself can help as I use his great kernel for compiling. Thanks in advance.
[Android Builders Collective] Minux31:
Hi everyone !

It's been a long time since my last build on Oneplus3, and I've decided to build again for my Oneplus5. I choosed Aosp Extended as base, but I forgot all the step to build a proper rom for the device.

I've made my building environnment (a docker container based on Ubuntu 18.04), repo sync sources ( repo init -u git://github.com/AospExtended/manifest.git -b 9.x && repo sync -c -jx --force-sync --no-clone-bundle --no-tags) but device tree is not available for my device (I've got an error when I try to lunch for my device)

So I'm asking how to add device tree from another rom ( https://github.com/GZOSP-Devices/device_oneplus_cheeseburger and https://github.com/GZOSP-Devices/device_oneplus_msm8998-common for example), and is it enough to get a functionnal build ?

Thanks in advance :)
[Android Builders Collective] ezio84:
If anyone interested, ABC P source is up :cowboy:

Atm i've added main daily-use custom features and some love to stock P navbar (full gesture and Pulse support) :D

In the meantime, here's November P gapps link:

https://www.androidfilehost.com/?fid=11410932744536996522

Here if you want to build the zip by yourself or build inline (pie-inline branch): https://gitlab.com/ezio84/android-gapps

From the rom custom vendor tree just add a call to the device .mk file of the new device tree (or trees if more).
[Android Builders Collective] phantom146:
Thank you very much for the efforts! Now if somebody is willing to sacrifice and build a 6p as I have no VM nor a dual boot on Linux setup. That would be great ?
[Android Builders Collective] kantjer:
I'm retiring my 6P today, new OP6T is scheduled to arrive this afternoon.
[Android Builders Collective] Lawlrus:
Thanks for all the 6p builds homie
[Android Builders Collective] phantom146:
Press F to pay respects.

Kidding aside, there goes my hope and dreams
[Android Builders Collective] rp158:
[MENTION=3306843]kantjer[/MENTION]: also from me many thanks for your N5X-builds after Mohican's. My bullhead stays alive, no need for retiring until now... pure luck or genious ABC, keeping the mainboard cool?
[Android Builders Collective] indian84:
Nice.

I may get OP6T too.

Would love be back on ABC bandwagon.

I've been on Essential Phone since I sold my Angler.
[Android Builders Collective] paolocorpo:
Hi guys,

I would like to come back to ABC for my N5X

I saw here

https://androidfilehost.com/?w=files&flid=97792

and teh last released seems to be:

ABC_ROM_bullhead-8.1.0-20180720.zip

Is it correct ?

Thank you so much

Paolo
[Android Builders Collective] rp158:
[MENTION=5056724]paolocorpo[/MENTION]: no, the latest is buffal0b1ll's 20181002
[Android Builders Collective] paolocorpo:
Thank you so much !
[Android Builders Collective] CLPose:
Bootloader and radio change in N5X November security update. So, I'd wait for the ABC November build to update, but it's up to you! Good luck!
[Android Builders Collective] paolocorpo:
Thanks for the info

I will wait with you

Paolo

Inviato dal mio Mi A1 utilizzando Tapatalk
[Android Builders Collective] rp158:
[MENTION=6310891]CLPose[/MENTION]: I'm on latest ABC and radio&bootloader of november image. No problem. Only vendors are linked to system.
[Android Builders Collective] g90814:
I think this is the last update (November) provided by Google for the N5X as well, end of an era!
[Android Builders Collective] jerethi:
Hopefully she'll live on through ABC!
[Android Builders Collective] Bobbaloo:
Thanks for all you've done! Its been great
[Android Builders Collective] fKm:
My ABC build for taimen is ready but not yet tested. Is anyone interested in it? Then I will upload it today in the afternoon so it can be tested.
[Android Builders Collective] Topse:
if I have seen it correctly, uses BenzoRom clang 8.0.

flash taimmen uses clang 7.0.

maybe there is the error.
[Android Builders Collective] KelevrA_8:
Ill give it a shot, I'm on Sprint so some things will be broke for me anyway.
[Android Builders Collective] fKm:
Okay, here we go: https://androidfilehost.com/?fid=11410963190603845536

Beware: I was not able to flash any ROMs via TWRP with Sultan Kernel installed. Use Stock or any other Custom Kernel to flash the ROM.
[Android Builders Collective] rrrrrrredbelly:
Thanks for building this, I'm not going to have time to flash anything this week, can't test it but I appreciate it.

Dan
[Android Builders Collective] Jabs123456:
Require help

Who is the culprit? Oppo Realme1 - Uber - PayTM India:

I am having a strange problem, unless more people have encountered the same?

We all know Uber allows payment through PayTM. I am facing a problem while Adding funds to PayTM..it takes me to "Processing your Transaction"...OTP stage...but immediately takes me bck to "Add Money to PayTM" base page. Interestingly, this happens with my friend too using Realme1. So is the problem with the phone? Oppo Realme1 users, please respond...as Uber and PayTM responses/logic below.

(1) Response from PayTM: Ignored repeated messages on APP for HELP; no reponse. Note my account is not in ban and can use PayTM account for other transactions.

(2) Uber says...Delete and download latest version, perhaps that wud help. Tried that, but the problem persists
[Android Builders Collective] indian84:
Huh???
[Android Builders Collective] alryder:
I'm assuming that PayTM is like Google Pay. You said "Note my account is not in ban and can use PayTM account for other transactions", do you mean other transactions on your phone? Are you rooted? If so what are you using for root? I had a similar issue when trying to pay Uber with Google Pay and Root was the issue. I had to use the Magisk uninstaller to completely uninstall Magisk and reinstall it from scratch. If you are rooted there are several SafetyNet checker apps on the Google Play Store, try running a couple of them to see if SafetyNet is being tripped. If it is, that is likely the problem.
[Android Builders Collective] Topse:
Any News for this bull**** error :confused:

Or is it needed to update to a new CPU :rolleyes: .
[Android Builders Collective] aoleary:
Haven't heard anything..

I'm using Google Cloud at the moment and find it very useful since I can access it from work, so if I get an error then I can fix it during the day if I have the time..
[Android Builders Collective] Face_Plant:
Edit - Never mind, figured out it out.
[Android Builders Collective] indian84:
[MENTION=3306843]kantjer[/MENTION]

Got your 6T?
[Android Builders Collective] kantjer:
Yes, it arrived November 7th
[Android Builders Collective] indian84:
Naice. I got mine yesterday too. Can't wait to be back on ABC.

LOL.

Had Essential for almost a year.
[Android Builders Collective] kantjer:
Nice, great phone.

Stock OOS is great. No need for a custom ROM .

I'm on rooted stock with Blu spark kernel
[Android Builders Collective] indian84:
Lol. Same here.
[Android Builders Collective] Roger.T:
I am also on Stock OOS on my OP6.

OnePlus does an excellent job, even though the dumbasses in the OP forum see it differently...?
[Android Builders Collective] Spyros_V_S:
Is there any chance we see ABC Pie for bullhead or we will stay with the latest Oreo?
[Android Builders Collective] jerethi:
I'm sure one nagging issue is the problems getting VoLTE to work on Pie. I understand that this means the 5x basically can't receive incoming calls on Pie right now. Could be an issue as a daily driver for some.
[Android Builders Collective] rp158:
[MENTION=4778896]jerethi[/MENTION]: I'm not sure, if I get you, but I'm on CypherOS since 3d and have no problems with incoming normal calls. VoLTE isn't in my contract, cannot test.
[Android Builders Collective] buffal0b1ll:
At the moment, I have no plans to attempt building bullhead ABCrom for Pie.
[Android Builders Collective] paolocorpo:
I was hoping ... that it could be real for the future ;)

Inviato dal mio Mi A1 utilizzando Tapatalk
[Android Builders Collective] xperia1-2:
I want to know if there is a newer version of this desktop? I can not find him! Because my English is not good, I want to seek your help.
[Android Builders Collective] ezio84:
On my GitHub abc source as usual, "p" branch of the launcher3 tree . Keep in mind it's linked to the Recents (Overview) panel icon pack engine I added, so you need both things.
[Android Builders Collective] Roger.T:
Added some new wallpapers for you..?

Please enjoy it ??

https://goo.gl/v2NjSA