[OFFICIAL] LineageOS 20 for the Google Pixel 2 XL

Search This thread

npjohnson

Recognized Developer
lineage-os-logo.png


Google Pixel 2 XL

Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:
This is the Official Lineage OS 20 thread for the Google Pixel 2 XL.

Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
  • taimen - Official builds​
  • taimen - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

Known Bugs:
  • None.​
  • Find any? Report them according to this guide.​
Notes:
  • The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.​
  • Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​
Kernel Source: https://github.com/LineageOS/android_kernel_google_wahoo
 
Last edited:

dimpoblimpo

Senior Member
Feb 9, 2013
118
38
Installed without issues coming from an android 12 rom. Sim card took a minute or two to register during initial startup but no problem afterwards. Everything seems to work no problem although Google pay does not work out of the box. Thank you for your work, Pixel 2 xl is alive and well
 
  • Like
Reactions: runekock

dimpoblimpo

Senior Member
Feb 9, 2013
118
38
Hello, what do you mean by this? Its not working by default?
Does it support OTA? and I couldn't find official download, only unofficial.

Thanks!
Correct, google pay tap does not work by default. I would imagine magisk and some modules are required to pass safety net or CTS checks(sorry I don't know much about this topic on android 13) Only unofficial for android 13 for lineage looks like. OTA I have no clue as I adb/fastboot clean everytime
 
  • Like
Reactions: aziz07

kiennguyen19323

New member
Mar 4, 2020
2
1
Since LOS doesn't allow reporting bugs on unofficial builds so I guess I can put it here.

Expected Behavior
Unlocking phone from either lock screen or screen-off state should working normal.

Current Behavior
SystemUI crashes after unlocking from lock screen if the previous unlock was done from screen-off state.

Possible Solution
Replace the default Pixel Launcher.

Steps to Reproduce
1. Lock the phone
2. Fingerprint unlock without wake the screen up
3. Lock the phone
4. Wake the screen
5. Unlock with either FP or passcode

device taimen
version lineage-20.0
date 2022-11-05
kernel 4.4.302-lineage-g441dbc7fd87e
baseband g8998-00034-2006052136
mods Google Apps/Pixel goodies included with the rom

The logcat is filtered from "com.android.systemui" and "com.google.android.nexuslauncher"
I suspect the animation of the wallpaper going from lock screen to home screen was causing the issue.
 

Attachments

  • logcat.txt
    398.7 KB · Views: 30
  • Like
Reactions: nitin.chobhe

npjohnson

Recognized Developer
Since LOS doesn't allow reporting bugs on unofficial builds so I guess I can put it here.

Expected Behavior
Unlocking phone from either lock screen or screen-off state should working normal.

Current Behavior
SystemUI crashes after unlocking from lock screen if the previous unlock was done from screen-off state.

Possible Solution
Replace the default Pixel Launcher.

Steps to Reproduce
1. Lock the phone
2. Fingerprint unlock without wake the screen up
3. Lock the phone
4. Wake the screen
5. Unlock with either FP or passcode

device taimen
version lineage-20.0
date 2022-11-05
kernel 4.4.302-lineage-g441dbc7fd87e
baseband g8998-00034-2006052136
mods Google Apps/Pixel goodies included with the rom

The logcat is filtered from "com.android.systemui" and "com.google.android.nexuslauncher"
I suspect the animation of the wallpaper going from lock screen to home screen was causing the issue.
Yeah I just hit this when I updated Pixel Launcher right before release - build with the fix is in testing right now.
 

ct85msi

Senior Member
Jan 7, 2011
69
26
Constanta
the updater forcecloses when I tried to update from 20221105 to 20221109 and from 20221109 to 20221110. I had to update with sideload.
 

Attachments

  • Screenshot_20221110-180207_Settings.png
    Screenshot_20221110-180207_Settings.png
    158.9 KB · Views: 110

ct85msi

Senior Member
Jan 7, 2011
69
26
Constanta
Thank you!
L.E. I think the new image should be renamed. It is named Lineage 19.1.

lineage-19.1-20221110-UNOFFICIAL-taimen.zip
lineage-20.0-20221109-recovery-taimen.img

L.E. 2 Also it boots with the message "Trust SELinux is not enforcing.." and it seems it doesn`t pass Safetynet tests.
 

Attachments

  • Screenshot_20221110-192418_SafetyNet Test.png
    Screenshot_20221110-192418_SafetyNet Test.png
    147 KB · Views: 195
  • Screenshot_20221110-192354_Pixel Launcher.png
    Screenshot_20221110-192354_Pixel Launcher.png
    120.9 KB · Views: 191
  • Screenshot_20221110-192403_LineageOS Settings.png
    Screenshot_20221110-192403_LineageOS Settings.png
    171.4 KB · Views: 189
Last edited:

dimpoblimpo

Senior Member
Feb 9, 2013
118
38
Thank you!
L.E. I think the new image should be renamed. It is named Lineage 19.1.

lineage-19.1-20221110-UNOFFICIAL-taimen.zip
lineage-20.0-20221109-recovery-taimen.img

L.E. 2 Also it boots with the message "Trust SELinux is not enforcing.." and it seems it doesn`t pass Safetynet tests.
I believe all android 13 ROMs are permissive unless someone can shine more light on this. Security is out the window if that's what your after on android 13. Go to arrow 12.1 if you want everything working for safetynet
 

npjohnson

Recognized Developer
I believe all android 13 ROMs are permissive unless someone can shine more light on this. Security is out the window if that's what your after on android 13. Go to arrow 12.1 if you want everything working for safetynet
it will be fixed in the next build, temporary.
 

northsail

Member
Sep 13, 2022
23
6
lineage-os-logo.png


Google Pixel 2 XL

Code:
- Your warranty is now void.
- You have been warned.
- Use at your own risk.

Introduction:
This is the Official Lineage OS 20 thread for the Google Pixel 2 XL.

Downloads:
Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
  • taimen - Coming Soon!​
  • taimen - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

Known Bugs:
  • None.​
  • Find any? Report them according to this guide.​
Notes:
  • The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.​
  • Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​
Kernel Source: https://github.com/LineageOS/android_kernel_google_wahoo
Great work again, i'll be wait for official with minor fixes.

Thanks for keep this mobile alive
 

mo0zh222

Member
Apr 23, 2022
11
2
Google Pixel 2 XL
Hey Dev!
Thank you for your continued support of Taimen as this phone still is a workhorse even in late 2022! I can not log into my snapchat as of the latest build, today is 11/17/22 , it says due to repeated attempts or unusual activity your access to snapchat is currently disabled. I reverted to the stock 11 rom and it worked fine! Yes I tried their troubleshooting and support to no avail. How fluently you have 13 working on here Google should still supported Taimen!!!!! Thank you I look forward to and anticipate future builds!!! I flashed back to your rom after testing logging in on 11. Also the SELinux not enforcing thing I am concerned about as well.
 

npjohnson

Recognized Developer
Hey Dev!
Thank you for your continued support of Taimen as this phone still is a workhorse even in late 2022! I can not log into my snapchat as of the latest build, today is 11/17/22 , it says due to repeated attempts or unusual activity your access to snapchat is currently disabled. I reverted to the stock 11 rom and it worked fine! Yes I tried their troubleshooting and support to no avail. How fluently you have 13 working on here Google should still supported Taimen!!!!! Thank you I look forward to and anticipate future builds!!! I flashed back to your rom after testing logging in on 11. Also the SELinux not enforcing thing I am concerned about as well.
SELinux is permissive due to a single bug I need to solve.

And snapchat is safety net related. Enforcing might fix it alone.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    The weekly LOS 20 updates now have three img files available to download along with the update itself. Where are any details/instructions concerning the use of these img files documented?
    Same as it was before, follow the wiki, those images are mainly for debugging issues if you have them, and maintainers may ask you to use them to debug things, but really just the exact same process you're used to following
    2
    Good to hear!
    I have 2 taimens, one really beat up taimen I bought from ebay really cheap just for testing and my daily driver I've had from new and have ran unofficial LOS 19/20. The whole RIL issue came up with Android 13 last year when everyone first installed, it took the devs a while to sort out, one of the steps to fix was to go back to stock and reinstall A13. On my test taimen I have had to go back few times to stock as i install/switch to multiple roms.. on my daily since being on unofficial 20 I have never had to do it again, even if I had to wipe and reinstall clean again, so sticking to one seems to avoid reverting to stock.

    I don't really know why it happens changing from A12 to A13, thats a question for a dev. Remember the age of the phone, its 5+ years old and not everything is open source, qualcomm drivers etc.
    The whole Verizone texting issue i think is a rom based issue, something is missing from the rom system causing that issue but that will soon be fixed also hopefully
    So to the Verizon texting thing - I use Verizon - It worked for me fine on AN12 as soon as I went to AN13 nope. I can recieve them, and send in groups (MMS) but not direct SMS. I know its not cool talking about other ROMS here, but I came here to as my plan was to try 20 fro my Taimen. I have used Pixel Exp 13 and 13 +, PixelDust, and even tried EVO X. All still cannot do it - the only difference I can see is my SMSC # is "+19037029920",145 - my Pixel6 Pro, on Verizon - same SIM - uses SMSC# +19037029920 and it sends all SMS texts fine. I was hoping I could root and change a build prop? Unsure, but if any dev can use this info to try to help AN13 with Verizon it be great!
    2
    So, you are saying that the only way to restore the RIL is by temporarily restoring the stock Google Android OS, then installing LOS 20? Too bad there isn’t a simpler way to do this. What other layers of the Android ecosystem have proprietary components requiring the temporary reinstallation of stock software to restore proper function
    Well, I followed your advice after first trying to install just the radio img file from the taimen factory image with fastboot. I hoped that might correct whatever the problem was with the RIL, but no such luck! So I had to do the full install of the factory image, which restored SIM detection as you said it would. I then installed the 0223 LOS 20 build and all appears to be well, my 2XL is currently running an app and data restore. I would like to know what might have caused this problem to occur in the first place so I can possibly prevent it from ever happening again!
    thanks for your guidance and support!
    2
    Hi sir On new builds data connectivity toggle on qs is slow also Bluetooth connection is slow and too hard to find devices please do something
    Neither of these are helpful bug reports.

    Please use the bug reports system detailed on the wiki if you have issued.
    2
    Yes, you need a USB 2.0 connection. I have had success with a 3.0 port and a 2.0 cable. As for the connectivity, I suggest flashing bone stock to it, and reflashing LOS to refresh the radios and all that good stuff that needs refreshed now and then for some reason.
    I'm sure you are right about first installing the stock image, but this should not be necessary. Initializing the hardware correctly is one of the basic things operating systems do, or should do (I'm an old -- very old -- OS developer) very soon after coming to life. Why do we need the stock image to do this for 20/13? This hack, even if it works, does not exactly inspire confidence. I am going to reflash 19.1 and wait until 20 settles down.

    Thanks very much for trying to help.
  • 20
    lineage-os-logo.png


    Google Pixel 2 XL

    Code:
    - Your warranty is now void.
    - You have been warned.
    - Use at your own risk.

    Introduction:
    This is the Official Lineage OS 20 thread for the Google Pixel 2 XL.

    Downloads:
    Please follow the install instructions in your device's Wiki page linked below exactly, and make sure your device's firmware matches the required firmware listed.
    • taimen - Official builds​
    • taimen - My unofficial with Google Apps/Pixel goodies included. Passes SafetyNet by default. OTA's roll roughly once a month. Support not guaranteed or implied.​
    If you don't follow these instructions, or use 3rd party add-ons (like Magisk) please don't expect support here.

    Known Bugs:
    • None.​
    • Find any? Report them according to this guide.​
    Notes:
    • The only supported GApps package at the moment is MindTheGapps, linked on our Wiki page about gapps.​
    • Firmware is shipped in the ROM package for this device, so no need to worry about updating it on your own!​
    Kernel Source: https://github.com/LineageOS/android_kernel_google_wahoo
    17
    Official builds will roll within a week!
    8
    Did anyone bother to try out every recent build and see which is the latest one that works without a bootloop?
    It seems that at least
    20230106
    20230109

    are not working.

    @npjohnson I understand that devs are extremely busy people, but how available are you for this project? If you do not have much spare time, could you at least make a working ROM (that is, without bootloops) before you take a break from this project? Much appreciated!
    work trip, I'll look into it when I get back. No clue what's going on.
    7
    Hey Dev!
    Thank you for your continued support of Taimen as this phone still is a workhorse even in late 2022! I can not log into my snapchat as of the latest build, today is 11/17/22 , it says due to repeated attempts or unusual activity your access to snapchat is currently disabled. I reverted to the stock 11 rom and it worked fine! Yes I tried their troubleshooting and support to no avail. How fluently you have 13 working on here Google should still supported Taimen!!!!! Thank you I look forward to and anticipate future builds!!! I flashed back to your rom after testing logging in on 11. Also the SELinux not enforcing thing I am concerned about as well.
    SELinux is permissive due to a single bug I need to solve.

    And snapchat is safety net related. Enforcing might fix it alone.
    4
    I believe all android 13 ROMs are permissive unless someone can shine more light on this. Security is out the window if that's what your after on android 13. Go to arrow 12.1 if you want everything working for safetynet
    it will be fixed in the next build, temporary.