yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Burt Squirtz:
@Freak07 My goodness great work sir! The first custom kernel for the OnePlus 6 Pro.

So far running very well!

Just some few early unusual observations, and this might be my only unit doing this:

1) Device is slightly snappier now. But this seems to come at the cost of fluidity. Doesn't feel quite as smooth as stock kernel.

2) When the device is charging, the charging device vibration haptics randomly buzzes from time to time - when a cable is plugged in. It would never do this on stock kernel. Again. Might be just some sort of weird fluke as I just literally flashed this.

Is it possible you could implement KCAL color commits to alter saturation white point controls? If there's ever a device that needs it, I'd say it's this one. That yellowish piss hue on the screen is simply gross. The six Pro has the clearest screen I've ever seen, but the color reproduction looks nothing short of horrendous. I don't understand why Google doesn't implement white point or wide color gamut support on Pixel devices. It's a night and day difference to your eyes. I love that dopamine kick from seeing beautiful, vibrant colors.

EDIT: Also, I can't stress enough. This first build is nothing short of amazing. I know it's super tough because this is all new stuff.

Could you possibly consider adding some CAF boost controls sometime in the future? It's so awesome to build and make the device a little bit snappier on command^

EDIT 2: this might be far too early to tell, but there seems to be a bug with charging. Along with the random vibrations going off, the charging speed is unusually slow. Again, this might be only my device doing this (Fluke) so maybe other people can concur.

EDIT 3: just noticed another bug. Again. This might be only my device. LTP0 doesn't seem to work. Everything is locked at 120 Hertz. Not sure would have caused that. I've rebooted a few times and it's still there. I can provide any logs of necessary.
[Google Pixel 6 Pro] vassosman:
Wireguard was implemented by Google in the Android 12 kernel.

Google adds WireGuard VPN to Android 12's Linux Kernel

Google just made a big move to bring WireGuard VPN kernel acceleration to Android 12 by merging support in Linux Kernel 4.19 and 5.4 trees.

www.xda-developers.com
[Google Pixel 6 Pro] Zilla0617:
I prefer to activate it without the slower VPN key method. If you have a custom kernel, you can activate it in the background (without the VPN key). Right now if try to activate Wireguard on the stock kernel the tunnel is created via the key.
[Google Pixel 6 Pro] bjevers:
I just had a reboot. I've attached my pstore folder.
[Google Pixel 6 Pro] allenjthomsen:
same getting random reboots every so often

ill get my pstore and upload it for you in a few
[Google Pixel 6 Pro] danw_oz:
Awesome, now a reason to get root.
[Google Pixel 6 Pro] Freak07:
Update to 1.3.0

Hey guys and girls,

Alright here´s the next update and it´s a really big one.

Some of you used to run Kirisakura on the Pixel 4 XL and just like on that device today we were joined by @tbalden and his excellent features available in his CleanSlate kernel. Thanks a lot to him for his dedication and time he put into the features again. Finally sweep to sleep made its glorious return. :)

This release has the CleanSlate features working for Pixel 6 Pro users. Unfortunately they don´t work on the Pixel 6 at the moment.

Please follow the instructions in the CleanSlate thread to get the CleanSlate apps working correctly.

As previous kernels of mine, this kernel has now been upstreamed to latest linux-stable 5.10.79 (at least latest at the time of testing)

kernel/common 5.10 for android 12 has been completely merged as well, which includes a lot of updates and optimizations as previously mentioned. The previous release only had some excerpts from that. kernel/common 5.10 for android 12 is currently at 5.10.66, I except this drops to stock in the next few months.

Several other improvements are included as well. More details in the changelog.

Please flash all three provided images according to the instructions. If you don´t flash vendor_dlkm CleanSlate features will not work and you´ll lose some of the other optimizations. dtbo.img should be stock for now, but eventually there will be changes. It´s best to adjust to the instructions now to provide confusion later. :)

I hope I can work out non-userdebug vendor_boot.img later, so we can just flash all four images and be fine all the time.

Spoiler content hidden.

Changelog:

- linux-stable 5.10.79

- kernel/common merged

- CleanSlate features added

- update several drivers to use power efficient workingqueues (for example wlan driver)

- kernfs: use buffer from the stack space

- printk: use buffer from the stack space

- kthread: use buffer from the stack space

- bpf: avoid dynamic memory allocation for small value buffers

- binder: Reserve caches for small, high-frequency memory allocations

- kernfs: use kmem_cache pool for struct kernfs_open_node/file

- cgroup: use kmem_cache pool for struct cgrp_cset_link

- f2fs: reduce timeout for uncongestion

