yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] calvinistmac:
Works just fine for me on the latest build. Check your DND settings again and also check to see if you have the app(s) set to override DND. That would be the only way you're getting sounds while DND is turned on. There are also some apps that are coded badly and just don't obey the DND rules. i've had that happen with some messaging apps I've tried in the past.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Hyflex:
I've ran into several issues:

1. I can't turn the sound up/down or off for any media players (YouTube for example)

2. Google Photos crashes throwing up a "Reinstall photos - An error occurred during the installation of photos. Please uninstall the app and install it again." Of course I have tried this but it doesn't work.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ViperPyro:
I don't have any tips I can think of, but just chipping in that I haven't seen either issue in all my LOS updates. You installed the right GApps?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] calvinistmac:
Seems that a lot of the errors I've been seeing people report are random. This is most likely due to user error. Y'all need to make sure you follow the instructions for flashing to the letter. Flashing a ROM on a Pixel is not the same as flashing it on a non A/B device such as the OnePlus 3. If you follow the instructions on the Lineage OS site you'll run into no trouble.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] thomasck:
I had same errors, plus some others. That was due to wrong flash. Try to flash again, and follow [MENTION=9317193]73sydney[/MENTION] guide from post #386. Worked flawless here, not a single error since I've done that way.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Bigred1991:
I have an issue where only a few of my contacts names are showing up in the Android Messages application. It is strange, all my contacts are synced via my google account, but only some have names in messages and others show just the number. Has anyone else seen this? Also, it seems the phone just disconnects from cellular service from time to time. I know I have coverage, because I have used the same carrier where I live well before using LineageOS. Thanks for any help! I searched, but did not see the issue for the contacts.

EDIT: I should have clarified, I am using the stock kernel.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] cb474:
Purely from the point of view of security and given that there are no more security updates from Google, are their advantages to running Lineage 17.1 now over stock Android from Google?

It seems like there will be no more kernel updates for Lineage (right?), because they would have to be provided by Google. There will also be no more updates to proprietary firmware for the Qualcomm chipset and other hardware, regardless of whether one runs Lineage or sticks with the last version of Android from Google.

And then, Lineage is currently based on Android 10. But the final version of Android, for the Pixel 2, from Google is Android 11. Android 11 includes a lot more capacity for Google to update system elements through the Play Store, without a full system update. So with Google will there still be some updates for the Pixel 2 from the Play Store that way? Which Lineage would not get, because it's based on Android 10?

What do people think? For security on the Pixel 2 is Lineage 17.1 (based on Android 10) better or is the last version of Android 11 from Google better?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Sui77:
Good questions
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] friedsonjm:
For what its worth, running Lineage Official 16 on my Galaxy Tab S2, which updates weekly, it only says that platform security patches are up to date, but vendor updates are not. Clicking for the full explanation reveals that Lineage is incorporating the general Google security patches, but not those that are device hardware specific. It does not say what monthly patch is implemented.

I don't know how it will work on this Pixel 2 ROM.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Eamo5:
There are advantages and disadvantages coming from stock. The most clear advantage in terms of security, is that monthly android security bulletins are still merged for open source components to protect your device from CVEs. On the other hand unlocking your bootloader makes physical access to your device far less secure. What matters more is up to you.

I'll backport kernel ASB patches as they become available. There's no guidelines specifying the patches have to be from the OEM. However I do not intend on doing linux-stable merges so you'll miss some upstream patches there.

You're correct about proprietary Qualcomm components. For the foreseeable future we will use the latest blobs from the Android 10 August ASB.

The components that Google play system updates use are built with AOSP. Since the Lineage OS team continue to update older versions of Android to the latest security bulletin, these components should be updated when you take an OTA.

I hope this answers your questions.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] friedsonjm:
If I understand all that correctly, it means that as long as you maintain physical possession of your device, the further we get in time from the last factory update [December 2020] the better off we will be using the LinageOS ROM instead.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nandrew:
Hello! I am preparing to go from October stock to LOS so today I'm doing my research for Taimen.

Is anyone using the LOS recovery? I know the OP and the wiki say TWRP. It's just a question. I'm a minimalist and use it on my shamu just fine. LOS recovery is being built with every update.. just teasing to be flashed. Anyone owning a Galaxy Nexus know all about the crack flashing pandemic 10 years ago. Ha-ha!

As for either recovery:

Use "fastboot boot" for temporary use as the initial ROM install, (reboot bootloader) then reflash for gapps install?

And later after LOS is up and running use "fashboot flash boot" for sticking, allowing updates using the Lineage Updater in Settings?

Thanks!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I do not use LOS recovery nor do many, but some do, I also do not install TWRP, just ADB fastboot it when needed, nor the TWRP app.

