yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] heocon77:
I installed the rom ok but I installed a kernel and it recognized the device as pixel 5, how do I change the device to a pixel 4xl, thanks for supporting
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] jubeilecu:
Installed and working.

One question, would be possible to next build include a disabled power button feature on lock screen ?? I mean when the screen is locked you couldn't reboot or power off the device unless you password it.

I saw this feature in others ROM and think it's a great solution in case of lost or stolen.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
This is by design. We spoof the Pixel 5 ID to pass safetynet.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
I've found little things here and there for bugs, that's either on my end or due to something I caused myself, but that Pixel 5 thing threw me off, lol.

Even when I reflashed back to stock, my PC still thought I had a Pixel 5 till I uninstalled the USB driver. Also got that " Welcome to your new Pixel 5! " email from Google.

But, there's a Magisk Module that passes Safetynet without having to spoof, I think that's a better option since spoofing the device causes other apps to not work correctly. Biometrics is disabled for me due to the fact that the Pixel 5 doesn't have Face ID. 🤔

Edit: Spoofing back to a Pixel 4 XL fixed the biometrics issue with LastPass for me, and still passing safetynet, guessing due to it thinking it's a Pixel 5 by default anyways.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] king_david43:
Does NGA display properly on this build?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
The dev is aware of the magisk module to pass safetynet (safetynet-fix-v1.1.1.zip). I won't speak for him but it was done on purpose to pass safetynet out of box without the need for any modules. Users are free to do whatever they want (changing model fingerprints for example) but just keep in mind that doing so changes the ROM from the intended design. You may run into other issues that no one can reproduce. When we can't reproduce an issue, it makes it difficult to help or pinpoint the issue. It also makes it more difficult to know if its a true bug or user modification issue (example would be changing the fingerprint to something different than intended).

Just something to keep in mind when reporting bugs or issues. Try to remember what's been changed from the base (core ROM) after installation and report it along with the bug/issue.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
Everything's stable as can be, just a couple kinks here and there within settings without messing with anything, nothing serious.

And yeah, I read about it being intended, but it broke biometrics with some apps. Some still worked perfectly fine without spoofing back to a Coral though.

You don't get the colorful Google colors at the bottom, but it's the same UI.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
New build with Feb patch was pushed.

As many requested I changed the fingerprint to original Pixel 4 XL and it still passes safetynet. Also live volume steps were added as per request. You can find the changelog in the second post.

Have fun! Dirty flashing may work, I havent tested.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Rock on! THANK YOU for the volume steps, that's all I was missing!!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I am pretty sure it's the play store updating to the latest version, I had to roll back to March then allow play to update but I haven't upgraded the April ROM build yet. It's within the play store update causing the issue but I don't know why yet. All apps originally opened until the store updated, then all apps went to crap along with the store FC. I even removed the play framework update, cleared data and cache, nothing solved it so I rolled back.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
I recompiled with the latest blobs and stuff and flashed it on my coral. Zero issues.

I pushed a new build.

If you have any problems atleast try a clean flash after flashing stock before. That worked flawless for me.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] phuphat1986:
Thanks sir
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
deleted
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
did you dirty flash or do a totally clean one?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
any luck tracking down the issue?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
I did a clean flash to be safe.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
I just dirty flashed and all seems to be well... Thanks for another great build. Cheers.

Just one more thing... Do you have any idea what's causing Smart Charging to not work?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Not yet, but I also haven't had time to review anything. I work on average 12 hour days, usually more so I only do this with XDA to take the load of support off the devs. I do this because back in the cyanogen days, I used to release my own ROMs but supporting them became impossible so I moved to helping instead. I figured out why it was working then not working, I also had a 3rd party root charging app running so it seemed like it was working (smart charging), but it was really my root app.

This one works fine for me, and you can use it until it's fixed in the ROM:

Battery Charge Limit [ROOT] - Apps on Google Play

Stop charging at desired level to preserve battery health for most devices!

play.app.goo.gl
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
The app isn't working for me either :-(
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Really? Thats definitely odd, you ROOT'd and granted ROOT correct?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I backed up my entire device (just in case of issues), then dirty flashed and it worked fine this time around. I will note, the PlayStore WAS updated to the latest version by Google overnight BEFORE I upgraded.

