yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
Just for info, sorry for the off topic comment, but seems July patch fixed performance issue for me, it's more reactive and fast... big G says it fix some issue with Titan M chip, I don't know if it's placebo effect or a real deal, maybe that damn chip it's the culprit of the bad performance? At least the battery duration prediction in the settings as gain half hour ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
Yummy ?. The best of the best! ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gvsukids:
Last release is from June 25. So there's nothing new, but it's ok to flash on July?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] saxmydix:
You just quote the answer
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
I posted couple reply before stating everything is fine. I think I updated and test it right when they had July patch dropped. I guess no one pay attention to poor me.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Jiggs82:
So this kernel doesn't work on Android Q correct?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Correct
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Franco Kernel Manager is temporarily free

https://www.xda-developers.com/franco-kernel-manager-free-play-store/
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] glehel:
why do I not see the blockable items in the wakelock blocker menu? I'm using EX kernel manager. the other kernels show the items that can be blocked.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Face_Plant:
I believe that ability was removed from the kernel a while ago. I haven't been able to block anything for at least 2 months.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] melodystyle2003:
Hello @OP, I have one question: have you tried with your kernel to overclock display's refresh rate up to 65, 69 or 70 Hz and if so, how it performs? TIA for your answer.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fuzzgruble:
[MENTION=3428502]Freak07[/MENTION] Have you considered or looked in to lzo-rle as the zram compression algorithm? I know lz4 is currently stock but I understand there are some improvements to be seen with lzo-rle.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] fuzzgruble:
Got a reboot :(
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] luckana:
There is an app called Wakeblock, it works :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Face_Plant:
I know, I've been using it for a long time. It can't be used to block kernel wakelocks, though. The wakelock blocker built into EXKM was used for blocking kernel wakelocks rather than app wakelocks like Wakeblock.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Developer does not support wakelock blocking actively. It is his opinion (and mine for that matter) that blocking wakelocks generally causes more problems than it solves.

Issues related to the kernel that seam to be running away from you are likely derived from a bad app or mod, and that is where you should resolve your issue
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
It’s like you said. I removed that functionality since 3.0.0 if I remember correctly.

There’s only one reason to block kernel wakelocks. If there’s hardware incompatibility between the phone and another device. This will most likely cause your device to not sleep at all then. Which would be easily noticed.

never saw that on the pixel 3 at any place.

Blocking for example wlan Wakelocks to “improve” deep sleep will probably not improve your deepsleep at all. The wlan driver has way more than a few ways to get its awake time.

Plus blocking Wakelocks can easily introduce instability or other malfunctions like missed notifications etc.

I received one or two PMs with logs regarding random reboots. I’m looking at them, I’m just very busy at the moment, I apologize if I didn’t have the time to reply to you.

Overall I’m currently quite satisfied with how the kernel runs on my device. I still didn’t get a single random reboot yet :)

That said there will be a new release with Q preview 5 code merged and Linux upstream hopefully this weekend! :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Since preview 5 is also considered release candidate 1 does that mean we get a release candidate kernel to go with it ?? (ducks and runs for cover)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gnomish:
Loving this kernel.. thanks for the work!

Just reaching out to see if anyone else is running into issues with their screen not waking back from timing out when using 'high brightness mode' from flar2

The app itself works great, but if the screen times out, it won't come back on. Wondering if this is just my config or possibly the kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
I haven't used it in quite some time because of this
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] yosua_shtg:
Can someone take a ss from zram section in exkm..?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] acidspider:
If I can find it hahaha
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] newkydawg:
Is this what you want?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lssong99:
I concur! (then also ducks and runs for cover... Maybe huddle together?) Haha!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jlee08517:
Haven't noticed anything. But honestly I stopped using the app. It barely makes it any brighter than from the manual setting.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
After updating to latest canery magdisk I had to reflash the kernel in order for the touch to be working on screen. Just a heads up
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] yosua_shtg:
Yes sir, thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] hochoch:
Yeah. It's broken which sucks. Love it on a sunny summer day! Hoping it will eventually receive an update to fix this.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lohanchien:
I use Franco's manager to set high brightness mode and it works great. The best part being the Auto feature with light level trigger. Also, Franco's doesn't reset when you turn the screen off and on. It stays enabled. It works amazingly well and even though the brightness increase is not huge it does make a noticeable difference in direct sunlight.

The Auto feature is smart enough to not trigger when you set the brightness to a certain level but it uses the ambient light to determine if it needs to enable it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update to 3.4.0

Hey guys and girls,

So here is the next update for you guys. Got a little bit later but here it finally is.

The kernel is still made for Pie! It won´t work on Q.

I wish everybody a nice day/evening! :)

Changelog:

Kernel Base Changes

- Merge Q Preview 5 Code

- Merge 4.9.184 and 4.9.185

