yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
This change isn't finalised yet and is still on Lineage OS Gerrit. This should be improved before this is merged into Lineage repos. I completely agree with you.

EDIT: I talked to the commit author today. Here's what he had to say.

So yes this should be improved considerably over time.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
Twice in last 2 months - sideloading/flashing of lineage update and gapps over current lineage installation has caused a bootloop and asking to factory reset as data went corrupt. But other times it has been successful too. Any ideas where it could go wrong intermittently.

Situation: Existing Lineage (ver x) with openGapps-micro version, PIN locked (cant remove PIN else work profile gets deleted)

Steps:

1. Reboot to Lineage Recovery

2. ADB sideload the new lineage update (ver x+1)

3. Restart into Lineage recovery again

4. ADB sideload the open gapps again (Is gapps required to be flashed with each lineage update?)

5. Reboot into system

Outcome is

either: Lineage boots fine and i can see the (x+1) update in build

or : Lineage goes into a bootloop 2 times and then it asks to do a factory reset as data is corrupted. If i factory reset here then, then it boots fine with the new (ver x+1).
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
I've been dirty flashing every lineage build for at least the last month and a half and not had a single bootloop. I would think this is probably an issue with failing to flash gapps or remembering to reboot to bootloader before flashing gapps. Or perhaps its because you're flashing a newer OpenGapps package that has resulted in breakage compared to the one you used previously. Btw there's pretty much no reason to ever update your OpenGapps package once you find a working one. This is why I still recommend you use razorloves OpenGapps.

Yes, unfortunately you do have to flash gapps every update as addon.d is seemingly broken on wahoo at the moment. This is the last issue preventing official Lineage OS support. Since my taimen doesn't respond to adb or fastboot at the moment, I can't try and fix this until my new taimen arrives that I can actually flash gapps on.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
Thanks for explanation, i think reboot between ROM and gapps mostly ,,,, or the faulty gapps could be one.

Razorloves gapps sadly has the olden days pixel launcher which doesnt update in playstore.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
Ah I wasn't aware of this, I use trebuchet. I assumed pretty much all gapps would be updated by the play store. I'll try and find an updated working gapps package when I receive my new taimen. Thanks for informing me.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I like Eamo5 (and probably lots of other users) also dirty flash every single update, and never have had a single bootloop. I follow steps 4 on for the updates and always use/download the latest opengapps micro. I first remove the PIN, reboot to bootloader, ADB TWRP, apply the update, reboot recovery, flash opengapps GAPPs, then boot to system, fix MAGISK (boot.img updated in MAGISK then fastboot flash boot the patched .img), then I am golden and restore my PIN, have ROOT, updated OS and never ever have a single issue. There is no point in my mind, to install TWRP, as I ADB boot it whenever needed and its one-less thing to worry about (without having TWRP physically installed), I just ADB TWRP when needed (for updates really), TWRP is not needed otherwise (again my opinion) but it hasnt been a single issue for not having it installed. I leave the LOS recovery and everything works flawlessly. My final piece to the update, is to install EX Kernel (through the app with ROOT), then update and edit the build.prop in /system, thats it, updated to the latest, no corruption, nor issues. I use NOVA launcher pro so keep that in mind with EX Kernel and MAGISK / ROOT.

I dont know about razorloves GAPPs so I would stay away from 3rd party'ish GAPPs and stick with the recommended ones (opengapps). Again, I always update and download the absolute latest version of GAPPs every time I dirty flash (directly from opengapps website unless the version is the same as the one I previously downloaded and used). I dont think there is a conflict with the opengapps and the latest version of GAPPS with the latest release of LOS (as thats what I use and always use without an issue).
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Eamo5, I am using the "lineage-17.1-20200514" version (found under old builds, then taimen, then the latest build), with "open_gapps-arm64-10.0-nano-20200519" and its running as expected, no issues, bugs, or crashes so IDK if you want other users to test it, but its working great for me. LOS has been my daily driver for 3 weeks now (actually longer). I dirty flash (steps 4 on in the install directions) to keep it updated with your latest build releases, then I add in my own tweaks (build.prop, EX kernel, fix ROOT using boot.img), and so on after each update. It runs flawlessly!

All I am asking/saying is do you want this announced? Do you care or mind when I announce the builds after testing them (I test everything before I confirm it works flawlessly), or do you need to perform more testing on your side before its announced (I dont know your process for announcing new updates)? I do see ones available but not announced so IDK how you handle them? I am trying not to step on your toes, but also at the same time, I am trying to help you by letting others know the build is up and personally tested by me (and found no issues at all), so let me know!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
Typically this is where I put builds that I'm asking others from my telegram group to test. These usually only contain some very minor changes over the previous builds and they're typically experimental things I can't test myself. In this case, it was in regards to an esim change.