- f2fs: Demote GC thread to idle scheduler class

- f2fs: set ioprio of GC kthread to idle

- mm: vmstat: use power efficient workingqueues

- optional powerhint magisk module to possibly save a little bit of battery on screen off scenarios like music playback.

Download:

Downloads for : -Android- Generic Device/Other | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.

Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.

www.androidfilehost.com

Instructions can be found in the OP! Please follow the instructions to avoid any issues.

Don´t forgot to restore the stock vendor_boot.img found in the factory image of the firmware you´re currently running if you flashed 1.0.0 vendor_boot.img in the past!
[Google Pixel 6 Pro] gokart2:
Right on time. Thank you!
[Google Pixel 6 Pro] DanielF50:
Should vendor_dlkm.img & boot.img be hosted on the AFH link? If so, they seem to be missing 😬
[Google Pixel 6 Pro] roirraW "edor" ehT:
I was just about to ask the same thing. Wasn't sure if maybe we were supposed to use the old files for those two, but I doubt it.
[Google Pixel 6 Pro] Freak07:
fixed :) internet didn´t want the way I wanted :D

thanks :)
[Google Pixel 6 Pro] roirraW "edor" ehT:
I figured maybe they didn't get imported from the FTP or something like that. Thank you!
[Google Pixel 6 Pro] john-aurelio:
Excellent work I'm from my 4 xl pixel
[Google Pixel 6 Pro] Texan1:
Hi mate, I'm assuming where it says in the instructions to flash vendor_boot.img that it is not required as the subsequent instructions just say to flash dtbo.img and boot.img?

(BTW, many thanks for the new kernel, love your work (y))
[Google Pixel 6 Pro] Nekromantik:
what idle drain people getting on here?
[Google Pixel 6 Pro] Exel:
Followed the instructions to a T from OP and everything flashed perfectly.

Coming back from using an iPhone for a long time, so excited to be tweaking stuff again.

Thank you @Freak07!

Side note, if we don't care about the CleanSlate tweaks just better stability, faster updates and battery life, just don't install the app and all of those features should be disabled by default?
[Google Pixel 6 Pro] Freak07:
Thanks for the kind words.

Correct. Thanks for spotting it, already corrected!

I'm losing about 2-3% over 7-8 hours overnight. Basically similar to stock. :)

Signal strength, network quality, wifi, installed apps, background apps/processes have way bigger impact on that as kernel changes.

Great to hear it worked out well for you.

Yes, if you don't care about the CleanSlate features don't install the apps and they will be disabled.
[Google Pixel 6 Pro] Nekromantik:
do you only need the cleanslate app if you want the gesture controls?

will you add wakelock blocking?
[Google Pixel 6 Pro] TotallyAnxious:
You need clean slate app(s) for clean slate features.

Which does not effect stability. Maybe minimal increase in battery usage.

You don't get kernel updates quicker or a more smooth experience if you don't use, as someone else above implied.
[Google Pixel 6 Pro] Exel:
That's not what I implied, I implied I use this kernel for a smoother experience and faster upstream updates rather than waiting on Google's monthly patches, not for gimmicky features (not that some people don't use them, they're just not for me.)

I didn't say that if you don't use CleanSlate features it would be smoother or be updated faster.
[Google Pixel 6 Pro] liver20:
Kernel support kcal?
[Google Pixel 6 Pro] TotallyAnxious:
This is off topic. Using clean slate features wouldn't effect updates of anything.

Wrong to say otherwise in anyway.

You said "Side note, if we don't care about the CleanSlate tweaks just better stability, faster updates and battery life, just don't install the app and all of those features should be disabled by default?"
[Google Pixel 6 Pro] Exel:
I never said it did, but agree to disagree -- it's easy to misinterpret posts, let's stay on topic here. :)

Day 1 of using this kernel and so far so good.
[Google Pixel 6 Pro] Jhoopes517:
So, I attempted to flash version 1.3 on my Pixel 6 and keep getting bootloop in to bootloader.

Downloaded all 1.3 images from afh.

Grabbed Vendor boot from latest OTA on google's servers.

Started with

fastboot flash vendor_boot vendor_boot.img

then followed the rest of the instructions from the OP but no go. Tried wiping to confirm not issue with data and no go.

Any suggestions?
[Google Pixel 6 Pro] Freak07:
you need the cleanslate apps, if you want to control the cleanslate features.

wakelock blocking maybe, which wakelock(s) do you want to block?

The latest release has two wlan wakelocks already removed from the wifi driver, that I could attribute to a lot of wakeups.

