yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] baj24:
Can anyone with Fi comment on whether esim works with this rom?
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] adm1jtg:
I believe it's actually a Verizon thing. On my n6 and my og pixel xl and now on stock 10 on my 3a xl apn settings are greyed out and no ability to add a custom apn either.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] jsminnis:
Just curious if this rom will be updated as security patches are released?
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] oranget:
He has been working on it, but the changes in the december build have been causing problems. He will get it eventually.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] baj24:
Anyone?
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] Ericarthurc:
I can't confirm, but probably. The community works together on a lot of these custom rom advancements. About 8 months ago the Pixel 2 XL custom roms (including Havoc) had esim support. It's most likely going to work. If not though, you can always order a sim card through Fi for free, and it comes in like 2 days.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] stebomurkn420:
Yes it works fine...
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] stebomurkn420:
This is an accurate statement and when I get havoc booting properly again I'll be sure to share my build here...
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] KenK13:
Hi Folks, I'm having trouble trying to get this ROM installed. I have flashed the factory image using the flash-all.bat which was contained in the downloaded factory image and when I reboot to the bootloader and attempt to flash the boot.img, I get the following response:

C:\3A XL>fastboot flash boot boot.img

target reported max download size of 268435456 bytes

sending 'boot' (65536 KB)...

OKAY [ 1.531s]

writing 'boot'...

FAILED (remote: Failed to write to partition Not Found)

finished. total time: 1.917s

Anyone know what the problem could be?

Thanks!​
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] oranget:
You have to flash the november stock build before flashing this one. If you flashed december stock before this, you will get that error.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] KenK13:
Thanks for the quick feedback. Just so I'm 100% clear so I won't mess anything up - - -

I'm currently on QQ1A.191205.011 which was my last OTA update. But now I need to manually flash QP1A.191105.003 which was the November stock?
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] oranget:
Yup..you were on december stock. Flash november, then flash this boot image, then sideload the havoc rom...that should do it. Just follow the instructions on the first page...
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] KenK13:
I was able to get everything completed up until attempting to sideload the ROM. I selected the Update via ADB from the Recovery menu and issued the command: adb sideload Havoc-OS-v3.0-20191127-bonito-Unofficial.zip

The results were as follows:

* daemon not running; starting now at tcp:5037

* daemon started successfully

adb: sideload connection failed: no devices/emulators found

adb: trying pre-KitKat sideload method...

adb: pre-KitKat sideload connection failed: no devices/emulators found

Now when I attempt to boot back into Fastboot mode, Fastboot will remain on the screen for perhaps a second and then the phone proceeds to boot normally. Any way to force Fastboot mode to remain on long enough to get the ROM installed?
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] KenK13:
Well, I came back to this phone after a few hours and today when I press the power button, I get a screen with the green Android robot and "No Command" underneath. Same result if I also attempt to boot into Fastboot mode. So, apparently it's bricked. I'll try to return it. It was purchased from Amazon and they had claimed it was "Unlocked" on their website and the phone they chose to send me was in fact locked. Took quite a long time to finally get it unlocked as OEM unlocking was grayed out in Developer Options and not selectable. Should have just returned it then, but preferred to have the phone then go through the hassle of exchanging it for what they advertised. Ended up taking it to a local phone shop and the guy there was able to use a special cable to unlock it.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] stebomurkn420:
WHAT! No it's not bricked at all. When on the green Android screen press power then volume up. That will boot you into recovery. Then boot into fastboot from there. Your issue is likely due to not having the most recent Android sdk installed...
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] KenK13:
Thanks for the further information, but pressing power and then volume up while the green Android robot appears did absolutely nothing. The screen remained exactly the same. It's been displayed for about 25 minutes now with no change. Tried pressing power, then volume up multiple times.

The ADB I currently have installed on the laptop is: Version 29.0.5-5949299
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] stebomurkn420:
Ok. Good luck then
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] CenFlo:
I have yet to put a ROM on my 3AXL or even use it as an activated phone, so I am for one, waiting!! :cool:
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] Dnorris55:
Hold both buttons down at the same time for about 8 seconds.

Works on my 3aXL.