fastboot boot twrp-3.4.0-0-taimen.img

Lay out your install steps you plan to use as from what you listed, it doesnt spound right but it may be a lost in translation issue. Lay them out so we can see, but the simple process I use without a single hiccup, is to ADB TWRP, wipe all partitions, reboot to BL, ADB TWRP, then install LOS, reboot to BL, ADB TWRP, then wipe them all over again, this time all errors are free since LOS installed all needed partitions (mainly the vendor), this is not required (second wipe after first install), but I like to see it cleanly, then once I wipe and format everything (plus /data after backing up everything), I then install LOS again (after pushing to SDCard from ADB the ROM/GAPPs), reboot to recovery and install NANO OpenGapps. I laid out the step by steps earlier in this forum as well as did others. I also install MAGISK through patching the boot.img which is also laid out earlier.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Eamo5, thank you for the October update!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nandrew:
Thank you for your response. I'll lay out some steps using the OP install guide, wiki and TWRP.me. In a nutshell, I'd like to compare TWRP to LOS recovery. Question: You must boot the recovery prior flashing the recovery? Method is by installing the recovery.zip within recovery? There is no LOS_recovery.zip to later flash both boot slots. So can we flash the recovery after the rom is installed to utilize the Updater App found on the devices settings? I think I'm lost on when you can flash a recovery vs. booting to the recovery.

Here are my steps. Let's assume the device's BL is already unlocked and connected to the host computer via a USB cable and USB debugging is enabled.

1. D/L on host computer: ROM.zip, LOS_recovery.img and nanogapps.zip (no LOS_recovery.zip).

2. Reboot to the BL: "adb reboot bootloader"

3. Delete the encrytion/userdata via fastboot "fastboot format userdata".

4. Temporarily boot into the recovery via "fastboot boot recovery.img".

5. Install the ROM within recovery. Sideload ROM.zip via: apply update> apply from ADB and on the host: "adb sideload ROM.zip".

6. Reboot to bootloader then fastboot recovery via "fastboot boot recovery.img".

7. (Optional) Install nanogapps within recovery. Sideload nanogapps.zip via: apply update> apply from ADB and on the host: "adb sideload nanogapps.zip".

8. Reboot system / recovery> reboot system now.

9. (Optional) Flash kernel/recovery/root/reboot system

Can the lineage updater app apply updates successfully at this point? That was more or less the goal of my posts. Booting into the recovery is different then flashing it? Is the the point where you could boot into the recovery and flash the TWRP.zip (if previously using TWRP.img)? If the ROM is installed and running can I flash the LOS_recovery.img to my boot? "fastboot flash boot recovery.img"?? Or is nobody flashing recovery anymore and only booting to it??
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nandrew:
Thank you! This is all helpful to me and will be to many other people now that the Pixel 2 and Pixel 2 XL have met the EOL by Google. LOS has always been my go-to ROM!

The only thing left unanswered is the "fastboot boot recovery.img" vs. "fasboot flash boot recovery.img".

My assumption here is that the latter “flashing” is unnecessary for the OTA updater to work. I can live with that. The wiki says you can do either, the OP and you say to boot (not flash boot), so I just wanted clarification.

Thanks!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] cb474:
Hi. Thanks super much for the detailed response to my question.

I've already unlocked my bootloader and rooted my phone with stock Android, so I won't be taking any extra risks at that level, if I switch to Lineage.

When you say that with Lineage, "monthly android security bulletins are still merged for open source components to protect your device from CVEs," are those the same updates that would come through Google Play in Android 11? I'm a little unclear still if there are certain updates I would get with Lineage, in this regard, that I would not get wit the final stock version of Android 11 and Google Play for the Pixel 2. It seems like at first you way that there is a security advantage with Lineage, because it provides the monthly android security bulletins. But then it seems like you say those bulletins come anyway through Google Play on Android 11. Just trying to make sure I'm understanding correctly.

Also, it sounds like with Lineage I would get some kernel patches that I won't get anymore with stock (since it's not being updated anymore on the Pixel 2), but I won't get all the kernel updates that are out there upstream. Is that correct?

Thank you for any further clarification.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Boots TWRP, installs TWRP, you only need to boot TWRP. I do not install TWRP, for me, there's simply no need. If you install TWRP it also may be overwritten with an OTA and stock LOS recovery. I can't remember if LOS bundles the recovery to the ROM install or not (since I do not install TWRP nor boot LOS recovery). I'd have to check but I believe it does.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nandrew:
Thanks again! You are correct -LOS bundles. Got up and running a few minutes ago. You have to boot to TWRP. Trying to boot to LOS recovery just restarts the phone.

