yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
Thank you, this is what i just did

noted for next time!

Of course, 100%. Just flashed the stock boot.img to both slots, fastboot booted twrp, flash twrp again, then flashed your kernel and magisk, and all seems to be working as planned

Thank you all!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I´m about to release 1.5.1, flashed it via FKM app and I kept root. Just choose the file, and to reboot directly afterwards.

[MENTION=5260103]Sevael[/MENTION] yes you´re right. That´s why I would like to know what´s happening. I tested via TWRP, EXKM and FKM and I always kept root just fine.

If you flashed the boot.img, booted to TWRP to flash Magisk and the kernel.zip all in one session without a full reboot before flashing my kernel.zip after flashing stock boot.img + magisk zip that´s why you "lost" root.

There is no need to flash stock boot.img before flashing my kernel. only flash boot.img if you face issues.

Flashing stock boot.img plus magisk afterwards in twrp needs a reboot. Then flash my kernel zip wherever you want to and root should just preserved.

Just to make this absolutely clear! If you would have flashed stock boot.img, boot to TWRP, flash my kernel.zip plus magisk afterwards you would have been rooted. But for Root to be preserved you need one reboot after flashing magisk!

could you do me a favour? make sure you´re properly rooted with magisk and maybe tell the magisk version you use.

Then download 1.5.1 which soon drops and just flash it in twrp. Afterwards save a recovery log in TWRP and post it in case you lost root again.

Don´t restore stock boot.img or do anything else.

To Everyone,

Thanks for all the posts guys! It´s great to see the kernel got some traction here! We will get it figured out what´s happening here! Thanks for all your support!!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Dacian97:
Hey, I flashed 1.5 earlier today with twrp and flashed magisk 17.3 right after then rebooted. I was Alg. With 1.5.1 I was curious and tried flashing it with exkm, rebooted right after. And I lost root.

Not sure what's the go, I linked my logs from twrp, if that's any help to figure out what's going On. I don't mind, I'll just flash magisk after from now on.

I was on magisk 17.3 before, and 1.5 of this kernel.

https://drive.google.com/file/d/1hgyFonDMKn7K1MPO1UFffAB9zx2aYnta/view?usp=drivesdk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] _LLJY:
There are some issues, namely

1. I would rather trust Google with EAS, I wouldn't merge anything from CAF unless it's really necessary, CAF isn't exactly known for quality code

2. Just follow bluecross kernel from Google as Google will pick changes from CAF only if they deem it necessary

3. Although I like the idea of cpu_input_boost, we already have a powerhal that boosts cpu frequency according to userspace hints. Boosting it on pixel launcher is not very useful on our pixel 3 since we already have a rather aggressive interaction boost from the powerhal.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I need a recovery.log not a kernel log...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
everything was set the same (max cpu, iosched default to CFQ, fsync on and off two tests, and no encryption and one with encryption)

ran androbench 3x on each and got the average.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Dacian97:
https://drive.google.com/file/d/12nZBpUV_G3yJLlibWY2ZNJ10-3jWHFFd/view?usp=drivesdk

Oops
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
1. If the EAS implemenation from Google would be closer to ARM´s EAS implementation I would agree. However as I see it currently Google decided this time to base their EAS on top of CAF. As long as there are no fundamental changes which may conflict, and testing isn´t showing negative results I happily merge CAF updates in. If Google decides to go a different route I can always revert the CAF updates and follow Google :)

There is always the possibility to maybe change the EAS completely to ARM´s implementation in the future! For now this performs very good for me.

2. Carefully merging in selected CAF changes (as was done for example by [MENTION=6842057]nathanchance[/MENTION] for his Pixel 2/Xl Kernel and my Pixel 2 XL kernel) can improve the kernel if properly tested.

Additionally this time around Google based their kernel heavier on CAF as done in the previous years.

https://twitter.com/nathanchance/status/1053896927631167493

https://twitter.com/nathanchance/status/1053896928948191233

https://twitter.com/nathanchance/status/1053896929975750656

3. Powerhal boosting the minfreqs is disabled via this commit. Powerhal now boosts only top-app stune boost to 50. That in concunction with cpu_input_boost is exactly what I want currently for this device to retain the smoothness :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
the recovery.log was not while flashing my kernel and loosing root wasn´t it? I don´t see my kernel flashing in the log.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Dacian97:
Sorry, how would I get the recovery log for it if I'm using exkm to flash it ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
What custom rom are you running? If you don't mind me asking
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Mawtin:
Personal rom built himself
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
Man there is some wicked development going on here. [MENTION=1037050]freak7[/MENTION] thanks for sharing your hard work! Q on [emoji3050] Amazing!