Other times I've had to hold one button down and just click the other..
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] bavarianblessed:
Having the same issue, did you ever find a resolution? I'm going to try flashing the stock 191105.003 kernel to see if it works, otherwise I'll have to use something else. The ROM is great otherwise
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] Soulmatik:
I just wanted to say thanks for this ROM & kernel. I came from my old ass Nexus 6 running Cataclysm for the 3 past years and I was hoping I could find a ROM that was customizable and just as solid for a daily driver. This ROM/kernel is perfect and smooth as hell. I have great battery life and no issues. Thanks [MENTION=4517290]stebomurkn420[/MENTION], I greatly appreciate your work!
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] dhairyadev:
Just came across this ROM. I have a few questions, and I beg your pardon if they've already been answered in the posts above mine.:

1. How good is the battery life, on the 3a XL especially?

2. Are there any unresolved (major) bugs in the ROM?
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] stebomurkn420:
*** Updated for January ***

To many features and fixes to list. Head over to Havoc OS github for a full feature list. Please notice you now need to flash the dtbo image as well as the boot image. Enjoy!
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] stebomurkn420:
Battery life is great on every ROM I've tried. I use the same kernel in all my builds which is very similar to stock. In Google we trust!!! The only major bug would be active edge isn't working yet and I've seen people having issues with android auto. No logs so I cant help. lol. Speaking of kernel, I switched back to using LOS stock kernel which is as close to AOSP as possible for stablities sake.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] dhairyadev:
That sounds nice. Would you be able to give me an estimated SOT tho? I'm really looking forward to flashing this ROM on my XL.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] stebomurkn420:
I don't like going there because our usage is probably a lot different. 5-8 hours SOT. It can vary on one's usage dramatically. I average around 6-7 myself.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] dhairyadev:
I understand that. I manage to get around 6-7 hrs on stock currently. Guess it won't be a huge change then. Thanks anyway! :D

Also, I do use Android Auto, so let me know if I can be of any help to you in fixing it.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] stebomurkn420:
This is my first full cycle so far...

View attachment 4924597
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] Soulmatik:
If I'm running the Nov version, do I have to do a full wipe clean install or can we do a dirty flash? I really don't want to have reinstall everything and all my settings. Thanks!
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] chuckcheeze:
Dirty flashed this moring. So far so good. Thanks for the new release
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] CenFlo:
Did I miss the current version that you're using, specifically which security update? Is this still on Nov or have your moved to a more recent one? I have yet to use my 3aXL, have been waiting for a ROM that based on an updated stock security level.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] CenFlo:
Okay, which security update is this ROM?
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] stebomurkn420:
READ the title... 10.0.0_r25
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] stebomurkn420:
Let's get rid of all the negative energy and post screenshots of our homescreens... I'll start...

View attachment 4927495
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] Az Biker:
* * * Thread Cleaned * * *

Four pages worth of deleted back and forth arguing, disrespect, and off-topic comments?

Please allow me to remind everyone here of the Forum Rules.

Posts must be on topic. In a development thread, that means comments must aid in development of the current work; troubleshooting bugs, testing features, feedback on reliability, etc. NOT arguing, name calling, personal insults or flaming other members.

ALL Xda members must refrain from posting disrespectful, insulting, attacking, or rude comments.

The proper method of dealing with trolls, and troublemakers is to REPORT them. Please do not engage them, argue with them, or fill 4 pages in a development thread with useless back and forth. REPORT them and allow moderation staff to address the issue.

Further comments that violate forum rules will be deleted, and if previously involved accounts continue posting in this manner, they will be reviewed for restriction or removal.

To the good, positive, productive, contributing members of Xda; please do not allow the trolls and ungrateful members to drag you into violating the rules with them. YOUR presence is welcomed in Xda, theirs is not, and the BEST way to remove them is to REPORT them and NOT argue with them.

For those doing the right thing and using Xda as it was intended, thank you!

And thank you to everyone for your cooperation from this point forward :good:

tl;dr

Way too much arguing and useless off-topic cluttering the development thread

Please just REPORT the problem, don't become part of it

Dev and contributors are welcome, trolls are not

Be respectful, and helpful when posting
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] stebomurkn420:
*** Test Build ***

- Switched back to using Dank kernel (Thank you shag for finding the random reboot fix from upstream, it's actually an issue with techpack from what he said)

- fixed CTS (it passes now)

- couple other ROM changes (please see Havoc OS GitHub)

Boot: https://drive.google.com/file/d/1LD0le7fiqJbAreWZg4ff0FwXD4t0kJqU/view?usp=drivesdk

Dtbo: https://drive.google.com/file/d/1Y_YhCrjxnFK9DtItYFk_neYPpsRRBXXH/view?usp=drivesdk

ROM: https://drive.google.com/file/d/1LgQE6WOiyIA1VKlbVA7qxKoPuNYs8TaZ/view?usp=drivesdk
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] anbinhv:
Thanks dev! Is Random Reboot is the same as Random Shutdown (when charging) on stock rom?
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] stebomurkn420:
I do know what you are talking about. We have been calling it The sleep of death (SOD) lol. It hasn't happened to me on this build though so maybe it is fixed...
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] anbinhv:
13 hours on the rom and so far so good. No issues found.

