yashsingh1/xdaforums huggingface dataset:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sharanoth:
it's being worked on
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sohail_23:
pixel 2 xl not mentioned in the web installer which device should i choose for clean installation?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
Proton no longer supports the P2XL, so the answer is...none.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jam456:
its still available but you will have to manual install the rom to the phone, as its no longer being updated. I was hoping maybe another dev can adopt this rom and keep it going as this and pixel dust roms are the most stable and smoothest.. sticking to pixeldust 11 until 12 reaches the same standard.

v11.6.0 · ProtonAOSP

Released to patrons on August 7, 2021 and publicly on August 24.

protonaosp.kdrag0n.dev
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sharanoth:
well im doing that, only for android 12 protonAOSP instead
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] jam456:
I appreciate all the work you put in, all the pixel2xl users do, honestly.

the 2xl is my personal phone and daily driver, the rom has to be stable and be able to pass the banking checks so I will be moving to android 12 in a month or 2 once that has been worked out.

i use a iphone x for work and know apple still update the older 6s. what i dont understand is why google cant do the same with the phones it has released, they seriously overlooked that and it will cost them in terms of people buying the phones. google could have set themselves apart with the pixels from the other android phones with that one move... anyway thanks for the reply, sorry about the rant about google lol
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ViperX85:
What kind of bull**** is this? Why is this ROM posted here if P2XL is not supported?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sharanoth:
are you an idiot?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ViperX85:
I guess you are.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] sharanoth:
No seriously. This thread has been here for over a year. Pixel 2 XL has just been removed off the supported list of devices. You want the thread to spontaneously disappear? 🤣

If you want a continuation to protonAOSP, check the latest xda thread. Dont be a moron.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] adkamble89:
hi proton team,

i just flashed proton rom but calling not working.

after dialing any number it just call ends ........ thanks
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Speedy556:
Very good rom, with many features, but i have one problem, vibration, is too strong, how can i make it normal without apps like BuzzKill? i dont find vibration strenght in settings, i find only option to turn it off or on
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Walterkom:
sim manager keeps stopping

version protonAosp 11.6.0

version with gapps no problems but last version 11.6. cant be flash in device-flasher[fastboot error], so locking bootloader is not possible. so i manual flash all files version 11.6 with gapps. and in persmission manager i have body sensors 200 alowed :D:D
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I warned of this on post 16 not to patch boot.img or looping. Its better to use the official MAGISK now than canary because the loop issues are resolved in the latest version, this is how I did it and it works every time I tested this for users. I would also caution on not sharing patched boot.img's as unsuspecting or newbs may take this as a step needed or not do it right, or worse, use it for the wrong ROM and/or the wrong version causing worse issues. Instead flash the latest MAGISK through TWRP, I have found right now its safer than patching boot.img for proton. Normally I am all on board with you and always recommended to patch boot.img, but not for proton. Use TWRP and zip instead, its far more stable and has a better chance at success, but do whatever you feel is best, just a head's up pre-warning.

Just a word of caution for others, be careful with doing this, or if you do choose to do it, make your own boot.img, not someone else's you cannot verify the version of kernel, integrity, and ROM compatibility as all boot.img's are not the same across ROMs.

And please do NOT take anything I said out of anything other then guidance for others reading it. I'm not attacking nor putting down your attempt to help, your post is exactly what we need in XDA. Helping others, my only concern was newbs reading and taking it without any advice or guidance then run into data-loss.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] RandomPRSN:
Is Google photos affected in anyway way with this ROM?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
Currently it's using the Drive storage. Think the fix will be coming in next update.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] KiranGadge911:
Actually I wasn't able to find success rooting using the magisk manager 8.0.2. That's why had to use canary. You are right, there has to be a guideline for newbs not to use the boot.img with another ROM. I'll go ahead and edit the post. Thanks for the advice
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
All good, I am glad you understood and listened. Usually it's the opposite and arguments ensue.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ironLink21:
Boot image

What's up guys! So I'm just getting back into the rooting scene because google is no longer supporting the P2xl and I don't want to fork out a bunch of money for a new phone when my current one is working perfectly fine still.

Reading through this thread I've got a couple of questions. I'm wanting to install magisk because there are a couple of apps that still won't run because they "detected that I'm rooted" even though I'm passing safetyNet. Previously I would just flash TWRP and then flash magisk from recovery but will that break safetyNet now how it's currently implemented?

It also seems liked patching the boot image route is a lot easier and less involved and less to break safetyNet?

With that said where does the boot.img for this ROM reside previously the boot.img would just be included in the ROM zip but in the case of Proton I'm not seeing the boot.img in the zip.

