yashsingh1/xdaforums huggingface dataset:
[Google Pixel 5a] aleasto:
LineageOS is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.

LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. LineageOS does still include various proprietary hardware-specific code.

All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

Informations :

This ROM uses source built kernel, kernel modules, boot kernel modules (vendor_boot) and vendor image.

This ROM bundles the latest firmware so you don't have to worry about updating firmware.

To use the eSIM you need to have GApps

Instructions :

Follow https://wiki.lineageos.org/devices/barbet/install for how to install

Follow https://wiki.lineageos.org/devices/barbet/upgrade for how to upgrade from LineageOS 19

Downloads :

Official builds

Optional GApps: MindTheGapps

Reporting Bugs

Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)

If it is a random reboot, grab /sys/fs/pstore/*

If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log

Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved.

Known Issues

Google Play Store provides a very out of date version of Google Camera. You can use GoogleCamera.apk extracted from stock here

Contributors

mikeioannina

aleasto

The LineageOS team

Source Code: https://github.com/LineageOS

ROM OS Version: Android 13
[Google Pixel 5a] aleasto:
Source code temporarily on my github before it can be moved to the LineageOS organization
[Google Pixel 5a] CapriciousCrawdad:
Thanks for putting this together so quickly! I've been running for a couple of days now with MindTheGapps and haven't noticed any significant issues. I'm now pretty darn satisfied with my new 5a (Even though it's a friggin chonk). I'm on Visible and I was able to just pop my SIM card in and everything worked. Wifi calling, texting, 5G connection, etc - all good.

Only weird thing I've noticed is that after setting up fingerprints for device locksreen security I'm not able to then use fingerprint security within my other apps. For example - Chase app tells me "You haven't set up fingerprint sign in on this device", PayPal app says "We're having trouble confirming your fingerprint right now" and Bitwarden app doesn't present an option to enable "Unlock with Biometrics". So I'm using currrently using PINs for these apps which is a fine compromise for me - would be curious to know whether others have experienced this.

There have been some changes to SafetyNet in the past couple of days that tripped ctsProfile on my Pixel 4a running official LineageOS but I was able to pass SafetyNet check in this ROM by installing kdrag0n's Universal SafetyNet Fix v2.0.0 and using MagiskHide Props Config to set device fingerprint to Pixel 5.
[Google Pixel 5a] aleasto:
I doubt you need to set device fingerprint to Pixel 5 for safetynet.

Will fix fingerprint in apps in the next build now fixed
[Google Pixel 5a] grassyloki:
Thanks for the build! it seems mostly good from my testing but one issue im having... for some reason the phone refuses to connect to the carrier after a sim card is inserted. I can see that it is detecting it, and that it sees that it should be using t-mobile, but It wont connect. Not sure if this helps, but i got a logcat of adding the simcard and airplane mode toggling on/off. maybe there is a useful log in there. Log is here. Thank you for your hard work!
[Google Pixel 5a] aleasto:
I'm afraid i don't know what's wrong.

Can you try with adb logcat -d -b radio
[Google Pixel 5a] grassyloki:
Here you go
[Google Pixel 5a] CapriciousCrawdad:
You're right. I'm passing now with Pixel 5a fingerprint.

Also thanks for the quick update. After flashing 09/07 build all the biometric security stuff is working as expected. All apps I'd listed in my previous post are fixed.

No new issues to report. Loving the setup 😄
[Google Pixel 5a] aleasto:
New build out with september security patch
[Google Pixel 5a] aleasto:
@grassyloki Does your radio work on the latest build by any chance?
[Google Pixel 5a] TheSayaMan:
I can verify radio is fine on my phone. Maybe it's carrier related. I'm on Google Fi with E-sim.
[Google Pixel 5a] grassyloki:
The build did not initially... but some fiddling with hidden menus eventually triggered cellular to activate!

See this video as to the issue. Basically the phone was seeing the SIM but not activating, same as the other builds. Airplane mode did nothing, even leaving it for an extended period of time off. I did get it eventually working by heading into the secret menu *#*#4636#*#* in the dialer, then the phone info screen. In here I cycled mobile radio power and changed the prefered network type to something different. Then Cellular activated. Once that happened, i went and selected the correct APN and enabled mobile data, and it worked! Not sure if any code change effected this outcome, but im just glad its working now! Thanks for the build and looking at my issue. Maybe this will help someone out who is having the same issue.
[Google Pixel 5a] Zedicus:
does the lineage updater work on this build or whats the process to update to the newest build?

thanks
[Google Pixel 5a] weeems:
The recovery I flashed keeps telling me that "E:Failed to open /dev/block/bootdevice/by-name/misc: No such file or directory"

Flash Factory Reset also fails for that reason.

I am unable to Enable ADB to Flash Lineage OS for this reason. What am I doing wrong? I used https://mirrorbits.lineageos.org/recovery/redfin/20210908/lineage-18.1-20210908-recovery-redfin.img
[Google Pixel 5a] aleasto:
Updater does not provide unofficial builds.

Boot recovery and sideload the new zip. If you had addons (gapps, magisk), reboot recovery and flash them again, like the first time.
[Google Pixel 5a] Nburnes:
Pixel 5a is barbet. That recovery says it's for redfin (Pixel 5).

You need to download the recovery from the sourceforge link in the OP.
[Google Pixel 5a] aleasto:
Uploaded a new build.

No differences except some experiments on kernel side (branch redbull-merge for the sources). Please let me know if audio still works:

https://sourceforge.net/projects/aleasto-lineageos/files/LineageOS%2018.1/barbet/lineage-18.1-20210911-UNOFFICIAL-barbet.zip/download
[Google Pixel 5a] Zedicus:
Is there a prebuilt magisk for this?

I am on 0909 and audio has been working. It does not get real loaud but otherwise works fine.

Thanks for the build.
[Google Pixel 5a] aleasto:
Just adb sideload Magisk-v23.0.apk in recovery
[Google Pixel 5a] reichstah:
Just got my 5a delivery today. Applied today's image, worked without any issues whatsoever. Fantastic work, very much appreciated.
[Google Pixel 5a] andy356:
Oops, I forgot to follow up. Going from 19 to 20 removed Magisk, as you said. And re-flashing the Magisk zip after the update worked absolutely fine. The APK stays installed through the upgrade, only the zip needs to be re-flashed. So here's the procedure for anyone needing reassurance.

- Upgrade from 19 to 20.

- Boot into the OS.

- Open the Magisk app and notice that the Magisk zip isn't installed.

- Reboot to recovery and sideload the Magisk zip like usual.

- Reboot and open the Magisk app again. Magisk is now installed.
[Google Pixel 5a] mac62:
I took the plunge to, and it seems to be pretty great except for the battement life. Curious what you are experiencing.

I'm rooted with Canary, Zygist and the most recent universal safety net fix. Lost 15% over night with no usage. Stock battery monitor says Duck Duck Go used 15%. I'm going to clear the app, and maybe disable it to see if it is really the problem.

Update. Looks like it was DDG. I was using the app tracking blocker, and it was chewing up the battery. Reached out to the DDG people to report bug.
[Google Pixel 5a] barydos:
I used to love Pixel Experience, but since last year it doesn't work with Google Wallet/Pay.

Does this ROM work with Google Wallet/Pay? And does it have features such as brightness slider (status bar), and swapping the order of the navigation bar? Cheers
[Google Pixel 5a] mac62:
I just did my first update of 20.0 through the System/Updater and lost root then too. Flashing the patched boot image fixed it, but I never had to do this on 19.1. Root was always retained through updates.
[Google Pixel 5a] andy356:
You're using the incorrect method. You're not supposed to patch anything. Simply 'adb sideload magisk.zip' in LOS Recovery, like aleasto said earlier in the thread.
[Google Pixel 5a] andy356:
@aleasto The barbet changelog page (https://download.lineageos.org/barbet/changes) has suddenly started showing commits from the LOS 19 branch instead of 20. I've checked a few other device pages, and none of them have this problem.
[Google Pixel 5a] portsample:
Installed the nightly build on my Pixel 5A with no problems after having been away from Lineage since Android 8. What is the accepted means of rooting at this point? Would Magisk with a patched boot.img be reasonable? TIA
[Google Pixel 5a] BTK19:
Reboot to Recovery click Apply Update and then Apply from ADB then adb sideload Magisk
[Google Pixel 5a] portsample:
Yes, that worked.

Put the following in a directory on the PC to sideload onto device:

-Lineage recovery from here: https://download.lineageos.org/devices/barbet/builds

-LineageOS image for device from here: https://download.lineageos.org/devices/barbet/builds

-current GAPPS for 13.0 from here: http://downloads.codefi.re/jdcteam/javelinanddart/gapps

-current Magisk-v25.2.apk from here: https://github.com/topjohnwu/Magisk/releases/tag/v25.2

Enable developer settings on device. Unlock boot partition by enabling OEM unlock in the developer options under device Settings.

Allow USB debug setting. Connect device to computer with USB cable.

Open command prompt in directory containing above files.

-----To unlock the bootloader do the following...

Type "adb server-start"

Type "adb reboot bootloader"

Type "fastboot devices" to confirm device is detected.

Type "fastboot flashing unlock" to unlock bootloader. Device should reboot.

May need to re-allow developer settings and USB debug, etc.

-----To install the LineageOS custom recovery do the following...

Type "adb reboot bootloader"

Type "fastboot devices" to confirm device detection.

Type "fastboot flash vendor_boot vendor_boot.img"

Reboot into recovery to verify the installation using the bootloader menu to navigate to and to select the Recovery option.

In recovery, select "Factory Reset", then "Format data / factory reset" and continue.

-----To sideload the LineageOS custom rom do the following...

Return to main menu.

On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.

On the host machine, sideload the package using (typing): "adb sideload lineage-20.0-20230309-nightly-barbet-signed.zip".

This can take a long time (5 mins)

-----To install GAPPS, do...

Even though you are already in recovery, click Advanced, then Reboot to Recovery

When your device reboots, click Apply Update, then Apply from ADB tobegin sideload.

On the host machine, sideload the package using (typing): "adb sideload MindTheGapps-13.0.0-arm64-20221025_100653.zip"

Reboot into LineageOS.

-----Rooting with Magisk

Change suffix from.apk to.zip, Magisk-v25.2.apk to Magisk-v25.2.zip.

Open a command prompt terminal in this directory.

Type "adb server-start"

Type "adb devices" to confirm detection.

Type "adb reboot recovery"

On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.

On the host machine, sideload the package using (typing): "adb sideload Magisk-v25.2.zip"

Wait for the process to complete. Once done, select Reboot System now.

Magisk should prompt for the user to complete installation.

Note: this method of rooting ("Custom recovery") is described as outdated on Magisk site here: https://topjohnwu.github.io/Magisk/install.html
[Google Pixel 5a] Super Jamie:
Many thanks to aleasto for keeping this alive.

I hadn't upgraded since the last LineageOS 18.1 image, so the process to upgrade to 20.0 wasn't quite straightforward. Flashing the latest LineageOS Recovery over the 18.1 recovery just boot-looped.

It was necessary to flash the Android 13 official factory image and boot into the official OS. Then installing LineageOS Recovery worked. It was also necessary to perform a Factory Reset inside LineageOS Recovery before installing, as portsample just listed above and as the official wiki says.

Note that this wipes all user data (including internal storage) but I intended to do that anyway to get a nice fresh start, so everything was copied off before I started. Always have a backup!

Hopefully that helps someone else in the same situation.
[Google Pixel 5a] 306bobby:
Why do that. Grab the boot.IMG from lineage, patch it with the apk, then reboot into bootloader and fastboot flash boot the new patched img
[Google Pixel 5a] 306bobby:
In regards to that method being outdated, read my post above. Also safetynet-fix mod by displax fixes safteynet and allows for google wallet and tap to pay to work
[Google Pixel 5a] BTK19:
That's a lot more steps to do the same thing
[Google Pixel 5a] 306bobby:
Once you make the patched boot file just fastboot flash it every time there's an OTA. Can make it an automated batch file even, that's what I did
[Google Pixel 5a] BTK19:
root persist after an OTA update for me with magisk​
[Google Pixel 5a] rodken:
What about the method to updating to a newer version of MindTheGapps without borking the system?
[Google Pixel 5a] 306bobby:
Honestly never updated it yet haha... But recovery is the only way for that afaik
[Google Pixel 5a] andy356:
I don't use any GApps. If it's feasible, you could also try going without. It's very liberating. (No, that wasn't a pun about free software.)
[Google Pixel 5a] sinkoo1979:
Thanks for the rom. Running smooth. Great battery life!!!
[Google Pixel 5a] Steve Graham:
My phone won't install OTA updates for some reason. They download, but an attempt to install always results in the highly informative message "Install error". (What genius came up with that?)

I can sideload zips with ADB and install boot.img in fastboot, but recently the download website also has dtbo.img, super_empty.img, vendor_boot.img and vbmeta.img - should I be doing anything with these images? I don't want to brick my phone.
[Google Pixel 5a] sinkoo1979:
I just flashed the new built (did not flash any other files other then the lineage update rom). I sideloaded the rom, reboot to recovery and flashed the same gapps that I used on the initial install. So far no bugs. Hope this helps.
[Google Pixel 5a] Steve Graham:
Thanks. Yes, I now see that the OTA update only includes the lineageos zip, so sideloading that alone is probably correct. Here goes.
[Google Pixel 5a] andy356:
@aleasto Do you still use this device?
[Google Pixel 5a] andy356:
Has anyone in this thread encountered the infamous Pixel 5a motherboard issue which killed their device? A large number of users have reported it, even on XDA, but I haven't seen any LOS user talk about it.
[Google Pixel 5a] eqroiueq:
After updating to the Nov 13, 2023 OTA, the network traffic monitor in the status bar shows the units as "LiveDisplay" when I have it set to "kB/s" and always displays "unknown unknown" (speed, units) if I have it set to automatic. The other options seem to work as intended.

kB/s:

Spoiler content hidden.

Automatic:

Spoiler content hidden.
[Google Pixel 5a] holypaulie:
Is it better the stock room?
[Google Pixel 5a] sinkoo1979:
To me, Yes
[Google Pixel 5a] eqroiueq:
Is there still a build of LOS 20 available? I'm looking for something newer than 20240209 if possible. I'm not interested in upgrading to A14 yet, but want to switch back to LOS from another rom.
[Google Pixel 5a] aleasto:
New build with new kernel experiments targeting official release.

Please test and report whether audio works still:

https://sourceforge.net/projects/aleasto-lineageos/files/LineageOS%2018.1/barbet/lineage-18.1-20210912-UNOFFICIAL-barbet.zip/download
[Google Pixel 5a] Zedicus:
dirty flashed.

MEDIA audio is JUST BARELY audible at max volume. in any player or browser.

alarms, and phone calls are fine.
[Google Pixel 5a] aleasto:
is that different from before, or?
[Google Pixel 5a] Zedicus:
on the 9-9 rom i could start to hear MEDIA at 1/2 volume and up.

on this newest rom i can start to hear MEDIA at 3/4 volume and up. so yes, media on the newest rom borders on unusable.
[Google Pixel 5a] aleasto:
can you get me these logs:

adb root
adb shell lsmod > lsmod.txt
adb logcat -d > logcat.txt
adb shell dmesg > dmesg.txt
[Google Pixel 5a] Zedicus:
as requested, do these need scrubbed?? i didnt look through them.

converted to PM
[Google Pixel 5a] elisam98:
Thanks for the hard work, @aleasto ! Do you have a link to the proprietary blobs sources? Wanted to try to spin a custom build myself...
[Google Pixel 5a] aleasto:
Soon on TheMuppets. But they're simply extracted from the latest OTA, as always
[Google Pixel 5a] MetalJulia:
I tried building TWRP with these sources in hopes it could produce a working product, but I got arcane errors that seemed to originate from the build system trying to build both the normal Lineage recovery and the TWRP. Any ideas what that's about? I've deleted the files but can try again.
[Google Pixel 5a] aleasto:
Official builds set to start on Thursday at https://download.lineageos.org/barbet
[Google Pixel 5a] tlby:
Built from source last week (using bramble instructions at the time) with no issues, and tried the nightly build today. Seamless both times, thank you!
[Google Pixel 5a] Bobyouall:
So if I have the previous unofficial build installed, can I dirty flash the official nightly with no issues?
[Google Pixel 5a] aleasto:
no
[Google Pixel 5a] Bobyouall:
Alright thanks for the response!
[Google Pixel 5a] v3c7r0n:
Thanks for all your hard work Aleasto, I just ordered my pixel 5a yesterday and I am looking forward to installing Lineage on it!

I'm coming to the Pixel 5a from an LG V30 running SGCMarkus' 17.1 unofficial build as it does not and never will have VoLTE and...CDMA service here is "usable" - in the sense of you can make a call...eventually and maybe, if you're lucky you'll be able to talk long enough to finish your conversation without the call dropping

I do have a few questions (not specifically for anyone, they're general questions):

- I hadn't been able to find this specific question answered, but does VoLTE work on Verizon with this build?

- I know "Ol' Faithful" Titanium Backup has been defunct for awhile now but it was what I'd always used. Does it still work for moving data? Specifically SMS/MMS messages, call logs, bluetooth pairings, remembered wireless networks, and I know you can't restore apps anymore, but restoring data was still working when I moved to my V30 as long as you installed the app first. Is this still accurate or should I not even try?

- What do people use for backups these days? Since the Pixel has no micro sd slot (another phone, another feature that I had to trade off) I concerned about being able to backup my device, automatically on a schedule. I read that SeedVault was being adopted by Lineage as the "official" backup, but no new information on that front seems to have surfaced in almost a year.
[Google Pixel 5a] aleasto:
Yes we do support VoLTE.

I don't know about titanium backup.

If you're looking to transfer data from your V30 running LineageOS just use Seedvault, assuming that your unofficial build is recent enough to have that on 17.1.

It supports SMS, call logs, apps and their data.

Also if you use google services, their backup provider does the job as well.
[Google Pixel 5a] v3c7r0n:
Great, thanks again for all your hard work!
[Google Pixel 5a] michaelc5047:
Works like a charm! Thanks for your hard work on this. Any recommendations on a replacement for GCam, as the one on the Play Store is so old? I downloaded the latest Camera PX from the GCamMod hub and seems to work well enough -- just want to make sure I'm not missing any other obvious options.
[Google Pixel 5a] aleasto:
Oh just get the official apk from apkmirror or similar. Latest stable version is 8.2.400
[Google Pixel 5a] thx1200:
I successfully flashed recovery but when I try to flash LineageOS I get the "device offline" error. adb devices shows no devices attached. Fastboot works and I can flash both recovery builds on the Lineage website, but again can't flash Lineage from ADB inside recovery.

adb.exe sideload lineage-18.1-20210930-nightly-barbet-signed.zip

adb: sideload connection failed: device offline

adb: trying pre-KitKat sideload method...

adb: pre-KitKat sideload connection failed: device offline

adb.exe devices

List of devices attached
[Google Pixel 5a] aleasto:
On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
[Google Pixel 5a] thx1200:
Yes I did that. It has the "cancel" option but it is not responsive to the host. I tried another PC. I tried Linux and Windows. I made sure I was running either adb admin (windows) and sudo as Linux. I tried "enable adb" and "mount system" options in recovery as well (in case there was something there). I also tried the old recovery that is on Sourceforge. I redownloaded latest SDK (adb) for both Windows and Linux.

So in summary, same behavior (no devices listed) with:

- Two different PCs

- Linux and Windows

- LineageOS recovery, all three versions for this device

- Fastboot works

- Latest ADB

- Entering recovery, apply update, apply from adb, look for "now send the package" message, only other option is "cancel"

- run the adb sideload command, device not found.
[Google Pixel 5a] thx1200:
OK weird, it was the USB cable.

The cable worked for file transfer under Windows and also fastboot, but somehow with adb, it did not work. I have never seen that before, but, well, here we are.

If anybody else runs into this, don't overlook the USB cable. :)
[Google Pixel 5a] thx1200:
Two update questions:

- I just got notice for OTA update. For the OTA updates, do we need to disable/uninstall Magisk before applying the update?

- Is there a way to do a Nandroid (or similar) backup in recovery before applying an update so we can roll back if it goes wrong?
[Google Pixel 5a] aleasto:
If you installed Magisk by sideloading in recovery it will persist the update. Otherwise you'll need to reinstall it after the update if you want to keep root.
[Google Pixel 5a] zachariahpope:
@aleasto I just wanted to say thank you as this rom is so clean fluid, and fast. Much faster than stock Android. Camera quality is unreal. I was having a great experience on the Android 12 beta, but this is an even better experience. It's been a long time since I've had an Android device on lineage (or any custom OS), but your builds and the updates (as far as 10-14-21) have given me no issues whatsoever. I've retained root through every update and I'm still passing safetynet checks. Thanks again for all your hard work... For anyone curious, this is the best you can run on the Pixel 5a yet. 👍👍
[Google Pixel 5a] Pixel86:
To pass SafetyNet, do I need to install Magisk? I guess my real question is, does Lineage 18.1 pass SafetyNet out of the box, without root?
[Google Pixel 5a] aleasto:
You do need Magisk with Riru and Universal Safetynet fix modules
[Google Pixel 5a] MrPolite:
Received a brand new Pixel 5a 5G today and flashed this rom. @aleasto thank you for making this. This rom was the main criteria in my choice of phone.
[Google Pixel 5a] FitGirl32:
I saw in LineageOS site latest build - 20211022, is this an Android 12 version update?
[Google Pixel 5a] Slim2none4u:
No. Its says 18.1