[ROM][Pixel 4 XL][10_r41] PixelDust Android 10 for coral [05 August 2020]

[GROOVYJOSHCLARK]

FWIW, the 1/22 build of PD 11 has been rock-solid for me! (Granted, I've only been running it for a day and a half, but still...)

Good call, I am trying 11 version (latest PD) now, and so far, wow, rock solid! If it all works out, I will stick with 11 PD!

Ha! I love safetynet passes out of the box, I may change the fingerprint back to 4XL, but I might leave it. Running great so far but I will reply when its all setup and running (in case I encounter any issues) but so far, so good!

-EDIT, after a day/night of 11, I rolled back to 10. Not for ROM related reasons, but because of overnight battery consumption and warm device with nothing running. This isn't a ROM issue, I know this because I fully tested it BEFORE going to bed (but ALSO BEFORE installing and configuring everything, including kernel testing), so it was cold to the touch as well as normal battery usage. Later after configuring everything, and testing a kernel, overnight I was streaming Disney+ and it started to warm up, skip ahead a few hours and it was hot so I shut down streaming and rebooted but didn't start anything. It didn't cool down and the battery continued to drop with nothing running. This means I did something in my testing after it was smoothly running so until I sort out what I did that caused this issue (my own fault, again, NOT ROM related), I will remain on the 10 PD.

My best guess is an older app that I always use in my setup that isn't compatible with 11 and caused it wakelock. I will sort it out and get to the bottom of it. AGAIN, NOT A ROM (11) issue but my own doing so don't misread this as a bug in 11, its not.

 

[dragynbane222]

On the 1/22 build, I'm not sure if rcs is just being weird with sticking on verifying number, or of it's just broken on PD, I'll try and get a log tomorrow, fKm, haven't had a chance today to do so.

 

[fKm]

On the 1/22 build, I'm not sure if rcs is just being weird with sticking on verifying number, or of it's just broken on PD, I'll try and get a log tomorrow, fKm, haven't had a chance today to do so.

What is rcs?

 

[GROOVYJOSHCLARK]

What is rcs?

Google "Rich Communication Services" which is the live messaging (like an apple user texting another apple user), it simply shows live typing and stuff like that (but a lot more, this is one of the features). It works for me on 11 (this ROM) using Google Messages so I suspect Google had a hiccup (which happens all the time when I am setting up RCS), but wasn't a ROM issue. I know this works BECAUSE I used 10 and 11 of PD WITH RCS working and verifying on both devices. This is a Google issue most likely and will sort itself out in time, but NOT a ROM issue! I have this RCS verification hiccup happen every few attempts on multiple ROMs including stock 10 and 11.

 

[dragynbane222]

Google "Rich Communication Services" which is the live messaging (like an apple user texting another apple user), it simply shows live typing and stuff like that (but a lot more, this is one of the features). It works for me on 11 (this ROM) using Google Messages so I suspect Google had a hiccup (which happens all the time when I am setting up RCS), but wasn't a ROM issue. I know this works BECAUSE I used 10 and 11 of PD WITH RCS working and verifying on both devices. This is a Google issue most likely and will sort itself out in time, but NOT a ROM issue! I have this RCS verification hiccup happen every few attempts on multiple ROMs including stock 10 and 11.

Good to know it's likely just rcs weirdness

 

[GROOVYJOSHCLARK]

Good to know it's likely just rcs weirdness

No worries, I always have issues with RCS. When it fails to activate, I give up and wait a few hours. It usually does it itself in the background, or I need to reactivate it then it works. Is definitely not a ROM issue though, I tested both 10 and 11 of PD and both work. RCS is active on my 10 PD right now from this mornings rebuild.

 

[jubeilecu]

New build is up: https://www.androidfilehost.com/?w=files&flid=318615

Please test and report back. Latest stock image (Jan) is required.

Build installed and running OK.
Not big bugs by the moment, very smooth, nice battery life, Safety pass OK.
All working perfectly, Android Auto, Hotspot, Bluetooth, LTE, etc...
Also works three fingers gesture screenshot, dt2w, dt2s.

Some minors bugs:
Living universe wallpaper forces close if you chooses directly. You can set up anyway through Style & Wallpapers.

Other little bug, or maybe isn't, appears when you press power button and it shows the Google Home Control Devices. This screen should be opacity, but it's translucent.

Miss some features:
Always on display. I can't disable or at least i can't see the option to turning off.
Refresh Screen Rate: Same trouble. I can't see the option to force it to 90hz, even developers options.

I did clean install.
100% recommended.
Great work!!!

 

[jubeilecu]

Build installed and running OK.
Not big bugs by the moment, very smooth, nice battery life, Safety pass OK.
All working perfectly, Android Auto, Hotspot, Bluetooth, LTE, etc...
Also works three fingers gesture screenshot, dt2w, dt2s.

Some minors bugs:
Living universe wallpaper forces close if you chooses directly. You can set up anyway through Style & Wallpapers.

Other little bug, or maybe isn't, appears when you press power button and it shows the Google Home Control Devices. This screen should be opacity, but it's translucent.

Miss some features:
Always on display. I can't disable or at least i can't see the option to turning off.
Refresh Screen Rate: Same trouble. I can't see the option to force it to 90hz, even developers options.

I did clean install.
100% recommended.
Great work!!!

By the way, Rooted and magisk 100% funcional

 

[heocon77]

I cant find mosion sense in rom ?, hic

 

[heocon77]

and i can modify name to Pixel 4xl ?, thanks

 

[fKm]

I cant find mosion sense in rom ?, hic

It is not supported in A11 yet.

 

[fKm]

and i can modify name to Pixel 4xl ?, thanks

That is possible in settings.

 

[ryaniskira]

By the way, Rooted and magisk 100% funcional

Can you share your Magisk patched boot image please? I tried patching the boot image on the latest Canary but it's not booting for me.

 

[shiftr182]

Can you share your Magisk patched boot image please? I tried patching the boot image on the latest Canary but it's not booting for me.

You dont need canary anymore. Use stable.

 

[jubeilecu]

Can you share your Magisk patched boot image please? I tried patching the boot image on the latest Canary but it's not booting for me.

I'm not use canary really. Stable Version works perfectly at all.
Could you try by this?

 

[GROOVYJOSHCLARK]

Can you share your Magisk patched boot image please? I tried patching the boot image on the latest Canary but it's not booting for me.

as others said, use stable, no more canary needed and you shouldnt reuse someone else's boot.img, patch your own, otherwise you may loop. I use this ROM (10) with stable MAGISK and its rock solid.

 

[appro77]

Deleted.

 

[appro77]

I've installed the latest version of 11 and tried patching the boot image and flashing it several times using Magisk 21.4 but when it boots it gets to the lock screen and is unresponsive. I've tried both the Stable and Beta channels of Magisk.

My only option then is to go back to Fastboot and flash the original boot.img.

Any ideas?

 

[GROOVYJOSHCLARK]

I've installed the latest version of 11 and tried patching the boot image and flashing it several times using Magisk 21.4 but when it boots it gets to the lock screen and is unresponsive. I've tried both the Stable and Beta channels of Magisk.

My only option then is to go back to Fastboot and flash the original boot.img.

Any ideas?

Are you sure you are not patching the wrong boot.img, OR reusing any older one, OR someone else's? I only ask because this is the ONLY ROM I use (PD 10) as my DD (I test all ROMs but PD 10 is my go-to daily driver) as its solid! PD 10 is rock solid stable with ROOT and MAGISK working without any loops so its my go-to for stability and performance! I also want to point out, you are posting about 11 issues in the PD 10 forum, so I am not sure if you are somehow using the wrong boot.img (possibly from an 11 ROM) and trying it on the wrong OS-level (10 vs 11) or if its just the process used.

The latest MAGISK (stable) works without an issue so its either the wrong boot.img used, OR the process along the way got messed up. If you use the last 10 PD ROM, with the boot.img pulled from the 10 ROM, then freshly setup 10 Android OS (or 11 if using 11), then patch the boot.img from the SAME OS and boot.img pulled from the zip used to install the ROM with the same MAGISK installed into that ROM, then ADB and boot from the newly patches boot.img, it will work. This I promise you, but dont use anyone else's boot.img, or any other boot.img EXCEPT the one for the same ROM made by the SAME MAGISK installed under the running Android OS.

It WILL loop if you use someone else's, OR the wrong boot.img, OR you do not use the same boot.img made from the same running OS you just installed. What I mean by this is simple, EVERY TIME you rebuild the OS, make a new boot.img (from the ROM install zip) and patch that .img to the SAME OS you used to make it with (meaning dont reuse an older one or one made from the SAME OS but at an earlier time). ONLY make it with the SAME OS you plan to use it on, otherwise I have also had loop issues, it wasnt until I figured out that MAGISK needs the same boot.img it patched from the SAME running OS and not an older one, or someone else's. Basically what I am saying is do not take shortcuts, make a new boot.img and patch it on the same running OS as you plan to be ROOT'd and running with. Make sure to go through the setup first (Android), then install MAGISK, then patch a fresh boot.img, then ADB it and boot, and it will work, but only if you do it right without any shortcuts.

If all else fails, explain your install process of the ROM, then GAPPs (if using GAPP-free), then explain the MAGISK and ADB process so we can sort it out, but if you do what I laid out, it will work.

--EDIT, one other thought that popped in while reviewing your post notes, is KERNEL. Are you using 3rd party kernel? If so, try it without the kernel and use the stock built-in kernel to see if you can rule that out.

 

[appro77]

Are you sure you are not patching the wrong boot.img, OR reusing any older one, OR someone else's? I only ask because this is the ONLY ROM I use (PD 10) as my DD (I test all ROMs but PD 10 is my go-to daily driver) as its solid! PD 10 is rock solid stable with ROOT and MAGISK working without any loops so its my go-to for stability and performance! I also want to point out, you are posting about 11 issues in the PD 10 forum, so I am not sure if you are somehow using the wrong boot.img (possibly from an 11 ROM) and trying it on the wrong OS-level (10 vs 11) or if its just the process used.

The latest MAGISK (stable) works without an issue so its either the wrong boot.img used, OR the process along the way got messed up. If you use the last 10 PD ROM, with the boot.img pulled from the 10 ROM, then freshly setup 10 Android OS (or 11 if using 11), then patch the boot.img from the SAME OS and boot.img pulled from the zip used to install the ROM with the same MAGISK installed into that ROM, then ADB and boot from the newly patches boot.img, it will work. This I promise you, but dont use anyone else's boot.img, or any other boot.img EXCEPT the one for the same ROM made by the SAME MAGISK installed under the running Android OS.

It WILL loop if you use someone else's, OR the wrong boot.img, OR you do not use the same boot.img made from the same running OS you just installed. What I mean by this is simple, EVERY TIME you rebuild the OS, make a new boot.img (from the ROM install zip) and patch that .img to the SAME OS you used to make it with (meaning dont reuse an older one or one made from the SAME OS but at an earlier time). ONLY make it with the SAME OS you plan to use it on, otherwise I have also had loop issues, it wasnt until I figured out that MAGISK needs the same boot.img it patched from the SAME running OS and not an older one, or someone else's. Basically what I am saying is do not take shortcuts, make a new boot.img and patch it on the same running OS as you plan to be ROOT'd and running with. Make sure to go through the setup first (Android), then install MAGISK, then patch a fresh boot.img, then ADB it and boot, and it will work, but only if you do it right without any shortcuts.

If all else fails, explain your install process of the ROM, then GAPPs (if using GAPP-free), then explain the MAGISK and ADB process so we can sort it out, but if you do what I laid out, it will work.

--EDIT, one other thought that popped in while reviewing your post notes, is KERNEL. Are you using 3rd party kernel? If so, try it without the kernel and use the stock built-in kernel to see if you can rule that out.

Thanks for the detailed reply. I ended up giving up on 11 because I found bugs like the dialer not hanging up a call. That was enough for me to get rid of it as unreliable. I then tried to install 10 again by first flashing the Aug 20 stock firmware and then installed PD10 using the links at the start of this thread.

I had exactly the same issue as the first time I tried to install. The install got halfway through and then gave an error. I can't remember the exact error that was shown in the command window. I should have written it down. The phone definitely wouldn't boot. At that point I gave up for now and flashed stock and rooted it with Magisk no problem.

I'd like to give PD 10 another try because I really like the look of what I saw when I had PD 11 running. Unless I've done something wrong when installing 10 I'm not sure how to get it installed, given that my previous 2 attempts failed in exactly the same way.

Should I be flashing the Aug 2020 stock image and then using the links to the rom zip and boot image at the start of the thread as I have done on my previous 2 attempts?

Edit: It wasn't a slot problem because.....
fastboot --set-active=a or fastboot --set-active=b didn't help it to boot.