yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Israafil:
Hey guys i am facing an issue its indirectly a kernel issue. Whenever i use the powersave option in exm it doesnt effect core block 3, i always have to regulate block 3 manualy. Block 1 and 2 works flawlessly only block 3 does not react to a change in powersave mode. Anyone any idea if there is a fix for that missbehavior??
[Google Pixel 6 Pro] Freak07:
The powerhal doesn't allow for this to work. The powerhal changes max cpu freqs dynamically depending on certain scenarios.

That will overwrite the exkm settings. Nothing to do with the kernel itself.

However install the cleanslate config app and enable the battery saver mode. It will do exactly what you're looking for. You have three levels to choose from.

You can also choose if you want to limit cpufreqs on interactions or not.

Here's a detailed overview of the three levels:

Kirisakura_Raviole/drivers/cpufreq/cpufreq.c at f17f5173c265c52baf75c7d411477887c08160a4 · freak07/Kirisakura_Raviole

Contribute to freak07/Kirisakura_Raviole development by creating an account on GitHub.

github.com
[Google Pixel 6 Pro] Poesini:
Hey @Freak07 , been using this kernel with my Pixel 6 Pro for 1-2 days and so far it has been great!

I'm on December and I may ask if this has USB Fast Charging (For PC better charging) enabled or can it be? Sorry if this has been answered before but I didn't find anything

Thanks and great work :D
[Google Pixel 6 Pro] TotallyAnxious:
If you use USB c port on computer it'll likely charge over USB PD. Which is fast charging.

