yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] :
He sent you a photo with complete battery usage. Not much else he can explain to you.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] hga89:
Well, someone claimed that LOS was less energy-efficient than stock which is what I am trying to understand the reason for.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] :
Well, it is less energy efficient, this rom is in very early stages of development and has already switched developers 2 or 3 times. Infact, theres not that many roms for any device that will give you better battery life than stock.

Edit from the looks of the thread there was 1 build released by the OP. Then another couple untested builds by another developer. And you want to know why the battery is worse? Cmon man.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] codethief:
I actually think [MENTION=3443260]hga89[/MENTION] raised a valid point here. For a lot of phones LOS (without gapps) *is* more efficient, for the sole reason that most stock ROMs come with gapps and lots of other battery-draining apps. So I, too, would like to know what's causing the battery drain here (provided [MENTION=1096286]snoopy20[/MENTION]'s experience is reproduceable) . On the three phones I've used LOS on so far, LOS always used to be between 30 and 50% *more* energy-efficient than the stock ROM they came with and *never* less efficient.

Anyway, I just bought a Pixel 3a and will give it a try myself. I'll report back in a couple days.

EDIT: I just came across this thread on Reddit. [MENTION=1096286]snoopy20[/MENTION], might the WiFi scanning functionality be the issue for you?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] :
Its actually quite stupid to wonder why a 1 off release of an unofficial version of a completely unoptimised rom is less efficient than stock.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] snoopy20:
I don't use wifi so it won't be that (unless it occurs when wifi is off).

Basically I get a good 15% less battery over night than the stock ROM (completely clean install, no gapps etc). Perhaps it's wake ups, I'm not an expert though I'm happy to do some investigative work if someone wants to point the way.

This ROM is still my main driver, if it weren't available I'd have sold the Pixel 3a.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] el_ruwen:
First of all, thanks for this amazing rom. It works quite well for me. My first battery charge lasted 3 days (I didn't use it that much), now it lasts normally two days and a bit. I dont use any gapps. I have no comparison with stock, I bought this phone and put straight this rom on.

The stock camera works most of the time. Just sometimes when I press the take photo button in the app it becomes gray and does not record a picture. I started a few days ago to use an open source photo app from f-droid called open camera. So far it works fine. So if you dont want any google stuff on your phone, that might be a solution for you ;)

About root: I installed the addons/extra from the official lineage page. That works pretty well for stuff like oandbackup. But they don't support systemless root.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] wijewkyoc4gu8krwf4igg:
Bit of an issue, when rooting I've come across an issue where the fingerprint sensor will not be detected by Apps.

With AFWall+ for instance, it says "Your device lacks a fingerprint sensor", however If I go to add a fingerprint in settings, it works fine.

Banking application and Password manager also cannot see fingerprint sensor.

Reboot doesn't resolve issue.

Does anyone have a fix?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] matt4321:
Are you saying it doesn't detect the sensor when you have no fingerprints registered?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
FYI - I haven't forgotten about these pie builds. If anyone is trying to build it for themselves, feel free to shout out if you have any questions.

I'm waiting for these commits to get merged and then I'll fire up a new los 16 build for sargo.

https://review.lineageos.org/q/topic:"P_asb_2019-10"+(status:open OR status:merged)
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
I have a new los-16.0 build, but I'm not able to test it myself. My test phone is already on qberry.

PM me if you are able to test this and I'll send you the link.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
Here's the latest lineage-16.0 unofficial build. This includes the October security patches and pulls in bonito specific changes from aosp android-9.0.0_r47. We don't have an updated vendor image for pie, so the vendor image is still on the most recent pie vendor.

I'm not able to test this build, but I did test a parallel build. They have the same basic code, but this build is more stock.

https://brownbagdinner.com/lineage-16.0-20191015-UNOFFICIAL-sargo_2937e0f5.zip

Device tree is here. https://github.com/gee-one/android_device_google_bonito
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] klingels:
Thank you for providing that untested build. I want to give it a try.

How do I do an update - no clean install - with that zip?

I tried to flash it with twrp and I was not successful. That means I checked the build number after flashing and it didn't change.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
The build number should be the same since there are no more pie updates. Look at the build date. It should be 2019-10-14 or so.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
Did the build date change? Were there any errors in trwrp?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] wijewkyoc4gu8krwf4igg:
Disregard, it was the privacy guard blocking the fingerprint sensor for applications. Issue resolved

---------- Post added at 04:05 AM ---------- Previous post was at 04:02 AM ----------

Thank you for this, however how can I update the current build to this one without having to do a clean installation and loosing all my data?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
If you are on the last unofficial build from Sept, you should be able to dirty flash in recovery. I use the LOS recovery that is already included. I think you should be able to flash in TWRP as well, but I am waiting for [MENTION=2915929]klingels[/MENTION] to confirm. I would test on my phone, but my bootloader is locked on my daily driver, so I would lose data to test this; and my test phone is on qberry.