How's that for an update? Pretty darn quick if you ask me! [emoji6]

If you like his work there is a link to donate on the kernel releases. Just saying [emoji112]
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kaicat:
Getting good performance and good battery life in the latest version on AOSIP.

Nice work thanks you:svetius:

---------- Post added at 01:51 AM ---------- Previous post was at 01:26 AM ----------

One issue is that I need to reflash the magical after installed the kernel
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] acidspider:
Any one recommend any alterations to the default settings for this kernel? Or best settings are already default? (Pixel 3)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
[MENTION=3428502]Freak07[/MENTION] already said two or three times that he put the best settings as default.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
nvm.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] yung40oz84:
I know you did not get Zram writeback to work but for PSI would it be possible to create a flashable zip for stock PIE that would give us this benefit? That may have been what you meant by the patch set, lol.

The kernel I have been running since you dropped it and I have not had one single issue at all.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
2.1.0 is smooth af! Good job [MENTION=3428502]Freak07[/MENTION].
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
I am on stock pie running latest kernel. Very good here ??
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
Did you flash it through Twrp, EX kernel manager or FK manager?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
Exkm.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
EXKM, just flash zip files
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] -iNSiGhT-:
I flashed through TWRP (i only boot TWRP, not installed. But the result should be the same).
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
And, just to finish it off, I used FKM. I've also used TWRP at times (booted, not installed). They all do the same thing.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rspkt:
Installed the 2.1.0 kernel via TWRP 3.2.3-3 directly over the old 2.0.14 kernel with no issues. The device definitely does boot a bit quicker than before and other than that everything seems to be smooth and running well. Thank you again, [MENTION=3428502]Freak07[/MENTION].
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
I just updated to 2.1.0 with ExKM easily too.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Announcement

2.1.1 which has 4.9.164 (released a few hours ago) included will drop soon :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xFirefly93:
No Q DP1 kernel ready for us die hard tinkerers? :p
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
So with kernel 2.1.0 on stock rom, with many stuff disabled that I don't use. I am losing battery very fast. I have magisk 18.1 installed.

If I use phone, I lose 2-3% within 10 minutes. And I use phone for basic stuff, texting, email. I have location services off, bluetooth off. Not many apps installed either. No social media apps installed.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
You can always do a reboot. Sometimes it's enough.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
I did a reboot several times :\. The phone is smooth though, no more lagging.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
I have ~8%/hr active drain on 2.1.0 so it's probably a rogue app?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] yung40oz84:
I haven't really found another kernel to give me battery comparable to stock, so I'd say you probably have a rogue application or something else going on. I always do a full wipe when I face issues like that. Then if it is still happening after that, get a battery monitor app and find the rogue application sucking battery.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
I did a full wipe. Literally deleted everything from TWRP. Then flash-all march stock with wipe. installed Magisk v18.1, then this kernel. No apps installed but ad away and magisk tbh. I have dark mode enable in whatever stock rom allows.

Can you recommend which battery monitor app is good?

I only have stock apps :\. It is strange.

Maybe dark mode and night mode enabled is causing drain?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] codygs83:
What monitor app are you using?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] joetheshmo:
Exkm
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Hey :)

As the others said it’s probably not the kernel. I’m getting really good battery life too.

Best app to find rogue apps or possible cause of drain is better battery stats. You can find it here on XDA :svetius:

I´m not using Q. Since there is not root, what´s there to tinker with anyway?

With patchset I meant a range of commits custom ROM maintainers can merge and include it in their builds. Maybe there will be a flashable zip at some point, but I´m tight on time so no promises on that front.

I just checked the Q source again, and it seems ZRAM writeback is enabled in the kernel, but the ROM side implementation is actually missing in the Q source.

I tried to implement ZRAM Writeback directly from Googles master branch (not Q branch) into a Pie custom rom but all I get is a crash after boot up for now.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update to 2.1.1

Hey guys and girls,

As announced here is the kernel with 4.9.164 included!

Have fun flashing and a nice day everyone :)

Changelog:

- Linux-stable bumped up to 4.9.164

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?

I wish you all a nice day/evening!

Download is below :)

Download:

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

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: http://paypal.me/freak07
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
I don't know if it could be kernel related but FK Manager won't update from the Play Store to the version 4.0

