yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] marbertshere:
Is this a common thing? Not being able to get lte to work? I haven't flashed the rom yet
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] zminer123@gmail.com:
I can't answer that question

I wasn't able to find anyone else with the issue on this rom or any of the other AOSP roms I tried. Years ago I had a situation where the Google setup was failing to work, and I remembered that it broke data on my phone at the time. As a result, I surmised that perhaps it was actually the gapps package that I chose. Therefore I switched from nano to Pico to see if that solved the problem. It's solved the problem completely, and now my carrier settings work and I have LTE. Keep in mind that that's only on lineage though. I didn't get the opportunity to test it with this ROM because they already include gapps.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] XMayhem2099:
November goodies is out!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] krabban:
where ? cant find

found it, thought it was android 11.

so august firmware on latest?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] mingaldrichgan:
Nope, it's Android 10 with the November security patch.

https://aosip.dev/coral
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] krabban:
Ah understand. Good battery and standby drain on this?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] wrongway213:
ROMs don't really have good or bad battery - that's up to your usage mainly. A kernel can impact battery life, but unless there's some serious bug - a ROM won't boost or kill your battery life in any real, discernible way.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] krabban:
Yeah your right! I'm on another rom now and getting some high wakelocks in android system.

Clean install. Might try to factory reset and see if it will get better
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] mingaldrichgan:
I've been running AOSiP a long time on my Pixel 4 XL with no issues. That said, I'm never too far from a charger, especially during COVID times, so I'll admit I haven't been paying much attention to the battery and standby stats.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] CyberpodS2:
This is spot on with my own experiences also.

The only time I've seen roms kill batteries other than an explicit bug is either trying to pack too much crap in the bag (for example PacMan) which I guess is a bug in itself lol or some particular setting or app the dev included that is power hungry.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] mingaldrichgan:
Is anyone else having issues with the Camera app refusing to open on the latest build?

EDIT: Nope, nothing to do with the ROM. Still having this issue after clean-flashing the stock factory image.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] enndub:
Is anyone else having trouble updating google play system and downloading extra download for assistant? They both consistently fail for me. What factory image should I start from if I want to start from scratch?

Also, what's up with the Android 11 fingerprint?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ojessie:
Thanks for the December update
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
If this was noted in the thread, I apologize, I could not locate the answer before asking.

Can someone using AOSiP (this ROM for coral) confirm the kernel name that is shown (settings/About Phone/Android Version / 10 / KERNEL Version)? To me, I see DU's kernel (UnicornBlood) so I want to make sure I didnt screw up the MAGISK boot img and patched the DU kernel instead of AOSiP.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dragynbane222:
DU and AOSiP share the same kernel base, at least for 10, not sure what they are using for 11. What you're seeing is not abnormal and is how it should be.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Awesome, thank you! I also pulled a fresh boot.img and redid magisk with the same results but I appreciate the confirmation.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Where do you see the Android 11 fingerprint? None here (Android 10 is seen) but are you using props config in MAGISK to pass safetynet? If so, did you apply the wrong fingerprint? I use this ROM and Android 10's fingerprint is used, but I used props to force basic and used Android 10 fingerprint but even before doing so, I dont recall seeing 11 anywhere.

Google Assistant works great for me, pops up when I call it, and functions as it should.

