yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ArkReborn:
Hi! First of all I'd like to say thanks to [MENTION=3428502]Freak07[/MENTION] for this amazing kernel that he have developed. I have a question about my phone, I don't know whether this is the right place to ask or not but if someone have similiar / same problem and have fixed it please do tell me about it.

So I just recently bought my pixel 3 from my friend, and the first thing I do is reflash it + wipe it with the factory image (Android 10), root it and install kirisakura kernel, but I got strange issue where my phone won't deep sleep after it got wake locked. The main wake lock seems to be wlan and epoll_system_server_file[timerfd12_system_server] (Screenshot Attached). It do go away when I reboot the phone, but It will eventually come again in 2 ~ 6 hrs of usage.

If someone have similiar / same issue and have fixed it please do teach me about it, many Thanks in advance!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dark2099:
What's the "bromite" app you have installed. Since that's the only non stock app on there, going to lean toward that being the culprit.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ArkReborn:
Hi thanks for replying! It's my browser replacement for Chrome, you can find out more about it here :D
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dark2099:
Was mostly interested since it was the only non stock app you had installed, and since wake locks are usually from apps, seeing one I had never heard of made me suspicious of that being the app causing your phone to not deep sleep.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ArkReborn:
Hi! Totally understand your point of view, I'll try to uninstall the Bromite and going to update about it here! Thanks a lot!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Install better battery stats. You should be able to find it on XDA.

Install the app, grant root, finish the setup.

Set a custom reference, let phone sit on the table face down with screen off for an hour.

Then open the app again. Check partial wakelocks and kernel wakelocks. That will show you what’s going on.

Wlan and epoll are expected and necessary for your device to work.

Overheat mitigation I never saw on my device. I guess your phone must have been quite hot when setting it up. That would be my explanation for this wakelock.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ArkReborn:
Hi! Thanks a lot for responding and answering my question, I have installed the BBS from Play Store but haven't set the custom reference yet. I'm going to charge my phone to full again and will post the update again on this post about the result later on

And should I turn off adaptive battery options from the Settings > Battery? Because I've read on some post in the forums that some people suggested to turn it off

Thanks in advance!

Edit 1:

I've done collecting some sample of data from BBS, I have uploaded it on the attachment below

Edit 2:

Turns out the problem didn't persist when I reboot the device into the safe mode, strange enough but I'll try to find what apps causing the epoll wake lock over and over again

Edit 3:

After Reflashing and Wipe my phone clean to stock again (I haven't root it + Installing Kirisakura Kernel again), the Deep sleep problem didn't happen anymore (Now 16 hrs on going with Deep Sleep)

On the last time I flash the Kirisakura, I did change some option via EXKM (On Boot) which is:

* I/O Scheduler to Maple

* I/O Scheduler Read Ahead from 128 to 4096

* TCP Scheduler to BBR

* Entropy to 1024 and 4096

I'm not sure if it's related or not [MENTION=3428502]Freak07[/MENTION] kindly need your assistance on this one, I will try to flash the Kirisakura again and let it stay on the default options first. Hopefully there will be no problem with the Deep Sleep anymore
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tekken Lord:
I am hoping [MENTION=3428502]Freak07[/MENTION] would spare us poor "Corsshatch" users some valuable time. I know he has been selected by ASUS to develop a custom kernel for the ROG 3 gaming phone. Congratulation on your growing popularity, [MENTION=3428502]Freak07[/MENTION]
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Haven’t forgotten about you guys, no worries :svetius:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] acidspider:
Flashed ok with exkm. Working
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
Failed with both EXKM and FKM on DU (A10). Previous version was installed with FKM with no issues. Apologies if I missed something that it was R only since the Google source didn't change from 10 to 11.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DOMF:
Flashed fine on stock 11 with exkm. Thanks for all your hard work!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sic4672:
Maybe a dumb question, but does this now support LZMA ramdisk according to fastboot oem dmesg (quoting bigbiff from the TWRP topic)?

Basically I just wanted to ask if your latest supports TWRP. Appreciate your time and effort in all of your work.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] muttonhead411:
R2 working beautifully! Thank you so much!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
nice to hear :) you´re all welcome!

Is there a working TWRP for A11 yet? I guess data won´t decrypt anyway on A11 yet.

It´s not enabled in the 2.0.0_R, but I will enable it in the next release.

That´s completely incorrect. The kernel source did change quite a lot from A10 to A11.

Most obvious difference is stock A10 kernel was still on 4.9.210, while stock A11 is now on 4.9.223.

There were no changes from R-Beta-3 to Stable R-Release. Maybe that´s what you read.

The kernel is completely rebased on the Android R-Source. I have absolutely no idea if it even boots on Android 10.

