yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Well that's what I'm confused about, maybe it was the wording you used but you did say that you're running STOCK. Stock ROM (Google firmware) is how I took that comment, but not PixelDust. Did you mean stock as in PixelDust not rooted (untouched boot.img for PixelDust), OR what you actually said and firmware that came with the device (stock)? I just try to clear up the confusing details for newbs so they don't get the wrong info. Stock usually refers to what Google provided (official firmware).

If you meant stock as in PixelDust boot image, and you're using PixelDust ROM, then yeah that works fine and how it's intended to be used. Your wording is very confusing because you say stock, stock is Google untouched firmware so that's the clarification I'm making.

Regardless, you're solution won't work because of unlocked bootloader. Just root, magisk hide, and clear playstore, but it won't magically work with the BL unlocked and flashing the ROM boot.img.

Also you're using CUSTOM kernel so that removes the stock boot.img with anykernel and would be the ONLY reason a STOCK boot is working with a CUSTOM ROM.

And don't take anything I say as an attack on you. I'm only trying to keep the right info in the forums for other users who need the help but not attacking or being argumentative.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] blueyes:
Again I thought I was pretty clear the first time when I stated I ran stock android with this pdust boot linked in the thread. I can give you a step by step process if that helps.

I was running STOCK Android 11 April factory build straight from Google. I thought about flashing this ROM so I downloaded the boot from the op and patched it with magisk. After unlocking the bootloader I then immediately flashed the PD boot image. Rebooted my phone and went through the setup process again as the unlocking wiped it. At this point I'm still running fully stock android 11 April factory build WITH the PD boot image. Never got around to flashing the PD ROM so up until the May factory google update was released I ran the factory ROM with the PD boot without any issues other than missing apps as I previously stated.

Before updating to the May build I had to flash the stock boot image. After it updated I patched the stock boot and reflshed it gaining root. Immediately after booting back up those missing apps were now present and available in the playstore. No magisk hide, no relocking the bootloader no safety net patches. Having used ElementalX for years I did then use the app to flash Ex. Still no issues with missing apps. (I'm fully aware of how any kernel zips work and they don't effect the symbolically linked default.prop located inside the boot images ramdisk.)

To summarize , for 1 month ran completely stock aside from the PD boot ran fine but had those missing apps, back to stock boot upon may update. Apps present and available. Never had PixelDust on this phone. Only the boot image.

This has gone much farther than intended and if you've posted a fix that works for you, I missed it. Wasn't aiming to step on any toes.

I also don't mean to be argumentative or sound condescending. I don't think we were on the same page and things were getting more complicated than necessary. I do respect you looking out for "newbs" , but having built plenty of ROMs for several devices I would never bring up something that I hadn't tried or tested myself. That would be irresponsible.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
OK so basically it was a wording issue. No prob, all good.

A few things to clarify. When you say "for one month completely stock", were you also running a custom kernel? Also you probably were running stock/stock on the separate partition.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] blueyes:
During the month in question I ran completely stock (factory ROM) and the PD boot for a week or so then using the ElementalX app flashed his kernel on top of it for a couple weeks. Had the missing apps for the entirety.

Apps showed back up following my updating to the May factory build, stock boot , rooted etc. After a few days , yes I did reflash Ex. Apps remain present.

Are you asking about the inactive partition while running the stock ROM and PD boot on the active partition? In April I was actively on slot_b (stock ROM and PD boot). And actually was also stock with PD boot on the inactive slot_a. The reason being when I flashed the PD boot initially I flashed it to both slots. (Im aware it's not necessary but between continuity and maybe a little OCD I've been in the habit of flashing both slots since they introduce AB)
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
OK so you answered the question. You ran EX (custom kernel) which is why you lasted a month and it worked. I've beaten this to death so I'll leave with this final thought, flashing the stock boot will not magically make your device certified and pass safteynet so don't do it and expect it to work. That's my main take away and what I've been pulling out from the convo.

No I'm not asking about the inactive partition (slot). I'm trying to get you to understand what you actually are doing verses what you feel is happening.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] blueyes:
Ok I guess we'll just have to agree to disagree. I appreciate it but I don't need you to help me understand what I did. I know exactly what I did. EX has zero to do with it, just extra information. Phone ran fine with stock ROM and PD boot for 2 weeks before flashing ElementalX. Saying flashing ElementalX is the reason why I lasted a month makes no sense as it ran 14 days beforehand and could of ran 14 more if I had chosen not to flash it.