This ROM is REALLY stable with good battery use (system drain), no bugs, reboots, nor any issues whatsoever (which is why I worried I applied the wrong kernel). The built-in kernel works fantastic (same as good as DU's kernel). I go back and forth between DU and AOSiP, but landed on this ROM (AOSiP) for the extra goodies that DU doesnt have, but they are BOTH flawless. AOSiP is my new DD and will probably remain so for the time being (unless I ever encounter an issue), which I doubt I will. I tested this OS pretty intensely.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
I posted this over in pixeldust forum as well, using the new safetynet fix you can pass safetynet again.

First thing I did was backup my SD (just in case), then I FULLY removed magisk (uninstalled), rebooted, installed the latest magisk app, redid my boot.img and enabled root. Rebooted then enabled magisk hide, and installed "safetynet-fix-v1.1.0.zip" along with props (only the two modules in my second pic).

I used the new safetynet fix with magiskhide and props config (using pixel 4XL with 11 fingerprint) with basic forced on my 10 ROM and it's back to normal. Screenshot shows the date and time (right now) with safetynet passed in the background.

You may not need to FULLY remove magisk but I did so because I was testing many modules so I didn't want to confuse things or worse, use a module that wasn't needed and isn't confirmed safe (I tried a lot at first and all found on random internet searches) so I felt it safest to wipe magisk data, delete all downloaded modules, remove magisk FULLY and start over safe and freshly.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] wrongway213:
Just a heads up, I can tell from you posting all this that you weren't sure so I'll inform you and anyone else who may be reading:

None of that was necessary. Flashing the modules over your existing setup would have been fine. There's no harm in you having started clean - just letting you know for next time you don't gotta do all that, & anyone else reading as well. Hope that's helpful 👍
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Yup agreed, I wasn't sure what was needed at the time and since I am also a dev, I did lots of testing/hacking with code changes so I wanted to get back to basics before I tested the latest method. I had tons of changes I made with numerous modules installed so I wanted the best chance of success with the least amount of changes made or installed to relay to everyone only what's needed. Once I cleared my device of all magisk, magisk modules, and code changes I made, I started over with just this 2 modules.

I'm sure I did overkill but I don't like leaving untested modules or apps installed so it was more for my safety because I forgot everything I did and installed.

Thanks for the clarification! (y)
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] 2WildFirE:
Any news about aosip? Can't found any Info
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dragynbane222:
It's still being worked on, seems they have the same philosophy as the devs behind the Elementary OS Linux distro (release it only when it's ready). Have patience.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Ejay Soe:
Need adb sideload both ROM and gapps?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
No, not if you are using the ROM version with GAPPs. The latest release on sourceforge is GAPP'd (and says it in the name), so this means GAPPs are included with the ROM install. This means you do not need to also flash GAPPs separately, so do not also install GAPPs after the ROM install or you will error everywhere with Google framework issues:

AOSiP-10-Gapps-coral-20210621.zip

https://sourceforge.net/projects/illusionproject/files/coral/AOSiP-10-Gapps-coral-20210621.zip/download
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Ejay Soe:
Thanks
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Ejay Soe:
I can't boot into recovery.

It is showing error boot prepare.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
redo the boot.img process to BOTH slots and try again (make sure you are using the right boot.img for the ROM):

fastboot --slot all flash boot boot.img
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dragynbane222:
No, there's a build with gapps baked in, and one without
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] AlexKarimov:
Recently flashed this on used Pixel 4(Flame) and I love the ROM but I've encountered an issue on both the non-GApps and GApps builds.

It started when I took the phone with me driving and plugged it into a USB-aux cable to listen to music(Pulsar music player). At first the phone played through its own speakers, like it wasn't plugged in. Upon unplugging and plugging back in, the phone played through the stereo as it should. Less than a minute later, it rebooted and stayed in a bootloop until I reset it with volume and power keys. The phone ran fine after this until I plugged it in and the same freeze to reboot happened again. With more time, I clean flashed both GApps and non-GApps builds and tested again. The error occurs on both.

Specifics:

Flashed image-flame-qq3a.200805.001.zip with corresponding bootloader and radio

Skipped setup and enabled USB debugging

Flashed AOSiP-10-Official-flame-20210621.zip per instructions in 2nd post

Rebooted to recovery and attempted to flash OpenGApps Pico but failed

Rebooted to system and boot TWRP

Pushed OpenGApps Pico to /sdcard and flashed through TWRP

Rebooted and set up phone. There were no random reboots until the aforementioned issue

At this point, I thought it was maybe the the GApps package or the way I flashed it and that's when I flashed the GApps build of AOSIP with the same result. I should note that the cables and Pulsar don't cause any issues on my rooted 4a so it's possible there's a flaw with this phone in particular.

The logcat is from the GApps build. I plugged the phone into my laptop and started Pulsar music player. I closed it once and reopened to find a blank screen and a freeze. The phone rebooted not long after and hung in a bootloop until I ended the log. The phone is not rooted.

If there's anything else I can do, please let me know. I'm going to flash a different ROM just to make sure it's not the device itself.

Thank you for all your work.

EDIT: I'm having trouble attaching the logcat. Hopefully this helps

Dropbox

www.dropbox.com
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] dragynbane222:
Logs would really help, without them troubleshooting is nl insanely tough. Should be able to get at least some of the log through adb shell logcat
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
My guess is the Google framework is screwed up, I cant reproduce it but looking at your log shows many Google framework crashing, then your media service dying. I wouldn't install the way you did, instead, simply download the GAPP'd version, then FASTBOOT the boot.img and boot off it, then ADB sideload the update (the GAPPd version). The issue you face seems like missing or corrupt Google required services, and you noted GAPP issues flashing it so it lines up in my opinion. I would clean it, and start over, but use the .zip GAPPd version, not the images. I do not feel its your USB interface but the Google framework crapping the media service.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] AlexKarimov:
Thank you for looking at the log. I confirmed it's not the device nor the cables. I've flashed two other ROMs and had no issues. You're right, there were a lot of errors in flashing the open gapps through twrp but the log is from the GAPP'd version itself with no apps disabled.