CleanSlate config app does nothing, except modify a file that has the configuration. It doesn´t affect battery life in any way.

CleanSlate companion app takes less cpu share than enabling any of the battery monitors in EXKM or FKM. So it´s next to nothing.

no, not at this moment.

KCAL is implemented on drivers that are used on qualcomm based phones.

Answered previosuly here:

https://xdaforums.com/t/kernel-20-1...pixel-6-pro-aka-raviole.4358435/post-85906969

check the next posts too, another user found a few apps that made him happy and I mentioned CF-Lumen.

Were you rooted before attempting to flash this kernel? Did you already issue the vbmeta disable verity/verification command via fastboot?

your fastboot environment could be outdated.

always patch the boot.img via magisk on the device you´re flashing it on.
[Google Pixel 6 Pro] triggerhappy_:
Always manual. 80% all the time. Adaptive features are on except brightness and sound.
[Google Pixel 6 Pro] ctfrommn:
Question for one of the developer minded on here......Im trying to build my kernel for Bluejay (Pixel 6a) which is extremely similar to the Pixel 6/6 Pro and am using Googles/Androids method (https://source.android.com/setup/build/building-kernels). It seems very straight forward and Ive built literally thousands of kernels & Roms over the years but for some reason even building this bone stock results in a non boot situation.

Is there something Im missing with this device or method I should be aware of or is there a simpler way to do this? Ive historically just used my own build scripts but the repo structure of these devices is so different and there are so many modules loading that I figured I would try the AOSP approved method first

Thanks for any insight.
[Google Pixel 6 Pro] Utini:
Working fine on todays june update build 004.
[Google Pixel 6 Pro] Freak07:
yes it´s a new thing. I think it affects currently pixel 5 and later.

with the fastboot flag

--disable-verity --disable-verification

you should be able to either flash the vbmeta.img of the firmware you´re currently on (extract from factory image)

fastboot --disable-verity --disable-verification flash vbmeta_system_a vbmeta_system.img

or just flash the image-update.zip found inside the factory image of the firmware you´re currently on via

fastboot update --disable-verity --disable-verification image-update.zip

disabling those flags will completely wipe the device!!
[Google Pixel 6 Pro] ctfrommn:
Got it, thanks for your help. I think Ill just go the AK Zip route as that seems a lot simpler for the amount of flashing Ill be doing during development.

I feel like every new generation of Google device gets exponentially more difficult to develop for. I miss the old Nexus days where you could cook a kernel & ROM and flash it with no fuss....lol
[Google Pixel 6 Pro] Freak07:
if you compile a whole build from source, you don´t run into those issues, since the images from the kernel build match the rest of the firmware not tripping the avb check. :)

but yes I agree, it needs getting used to and next generation will have a few more changes... etc :)
[Google Pixel 6 Pro] ctfrommn:
Thats the plan, though building Roms for Pixel devices has been a much more difficult affair vs the Nexii. I would love to get Velocity fully up and running but I was unable (more like unwilling to spend the time) to get it done for the 3a.
[Google Pixel 6 Pro] xflowy:
@Freak07 little off-topic mate, but since you are my favourite dev here. will you be moving to the pixel 7 (or support it additionally?). i'm considering moving up in october.
[Google Pixel 6 Pro] Lughnasadh:
If I'm not mistaken, it affects the Pixel 4a5G (not the regular 4a) as well. Of course, I'm often mistaken 🙃
[Google Pixel 6 Pro] liver20:
Latest build works on Android 13 beta 4.1?
[Google Pixel 6 Pro] SkaboXD:
No build works for A13 beta nor he plans to make it work in the future as developer said. Wait for official Android 13, Kirisakura will get update compatible with it than.
[Google Pixel 6 Pro] ctfrommn:
One more question if I may.......what is the difference between the AOSP folder and the Private folder? It looks like both are used and I "think" the AOSP one is the one to modify? This file layout and format is completely non intuitive, especially compared to what Im used to.
[Google Pixel 6 Pro] Freak07:
I´m assuming you´re talking about the aosp folder from that manifest?

default.xml - kernel/manifest - Git at Google

that´s just the android common/kernel without any device specific stuff in it.

private/gs-google

private/google-modules

is what you want for the p6 kernel.

Go through the build scripts in /build and in private/gs-google to understand what´s happening. :)

thanks for the compliment, I feel flattered but I have no idea about the pixel 7 series. Depends how the devices turn out, price and a few other factors. so I can´t really give you an answer.

you´re correct I think as p45g and p5 are of the same generation iirc.
[Google Pixel 6 Pro] NLQuantumFluxx:
Sorry if this is a dumb question I've just returned to an android phone after like 3 years of being on iPhone.