After reading through the thread are we just using the stock boot.img to boot this ROM? If not then how/where can I get this ROM's boot.img from the Proton source code?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] MartinN6:
root / SaftyNet

I honestly don't understand why some people have such problems with the root and SaftyNet.

My way is very simple:

- boot into the booloader

- fastboot boot twrp.img

- flash Magisk 21.1 (latest beta)

- reboot to system and activate Magisk hide in the settings

SaftyNet passes without any problems

And by the way ... BIG thanks to kdrag0n for this excellent ROM!!!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] veedubrocks:
So what is the TWRP file your using? Thought it wasn't available for Pixel 5. Thanks

---------- Post added at 11:12 AM ---------- Previous post was at 11:09 AM ----------

It's inside the zip. The image zip file inside the proton zip file. Hope I'm explaining correctly...lol

Unzip proton file then unzip image file inside that. Boot image is in there
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
This is the pixel 2 XL forum, TWRP is very much alive for this device but I am unsure why you are looking for a pixel 5 TWRP. DL the latest official TWRP for taimen and you will be fine.

---------- Post added at 02:31 PM ---------- Previous post was at 02:21 PM ----------

Its a little bit more than just unzip, you need python plus the payload script to extract the payload.bin. In there is the boot.img and all other images needed for the ROM to install. For MAGISK, all you need is boot.img and to patch it in MAGISK app, then ADB boot.img (patched image) to the boot partition.

Python 38 works well:

payload_dumper.py payload.bin --> script code for payload export (Google payload_dumper.pl)

fastboot flash boot magisk_patched.img --> ADB boot sector with the MAGISK patched image
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] veedubrocks:
Super sorry for the confusion. I have both thread and didn't see it was 2xl I was posting in. Disregard all my comments....lol.

Cheers
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] ironLink21:
First, thank you very much for your reply! Also thank you very much kdrag0n for this amazing ROM! I know that it takes a ton of work to get these projects done so thank you very much!

ahhhh ok awesome. When I didn't see the boot.img in the .zip file I knew that there had to be something else that I needed to do to extract the boot.img.

Let me do some poking around for that payload_dumper.py and see if I can get that image extracted :)

Thank you again!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
All good! NP, I was just like, hmm, not sure where this user is going but something didnt add up :)
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Maverick Jester:
[MENTION=7291478]kdrag0n[/MENTION] I've long awaited a Proton kernel/ROM for the 2 XL. Your work is always exceptional.

I have a feature request- would it be possible to implement the Pixel 5's elevated haptic feedback settings options? The 2 XL has a notably better motor, but no way to adjust the strength, which I would love to be able to tune better.

Alternatively, is it possible to use the Pixel 4's haptic variables? The motors appear to be a similar type (linear resonant actuator) but the tuning seems to be far better on the 4/XL.

EDIT: if these options already exist, I apologise. I haven't yet had the chance to flash the ROM, but will be doing so soon.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
[MENTION=7291478]kdrag0n[/MENTION] This is perfect. All I wanted was a simple ROM with Active Edge, which LineageOS refuses to employ despite the tech being reverse-engineered. But, is there a reason for using test keys to sign the ROM? Without sounding too alarmist, from what I recall using test keys in a release ROM isn't a good idea.

EDIT: One additional thing. Regarding the GApps build, would it be possible to include a script that would go through and either disable, or ideally, delete the AOSP versions of common apps (e.g. Contacts, Calculator, Camera, Clock, keyboard, Phone)?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] kdrag0n:
The Pixel 2 XL's vibration motor is worse and produces less sharp vibrations than the 5, not better. I have both devices and the 5's vibrations are noticeably sharper and "cleaner" than the 2 XL.

All modern Pixels have LRA motors, but the vibration driver ICs differ. The Pixel 3/XL and 4/XL have a better driver IC from Cirrus Logic, while the Pixel 2/XL, 3a/XL, 4a/5G, and 5 have a lower-end one from TI. That's why the Pixel 5's vibration is actually slightly worse than the 4.

LineageOS 18 will support Active Edge using the new reverse-engineered implementation that I built for ProtonAOSP. My implementation is the first reverse-engineered one; the previous solutions were dumping decompiled code from stock into the system, which comes with legal, compatibility, and stability issues.

The use of test-keys is not ideal, but I do not have infrastructure to support secure key management and distribution across the multiple (sometimes ephemeral) machines I use for ROM builds at the moment. I would rather keep the early days of the ROM simple, and focusing on this kind of security is not a high priority. Proper signing keys with AVB support may be used in the future, but not now.

