yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] kop316:
This is my build. I also use t mobile in the USA.

I'm having a similar issue with AOSP as well, that's why I came and built lineage.

Edit: I should note that I don't have Gapps installed, do you all have it installed?

UPDATE: It seems on AOSP that when I swapped "preferred network type" to 3g instead of "4g", the problem went away.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] corebore:
I'm having really severe issues sometimes connecting to the Verizon towers near me. I have to switch APNs for it to pop on to 3g or 4g. That's the only major issue I have.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Geo411m:
I was finally able to get lineage working for pixel 3a xl. testing not to see what works and what doesn't.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] snoopy20:
Installed on my 3A. Love getting rid of all that Google junk. So far so good!
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] snoopy20:
First problem, Google Camera (https://apkpure.com/google-camera/com.google.android.GoogleCamera)

Crashes on start-up. Anyone got another version working?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
The August firmware is out now. Time to dust off the computer and see if it still builds...
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Geo411m:
thanks to OP and Gee One I was able to get a 3a XL version built. Link
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] anonym12:
Is it possible for one of you to provide a flashable zip for pixel3a ?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
I'm still testing to see how well it works. It was bootlooping this morning, but I think I had a typo in my build. At least I'm hoping it was the typo that caused the issue.

The battery drain is also still an issue.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] snoopy20:
Love it so far. For those wanting Google Camera just install

https://www.apkmirror.com/apk/googl...-031-259661660-android-apk-download/download/

and

https://www.apkmirror.com/apk/googl...rk-9-4832352-android-apk-download/download/~~

(use Jan 19 apk as April one is corrupted).
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] sbth_:
Hey, all! I'm very interested in giving this ROM a go. What would need to be done for it to obtain official status?

EDIT: I've seen mentions of battery life issues. Is that just your standard "first day of Lineage" battery drain, or does it continue after the install day?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
For the battery, it seems to be better after the first day or so.

For being official, I think it needs a maintainer, which it might have already since there is already a lineage tree for it. I think that the A/B/vendor complexities are slowing down all pixel development. At this point, I think that only marlin and sailfish are official, and they have slightly different trees than the more recent pixels, to my untrained eye.

I have an unofficial build, but I'm not 100% sure it's flashable yet. The other build I use on my daily driver has stuff built in that most people won't want.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] anonym12:
Download the august 2019 facory images sargo-pq3b.190801.002-factory-56817dc2.zip and extract

run flash-base.sh

run sudo fastboot update image-sargo-pq3b.190801.002.zip

gee one provided me with the following firmware flashable via twrp-3.3.1-6.img

sudo fastboot boot ''twrp-3.3.1-6.img'

adb sideload 'lineage-16.0-20190806-UNOFFICIAL-sargo_5afa2f9e.zip'

Since it is A/B an operating system is always flashed to the inactive slot. So you have to start the recovery again and the slots are automatically switched.

Now flash magisk and mindthegapps via sideload. Such addons are always installed to the active slot.

You do not need to flash twrp, because you can use the integrated lineageos recovery.

The battery runtime seems to be good.

You need mindthegapps for A/B support and seamless updates MindTheGapps-9.0.0-arm64-20190615_031441.zip

They are also the preferred gapps for lineageos.

Magisk-v19.4-736729f5(19307).zip for seamless A/B updates

Bugs:

The rear camera cannot take photos with the stock camera application. I had to install google Camera from the play store.

VoLTE seems to be missing

I strongly recommend gee one to create his own thread and hope that i or someone else can help him with debugging the camera issue.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
This is with 2 hours of screen on time. I'm don't consider myself a heavy user. So maybe you can extrapolate 6 hours of screen time? It's not the fabled 9 hours that requires the user to post to XDA, but it lasts long enough for me.

Maybe some kernel tweaks and you know, actually optimizing the rom would probably make a huge difference. There are a bunch of selinux denials in the logs that would probably be easy to fix, some look like they are power related too!
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] kop316:
The A/B stuff has already been solved with the Sony Xperia XA2 (I used that as a daily driver until a cable ate its USB port). The vendor seems to be more of a legal issue? I'm not sure what problems you had with that.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
No problems on my end. I agree with you-the legal issues around the vendor might be slowing down development.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Pogo:
bump
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] kop316:
1) I imagine is it supported, since it's a driver and otherwise implemented in AOSP.

2) Same as above

3) it was released without Gapps? Look at the one on the first post

4) without logs nor debug info, we couldn't tell you
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Pogo:
Thanks for the reply.

3) sorry, mixed up the ROM's. my mistake

4) let me rephrase: when the option 'Automatic (time of the day)' is selected in Setup->Display->Style->Style I would expect Settings, Status Bar, Quick pulldown, etc. to switch to Dark theme at some point during the night/evening. No matter what the time is - early morning, noon or late night the background (theme) is always the same - white (my default).
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] snoopy20:
Battery life in standby overnight drops 20% whereas with stock it's 10% and with a cleaned stock (rooted, Google crap cleared) it's 5%.

So quite a bit of attention needed in this area.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] kop316:
So my mistake, it turns out the eSIM needed a proprietary driver. The proprietary driver list I posted enables it.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Pogo:
Nice! So, we might expect eSIM in the next release, right?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] kop316:
Maybe. That's up to the developer. That file I made was for my own AOSP build, not for lineageOS.

I am also not sure which of the file activated it, and which files don't do anything or have other functionality. If you could help test and figure that out it'd make.ituch easier for the devs to include it.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
I tink esim also requires gapps to work, otherwise it just force quits over and over. So the build might be OK as long as gapps is flashed.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] kop316:
Heh. Interesting. The only reason I am suspecting that eSIM is functional is when I reset my network preferences it asked me if I wanted to reset my eSIM as well, and that did not happen before I added the proprietary files.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Pogo:
I would like to test but don't expect lots of help from me with coding or cooking ROM.

So far my ideal ROM will be stock - gapps - few Pixel things + pixel_camera + eSIM.

Pixel things are easy to rid off. Pixel_camera is working on Lineage (pulled from stock ROM).

I'm using microG + F-Droid + Aurora for google stuff (I have no need for Google Pay or Google Play).

If eSim require gapps and it won't work on microG it's certainly not deal breaker. I'm using SIM cards for 20+ years, I can live without eSIM.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
Testers are always welcome. Sometimes it's just nice to know the rom will flash on another phone cuz that's how much confidence I have in my builds.

What are the pixel things? Like squeeze? I have about 10 minutes is use in the stock rom- just long enough to unlock the bootloader.

I'm running gappless with fdroid. I sideload a few apps, but they run just fine without gapps.

I haven't played with microg, but my understanding is that there are security choices to consider.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] kop316:
Does it also make sense to post am updated way to compile lineage? That way multiple.people can try and figure out what each driver does.

Also, what is the squeeze sensor? I may not have it on my phone.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Pogo:
Message me once you have something to test.

Squeeze sensor will be nice, can't remember any other Pixel specific things on top of my head.

I was also running gaplesss for few years but I have few apps like Signal and two bank apps that won't work without gapps. MicroG work well by faking these apps. Security is always a tradeoff. My security toolbox include XPrivacyLua, MyAndroidTools and NetGuard. Magisk (Magisk hide) and EdXposed of course. The phone is booting slower, use little bit more battery but I'm ok with that.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
I haven't tried microg, but I think some of the security issues can be addressed by building it yourself with your own keys.

---------- Post added at 02:27 AM ---------- Previous post was at 02:20 AM ----------

The squeeze sensor is on the sides and activates google search or assistant when you squeeze the phone.

Documentation is always a good thing. ;). That being said, I have a frankenbuild that might have all the proprietary files. It flashes in fastboot, but not recovery yet... I'm testing something and I just kicked off the build, so maybe I'll know more later tonight.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] kop316:
So FYI, in AOSP, when you compile it, you can use the command "m installclean" and change around the proprietary files. When you recompile it only takes like 5 minutes. So it may be worth trying there and applying the results in lineage
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] n1kolaa:
Development is dead? Didnt find his sources. I can start work, need to make on one ssd linux again maybe will start work latter. Im out of time now.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] :
Thats why im waiting for official lineage now. DU finishes after 9, statix no longer developing also. Happy with stock anyway roms dont offer much over stock aosp anymore :(
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] dpryor88:
Du doesn't finish after Pie haha. DU will be continued on AOSP Pixel devices (like sargo) through Q and who knows how much further..

But yeah, DU will be probably the first custom Q ROM we get with sargo. Alex, the official sargo DU maintainer, is on the ball with updates. So we'll be seeing DU Q soon enough..

---------- Post added at 06:26 PM ---------- Previous post was at 06:25 PM ----------

Actually, I think if anything, I heard that lineage lost the maintainer for sargo/bonito for some reason. So we may actually not be seeing official LOS anytime soon if anything. Not 100% on this. Just what I heard recently..
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] :
I know this is old, but whats this then? Or did he change his mind?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] dpryor88:
Yeah that's old news haha. Fortunately :)

We will be seeing DU Q :) don't worry.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] :
Cool thanks for clearing that up, thats actually what was stopping me installing DU. Might even give it a try now. Is it any good? Would u say better than stock?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] dpryor88:
TBH, it has battery life similar to P stock (it's better than Q stock in my opinion at the moment). The custom features are great. There's not an overwhelming amount of custom stuff like on Havoc, Liquid Remix, etc ROMs. Just the right amount of cool stuff to play with. I love stock, whether it be P or Q, but I like having more control and less bloat, so I usually will prefer DU over stock. Also, DU for our device comes with the bare minimum Google apps and lets you install what you want from the play store instead of choosing for you what apps you'll be having.

I hope this helps. It's totally worth a flash if you haven't tried it yet, especially since it went official for sargo recently. It's a solid ROM.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] snoopy20:
Such a shame this was discontinued. I find it perfect other than the lower battery life.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
I'll cook up a build soon... I'm also itching to Terry a free things in qberry.

---------- Post added at 11:40 PM ---------- Previous post was at 11:39 PM ----------

Edit: itching to try a few things in qberry. Swype keyboard is a blessing and a curse.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
Here is a fresh build of lineage-16.0. The build has been pretty stable lately and not much has changed in the tree. There are probably just a few incremental fixes that aren't sargo specific.

I haven't tested this, although I don't have any reason to believe it won't work. I flashed qberry on my test phone last night, so I probably won't flash back to pie on it.

https://brownbagdinner.com/lineage-16.0-20190905-UNOFFICIAL-sargo_52e26e07.zip
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Helios747:
I'm not really sure if you can flash back to pie, hasn't the storage been repartitioned on Q?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
Yes it has.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] kop316:
Storage was repartitioned, but you can reflash back to pie.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] snoopy20:
I can confirm it works fine!

There appears to be no audio (mic and speaker) in the dialler now, investigating...
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] snoopy20:
Hi, is there a way to flash the old img files over the new zip? The phone now has no call volume or mic send.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
I think fastboot will let you flash anything you want but recovery might enforce the rollback protection.

I was going to kick off a new build tonight, so I'll also add the img files.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
I have a new sargo build and I think found the issue with volume.

PM me if you want to test it. My phone is on q so I'm not able to test this pie build.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] snoopy20:
Will do.

Unsure if it's volume per say, I can't hear any incoming audio and the receiver can't hear sound from my mic. Only on the dialler.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
New build is up- I think I figured out the call issue. Somehow my vendor trees were deleted, so the rom didn't include all the proprietary files.

This is a stock build with all the los rom updates as of 9/18, although the build date is 9/19 since I kicked this off late last night.

The images link has just img files if you want to flash through fastboot. I think most people will want the first link which is a flashable zip.

Thanks to snoopy20 for testing this.

Flashable zip

https://brownbagdinner.com/lineage-16.0-20190919-UNOFFICIAL-sargo_33f3f20a.zip

.img files for fastboot

https://brownbagdinner.com/lineage-16.0-20190919-UNOFFICIAL-sargo_images_a6835a00.tar[/QUOTE]
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] tnicko:
Running like a champ man, couple days now, no issues. Calls work fine as well.

Thank you so much dude for taking the time to build these :good:
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] codethief:
Hi gee one,

First of all, thank you for all the work you've been putting into making Lineage work on the Pixel 3a!

I'd like to revisit sbth_'s question. What would be needed for your builds to become "official"? Is there still anything crucial on the technical side that's missing / not working? Or would we "just" need a maintainer? (As far as I understand, you're not going back to Pie, so I assume someone else would have to do the maintaining.)
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
I think there are other issues with the pixels that are keeping them from release. They have google and aosp support so it should be "easy" (tm) to get lineage working. I think all of the pixel devices have lineage repos that are in good shape (and out there by lineage maintainers), but for whatever reason, there are no official builds beside marlin/sailfish. It might be due to the charter requirements-if functions are on the stock rom, then they have to be working on the lineage rom. But, this might require gapps to be distributed with the rom, which could be problematic. This is just a wild guess on my end. Of course if it were something as simple as the squeeze sensor nor working then there *might* have been an exception months ago.

https://github.com/LineageOS/charter/blob/master/device-support-requirements.md

I seem to recall that one of the earlier pixels wouldn't boot without gapps installed, so this might have stopped pixel development. It could be a completely different issue like not having the proper license for the poop emoji.

Regarding pie, my daily driver is still on pie, so I'm still building it weekly or so. Most of the lineage effort is on 17 right now, so there are mostly generic changes in 16. I don't think that Google will put out anymore pie updates.

My test phone is on 10/X/qberry, so that one is hard to flash back to pie.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] elepton:
I remember one issue being that opengapps had to have seamless support for A/B in Pixel. I don't know if the situation has changed but earlier we had to manually check boot slot and mounts before flashing gapps.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] wijewkyoc4gu8krwf4igg:
Whats the chances of an Android 10 version? Thank you for this by the way :)
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] codethief:
[MENTION=2790198]gee one[/MENTION]: Thanks for responding so quickly! I've got a few follow-up questions:

Are you referring to https://github.com/LineageOS/android_device_google_sargo (which points to the bonito repository)? If yes, in how far do your builds differ from that repo?

What about the Pixel 3a specifically? Are there any features that don't work or necessarily require gapps? I've gone through the entire thread and it seems that everything's working fine with the possible exception of the rear camera which might or might not require Google's camera app(?)

Well, but the Pixel 3a does boot without gapps when using your build, doesn't it? (Unfortunately, I haven't actually been able to test your build yet as I'm currently in the process of deciding which new phone to buy and the Pixel 3a is one of the candidates I'm looking at. I'd strongly prefer a phone, though, which has a chance of receiving official LOS support eventually – both because of automatic [security] updates and because of MicroG support). (×)

As for licensing, while I'm a software developer I'm afraid I'm not too familiar with the ins and outs of building Android, so at the risk of asking a stupid question: Am I correct in saying that the only non-free part of your builds comes from reusing the proprietary vendor blobs that come pre-installed on the phone? If yes, is it absolutely necessary to distribute them along with the ROM or could those also be pulled somehow from /vendor during the flashing process in order to avoid licensing issues? In any case, as far as I understand this will no longer be a problem as soon as LineageOS fully supports Project Treble and we'll all be flashing GSIs, correct? (Is it known yet whether LineageOS 17 will support GSIs?)

(×) I'd also contribute and put in some work myself if need be – as long as it's foreseeable that the build process can be fully automated at some point and I won't have to fiddle around for every single build / whenever a new commit hits the LineageOS repo. However, I'm not sure in how far this is achievable in general? Put differently, how much work is it to maintain a working build once it was fully working one time? In how far does this depend on whether or not the OEM releases breaking vendor blob updates and, more generally, how does one go about incorporating vendor updates into new builds automatically? (I'm basically asking about general experience with maintaining an unofficial LineageOS ROM, so that I can gauge how much time & work I'd have to put in.) My idea would basically be to set up a Docker container that pulls new commits from the LineageOS repo, possibly applies the MicroG patch and adds the vendor blobs, then runs the build process every night or so and finally serves the build over a custom OTA server. (See e.g. https://blog.julianxhokaxhiu.com/20...rver-works-and-how-to-implement-and-use-ours/ ) Does this sound achievable to you?

Oops, this post has gotten way longer than expected. Thank you in advance for taking the time to read all of this!
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] codethief:
Once again, thanks a lot for your detailed response, gee one! You cleared up lots of things!

Haha, so it indeed looks like the most likely reason is that there's no maintainer (apart from the hardware issues).

I suppose "building" the vendor image in this case doesn't entail any real "compiling" and is rather just a "repackaging" since the component files you're mentioning are probably proprietary / closed source?

I'm confused, aren't it the LineageOS developers that decide what AOSP changes get pulled into LOS and wouldn't the device maintainer simply (automatically) pull those new commits from the upstream (main) Lineage repo?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
Yes, to be clear, it is just repackaging the individual files, not compiling from source. If we had the source code, we wouldn't need the proprietary blobs. The difference is mainly whether or not the vendor.img is distributed with the rom or if it is just assumed to already exist on the phone.

I'm not sure about this part- it might be automated, but the maintainer would have to fix merge conflicts or other issues that are handled differently in lineage. Something like verity or bootctl that have a different setting/implementation in lineage.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] wijewkyoc4gu8krwf4igg:
tested ROOT via https://www.xda-developers.com/how-to-install-magisk/

Only issue is CTS failed, however Magisk Module called as Universal Safety Net Fix, fixed the issue.

Everything works great, inc gapps pico, tested other gapps which failed.

Best way would be to install pico and add whatever else you need
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] snoopy20:
I can confirm the battery drain isn't much of an issue, it seems to be more the initial algorithm then actual drain. It's still not as good as stock but not drastically far from it.

To my eyes this ROM makes the phone usable!
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] hga89:
What might the reason be that LOS uses more power than stock?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
I think the battery is pretty good...
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
This is almost 2 days with no charging and over 6hrs of screen time. I am a light user, so ymmv.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] hga89:
Your answer does not address my question. I am not sure what "pretty good" is, particularly since my question was in response to a comparative statement by somebody else.