yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dd805bb:
Well this kernel or app. Only thing I did to actually get it to update was remove the boot.img with the kernel was flashed to by restoring the stock back up from magisk and reinstalling magisk. Same magisk version. So either ak3 is messing with it which both fk and ex use, or both kernels suffer from the same problem. No reflashing via fastboot. No sideloading from recovery. No manual anything. Just restored my back up from when I updated via factory ota via system. I was in awe last when it finally updated after I just restored the stock boot and reflashed magisk before rebooting. If it was magisk, it would not have done it at all because I still had magisk installed when it updated. And really doesn't matter to me. The app does what I need. Paid for that and the button mapper. Was really wary of even saying anything, but this happens last month too. It wouldn't update to September Google play system until I removed the custom kernel last month. But last month I removed a ton and repatched the boot from the September image. Stated fresh last month due all the bugs surrounding pie to beta to official. I figured it was that. Nope. Not this month. Narrowed it done to these two things. Hey but if it's easier to act like it doesn't exist. Cool. Have a good day. I know what I did different.

---------- Post added at 03:22 AM ---------- Previous post was at 03:13 AM ----------

Oh and I didnt remove any modules either this month. So not that either. Magisk was sinstalled and running when I took the update last night. Even have edxposed installed. I could see if disabled all the modules and it took them I would say it was just a module. None have even updated since idk when. Checked those too. Check magisk props because found that could stop it. Nope. I ran it all done for the last month. Chasing my tail. End of last month I got it to update after a few weeks of it being out. The security updated to September last month but not the Google play system. I didn't even think it was the kernel. I was actually running my own tests and realized I had no stock kernel tests, and that was the only reason I had the stock on there. I saw a notification about twenty minutes booting the stock kernel play system update and caught it installing. Then asked to restart. Search magisk documents for anything about the play system update. Nothing so I just restarted and the picture I posted is what I ended up with.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
If you're talking about an over the air OTA then you can't be running a custom kernel.

I download the factory image every month and install that. I just remove the -w from the install script to prevent data from being wiped.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dd805bb:
And you have a messed system. That leaves magisk in the boot slot you updated from. And also, no I am not taking about the ota. There is the ota and a day or two later a Google play system update happens. Should be two dates under the security tab in setting. One for security update and the other for goobel play system update. I know mine would disappear at times and would not come back until I restarted. Since not installing any custom kernel, no disappearing google play system update. I didn't know there was two different date until I saw in an unrooted phone. And wondered last why I didn't have the new date. This effects both custom kernels I use but I used them both threw exkm. So the answer lays in here....
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] flar2:
Again, I will reiterate, there is no connection between custom kernels and Google Play updates.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dd805bb:
I will wait. It seems and you can go ask Neo, every time I bring something up, it is months ahead of schedule. Every problem I have ever brought up on here, at first gets booed neyed and flamed. Then a few months later everyone has that problem. Twrp, brought every issue up that everyone is having at the beginning of the year before Android 10. Then 10 completely crashed it. Pixel 3 having different systems for different chipsets. Brought that up beginning of the year. Well now it seems people are catching on. Tjw even posted about the different systems for same phones. Pixel 3 xl uses two different ram chipsets... And I pretty much figured it out. Anything to do a certain dev I will not run, hack job city. Personally I would suggest losing the ak3 method and figuring out a clean way of flashing the kernel, either via magisk or a flasher outside of ak3. Android 10 is still new and has many bugs. But being quick just to dismiss has me like wow, you honestly believe without a doubt it can not be a custom kernel and or the tool used to flash it is beyond me. And I believe my first post was asking if anyone else had this problem. I didn't ask if it was this or not. I know it's this now. After removing this, exkm, and button mapper, posts of problems gone, resizing of font. The color shift from k lapse. Game glitching, gone. All kinds of issues I didn't notice due to this kernel but notice ce now after uninstalling. Go ahead and say again it wasnt this, I got a whole list of issues. This is was just the biggest problem. Like wifi issues on this kernel. Dropping lte and going to 3g in the middle of lte area. Been on lte since removing this kernel. So please tell me again it is not this. I can bring lists of problems.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
By dismissing the user above by saying that magisk is still in the boot image when using the flashall with -w removed, you've invalidated everything else you could possibly say about this device. Good luck out there [emoji106]
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dd805bb:
You have to uninstall magisk either restore boot or complete uninstall. Read magsik documents. What you said goes against what tjw has said about updating. It can cause massive problems. First step with taking an ota is removing magisk. So idk what you are saying but magisk has to be removed. Read documentation. https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation

Magisk can stay in even when doing flashall when removing the -w. It can stay sometimes when leaving the -w. Only two ways to rid magisk for sure is restoring boot image or uninstalling it completely via uninstaller zip.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
OTA and manually flashing the factory image are two very separate things. The boot image gets completely replaced by the factory images stock boot image. Since I never switch slots I have always stayed on the A slot, so your argument is invalid. Nice try though
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dd805bb:
Both do the samething. One moves over to the other slot, ota, and the other just rewrites over the the slot. Boot.img does not get deleted in either instant. So if the system doesn't even recognize magisk, it does nothing to it. Oem factory reset will not remove magisk. That wipes data. Flashall can leave magisk completely and totally intact. I have had it happen. On every pixel phone I have owned. Which I have had them all. Each one has its own tricks too. But magisk staying can happen using flashall with or without the -w. Oem doesn't recognize magisk. Root files can stay intact too past a flashall clean install without removing magisk first. This is not a new fact. That's why it is mentioned to remove magisk first before updating at all. Uninstalled zips wouldn't even exist if flashall always took care of magisk. There would literally be no need for it, why? Because a simple oem reset would remove it and flashall. But it doesn't.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
Prove it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dd805bb:
Prove what? An uninstall zip exist? Lol. Totally. Lol. Check out xda for while and read some threads. That is not not known what I said. After your first install of magisk, did it run an environment test and download a zip then reboot? You already had the boot patched right? Magisk just stays in boot right? Lol. Patching the boot only starts the process. But I am totally sure by your responses you can give the full break down what magisk actually patches and does. Patching the boot.img and flashing is the first step. The rest it does on its own..
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Piesie kwame:
Pixel 3 Android 10. HBM mode disables anytime phone sleeps. Please help
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bemagrp:
[MENTION=4684315]flar2[/MENTION]

I know my question is not related to this tread, just quickly, would you be able to support Pixel 4 XL? I know many of Pixel 3 Xl owners moved to 4Xl. And of course, another dinner coming from me in appreciation to your hard work;)

Thank you in advance
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] pahlerc1:
my two cents, is worth noting, that wipe my phone for every security update, which is monthly... sometimes i skip a month, but i like doing "clean" installs of the factory image to wipe my phone. i do a lot of customizing and installing a custom ROM, with root, so clean flashing the images every month help me keep my phone clean and up to date.

with that said, i have never used the uninstall magisk zip before running the flash-all.bat with the -w. not once. ever.

this is how i keep my phone clean and up to date. by running the flash-all.bat script when the monthly security updates are released. i flash it to both slots. my phone is always clean and magisk has never survived.

end of rant. i'm not the most advanced when it comes to this stuff, been rooting for years on years, but reading and following instructions has gotten me to where i'm at. and that's all i need.

flash-all.bat script wipes your phone, plain and simple. no need to use an uninstaller beforehand. i know from many experiences. we shouldn't have wasted our time on this clown who was replying to you, but thought i'd chime in my two cents and describe my firsthand experiences :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] mcg:
I am actually having a different problem with HBM, my phone's screen doesn't turn on after going to sleep. It seems to happen if I try to wake the phone in direct sunlight (ie. enough to trigger auto-HBM) and then it will stay black. It seems I can do inputs fine, ie. when I place my finger on the fingerprint sensor I feel the buzz, but any attempt to wake the phone via. button or fingerprint fails.

I have to do a power/volume reboot to get out of it.

For now, disabled auto-HBM and just using a pull down toggle. I'm surprised no one has brought this up yet.

Running P3XL on Android 10 Oct patch, 2.06 EX.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] flar2:
I didn't notice that because I had ambient display always on. I'll check it out.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] bleez99:
Delete
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ffchampmt:
+1 to the problem. I've actually had the issue since Pie, so like a year, but I always have ambient display off... Hmmm
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] flar2:
It's fixed in the latest 2.07
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ffchampmt:
Got the notification for the 2.07 update but the download fails (says I may have an ad blocker, but I don't). I also checked elementalx.org and it's still listing only 2.06.

Note: I appreciate you looking in to this! I'm excited to start using hbm again.

**edit - tried again after 5 minutes and it downloaded in app and flashed. Must have been a connection issue. I will get hbm back and test
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] belair56:
[MENTION=4684315]flar2[/MENTION] Thank you for the Pixel 4 Kernel
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jamiejames:
Thank you for the pixel 4xl. That was fast. Works perfectly.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] mmotorock:
I'm sorry but where can I read changelogs?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jamiejames:
Sorry to ask this on here. There isn't a 4xl forum started yet.

The 4xl has a bug that applies the wrong gamma table when turned off and on. Is this kernel related? If it is can it be fixed.

I'm really not understanding how Google let that slide. It looks horrible. Thank you for your time.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] iamjimmy:
Anyone know if EX 2.07 works with the November security update from Google? As far as I know, [MENTION=4684315]flar2[/MENTION] has not pushed out Nov update for EX Kernel. Thanks.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MrPepperino:
Newest update can be flashed via app. November is ready via app
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rob42ert:
Hi guys,

Pixel 3XL, Android 10(QP1A.190711.020), ELEMENTALx-p3-2.08.

I want to apply the latest Android Patch(monthly security patch) without losing anything.

1. I deleted the boot.img off my phone when "Files" cleaned all the unnecessary files.

2. Should I re download Android 10(QP1A.190711.020) and extract boot.img file? Then flash it using RESTORE in Magisk?

3. If I understand correctly ElementalX kernel should be wiped off. Then I can use OTA update to apply the monthly patch.

4. Reinstall ElementalX kernel using the boot-patched.img?

I am a bit confused on how the update process should happen. And I really don't want to wipe it off in the process.

Thanks.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tasneem khan:
https://youtu.be/4Nduxj7ry3o
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] flar2:
Maybe the easier method is to download the latest factory image, unzip, and remove the "-w" flag from the flashall script (removing the "-w" will ensure it does not wipe your data). Then reboot to bootloader and run the flashall script.

After this, you grab the stock boot.img from the factory image extracted above, copy it to your phone and patch with Magisk. Then flash magisk_patched.img in fastboot. From there you can reinstall ElementalX in EX Kernel Manager.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rob42ert:
The last update i did was before i rooted my phone in september.

Are you sure I don't have to use the september boot.img to restore? If my version is september, then if i get the latest firmware, november, then my phone will stop working.

Sorry for being a pain, is there a step by step tutorial please?:confused:

Thanks again.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] iamjimmy:
Please look at this guide here: https://xdaforums.com/pixel-3-xl/how-to/guide-pixel-3-xl-android-10-0-q-t3964117

This has a step by step procedure detailing what [MENTION=4684315]flar2[/MENTION] just mentioned.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TheGeekyNimrod:
Question: Is anyone using the wakelock blocker in the app? It's been way too long since I even thought about wakelocks. Any success using it or recommendations on which ones to block?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
These should be enough to block;

- wlan_wow_wl

- wlan_extscan_wl

- wlan

- qcom_rx_wakelock

- netmgr_wl

- DIAG_WS (If you now are plauged with this sucker)

:)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nht48823:
does anyone know if this Rom has a Bluetooth metadata working in the car? i have a factory Android 10 Pixel 3xl. I have not been able to get metadata to work since android 8.1. I have changed the avrcp from 1.3 to 1.6. nothing seems work. i use my old Nexus 5 with Android 8.0 for my streaming since i cant get my 1K pixel 3xl phone to work.

My Nexus 5 settings are:

AVRCP: 1.4

Sample rate: 44.1kHz

Bits per sample: 16 bits

Chanel Mode: Stereo

Pixel XL wont save the changes to the following setting in developers options.. only thing lets me save the changes is avrcp version, all the other setting keep going back to the default.

I really dont want to install a ROM on my daily phone but i am just annoyed that i cant get this to work, and google doesn't seem to be fixing this issue after 2 years into this. i am guessing all the google developers are using Iphone why they are not aware of this or they dont drive. plenty of threads on google related to this issue, but no solution i been able to fix this issue.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
How is this kernel been for people on Android Q - Nov update?

any random reboots, BSOD, etc? and relative to stock kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Porogami:
I was previously on Kiri but was experiencing random reboots and now on this kernel the random reboots don't seem to be happening but when I opened the camera and tried to take a photo the phone rebooted so I might just a problem on the Nov update
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Jiggs82:
Same here but no reboots while using camera yet but I never realized how fast this kernel is compared to kiri on my pixel 4 xl lol
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] flar2:
ElementalX is always smooth and stable, that's the point.

December update is available in EXKM
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
I agree . Ive been using elemental kernel for Nov. Very smooth and stable! No issues with camera, rebooting. Thank you for ur hard work! Appreciate it!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] KUSOsan:
Just got a pixel 3xl and flashed the Android 9 version and everything has been great so far. Scrolling has had no hiccups so far. Main reason I flashed it was for high brightness mode. Saw there is an ability to customise when you want the HBM to turn on which is nice. Thanks for your work ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Updated with December update on December security image.

Smooth sailing so far. Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] wangdaning:
I recently switched from a custom pie rom to stock November build. Wanted to test the kernel (custom kernels were not suggested on previous roms). I am unsure which version should go with the November factory image. Here it shows 2.06, but in EK Kernel Manager it shows me 2.09. 2.06 is October I guess, but is 2.09 November or December?

Used to use this kernel all the time, since Hammerhead, just haven't been caught up lately. Thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nullness:
2.08 is the correct version for the November update. 2.09 is for the December update.

https://elementalx.org/kernels/blueline/10/AOSP/ElementalX-P3-2.08.zip
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] wangdaning:
Thank you. I was looking all over the site but could not find a link to that particular page. It just kept showing the kernels hosed on androidfilehost...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] flar2:
You really should get the app, the project can't continue without support
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] pahlerc1:
2.09 is for December image. But I believe you can run the latest ex kernel on older factory image, I may be wrong but I think it's okay.

Hammered, Nexus 5 right? Ah the good ole days, bringing back memories of flashing rom after rom to get a feel for which I liked best and looking for differences amongst them haha
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] wangdaning:
OK, so the question is, can I run the 2.09 kernel on November image? I have the paid for app, and it is showing that as an update. I am guessing it is safe otherwise it would not suggest I update? Just don't want to bork my phone right now as it is my only payment method and my wife is out of town until the weekend.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] pahlerc1:
1- if you're that worried about your phone, only form of payment i would never update anything. especially if you have no access to computer to fix if you jack something up (rule of thumb)

2- YES i thought i just stated that in my last reply to you. The only time i don't think the updated kernel would work on a older google stock image is when say it is different versions of android software. So say you were on August security update (I believe is the last version of Pie) and you want to flash the latest EX kernel (which would be based on Q) that might not work out. But yes, November is Q, December is Q. I don't see why it wouldn't work. But that goes back to point one, why even bother with the update if you can't fix it if it doesn't work or messes something up?!

Just wait until the weekend or take the update. Not a life or death decision :p
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
On Kirisakura, several had issues flashing the December Kernel on top of the November base for some reason.

Typically I've never had issues with mismatching, but that's purely anecdotal, so ymmv.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
That's because Kirisakura also had dtbo updates that were incompatible with Android updates. That's why there's a check for which Android update your on.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] wangdaning:
Thanks, just wanted to confirm, as your tone previously seemed a bit cautious (I guess any type of flashing has risks though). I will wait until the weekend anyway.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] pahlerc1:
yeah always tend to be on the cautious side. sometimes i don't think things 100% all the way through and it bites me and have to flash-all with the -w and reset everything. but it's always fun. but if you don't have access to computer and its your only form of payment, yeah i wouldn't play around with that ;)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] wangdaning:
Want to report back that it worked.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Mangtas_666:
Question my pixel battery drains fast with this kernel but using kisakura it doesn't drain that much.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] wangdaning:
OK, but what is the question ;)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] KUSOsan:
How long have you been running the ex kernel? Also did you change any settings or just leave it as they were?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rockingondrums:
Well I searched and I'm surprised no one's asked: does this pass the bootloader safety net check? Sultan's kernel is long retired and that's why I used his kernel.

Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Pretty much all current custom kernels pass the bootloader check. That patch has been known for a long time now.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] suzook:
Off topic, wondering if there's any way to get HBM all the time on my pixel 4xl??? I have it enabled, but it turns off after screen is turned off, then back on.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 5.1:
Hello,

You know this is the 3XL forum right? ?

Anyway, if you use EX kernel manager, you can go in: Graphics and enable "High Brightness Mode" and tap the button on the right, so it survives a reboot... (Hopefully 4XL options are the same as the 3XL ones...).

Good luck...

Sébastien.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Mangtas_666:
The question is why it drains battery fast?

---------- Post added at 07:27 AM ---------- Previous post was at 07:25 AM ----------

I came from kirisakura..I have ex kernel for almost 2 weeks i drains battery faster.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] flar2:
It doesn't