Thanks for the Rom!
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] oranget:
Thank you for keeping this rom updated on here. I really appreciate you and your work!!!
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] bildo:
ROM is running great. Only issue I had for some reason was with the stock keyboard. Whenever I swiped it would crash for some reason. Switched keyboards and all is well.

* I'm on the test build from 1/16. Clean install.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] Ericarthurc:
oh man... i would love to use this rom; but I have Visible for my carrier and was unable to get it to work with the last (nov) build. I don't know if anyone knows (I know Visible is a small carrier and many people probably dont have it), but is there any chance of service with the newest build?

I mean I am down to just flash it to try, but if anyone knows for sure I can save some time. Thanks
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] anbinhv:
I have to thanks dev again. Maybe placebo but I feel smoother than stock!
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] PGHammer:
I have the sargo version up and running (had my issues, but it turned out that a re-download fixed them). I'm still running stock except for the preview of Microsoft Launcher (which I was running on stock Android 10). I have no other changes - literally - from stock Android 10. I crossgraded from the latest stock factory image of Android 10 for the express purpose of a heads-up comparison TO stock. Because I am staying home this week, it will be a straight test series of everyday usage (again, compared to stock). Next week will be a more detailed test because I'll be using it in greater detail (taking it out for thrashing). Can one of the developer/builders create a thread in the sargo forum for this ROM? (I have noticed that I'm not the only sargo pilot.)
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] stebomurkn420:
It's only me... If someone else would like to build and post of course they are more than welcome. For now you can just ask any questions/post feedback here. The more the better! It's honestly easier for me to see everything in one thread (when I make two threads like I did for OG pixel the smaller variant always ends up being neglected). Especially since there aren't many users in the first place.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] PGHammer:
Not JUST bonito, sir.

This is out for sargo (3a) as well; that's what I'm running it on. It has the distinction of being the first non-factory ROM I've gotten to run on it. (Amusingly, I have never gotten a non-factory version of Pie to run on the 3a - and it isn't for lack of effort.)
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] Ericarthurc:
Want to report back; installed the Jan build. And visible started working right away. LTE, sms and mms are working great. Service says Visible and the APN settings picked up correctly. And when I reboot the "Verizon AVS settings" start right away. Thanks!
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] PGHammer:
Do you have VoLTE support? I do (TracFone/T-Mobile) with a nice big indicator that it is active (something stock lacked, though it does support the feature).
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] stompysan:
No ****? I never thought I would see Visible working properly with a custom ROM. I may jump ship again if I can get on a family plan.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] Ericarthurc:
Yeah! The volte symbol in the status bar is there. I made a call and it sounds like Volte quality.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] PGHammer:
I don't think it's lack of users...

I don't think it is lack of users; my own suspiscion is that it has more to do with the strength of stock Android (9 and 10). For the first time in years, dead-stock Android is not something to be mocked OR feared. It is for that reason that I am doing something that hasn't been done since Pixel Experience - comparing a ROM to dead-stock.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] Archangel:
Yeah I know brother been running it for a while now
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] alin919:
Thanks for everything you do ! Running perfect ?
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] PGHammer:
Other surprises...

I have NOT had to switch out of VoLTE even once so far (which is something I couldn't say about stock, despite it also supporting VoLTE). My entire feature set is available at once; while stock supports VoLTE, it had issues with telephony routers (such as one in my own garage). I'll have additional reports next week, since VoLTE I will have to use more often due to being at my infusion center Monday for about five hours. SMS and MMS are solid as well (even with VoLTE active). Basically, Havoc 3.1 DOES have advantages over stock - which will HAVE to be the case with any Android ROM going forward.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] PGHammer:
Surprise upon Surprise

I'm loving this ROM because it lets me do some things that I couldn't do with stock.

One issue I had with stock was Voice over WiFi with certain routers and APs (primarily telephony routers). With Havoc, I don't have to switch out of VoLTE or VoWifi for anything. (At worst, I have to not try to use data and voice at the same time - however, that is expected when using VoLTE or VoWifi; remember, neither is normally used for voice.)