- use prebuilt Clang 9.0.5 from google

- add lzo-rle compression for ZRAM (this is not set as default, you have to change it yourself)

Important :)

All flashing errors are now fixed. If you experience the ramdisk error please take a look at the FAQ.

Have fun flashing and enjoy your device with latest linux-stable :)

Why is linux-stable important?

Download is below :)

Download:

https://www.androidfilehost.com/?fid=6006931924117918860

or following the link in the op to the correction version

Instructions can be found in the OP!

But look at this post too :)

Have fun, enjoy the kernel and your phone.

If you like my work please consider a donation.

Donations are not mandatory but very welcome.

If you like my work and want to buy me a coffee/green tea: http://paypal.me/freak07
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] muttonhead411:
latest kernel has been smooth so far. Thanks so much!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Cris7ianO:
Flashed latest version over stock (July build) and am using EXKM. Haven't tweaked anything major. Device runs really smooth. I am always charging the phone over night. As I woke up it had done a reboot in the night. Weird. Will have an eye on that.

Btw I am using Blueline Pixel 3.

Thanks for sharing your awesome work Dev :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lukefgoogler:
If we switch our ZRAM compression algorithm from the stock lz4 to the newly-included lzo-rle, what would we expect to see for our use case (Android in general, Pixel 3 XL in particular)? I'm not well-versed on the subject, but my understanding is that lz4 is very fast in both compression and decompression, basically blowing everything out of the water in speed but using a lot of memory to do it. Should lzo-rle be a big improvement for Android? I don't remember the specifics, but i think lz4 enjoys some of the benefits of having rle-like execution. If lzo-rle is better, why isn't it set as the default?

TLDR: "In Freak07 we trust", I'm no expert so I'm keeping the stock ZRAM settings absent an articulatable need to swap them, Freak does a great job optimizing stuff.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Mrcactuseater:
You should really just Google search for information so easily available. You're right in that lz4 is good, but lzo-rle should be better in a lot more use cases.

https://lkml.org/lkml/2018/11/21/637 more reading.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lukefgoogler:
I also had a reboot while plugged in & charging shortly after installing the kernel (I was in a rush to get out of the house in the morning tho, so didn't capture any logs :( ). I attributed it to the fact EKKM seemed to be having trouble switching my ZRAM from the stock lz4 to lzo-rle (I don't know how to do this thru terminal), so after it started up again I just flashed 3.4.0 again using EXKM and kept stock ZRAM settings. No reboots so far, smooth running as per usual

---------- Post added at 11:25 AM ---------- Previous post was at 11:15 AM ----------

Thanks for the great link, very informative. Makes a great case for lzo-rle (I saw some other good posts on LKML.org re. lzo-rle from that user, but not that one in particular), I'll probably switch after I figure out how to do it without using EXKM.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Put a script in post-fs-data.d

echo lzo-rle>/sys/block/zram0/comp_algorithm
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
I had 3 reboots with my phone on my wireless charger yesterday and another when I woke up (plugged into corded charger).

I was unable to get logs. I too am on the latest kernel and had tried changing to the new ZRAM compression, but couldn't get it to stick in EXKM.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Lagarde:
Had at least one reboot overnight with 3.4.0. Wired charging and idle for hours. If it happens at a time when I'm around, I'll grab logs.

I was using default zram and other kernel settings. Hadn't tried out the new stuff yet.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DOMF:
Three reboots here so far since flashing the latest. Also somehow my alarm sound changed which greatly confused me when I woke up this morning. Also, unsure of this could be related but now my stock headphones only put out sound if I hold down the button on them? Stock June update.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
How to make sure you can keep ramoops logs, even if you miss the reboot.

Create a script in service.d

logdate=$(date +%Y%m%d-%H:%M:%S)
[ -f /sys/fs/pstore/console-ramoops-0 ]&&{
mkdir -p /sdcard/logs/$logdate
gzip -9c /sys/fs/pstore/console-ramoops-0 > /sdcard/logs/$logdate/ramoops.gz
}

That will, if it exists, grab the ramoops file, compress it, and stick it in a sub-directory based on date+time under /sdcard/logs/
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Lagarde:
Brilliant! Thanks. Been looking for something like this for...well...a really really long time.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Just happened again this morning while charging

Ramoops

https://drive.google.com/file/d/1-Cu2XlzJRKWwDicJCHF9gHXDBWUCTbdR/view?usp=drivesdk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
I just had a reboot as well. Also happened while charging (inactive other than that).