However, I'll clean flash and try the GAPP'd version again and report back. Thanks again.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
no worries, I used AOSiP ritually in the beginning (until 11ROMs came the norm) and never had these issues, so keep me in the loop and let me know how it goes. I only recently moved away (well few months now) as 11 became solid, stable, and bug-free otherwise I would still be on AOSiP 10 ROM.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] AlexKarimov:
I've tested again and was able to flash openGapps pico through twrp with no errors other than "unable to mount vendor" but even flashing the AOSIP-GAPPS ROM again, the problem still occurs. The same issue also occurs on another A10 Custom ROM that has GAPPS included but Stock A10 functioned flawlessly. All attempts were done after a clean flash and following the proper installation procedures.

I didn't reproduce a log because there's one in my OP with the same issue taken from the GAPP'd version of AOSIP after a clean flash. I have no idea what it could be but thank you to all who looked into it.

EDIT - To clarify: I flashed the no-GAPPS-AOSIP than flashed OPEN GAPPS. After the same issue, I clean flashed back to stock A10 and flashed the GAPP'd AOSIP with the same results.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Yes, I was also testing the latest version (both GAPP'd/non-GAPP'd) and I couldn't get it to boot. I tried to test for you to make sure it wasn't your process, and I don't think it is. I know because I follow the steps to the T and I am a dev, and at one time, baked ROMs for users on XDA, so I know how to follow steps and develop/install ROMs. I am only adding in that extra bit of info so you know I am decent with Android development and have been one since ICS years, so this wasn't a user error (nor do I think your issues were either).

After attempting a few times, they all error'd and wouldn't boot, and wouldn't go past the BOOTLOADER. It was error'd with "prepare boot failure" no matter if I used the stock boot.img, or pulled it from the payload (ROM/boot.img) using python, or even if I tried to just boot from the install/OS after a clean/fresh install. Every attempt failed with prepared boot error so honestly, I don't know what the status is right now of the 10 AOSiP. I haven't built, used, or run any 10 images or ROMs in a while so it might be the firmware we are coming from causing the issue, I am not sure. I did prep before the 10 install (AOSiP) by factory resetting the required version using a Google Factory image restore based on the required firmware level the ROM is seeking. I know this because its within the ROM itself, and found inside the METADATA under this location - AOSiP-10-Gapps-coral-20210621.zip\META-INF\com\android\metadata. Opening this file (attached pic example), shows the following 11 firmware is needed so this may be our hiccup (using the 11 firmware with a 10 boot) but IDK - coral-rp1a.200720.009

I will need to test more scenarios with using 10, 10 BOOT.img, and so on, but I also need my phone so I rolled back to ProtonAOSP (11) for right now. I will resume testing on this next week when I can rebuild my phone.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] AlexKarimov:
WOW! Thank you so much for all of this. I've experimented a little more to since the 4 is my spare/tester(daily is a 4a) and I had a few more results.

One more A10 Rom I flashed has the issue but the last one I tried doesn't. So, not slamming any ROMs or Devs but just in the interests of adding more info:

Issue happens on:

AOSiP(both versions)

DU

Pixeldust

Issue doesn't happen on:

Stock A10

Scorpion

EDIT: Don't know if it's related but something to consider is that I'm pretty sure the first 3 ROMs all share the same kernel. I don't know if it's the cause but there it is.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] GROOVYJOSHCLARK:
Nice findings! Yeah I would imagine its something along those lines of sharing the same base code causing them all to face the same issue, but what's the underlying issue, that's what I need to figure out.

I am on ProtonAOSP right now (11) so I cant test anything else for a few days with my work (I am on-call and cant risk it), but I will try to figure out whats up and going on with the 10s. I also suspect its the firmware level as most of us are on 11 base, so even though it shows an 11 base in the ROM METADATA, it might be the cause and we need a 10 base (IDK I am guesstimating here without factual data yet). I will test it later when I get a chance as AOSiP was always my go to DD for most of my devices (when available for that device) so I love it too and would love to run it again! I may build an 11 myself (if no one else does soon), but IDK if I have time or if the source is available. I would have to review/research and see whats there and what is needed.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ZG_DEV:
Thaaaaaaaaaaaaanks

Nice ROM bro
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xlxfoxxlx:
yes it does.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] kirschdog1:
Not working stops at 47 percent on adb sideload and reports as a payload timestamp error? Anyone actually have this running? Clearly an alpha that doesnt boot!
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Mackay53:
The problem isn't the ROM
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] chris_stan:
No problem for me