For most users, I'd advise to just stick the builds I have linked as there's no experimental changes that haven't been properly tested. Newer builds that I don't release on XDA probably won't be worth your time downloading and updating unless you know what to look for anyway.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Meowdib:
Join the telegram group.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I am in it :p

---------- Post added at 03:37 PM ---------- Previous post was at 03:35 PM ----------

Understood, thanks for the detailed reply, I wont announce, but I will test them all. I like experimental/beta testing so I am all in!

Still rocking LOS (your LOS) as my DD, it is truly awesome. Right before I tried yours, I was syncing the repos to build my own, but figured what the heck, let's test it for a few days, and havent changed since. I deleted the repos locally and only use LOS these days.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
Lineage OS 17.1 (27/05/20)

Properly implemented Black Theme in Settings -> Display -> Dark theme

Implemented dark theme for AOSP Dialer, Messaging and Contacts apps

Added option to exclude the top of the screen from the back gesture area

Updated AOSP Dialer, Messaging, Contacts and Clock apps to sdk29

Various bug fixes and improvements
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
Very lovely changelog. Things like custom vendor and these black theme stuff you doing for the folks - i hope they are merged upstream and more ROM Devs start implementing them. It would be awesome to have these much needed stuff across the board.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
everything works flawless! awesome, thank you!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xSpartacusx:
I cant sign into a google account. the screen goes black when the signin page pops up on the initial setup :(
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] all43:
27/5 build is super fast as the previous, no issues installing, I was a weekly rom hopper till the pixel xl2 slowed me down but this is the fastest 10 rom Ive tried and my daily driver,

Cheers
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
You have either done a dirty flash or otherwise flashed ROM and gapps in the same session wtihout a bootloader restart in between.

If so , please follow the instructions - i hv tried this build and is flawless in installation n run.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] xSpartacusx:
I ended up figuring it out, thank you!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] kingramon0:
I'm running a build of LOS 16. Has anyone tried flashing one of these builds without wiping userdata? I'm going to take a backup anyway, but if I can save time not having to restore it all after the upgrade that would be nice.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
Clean flash after may factory and then install LOS17, after that you can keep using it forever on month to month updates without cleaning data.

Better wait a few more days so you can start fresh with June.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
Lineage OS 17.1 (04/06/20)

June ASB

Linux 4.4.210

Updated firmware from June factory images

Implemented hide gestural navigation bar

Implemented quick QS brightness slider

Fixed a strange wallpaper bug

Various bug fixes and improvements
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I always wipe user data but not through ADB as that screws up the partition layout in TWRP until its formatted (/data), thats why you see all the mount errors after doing so, you need to follow up the erase user data with a reboot of TWRP (BOOTLOADER/ADB/TWRP), then format /data, then repeat reboot BL, ADB, then TWRP and finally you can wipe and all partitions are clean with no mount errors.

If you do not wipe user data (or format user data), you will run into numerous FC's or outright funky behavior. This is ESPECIALLY true if you are coming from a different version or ROM. The best bet is to flash the stock firmware (Google) with the -w, then start the process but without formatting /data, thats fine because its a clean base of a stock firmware, I do that all the time.

Just one man's notes, you can choose to do it my way, or not, up to you, but it definitely works for me every time!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jimmyjambo:
I'm liking the full-screen gestures! thanks [MENTION=9116297]Eamo5[/MENTION]
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] azoller1:
Is there any way I can access or receive .img files versus a flashable zip file for LineageOS? Building takes forever on my machine and TWRP doesnt seem to work properly on my device with the latest Android update. If not, I guess I can try building my own. Thanks!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jimmyjambo:
https://github.com/cyxx/extract_android_ota_payload

try that works for me.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] azoller1:
Did not know that tool existed! That seemed to work! I was able to boot up Lineage.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draekko:
I'm getting random reboots with the june build, any suggestion to try and debug it?

---------- Post added at 02:56 PM ---------- Previous post was at 02:44 PM ----------

Also Google payload dumper, i've used that one but the original repo i had found way back doesn't seem to exist anymore. Here's a what a quick search found:

the custom droid dot com /how-to-extract-android-payload-bin-file/

https://www.the***********.com/how-to-extract-android-payload-bin-file/