Anyone else facing that?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
Does the new update address high battery drain?

I installed another kernel, and no such high battery drain. I did thorough checking, there is something in kernel 2.1.0 that is/was draining battery very fast.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] smartymcfly:
Updated just fine for me.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
I updated with no problem. Whats the error you're getting?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
Yep, the changelog clearly says "fixed high battery drain that nobody is experiencing but one who has no idea what the cause is but has nailed it down to...something".

I'm kidding... But it's odd you asked that after [MENTION=1037050]freak7[/MENTION] responded. Your kidding too, right? [emoji23][emoji23][emoji23][emoji23][emoji23][emoji23][emoji120][emoji120][emoji120][emoji120][emoji120][emoji120]
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
flash through exkm and all is good.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
That was strange. Don't think it's explicitly the kernel but I just had a hard reboot. Ramoops attached.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] youlun.zhai12:
Same here. I've faced hard reboots three times after upgraded to 2.1.0. :eek:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] yung40oz84:
So you have the commits for DTS headphoneX and DTS Ultra to work from here?

https://gitlab.com/dts_project/intro

I checked GitHub, it's just hard to tell and find the commits, lol.

Thanks!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Golf c:
Really, don't want to add more crap
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] yung40oz84:
You are just a user correct? Your opinion is fine, but please research before you call something crap. DTS is definitely not crap. Also, are you trying to say there is too much crap in this kernel ? Because you said anymore... The point of this kernel is to be diverse I believe. That's why it contains so much "crap", lol. Anyway, it is only a few very simple commits and brings very great sound experience to the user. Lastly, it doesn't affect anyone unless they actually flash the zips to install either DTS HeadphoneX or DTS ultra, so it's not really a losing situation for anyone.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] yung40oz84:
I had a reboot when I was scrolling through Twitter, and I'm not sure if it's kernel related or Twitter related, lol. I got the console ramoops and last kmsg to examine. I have no clue how to read them ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] elitewarrior:
[MENTION=3961342]gvsukids[/MENTION] which version of Magisk are you using? I can't get google pay to work :(
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] 93ae8074:
Sadly, is happening to all of us lately. Nothing to do with the kernel, tho.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Bryanx86:
Nevermind
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] c_86:
Search

https://xdaforums.com/pixel-3-xl/help/gpay-tell-root-t3910767/page3
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
It thinks a bit at the end of the download and it gives the generic error like in the screenshot.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
My Chinese isn't that great, but I think it translates to "your phone is in wrong hand" or "your phone upside-down" but there isn't a direct translation.

Have you asked the dev? He's very helpful and is a pleasure to work with. App installs fine for me.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
I assume you did "try again" ?

2 things I would try. First try deleting data and cache from Play Store. If that doesn't work I'd take a backup of the existing apk (maybe take a nandroid of the data partition as well), uninstall FKM, then try installing the new version from the Play Store.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
I de systemized the app and the update worked.

Thanks for your tips. :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] shreyamt:
I don't know if this is because of the kernel, but I only started experiencing this after I installed this kernel. I'm on v2.1.0 right now, with stock rom on March update. Whenever a notification appears and it makes the notification sound, it shuts down (or so it appears but after a closer look I found out that the audio is faintly audible when I keep the speaker close to my ear) the audio which is playing in the foreground, be it a song on Spotify or a YouTube video. You can easily replicate it by taking a screenshot while a song or video is playing and the notification for the screenshot appears. Someone pls confirm if this is the kernel or something else.

Edit: Just discovered the culprit was Audio Modification Library. Just leaving it here if it helps anyone!

Edit 2: This happens with Ainur James DSP too!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gvsukids:
18.1
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Thank you very much for the log!

I don´t see a kernel panic that would cause a crash. Are you running stock or custom ROM?

What did you do when the reboot occured?

Nevertheless, the two WARNs you have in the log will be fixed with the next release I hope :)

no logs, no reboot happenend ;) get me a ramoops and I gladly take a look at it.

Take a log at the FAQ in post #2 and post #3

Actually applying the commits affects the kernel, even if the magisk zips are not flashed. So that statement is not correct.

However I tried it already some time ago and the kernel isn´t booting with the DTS commits applied. If you would have used the search function and searched for "DTS" this post would have popped up:

https://xdaforums.com/pixel-3-xl/de...l-3-xl-aka-t3864563/post78862685#post78862685

