[ROM][Pixel 4 XL][11.0] [Clang 13] PixelDust Android 11 for coral

[GROOVYJOSHCLARK]

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!

Same here, I used PD on my Pixel 2XL, and now again on my 4XL, PD just works and works well!

 

[chopt51]

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!

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.

 

[Curiousn00b]

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.

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.

 

[chopt51]

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.

Wow, thanks for the tip! That worked.

 

[xChowderrrx]

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.

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!!

 

[fKm]

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!!

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.

 

[matt99017d]

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.

I look forward to it! I love running this ROM

 

[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!!

 

[WhiteReign]

When installing I get " Failed to read command: No error " did a clean install and everything.

 

[GROOVYJOSHCLARK]

When installing I get " Failed to read command: No error " did a clean install and everything.

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?

 

[WhiteReign]

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?

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

 

[GROOVYJOSHCLARK]

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

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*****

 

[fKm]

New build with march security update was pushed. No FCs or other problems after a short testing by me. Have fun.

 

[GROOVYJOSHCLARK]

New build with march security update was pushed. No FCs or other problems after a short testing by me. Have fun.

Awesome!!! I'll test shortly with a dirty flash!

 

[fKm]

Okay, still the DeviceHealth FC. Gonna check if I can iron that out.

 

[GROOVYJOSHCLARK]

Okay, still the DeviceHealth FC. Gonna check if I can iron that out.

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.

 

[GROOVYJOSHCLARK]

Okay, still the DeviceHealth FC. Gonna check if I can iron that out.

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.

 

[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.

 

[GROOVYJOSHCLARK]

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.

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.

 

[Darian71]

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.

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