I don't believe it has that with USB A ports, as there's no toggle for it in ex kernel manager.
[Google Pixel 6 Pro] danw_oz:
@Freak07 Thanks very much for updating the kernel flashability!
[Google Pixel 6 Pro] john-aurelio:
DAfter having updated the kernel that corresponds to the month of January, I have a problem with the Bluetooth I don't know if anyone else has noticed itAfter having updated the kernel that corresponds to the month of January, I have a problem with the Bluetooth I don't know if anyone else has noticed it
[Google Pixel 6 Pro] roirraW "edor" ehT:
The most recent I see at the Android File Host download page is from December (v1.4.0). There hasn't been a January update at least there yet, since there is no January update for the Pixel 6/Pro yet.
[Google Pixel 6 Pro] Poesini:
You are right. Using the USB C from my Mobo charges faster (even faster than my Warp 30T [I know it doesn't work with that tech]), but it would be nice to still have it with USB A
[Google Pixel 6 Pro] john-aurelio:
OI mean, there is kernel there and I used the one on the date of January and I came back As of December I have no problem with Bluetooth
[Google Pixel 6 Pro] Zach Alt:
How easy is it to flash the stock kernel if you want/need to after flashing this?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Just flash the stock versions of the same partitions referenced in the manual installation directions - "Spoiler: Manual Installation for 1.4.0 and higher" in the OP. Otherwise, the installation directions are identical.
[Google Pixel 6 Pro] Lycidias:
Does this kernel need disabled verify and verification? I am just rooted and used the latest magisk canary on november build.

So I think both are enabled for me.

Thanks
[Google Pixel 6 Pro] roirraW "edor" ehT:
The information you're looking for is in this post, which I found by choosing the "Search This thread" button at the top of each page in a thread, typed verity as a search term, and for the username of posts to search in this thread I typed Freak07, then looked to see which search result was the most recent: https://xdaforums.com/t/kernel-16-1...pixel-6-pro-aka-raviole.4358435/post-86109665

It also turns out I could've just followed the link in the OP for the changelog to the most recent version:
[Google Pixel 6 Pro] darbylonia:
Thank you for including us girls! (in your intro) :ROFLMAO:

I have used your kernel on my Oneplus 7 Pro for a long time - excellent work!♥️
[Google Pixel 6 Pro] Burt Squirtz:
Oh man I'm so sorry to hear that from you brother. I'm sure you well aware this but the six pro is going to get dramatically better with updates.

In fact, I'm actually getting about 10 hours of screen on time. Finally, after about 8 days of usage. The adaptive battery just takes time to work. I'm not sure Tensor actually integrates and helps battery optimization, but I'm seeing incredible battery life finally. My suspicion is that it does.

The Google assistant and live translational alone -- is reason enough to get this device, in my humble opinion. It's a that much of a game changer.

The 6 Pro isn't perfect, but right now -- it's the best Android phone you can buy, bar none, overall. I feel the device isn't even remotely Fully optimized' yet.

A classic similar situation is the 9 Pro. It was very underwhelming when it was released. And now due to software upgrades it's effing incredible .

With some third-party apps, I've been able to make my six Pro screen look identical to my S21 Ultra or 9 Pro, to which has the best color reproduction I've ever seen On a Smartphone. The white point and vibrant colors look so nice now.

This device will get dramatically better. I would recommend sticking it out. But you're extremely intelligent Dev and I'm sure you've mulled this over very carefully.^^
[Google Pixel 6 Pro] Zilla0617:
Would you care to share which 3rd party apps helps with color reproduction? Thanks
[Google Pixel 6 Pro] Burt Squirtz:
Sure man. It's very easy. I used two apps to make the color look perfect.

1) I use an app called Color Changer Pro. ( A Google search and you'll be able to find this for free very quickly lol),

2) The other app is simply called Screen Balance Pro. Easily attainable by the same method mentioned above. I have the pro version. I spent hours and hours and hours calibrating everything so that it looks perfect.

Obviously there's some blatant subjectivity to setting desired color reproduction, but if someone wants me to upload screenshots of my exact settings I can do that^.

I also have a way of using third-party gestures for navigation, as opposed to the inbuilt ones. Why would I change that, you might be wondering? There's this really annoying two pieces of animation you get when you use the stock gesture navigation. There's this stupid brief translucent arrow when you swipe left or right edge of the screen. Also, there's this minimizing app animation that cannot be removed when you swipe up to home screen. My keen eyes and OCD simply aren't having this.

Instead I use an app that hides the normal navbar and I use third party gesture navigation apps like FNG. No stupid animations at all whatsoever, - and it's clean and lightning fast. Another large benefit to this - is it allows you to use a custom launcher like Nova, (which quite simply put - blows the stock pixel launcher out of the water), No more glitchy issues or launcher reversion, when you gesture.
[Google Pixel 6 Pro] Zilla0617:
Thank you, could you upload a screenshot of your settings. I would like to see how it compares to stock on natural setting.
[Google Pixel 6 Pro] Burt Squirtz:
Sure bro. Here are screenshots. One picture is the actual white point settings i inputted on Screen Balance, the other is the RGB values on Screen Balance, and the last one is the exact full color settings I use for color change of Pro. 👍

Obviously it makes the colors a lot more saturated - but that's what my eyes love. The saturation might take you off guard at first, but stick with it for at least 30 minutes. When you go back and look at your stock colored screen, you'll vomit.

I don't care about 'realistic' or 'scientific' color. I care about what makes the dopamine in my brain explode^. I don't care if the RGB values are supposed to be the most accurate of any device. Even that is a little unbelievable. Under stock color settings, blues are actually an off-purple. The richness, and vibrancy are completely missing. That was a clear indication immediately that the white point is fukked. I enjoy gaming and watching movies, and these color settings make everything look exceptional. Blues are vibrant blues now. Grays are grays. Reds are reds. Perfect contrast between AMOLED, black and colors.

There's no excuse, And it's downright mind-boggling as to why the pixel development team didn't add any wide color gamut or white point settings under display settings on the 6 Pro.

The stock color settings on the pixel 6 even under 'Adaptive' are so dull, washed out and sickly - with a horrendous yellow-piss screen tint. With these new settings, my screen color/contrast looks identical to the S21 Ultra and 9 Pro. In fact, it's It's definitively quite jaw-dropping with these changes have done for me.

EDIT: Believe it or not, i actually recommend setting initial color setting under stock settings to 'Adaptive', before applying these mods. Some people will be shocked by this, but highly recommended it.

EDIT 2: In my humble opinion, at the end of the day, having kcal kernel commit implementation is a slightly superior option. ( Unless Google adds white point and wide color gamut support in the future). For some reason K-Cal color saturation looks a tad better and more contrasty then this workaround I posted. Hence why requesting kcal or a similar implementation.

EDIT 3: One last important thing that's crucial to exemplify:

I highly recommend to setting the brightness of the screen in general to no lower than a manual 87%. In my personal And this is the sweet spot where the screen actually looks perfect with the color. 87% might sound high, but Google's 87 is more like a 65 or 70 on most other flagships.

I've never liked adaptive brightness - as it never quites get the brightness that your brain wants, or appears optimized and beautiful .However , I've been told with tweaking, The device brightness could eventually get perfect to what your brain desires.
[Google Pixel 6 Pro] joban727:
So I followed exactly the steps and I get google logo booting screen then stuck in bootloader. Did I miss something?
[Google Pixel 6 Pro] Burt Squirtz:
Did you enable any of these in accessibility settings? Did you allow proper permissions? You have to do that.

These apps are completely safe and will not cause a boot loop. I've been using them for about 2 years. Something else is going on.

Also which sites did you download the apps from? Of course some sites could be sketch. If you PM me I'll tell you the exact sites where I got them from. I'll get in trouble if I post them here.
[Google Pixel 6 Pro] Zilla0617:
I am unable to see the extra settings under color changer pro specifically hue, sat, blk, wht
[Google Pixel 6 Pro] Burt Squirtz:
You have to have the pro version of screen balance.

1)In the upper right hand corner, click the three dot menu in Screen Balance.