I picked the commits in my pixel 2 xl kernel and well sound via USB C to 3,5mm cannot be altered by this soundmod anyway. So I don´t really see that much use in it. I just kept it in my Pixel 2 kernel by request, but I think it´s not going to happen for the Pixel 3.

Thank you for taking your time to grab the logs!

Same for you as for [MENTION=4487388]jcmm11[/MENTION]. I see no kernel panic that would cause the crash but the two WARNs you have in the log will be fixed in the next release hopefully.

I don´t think the kernel is responsible for the behaviour you described. This should be entirely ROM dependant.

I´m on a custom rom. When taking a screenshot while music is playing, the music gets quieter, so it´s in the background and in the foreground the screenshot sound is clearly audible.

But the music is still playing and audible without the need to put my ear close to the speaker. After screenshot is finished the music just resumes to normal volume.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Donric13:
Just a question. Is wireguard still supported in this kernel? In wireguard app command line tools arn't available anymore and vpn icon appears in status bar. Anybody else remarked this?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
It’s still included. Wireguard app shows kernel-backend for me and command line tools are installed as a magisk module.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] shreyamt:
Post edited, but thanks for trying!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Donric13:
Thanks. Deleted and reinstalled the app. Now all is fine again. BTW kernel works perfect! Thanks for your work!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
Stock + Canary Magisk. I don't remember what I was doing at the time. Actually just before. Pretty sure (but not 100%) I was sitting on the home screen when it happened and had just exited something. The pmsg-ramoops file referenced Dropbox, but I definitely wasn't actively using that, although if it was doing something in the background I don't know.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Only the console-ramoops file is relevant. Since there is no kernel panic that would have caused the reboot it could be due to magisk and canary as the last few canaries have quite some extensive changes.

If it happens again please try to grab the file in the sys/fs/pstore folder again and let me know! Thank you!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HiM@L:
[MENTION=3428502]Freak07[/MENTION]

I am having Bluetooth issues while connecting to my car. it gets connected and disconnected continuously. I tried deleting and reconnecting again but same issue.

I am saying this might be kernel issue because i tried another kernel(don't want to mention other kernel name out of respect for dev) to see if the same issue exist and dont have any issue at all.

Please let me know what file you need for troubleshooting.

running stock.

Thanks for great kernel.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HamsterHam:
[MENTION=3146842]HiM@L[/MENTION] I've had no issues with Bluetooth in my car and with my headset.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HiM@L:
I am clean flashing Kiri Kernel again and will try to connect and see if it happens.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
When did this start with my kernel?

I had this with my Bluetooth dac on stock kernel too. (long time ago) Did you try to reboot to see if it fixes the issue?

if it’s easily reproducible for you, I guess a logcat and a dmesg while you try connecting when you have issues would be also helpful. :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HiM@L:
you know what It was User Error.

I didn't get any issue again after clean flashing Kiri. Something must have happened.

Thanks for jumping in and trying to help.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] EMJI79:
Is it relevant to activate "force GPU rendering" in the developer options settings or is unnecessary or even conflicting with the kernel settings?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] rspkt:
I've had zero issues with Bluetooth connections using this kernel since day one and I use my Bluetooth in my truck daily.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] GollyJer:
Possible to change the minimum RGB behavior for KCAL?

Hi Freak07. Thanks for the amazing kernel. Your choice of defaults is excellent. I don't tweak a thing in EXKM beyond how I want klapse color/functionality to behave.

However, I have run into one weird issue. Generally I use CF.lumen to change the color of my screen and have it go into "night" mode at 10PM. This night mode is set to RGB 256-0-0 (pure red). I was thinking I would no longer need CF.lumen as a separate app if I could use klapse to do the same thing. However, it seems the RGB settings in klapse have some sort of minimum built in.

In other words, if I set klapse to 256-0-0, close EXKM, reopen and go to the klapse settings the RGB is set to 256-20-24. The klapse author thinks this is a safety measure so the user doesn't set things to black, 0-0-0, and shoot themselves in the foot. And I agree!

My suggestion was to change the safety measure. Instead of never allowing any of the values to drop below a limit only apply the limit to any one color. This way the user could have full red, green, or blue if desired.

The klapse author mentioned this limitation is probably built into the KCAL code and that the kernel author would be the person to ask if hopes of a change were possible.

So, here I am, after that long explanation asking if this is something you can implement in the kernel code.

All the best and thanks for listening reading this far if you made it. ?

Jeremy
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] tanish2k09:
Following from the above post,

Please note that you would also need to change the scale_val_min define in klapse.h.