yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] BostonDan:
No. The old boot.img file is required to revert to an "unrooted" state. If you applied Magisk by patching the boot image file, then fastbooting and flashing this rooted boot image file to the phone via fastboot, then Magisk does not keep a backup of the stock boot.img.

If you apply OTA and then directly patch the phone (which is what TopJohnWu recommends once a phone is rooted by the patching of the boot image) the phone keeps a copy of the boot image file.

I recommend reading TopJohnWu's official OTA Upgrade Guide: https://topjohnwu.github.io/Magisk/ota.html

along with the page I referenced above on how to store a clean boot.img on the phone.

Cheers,

B.D.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kancrutt:
many people (including me) doesn't have notification of OTA update while on rooted. so I have to manually sideload OTA or flash full image every month
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Echosen:
What are the best settings for this in FKM?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
It's works great the way it is set up . Though the dev did mention he/she personally has swappiness [MENTION=585080]175[/MENTION] rather than 100.

---------- Post added at 09:00 PM ---------- Previous post was at 09:00 PM ----------

It's works great the way it is set up . Though the dev did mention he/she personally has swappiness [MENTION=585080]175[/MENTION] rather than 100.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
I am 100% in the same boat as you, never got the ota update from my phone, I have to apply the update manually everytime.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nikhilnangia:
Unless you know what you're doing, I would leave it as it is. Freak07 really optimized the kernel well. Still, here are my settings:

1. Memory->ZRAM compression algorithm changed to lzo-rle. It's a more efficient algorithm than lz4.

2. Swappiness set to 160-175. Calls for a much more fluid experience, but YMMV.

Here is what Swappiness does:

swappiness controls the relative amount of swapping memory pages and dropping the cache.
Having swappiness at 100 means memory and cache have same priority.
With swappiness set to 0, memory will never be swapped out in favor of cache, so the kernel will always drop cache first because it will never swap out any memory.
With swappiness set to a higher value than 100, swapping memory has more priority than dropping the cache

3. I/O scheduler set to fiops instead of default cfq with a readahead buffer size of 384KB.

4. TCP compression algorithm set to bbr.

5. Graphics governor set to simple ondemand instead of msm-adreno-tz

That's it. Again, these are my preferred settings. There is no "one size fits all" approach when it comes to tweaking. ;) Good luck!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Echosen:
A lot of these issues come from non-official Google pixels. I bought mine straight from Google unlocked and I receive all OTAs.

---------- Post added at 09:51 PM ---------- Previous post was at 09:45 PM ----------

I definitely don't know what I'm doing because all these terms in FKM kernel manager look Chinese to me and I only understand English unfortunately. Lol but I have been rooting and modding since the Nexus 4 days I know enough to get around and I'm willing to learn more but my main desire is just to have a better kernel than stock.

So, I'm just going to leave it as it is but question what does the swappiness do exactly?

I see you also mentioned that it has to do with call experience. Do you mind elaborating on that a lil bit more?

EDIT: I see you explained what swappiness does. My bad ?*♂️

---------- Post added at 09:56 PM ---------- Previous post was at 09:51 PM ----------

Would it be wise to mess with Microphone / speaker gain?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nikhilnangia:
No worries. That's what this forum is for: learning and experimenting.

I said "calls for a fluid experience", which meant "leads to a fluid experience". I never mentioned "phone calls". ;)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
I bought mine from google store, unlocked. so what else you want to say?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Echosen:
Replacement?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] BostonDan:
While you may not get notification of the OTA update (especially if notification of this is turned off), the OTA availability can usually be checked about 3-4 days after official release. Go to security, updates and do a check for update. Then apply the method I quote above.

I will stop hijacking this thread from this great kernel now, but advise people to look into applying the OTA update. I do understand that YMMV but I am waiting until tomorrow (when the OTA is scheduled to be released for my phone) to download and install it, maintaining magisk root without requiring a full wipe.

Cheers,

B.D.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] acidspider:
Is 1.5.3 ok to run with June ota or best wait for update?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Update to 1.5.4

Hey guys and girls,

Update time :) Linux-Stable, June Update, Wireguard etc. Detailed changelog below

Just in case:

If you face issues or bugs when running the kernel, please return to a stock environment, only your rom plus magisk root, without any modules, scripts, tweaks or mods and see if you can reproduce the issue.

Tell me the exact steps needed to reproduce.

Then send me a dmesg and a logcat (if the kernel crashes not) or a ramoops (in case the device reboots). Take a look at the second post for a guide on how to obtain these.