That´s why the Kernel-Zip fails to flash by design on Android 10.

If you feel adventurous, you can open the kernel.zip, find a file called anykernel.sh and change the following lines from

supported.versions=11
supported.patchlevels=2020-06 -

to

supported.versions=
supported.patchlevels=

save your changes and reflash. Make sure to have a backed up boot.img as well as dtbo.img handy in case your device won´t boot.

It may be valuable information if it works on A10 for some, so if you decide to try it I´m sure others appreciate if you report back.

Just keep in mind the kernel is made for A11, and if you face issues your on your own. No support for A10 from my side if you use the R-Kernel.

Then you´re better off using the latest release for A10 :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
Great info, and I am definitely feeling adventurous. I will reply back with results.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sic4672:
Good point, I guess A10 is still in the works. Look forward to using this once pixeldust is updated.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
No luck. No errors in EXKM after editing the zip in place. On reboot, it just hung on the booting screen (the spinning DU logo). Rebooted into bootloader and flashed my original magisk_patched to both slots. Back to normal with Unicorn Blood and then flashed the A10 version of Kirisakura with no issues.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ArkReborn:
After a Few days of searching, turns out the one causing the issue was:

* Entropy to Read_Wakelock 1024 and Write_Wakelock 4096

When I don't try to edit and fiddle with it, the issue is gone completely! But I'd like to ask, do adding entropy had any effect to Android Device nowadays? Because back then there is an app called seeder if I'm not mistaken that adding entropy and supposed to make the device more 'smooth'

Thank you very much everyone!

Edit 1:

Found my answer here. I guess Kirisakura Default Value was already very optimized for the device :D. Once again, Thanks a lot for the effort and dedication [MENTION=3428502]Freak07[/MENTION]!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] acidspider:
I was really enjoying 2.0, however this morning didn't wake toy usual alarms that had been set,on checking the phone the screen would come on but apps wouldn't load, I could open the app drawer but apps would not load, attempted to restart but just got a spinning restart logo, so I hard reset and phone booted but then if I let the screen go off by itself it would.not come on again and had to reset again, had to flash back to 1.5.4

Stock rom, rooted latest canary on A11
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Yeah I expected that given the amount of changes between A10 and A11.

Thanks for testing and letting us all know. Good thing I put the Android Version check in :)

Thanks for letting us all know what caused the issue! And for actually taking your time and not blindly blaming the kernel, which happens just too often.

That’s why I ask for bug reports to be reproducible on a completely unaltered device. No tweaks, mods, scripts or other modifications. This serves as a good example that even a very small deviation, can cause issues that are seemingly unconnected.

Nice work nailing this one down!
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] sliding_billy:
Any time.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ArkReborn:
The pleasure is all mine to be able to enjoy your kernel :highfive:
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
You know the drill. Please take a look at the FAQ on how to report bugs.

Make sure to not use any mods, tweaks, scripts or magisk modules. (remove even the tiniest modification, you think are absolutely unrelated.) Then reproduce the issue and gather logs. I’ll gladly take a look at them.

No logs, I can’t do anything. 2.0.0 worked fine for me with an uptime of just shy of 7 days without a single issue. :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
Hey,

Is it possible to flash the updated kernel without root? I read that magisk is slowing down the phone or causing other stability issues on android 11?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
yes it is, but it requires some effort from your side.

You need to repack your boot.img with the kernel and the dtb from the kernel.zip.

You can use magiskboot from the magisk.zip to repack (search google for magisk documentation on how to) or osm0sis image kitchen found on XDA.

Then you need to flash the repacked boot.img and the dtbo.img (from the kernel.zip) via fastboot.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tekken Lord:
[MENTION=3428502]Freak07[/MENTION] ,

I am thankful for your work. I have a curious question about the GPU driver: it shows that it is a recent release on June 26, 20. Did you update it in your kernel or is it coming from Google? If you actually released as a part of your kernel, will we be expecting up-to-date drivers from now on?

Cheers,

TL
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] acidspider:
First attempt at a logcat
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] nikhilnangia:
Funny enough, I experienced similar results with 2.0.0 running on Android 11.0 (clean install). My phone hung and I had to force restart it. Upon restart, the apps lost their icons and none of them opened. After a few seconds, the phone hung again and I had to force restart again. Let me know if you'd need my logs, too - reason being perhaps acidspider's would be enough.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Can you send me a screenshot what you exactly referring to?

If you’re talking about the adreno blobs, that’s from google ;)

No one log is never enough. The more the better. Without a log there’s no way of telling what happened. The “me too” game doesn’t help anybody in the end :)

[MENTION=3408326]acidspider[/MENTION] a logcat is not really helpful. it shows only rom stuff. I need a dmesg in particular.