Alpha boot
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] shooterlgk:
Anyway to add screencast?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ZeroKool76:
If you're talking about casting via the hotspot, no, google did away with that option entirely on A10. They actually attempted it a few years ago via a google play services update. Their excuse was that a hotspot connection is not as secure as a standard wifi connection. But apparently enough people saw through that nonsense, so they brought it back. Looks like A10, they decided to put their proverbial foot back down and killed it off altogether. Thanks Google for telling me what's best ?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] shooterlgk:
I'm not sure that's what it is, I meant like to display ur screen to the TV? I've seen other roms with it it but on this one it's just like the stock rom on that feature. It don't have the option to enable
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ZeroKool76:
It's a quick tile as well, and it says it only works with wifi. Screen mirroring, that is. You can cast to Chromecast just fine though, if you just want to play media. I assume it would directly connect to a smart TV as well, but I can only speak to what I know works. Which rom have you seen with it? Now im curious which rom you're talking about that has it working.

---------- Post added at 07:59 PM ---------- Previous post was at 07:57 PM ----------

Oh snap, you actually just taught me something. I searched for cast in the settings section and that option you posted above popped up. Low and behold I am mirroring, noice!! Looks like you found the loophole ??
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] shooterlgk:
I seen it on dirty unicorns. I guess it works but not how it does on the other rom.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xlxfoxxlx:
will check into it never tried myself
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ZeroKool76:
it's in connected devices/connection preferences. It mirrors your screen just like the quick tile used to do. Tbh, I never even paid attention to this option because the quick tile always worked. So, thank you for pointing out a work around. I was actually pretty pissed to see that option removed, but this will work ?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xlxfoxxlx:
i have run and tested this for 2 months before posting it clearly isnt a rom issue but a following instructions issue
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] kirschdog1:
MOD EDIT: QUOTED POSTS REMOVED

You on latest firmware? February? Either way I'll wait until this is a beta or official but wondering what a timestamp error would be caused by. If anyone really knows what it is and isn't just going to say I'm the problem. Need clarification on what that error means?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] wrongway213:
February firmware is fine. Timestamp error means you are trying to flash a build timestamped prior to the build you're currently on. If coming from another ROM and formatting as mentioned in OP - no reason you'd see this error. Only time you should see this error is when trying to dirty flash an older build over a newer one.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] kirschdog1:
Thanks for the explanation. That's what I was looking for all along. Apologies to developer. No apologies to Kool for not helping.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ZeroKool76:
I don't need an apology, lol, I actually learned something myself. I always format before flashing the rom, so that's probably why i have never seen that specific error. But I still refer to what I said earlier, all things being considered equal, the simplest explanation tends to be the correct one. And in this instance, it certainly was not the ROM
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] wrongway213:
You're quite welcome. I do have to be honest though - [MENTION=6100315]ZeroKool76[/MENTION]'s explanation WAS correct. You skipped the step in the installation instructions right in post #2 - "Factory reset phone in aosp recovery" - had you followed those instructions you would not have gotten this error, so I do believe his initial reply was him being helpful, not trying to start an argument or mislead. Regardless, glad everyone understands what the error means and how to avoid it :good:
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] kirschdog1:
Any one help me turn off always on display? I can't seem to find it??
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] xlxfoxxlx:
There is a QS tile for it, not sure why there isnt a switch at the moment will get it added
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ZeroKool76:
There is a switch. It's called idle lock screen, under motion sense gestures. Just turn it to off
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] quinejh:
Not sure if this has been addressed yet, I briefly skimmed the thread. Has anyone on Fi been able to successfully use this? As soon as my project Fi gets installed it keeps stopping. And when I try to make phone calls it tells me sim not setup for voice calls.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] wrongway213:
You'll be good to go in coming builds. I raised the issue and Fox fixed it.I tested - Fi calling works with changes he's made and I assume will be good in builds to come
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ZeroKool76:
Thank you for the update, Josh. The updater app is working like a charm

EDIT: I think I may have underemphasized this. This is fukn epic!!! No longer tethered to a PC for updates is huuuuuge. Thank you so much
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Madjax2020:
good day all, is this an official release?
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] ZeroKool76:
Yessir. Honestly, I can't figure out why it's called an alpha, it's stable AF.
[Google Pixel 4 XL ROMs, Kernels, Recoveries, & Oth] Madjax2020:
thanks for the speedy reply, have you tested any other ROMS out for the P4XL? if so ... this your fav?