yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] flash713:
I haven't had this happen. Not sure if it's a Verizon thing or not but I do know if you two can grab a log , start a log before you hang up a call and try and capture this behavior on log and post it, I'm quite sure the developer will check it out. If not it's just useless pretty much.. Not trying to sound like an asshole just speaking the truth.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] JLow0214:
So I installed the august build, now my screen never turns off. It will only turn black and only show the clock when I press the power button. It never fully turns the screen off. I tried every display setting and it still won't turn off. Also when I get phone calls it gets stuck if I don't answer the call and keeps ringing infinitely then if I try to decline the call it just comes back and if I try to finally pick it up it just goes back to the incoming call screen. I tried reinstalling the phone app and it did nothing. I did a clean install and yes I flashed the correct factory image first. Anyone have any idea if I can fix these problems before I try reflashing?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] flash713:
I've used all these Bliss builds on my coral and have never had anything like you describe here happen.

Just for kicks here's my install process:

Let's say I'm currently on Lineage 18.1 and want to flash Bliss...

1) Boot phone to boot loader mode

2) fastboot flash boot Bliss-boot.img --slot all

3) navigate to recovery mode using volume select it with power button

4) factory reset in recovery

5) adb sideload Bliss-xxxx.zip

6) reboot boot loader

7) fastboot -w

8) reboot system

On updates I do same process only I don't wipe data. If I'm installing a rom that doesn't have gapps after step #5 I reboot boot loader then select recovery mode, and do a: adb side load open-gappsxxxxx.zip. Then reboot system afterwards. The fastboot -w probably isn't necessary but it makes me feel better knowing my phones wiped clean.

I would take a wild guess and say maybe you didn't format data. Wiping data and formatting data are different. Maybe plug in to your PC and do a fastboot -w and reboot afterwards and see if that fixes anything.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
I think you accidentally clicked the wrong thread.

The power button issue, I'm not 100% sure on that one, could just be an unfortunate side effect of the flash, but the current build is definitely plagued with a Dialer issue.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I wouldn't bother any troubleshooting asuming you havent fixed it yet. Reset first using the factory firmware from Google directly, wipe data (erase userdata), and follow the process for the ROM install of your choice, then go from there and most likely you are golden again. this is of course assuming its not a device hardware failure, as long as you first factory reset using Google firmware, you will be back in shape.

I know its a pain to reset and rebuild the device to restore everything the way we like it (data/config/SMS/ETC), but sometimes its the safest (and quickest) method, rather than trying to undo damage thats unknown (since it truly could be anything at this point). If it were me, I would copy off everything from internal SD to my PC (assuming you have MTP enabled before this happened), then reset and restore your data. This is the safst and sure-fire method.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xFaultx:
Is there anyone else having an issue where the dialer will get stuck on hanging up? It doesn't happen to me every single time, but it happens pretty frequently. Essentially when hanging up a call the dialer will often times get stuck at hanging up showing the notification at the top of the screen. If I try to force close the app it just reopened showing the same screen indicating that it's trying to hang up on the call, and the only way to fix it is to restart. I can't receive any calls when this issues happening nor make any. Any suggestions?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] mostyle:
Yes, happens to me frequently. It's the main reason I had to leave this rom.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xFaultx:
-Deleted message-
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xFaultx:
Let me know if you find a good replacement. Im having a hard time finding one thats stable while offering at least some base level of customization. Call screening was something broke on several roms thats really important to me, as well as Android Auto support
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] debiansid10:
It's a very promising ROM! When we can get update build? Thanks
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] debiansid10:
Btw,pixel live wallpapers not working on latest build .
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ZG_DEV:
Downloading.....

I will test it in my friend's phone !
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] AOSPMaster:
Hello, I have this problem when I install August Factory image (on both slots) and then try to install PixelDust it says 94% ( Update Aborted, Error Code:KdownloadTransferError 9, I tried so many times and almost did everything, hope you can help me. ..
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
New build with some enhancements was pushed. Enjoy!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Thanks for the volume steps, that was all I needed to move to 11!

Just an FYI the download link is still to the previous version but if you edit the URL you can delete the zip and go up a level to find the one you just uploaded.

https://sourceforge.net/projects/pixeldustproject/files/ota/coral/PixelDust-Eleven-aosp-coral-user-20210205-1846.zip/download
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ceelos218:
Would i have any problems if i flashed a magisk patched custom kernel and dirty flashed a PD update?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
I don't think so. The PD stock kernel will be flashed again though.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ceelos218:
How would I maintain root without having to repatch?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
Not possible I guess. You need a Pc to flash an update so rerooting shouldnt be a problem.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fezzy102:
Can you accept dogecoin as a thank you?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
Hey, thanks for your offer but no one of the team has a wallet for doge coins. Feel free to spend some bucks via PayPal.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] neejay01:
Has anyone been able to build from source recently?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
What problem do you have?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Elyey:
Hello