Now I can answer some of my own questions.: You cannot boot to LOS recovery. Maybe you can flash it, but you don't need to. The ROM installs LOS recovery. So when you use the updater app or the reboot to recovery option, it goes to recovery. BOOM.

Now back to setting up all these apps... :silly:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] 73sydney:
MagiskHide Props Config is a far easier (and reversible (if need be) and updateable) way to deal with SafetyNet going forwards than remounting system and creating scripts, especially if youre flashing ROM's often. People forget theyve used scripts etc quite often. MHPC is far more visible, as its a listed Magisk module
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nandrew:
FWIW, Google fi users need to use a physical fi Sim card in conjunction with flashing the additional google fi zip (OP) to utilize network switching between Sprint, T-Mobile and US Cellular. If you try to use your eSim and the zip, you will only have access to the T-Mobile network.

Luckily I still had an old sim card from my Nexus 6P! Picture me in my attic rummaging through boxes with a flashlight in my mouth. Lol!

Feels great to be back on LOS!

Thanks!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Javellinh:
Hi guys, i want to say thanks for this smooth LOS for my 2 XL. I have using it for week, maybe a little bit more, and everything works fine. But i have faced some strange behaviour there.

I usually have telegram and Twitter ran in background (i just swipe up to home, dont close the apps) and if i open any other app - both of background apps got closed (i mean when you choose it from recents - app refreshes). It is strange because i have more than 1 gb ram and 1.5 gb zram free (i am not so experienced in this but i thought that low memory killer only close apps when android have not free ram).

Do you guys have any thoughts how can i prevent apps from force closing? Is it only me or it is OK behaviour? Thanks in advance!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] merkyone:
Try developer options where you can choose how many apps are allowed to run in the background... I believe lineage limits those, but I could be wrong :confused:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Javellinh:
I found that "Background process limit" in dev options (maybe it called slightly different because i am not english speaker) but it has very strict values: default, 0, 1, 2, 3 and 4 background processes max. There is no "disable limit" or something like that :rolleyes:

Is it possible that sultan kernel cause this problems for me? I have LOS, magisk, twrp and sultan kernel installed right now
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] merkyone:
I'm not sure... Maybe there's another similar setting in lineage?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
True but I prefer not to use any modules, especially magisk modules to do the same thing a simple script will do. Set the script once and it retains through OTAs so that's my go to method. This is also 100% reversible by removing the single line of code. The main reason I use it is because I like to have full visibility into the options I use and know what I'm changing than use a module I didn't write thus can't really support. The script just works so there's no 1 right way to do it. I just prefer to know what's going on than rely on someone else's module I can't support. I also highly rely on the KIS (Keep It Simple) method and try to do that simplest changes to my system. To me, it's a lot simpler to RW /system and drop 1 line of code then to mess around with modules. I've had bad luck with modules in the past so keep that in mind.

No, I'm not starting an argument or trying to aggravate you but simply explain why I only support or recommend using the scripted approach so don't take it incorrectly and we have another round of arguing.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] gogol:
Is it necessary to also run "fastboot unlock critical"?

My 2XL is still locked.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Lughnasadh:
If your bootloader version is prior to TMZ20a, then you may need to use the "fastboot flashing unlock_critical" command as well. If it's a later version, then just using the "fastboot flashing unlock" command should work to unlock the bootloader.

Make sure your Platform Tools are up-to-date before proceeding... https://developer.android.com/studio/releases/platform-tools
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draekko:
FYI for those wanting to try long exposure photography

Magisk long exposure modules

https://xdaforums.com/showpost.php?p=81444109&postcount=2307

GCAM Mod with Astral photography mode for P2 XL.

https://xdaforums.com/pixel-2-xl/themes/google-camera-camera-mwp-v2-5-mod-t4076579

The magisk module also works awesome with Camera FV-5, I tested it with a noname brand ND-10 filter in front of the lens.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] gogol:
I just checked via fastboot and I saw this:

BOOTLOADER VERSION - TMZ30m

Is that prior? I am not familiar with the numbering.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
No issues with your bootloader version
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] gogol:
Yes, I have no issue with the bootloader, but that's not my question.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I believe what that user is saying is that you should be good with commands with the firmware you have. Make sure OEM unlocking is checked in dev options or nothing will work (assuming this is a Google device), then backup everything as it will wipe once unlocked. Once backed up, reboot to BL and run these two adb commands below (make sure adb is that most current). If it fails to run the command, then most likely you don't need it (it will tell you). I know this because I ran both when I unlocked mine and only one was needed.

fastboot flashing unlock

fastboot flashing unlock_critical