Is there any way to flash this kernel without root? Or a kernel that can be flashed without root.

I can't be bothered with constantly trying to work my banking app around root, mines probably one of the worst for constant detections.

Thanks!
[Google Pixel 6 Pro] Freak07:
No way to flash or use this kernel without magisk root.

As soon as you unlock the device you won't pass safety net on stock firmware. So there's no way around root either as it's not root safetynet is being tripped from. So if you don't want to be bothered by safetynet troubles stay on stock locked bootloader.
[Google Pixel 6 Pro] ctfrommn:
Thanks, I'll take a look and see what's what, though scripts aren't really my forte and there are a lot of them.

Do I even need the AOSP folder then? Do I even need to build using this method or are you doing it on a more simple, elegant way?

I'm used to just simply building the Image and dropping it into the device folder of a full AOSP build and then make bootimage
[Google Pixel 6 Pro] Archie k:
works perfectly.thanks
[Google Pixel 6 Pro] DespairFactor:
yeah this is an android 12 bug, still happens on android 13, but a lot less.
[Google Pixel 6 Pro] dd805bb:
I have been on 13 awhile and this hasn't happened once to me. Now on beta 12L this happened all the time. Since 13 no issues like that. 13 beta is and was way better than 12L beta. 12L had a lot of issues in beta. 13 beta has had way less. 12.1 on my GF's 6a and my son's 5a, bootloader locked and stock, has issues to this day. GPS to unlocking and calling issues. Bluetooth issues. 12.1 is a lost cause. And within a month will be..
[Google Pixel 6 Pro] Ghisy:
I flashed the newest EMEA July update (SQ3A.220705.001.B2) and it seems like the kernel is working fine! Don't know if Google made any changes kernel-wise, probably not.
[Google Pixel 6 Pro] triggerhappy_:
How could I safely flash the new 12.1.0 (SQ3A.220705.004, Jul 2022) firmware being on the latest Kirisakura Kernel? Never done an update before, just curious. Appreciate.
[Google Pixel 6 Pro] Freak07:
No changes have been pushed, so I'm pretty sure by now there are none.

Either use factory image or full OTA zip to update. That's probably the easiest route. Both will just flash the updated stock firmware, so you're device will end up being on the new stock firmware.

Search the forums, there are guides on how to update. :)

Afterwards just follow the instructions to flash the kernel again if you desire to do so.
[Google Pixel 6 Pro] triggerhappy_:
So, afais, all I need to do is flashing the latest stock factory image.
[Google Pixel 6 Pro] Utini:
Any chance to make the phone less fragile to hot summer days?

E.g. by throttling more/sooner at a certain temp limit?

15mins on the lake (30C Temperature) of browsing in the sun and it will shut off connectivvity due to temperatures.
[Google Pixel 6 Pro] jericho246:
I feel your pain man.

This kernel has CleanSlate kernel features such as Battery saver which can be used to reduce heat. In my experience the difference was minimal, but maybe it'll be different with your usage. Worth a try I guess.

https://xdaforums.com/t/kernel-cleanslate-s1-4-4-s2s-adblock-vib-batterysvr-june-8.4364671/

You gotta install Clean Slate Companion app + the configuration app. Grant necessary permissions and then choose a Battery Saver level from 1 to 3, with 3 being the most aggressive.
[Google Pixel 6 Pro] Freak07:
Use CleanSlate battery saver during those conditions. :)

Edit: i was ninja'ed.

That limits only cpufreq though. Might not make the biggest difference, but still useful.

Running display at highest brightness, while being in direct sunlight, high ambient temp, mobile signal etc, it's just a matter of time until it gets hot.

Apart from that thermal throttling is not directly controlled by the kernel, but the thermal hal. That part is not open source afaik and I don't want to touch it either way.
[Google Pixel 6 Pro] Utini:
Thanks. I also just changed from "always dark mode" to "light mode during hot hours".

I hoped that the light theme heats up slower than the dark theme :S but more battery usage then I guess.
[Google Pixel 6 Pro] shizonic:
Is it safe to flash over the august update?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Probably not since @Freak07 was supporting the Stable Android version only, and not Android 13 Beta. Now that 13 is Final, I'd just wait.

But perhaps someone who enjoys risk more than me these days will test the theory! 😲😜
[Google Pixel 6 Pro] shizonic:
I see. Thanks.

Maybe I gonna be the one who risk it by tomorrow...
[Google Pixel 6 Pro] Freak07:
if you want to know if it´s safe to flash the A13 stable factory image over A12 firmware with this kernel installed, yes it is since it replaces everything.