It went like this, yesterday it crashed from the update, I reverted to the March build, restored everything (TXT/apps/data), it was then running properly with the older/original PlayStore (hamburger style) menus, then overnight it updated to the latest and greatest PlayStore from Google (so now the right side has the account/options), then once it was updated to the latest PlayStore framework (overnight into this morning), I did the dirty upgrade, this time around no issues with apps, no crashes, nor anything to note.

All is well and works as it should so its OK to dirty assuming the framework updates, but that being said, I am not 100% certain that's needed (PlayStore framework) but it is something to note (just in case anyone has issues, we can start to rule out why).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] phuphat1986:
With latest build, worked flawless for me too

And ofcourse, clean flash for sure
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] chopt51:
Dirty Flashed from Feb to April and everything went smoothly. Rooted right away. So far everything looks good. Thank you. We all appreciate your hard work.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
oh yes
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] agill17:
Thank you very much for all of your help. I was able to get the ROM flashed.

Firstly, redownloaded fastboot and drivers to successfully downgrade to A11. From there for whatever reason could not get the ROM to flash. I then used the minimal ad/fastboot tool to flash the ROM. But everything is working now without issue.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
Dirty flashed during my lunch break, everything is up and running smoothly here. 😎

I meant to report it last build, but never got around to doing so, but the Gesture deadzone doesn't appear to change for me. I have it set to half screen it still works by defaults. Can anyone else confirm?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
Is it just me or in "Motion Sense" feature missing in this rom?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
See OP...
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
oops...sorry I missed that. Is this an issue with all custom roms or just PD11? Any chance it might be fixed in the future?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
is there any way to go have face unlock activated as soon as as I pick up my phone? Right now when I pick up my phone The screen turns on to show the AOD and I have to tap the screen to fully wake up the device to activate face unlock.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Ulyaoth:
Hey so I just updated to the latest build and I had the quick pin unlock thing enabled where it attempts to unlock on the 4th digit, but it's not working. Can't unlock the phone now :p What can I do?

Edit: Worked around it by connecting a usb keyboard and pressing enter. I'll try re-enabling it.

Edit 2: Re-enabling it did the trick.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
As far as I know now custom ROM based on A11 supports Motion Sense now. It worked on A10. Feel free to port it to A11. I am not skilled enough for that.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Awesome, I'm very glad to hear it finally worked out!!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Mine does just that, I pick it up and face unlocks BUT I disable ALL AOD so that's probably where you get hung up. Without AOD on, it works how you're asking for it to work. I disable AOD for battery reasons but I also don't like it waking my device.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
As far I know, even with LOS Motion Sense doesn't work yet. I haven't tried anything other than PD11 and LOS11 (18.1) for Android 11, but I don't think it works yet anywhere. I could be VERY wrong with this, but I am pretty sure motion sense is not available on custom 11 ROMs yet as its proprietary and hasn't been reversed engineered yet. I for one, could care less, that's one of Google's cool features I don't like or need. Its a battery hog so I disable it no matter what (stock firmware).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
Is anyone having issues with Google Assistant launching extremely slowly(almost 4 to 5 seconds) or not opening at all, either via saying "OK Google" or long pressing the home button?

Edit: I even booted into safe mode and tried but the issue still presists.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
IDK what to say as I don't often (or really EVER) use Google Assistant (so take this with a grain of salt), that being said, I just "OK Google'd" and it popped right up within no second passed. Meaning it was so instant that not even a single second past (I am trying to use your benchmark to show it works differently for me). I do not have anything funky going on, nor any MAGISK modules, or anything like that, plus I use the default kernel as well, so IDK the differences between us, but it most surely works (at least for me).

One thing to note (and I am not 100% sure this matters or not) as I dont often use GA, BUT I also have the separate "Assistant" installed from the play store (so I dont know if thats why or not):

Google Assistant - Apps on Google Play

Get things done faster and easier

play.google.com
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
thanks (as usual) for your reply....would it help if I posted my logcat ?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Honestly, I am not sure because I do not use GA, nor know what to look for. My recommendation would be to wait and see if other users report the same thing, OR if its a fluke for you (or me). It very well could be a global issue for everyone but because it works for me, I would assume it works for everyone. I wouldn't necessarily know about other user's having issues with it (so I would assume it works for everyone) and give false advise not knowingly.