Like it’s described in the FAQ. In case your device hangs I need a logcat and a dmesg taken at the moment when your device hangs.

Take a look at the last release post and the FAQ. It’s described there which situation requires which logs.

If your device forcefully reboots I need a ramoops.

If your device hangs I need a logcat and a dmesg taken at the moment it happens.

Guideline for taking logs can be found in the FAQ and the 3rd post as well.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tekken Lord:
[MENTION=3428502]Freak07[/MENTION]

Pls see the attached.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] ArkReborn:
Hopefully this thread here and here can help, many people said that 'Systemless Host' module on Magisk lead to the frequent freeze
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
Yeah, thats what I've been reading too. It is magisk related. Im going to flash kernel without magisk/root. Will report back
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Upy3r:
Anyone else facing this on EX manager? Can't see anything at Kernel Wakelocks.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] mickyw1980:
I have experienced the same issue running stock kernel patched with magisk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LimitsX:
I installed factory Android 11 final version. Erased my partition before completely.

Your problem could be magisk, as others who noted, are experiencing something very similar with stock kernel

---------- Post added at 09:20 PM ---------- Previous post was at 09:17 PM ----------

So update: I installed kernel 2.0 manually without magisk/root and any manager. It is running great, no freezing, no lockups, nothing. The phone feels smooth, responsive, and no lag. I cant comment on battery life yet since its been less than one 12 hours I've been using it.

Thank you so much Freak07! The Android 11 and this superb awesome kernel of Android 11 CAF is just a beast.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] acidspider:
I understand that the problem could be magisk, but I have no issues when using 1.5.4 On a11
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
That´s expected. The wakelock blocking driver that EXKM displays on that page is not built into the kernel.

Interesting. So far my phone works fine since I updated when A11 stable dropped. Thanks for the report!

You´re welcome! Great work with repacking as well.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
anyway if you can shared your boot.img file? I am having the problem with magisk causing freeze. But would love to have this kernel, I am running the phone without anything right now.

Edit: I finally managed to disabled the systemless host module and thing are back to normal, with 2.0 installed too. Thanks
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Tekken Lord:
Hey guys,

I am not exactly sure why some of you are having freezes, and other issues with the

Canary Magisk

root, but I don't. I did have a bootloop because I forgot to uninstall the incompatible modules, and everything has been smooth since then, meaning no freezes, reboot,..etc.

What I did was:

1. flash-all without -w (I went straight from the last Q's August firmware to R's September).

2. Patched boot image with Canary Magisk Manager (magisk debug apk).

3. Fastboot flash boot ***.img with that patched boot image.

4. Got bootloop, then enter this command "adb wait-for-device shell magisk --remove-modules" (without the quotation marks) while bootlooping (make sure to accept the trust device message on the phone, or the adb won't be able to act with root privilege). If that did not work, you might have a faulty hardware or slot A/B corruption.

5. Go to Canary Magisk Manager's Setting and select Canary as Source. Update to the latest Magisk and Manager (should automatically inform you of new updates with an active Internet connection).

6. I am using the latest EXKM to flash the kernel, and have not had any issue flashing and running this kernel. I have heard FKM is still on the summer update and has not been updated to any new version, and might cause flashing issues.

Please also carefully read the Rooting Guide for 11 in the other subforum.

Good luck to you all and report back if you are successful with my method,

TL
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] qualitymove13:
I am running hot to the point where I get shut downs when gaming. Before I grab a log, is it just me?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] vprasad1:
Does it happen with stock kernel?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] acidspider:
I have only found a11 to be stable with krisakura 1.5.4, I found a workaround to the freezes with stock and r2.0 having always on display turned on but I don't like the amount of battery it uses for my usage so I am happy using 1.5.4 for now
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] kakabobo:
swappiness cannot set above 100.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
you´re correct, the commit for this is missing in the R-Kernel. Thanks for spotting it. Will be fixed in the next release.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Xeust:
I also noticed the missing lzo-rle compression. Or it is unnecessary?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] LunaticSerenade:
For those that were having boot loop issues (I know I was), the newest canary build of Magisk seems to have levelled that out. At least for me it did.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] dnsmo:
do you have systemless host enable? do you have freeze problem after reboot?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Paz9:
Any idea what

persist.traced.enable=1 is

It's enabled in build . Prop its the only thing that stands out that may be a long function that's enabled, what would the draw backs be if we disable it?

Also

echo "NO_GENTLE_FAIR_SLEEPERS">/sys/kernel/debug/sched_features

Makes everything faster for me
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MArtyChubbs:
Given: I have Magisk (latest canary,) Swift Installer (for Swift Black,) Busybox MM, YouTube Vanced MM, Viper FX MM, and TWRP Recovery all installed. I flash this kernel almost daily.