if you want to know if the A12 kernel runs on A13, it won´t.
[Google Pixel 6 Pro] shizonic:
Thanks for clarifying.

Are you planning an A13 version of your kernel?
[Google Pixel 6 Pro] TheLoonyRebel:
I believe it was stated a few pages back that once A13 is final the kernel would migrate over to A13 as well.
[Google Pixel 6 Pro] shizonic:
Glad to here that. Thanks.
[Google Pixel 6 Pro] Freak07:
It seems I forgot to reply to this.

The kernel is now in more "places" than the boot.img and afaik nobody managed to build a monolithic kernel yet.

Given the kernel build environment I also don´t see a need here.

The parts of the kernel end up in boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img.

The aosp folder contains kernel/common, which is just the GKI kernel. If you just compile the zImage, you probably will need to force load the other device specific drivers which end up in vendor_boot (those that need to load early, plus dtb) and in vendor_dlkm to make them load.

Ideally you want to compile zImage, dtbo.img, vendor_boot and vendor_dlkm. That will give you a "full" kernel build on pixel 6 devices. This is also what the scripts do, you´ll end up with those images in the out/.../dist folder of the environment.

You can invoke the build with the scripts. private/gs-google and private/google-modules is where the kernel repos are.

Since my kernel changes abi as it´s very very far from stock, I need to generate new abi, otherwise build will fail. For example I do so with build/build_abi.sh --update.
[Google Pixel 6 Pro] Freak07:
indeed :)
[Google Pixel 6 Pro] Freak07:
soon :)
[Google Pixel 6 Pro] Sek0n:
Perfect timing. Just updated to 13 stable a minute ago, and saw the update get posted. Flashed and working so far. Thanks again! (y)
[Google Pixel 6 Pro] zyonee:
Awesome! Any chance we can have double tap2wake implemented in this kernel? I find the single tap to cause issues with the screen always waking up, just like lift to wake.
[Google Pixel 6 Pro] Mrcactuseater:
Very nice indeed 😉
[Google Pixel 6 Pro] cd993:
Just to be absolutely clear, would this be ok on latest A13 beta or is this strictly for stable only?
[Google Pixel 6 Pro] cd993:
I'd really like this too.

Mods like AOSP Mods for magisk have the feature, which kinda works, but it keeps the single tap I found and the double tap sometimes takes 3/4 double taps to wake up!

Would also love the classic double tap to wake to ambient screen, but realise this may be more a rom feature than kernel?
[Google Pixel 6 Pro] triggerhappy_:
Hello boyz and girlz, it's me again :p

Is it safe to use this scenario to update from A12 to A13 currently being on 3.0.17 Kirisakura?

Spoiler content hidden.

upd. figured it out thanks to Sek0n

going to "Update and Root Factory Image" from the main P6 thread.
[Google Pixel 6 Pro] spr33:
Thanks for the fast kernel update! Working behind the scenes on it for a while huh?

I'm currently testing using 1080p to see if there is indeed any battery savings to be had to make it worthwhile. Using custom DPI of 340 so that it scales nicely (to my eyes).
[Google Pixel 6 Pro] triggerhappy_:
Updated to A13. Flashed Kirisakura 4.1.0. Works perfectly fine.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.
[Google Pixel 6 Pro] hanschke:
will you support update json for franco kernel manager?
[Google Pixel 6 Pro] roirraW "edor" ehT:
The same solutions that worked for me on Android 12 Stable are working for me on Android 13 Stable. [How To Guide] Working SafetyNet with Pixel 6 Pro Android 12. I did have to wipe the Play Store's app data and cache for the store to show me as having a certified device, but I still passed Basic Integrity before that.
[Google Pixel 6 Pro] triggerhappy_:
Reinstalling SafetyNet Fix 2.3.1 in Magisk Modules seems to be working fine.

Spoiler content hidden.

But still I haven't DEVICE_INTEGRITY in Play Integrity API checker. upd. after cleaning cache, now it doesn't have even BASIC.

Spoiler content hidden.

The app is probably corrupted, others are just doing fine. Anyway.

Spoiler content hidden.
[Google Pixel 6 Pro] Utini:
@Freak07 is it still recommended to have verity/vbmeta disabled or can we safely enable it again (Android 13)?
[Google Pixel 6 Pro] DIXZ06:
@Freak07 thanks for the timely update. I have missed using your kernel since A13 B1 came out. It is good to be back in the "in group" again.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I haven't had mine disabled since last December or so. Still working great with this kernel on Android 13 Stable, as it has every month.