My point is that I do not like giving advice or offer ideas when I cannot reproduce the issue myself. If I did give advice, it could be wrong and cause more damage than good so I tend to try and only help when I can reproduce it, OR if I know the code inside and out and how the app should function. GA isn't one of those apps I know inside and out so I am treading carefully to not give you wrong advice (that wouldn't help you if I did).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
I understand :-)
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Its the weirdest thing, literally within an hour of writing my reply that I couldn't reproduce it, I stopped over to visit my daughter in college (real close by to my apartment). As I was waiting for her to come out, I was testing "OK Google" and "Hey google", to see which one worked now (I forget which is used nowadays), and sure enough, it did take a few seconds.

Here is the catch though, I don't know if it was a hearing thing or if its an actual GA issue or not. What I mean by this is, I don't think Google heard me over the noise the first time, and picked up the second test I did a few seconds later, OR if it was the FIRST request popping up 4 or 5 seconds later (if so what happened to the second request) or did it not hear both of them. I am going to test this some more as I cannot get it to reproduce on every attempt, but I can see what you mean (I think).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
What is Google doing? Now I'm right back to the old version of the play store (and I didn't do anything), this happened all on it's own and safetynet is failing with API error now.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Lughnasadh:
The SafetyNet Attestation key that John was using was blocked. He got a new API key working and will push an update soon.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I saw that too right after I posted and hit Twitter for MAGISK, thankfully he fixed it and will push out the update shortly! One issue solved, thanks for the additional confirmation! Thankfully the key issue didn't actually break ROOT or safetynet, just the magisk safetynet checker, but not actual safetynet.

It doesn't explain the play store roll back so I am curious what's up with that.

----EDIT: 5 minutes later, the new play store is back, what the heck Google?!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
Within Gestures, turn " Lift to check phone" on. That'll wake your device when it detects movement along with the brightness change. It could just be the brightness change that triggers it as well, not 100% sure. I keep this option off.

Are you using the old Google UI or trying to use the stock Pixel UI?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
John Wu updated the canary build to include the new safetynet key and it's passing again. You'd need to update the app to canary or just wait it out until it reaches production. I never lost ROOT or safetynet, this only affected the MAGISK safetynet API key so it wasn't causing issues as far as I could tell. For that reason, I'd wait it out unless you have a specific need or issue that requires it;
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Prey521:
Newb question.....

When dirty flashing from one month to the next, do I still have to flash the stock factory image for the new month before flashing the latest PixelDust zip?

Thank you
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
Nope.

Just boot into bootloader, flash the given boot.img, and then adb sideload in recovery. You will have to restore your custom kernel if you're using one though.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Without a working custom recovery (TWRP), you need the boot.img to allow signature bypass in recovery. The only way to flash (without TWRP) is with the recovery provided by the boot.img (so you can sideload without signature mismatch).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] NewDev4IOS:
Widevine is L3 on my pixel 4 XL running this rom any way to get it back to L1 without factory resetting and going back to stock?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I havent tried this myself on PD11 so tread carefully. I do not have any streaming issues at the moment (and I use NF/HBOMax/Hulu/Showtime/ETC) but I have in the past. I used this a while ago and on a different Android version and ROM so IDK if it will help, but please review and report back to us the outcome (as always backup everything first just in case). This is for a different device but it worked for my PX2 (I believe it was) or my HTC, I cant remember so be careful:

https://xdaforums.com/t/fix-for-widevine-l3-to-l1.4115977/

You also didn't mention what service is being affected. I know there are Netflix APKs floating around that supposedly force L1 and works but I haven't tested or have a clue, just guessing here. I also am not sure if factory resetting will revert it to L1 because it may be in the firmware/ROM as a security update. You may need to wait it out until its fixed upstream by Google.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] NewDev4IOS:
It's all services, just tried installing the app fix but app did not install. :(

I might try rooting next, for some reason on stock android I could not install Netflix or Disney+ and some other random apps for some unknown reason, usually if it happens it clears up after a bit and it allows me but it never did so I installed this rom and was able to download the apps but widevine is L3 not L1 which makes everything play in SD which is quite frustrating but I've been dealing with it so far.