2) Then, click 'color mode'. This is where you can cycle between the RGB and white balance settings. I don't recommend touching the 'hue' settings, whatsoever. That's actually set perfectly. If you try adjusting it, you'll see what I mean. Instantly makes the screen look like sh1t, even if it's one point above or below.
[Google Pixel 6 Pro] joban727:
Sorry I was talking about flashing the kernel. Thank you for trying to help tho! =)
[Google Pixel 6 Pro] Burt Squirtz:
Haha, doh! My bad.
[Google Pixel 6 Pro] joban727:
Now I am trying flash the stock files from factory image and I get sending 'vendor_dlkm' ok writing 'vendor_dlkm' failed (remote: 'No such file or directory') ugh I cant get it working now please help!
[Google Pixel 6 Pro] Burt Squirtz:
Make sure you're in fastbootd. That's the only file that should be flashed in FastBlootd.

Adb command: Fastboot reboot fastboot.

After flashing vendor-dlkm, Make sure you reboot back into normal fastboot:

Fastboot reboot boatloader.

I wouldn't flash the Magisk patched image until you've fully booted into the OS. Then go back to fast food and flash the patched magisk boot.
[Google Pixel 6 Pro] joban727:
Yes I am in fastbootd and i tried different usb cables and different pc and still same problem. I looked at my slot and it says im in A.
[Google Pixel 6 Pro] Jindivikk2:
Use a different version of fastboot. It happened to me too

Try the portable version from here

https://xdaforums.com/t/tool-windows-tiny-adb-fastboot-august-2021.3944288/
[Google Pixel 6 Pro] joban727:
haha thats the one I am using but ill try another one now. I flashed vendor_boot and that worked fine but whenever i do the dlkm one it doesnt flash
[Google Pixel 6 Pro] Jiggs82:
Hey @Freak07 it's good to see u in the 6pro forums I remember flashing ur kernel for 3xl 😁👍🏻 just curious and sorry if this has been answered already but could this kernel be flashed through ex kernel manager app? Or will there be a flashable zip? Thanks in advance
[Google Pixel 6 Pro] Burt Squirtz:
I had the same problem until I realized it has to be the exact dead on accurate verbatim label. It wouldn't flash for me either because I decided to put an extra word before the word 'vendor' to make it easier to see/ find amongst a sea of other OTA package files I had in my ADB folder. So it must be verbatim exactly as it's shown.