My kernel.zip flashes both boot.img and dtbo.img. So if you want to return to stock, you need to extract both from factory image and flash them via fastboot if on stock rom.

If you’re on a custom rom you will need to dirty flash your custom rom or learn how to extract both images from a payload.bin

Special thanks to [MENTION=4487388]jcmm11[/MENTION] and [MENTION=336855]melgar[/MENTION] for testing and keeping up with me!

I wish everybody a nice day/evening! :)

Changelog:

- Update google sources to latest June state

- Linux Upstream to 4.9.225

- update wireguard to latest snapshot

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=4349826312261825407

or following the link in the op to the correction version

How to flash the Kernel:

1. Make sure you are rooted and either EXKM or FKM is installed. Download the kernel.zip to your device.

2. Flash kernel zip in EXKM or FKM app. Root will be preserved!

3. Reboot and profit! Before reporting any issues make sure to read the Release-Post of Bluecross_Q_Release_1.1.3!

Instructions can be found in the OP 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] Freak07:
setting I/O scheduler to anything else than CFQ will not be beneficial at all on pixel devices.

Take a look at the pk´s tuning script thread on the Pixel 4 xl forums, I did a detailed explanation there.

Using simple ondemand GPU gov doesn´t make sense to me as well. It was a tweak to overcome an issue on msm-adreno-tz a few years ago where some 2D games suffered performance problems, because msm-adreno-tz was too conservative.

There´s also a commit floating around adding GPU boost for msm-adreno-tz (adressing the same issue), but that isn´t needed on modern qcom socs either. :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nikhilnangia:
Thank you so much for sharing, Freak07! I will have a look at changing from fiops to cfq.

As for the GPU governor, that was exactly it: it was too conservative which led to stuttered scrolling which was immediately fixed by simple on-demand. But I'll change back to msm-adreno-tz as you mentioned it was an old issue that would be fixed. :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
Even after manually checking for an ota update, I haven't received one since the March update, FWIW
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tekken Lord:
Thank you very much for your great work. We would very much need more Pixel heroes in P3XL forum. Please enjoy the rest of your day and stay safe.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
[MENTION=3428502]Freak07[/MENTION] Thank you very much for keeping P3XL alive and active.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] KurioHonoo:
Same! Finally manually updated to the June patch and called it a night. Guess Goog hates us now.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Echosen:
So how do you use your phone exactly?

I did some research and I was tinkering with the settings and notice it's draining more than saving.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HankMcCoyX:
Is this backed up boot.img somehow different from the boot.img in the image file downloaded from Google?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jcmm11:
The boot image is the same (although in a slightly different format, it's zipped and the name includes a hash). However if you've applied kirisakura then to revert you also need the stock dtbo image (which can also be obtained from the downloaded image file).
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] gvsukids:
I wait for the July kernel
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
July patch is out guys

Got it installed. Waiting for kernel. ::laugh:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] swieder711:
Is anyone running the 1.5.4 kernel on the July update? I was going to wait for the new kernel before updating the OS.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Qw12:
Working fine here ;)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] BostonDan:
According to Flar2 from ElementalX kernel, no kernel updates were required for July.

Cheers,

B.D.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tekken Lord:
Yeah, still need to hear from the OP :p...either way, I hope the OP would have a rested month and time for sabbatical.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
As it seems there is no source code update this month like already mentioned. So it should be fine to use 1.5.4 on July :)

I plan to update the kernel soon though :) Just ran into other issues elsewhere. Sorry for the delay everybody :)

I also have some other good news. I gave merging CAF completely, like we had on Android 9 (if anybody can still remember), a try again. After spending the better part of the weekend on it I got the kernel to boot finally.

So it seems this might makes its return for Android R if everything goes according to plan :) Quite exciting, because that still bothered me for a long long time :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nikhilnangia:
Anyone notice that ZRAM keeps getting disabled on its own in the latest version? Or is it just me?

Thank you for the advice, if any!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
It’s probably some tweak, mod, script or app that’s disabling ZRAM. Maybe a forgotten setting in an kernel manager or some random kernel “tuner” script or app thinks it is a good idea to disable it.

ZRAM is enabled during boot from usersapce by the init scripts. The kernel can’t disable ZRAM on its own it needs to receive a command for that.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
Aug update is lived guys
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nikhilnangia:
Anyone tried if 1.5.4 works with August patch? Thank you!

EDIT: Works just fine. ;)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Benson King:
Hi is the kernel support android 11 ? Could this kernel use swap function?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] k0rner:
Hi [MENTION=3428502]Freak07[/MENTION], would it be possible to add this patch to your otherwise great kernel?