I apologize for my question here.

Are you planning to release this ROM for the Pixel 5 or not planning?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Deliberate:
Hey just wanted to tell you this is a great rom! I've been messing with it off and on this morning and the only thing I can see that's a visual problem is the Google assistant at the bottom of the screen. While using active edge it doesn't show anything but it's still listening to you and does whatever you're asking it to do. Kind of weird just thought I should tell you. Other than that great rom. Thanks!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] neejay01:
"build/make/core/base_rules.mk:331: error: hardware/qcom/sdm845/data/ipacfg-mgr/hal: MODULE.TARGET.SHARED_LIBRARIES.liboffloadhal already defined by hardware/qcom/sm8150/data/ipacfg-mgr/hal."
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dragynbane222:
A apparently fKm is the only one not running into that, me and another dude on Telegram have run into that, basically gotta tell ninja not to build the sdm845 version of each library
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] neejay01:
That would be me lol I forgot XDA reset profile pics, I had mine matching Telegram and XDA. I was just curious if anyone else had the same issues you and I had (outside of Telegram).
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] cracky.ice:
Where is the switch of "Always On Display"
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] chopt51:
I had to turn it on through a tile in quick settings.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] cracky.ice:
My goodness, I'm so stupid, I spent days looking for this option and even tried to use ADB to control...

Thank you for stopping my stupidity
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Darian71:
Looks like a newer build since yesterday . Same date with a 2059 number. Appreciate all you guys! I got to test with a few others when A10 rolled for Taimen and now with my coral. So far so good too!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Same here, I used PD on my Pixel 2XL, and now again on my 4XL, PD just works and works well!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] chopt51:
Do you know if the google assistant 2.0 overlay is working? I'm on the last build and then you long press for assistant there is nothing on the screen, but I think it's still kind of working in the background.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Curiousn00b:
If you add a secondary language to Google Assistant that the newer one isn't supported, it'll use the older look correctly so you can see it.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] chopt51:
Wow, thanks for the tip! That worked.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xChowderrrx:
Aha! That saved the day! Thank you so much.

I've been using this ROM for about a week now, and I love it! It is so smooth and enjoyable to use. Though I did start noticing today that sometimes after a phone call, a process will stop responding. I didn't initially recognize which process it was and didn't have time to look into to it because I was at work. Next time I see it I will attempt to get more information and report back. Other than that and the assistant issue, this ROM has been a pleasure to use. Thank you all so much for your work on this!!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
This will probably be fixed in the next build. March update is ready but I don't have the newest blobs right now. Maybe I will push it at the weekend.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] matt99017d:
I look forward to it! I love running this ROM
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I finally moved to PD 11 as my daily driver (from PD 10), and I'm very pleased with it! I have been running it for about a week now and it's amazing! I was worried the battery life wouldn't holdup, but it does (once I disabled all start-up apps and services I don't care about). I'm getting really good battery life (1 day +17 hours give or take an hour or so) but that's REALLY good for an 11 ROM! I tested PD 11 many times but it wasn't until last week that I actually moved from PD 10 to PD 11 and I'm really glad I did!

Well done FKM!!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] WhiteReign:
When installing I get " Failed to read command: No error " did a clean install and everything.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Well without pics, or errors, or logs, its damn near impossible to troubleshoot. That being said, I went through a clean / fresh install just yesterday morning (post above yours) and it worked perfectly fine and without a single hiccup. I followed the steps to a T and it worked exactly as it should.

