yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] spezi77:
Could you tell us what exactly is wrong with the display of "It's twelve oh one"? I am not a native speaker. But if you look it up on this website, the clock display in the PD ROM behaves correctly: http://www.theenglishminute.com/Videos/Time.html

Incidentally, the display is exactly the same as in the stock ROM.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] agill17:
Wow, thank you so much for your thoughtful reply. I too love open source and custom ROMS. I have been using them since the days of Cyanogenmod on my Galaxy S2. I will send you a screenshot of what happens when I try installing via ADB. Would it be possible to set up a remote desktop connection to my computer so that we could work through it together? Can PM me if that is something you are interested in.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Unfortunately that's not possible with my day job (plus remotely doing a phone from ADB on your pc would be near impossible), I would need to see the device with the PC for that to work. I usually put in 12 to 14 hour days, every day, 365 days a year (with less in weekends but still a full day). That's why most of my detailed replies come early because by the end of day, I'm done and don't have the energy to care about anything.

Let me do this though, I'll write up step by step with pics and it will make super easy. It will take some time, but I'll write it up. As long as you follow them exactly as I lay them out, you will be fine.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
I was unaware of that! It seems so odd coming from o'clock.

On a sidenote, my double tap power to open camera doesn't seem to work, can anyone else confirm?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Right but it's also not quite right for all use cases. Yes oh clock is used, but generally in the NYC area, for example, we do not say oh, but 'o clock. It goes either way is the problem and either can be used, me personally, I only use 'o clock and never the OH clock.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
Maybe that's why in my head "oh" just looks so wrong. I'm in PA, and pretty sure I saw "o'clock" a crap ton of times before I ever saw "oh'clock". I'll have to do more digging and paying attention to remember 100% if the other rom did which at what time now that I'm aware of a difference. o_O
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
100% exactly what I'm saying and meaning ;) it's like saying lift in england for elevator, but here we say elevator, not lift.

I live in upper NJ, work in NYC and I've NEVER once used 'oh clock in my life. I've lived here in the east coast (NYC/NJ) since I was 6 (so 39 years). The other way 'o clock is the only way I've used it and anyone else I've ever known uses it. It's just a matter of expression but yeah, it looks weird to me too and I called it a 'bug'. I guess it's not, but I also wouldn't use the way it is in my daily use, but others would so it's not right or wrong I guess. That way does look wrong and funny to me too ('oh clock).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Here try this:

From Google with my notes:

PREPARE:

You need ADB and ADB drivers (SDK) installed and available for CMD to find it. You will also need the matching ROM / firmware FACTORY image downloaded to your PC. Unzip the factory firmware zip you downloaded. In there contains the images needed to factory restore the device, along with the flash-all batch file to do the work.

Factory Images for Nexus and Pixel Devices

This page contains binary image files that allow you to restore your Nexus or Pixel device's original factory firmware. You will find these files useful if you have flashed custom builds on your device, and wish to return your device to its factory state.

https://developers.google.com/android/images?hl=ru

Warning: To flash a device using one of the system images below (or one of your own), you also need the latest fastboot tool. You can get it from the Android SDK Platform-Tools package, which you can download here.

Once you have the fastboot tool, add it to your PATH environment variable (the flash-all script below must be able to find it).

DOWNLOAD/FLASH:

Go here, download the March firmware to your local PC/MAC/Linux:

https://dl.google.com/dl/android/aosp/coral-rq2a.210305.006-factory-82bad63d.zip?hl=ru

Unzip the firmware you just downloaded to disk, make sure ADB is installed with drivers and in the same folder or in your environment path

Open a terminal (command or bash) and navigate to the unzipped system image directory (which also has ADB and fastboot or make sure it’s in the environment variables so the entire system can find it).

SET ACTIVE SLOT to A then to B when A completes (more info below)

fastboot --set-active=a

fastboot --set-active=b

Execute the flash-all script. This script installs the necessary bootloader, baseband firmware(s), and operating system. This is first done on SLOT A, then SLOT B (on SLOT A because we forced slot A, then when done, SLOT B, so we can get BOTH slots prepared for the A12 removal and restore BACK to factory 11).

WATCH the process on the initial A slot, when it gets to the VERY LAST STEP, erase userdata, it is almost done. The very second it reboots (but NOT before it completes), let it finish then reboot on its own (its part of the flash-all batch), hold POWER+VOLUME DOWN to catch the boot process BEFORE entering the OS for setup. Switch to SLOT B, execute step 3 (same flash-all) on SLOT B, this time, hands off and let it boot into the OS setup. Skip everything, no G account, no pin, nothing, once its done, reboot to BL and follow ROM steps.

Now its prepared and ready for the ROM install. I will also send this to you in a word doc over PM so it keeps my formatted notes.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Prey521:
Why do you have to flash to both slots? I've never done that with any ROM, including this one, and have never run into any problems.

EDIT - Nevermind, I see that this is to resolve his particular issue.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] agill17:
Any idea why I have been getting the errors that I listed in my screen shots? I have followed all of these instructions as well as other I have found on the internet.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Yes Android 12 preview, we're trying to get rid of it and back to factory to install pd11
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
From your error you are getting further along but now you're having write issues. That's either USB cable, ADB driver is outdated, SDK is outdated, or connection issues. I've seen that before personally when my ADB and fastboot is outdated so get a newer copy of both (driver and all). Start with sdk and use a different USB cable just to be sure. I've had that happen when cable disconnects from age, and also another time when my sdk was outdated so it didn't reboot to fastboot. You're almost there and almost ready, you just need to fix this last piece.