The gapps build is designed to include as few gapps as possible for full functionality, so there are no plans to remove AOSP/LineageOS apps.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
[MENTION=7291478]kdrag0n[/MENTION]: Clearly I misunderstood the situation with other ROMs and their active edge code. Thank you for the education. The keys thing...I understand your point of view. The script? That's simply me wanting to be lazy, or else it's my OCD talking. :good:
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Maverick Jester:
Thanks for this. I assumed that Google were also using the Cirrus Logic IC for the 2 XL, but TIL. Appreciate it.

I've flashed the ROM, and it is indeed superb. Thank you for the hard work on this!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] tripLr:
Active edge should just be another type of touch sensor , not a code, and works in other roms as whatever service you want like, camera or screenshot
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] cubzfan68:
Magisk Canary

Not sure if I'm missing something obvious but, Is there a way to flash modules on Canary? I'm trying to flash A11 which I'm guessing only Magisk 21 will work but can't flash modules..... I did search this thread before asking and found nothing, any help would be appreciated......
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] 73sydney:
You click the puzzle piece in the icon bar at bottom of magisk manager, then install from the repo, or install locally from sdcard (which is what i do about half a dozen times a week, on a bad week)

Works the same it always has in the new interface, im on canary, no issues

Just a reminder, this is a ROM dev thread, and if youre still having issues, youre better heading over to the magisk support thread
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
You would think so, but being able to translate this sensor's input into a meaningful form, e.g. calling up the Google Assistant, requires coding. The LineageOS maintainer for the P2XL refused to add Active Edge because the code everyone else was using was from Google and was NOT part of the AOSP. The version here in this ROM doesn't have that issue according to the developer.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] cubzfan68:
Thx for that, got it figured out, Rom is really good, I'm running MicroG so I don't have the Gapps issues some people were posting about.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] smorgar:
Maybe a really stupid question, but here I go:

When in stock ROM I can't use dual SIM (one physical SIM and one e-SIM) because of some limitation in the software I believe. I can only use physical SIM + google fi as an e-SIM. Is it possible to use physical SIM + regular e-SIM with a custom ROM and if so; does it work on this ROM?
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Green-Bot:
Updated most default apps from LineageOS

This is a line from dev' GitHub page. I assume, these are the default apps from LOS. Is there a way if we can remove these LOS default apps and replace with P2XL's default apps from play store? My aim is to keep it real close to stock while installing the monthly security patches(thanks to the dev).

Also, is there a simple step-by-step process to get this ROM running for first time without any issues? It's been many years since I tried installing any custom ROM after my Samsung Galaxy Note 1(GT-N7000), android 3/4 days.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
I already brought up the idea of being able to remove the LineageOS apps. The developer won't be doing that, and I understand his reasons.

As for a step-by-step, follow the dev's instructions. I had no issues installing this using them.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Green-Bot:
Is using OpenGapps an option? Maybe we can use their micro/super/aroma packages instead of this rom's gapps package? Just curious.....thank you.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
As long as you choose the non-GAPP'd version, sure is:

Downloads

Downloads and changelogs can be found on GitHub. The topmost release is the latest. Builds with and without gapps included are provided for convenience.

proton-aosp_taimen_11.2.0-gapps.zip

proton-aosp_taimen_11.2.0.zip --> CHOOSE THIS ONE
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] 73sydney:
Youre far better off using NikGapps - the Open G-Apps folks are slow to build major releases, and their test version for Android 11 (R) is nearly a month old

Downloads - NikGapps

NikGapps Website

nikgapps.com

Faq here:

FAQs - NikGapps

NikGapps Website

nikgapps.com

I use a config file (explained in faq) with the full package to cherry pick what i install (just as i did with Open G-apps Aroma)

Note: you can use a debloater.config to remove apps, i personally just use this Magisk Module to do the job, far safer, and reversible
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Green-Bot:
My criterion is to use the stable framework and based on my requirements & past experiences, I will stick to using OGapps. Looks like I will need to do some research about the customisation part though:) Thank you!!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] Strephon Alkhalikoi:
Customization of an OpenGApps package isn't difficult. Their wiki goes into more details, but stored in the same location as the package you also have a text file named "gapps-config" that will either forceably install or ignore specific GApps.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] palimatix:
wow... the power of n flexibility of nikgapps.config is really awesome. I tried it after your post wtih this ROM and configured it exactly to my liking and must say am impressed. its working fine with this ROM. I hope the dev continues with the gapless builds for upcoming releases.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
All the bickering with users aside, I do like proton, its my 11 "go to" ROM. I use LOS for 10, and proton for 11 but find proton to be unbelievably stable. I have no issues or bugs, my only weirdness is my LED notification still doesnt seem to light up right but I am working on it.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] theimpulson:
Hey guys! I have removed some posts from this thread which seemed to me causing misunderstanding and initiating fights that we don't want on XDA. Please remember that it's always possible that what you are writing might be misunderstood by someone else. Tolerance is a two-way street. Let's not get into petty fights over projects which we love.