https://github.com/vm03/payload_dumper

can't vouch for either as i haven't tested them but doing your own search could bring up other alternatives.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] b00ster23:
First of all, beautiful work! Greatly appreciate a new daily driver without Google Services intruding upon my usage (and location details). So I'm on Big Red prepaid with my Pixel2, and too am getting the Carrier Service crash. In fact just got one as I received a text message. Would be happy to send a logcat, but assume you have a handle on the issue and VZW Carrier Bundles. To note Visual VM is broken, which makes sense if VZW can't connect to it's carrier cloud services. Anything I can let me know... Would be happy to jump in Telegram and test as necessary.

Keep Up The Great Work Shaggy!

EDIT: Visual VoiceMail doesn't work with VZW prepaid service so not related.

I do notice quite the lag in SMS RX....TX seems to go thru quick enough

EDIT#2

For whatever reason I had 2 Carrier Settings installed. Disabled the Google Version and now SMS does not lag and my app crashes have deceased. :)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] davschm:
Just found this Lineage build for Android 10 and I would like to give it a try. I will be coming from stock android 10, rooted with Magisk.

To prepare I have already backed up my personal data like pictures and videos. But i have a lot of apps configured that are hard to really backup. Like dozens of bookmarks in Firefox and chrome, games that don't save data to googles cloud, even google authenticator accounts. among other things.

I tried installing the newest TWRP and doing a backup, but that fails every time, and looking in the thread it seems that that's normal with new android versions.

If I follow the instructions on the first post it says "3. Wipe userdata" What will I lose if i do that? Is there any way to save or migrate my app settings like bookmarks, open web tabs, and game information?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Neverfalter2015:
Swift backup is a great solution to this type of issue.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] davschm:
So does that mean the install will wipe all my apps and their settings, but using this i can restore it all after i flash Lineage 17.1?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Neverfalter2015:
Yes. The wipe userdata is going to completely factory reset your phone. Read everything in swift backup carefully as you go, but its a fairly easy app to use. it makes titanium backup look extremely complicated by comparison.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jimmyjambo:
Yeah swift backup works well asuming you are going to use Gapps with lineage otherwise it wont work, you have to sign into your google account for it to work unfortunately. Back up all your apps in swift including all the backup options like app data etc. When that's done copy the SwiftBackup folder from your phone to computer. Once you've got your new rom up and running copy the SwiftBackup folder back to your internal storage, then download swift backup and restore your apps, including all the extra options app like app data etc. like you did for the backup. All your apps should be as you left them.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
I have tried a lot of backup apps including Swift backup, but the backup APKs don't restore 100% of them don't know why. always there will be some random apps which will not restore and I will eventually need to download from the Play Store.

Since I have no limit on the data so always restore them over mobile internet.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] a_khusairi:
Im use Migrate GPE for backup and Restore apps+data+.. its working for this rom and another rom
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] twfs:
Anyone have system settings crash on the latest update?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] YoungFiire:
First, thank you for your work [MENTION=9116297]Eamo5[/MENTION].

I have a problem with installing gapps full on the latest lineage build, after installing lineage and rebooting to bootloader.

TWRP gives me error code 70 (Not enough storage), I tried factory reset and formating data but it still doesn't work.

The only option I found online so far was to resize system partition in TWRP, using advanced wipe but that won't work either.

It says that I have enough storage free on the system partition, could it be that it has to do with the lineage installion maybe ?

It would be awesome if you could help me here, or anyone else who knows what the problem could be. :)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
Simple answer and way out is -- use the micro or pico version. Full, stock etc needs bigger space that is not supported out of the box and you would need to do resize etc and fiddle with the cat.:)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Edmontonchef:
Use razorloves gapps
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Karim.:
I want to flash Lineage os I have stock android 11 beta now should I downgrade and do I will lose my personal data and Apps?

Thanks
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draekko:
FYI TWRP 3.4.0 is out, fixed my issue with password/pattern when entering recovery.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Edmontonchef:
Yeah, you'll have to format data to roll back.

I formatted data in twrp and then flashed lineage + twrp installer, reboot recovery then flashed gapps and it worked fine.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
Lineage OS 17.1 (08/07/20)

July ASB

Fixed kernel panics that can occur on the stock kernel

Added infinite caffeine ability in QS

Added LineageOS clock style

Various bug fixes and improvements
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Meowdib:
Can you share the link?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draekko:
https://twrp.me select for your device there
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] b00ster23:
I don't see 3.4.0 for either walleye or for taimen. Are you sure you didn't apply it to a different device? https://dl.twrp.me/taimen/
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draekko:
twrp-installer-3.4.0-1-taimen.zip	12.4M	2020-07-08 19:13:29 EDT