This firmware can only update the system in fastboot so it must be able to reboot mid-process of the firmware into fastboot to finish. That's where you are stuck now.

I will also note, what you show in your screenshot is slot A is good and roles back (at least one did but I didn't see your slot switch commands so I can only assume A), I can see it erased userdata. Slot B is A12 and needs to be rolled back (erroring) with system write (but didn't error on newer firmware). I would expect you can fix this updating sdk and trying another USB cable. That's how I've fixed it in the past.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
Update: Fixed the issue with the double tap to open camera. It appears that if the lockscreen shortcut isn't there, it does nothing. 😎
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] agill17:
I've tried multiple times with new cables, updated SKD, etc and still no luck. Will just wait until Pixel Dust for android 12 is released.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Right but something doesn't add up so something is not right but I don't see it remotely. You could also force slot A and install the ROM to slot A, that should work based on the pics you sent me. Slot A worked, but slot B didn't which makes absolutely no sense and doesn't add up. The process you're using, have been successfully done by millions of users including myself thousands of times. I don't get it and what's not working for you but there's something going on but I can't see it without doing it myself. Waiting for PD12 isn't really the best answer because who knows if that will happen and you're not fixing the issue by leaving it the way it is. You will be stuck on 12 until we figure this out.

One thing we didn't discuss is the device itself. What model is this, Google direct or carrier branded. I'm asking more for the bootloader status. I can't remember if you confirmed you went through the bootloader unlock steps. You can update using a signed firmware with a locked BL, but you can't downgrade so that's my last ditch effort here. Check the status of the bootloader but even that doesn't make sense based on your pics. That does look like slot A worked so I'm not how that did but not B.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] agill17:
Bootloader is 100% unlocked
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I assumed based on slot A rolling back but I'm not sure what's up with B. What's the OS running on your device right now A11 (March firmware), or still 12P on slot B? Does slot A work with 11 March firmware? Switch boot slot to a to know.

I'm curious if this works and you can boot A11 on slot A (which should technically work):

fastboot --set-active=a

If this works, you should be able to factory reset and use A11 with stock March firmware. Then install PD11 to slot A only and boot/use slot A (I mainly use slot B and leave A untouched). My slot B is usually my ROM daily driver and my slot A is left untouched in case of issues or emergency usecase, but it doesn't matter. Either slot can and does work for the booting the OS.

I still feel this has nothing to do with android 12 preview. I was on it myself when it first dropped for the pixel 4XL and didn't like it and rolled back to 11 and installed this PD11. I know it's possible from a pixel standpoint (mine is directly from Google though, not that it should matter), but I have no idea why yours doesn't work. Especially if this is truly a Google pixel and not a carrier branded version, they are meant to be factory rolled back by design so this doesn't make the least bit of sense. I'm still not sure what all that's been done to get you there, but the factory firmware most definitely should work and roll you back so somethings not right, but not being there in person nor knowing/seeing what landed you there (steps taken), makes troubleshooting that issue difficult to pinpoint but I wouldn't give up. Me personally, I would stick with it until I solved it, no way would I end up using 12P when I don't like it. I'd figure out what is going wrong and fix it. It's definitely possible but you need figure out what's going on. I still think your fastboot is outdated but that's just me.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
I just got a Pixel 4 XL and was recommended this rom. Im coming over from the Pisel 2 XL. Can anyone tell me how to flash this rom with Magisk and ElementalX kernel ?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Follow OP steps, I came from the PX2 XL and then 3XL, myself so its almost the same process. Get onto the latest March 11 firmware for the PX4 XL (make sure your bootloader is unlocked), then go through the OP steps. OP steps work 100%, if followed correctly. It is truly an excellent ROM for the PX4, especially being an 11 ROM. I use this as my daily driver and only test the LOS official 11 ROM but other than those two, PD11 is mainly all I use. You wont be let down using PD11, you will love it! Its fast, stable, and bug free, I get incredibly long battery life (almost 2 days if idle), and I haven't rebooted in over 10 days and probably wouldn't ever need to if I didn't test other ROMs. Point being, it runs so well, I never have to reboot to free RAM, or recover from any bugs. Its stable as a table!