Regards,

theimpulson
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] deepakdavidster@gmail.com:
Using the latest ROM in Pixel 2 XL seems like it is stable as stock ROM and battery seems to be better than stock I am getting close to 8hr SOT
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Rock on, I only try to give the easiest and sure-fire methods, but I dont always come off that way. OG is the only GAPPs framework I use so thats why I recommend it because then I can reproduce the issues, otherwise its a guessing game. Guessing games land us nowhere, so I do try to keep the user I am helping as lined up with me as possible.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Yup easy peasy and why I try to get the majority of users I help on board with OG so I can reproduce the issue and assist. I personally, have NEVER had a single hiccup or issue with OpenGapps, and I have no affiliation with them, they just work solid.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Can someone (anyone on Proton - this ROM), test if LED notifications fire for you and stay on until cleared (staying on is more of this question), I know the LED fires once quickly but doesn’t stay on for me. OR is it just me and I am nuts? I use edge lighting for my notifications so I didn’t really notice the LED (except for my original post) a few days ago. Now I have tested it for a few days and it is not working right for me (at least how I would normally expect it to work), for example, charging LED doesn’t come on. Its OK for the time being because of edge lighting but ideally I would like to fix this myself. I just need to know its an actual issue and not something obvious I am overlooking. Charging would be really what I am interested in hearing from others, does the LED light when plugged in?

Thanks in advance!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] MarkAnthony121:
Guys I'm really sorry. It's been a long time since I've rooted and installed a ROM but the Pixel 2XL finally stopped getting updates. I'm also trying to squeeze the last bit of battery life and performance for 10 more months before I buy the next phone. Is this a viable option? I know the risks, some apps not working, bugs, etc. But is there a noticeable difference coming from stock in terms of battery life and or performance if I don't plan on tweaking anything further than installing a ROM (no overclock/underclocking/tuning or things like that because that's out of my skillset).
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] tripLr:
1. U need to unlock bootloader in developer options.

2. Realize you cannot install twrp yet on October or newer stock roms.

3. Realize that No rom will be as stable as the last 10 stock rom so far. Except a couple "official" roms.

If you wish to install rom, and root, you must do it by side loading rather than twrp installed recovery.

Process:

Download twrp to computer from twrp.

Install adb and fastboot to computer

After latest factory install 10 or 11 from Google

Download rom to phone , download magisk canary and magisk manager to phone.

Unlock phone ( remove password , screen lock etc. Use swipe or none )

Enable developer mode Make Sure Unlock Bootloader is checked !!

Pair adb with adb devices command and usb

adb reboot bootloader

Reboot to bootloader " fastboot "

fastboot boot twrp.img for pixel2xl

Once there, flash rom. Flash gapps if not included, flash magisk, reboot and reboot.

Enjoy..

Ps first post with new xd
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] 73sydney:
Battery life/performance depends more on the ROM than the kernel these days. Post Android 7 the stock kernel is pretty damn efficient. Theres no harm in rooting and just installing a custom ROM to get security updates that will stop/have stopped on stock 11. You do not need to worry about going to the extremes of installing custom kernels and tweaking them, the gains are negligible if not entirely in the eye of the user.

As always you can extend battery life by turning off obvious things like AOD (always on display) and known functions that are known to affect battery life.

Android 10 still gives me better battery life than Android 11 in these early stages on Android 11 development, in the case of BlissROM its quite a bit more battery, but its EOL and not having any further security updates added. Theres also been noted battery issues for some folks in Android 11, which has been accepted as a bug report by Google and being worked on. Some ROM's are affected by this more than others depending on the way theyre developed and which repos the dev uses. Proton is pretty damn good. But you do also have the more mainstream projects like LineageOS which are probably arguably way more developed, and which often serve as the base for most other custom ROM's.
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] MarkAnthony121:
I totally get that and appreciate the post. I was more asking if the performance boost is decent or worth it for someone in my position. But this does help too!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] MarkAnthony121:
Ok thanks, this is precisely for the information I was looking for. It seems I'll just have to decide myself if it's worth the effort. It's definitely possible that I might as well just leave it as is, but again I'll have to asses that on my own. Thanks!
[Google Pixel 2 XL ROMs, Kernels, Recoveries, & Oth] cubzfan68:
My notification light works till cleared, blinks slow though, no charge light. I use an app called "led blinker pro" works really well on our phones. Hey, I had a question I wanted to ask you and you said you don't check p.m.'s

can you respond to this thread? I'm having a notification issue I can't figure out and so far no one can help......