My steps:

Uninstall Magisk (Restore images)

Install kernel in EXKM (FKM just as good)

Install Magisk

Reboot

Good luck!

This has worked for me...
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] MeetFace:
I just reboot to TWRP, flash kernel, flash Magisk, profit.

Takes 5 minutes.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Kernel will be updated probably later today with latest upstream, some more caf patches that fix a few memory leaks and a bit more :)

I’ll also reworked the kernel.zip to hopefully squash a few issues some were experiencing.

The kernel.zip is also ready for custom roms with this update :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] HiM@L:
Hi,

html dev claims that custom cpu boost like sultan we have is not needed for our device. what do you think?

how good is it compared to stock.

sultan's implementation was for Pixel 2 aka 835 devices and ours is 845. do you think sultan's logic still applies for our device for implementing this?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
When I received the phone I was running it stock for a week, to see how it behaves and how I like it. As expected the phone was very smooth (like all pixel devices are, even completely stock).

The stock power hal boosts quite a few things, quite similarly to the Pixel 2 XL, which I also developed for.

It boosts dev/stune/top-app/schedtune_boost to 50 and minimum frequencies on various occasions such as touching the screen, opening an app, flinging etc. (read about top-app schedtune boosting here at the end of page 26). By boosting top-app we give tasks that are mainly ui-critical priority to get completed faster.

Excerpt from the part about schedtune boosting:

This value is used to compute a margin to be added or removed to or from the utilization
signal of a task/cpu. The value of the margin is calculated to provide a well-defined and
expected user-space behaviour.

Keep in mind we boost only top-app tasks! (that´s the beauty of this approach!)

With cpu_input_boost enabled we still boost dev/stune/top-app/schedtune_boost to 50 for a longer period of time but no minimum frequenices via a power hal. Instead cpu_input_boost boosts the minimum frequencies (shorter than stock) following its logic a bit less aggressive than stock power hal.

The combination of boosting minfreqs + top-app/schedtune-boost (which is a courtesy of EAS) is what makes the Pixel Phones so smooth.

I decided to keep the cpu_input_boost for now. It yields on the Pixel 3/XL also very good results, I´m very satisfied with the balance of performance and battery (which is in my opinion excellent, see screenshots attached, mostly light to medium usage I´d say but I was still impressed) and the responsiveness of my phone :)

I´m not willing to sacrifice performance for maybe 10 minutes more battery life, that some may get, if a lower top-app boost is used. I expect my phone, to complete all the tasks I throw at it, in the quickest most efficient way possible!

My kernel delivers this for me, so I´m quite content currently :)
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Freak07:
Hey guys and girls :)

as promised the new update is here.

It includes linux-stable update to 4.9.140.

There are also a few CAF commits included which should fix a few memory leaks.

also thanks to [MENTION=7291478]kdrag0n[/MENTION] for giving me a heads up about not properly enabling the speculative page faults. Should be properly enabled now.

As already mentioned I changed a few things in the kernel.zip. In case you face issues with root being preserved now please start with stock boot.img, root properly via magisk and reboot at least once to the OS. then proceed to flash my kernel.zip.

Root should be kept now for all.

Please report back if it still isn´t. Please tell your exact steps you did while flashing and your previous setup! When flashing via TWRP you will also see again a line telling you root is preserved!

If you face the ramdisk error in EXKM, start too with a stock boot.img. I don´t know what this could be. I flashed now over 100 zips consecutively and never got it. The changes I did will most likely not solve this.

Also the kernel.zip is (should be) now ready for custom roms whenever they are about to drop :)

Changelog

- Upstream to 4.9.140

- Fix a few memory leaks found by CAF

- add missing entries to enable speculative page faults (thanks [MENTION=7291478]kdrag0n[/MENTION])

For further details please take a look at my github!

Download is below :)

Download:

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

or following the link in the op to the correction version

Instructions can be found in the OP!

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] Komodoketavaran:
Thank You for your quick updates.

What do you think about to enable CPU&GPU overclock ?

P.S Lass dir den Kaffee schmecken :)

Gesendet von meinem Pixel 3 XL mit Tapatalk
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] elreydenj:
Must have something to do with the Canary version of magisk... I am getting the ramdisk error again with both TWRP and Ex... I didn't in my last flash of your kernel. Only change being there was a magisk update in between. Do you constantly update to the latest Canary version as it comes out?
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] Semtronix:
Flashed straight through EXKM and kept Magisk install. Looks like you might've nailed whatever the issue was this time.
[Google Pixel 3 XL ROMs, Kernels, Recoveries, & Oth] DIXZ06:
Working perfectly, as expected!

Thanks for the detailed instructions. :good: