yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Lessaj:
I have done the latter for quite some time but not the former, the zram to 2GB does make a good difference. Things are killed less often but still happens to apps you wouldn't expect in the moment.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Face_Plant:
The ZRAM Manager Magisk module was recently updated to v1.3, so here's another modified version similar to the one posted by [MENTION=1750044]dethknite[/MENTION] that sets the ZRAM size to 2048 and the compression algorithm to lzo-rle for those that were using it (like me).
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
Testing his Android Q kernel at the moment and it is really good. It's my understanding that it's not complete yet, so idk when he will release it. But, it will be worth the wait when he does.

Not sure if it was due to Magisk or what, but stock kernel had memory management issues and the battery life was far worse than expected. I had to reboot often when heavily using the camera app. It was like early pie release all over again. Tried another kernel before giving up on Q to wait to official release and it was better than stock. Figured I'd just tough it out. Luckily, got a chance to preview an early version of Kirisakura for Q and it has been smooth, best battery life so far for my use case, and no slowdowns. Thank you [MENTION=3428502]Freak07[/MENTION] for sharing your hard work.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Jiggs82:
Is there a link for this test Q kernel? ;)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
That's up to [MENTION=3428502]Freak07[/MENTION] to post, if he so chooses. I'm sure he'll post once he's convinced it's stable enough
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Jiggs82:
Oh ok lol well hopefully he will decide to release it to the public soon
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] matssa:
Best bet would be to wait until next week since official 10 will be out, including official kernel sources, it would be easier for him to merge everything correctly and avoid issues. Also, a bit better to test when TWRP is also released since bootloops aren't far ;)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] subzerillo:
I have installed this kernel (latest release) with Havoc OS on my pixel 3 xl. But there is something that is bothering me. The phone is turned off and I want to charge it that way (it charges a lot faster), but there is the charging icon that won't turn off. It stays on while I'm charging. I'm worried that it will leave a ghost image on my phone.

This problem is not related to Havoc OS.

How can I change that behavior or do I need to flash an older version of this kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
It’s caused by having magisk installed. It was the same on the pixel 2 xl.

Best thing to do when you’re rooted, is to not charge when the phone is completely shut down.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Face_Plant:
As stated above, your only option is to charge your phone while on if you want to avoid the battery image being burned into the screen. The issue with this is it puts a strain on the battery since the charger will be constantly supplying power to keep it at 100%. To avoid this I use an app called ACCA to control how my phone charges to limit wear on the battery. For example, I have mine set up to charge to 100% (along with a few other things tweaked), then it stops charging until the battery drops below 80%, where it will begin charging again. With my current setup I wake up in the morning with at least 95% left. In my opinion, having 3-5% less battery during the day is a worthy sacrifice if it means my phone's battery will last longer since replacing the battery isn't exactly easy.

XDA thread about the app (a former Magisk module):

https://xdaforums.com/apps/magisk/module-magic-charging-switch-cs-v2017-9-t3668427/page309

Link to GitHub where it can be downloaded:

https://github.com/MatteCarra/AccA/releases
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Just a note that this seems to be fixed in Q beta 6.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
Android 10 is officially out.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] BarryPooter:
I've been browsing the pixel 3xl thread a bit and noticed your problem. It is true that the pixel 2xl had the same problem. I would suggest using the latest Canary build. Install the canary magisk manager, download the zip through the manager and flash it through twrp like you're used to.

https://xdaforums.com/apps/magisk/dev-magisk-canary-channel-bleeding-edge-t3839337

Make sure you use the correct magisk unistaller zip to completely remove older versions of magisk first.

This fixed the issue on my pixel 2xl so maybe it will also help you out :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] asanta27:
So how does stock Android 10 compare to the latest Android Pie with this kernel In terms of day-to-day performance?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fuzzgruble:
What do you mean, specifically?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] asanta27:
The Pixel 3 and 3XL are notorious for performance issues. To the point that rooting and installing a custom kernel is almost a necessity (in my opinion)

I want to know if the performance/stability issues were addressed in Android 10. At least to the point that the devices aren't frustrating to use without a custom kernel.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
Imo with Android 10 Q the Pixel 3 XL is quicker/more stable than Pie, I'm playing with it in last 2 days and the performance seems pretty solid, anyway when Freak will release his CF I'll flash it without any doubts.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] tiny4579:
I have found the exact opposite. It was fine with later pie releases but awful on Q so far.

It gets so low on ram and starts killing play music or pocket casts and can get super laggy that it's actually frustrating. Not good for a $900 phone. Never had this level of issues on the pixel XL. I can get about a day or two before I have to reboot. Maybe it's better with pixel 3XL than pixel 3 but not likely.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
As for RAM management, we were quite a few to have issues (like killing play music) already on Pie and it seems to be due to recent Google Play services update.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
I am going to try flashing 3.4.5 to Android 10 and see if it works or not.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Don’t bother it won’t :laugh:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 21cdb:
Performance has been much worse for me on 10 compared to Pie with this kernel. Can't wait to get this kernel on 10 to make my phone usable again.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
He's working on it, believe me. Some unexpected issues came up that people would not be happy about
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 21cdb:
Oh for sure, I wasn't intending to come across as impatient. More frustrated with Google for making me take a step back from what I had with Pie. There are improvements I like, but performance hasn't been great for me so far. I even did a complete wipe and flash instead of just installing the OTA.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] tiny4579:
Anyone have any idea why they changed zram size from 1gb to 2gb? Looking at the source it was done back in December. Could be related to some of the issues, causing more swapping instead or just killing apps. Though it has an internal bug id attached so it may be related to a legitimate issue.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] crackers8199:
has anyone had any issues with wifi calling not working? i flashed this a few days ago and it seems pretty good, but today i noticed that wifi calling isn't working (t-mobile). had to reboot to bring it back...i don't remember this happening with the stock kernel. it just worked...even with it now saying wifi calling as the carrier, it seems to be hit or miss as to whether or not it actually uses wifi or HD voice for the call. again, with stock it just always worked...

happy to provide logs or anything else that might be relevant...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] evilryry:
I believe the kernel itself has nothing to do with that, it was probably just a fluke thing resolved by the restart.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] namura:
I too noticed battery drain was way worst. Previously I was getting 6 hours SOT but now I'm down to mostly 4 hour SOT.

I changed google.xml to allow google play services to be battery optimized. Will monitor and report back if there's any diffrence
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kylothow:
I love Google phones, they're so polarizing. You either have people with no issues (like me) with good battery, no lags or memory management issues (to the point this is the only phone I have kept stock+locked for more than a month in YEARS) or people that have all of the above and more. Sometimes if you go through some forums it seems like Pixels only got camera and the rest is all borked.

Sorry for the off topic, but I just can't wrap my head around how such a diametrically different experience is possible on the same hardware.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] melgar:
Same here for the battery drain.

For me it get´s better after updating Magisk to v19.4-087b451e.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] spe05081:
Thanking the developers

With this kernel (and AOSiP custom rom) I'm seeing a significant improvement in battery life.

I wanted to thank the developers and volunteers for their awesome efforts! :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
Can't wait for your touch on 10.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
So hopefully in the next few days I find time to release a kernel for Q :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gvsukids:
Any for pie?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] alpinista82:
Can you please enable the cryptographic api and ciphers (xts) needed for dm-crypt/cryptsetup? If you need more detailed info on how to enable this in menuconfig let me know. I am really missing the ability to decrypt my usbsticks when I am away from my laptop.

Cheers

Paul
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] -iNSiGhT-:
Can't wait to taste your magik... (using beta Q...so missing your kernel for a long time)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
[MENTION=3428502]Freak07[/MENTION] thanks man as always, I really appreciate your work and I like your explanations posts.

Anyway latest release keeps give me error during flash with EXKM
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I just tried it again with the particular upload and not with my local file, it flashed just fine via EXKM on my unit.

It´s probably best to report it to [MENTION=4684315]flar2[/MENTION]. [MENTION=4487388]jcmm11[/MENTION] had the same issue yesterday, but FKM worked fine for him.

Maybe take a screenshot of the flashing error so [MENTION=4684315]flar2[/MENTION] might have an idea what´s going on.

If you went from Pie to Q without completely wiping and used TWRP in the past, it might be related it might not.

Maybe try to re root via patching boot.img with latest canary and afterwards try to reflash.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
You can add your voice to here ?

https://xdaforums.com/general/paid-software/app-ex-kernel-manager-t3560850/post80258059
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] webleeper:
Same issue for me... Tried flashing the same download using FKM and success. Definitely an EXKM problem.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
Yep, with FKM the flash works, so definitely an EXKM issue, thanks everyone for the reply! ❤️
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gettinwicked:
Yes! I've been waiting for this for a long time since I went to Q! Flashed fine in EXKM for me. Everything is running great here so far!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] olivierke74@gmail.com:
How do we flash?Is there twrp for android 10?

Verstuurd vanaf mijn Pixel 3 XL met Tapatalk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] pangolin.rollin:
Flashed on crosshatch (latest q stock rooted), failed with exkm and flashed ok with fkm. All is working well. Thanks dev, you are appreciated!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Railey:
Thx Mate... [emoji1303][emoji51]

7TW02428CY665825D

Gesendet von meinem Pixel 3 XL mit Tapatalk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
Once you have root you can install Franco Kernel manager and flash the kernel with it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] -iNSiGhT-:
Few posts ahead :
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] stryker09:
Just got a random reboot while charging :/

Grabbed the ramoops, hopefully it helps!

No magisk modules or anything fancy running.

Tried ztsd, swappiness 175% is all I changed.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
The logs you sent me are all from the current running session I assume. At least they show a recent, only few minutes old successful reboot.

I need a ramoops, not dmesg or logcat in case of a random reboot.

But here’s something else, which might be very interesting for you:

I can tell from your magisk log that you’re affected from the bug I mentioned in my release post. Your persist partition is not holding all the sensors/calibration data in a proper way.

So you might want to try to restore your persist partition.

There’s an “how to” in the thread I linked. you might be able to do this without losing any data. Just give it a read.

I honestly think everybody that used twrp back on pie and updated to Q, without completely erasing the device is affected by this bug.

Twrp guys are working on it, so it doesn’t happen in the future.

I wiped my device several times when I started working on Q, so I never was affected.

Link for reference:

https://xdaforums.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
FYI to add to what Freak07 said I initially tried the method in that thread but it didn't completely work. What I ended up doing was: factory reset followed by installing factory image without removing -w.

My phone is now much happier, even though it was a pain to save everything and then setup again. I created a tar file for /sdcard. Saved my split APKs using SAI since Titanium does not handle split APKs properly, although you can use it to restore data - just not the app.

Edit: to check if this is what's probably the issue see if /persist/cache/ exists. If it does you'll probably find TWRP logs in there.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] stryker09:
Awesome thanks for the suggestion I might just do this instead.

Btw I use Swift Backup since it can handle split apks and backs them up to your Google drive which is great for clean flashes :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] -iNSiGhT-:
Does it affect phone on which TWRP has been installed or even if we just booted TWRP via fastboot ?

the "persist" folder should be at the root of the device ?

Thanks all.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nikhilnangia:
I'm the author of the thread [MENTION=3428502]Freak07[/MENTION] linked here: https://xdaforums.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904

A couple of us started having this issue and it turned out it was very widespread. Thanks to a few, we have a solution now, but it's a bit complicated. For more information, read the first post carefully - you can even fix your phone without losing any data.

To answer the previous poster's question: anyone who had TWRP installed AND made nandroid backups will be affected by this issue.

To answer the second question, you will find the persist partition in the following location:

root/mnt/vendor/persist

All these details are in the thread.

[MENTION=3428502]Freak07[/MENTION]: thanks, as always, for the kernel, man. Working great!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
Just to understand, I haven't the cache folder in /persist/ and I formatted the entire device before updating, and on pie I never flashed the twrp, just booted through fastboot. What I need to check if I've this sensor bug?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nikhilnangia:
Trust me, if you had the sensors bug, you would know: none of your sensors would work.

Still, just to be sure, here are the steps:

1. Open a root explorer

2. Navigate to /root/mnt/vendor/persist/sensors/registry/registry

3. Check if all files are >0bytes. If true, then you do not have the sensors bug. If a few files are 0bytes, then you have the issue.

If you or anyone else have any questions about this, please post them on the main thread we linked before. Let's keep this thread for the beautiful Kernel that Kirisakura is ;)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
Thanks for the explanation, very clear, I'm not affected thanks god, I was already contacting Google for a replacement ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] -iNSiGhT-:
Thanks [MENTION=7750470]nikhilnangia[/MENTION]

Doesn't have the cache folder. Registry folder contains a lot of files though, but the few i checked wasn't 0byte.

And my sensors are working well (at least proximity sensor and gyro).

I think remember i did a factory reset during beta Q (playing with root ending in non-booting phone).

Thanks again.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
I'll answer this and further comments should probably go to the sensor thread.

In my case I never installed TWRP, just booted it. I did make a nandroid though.

I have a symlink to persist off of my root directory, which takes you to /mnt/vendor/persist/
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fuzzgruble:
I also had a reboot while charging overnight. Here are all them logs.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Lagarde:
One more person with overnight reboot with ramoops. ALSO, had some force-closes of apps (Spotify, usually about 30mins into listening).

Edit: realized original sounded unappreciative and had to correct myself...kernel is running GREAT, but there appears to be an idle/charging bug rebooting it occasionally. Thanks for all the hard work!

Edit2: Massive battery drain and heat spikes today (normally is 30-34C, but with no apps running and screen off, it was running 39C). Can't trace it to any app. Phone glass is hot to the touch but was idle. Flipping back to stock kernel for now, but will be back once things look safer. :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dd805bb:
Dirty flashing doesn't work. I had an error flashing in exkm. I was on ex kernel. The ramdisk will not rewrite. Fk and exkm use the same flashing technique. AK3. I found before with exkm on q going back to stock kernel back up, I had to uninstall magisk, restore just boot, reinstall magisk so now it has a magisk installed boot.img with stock kernel. Then reinstall kernel. Just something I found. (And no I am not demanding anyone do this. This is something I found in my own experience I would like to share.)

---------- Post added at 02:48 PM ---------- Previous post was at 02:42 PM ----------

I brought this issue up on the twrp and root thread and was roasted almost a year ago on pie. Twrp was corrupting files in recovery. The power off charging logo issue is twrp too. I have a post about not using twrp and corrupting the ramdisk. Corrupting a lot of files, not just sensor ones. Careful, a few moderators don't like when people bash twrp. But there are issues when using twrp. Even if you had it install and never did a clean install, it is still in there waiting to go off like a bomb. Just saying.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jsauder2:
Reboot while driving and connected to car charger.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I listen to music very frequently and don’t have any issues with spotify. You can grab a dmesg with EXKM right the moment after spotify closes.

That sounds like your device runs out of memory and decides to close spotify.

The issue seems very widespread, but I have no idea why some people are affected by it and some not. The pixel 3 google forums are full of this issue.

Well yes I can see the kernel panic in both of your logs. It’s the same issue I “introduced” by merging Q beta 5 code in my kernel. So I’m pretty confident that the stock code is actually causing this.

The question is why is this happening for some, but not others.

I can do the same reverts, I did earlier. The question is now, why does this happen in the first place. It seems that it is caused by the stock charging driver and on stock code.

I guess I will compile a kernel with the same reverts I did back on pie to stop the reboot. The Q kernel hasn’t changed from the last beta release to the final Q release.

However I have a question for both of you.

Did you at any point jump from pie to Q without completely erasing the device? (like updating without having -w in the factory image)

I’ll post a new kernel hopefully later today. Please everybody with these charging issues, try it and report back.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fuzzgruble:
Nope, erased moving to q stable from q beta.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] SinisterXReaper:
I have had no issues, it's all been smooth sailing! I had no issues from both, a dirty flash from beta Q, to stable, and a clean flash. Stock Q, no modules installed.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] masri1987:
flashed latest kernel using exkm, what settings do y'all use on exkm anyway?

---------- Post added at 09:04 PM ---------- Previous post was at 08:49 PM ----------

happened to me too but didn't grab logs
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I´m done for today and it´s getting late :)

This kernel has some more updates, I´ll describe in the changelog for the next release.

If this shows no more reboots during charging for those who had issues, this might be the next release.

It includes the same reverts I did for 3.4.5, that fixed the reboots while charging. Since that´s code from Google, well hopefully it gets fixed, but some changes in my kernel seem to trigger an issue, the stock kernel suffers from too.

Please test the attached kernel and report back if you have any more reboots.

Good night/day everybody, see you tomorrow!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nikhilnangia:
Thank you! I wanted to report a few things:

1. For some reason, ZRAM doesn't stick on this one and disables itself on each reboot. Tried both EXKM and FKM. I moved back to the version you released yesterday and all is back to normal now and zRAM sticks.

2. Changing the advanced color settings and increasing saturation causes heavy color stuttering on Google Photos. Google photos recently made some changes about this, I believe. Perhaps some changes need to be made. This is also true for EX Kernel

3. I am aware this issue has been ongoing for a while now, but I do not know the reason (can someone please explain?) Whenever I change the ZRAM compression algorithm, it defaults back to lz4 upon reboot (both on EXKM and FK)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] brandonpa:
I flashes using Franco, exkm didn't work for me at all. I totally wiped when I updated. So far working for me, charged without problem. Have busy box, active edge and energized installed only. Otherwise stock