https://github.com/kdrag0n/proton_bluecross/commit/bf5d4feecdd80b131fbbab9e1111eaa86f6eeba5

Alternatively, are build instructions available somewhere?

(high level, e.g. install this Ubuntu version, add these packages, download kernel and run make whatever)?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] RubenPCA:
Random reboot

I was passing photos from my device to my computer, I left it connected after passing the files, because I was editing the images, the device (blueline) rebooted randomly without any cause.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] k0rner:
answering my own question, how to build this kernel:

Set up a VM with recent Linux (I've used Fedora 32) and 16+ GB of RAM

Get the kernel https://github.com/freak07/Kirisakura_Bluecross/tree/Release_Q_1/

Get Google Clang from https://android.googlesource.com/platform/prebuilts/clang/host/linux-x86

Get Android NDK (https://dl.google.com/android/repository/android-ndk-r21d-linux-x86_64.zip)

Adjust build_kirisakura.sh variables to point to downloaded tool locations (CLANG_PATH, CROSS_COMPILE, CROSS_COMPILE_ARM32, LD_LIBRARY_PATH variables)

Run the script to build the kernel

Grab the kernel image from out/arch/arm64/boot/ folder.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ffuser1:
Were you able to successfully add that patch? What's the legality of sharing that build? Seems like a useful patch if it doesn't fry the phone
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Read the OP. No, it does not support Android 11.

ZRAM is enabled in the kernel if you mean this by swap function.

If it happens again take a look at post #2 and #3. Please take the correct logs, without any additional mods installed.

Once you gathered the logs I can take a look at the issue. Without logs I can´t do anything.

Apologies for not getting back to you sooner. I was very busy the last few weeks and didn´t have much time to work on the kernels.

Great to see, you already answered your question about how to build the kernel. Good work [MENTION=2309157]k0rner[/MENTION] !

To be fair I´m a bit reluctant to add that patch as I generally don´t like to play with charging drivers.

Bad tongues might say google added this as to only sell their, to be frank, very expensive Pixel Stand. Others might say it´s there for security reasons.

Charging faster over wireless means generally more heat. Heat is bad for the battery. While this might not be a problem in some parts of the world, it might be one in others where ambient temps are constantly higher.

Just to bring one argument nobody has control over. That means I can test it on my end and everything appears to be working fine and in sane limits when ambient temp is about 20°C, but it might cause the battery to get significantly hotter when ambient temp is 30°C somewhere else.

Over time this will degrade the battery way faster on the 30°C ambient temp device. So I´m not sure if this is a choice I want to offer.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] k0rner:
From my experience (using this patch in form of a shell script for ~year now), battery temperature management is independent of wireless charging speed - if phone detects battery temperature over 38 C, it will limit charging current to 500mA, further limiting to 250 and 110mA at 40 and 41 degrees.

So the patch will not cause excess battery degradation either from temperature (as phone will limit current) or from high charging current (maximum obtainable on wireless is ~1600mA, and USB PD fast charging is peaking at 2900mA)

One question regarding building the kernel - can you hint at where correct version of "mkdtimg" tool should be obtained?

I've built kernel Image.lz4 successfully, but flashing my dtbo.img disables touchscreen.

From the driver sources (https://github.com/freak07/Kirisaku...rivers/power/supply/qcom/p9221_charger.c#L348) it looks like Pixel 3 will enable fast wireless charging for "EPP"-compatible chargers, if that's not supported - "basic profile" is used, which we all observe.

More details:

https://support.moshi.com/hc/en-us/...-latest-in-wireless-fast-charging-technology- and on Reddit:

https://www.reddit.com/r/GooglePixe...el_4_qi_epp_wireless_charger_recommendations/
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
I have no wireless charger to test, but in that case I guess I include the commit in the next release. Maybe it´s useful to some.

I don´t know if many people use wireless charging at all. I guess it comes down to personal preference.

I´m using tools compiled from AOSP.

I think you might be fine using those found here:

https://xdaforums.com/pixel-2-xl/how-to/tools-tools-building-pixel-2-xl-kernel-t3693955

you could pass dtc similar to how I do it on the pixel 4 kernel I guess:

https://github.com/freak07/FLORAL/blob/master_floral_caf_11/build_kirisakura.sh#L18
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] swieder711:
I use wireless charging in my car and home.. Im using the Advanced Charging Controller App (AccA) to manage current (mA) and temperature behaviour which seems to help extend the battery's health.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tekken Lord:
Count me in as a 2nd wireless charger. I am currently using the Belkin one, but it does not support stand function, just the fast charge.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] BHermes211:
Mind helping me compile?