I never said flashing the stock boot will make it magically pass safetynet. Never mentioned passing it. In fact I clearly stated earlier I never activated magisk hide. For some reason last month the apps were hidden and now they're not. The ONLY DIFFERENCE between the two is the base boot image. Something between the 2 changed allowing those apps to be available. I know what I did just can't say why, but at this point I don't care anymore.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Okie dokie, I'm not arguing. I don't care what happens but I am trying to keep it accurate for others and it's not. I could also pour milk in my gas tank and it will work, until it doesn't.

It's all built from Google code, so sure, some things will work, but that doesn't mean it's correct. Others should not read this and assume you can flash another OSs boot and run it. You also cannot flash the boot.img and fix safteynet and playstore certifications (which started this with the "possible solution"), it's not.

NF not showing in playstore is very well documented, and certification/safteynet related, so that's the issue. That issue cannot be solved by flashing that months boot.img.

We can agree to disagree, but I don't think that's the issue. I think the issue is we're focussing on different aspects of what's being said.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] blueyes:
Stock/PD boot missing apps

Stock/stock boot apps available. Pretty simple until you disected it and browbeat it to death. Ridiculous analogy, my phone started up, rebooted, ran fine with stock/PD boot. If there was an issues it wouldn't of booted and ran fine for 2 weeks. You're logic is off.

Your engine requires combustion, milk wont turn it over much less last 2 weeks. What do I know, just an engineer at an oil refinery.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
LOL ok. I could chime in with who I really am and my multiple certifications in senior sys engineeing/architect, or the ROMs I have developed and supported for users, but why waste the energy.

We do agree on one thing, I did beat it to death so the accurate information was there.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] blueyes:
If I made some stupid ridiculous analogy about something you had expertise in I'd expect nothing less. Let me know how that milk in your tank works for you. I tried to keep it peaceful, but you just couldn't stop browbeating. I'm sorry but I can only take so much. I'm done.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Sorry if I rubbed you wrong, I did say early on that I wasn't personally attacking you or for you to take NOT it personally. I was not attacking you, so if I came off that way, I am sorry.

I do repeat myself on purpose to point something out that is not sound advice (so its seen over and over again to catch the newbs eye). I do this so it's in the thread and seen over and over to protect others. Sometimes this comes off wrong and the user feels attacked, so I am sorry if I made you feel that way. You are not the first user I have offended or upset with this type of repetitive actions but it was not intended hurtfully. My only intention is safety for others and their personal data. Using the wrong boot.img can (and usually will) cause either a soft brick, or bootloops.

You really shouldn't run another boot image, than the OS you're on. Being certified for the PlayStore is important for the apps to appear (when the BL is unlocked). Those were my only two points I was trying to clarify, the rest was wasted energy.

Goodnight
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
Why the hell one uses Stock with PD boot.img? Makes no sense for me, sorry.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Me neither, but I didnt get anywhere so I tried to made sure others didn't try it as sound advice.

Maybe this user will listen to you, the DEV of the ROM (and many others)!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] blueyes:
It wasn't my intention to run stock with PD boot. I downloaded both the ROM and boot with the intention on flashing both. After flashing the boot and before flashing the ROM I received a call on my landline with a work emergency that required I leave immediately. Ended up working nearly a month straight 7 days a week 12 hours a day so never got around to flashing the ROM nor the energy to. By the time May came around I just reflashed stock boot and manually updated. I never said to myself "Hey lets just flash this boot".
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dragynbane222:
I still say you should get around to finishing the process, PD is a good rom, after all.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Mr. Blanco:
Just wondering if anyone else is having issues launching the stock camera via double pressing the power button , i have double tap power button in gestures enabled but for some reason it is not launching , it was also like this on the previous version of this rom , im running this rom stock with no mods or root
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] KingMike67:
I have had it happen a few times but I can't always reproduce it. Does it happen mainly from the lock screen? I usually happens to me when I'm at the dog park and I take my phone out to take some pictures. I have Snapchat, Tasker and PicsArt that all want to use the camera double-tap shortcut, so after I set the Google Camera to be the default the problem only happens every so often
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Mr. Blanco:
It's actually not working at all for me(double tap ) power button for camera . I've resorted to using the active edge squeeze function to use camera , I miss the double tap function Badly ..lol
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Mizta_Rshn:
Hello there . Im new here :)

I have installed PD ROM yesterday .

How do i root it ? Should i use Stable or Canary version ?

I have tried using root method from link below using both stable and canary version . My touch screen not respond on first boot after flash the .img file that created by Magisk .