Have you tried a different USB C cable? Can you share your process, or logs, or errors, or a picture? Anything to help us help you more? Did you boot the boot.img, enter recovery, enable sideload, push the ROM exactly as outlined?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] WhiteReign:
I followed the steps to a T just as I did last time. I used 11.0.0 (RQ2A.210305.006, Mar 2021) and 11.0.0 (RQ1A.210205.004, Feb 2021) I am not sure why it stops at 47% every time with that error. I even downloaded the rom 3 times just incase it was from that
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
If you are using the latest found on SourceForge (PixelDust-Eleven-aosp-coral-user-20210226-2059.zip), then you need RQ1A.210205.004 firmware. I am unsure of what you meant with the March firmware, dont use March at all, its to high of a firmware for the current ROM release. Only the RQ1A.210205.004 firmware (unless the dev says otherwise). I always use and follow what is in the METADATA file (picture shows what I mean) if unsure (or if the right firmware wasn't specified, but it is in the OP). Again, you didn't give any info of the install process used or pic(s) of the error that would help me isolate what is failing for you and where/why, so I am guessing. This is what I do (after backing up EVERYTHING on the SD and MMS/TXT):

First I set the active slot to A

Run through the firmware with -w left intact (RQ1A.210205.004)

When it wipes userdata, I get ready and as soon as it reboots, I hold the power + up volume to interrupt and enter BL

Then I set active slot to B

Run through the firmware with the -w left intact (RQ1A.210205.004)

Once the B side is completed, I let it boot, go through a quick setup and bypass everything (Google account, pin,ETC). Then I reboot to BL, set slot B active, and flash the correct boot.img (dev recommended version and found on SF), enter recovery and ADB sideload the ROM.

I do both slots so I reset all partition table layouts on both slots, and by doing both, I know if theres an issue, I can use the other slot because its fresh. You dont have to do both slots (A/B) but I do and it works for me so I offer what works and has been tested thoroughly.

It sounds like to me, your failure is in the transfer which could be ADB, ADB drivers, USB cable, or failing USB port, any one of those could cause hiccups so I would reset the device (go through stock firmware with -W), then use a different USB cable, and make sure my ADB is updated and try again.

I am not trying to be argumentative with my questions or comments (lack of info), but trying to help you so let me know how it goes and dont take me wrong please. The full path to the METADATA file is this:

ROM.zip\META-INF\com\android\metadata

*****EDIT*****

FKM just released the March update, so what I said above is void now, use the March firmware. Apologies, it was updated as I was writing my reply so follow the OP.

*****EDIT*****
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
New build with march security update was pushed. No FCs or other problems after a short testing by me. Have fun.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Awesome!!! I'll test shortly with a dirty flash!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
Okay, still the DeviceHealth FC. Gonna check if I can iron that out.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I haven't gotten this FC on the 20210226 build (actually I get NO FCs). I will let you know if it happens under the March build.

Dirty flash worked perfect!

*****EDIT***** I did get a FC now on Device Health (but never have before) so it looks like in the March ROM it was introduced, at least to me and my setup.

I froze 'device health services adapter' with TiB and it's stopped without any issues so far.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I've rebooted 3 times, and not 1 FC happened with any apps. I do have with the device health driver app frozen (TiB disabled the system app). It's a working workaround in the meantime that hasn't caused me any issues that I've noticed.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Darian71:
I went into all apps and cleared storage on Device Health and Pixel Tips yesterday and had no FC warnings since. Checked data/system/dropbox this morning and no entries since yesterday on those apps either.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Try rebooting, I had it stable for a while as well (my original report was no FCs but I hadn't rebooted or given enough time). It was fine until I rebooted then it returned (until I froze the health driver). Since freezing the driver, no further FCs and I've rebooted a few times.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Darian71:
Yup. Started showing up again a few hours ago. I disabled it this time lol. Found a few short txt logs in dropbox if they'll help @fKm
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
The FC of DeviceHealthAdapter was fixed. Started a new build and will push it asap.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Awesome I'll test ASAP
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
New build was pushed and should be availible in the next minutes. Have fun
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Looks good, dirty flashed the latest (3/12) over top the previous dirty flash (3/9) and the FCs stopped. I defrosted the driver (TiB), and rebooted, and it hasn't returned nor any new bugs found or noted. Its running great so far with nothing to report!

Thank you and well done!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
New build was pushed. This time the kernel was compiled with proton clang 13 for more speed.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Cool, dirty flash still the recommended with the kernel change? I'll test as soon as I can but probably won't be today.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
Thats no problem. You can also only flash the new boot.img as there are no changes in ROM.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
It works great. I didn't even flash the ROM, I just downloaded the boot.img, patched in magisk, then flashed the patched .img using FKM (Franco Kernel Manager) while running the OS then rebooted (all done from my Android). All good!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Prey521:
Does adaptive charging & extreme battery saver work in the latest build? I've noticed that those don't work in Lineage ROM so wasn't sure if that's something that's common among all ROM's. I'm coming from stock and rooted 11.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
Tbh I havent tested.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I just tested extreme battery, it seems to work and also seems to work with apps you can exclude. I enabled extreme battery and it enabled, so it looks valid.

I cannot tell with absolute certainty that adaptive charging is working, but I think it is based on what I see. This is more of my best guess, than confirmed with logs or anything (so take it with a grain of salt)! If you have a method that you would like me to test regarding adaptive charging, let me know the details. I will test your steps (assuming you provide) and report back.

Also there is "smart charging" built-in that I do know works and is pretty much (in my opinion) the same thing as adaptive charging (with a few exceptions). Adaptive charging for the Pixel line actually uses alarms, so overnight it charges based on alarms, whereas smart charging, simply keeps it from overcharging, and once the threshold is hit, it slows the charge (or stops the charging process). They do similar things, and I prefer smart charging over adaptive (even on stock when testing 11 stock), I prefer smart charging because it goes off the battery level, and not stupid alarms as Adaptive does. Using alarms set before 5AM and having to plug in after 9PM simply doesn't work for everyone and that's the adaptive charging requirements to work.

I know Google tried to match Crapple's battery charging protection features used in iCrap devices but they failed in my opinion. Adaptive charging requirements do not work across the board so it's a flawed attempt and why I only use (or care about) smart charging which DOES work:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Cememer:
Is this rom support FeliCa?

(FeliCa is the Japanese standard for contactless IC cards.)
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] fKm:
Try and tell. I can't test that.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Ulyaoth:
Just flashed the latest build. I got the device health services keeps stopping message as soon as I booted. I was on the build from last week or so, I just downloaded the latest one, flashed the boot.img in fastboot, dirty flashed the rom in recovery, flashed the magisk patched boot.img in fastboot.

One difference I noticed was that after I flashed the patched boot image, on the first boot, the device restarted mid-boot and when it booted it wasn't rooted(I assume it used the other boot partition), so I just flashed it again. It then booted fine.

As I was writing this I also flashed the kirisakura kernel. I got a bootloop which didn't happen the 2 other times I flashed it with this rom. It booted fine after a soft reset. My kernel manager reports the kernel I installed, kirisakura 7.1.1. Device health services keeps stopping still. I cleared its data, and will disable it if it keeps stopping.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Something doesnt line up, the device health adapter FC was fixed, so are you sure its the absolute latest version (PixelDust-Eleven-aosp-coral-user-20210313-2306.zip) released 2021-03-14? Also I have had it reboot during the initial ROOT boot first time. I cant help with other kernel (3rd party), but I used Krishna and EX myself, both I felt didnt work as they should but I dont know why or have more information. All I know is during "live boot" (which shows to boot logs), when using 3rd party (krishna or EX), I would have timeouts and crashes in the boots, so I rolled back to the default kernel and was fine. I found I also had WiFi and signal issues with other kernels but that doesnt mean they dont or wont work, they just didnt work the way I wanted them to for me, so take what I say with a grain of salt.

As for the missing ROOT, did you accidentally switch boot slots while in ADB? You shouldnt lose ROOT if you patch default boot.img in MAGISK, then load that patched boot.img.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Ulyaoth:
I'm not sure about the missing root but I got over that at least. It might be a good call going back to the default kernel, I'll try that. But I'm definitely on the latest versionof the rom, and although I will say the "keeps closing" dialogues aren't as frequent as before, they are definitely still there.

Should I look into giving you some kind of log?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I think that's different and why I didn't get it, I believe you can uninstall that from settings

I just rebuilt it this morning coming from scorpion testing, I don't have that issue and I didn't change the kernel. It's default so restore stock and see if it helps. I have no FCs. I also had issues with the service health adapter, not services.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Ulyaoth:
What's different? You mean the kernel? I got fc dialogues even on the first boot with the default kernel
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Something is wrong then, I followed the steps to the T and I do not have any FCs. Did you install GAPPs with it by accident? Or magisk modules, something is off. I only run root with patched magisk but no kernel or modules or anything else, just user apps from the playstore.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Ulyaoth:
Nope, I followed the exact steps I mentioned. And it actually just got more frequent lol, I'll probably disable it again.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] shiftr182:
I'm rooted with viper, and a few other magisk mods. No issues. No FC's.