twrp-installer-3.4.0-0-taimen.zip	12.4M	2020-06-30 17:02:37 EDT

twrp-3.4.0-1-taimen.img	40M	2020-07-08 19:13:27 EDT

twrp-3.4.0-0-taimen.img	40M	2020-06-30 17:02:35 EDT

it's there https://dl.twrp.me/taimen/
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] b00ster23:
Gotcha...I didn't see it down on the list for taimen....although still not listed for walleye yet. LOL
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ViperPyro:
Darn, I'm holding out on updating Lineage for my walleye until twrp 3.4 comes out to avoid having to disable and reset all the fingerprint security settings. I guess by Aug pixel patch I'll bite the bullet..
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
If you sideload (adb sideload ROM.zip) your ROM updates, you dont need to dsiable anything and retain your security settings even after the flash. You would also be able to retain your Work Profile that way if you have one.

Top of it Lineage recovery supports only Sideload updates of ROM so your case is taken care of anyway .
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ViperPyro:
OH! Yes, you are right. That's awesome, thank you. I did not realize sideloading would get around the password/security issue of TWRP.

Just updated, no issues, using Lineage recovery too.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
Lineage OS 17.1 (24/07/20)

Fixed WiFi calling for various carriers

Corrected several proprietary blob signatures

Removed unneeded SSRestartDetector blob

Various bug fixes and improvements

Huge thanks to [MENTION=614507]razorloves[/MENTION] for fixing wifi calling on all pixels on aosp.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Bindle9:
Is your sha1 correct on the latest Taimen? I'm getting a difference on repeated downloads.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
Lol whoops, I accidentally put the md5sum there instead of sha1sum. Sorry I'll correct that now. Thanks for pointing that out
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Bindle9:
Thanks for the update!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
Lineage OS 17.1 (04/08/20)

August ASB

Expandable volume slider

Minor device tree improvements

Various bug fixes and improvements
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] user602:
Latest Gapps Mini and Walleye

I installed today's ROM update (4 August), and then tried to install the 4 August open gapps mini package, which failed with error code 70 (not enough storage).

If you have this problem, try an older open gapps mini package; I still had the 25 July package on my computer, and it worked perfectly despite being a slightly larger zip archive. :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Edmontonchef:
When in doubt use razorloves gapps
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ViperPyro:
I used latest Aug 4 Lineage and latest open gapps, no issues. Everyone says try the other gapps but I never ran into problems :shrug:

Love this ROM! Really bringing life back to the ole' pixel 2
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ViperPyro:
Is Pixel Call Screening supposed to work? Mine just sits on "Activating Call Screen (requires WiFi)" forever. I of course have toggled Wifi, uninstalled and reinstalled the Google Phone app, wiped Play data, restarted, removed all other dialers. Nothing helps. Using Verizon in US on walleye, if it matters.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
You need to install Google Dialer as a priv-app or else call screening won't work.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ViperPyro:
Ah, sneaky! Sorry for continued questions but how do you do that in Android 10 with system-as-root? Struggling to get anything into priv-app since it is locked, even once making it rw with su I'm still locked out. Titanium Backup convert to System App fails as well.

Thanks in advance, love Lineage :D
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
Please read below.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ViperPyro:
Hmm, so I followed that, it did move to priv-app without error. I restarted. Tried it, no luck. Noticed the normal app was still there as well (from TB). Removed it. Restarted. Cleared storage. Enabled all permissions.

https://xdaforums.com/apps/magisk/module-terminal-app-systemizer-ui-t3585851

But the Dialer is rather broken. It asks for Phone permission, I grant it, and it still asks for permission, but clicking it again does nothing. It just never continues. In the settings, the Call Screen is not visible as an option, only the other defaults like filter. I've restarted and cleared all data a few times.

Am I still doing it wrong?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] cubzfan68:
Just a thought, maybe clear cache/data on dialer and reboot??? Sorry, just re-read your post.... you did that.....
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ViperPyro:
Yep :-/

Just had someone call me and turns out I can't even answer calls. It vibrates as if ringing, but nothing to answer or end calls appears. Womp womp... Google Dialer is definitely broken.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] cubzfan68:
I had a similar problem once, I think I had to go into apps/dialer (Or what ever Los is calling it) and tell it that it was the phone app, I also installed google dialer frame work.....