For EX use the EX app or follow those dev steps for EX installation in the EX forum.

For Magisk, patch the ROM boot.img, then ADB the new patched boot, or follow MAGISK dev steps in the MAGISK forum.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
thanks for the reply. I just flashed PD 11 and an now tring to figure out how to root and flash EX kernel? any idea in which order it should be done?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Yes, MAGISK first for ROOT (you must be rooted to use EX app), its simple. If you need help, I will lay out the step by step but its also listed lots of places in the forum and the MAGISK forum itself. The quick answer is this:

-install MAGISK app

-patch boot.img within the MAGISK app (its the install option)

-then ADB the new patched boot.img.

Once this is done, and booted off the new MAGISK boot.img, you will achieve ROOT. Then install the EX app from the store and grant ROOT to EX, then in EX, it will notify you there is an update (this is because EX isn't installed and currently running as the kernel yet) so EX is telling you there is an update. The update is actually just the EX kernel latest release, you can directly patch from the EX app then reboot and its done.

I WILL NOTE, I have had issues with EX and 11 ROMs. I dont know why, but the last test I did with EX caused issues with RIL and WiFi. You will know right away if you cant get WiFi to connect. I am not 100% sure if this is fixed or not, so my point is to keep the patched boot.img handy and close by (the MAGISK exported newly created boot.img). You can ADB this using the same process to overwrite EX kernel IF you have issues. You might not, but I dont know because I am not using EX. The built-in kernel rocks so I am not using EX at this time, but EX was my go to kernel for a long time so just keep it in mind if you have odd issues after EX is installed. IF you DO have issues with EX, simply restore the patched boot.img from MAGISK (from step 1 - ROOT). This will roll back and remove EX and restore the default kernel (ROOTed).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
thank you so much for the aweesome reply...just one question the boot.img I will patch using the "Select and Patch a file" option in Magisk is the PD 11 boot image from the OP? The one at the link below?

https://sourceforge.net/projects/pixeldustproject/files/ota/coral/boot.img/download
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dragynbane222:
Correct. Though what the previous got said it's slightly incorrect. You can't adb spiderman a boot.img, you need to copy the patched boot.img to a pc, reboot the phone to the bootloader, keeping it plugged into a pc, then run "fastboot flash boot ./<name of patched boot.img>" from the directory the patched boot.img is in. Then you should be good to reboot and flash ex kernel, it'll automatically detect magisk and patch accordingly, so you keep root.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
got it done...but like you EX breaks wifi :-(
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Not true at all especially when the OP mentioned EX app. You can (and I do) directly flash from EX (tools, flasher).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dragynbane222:
Correct, I'm talking about the magisk patched image, though. Afaik the rom itself lacks the permissions to modify the boot partition from userland without magisk
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
This is what I meant, EX breaks WiFi. Use the EX app tools, flasher and restore the boot.img using EX directly FROM running android. No PC needed at ALL but you can also do the ADB PC method.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Have to tried this yourself, EX and MAGISK both utilize system-less. Both can directly patch the kernel using anykernel.

I'm not trying to be a jerk or start an argument but trying to keep accurate details for users who need them. What I said absolutely works without question.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dragynbane222:
Not for a while, no, so I could very well be wrong, though that might explain my abnormal state when using the fastboot method
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dragynbane222:
But I'm simply talking about the modified boot.img which is necessary for magisk to function, it's a catch-22 without it. You can't adb sideload a boot.img without some form of root
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
You are correct in that I said ADB, when its a fastboot command but he noted EX, so I replied EX. the command is truly fastboot flash boot magisk_patched.img so I think I actually confused everyone by my reply (even myself). I was referring to the EX method, but yes you need ROOT first, with fastooting the boot.img, I did note ADB, it should be fastboot. So I actually confused everyone by combining the methods when I shouldnt have so my bad for that confusing piece and good catch, BUT its still accurate in that anykernel can change a system-less ROM (ROOT/kernel/ETC).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dragynbane222:
Haha, not a biggie, I confuse myself all the time.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
:) I gave you even more kudos but you replied to quick. The usual reason I say ADB is because its almost always started with an ADB call to fastboot so I generally use the two terms interchangeably. That's wrong and I shouldn't use the short terms when its not accurate for the intended goal (fastboot patched boot.img). This is especially true for me, when my main intent is to keep accurate detailed info for users who need help. This was a good catch on your part, and a bad example of laziness on my part by short terming the true commands:

adb reboot bootloader

fastboot flash boot .\boot.img
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ckrummi:
I recently bought a used Pixel 4XL that had broken WiFi. I recently acquired root and I am trying to install Pixeldust. I was wondering how to restore broken WiFi, do you know how?

Side note:

Installing this ROM I am stuck at 51% says ADB and on my phone I am stalled step 1/3. Ideas anyone?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Explain broken WiFi? Does it work on an official firmware, or did it break from a physical issue? If it's physically fine, then roll back to official firmware and test, if that works, then install PD 11 (this ROM) but don't use a kernel. WiFi is perfectly fine with PD 11 and the stock kernel but as soon as I take that same PD 11 and install EX, WiFi breaks so that's software (kernel) based but not ROM related. PD 11 isn't the issue with WiFi, WiFi only breaks when using EX kernel but I don't know why. That's for the EX dev to sort out.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ckrummi:
Thanks for the quick reply. I am about to head to work here in a minute, I will reply after I get settled into work.

For now, I find that on stock android 11 there is an "unavailable" address or whatever for the wifi. The Pixel sees some wifi but not all all the time. When you try to click on the wifi network then sit save for the password, it consistently fails to connect. Never working. I was told the WiFi worked a couple months ago but now it doesn't at all.

I copped the 128GB device for $129 on Facebook Marketplace hoping I could root and somehow fix the WiFi. If not, still not the end of the world - I got unlimited internet on Magenta Max.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
That's really weird to be honest, almost sounds like somehow your Wi-Fi physically got screwed up, but IDK, just guessing. If it were me, and to rule out hardware definitively, I would roll back to a factory firmware. Then go through a quick setup and see if Wi-Fi works under a fresh, stock firmware (factory). That way you will know for sure if its software of hardware (physical), or not. If its software (firmware / ROM), then you should be able to solve it with a fresh ROM install (PD 11), but if its hardware then no ROM will solve it.

First thing I would do is test a fresh stock firmware and see the results. I say this because we still do not know if you bought a physically damaged device, or if this is simply just software based (IE kernel causing it, or OS causing it). Once we know if its physical or not, we can probably help better. FLAR2 (EX dev) also noted PD11 and Wi-Fi issues with EX so that's also possible (but since we do not have enough info, I am guessing):

https://xdaforums.com/t/kernel-september-8-pixel-4-elementalx-2-04-android-11.4046535/post-84783599
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
The Smart Charging feature doesn't seem to work for me? Is this a known issue?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
What issues are you seeing with smart charging? It works flawlessly here (and I wrote about it a few pages back in reply to another user). I have no clue what you have setup or configured with kernels and such so it makes it difficult to help. Without clear information or logs, users are basically asking us to guess and that's not affective so try to elaborate on the issues you see please.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] zangxx66:
Is there any way to block Google Play updates? My device often restarts automatically and Settings are initialized for this reason
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
No safe methods I am aware of, but maybe others have an idea. The updates come from Google directly so if you were to somehow stopped it, who knows what will break. My main worry would be the play store updates and normal usage. It does annoy me as well and I do lose my custom settings, but I just reset the changes back after the update. I know it doesn't help answer the question but I wouldn't try to stop it unless we clearly know what else will break.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
@GROOVYJOSHCLARK is there any way to make this rom compatible with EX Kernel? Flashing EX breaks wifi on this rom.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
You need to speak with FLAR2, this isn't my ROM, or my kernel so I cannot fix anything and as of now, no EX does not work with custom ROMs (I asked this same question to him last night). I also relayed this info a few pages back, for some reason, its not working with PD11 (or 10) but has worked on custom ROMs in the past. This is NOT a ROM issue, this is outlined by FLAR2 in his forum and is a kernel incompatibility with custom ROMs and EX kernel.

And I know and agree, it sucks EX isn't working with custom ROMs right now. EX has always been my go to kernel when I don't like the default ROM kernel. That being said, the kernel that comes with PD doesn't really need to be changed. It works really well with the built-in kernel.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ranasrule:
It doesnt stop charging at the set limit ie in my case 80%. I haven't made any changes to the kernel.