Let us know afterwards what the status is.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nandrew:
I came from this same bootloader version. I did NOT have to unlock critical.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] andrea.ippo:
Google Camera?

Hi everyone,

since our beloved P2XL is nearing EOL, I'm considering, like many, the option of switching over to LOS.

My only concerns are about:

- bug/glitches/overall stability and battery life (vs the Google ROM)

- camera -> can I use the official Google Camera? Can I download and update it via Play Store, and are the results the same as on the Google ROM, or is there some proprietary magic by Google happening in the ROM itself, which I would lose by switching over to LOS? Camera is the #1 reason why I bought this phone in the first place, so I couldn't accept any compromises in this department.

Thanks a lot in advance!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Lughnasadh:
No, that's after so you shouldn't need to use the critical unlock method, just the regular method.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] gogol:
Thank you, I will proceed without unlock critical.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Same, and neither did I but I still ran it just the same. It errors out and doesnt do anything if/when not needed, and unlocks when needed so I always tell users to try it. This is only useful if OEM unlock is checked in dev options so I hope the user in question made sure before trying.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
LOS17. 1 is one of the most stable A10 ROM and although it comes with AOSP camera, you can always install the Google camera and use it to it's full potential. There's no gimmicky stuff so photos come out same as stock. Battery personally is better for me. Stock gives me 6hr SOT but LOS gives 7.

Only thing to lose is active edge of you use it at all.

Until December ROMs come out I'll be in here in this ROM only.

Best of luck
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] andrea.ippo:
Thanks!

And what about AOSP/LOS default apps, can I choose which ones I want installed? I'd like to keep quite some Google apps, so I'm looking for a way to disable those that come with the ROM which I'm not interested in (e.g. browser, mail, calendar, camera...).

Or I guess I could just disable them?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
Install the open gapps and disable the aosp ones. Make sure to select the default phone app to Google phone else you'll be getting ringtone but no call UI as u disabled the aosp dialer.

Bitgapps perhaps replaces some of the aosp but I faced some other Google framework issues so I avoid it and use only OG micro.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] andrea.ippo:
Oh right, indeed there's that config file in gapps that allows you to do that. Lol I forgot, so much time since I've last flashed stuff on my OP3 :laugh:

Thanks for the tip!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] holmes6:
Just installed and it was nice and easy and seems to perform well. Only issue I had was android setup kept popping up and would crash if I selected to skip data transfer and also crash if I try to transfer data so it's stuck. I just disabled the app which works for me. Not sure if anyone else had that problem.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] friedsonjm:
Google Pay?

Does anyone have Google Pay working on this ROM, and if you needed to do something 'special' to make it work, what did you do?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draekko:
[MENTION=9116297]Eamo5[/MENTION]

FYI you can get 2560x1440 and 3264x1836 (front and back camera) by hex editing libmmcamera2_mct.so. (i needed QHD and something close to 4K for recording video on the front camera in 16:9 format)

hex strings 3200x2400 to 3264x1836 (replace the two instances):

800c00006009 to c00c00002c07

hex strings 2688x1512 to 2560x1400 (replace single instance):

800a0000e805 to 000a0000a005

Enjoy.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] andrea.ippo:
I've read something about this and had the same issue on a different device, you might need to flash a smaller gapps package or making sure that you're flashing gapps right after the system image. I literally queued both zips in twrp, so that they were both flashed in one go.

This was a Redmi 4A a few days ago, haven't tried flashing LOS on my main taimen yet, but I think the cause for your issue is the same.

Edit: sorry, it's unrelated to the gapps packages you choose, but it is related to when you flash gapps. FAQ#10 on the gapps website
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
Google Pay is working fine in this ROM. In case it doesn't work in any of the monthly updates then just just use hideprops in magisk.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nandrew:
That's a good point. Wouldn't the standard unlock fail (or critical for that matter) if the OEM unlock is not checked in Dev options? I think fasboot would return an error message just the same. I've never tried.

I would always suggest people refer to Google's very own flashing instructions when unlocking for the first time. It has probably the most up to date info for your device all lists all the requirements in good detail.

https://developers.google.com/android/images
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nandrew:
I'm running LOS stock with micro gapps. How did you get pay to work? I get the software isn't supported error. Magisk must be required.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Did you enable MAGISK hide? Or rather, lay out your install steps and process so we can figure out what has been done, what hasnt been done, and what may be lacking.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Nandrew:
No magisk. Just clarifying that you need that to have Google pay work.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] draekko:
I've modded the Magisk module to add the resolutions 2560x1440 and 3264x1836.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Yes as far as I'm aware, you need magisk to get gpay working on custom ROMs. I'm not a gpay user so take what I say with a grain of salt.