Not sure if my step are wrong or the boot.img file are wrong ? Should i use boot.img from factory image or from this thread ?

Link : https://xdaforums.com/t/guide-root-pixel-4-xl-android-11-r.4160441/
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Stable (MAGISK v23.0):

Release Magisk v23.0 · topjohnwu/Magisk

This release is focused on fixing regressions and bugs. Note: Magisk v22 is the last major version to support Jellybean and Kitkat. Magisk v23 only supports Android 5.0 and higher. Bug Fixes [App]...

github.com

Install the APK you download from that link (or here Magisk-v23.0.apk), open it, click install, then select patch (top option), choose the BOOT.img from the ROM (download it along with the ROM zip and make sure its the right monthly version), the name will resemble the ROM name (and date) but comes from the ROM not stock, once its patched, it will be in the download folder. Copy it out to your PC, then FASTBOOT it to your boot, then boot (reboot to system), enable MAGISKHIDE in the MAGISK options and you will pass safetynet (you should if you did everything right):

fastboot flash boot magisk_patched.img

The name wil be random but resemble something like this "magisk_patched-23000_XXXX.img".

Easy Peasy but I dont know whats going on with your touch, I have had issues like this when using 3rd party kernel, so I would only use the stock kernel and patch it but not a 3rd party kernel.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xFaultx:
Any suggestions for face lock and wearing a face mask? With the default face unlock you can trick it by wearing a mask on half your face. With this one it's just your face straight on, so it can't be tricked. Any help would be awesome, really annoying to have it lock me out just cause i have my mask on
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
Why not just distance yourself a little and pull it down for a quick second?

In some situations, I've seen my face unlock work with my mask on, but other than that, I just pull it down for a quick sec to unlock if I really need my phone.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xFaultx:
I work in a pharmacy, patient facing, bit have to use my phone for work a lot, and pulling down my facemask isn't really the most professional thing in a healthcare setting unfortunately. That's why i was wondering about the stock face unlock app, cause that one instead of one picture, the stock one takes several, so is easier to do a few with a mask on
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
Ahhhh, I see the issue.

I just checked Scorpion's Telegram and seen something about Face Unlock being merged from PD, so not 100% sure if it's different or not, but a small workaround is possibly Smart Lock?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] AuroraLights:
I can't connect when I check the update in the settings. What do I need to do?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I do not use the updater, just dirty flash the update.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xFaultx:
Also having issues with the squeeze to load assistant feature. My default it was set to take a screenshot, but when I change it to the assistant option it only sometimes loads, and actually ends up seeming to crash the assistant
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
Is it crashing or not popping up?

If it's not showing, you'll have to add a language to Google Assistant that the new one isn't supported in so that it uses the old one, which appears properly on custom roms.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xFaultx:
It's more so popping up very slow. Like 45 second later, and with terrible inconsistency
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xFaultx:
For the Google assistant, it seems what it might actually be is the assistant is activating, but there's no visual that it is like normal. So I can use the active edge and say set alarm, but it didn't have any visual or audio notification it's working really, just a quick pop up the alarm set, but no notification like it would normally have
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I'm pretty sure if you change the default language, it fixes that issue. Look thought the forums and it's written somewhere. I personally do not use GA so don't quote me on it.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] flash713:
Same on my phone. Anyone ever have pulse stop processing? Seem like I remember a solution being Android compatibility patch magisk module but there's quite a few options now when selecting that module. I guess I need to read up.. I use YouTube Vanced (rooted) for music and that's what I'm referring to when I say pulse stopped working.

(Edit)
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Unfortunately using a mod'd app (youtube vanced) or MAGISK module to overcome an incompatibility moves you into an unsupported territory. That would be 3rd party to the ROM (vanced YouTube) so its not really a ROM issue. I am only mentioning as you might not find the right support here in the ROM forum (is what I mean). You may find better support in the vanced/YouTube forum.

I cannot reproduce it myself as I do not use it, so maybe others do and can help, but I would also reply in that forum's support.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xganjazzx:
Does anybody know how to fix an issue where whenever I close a recent app, the stock pixeldust launcher pops up it's home screen instead of my 3rd party launcher? When this happens, I can just hit the home button and have it switch back to my set default launcher instead of pixeldust launcher, but that gets really annoying lol any ideas?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Prey521:
I'm having the same problem. It eventually fixes itself after a few reboots, but it is pretty annoying lol
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xganjazzx:
Indeed. It doesn't happen everytime, but it happens more often than not. If it only happened sometimes it wouldn't bother me, but that isn't the case. I wonder what it could be?I can't think of anyway to stop that from happening that is within my knowledge.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
did you freeze the default launcher? I only had this issue when I froze default launcher (recents), when using NOVA. When I unfroze it then set NOVA as the default, it no longer happened. For me the issue was 2-fold, first the recents were not working right because its tied to the launcher I froze, then the second issue was with NOVA not staying in memory (hence the stock launcher). Once I set it to default, its been fine ever since.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xganjazzx:
I tried freezing pixeldust launcher and ran into a whole mess of issues like you, so I knew that wasn't gonna work. Real big headache. I'm using Ruthless launcher and it is set as my default launcher. Has been set as default in settings for a couple weeks now and still keep getting pixeldust launcher popping up when I swipe away recents.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
shoot, unfortunately I do not know that specific launcher so I am not sure if its a launcher or RAM issue, or if its something I am not aware of, so I cant pinpoint the issue first hand. I know I had similar issues with NOVA until I set default and unfroze default launcher but IDK about Ruthless. I will see if I can reproduce it with that launcher myself and test.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xganjazzx:
I would appreciate any help I can get with trying to figure this out haha. It really irks me a little bit haha. Could you explain to me how the ram might be an issue?

I'm going to try setting pixeldust as default launcher again and then changing it back to ruthless just to see if that might help get things right.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
Wish I had some sort of insight to that but I use OnePlus Launcher by MrSluffy & GodLeaveMe.

Haven't looked back since then at any other launchers. You could maybe delete the default launcher from the system completely, or make a module to do so(maybe even use it to just throw Nova in as a system app).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xLoveHateLegend:
Spoiler content hidden.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xganjazzx:
I tried deleting the default pixeldust launcher once and literally broke everything until somehow it reinstalled itself and everything worked fine. Is there a way that I could make ruthless launcher take the place of the default launcher maybe?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
If setting it to the default app for launcher doesnt resolve it, then IDK. Thats how it reacts for me with NOVA, I set it to the default and leave pixel launcher in the background (not launched). This leaves the recents and all stock functionality intact (pixel launcher) but uses NOVA as the default.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
My best guess is that deleting is broke because PD Launcher controlled your recents UI. You could install a module to install the normal Pixel Launcher, or if you're up for it, you could install the OnePlus Launcher as well to replace your stock recents and use the launcher of your choice.

OnePlus Launcher: https://www.pling.com/p/1451515/sta...&file_type=application/zip&file_size=43448873

On another note, Mr Sluffy is currently working on a modded Pixel Launcher. You can check out the teasers here: https://t.me/mrsluffy_releases
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
The user could also dirty flash the same ROM (as an update) to fully reset the PD launcher and needed framework (whatever was possibly damaged with the deletion). This should solve the launcher/recents issues and what I'd try next as it's less intrusive and shouldn't damage any personal data (texts, user apps/configs/ETC). It will simply replace and restore what was removed by treating it as nothing more than an in place, dirty flashed update.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xganjazzx:
Just install the one plus launcher like a normal app? I didn't see any extra instructions. Just verifying.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
Just flash the latest Magisk version(6.2) of the module in Magisk and reboot.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xganjazzx:
Alright, I installed the OnePlus launcher and I like this recents screen a lot better. Is it safe to remove pixeldust launcher now? Have you noticed any improvements to performance and battery life maybe or is it negligible?

Also, I have another weird issue where my phone will reboot by itself one time after I reboot it manually. It doesn't happen everytime either, but a lot of the times. Anybody know what that could be?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
PD Launcher might be temporarily removed by the OnePlus Launcher, otherwise you could just disable it or leave it to the side.

As for the reboot issue, it could be something with your setup. Try disabling all your Magisk modules or specific ones and reboot to see if it still happens.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xganjazzx:
I only think I'm using 2 magisk modules for edexposed but I will try disabling them and reporting back.

After switching the default launcher back to pd launcher and then back to ruthless launcher, I didn't get pd launcher popping up it's home screen for like 2 or 3 days so I think there was just some lag from me switching launchers a lot trying them out. Still hasn't happened since I added oneui launcher and I really enjoy it with the oneui. I think my battery life has improved very slightly and my phone feels slightly snappier. Do we know if oneui or pd launcher consumes less ram?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] phuphat1986:
When update Jun 2021 @fKm ???
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
When it is ready. Feel free to do it yourself, sources are there for you to compile...