[Google Pixel 3a Guides, News, & Discussion] tekhedd:
Easy way comments

Thanks for this heads-up. So hard to find 3a-specific builds, lots of 3aXL builds but ... I'm also a huge fan of Deja-Vu Location service so everything here is apropos.

Build fails hard using the docker build.

First: I assume this error is normal, as it is ignored by the build:

build/make/core/product_config.mk:223: error: Can not locate config makefile for product "lineage_sargo".

Second: before.sh (I would recommend adding set-e to the top, but it doesn't matter, because the docker build doesn't check the return status of before.sh :o ).

Some of the cherry-picks appear to have been merged. The HBM patch cherrypick fails, merged on May 14 (hooray!) Can probably be removed? commit e3b20082e9d797bcff286311637669377f16e55a

The bonito RRO bluetooth patch was also merged: commit 28ba61337f05866d52f84167fcb50156477994a1, probably also hooray?

The CONFIG_HZ patch... cherrypicks but does not appear in the commit history. git is such a labyrinth of features I'm pretty sure I just don't understand how to use it. But at least that appears to merge without problems.

[edit] I have submitted a ticket in github for this.

Note: My builds were failing because of a leftover docker process. Beware! The docker build process does not respond to command line ctrl-c; if you want to kill the build do a docker ps and kill the process.

[edit2] Swap!

I have 24G of ram and normally don't run swap; without swap, the build runs out of memory and oom-killer will eventually kill the build. (Suspect the compile is writing large numbers of tempfiles to "disk" or generating an enormous memory mapped file -- and in docker "disk" is RAM.) This is expected behavior, but I thought I'd mention it, in case anyone is trying the build based just on the instructions here. I added a swapfile and am still waiting to see if it needs to be larger--the build is currently using 19G and still climbing. This build is quite impressively memory-intensive!

[edit3] Success!

The build was successful, and yes took a very long time. It's up and running on my phone in slot a. I'm running a gapps-free setup (no microG) so of course the camera doesn't work, but the rest is absolutely great. Definitely recommend this method as long as you have a lot of CPU cores and a swap file. :>

[edit4] "Carrier Services keeps stopping"

Based on one Reddit conversation, this is not a bug in your build. Don't panic. This appears to be a bug with the carrier services APK currently bundled with LineageOS 17.1. In a no-google setup, going to the Play Store to update Carrier Services is not an option, and I'm not even sure if this will fix the issue. Appears to be a Pixel-specific problem with Lineage, not limited to just the 3a. Workaround: I disabled Carrier Services , and have not noticed any degraded functionality (T-Mo). However, I use Signal instead of Messaging, which may lose some MMS and rich-messaging features (maybe this is a benefit for some?); and, we will eventually need Carrier Services as it is intended to manage things like LTE, so this is not a permanent solution. YMMV.

Editorial note: Google is gradually moving things out of the Android core so you are dependent on their cloud services (Play store) for core features like Camera and Messaging. :P