I followed all the steps

Kernel source, downloaded clang, adjusted paths. Ran the script and it errors with makefile:152: sub-make) error 2

Im not sure what android ndk is for...?

Maybe that's my issue

Thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] k0rner:
To fix that error you will need dtc and mkdtimg from https://xdaforums.com/pixel-2-xl/how-to/tools-tools-building-pixel-2-xl-kernel-t3693955 somewhere in $PATH (e.g. /usr/local/sbin/)

Also, to get more details on errors - comment out "make clean && make mrproper" line in the build script, incremental builds produce error messages which are more readable.

As for Android NDK - it is needed for CROSS_COMPILE and CROSS_COMPILE_ARM32 variables.

For example, I have google clang extracted to /build/google-clang and NDK extracted to /build/ndk.

In this case, the variables will be set as follows:

export CLANG_PATH=/build/google-clang/clang-r383902/bin
export PATH=${CLANG_PATH}:${PATH}
export CLANG_TRIPLE=aarch64-linux-gnu-
export CROSS_COMPILE=/build/ndk/toolchains/aarch64-linux-android-4.9/prebuilt/linux-x86_64/bin/aarch64-linux-android-
export CROSS_COMPILE_ARM32=/build/ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/arm-linux-androideabi-
export LD_LIBRARY_PATH=/build/google-clang/clang-r383902/lib64:$LD_LIBRARY_PATH
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] BHermes211:
Thank you

I'll give that a try after work
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] automattic:
Very nice work on this kernel, I appreciate your efforts!

I'm also interested faster wireless charging. I've noticed that most people either use wireless charging all the time or not at all.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] xuser_:
Hi [MENTION=3428502]Freak07[/MENTION],

Possible to share your setup details for pixel 3,

Rom, gapps, rooted, magisk mods if any, basic helper apps (kernel manager etc..)

Thanks...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
big update coming? andriod 11 is out officially.

tried to root it with magisk 20.4 but once I reboot the screen is not accepting touch, so a custom kernel really is in need for andriod 11, or maybe magisk need to be updated._

-------------

Just to clarify, when I pull the file from the phone after I patch it with 20424, I got the wrong file, after I did it again and it's working fine.

I will wait for an answer from op before I tried the 1.5.4
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
Canary Magisk is needed to root, and from what I understand there were no kernel updates in A11.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] acidspider:
Can we flash 1.5.4 then on a11?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Homeboy76:
[Guide] Pixel 3 XL Android 11 (R)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] acidspider:
I don't understand,a simple yes or no would suffice.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] domicq:
Of course you can, but probably you'll end with bootloop. Let us know how it works. :highfive:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
I just tried but doesn't work, kernel manager did not flash it

FXK did not work
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Homeboy76:
You're welcome!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sangiman:
I ended up patching the boot.img from the pixel dust forums.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nikhilnangia:
Good idea. Do you mind sharing it, please? Is it also rooted with Magisk canary?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] acidspider:
Please upload if rooted, ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sangiman:
I flashed using ElementalX manager https://www.dropbox.com/s/la7tjxqi661qv6c/magisk_patched.img?dl=0 or just flash using adb.

---------- Post added at 01:54 PM ---------- Previous post was at 01:52 PM ----------

Link shared. It was patched using the latest canary.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nikhilnangia:
Confirmed, works. Rooted with magisk canary and works on P3XL running 11. Thanks a lot!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] jlokos:
Maybe a few more details, please? You did an ota or google image update to android 11 and then you flashed the patched image using EKM? Doesn't EKM need root to work?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sangiman:
Doesn't really matter how you get to Android 11 but I took the OTA and then rooted using the stock boot.img making it so I could use EX kernal manager to flash his kernal but ended up wanting to try this one out. You can flash the patch boot.img using adb which only needs a unlocked bootloader so you can skip using a kernal manager.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Instead of flashing an outdated kernel on A11 that just happens to work without major issues, it might be worth to wait a bit to run a proper kernel :svetius:

Might come with major changes and surprises :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nikhilnangia:
Can. Not. Wait. :laugh:

Thank you for all your hard work!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dirtyreturn:
The surprise is probably gonna be freaking awesome! Who doesn't love surprises? Anyway
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nikhilnangia:
You got that right. If I'm not mistaken, I think I know what the surprise will be. ;)

[MENTION=250713]Freak[/MENTION]: you've successfully merged CAF, haven't you? ?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
really can't wait for your touch on this.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Xeust:
Sweet! I couldn't stand A11 without your kernel. Thank you very much!