As simple as it sounds, my brain had a hard time wrapping my head around it as I was able to label the DTBO or boot images to anything I felt like, (i.e. 'Kirisakura_DTBO.img) , ( fastboot flash DTBO kirisakura_DTBO.img, for example), And they flashed just fine.

This is not the case for vendor_DLKM though. Make sure you type it exactly as it's supposed to:

' Vendor_dlkm.img '

Also, I realize I'm being captain obvious here, but make sure you put ' .img' directly after dlkm.
[Google Pixel 6 Pro] joban727:
really loosing my mind with this lol i tried everything you guys mentioned.
[Google Pixel 6 Pro] Freak07:
don´t flash 1.4.0 on November build. It´s made for december and won´t boot on november firmware.

If you´re running November firmware you need to flash 1.3.0, which can be found in the download section and by following the instructions in the OP for version 1.3.0 and below on the bottom.

1.3.0 is not in a flashable zip format, but instead you need to flash the images provided following the download link.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Oops, glad you noticed that.

To spell it out for @Lycidias, Verity and Verification *do* need disabled (and you'll have to factory reset) in order to use the 1.3.0 kernel, but if you manually update to the December firmware (third link in my signature below), then you can use the 1.4.0 kernel and not disable Verity and Verification.
[Google Pixel 6 Pro] Freak07:
I think it should work to not disable the vbmeta flags on 1.3.0 if the boot.img provided in the download section is patched with magisk 23016 and the instructions are followed correctly.

Same as patching stock boot.img with magisk 23016 works on the november build as is seemingly confirmed by @Lycidias previous post.

There shouldn´t be a difference between stock boot.img and the boot.img of my kernel if magisk 23016 is used, that´s why I´d assume so.

However I´m not able to confirm this 100%, since I´m no longer on November firmware and have the vbmeta flags still disabled from when I rooted initially.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Okay, thanks. It's a confusing situation. I got the below response regarding this subject and @Freak07's kernel:
[Google Pixel 6 Pro] Lughnasadh:
I think the difference is that there is no flashable zip for 1.3, so the 3 separate images have to be flashed. But patching the provided boot image with Magisk 23016 before flashing should bypass the need to disable verity & verification.

1.4, however, has a flashable zip with the magiskboot binaries updated to 23016.
[Google Pixel 6 Pro] Freak07:
yes, it´s ultimately related to magisk, but it also affects the kernel.zips.

If magisk 23016 is used to patch/repack the boot.img vbmeta flags don´t need to be disabled as there´s a commit that removed the need for this.

So if somebody manually patches a boot.img with magisk 23016 or flashes a kernel.zip with magiskboot binary (which the kernel.zip uses to essentially switch out the zImage) updated to magisk 23016 vbmeta flags don´t need to be disabled.

If the kernel.zip contains however magiskboot 23015, the user will end up in a bootloop as magiskboot 23015 needs the vbmeta flags disabled, even if the user previously rooted fine with 23016.

If the user flashes 1.4.0 on November firmware (that´s no longer possible as it should abort, since I updated the kernel.zip a few days ago) there will be a bootloop.

There´s no flashable kernel.zip for 1.3.0 (which works fine on November firmware) so the user needs to manually patch the provided boot.img with magisk 23016 and flash all provided images via fastboot/d at the moment.

It´s a bit of a confusing situation, with vbmeta, the magisk canaries and now the removed firmware images for December firmware...
[Google Pixel 6 Pro] Lycidias:
Thank you very much for the great support and the detailed answers ☺️

So I'll wait for the upcoming january update (and probably the corresponding kernel update?) before flashing this beauty.

I want to flash it as a flashable zip and do not want to do a factory reset. For my understanding I don't need to disable the verify and verification flags for future kernel updates with the latest magisk canary?

All a bit confusing. Wasn't that complicated on the phones I had before 😆
[Google Pixel 6 Pro] Freak07:
That's probably the easiest solution if you're patient enough :)

Or try to see if somebody has a mirror of the December factory image, update to December and flash 1.4.0.zip :)

If you're brave patch boot.img 1.3.0 with magisk 23016 or higher and flash all images according to instructions. Maybe someone did and reports back here. Maybe it's not possible, but I can't confirm to be absolutely sure.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thanks! I must've been confused and thinking that I was responding in someone else's kernel thread. Oh crazy me! :)
[Google Pixel 6 Pro] Artemka2008:
January build is here: link
[Google Pixel 6 Pro] nummer:
january builds are here! keeping a sharp lookout for when this kernel gets updated...
[Google Pixel 6 Pro] Freak07:
just a heads up. there´s no january source code released yet and it´s getting late here.

Working day for me tomorrow, but I´ll try to update the kernel as soon as possible once January sources are released.

In the meantime the 1.4.0 zip works fine for me on January update. There seem to be not that many kernel changes as the stock kernel still has a November build date. :)
[Google Pixel 6 Pro] Prey521:
Sweet, I'll wait till your official update is out!
[Google Pixel 6 Pro] Jerreth:
unable to flash update via flash-all.bat gets stuck at boot partition missing or some such thing anyone else having that issue?