Because of that, I have pulled the manifest so I can go either self-maintainer (build for my own use) or become a co-maintainer (I'm not good enough to become a sole maintainer yet - and I'm not about to try).

Another welcome surprise - this ROM is *little*! Despite the device breadth, because it's based on AOSP 10 r_25, there is very little frou-frou. DU is a pig by comparison (and I'm still working on pulling all of it). This may actually be buildable on low-end PCs (I'm talking dual-core here) - not exactly typical, and decidedly unexpected for AOSP 10. (Not that I plan on *staying* dual-core; but that is what I have now.)
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] PGHammer:
Darn/drat/fidddlestix. How do I add sargo (as a device) to my Havoc repo?
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] stebomurkn420:
Clone my trees. The device tree is unified. Or just use the havoc-b4s4.sh from my scripts on GitHub. I can tell you that you will need sdm825/display from LOS. Other than that it will build clean for sargo. **One more thing** BT will be broken on your build as it was broken in source about a week ago. I have a 100% stable sargo build hidden in the OP! Good luck! [emoji854]
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] PGHammer:
Grrr- now I realize why I can't do anything except self-maintainer; lack of experience using multi-source tree cloning in git.

Right now, I'm going to build an online repo in Github desktop, and then rebuild my local git from there (which is going to be a royal pain). However, there is ANOTHER reason to do so; I'm ordering a larger HDD over the weekend - going from 1 TB to 4 TB on my build device. MUCH more room. Since I will have to rebuild the local git anyway due to the capacity gain

, I may as well have a better source to do the rebuild from.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] kkjb:
Sargo user, so I have the 0130 build but Jan factory base is a no-go to sideload (well it completes but no changes) should I use Nov, Dec?? Pretty Please ?

Edit. So tried last 3 factory to both slots, fastboot -w, adb sideload and no changes to base install. I must be missing something :(
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] PGHammer:
Last factory still requires a clean base; I tried the same thing you did, and got nowhere. A clean flash would likely work (via the Flash Android Tool); however, a dirty flash likely won't. I will be getting a new USB to USB-C cable next week via Amazon (Anker). The latest flash tool DOES support Chromium-based Edge (which is new). In a way, I'm glad it failed; Havoc is rock solid for sargo as of 3.1.
[Google Pixel 3a XL ROMs, Kernels, Recoveries, & Ot] PGHammer:
Clonage complete (and hints for future cloners)

Okay - I cloned the trees into my scripts subdirectory. A nice surprise; I didn't have to clone the entire Havoc directory beforehand - in fact, it tossed six commits from my previous pull of the Havoc tree. If the same is true of the other scripts, it will save me a crapton of pain and suffering (I'm thinking DU in particular; there's a script for it as well). Your January 19th sargo is indeed rock-solid; that's what I'm running and have been - it's what I've referred to as a "better stock" because of what I can do that I couldn't with stock.

The only reason I will be waiting on the Lineage script is because I want to replace my build drive first; 1 TB strikes me as being way too small for four ROM build trees - especially considering the sheer size of merely Lineage. As it is, I expect merely DU will be pushing the disk space constraints. Because of the pruning your script did with Havoc, it's possible that the DU script may do similar prunage; however, I am not counting on it.

Hints and tips for future cloners (because of what I uncovered):

1. Start from scratch (with a completely empty build tree). By scratch I mean do only the bare minimum to get your build tree skeleton up; the scripts will do most of the work for you. WSL (better yet, WSL 2 if running Windows 10) is actually ideal; if running Linux, Ubuntu (any 'buntu) of 18.04 or later works fine. I started with the Nathan Chance walkthrough, but stopped after the creation of the scripts folder (I imported the scripts into that folder, since importing them afterward - for some reason - doesn't work); hence my recommending starting with an empty tree.

2. Each script covers a ROM; run only what you want to build ROMs for. (I'm following my own advice; at first, I am only working on Havoc and DU - starting with Havoc).

3. Disk space is critical if you want to build more than two ROMs! While Havoc is small, Lineage isn't - it is why I am waiting until I get a larger HDD before tackling it.

4. The Nathan Chance walkthrough - This walkthrough is all too useful, especially for newbies; my "hints and tips" on this page is, in fact, based on it. The missing sections are because the scripts themselves do some things that are normally done later in the walkthrough (such as both the "automatic" and "manual" sections of the walkthrough) are not needed at all; the only portion I used was setting up git and repo. If I get permission, I will post my modified version of the Nathan Chance walkthrough for those of us using the scripts.