https://drive.google.com/file/d/1z8fhrIBu11Ap9UtUgnhB8xxj10X2TSCz/view?usp=drivesdk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lukefgoogler:
I know this is supposed to be a developer forum, but I don't know to to make such a script, or where to put it. Would appreciate instructions broken down, Barney-style, for us novices. A million thanks if you can.... PM is fine too but I bet that there are others in my situation who might like to be able to post a log for Freak after their phone misbehaved and caused some overnight reboots.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DOMF:
I'm in that situation, but what I did based on cursory research was to create that file on my local system, named it "ramoops", did:

domf@parsons ~/android> adb push ramoops /mnt/sdcard
ramoops: 1 file pushed. 0.0 MB/s (195 bytes in 0.036s)
domf@parsons ~/android> adb shell
crosshatch:/ $ su
crosshatch:/ # mv /mnt/sdcard/ramoops /sbin/.magisk/img/.core/service.d/
crosshatch:/ # exit

...Did I do that right?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
[MENTION=9595880]lukefgoogler[/MENTION]

Here's a Magisk Module zip for saving ramoops to /sdcard

You can flash it via Magisk, TWRP, or FKM

I slightly overhauled the script, added checks to make sure that /sdcard is writable (which won't happen until the phone is unlocked). I also changed the location. You'll find the compressed ramoops in /sdcard/ramoops/<date/time>/

Here's the current script

#!/system/bin/sh
# Do NOT assume where your module will be located.
# ALWAYS use $MODDIR if you need to know where this script
# and module is placed.
# This will make sure your module will still work
# if Magisk change its mount point in the future
MODDIR=${0%/*}

# This script will be executed in late_start service mode
Loc='/data/media/0'

until [ $(getprop sys.boot_completed) = 1 ]
do
sleep 1
done

touch $Loc/testx
until [ -e $Loc/testx ]
do
sleep 1
touch $Loc/testx
done
rm -f $Loc/testx

logdate=$(date +%Y%m%d-%H:%M:%S)

if [ -f /sys/fs/pstore/console-ramoops-0 ]
then
mkdir -p $Loc/ramoops/$logdate
gzip -9c /sys/fs/pstore/console-ramoops-0 > $Loc/ramoops/$logdate/ramoops.gz
fi

exit

[MENTION=5185223]DOMF[/MENTION] - almost right. You would have had to modify the permissions to make it executable. You can delete that file and just install this. The checks to make sure /sdcard/ is writable are actually rather important ?

For instructional purposes:

All Magisk modules and scripts live in /data/adb/

For immediate purposes

/data/adb/post-fs-data.d

/data/adb/service.d

/data/adb/modules

These locations are also mapped to /sbin/.magisk/ and it's sub-directories. So when someone says to drop something into post-fs-data.d or service.d those are the locations being talked about. Scripts in these locations need to have executable permissions in order to run.

post-fs-data.d scripts run earlier (pretty much before anything else is loaded) and are blocking (other scripts, parts of the boot process have to wait until they finish) which is why a script there will be forced to end after 10 seconds.

service.d scripts are non-blocking and run in parallel to each other and the boot process. Always choose service.d when possible.

Each individual module can have their own script which gets executed in either post-fs-data.d or service.d, which is what I did with this module, which is why you won't see this script in /data/adb/service.d

To learn how to write scripts - well, Google is your friend. ?

EDIT: see fixed script 4 posts down (really stupid error on my part) (above script has been corrected)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
could those with reboot issues while charging, try this kernel and report back please? :)

[MENTION=3418824]MeetFace[/MENTION] [MENTION=4487388]jcmm11[/MENTION] :highfive:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lukefgoogler:
Wow, thank's so much jcmm11! Really above and beyond, the Magisk module was a brilliant idea for us uninitiated. Thanks also to Freak07 for his quick response, I just installed v.3.4.1
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
It only created empty directories, no file saved.

---------- Post added at 09:31 AM ---------- Previous post was at 09:29 AM ----------

After installing, booted, let it sit for a few minutes, set it on wireless charger, let it sit for several minutes, picked back up, phone was unresponsive, screen stayed blank for several seconds, then reboot.

I have a hunch it might deal with deep sleep while charging?

Here's ramoops

https://drive.google.com/file/d/1-DvxoDVuaH0t2jVbs5rtiSkFPSDl8Oh_/view?usp=drivesdk

Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
#@@$&++#!!;

When I changed the location from /sdcard/logs/ to /sdcard/ramoops/ I forgot to change the mkdir command.

You can either go into /data/adb/modules/ramoops_save/service.sh and fix the mkdir command (just replace logs with ramoops) or install the attached update.

I suspect you're right about the deep sleep connection. I haven't had another reboot, but I've been using the phone while it's charging. When it did reboot it had just been sitting for a while. I'll have to experiment a bit myself. Which means postponing installing Q. ¯\_(ツ)_/¯

Ok - XDA is misbehaving again and doesn't want to attach the file, so here's a link instead

Slightly updated version. Will place gzipped file in /sdcard/ramoops/

File name will be ramoops_YYYMMDD-HH:MM:SS_UTC.gz

https://drive.google.com/file/d/19iNuvOrsJItDaAyWou8B5F9M8w_Usmso/view?usp=drivesdk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
so the next one. everybody is free to test, but I´d be glad if you could report back.

If possible with a ramoops in case of a reboot please. Instructions are in the second post :)

[MENTION=3418824]MeetFace[/MENTION] [MENTION=4487388]jcmm11[/MENTION]
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
So far so good, charged for about half an hour, 20ish percent without waking up.

---------- Post added at 06:36 PM ---------- Previous post was at 06:35 PM ----------

And the new magisk module works great, thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] lukefgoogler:
Ditto for me. 3.4.2 seems to be working better, no reboots while plugged in. I have the new magisk module too, thanks again guys, you all rock!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
If the kernel is stable for everybody again, I’ll hopefully merge 4.9.186 today and soon release the next update then :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TheCelt:
I'm on 3.4.2 and had a reboot overnight while charging. Apologies, no log. Grabbing that magisk module so I can supply a log on the next occurrence.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Just charged mine up to 100% this morning, partly while using it, but mostly sitting. Still no reboots.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] evilryry:
Yesterday soon after flashing 42 I had to charge, I plugged in and walked off. Came back a few minutes later and the phone was asking for pin upon restart. Didn't get a log though, as I was busy. I charged today though and had no issues. Probably not valuable input, just sharing since this has been the topic of conversation lately.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
I had a reboot unfortunately

https://drive.google.com/file/d/1-EzJvE3_5h0fD0aPRSv4zcgHI60RO8IR/view?usp=drivesdk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] brandonpa:
Thank heavens I am not the only one with this. Woke up twice now with my pin request indicating my phone had reset. Though I was loosing my mind.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
Me too on 3.4.2 and as soon as I charge the phone it rebooted
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DvLAx3l:
For me the 3.4.2 seems work, I left the phone on the Pixel stand for all the night and it didn't reboot
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Hey everybody,

so here we go again. Next test is up. [MENTION=3418824]MeetFace[/MENTION]

If you get a reboot while charging, please share the console ramoops file.

It´s located in sys/fs/pstore and can be easily obtained with a file explorer or the magisk module in case of a random reboot.

Please also share your setup. Your rom, firmware, mods etc. (best would be to test without any mods)

Also if you use the stock wired charger or the pixel stand. Or any 3rd party charger.

thanks to everyone.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DOMF:
I installed this kernel, and upon booting the screen was completely unresponsive. It then rebooted. Here's the ramoops:

https://drive.google.com/open?id=1yc12yslMlzRByBTjbpiN4zzn0aELTv0O

Stock OS, Magisk 19.3/Manager 7.3.2, Magisk mods:

Audio Compatibility Patch

Audio Modification Library

ramoops
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] infamous84:
Audio Compatibility Patch

Audio Modification Library

What does the 2 mods above do?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Was anybody else able to run 3.4.3 posted above successfully?

Reboots while charging?

The log above indicates no kernel panic.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tekken Lord:
I have, so far, no reboot yet with my Anker wireless charger, running with AOSiP 7/22 build and Magisk mods: Busybox 1.30.1, Energized Protection, Input Power Control, Systemless Host, and Youtube Vanced.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
So far so good. I'll know better sometime later today after I throw a long charge on it.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Lagarde:
No reboots on 3.4.3 yet overnight.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] TheCelt:
No reboots on 3.4.3 here either. Charged phone overnight with no issues
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LunaticSerenade:
Worked overnight for me, no issues.

Stock, Magisk, Pixel Stand
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Freak, no reboots for me. 2 different 3rd party chargers and stock pixel stand.

Latest stock ROM, latest magisk, AML, BusyBox, v4a, activeedge, YouTube vanced

Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DOMF:
They were for making Viper work before I just gave up on it and decided to stick with stock audio.

No overnight reboots for me! Also, the latest kernel brought back my proper alarm tone.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
3.43 so far worked for me two different charger on stock. Latest magisk with busybox. Thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dethknite:
I, too, have had no more reboots so far on v3.4.3. :good:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jiexi:
Definitely restarted on v3.4.0 . Flashed v3.4.3 this morning. Will report back if there any issues. Thanks, Freak!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Face_Plant:
I ran 3.4.0 for a few days without any issues (no reboots or anything). Last night I flashed 3.4.3 anyways just for fun and it seems much better overall.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rspkt:
No reboots on 3.4.3 for myself also that I'm aware of. Definitely fixed the issues on 3.4.0 for me which had plenty while charging.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
Works great for me.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
3.4.3 has been stable for me on 4 different chargers.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
No issues with 3.4.3 here either
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] mgp53:
Are the kernel defaults what most of folks use?