AHAHAHAH!!! i found it i guess that the Fastboot stuff i had in my path was old i just plopped the latest fastboot files in to the image folder and boom its working sorry for off topic by the way
[Google Pixel 6 Pro] Jiggs82:
I can confirm v.1.4.0 works fine with January update 👍🏻 looking forward to the new release tho.
[Google Pixel 6 Pro] :
Yes flashed it too, it works fine.
[Google Pixel 6 Pro] KedarWolf:
Boot failure, but on a dirty flash of the January factory image using the below method and flashing the kernel with the EK Kernel Manager.

Rooting with the newest Magisk.

https://xdaforums.com/t/method-to-u...thout-wiping-data-and-retaining-root.4356065/
[Google Pixel 6 Pro] :
I was on December build.

1. dirty flashed January Update

2. Patched the stock boot image with latest magisk canary and flashed it

3. Installed kirisakura 1.4.0 with exkm

Works fine so far.
[Google Pixel 6 Pro] KedarWolf:
What version of Magisk are you using? The one made for the December build?
[Google Pixel 6 Pro] KedarWolf:
Nope, I'm doing everything right. Right Magisk, on dirty flash after installing the kernel, boot failure. I'll wait for an updated kernel. :(
[Google Pixel 6 Pro] KedarWolf:
I had an older version of 1.4.0. Downloaded the updated one, fixed now. :)
[Google Pixel 6 Pro] Freak07:
Update to 1.5.0

Hey guys and girls,

I hope everybody started into a Happy New Year 2022. I´m very happy how this project turned out so far. The kernel runs absolutely great and despite many complaints I don´t really had a single issue on my pixel 6 pro. Luckily it seems my carrier and the bands that are used for network were unaffected by the bug that plagued a lot of users.

Aside from that I´m also very happy how this thread turned out so far. There seems to be some sort of community spirit that I´m missing often lately on XDA, people help each other and there´s a friendly constructive atmosphere. Big thanks to @roirraW "edor" ehT who constantly pops up here and helps other users and everybody else contributing one way or the other too.

I´m giving my best to reply to questions in a timely manner, at least as timely as my time allows, so it´s great to see this thread evolving over time and everybody helping each other. Thank you all for that and keep it up.

Alright here´s the next update then. :) There were only very minimal changes to this kernel in the January Source drop, but I managed to squeeze out two builds before I have to leave for work. :)

The mechanism that prevents small tasks to cause frequency spikes is now tied into the powerhal. That means when interaction is needed (app launches, camera launches, interaction) this mechanism is toned back as the device gets boosted anyway.

In all other cases the mechanism now gets more strict to prevent frequency spikes, videos, audio, navigation etc.

Next release will probably have a few more very interesting changes that are currently under testing so stay tuned. Didn´t think google would drop this before Monday.

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

Download is below.

Updated instructions in the OP!

Changelog:

- January Source update merged

- linux-stable 5.10.91

- use latest google prebuilt clang 14.0.1 for compilation

- improvments from kernel/common

- tie "prevent frequency spikes caused by small tasks into the powerhal"

- add latest CleanSlate features and updates (huge thanks to @tbalden, if you enjoy these features maybe buy the apps from the playstore to give a bit of support :) )

- other changes please look at my github

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.

If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_boot.img and vendor_dlkm.img before flashing. Thank you.
[Google Pixel 6 Pro] Lycidias:
Thanks for the fast update ☺️

Any hope you'll could provide a FKM json config ?
[Google Pixel 6 Pro] Freak07:
No i like to keep track of the download count via android file host.

I also want everyone to read the release post before flashing the kernel as it will ideally prevent issues if it's read before flashing.
[Google Pixel 6 Pro] Utini:
So to update there are three methods now?

1. Old way prior to 1.3.0

2. New manual way (which can either be done via ADB of exkm)

3. The .zip file to flash via e.g. exkm

Is that correct?

Also: If I currently have verity disabled, does flashing the kernel still work or do I need to enable verity first (which will factory wipe the device)?
[Google Pixel 6 Pro] :
Keep it disabled, it works flawless
[Google Pixel 6 Pro] Utini:
But doesnt that pose a security risk then?