If you have another custom rom installed that uses test-keys, you might be able to dirty flash on top, but typically when switching roms, you have to wipe data first.

Edit: in LOS recovery, you would use adb sideload to flash the rom:

1) go into LOS recovery

2) select apply update

3) select apply from ADB

4) on PC, type adb sideload lineage-16.0....blah.zip (you might have to make sure your path is correct)

5) it takes a few minutes to flash... and the percentage will start and stop a few times.

6) once done, reboot

In TRWP, it's similar, but I think the ADB sideload option is under the advanced menu
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] klingels:
I had no luck with flashing it via TWRP > Install.

Instead, since you mentioned "adb sideload", this time I tried to use "adb sideload" from within TWRP:

0) # With USB-Debugging via USB connection:

1) adb reboot bootloader

2) fastboot boot twrp-3.3.1.img

3) # TWRP > Advanced > Sideload: Wipe ✓Dalvik Cache

4) adb sideload lineage-16.0-20191015-UNOFFICIAL-sargo_2937e0f5.zip

Both ways don't update my LOS on my device.

No, the build date didn't change. It is still "Wed Jul 10 01:03:14 DST 2019".

LineageOS-Version 16.0-20190710-UNOFFICIAL-sargo.

I had no errors in TWRP.

How did you manage to "go into LOS recovery"?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
Either 1) boot into fastboot and hit the vol up button until it says enter recovery, then hit power; 2) of you have the advanced power menu turned on in the rom, you can hold the power button down until the menu pops up, and select recovery.

It sounds like twrp isn't switching slots, maybe? If you know how to check what slot you're on, you could check to see if it's really switching. The other thing to check would be if it's actually flashing. You could get the md5 hash of the boot partitions before and after flashing to check that it changes. You should be able to do this through adb in recovery.

I stopped using twrp since it has issues decrypting data. Los recovery is stable and works for flashing roms.

I'll post the image files later- it might just be easier to flash in fastboot.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] codethief:
Your condescending tone aside, you might want to consider that gee one's ROM is using the original vendor blobs and drivers which are all specifically tailored to the Pixel 3a's hardware. So "unoptimized" is far from the truth. This is not nearly the same difference as, say, the one between running the Noveau vs. the Nvidia driver on Linux.

--

Back to the original problem: I installed the ROM last week and left it running for a while (with WiFi and Bluetooth enabled, though not connected to any WiFi network and also without any SIM card and without any apps that hadn't already been there by default). After eight days, during which I only touched it once or twice a day to check the battery percentage, the phone was at 50%. That's really not bad I think, though of course it's hard to say how much that means in practice.

[MENTION=2790198]gee one[/MENTION]: I noticed that the builds you've published are engineering/debug builds (at least according to the "Build Number" I'm seeing in "About Phone" which is "lineage_sargo-userdebug 9 PQ3A.190801.002.eng.root.20190918.195730 test-keys"). I'm aware that debugging features might make your life easier but I still think it might be a good idea releasing production ("user") builds since the AOSP docs have the following to say about debug/engineering builds:

So maybe production builds will have an (even) better battery life? :)
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
I'm not sure how big a difference there is between user and userdebug builds in practice. I think some of the debug software isn't actually included, but I could be wrong.

---------- Post added at 12:18 AM ---------- Previous post was at 12:14 AM ----------

Oops, I hit send too early.

I get around 2-3 day's of use, but I'm also a light user. It's usually 4-6 hours of screen time.

I'll look into the user builds, but I don't have a great way to test it anymore and not a lot of time. I'm trying to upgrade some computers, including my build box.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
Here is the same lineage 16 build as images that you can flash in fastboot. See the readme file in there for some vague flashing instructions.

It's a tar archive that is lzma compressed. Most linux distros should be able to open it with ease (tar xf lineage-16.0-20191015-UNOFFICIAL-sargo-images_2a1bb832.tar). I heard that windows treats it as an archive within an archive so you have to uncompress it twice. I never tried on windows, so there's that.

https://brownbagdinner.com/lineage-16.0-20191015-UNOFFICIAL-sargo-images_2a1bb832.tar

Happy Flashing!
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] spinxen:
Thank you for your work!

I can successfully unpack this file using tar xf under Ubuntu-shell i Windows.

Following your provided instructions

fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta
fastboot flash vendor vendor.img
fastboot flash system system.img

... i get stuck during 'vendor' flash, error message: "FAILED: (remote : 'Partition should be flashed in fastbootd')

Lucky i can flash back to stock rom using sargo-qp1a.191005.007-factory-664181b1:

fastboot flash bootloader bootloader-sargo-b4s4-0.2-5736883.img
fastboot reboot-bootloader
fastboot flash radio radio-sargo-g670-00025-190805-b-5781381.img
fastboot reboot-bootloader
fastboot -w update image-sargo-qp1a.191005.007.zip

Any ideas?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
It looks like you already flashed qberry, which has dynamic partitions that can't be flashed in fastboot. I haven't found a way to go back to pie after flashing qberry.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] spinxen:
Thanks for a quick answer. Excuse me tho for beeing a n00b here, but what is qberry and how can i proceed if i want to install LineageOS on my Pixel 3A?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] fhude:
You could try to flash last p stock factory image and then install gee one's last lineage package. That's what I did coming from stock Android 10.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
qberry is what I call Android 10 (or is it is X?) Google got rid of the dessert names with 10 and switched to numbers. I like desserts.

Lineage is not official for pixel. There are unofficial pie/lineage-16 builds in this thread. Lineage-17 is definitely not out yet, official or otherwise.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] spinxen:
I belive this is what i did. Gee one's last package as 'lineage-16.0-20191015-UNOFFICIAL-sargo-images_2a1bb832.tar'? This is the one i where i got stuck at vendor.img flashing in fastboot... described in my previous post.

I also tried TWRP flashing your previous file 'lineage-16.0-20191015-UNOFFICIAL-sargo_2937e0f5.zip' with no success, this failed half way.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] fhude:
I used the same lineage package and installed it this way:

cd sargo-pq3b.190801.002/

./flash-all.sh

boot stock and complete installation

adb reboot bootloader

cd lineage/

fastboot flash boot boot.img

fastboot flash dtbo dtbo.img

fastboot flash vbmeta vbmeta.img

fastboot flash vendor vendor.img

fastboot flash system system.img

fastboot boot twrp-3.3.1-0-sargo.img to install magisk
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] rocktone:
I don't suppose you'd be willing to write up a guide on how to build it for yourself? Currently a little bit lost on it -- how do I merge the device trees? (do I do that?)
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
This will get you 90% of the way there. Just sub out sargo for sailfish.

https://wiki.lineageos.org/devices/sailfish/build

As far as I know, there are no official sargo builds yet.

There are some significant differences for sargo/bonito. One is that there is no recovery partition since it's an A/B device with system as root. This will change how flashing works.

It might require a newer version of fastboot and adb.

And the extraction scripts are different since it works for both bonito and sargo. Examine the extract-files.sh file to see the syntax.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] rocktone:
Thank you so much for your help! I think I figured out most of it following the older guide that I found further back in this thread....

However, I guess what I'm confused about is: should I run extract-files.sh, or should I follow the instructions found here, where he extracts the proprietary files from the binaries, which google provides here? It's unclear what I'm supposed to do. That's why I was hoping you could provide a quick guide on how you're building building LineageOS for the 3a.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
So the links that you are following are building the vendor in the aosp way. It pulls in the aosp proprietary files (google_devices and qcom) and this would be the same as building aosp. For pie, use the last pie build, and not a qberry rom.

For los16, I build my rom a little differently. I use the aosp vendor image (part of the google_devices tar) and also some proprietary files from the los device tree (look at the extract-files.sh in the sargo folder).

There is a readme here as well as the source. This could replace the los device tree that you sync'ed. The commit history is probably amateurish at best, so be warned. Once you see how the sausage is made, you probably won't want to eat it.

https://github.com/gee-one/android_device_google_bonito
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] rocktone:
Ok, I understand now. So if I want to replicate your work, I can either do it the manual way (take the aosp vendor image, and also run extract-files.sh like you mentioned), or I can do it the faster (but uglier) way by following the readme instructions and editing the roomservice.xml file.

Is my understanding correct? If I run extract-files.sh and take the aosp vendor image, I'll get an identical result to doing it the automatic way? Or am I misunderstanding (... I probably am)? Does that repository actually have proprietary files or are they just a path to generating them?

Sorry I'm so befuddled... this should be easier for me to figure out.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
The info in the read me file is just for adding my version of the device tree to your build. You still have to get the proprietary files with the extract script.

---------- Post added at 04:07 AM ---------- Previous post was at 04:04 AM ----------

This might work as a shortcut, but I think the sim manager will crash a lot. I think you can disable it in the vendor tree or in the settings once the rom boots. It might be OK if you flash gapps, but I haven't tried it.

https://github.com/TheMuppets/proprietary_vendor_google/tree/lineage-16.0/bonito/proprietary

---------- Post added at 04:08 AM ---------- Previous post was at 04:07 AM ----------

Adding the muppets repo will add the vendor/google directory and you won't need the extract script. You'll still need the vendor.img in google_devices/sargo/....
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] rocktone:
Ok, let me know if I'm understanding the steps right:

Follow your readme to add your device tree to my build.

Get the vendor images (like you said, part of google_devices.tar)

Get the proprietary files from the los device tree with extract-files.sh

profit ???

Or use TheMuppets build (which I might do but I'd rather do things the way that keeps things simple ;) )
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
Yup, that sounds right. Getting the vendor from muppets might be easier to start. Once you get a complete build, you can get extracting the proprietary files from the rom yourself.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] rocktone:
Thank you my friend! You are the best! :D
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] rocktone:
One more dumb question: do I still need to do breakfast sargo? Just want to triple check that I'm doing things right:

Basically I'm thinking something like:

source build/envsetup.sh
breakfast sargo
breakfast bonito
repo sync
breakfast sargo
repo sync
breakfast sargo

add manifest to build...

get vendor images

./extract-google_devices-sargo.sh

Go to the bonito device tree:

cd bonito
./extract-files.sh
cd ../sargo
./extract-files.sh

And then....

brunch sargo

That is a (really rough) outline of the commands I plan to run....

Edit: I did it... it took forever to build... I issued fastboot flashall -w... and it works.... with everything intact -- VOLTE and all!! Wow!! Thank you dude; I would have been so lost without your help. You rock!
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
Great job! You can turn on ccache to speed up builds too.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] n.pikota:
Hello. Has anyone built los17?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
It's buildable. The esim app is crashing similar to los-16, but that is easy enough to remove from the proprietary files.

If you don't want gapps or magisk or root, then it's probably very close to daily driver status. I'm not sure if that stuff would work or not. It might, but I haven't tested it.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] n.pikota:
Thanks for the answer. And why do gapps and magisk not work?
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] gee one:
I haven't tested gapps or magisk, so I don't know if they work or not.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Neo:
Yes

No

I don't know
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] matt4321:
Well... well... well...

Look who found me still lurking on XDA
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] patrickfenn:
Some feedback after a weeks use, I find that sometimes the bluetooth will randomly "disconnect" even though it still shows connected, have to restart bluetooth to get it to work. Otherwise I find that its a ok alternative from stock, might still return to it though because the camera quality is terrible. I guess google software really did make that much of a difference.

During setup I could not for the life of me get twrp flashed. Every attempt would end in a bootloop, finally relented and just temp booted twrp to install magisk and didn't bother.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Mokura3rd:
Try OpenCamera: https://f-droid.org/en/packages/net.sourceforge.opencamera/

Or Simple Camera: https://f-droid.org/en/packages/com.simplemobiletools.camera/

You'll need to install a custom kernel like ElementalX due to certain requirements for installable TWRP on the Pixel 3a. So you'd just need to-

1. Temp boot into TWRP.

2. Install ElementalX 1.06: https://elementalx.org/devices/pixel-3axl/

3. Reboot into the ROM at least once.

4. Temp boot into TWRP.

5. Install the TWRP zip. You may also need to re-flash Magisk.

6. Boot into your ROM, check and see if Reboot to Recovery works.
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] bargainbums:
TWRP INSTALL INSTRUCTIONS - mostly dummy guide =)

MAKE SURE YOU'RE ON ANDROID 9.

IF NOT - https://developers.google.com/android/images#sargo

I used the last 9.0 firmware - install this first or else none of the steps below will work properly.

https://www.**********.com/install-stock-firmware-on-google-pixel-or-restore-it-to-stock/

INSTALL LINEAGEOS FIRST

fastboot flash boot boot.img

fastboot flash dtbo dtbo.img

fastboot flash vbmeta vbmeta.img

fastboot flash system system.img

fastboot flash vendor vendor.img

fastboot -w (to wipe cache and data)

INSTALL SPECIFIC KERNEL

Link (the one I used) - https://xdaforums.com/pixel-3a/development/kernel-pixel-3a-xl-elementalx-1-01-t3931185

or alternative link - https://xdaforums.com/pixel-3a/development/mod-blackenedmod-v1-0-pixel-3a-pixel-3a-t3946070

Install TWRP (download both files) : https://twrp.me/google/googlepixel3a.html

fastboot boot twrp-3.3.1-1-sargo.img

TRANSFER ZIP FILE downloaded from above and install using the TWRP temp boot

Finally - install Magisk. THIS MUST BE LAST.

YOU CAN NOT INSTALL MAGISK FIRST, THEN INSTALL TWRP. I made that mistake for a few hours until I figured that out.

https://github.com/topjohnwu/Magisk/releases

You're set
[Google Pixel 3a ROMs, Kernels, Recoveries, & Other] Bokka80:
Just a question: both pictures and videos taken with this rom (or in general all custom roms for that device) will have the same quality of the stock rom?