If rooting doesn't fix I might factory reset and if it still doesn't work then full reset back to stock.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Do you mean they won't show up in the play store so you can't find them? If so that's most likely bootloader unlocked tripping safetynet and play isn't certified. To fix, ROOT with magisk, enabled magiskhide then clear play store data and it will be certified once you pass safetynet then they will show up in the store.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] NewDev4IOS:
Thank you, so that's why they would never show up lol
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
NP, it's part of Google's attempt to use safetynet to block apps when insecure (bootloader unlocked / ROOT) but it's only because safetynet trips. Once you pass and are certified (play store), you are seen as secure and official so it removes the block and all apps show up. I deal with it every time I switch ROMs. I forgot to add that you might need to use magisk canary right now because the API key was banned. The new key was added to the canary build.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Giunta._:
The motion sense works now?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Why would it now, verses before when it says in the OP it doesn't work (and noted throughout the thread)? I am not trying to be a jerk, but I am more curious why you would think it would work now.

I am not on this ROM right now, but motion sense is proprietary code so its not an easy fix.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] i42o:
This rom is not the best at screen share. Major lag .
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Do you mean Miracast (TV) casting or to Google Chromecast casting? I just tested Chromecast from my screen share and it didn't lag but I don't have any Miracast devices to test on.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] 2WildFirE:
Can I use this Coral ROM on flame?

In the past there was separate flame ROM.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
No, I guess not.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
New build with May security update and blobs was pushed. Have fun!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Awesome thanks fkm!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] blueyes:
I'm running stock rooted with bootloader unlocked. I flashed the boot image from this ROM (considered flashing the full ROM as I've used it on P1xl and 2xl). While stock rooted with the boot image I was unable to download Netflix and a couple others as they're hidden in playstore. Had this happen before so I self installed them from APK mirror. Wanting to update to the May security update I had to reflash the stock boot (adb sideload fails otherwise as the build.prop in the boot is a mismatch). Anyway after rebooting and rerooting, flashing ElementalX kernel, bootloader still unlocked I'm now able to see those missing apps in the playstore. So a possible fix could simply be flashing the stock boot then a custom kernel if you so choose as this won't change the boots build.prop.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] pallefar:
hey guys, is there a way to adjust the quicksettings bakground transparency? I see with the new update the notications opacity is added.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I am not really sure what you did or meant with the stock rooted and using this ROM boot.img. That won't work right unless you're using this ROM. The build.prop is failing because you're using a boot from another ROM and trying to sideload an update so it's detecting an incompatible ROM. To be honest, it makes no sense to use a stock ROM, and change the boot to using a different custom ROMs boot.img.

The NF missing is only because the bootloader is being detected as unlocked and failing safteynet / playstore uncertified. You need to pass safteynet, the easiest way is to magisk hide. All you did was fix the safteynet failure with custom kernel and magisk. An unlocked bootloader will always trip safetynet nowadays. That is the ONLY root cause to NF not showing up.

I wrote the fix a few messages back, fix safetynet with magisk and hide enabled, clear playstore data and you're good to go, NF won't be hidden anymore.

What you're suggesting as a possible solution won't work UNLESS you ALSO relock the bootloader then it won't be detected but not with how you presented it. Your fix was when you re-rooted and now passed safetynet. Relocking the BL is a bad idea so be careful with what you presented as others may read it and soft brick the device (bootloop).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] blueyes:
I thought I made it clear the reason behind my flashing this ROMs boot image. Thought about flashing this ROM as I've used it one a couple other devices. Flashed it's boot because it would be necessary to flash this ROM using stock recovery. Just never got around to it. I ran stock WITH THIS BOOT for a month with no issues other than the hidden apps. The boots made for this device so it is compatible. A month of running it proves that. Only when I decided to manually update to the May security update did I flash it back to stock kernel. And kept the stock base kernel. Once I updated I was able to see those apps, bootloader still unlocked. Still able to see them after rooting again. I also never hid magisk in the magisk apps settings, then or now. Nor did I clear the playstore app data. Nor did I ever relock the bootloader (why would I?). I've been at this a while and would never suggest something that hadn't first tried myself. After seeing your post I flashed a stock 2xl boot to my 2xl running Pixel dust. No issues either. You're acting as if I suggested to flash a boot from a totally different device to this one. That would probably cause a problem. Lol