yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Freak07:
Update to 1.7.0

Hey guys and girls,

So here´s the next update. It includes the february security update. Most of the changes brought by the February kernel source drop, were already included in this kernel by merging kernel/common and linux-stable.

Several other notable improvements and changes in this release:

Improve f2fs performance by merging a patchset to prevent writer starvation for the checkpoint thread. This was discussed this month in the f2fs mailing list and is already merged to the kernel/common tree. It´ll improve performance under heavy I/O utilization.

You can find more information following the discussion here.

Necessary backports were brought to the kernel and the platform specific f2fs-implementation was also adjusted.

Latest f2fs-stable was also merged to the kernel.

Update the patchset to prevent frequency spikes caused by small tasks as well. Tie those new changes into the powerhal. (That means users not flashing the kernel.zip, but instead use the manual installation method, which are only a handful from the download count, need to flash the updated magisk helper module. Users that flash the kernel.zip via FKM/EXKM have to just flash and forget)

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

Download is below.

Updated instructions in the OP!

Changelog:

- February Security update merged

- linux-stable 5.10.96

- include latest f2fs-stable

- improvments from kernel/common

- fix memory leaks

- security related patches

- mm improvments

- for details please check github

- introduce unfair f2fs rwsems to prevent writer starvation and improve IO perf

- update patchset to prevent freq spikes caused by small transient tasks (also tie this into powerhal)

- give pelt multiplier power hint for scheduler performance boost during fingerprint unlock

- fuse: give wakeup hints to scheduler to speed up compress/decompress in internal storage (details)

- enable RCU_BOOST (details here), also fix RCU_BOOST behaviour

- update LRNG implementation (thanks to arter97 )

- improvements/fixes for CleanSlate features

- 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] DanielF50:
Flashed - up and running perfectly, thanks!

Just curious, any particular reason for jumping from 1.5.0 to 1.7.0 in version numbers?
[Google Pixel 6 Pro] keaheng:
Can i just use the magisk module with stock kernel?
[Google Pixel 6 Pro] Freak07:
No, it now contains sysfs/proc endpoints that are not implemented in the stock kernel. It'll spam the logs with errors and won't work properly.

It's meant to be used with the matching kernel release here as structured in the download folder.

No specific reason.

It's a rather big update with lots of improvements. During testing I ended up with 1.6.x close to 1.7.0, so I just bumped it to 1.7.0 for the release as it's not "just a merge February google code"-release.
[Google Pixel 6 Pro] avid_droid:
Flashed and going good so far. Thanks for your work.
[Google Pixel 6 Pro] Sek0n:
All seems to be running smooth with the update on the latest release. Thanks for the work (y)
[Google Pixel 6 Pro] bouchigo:
Anybody using this kernel on the latest crDroid build?
[Google Pixel 6 Pro] jlokos:
I updated to February firmware and rooted the stock kernel; I then flashed 1.7 with fkm; when I rebooted I was unrooted. I attempted to patch 1.7 with magisk, but got an error message. I never had either of these issues before. Any thoughts on what I might have done wrong?
[Google Pixel 6 Pro] Reechings:
Maybe magisk version? I did exact same thing and had no issues
[Google Pixel 6 Pro] jlokos:
I'm using 24102.
[Google Pixel 6 Pro] Reechings:
Weird, that's the exact one I used to patch my boot image
[Google Pixel 6 Pro] foobar66:
No issue for me on this version.
[Google Pixel 6 Pro] avid_droid:
Noticed 1.4%/hr deep sleep idle drain overnight....
[Google Pixel 6 Pro] Utini:
Proxyhandler bug? Turn airplane mode on, reboot, turn airplane mode off

Kernel works great on february update here.
[Google Pixel 6 Pro] jlokos:
I downloaded another copy of 1.7 and flashed it. Everything worked. I must have had a bad download the first time around.
[Google Pixel 6 Pro] avid_droid:
I'll try again when I have some free time. Came back to stock kernel for a bit. Thank you
[Google Pixel 6 Pro] Freak07:
you´re welcome :)

It´s not the kernel. Might be an app in background, some service running in the background, after flashing a firmware update ART cache gets optimized in background.

Sometimes a reboot fixes an app or service acting up. ART optimization just takes a bit of time.

From yesterday to today during the night I lost 2% over 8 hours, which is what I´m usually seeing. Between 2-3% over 7-8hours.

Glad that it worked out for you. That´s what I also would have suggested.
[Google Pixel 6 Pro] avid_droid:
Impressive if only 2% was lost. Will give it another go soon.
[Google Pixel 6 Pro] k1209844922:
Hello, Do I have to swipe back to the original kernel every time I update the system? I update the prompt error, or do I have to use the version 1.7 to update the system?
[Google Pixel 6 Pro] Freak07:
Yeah the 6 Pro is a nice phone, I´m very happy with it.

That´s also mirroring what I was getting on the stock kernel. Since I got the phone I lost 2-3% each night like clockwork. (Except during vacation where we had extremely ****ty reception, where the phone barely got 2G mobile network, which cut off every few seconds. Then I lost way more during a night, which is expected)

If the device sleeps fine, it sleeps fine overnight. The kernel doesn´t do much there. If there are apps installed that constantly wake the device requesting wakelocks, the kernel can´t do much about this. If network coverage is bad, you´ll also face higher power consumption.

I have 2 google accounts syncing, wifi is connected, mobile network is enabled, bluetooth is enabled but not connected. I don´t restrict any background usage of any app or disable location usage etc.

But it seems many others aren´t that lucky looking around different threads on the forum here.

If you´re phone is modified in any way, for example by being rooted, you can´t take an OTA. That´s not strictly related to the kernel.

Use any of the guides found on this forum to update the phone to the new firmware by either using the android flash tool, flashing a factory image or a full OTA.zip. If you´re new to this, make sure to read the guides before and understand what you need to do.
[Google Pixel 6 Pro] Freak07:
Unfortunately it seems that for now it´s not possible to build a kernel that will boot A12L and A12 at the same time. There are some driver changes which are tied to changes in the firmware that don´t play well with each other.

So for now I´m probably going to stick to stable A12, as that´s what I´m running myself (and I´d assume most others will run as well) and only merge those parts from A12L that are compatible with A12 february firmware for the next release.

I´m not sure if I want to go through the effort to maintain two builds of this kernel, one for A12 and one for A12L as this kernel is not very close to stock, so it ends up in a lot of additional work.
[Google Pixel 6 Pro] sunnybwoy1:
Using proton with Jan update which version should I use thank you
[Google Pixel 6 Pro] Freak07:
1.5.0 is the update, that merged the January source code and matches what proton is based on I assume. So that would be the safer one to flash.

1.7.0 has February source included. I think it should work fine as well.

Make sure to have a backup of the partitions described in the FAQ handy in case you run into trouble.
[Google Pixel 6 Pro] Roll3r:
Just an FYI (because others have asked), the only ACC (Advanced Charging Controller) charging switch with working battery idle mode is:

gcpm/constant_charge_current_max 1866420 0

Several other switches tested as supported idle, but they'd all crash ACC when idle priority is enabled. You may have to add it manually.

Edit: I shouldn't say "only" - this is the only switch (supported by this kernel) that I found get the phone to idle with. There might be others out there, too.
[Google Pixel 6 Pro] Alxoom33:
Hi, nice to see you are developing kernels for the Pixel 6 Pro. Are you supporting A12L Beta. As you may know, 12L Beta 3 is out for the Pixel 6 series, as of yesterday.
[Google Pixel 6 Pro] avid_droid:
Read a couple posts above.
[Google Pixel 6 Pro] eg1122:
This is answered by the OP 4 posts above yours.
[Google Pixel 6 Pro] jjblaster3:
Completely understand your decision, it's definitely not worth the extra effort if you are going to be sticking to stable A12 in the near future.

For what it's worth I would say the upgrade to 12L has been worth it for me after seeing so much positive feedback about it in the 12L thread, but I'm sure most others would rather run the stable A12 release like you said.
[Google Pixel 6 Pro] wanttotree:
Okay, this amazing kernel just made my phone ice cold yooo. Thanks man.

Just wondering if the ak3 helper module is the same with the powerhint module.

Also, is the powersave option work well to squeeze more battery life? Quick explanation on my gps usage. I use waze almost daily for traffic mitigation, 50/50 split with screen on and off. Will the powerhint module override the powersaver from the config app?
[Google Pixel 6 Pro] Texan1:
If you have time @Freak07 , would love to see you attempt a one-off 12L kernel without any expectations of having to update/maintain it for a month or so before the official release 🙏
[Google Pixel 6 Pro] jac0b:
Looks like this switch works on Despair kernel also. I'll try it out tonight. Thanks
[Google Pixel 6 Pro] Roll3r:
Good to know! I was going to try and figure that out but didn't feel like going thru hours of trial & error again
[Google Pixel 6 Pro] jcp2:
@Freak07 Does this kernel have/allow native exFAT support?
[Google Pixel 6 Pro] Freak07:
Nice catch. I´m sure other might appreciate this. Thanks for sharing here.

yes, the ak3 helper module is the successor to the separate powerhint_module and includes everything that was added there. you don´t need to flash the powerhint_module at all if you flashed the kernel via the kernel.zip method.

No, the batterysaver option in CleanSlate config app, imposes hard levels on the kernel side and will overrule the powerhals max boosting.

You can try to set it to the highest level of powersaving, while still allowing the powerhal to boost in touch input9s (toggle battery saver, level 3 saver, do not toggle touch limiting option on).

You should be also able to add a QS tile for this, in case you don´t need this except for driving.

https://xdaforums.com/t/kernel-08-0...pixel-6-pro-aka-raviole.4358435/post-86270411
[Google Pixel 6 Pro] Freak07:
Android 12L Kernel

Hey everyone,

since there were a few requests about a kernel for Android 12L here´s a build. It will be provided as mentioned in the post I linked.

The build is confirmed booting by a tester and everything should be working just fine, but that´s where "support" stops at the moment. I lack the time to flash Android 12L and switch between Android versions.
[Google Pixel 6 Pro] Divine Bicycle:
Does the kernel require verity to be turned off if I was to flash it through FKM?
[Google Pixel 6 Pro] Freak07:
you shouldn´t have to disable the vbmeta flags as the zips includes the latest magiskboot binary.

It has nothing to do with the kernel, it´s a magisk thing. Since the kernel.zip relies on magiskboot for repacking the boot.img, it´s connected though.

however some people run into verity issues, as described in this thread, but that has nothing to do with the kernel itself as something else is messed up when this happens. (there are speculations on the thread as to the why and what´s happening)

Personally I´m running with verity disabled since I got the device, but mainly for convenience and debugging purposes so I can flash whatever images I want on my devices without the need to rely on magisk etc.
[Google Pixel 6 Pro] Divine Bicycle:
So if I'm using Magisk with verity and vbmeta enabled then I should be good to go right? Also how does this work when there are system updates, can I still just use the Android Flash Tool and then just re-root and finally reinstall the custom kernel?
[Google Pixel 6 Pro] Freak07:
You should be good if you use the latest magisk available. But just wanted to warn you that people seem to run into issues with verity even if they use the latest magisk and seemingly tick all the boxes to make it work.

If there´s a system update you flash it either via factory image, full OTA zip or the android flash tool,that´s correct. It´ll overwrite everything, you re-root and flash the kernel again, that´s also correct. If you don´t want to face issue it´s always better to wait until I have updated the kernel with the source for the latest firmware.
[Google Pixel 6 Pro] wanttotree:
Thanks for the quick reply. Sounds like it could benefit my usage. Cheers.
[Google Pixel 6 Pro] DanielF50:
No issues to report using 1.7.5 on 12L - been installed most of the day so far and is working great 👍
[Google Pixel 6 Pro] scloutkst:
1.7.5 on 12L working just fine and dandy.

Sidenote. The pixel 6 series should have been delayed until 12.1/12L was finished. My phone finally works properly. They definitely needed extra several months to work out all the problems.
[Google Pixel 6 Pro] Israafil:
So when a new version is released i dont have to patch the boot.img with magisk, i can just flash the kernel, it patches boot.img with magisk boot.img right?
[Google Pixel 6 Pro] john-aurelio:
yI haven't had to use the truth, just installed magisk, patching and fkm To install the kernel
[Google Pixel 6 Pro] scott.hart.bti:
That seems to be the general feedback ... Tempted to switch over...

Especially since we got some custom kernel goodness to go with it 👍
[Google Pixel 6 Pro] Jerreth:
I made the leap and it is so much smoother than the stable 12 release all around no overheating, haptics are really nice, just where it should have been from the start. i really hope that 12 non L gets this way as i would love the constant updates/support for the kernal from @Freak07 Also no wiping required for me anyway the ota went well and i was able to root again easily.
[Google Pixel 6 Pro] scloutkst:
12L will be the next general release of Android for pixel phones. Should be the march update.
[Google Pixel 6 Pro] Jerreth:
almost bummed i moved to 12L as going back will wipe the phone i believe maybe ill try backing it all up then flashing it like i normally would from the image file with the -w removed and see what happens lol

also sorry bout the Off Topic here :)
[Google Pixel 6 Pro] Az Biker:
Very cool of you to supply a one-off kernel based on a few requests.

Very cool.
[Google Pixel 6 Pro] MArtyChubbs:
Same here. Great work as always @Freak07
[Google Pixel 6 Pro] Freak07:
if you use the manual installation method you need to patch the boot.img prior to flashing it via fastboot every time.

If you´re already rooted and decide to flash the kernel via the kernel.zip method, root will be preserved.

Happy to hear that it´s working fine on your end. :)

Thanks for the kind works, I really appreciate it.
[Google Pixel 6 Pro] Maverick Jester:
My Pixel 6 Pro is arriving tomorrow (fingers crossed) so I literally just popped into the thread to check support for Android 12L. I've read too many good things about it to want to stay on regular 12.

Appreciate you bringing kernel support on your end.
[Google Pixel 6 Pro] Nightf0x_007:
updated my p6 to feb. update and flashed magisk and all went fine but device bootlooped when i flashed 1.7.0 kernel and now i get the device corrupted storage message (flashed kernel via fkm)

i disabled verity and dm previously when i was flashing jan. update last month and i wiped my device and started from scratch (the same happened again now and i dont want to wipe the phone again)
[Google Pixel 6 Pro] Freak07:
unfortunately I can´t help you. I guess from your message you didn´t disable the vbmeta flags when you flashed the feb firmware?

There should be no problem doing what you did, but something verity related got messed up.

Thread below has some speculation/guesses around it:

https://xdaforums.com/t/pixel-6-pro...his-link-on-another-device-g-com-abh.4400091/

I don´t know any good advice, it just seems to happen to some.

You should at least be able to flash back the stock kernel (magisk patched boot.img, if you want to end up rooted )and restore the other images (dtbo, vendor_boot and vendor_dlkm) as mentioned in the FAQ at the beginning of the thread here to get back a working device.
[Google Pixel 6 Pro] Nightf0x_007:
So there is no way to install the kernel? I reflashed factory image without wipe and re rooted and i will keep using my phone like this will ignore the corrupted device error
[Google Pixel 6 Pro] Lughnasadh:
Just curious, did you disable verity and verification when you flashed the Feb. firmware?
[Google Pixel 6 Pro] Nightf0x_007:
No, but when i wiped and flashed jan. Update last month i disabled them
[Google Pixel 6 Pro] Lughnasadh:
Ok, so that means they were enabled after you flashed the Feb. firmware because to keep them disabled you have to disable them each time you update or they will automatically become enabled.

Thanks for the info ✌️
[Google Pixel 6 Pro] Freak07:
I don´t think there´s a way. you could try to flash a full OTA.zip via sideload and see if that fixes whatever verity related is wrong on your device, but so far the only thing that helped is wiping completely, which also brings back verity to normal.
[Google Pixel 6 Pro] bush911:
according to my little understanding, once you disabled the flags for once, you'd better disable them again every time you flash the full factory image if you are still planning to install the third-party kernels because every time you flash the full factory image, the flags will be enabled by default.

It seems that only the first time disabling will lead to the wiping of data.
[Google Pixel 6 Pro] Nightf0x_007:
If i update monthly by flashing factory image should i disable each time dm verity ?, Can u tell me how to update via sideload will give it a try, really want to use kiri kernel and i dont want to wipe my device 🙈
[Google Pixel 6 Pro] DanielF50:
We are getting off topic here again, but yes. If you have previously disabled verity & verification, you need to modfiy the flash-all.bat file command to keep them disabled each update. Disabling verity and verification isn't needed anymore so If you're starting afresh, I wouldn't recommend disabling them as keeping them stock makes it easier to update.

To update via OTA, you can download the OTA files listed here, then just sideload the OTA in recovery (adb sideload <filename>). I assume you know how to get into recovery, but if not just follow the instructions found here.
[Google Pixel 6 Pro] Freak07:
If you want to keep verity disabled, you have to use the " disable command" found in the guide threads everytime you flash a full firmware update to your phone, which contains a vbmeta.img (so updating via android flash tool (i believe this has options to disable verity flags though, but i never used it, a factory image or a full OTA.zip).

You can flash the full OTA.zip from recovery via adb sideload. Please use one of the guides around to check the procedure for this. I don't think it will fix your issue, but it might be worth a try.

If that doesn't i don't know any other way that would not require a wipe.

It's also hard to "recommend" something specific to anyone. It's your choice to either keep verity enabled or disabled. And it seems nobody knows why some people run into the issue you're facing with verity enabled, while others don't.

I personally disabled verity when I got the device and kept it disabled every update for development purposes, so I'm not relying magisk to flash anything else than stock to my phone.
[Google Pixel 6 Pro] jimbo77:
@Freak07 could you please add/enable NTFS support to your kernel ?

I have already created a magisk module to access exFAT OTG drives and it's working nicely but no support for NTFS can be tested since it's not enabled in the latest kernels.

Thank you!
[Google Pixel 6 Pro] Freak07:
The open source NTFS driver is pretty much useless, since it only supports RO operation, even then it can be wonky.

I can enable support for RO, but it's very basic and will not be of much use.

The write support i won't enable as there's a warning about issues and RW support only lets one replace the same file, with exactly the same length. (Which renders it useless for most anyway i guess)

Kirisakura_Raviole/fs/ntfs/Kconfig at 02ab270a98f627bb05a435d5be21f868876744d6 · freak07/Kirisakura_Raviole

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

github.com
[Google Pixel 6 Pro] Krasendo:
Can anyone confirm that the kernel works after the new OTA?
[Google Pixel 6 Pro] Gordietm:
It works.
[Google Pixel 6 Pro] Neurom67:
Yes works fine
[Google Pixel 6 Pro] Freak07:
As already stated 1.7.0 is fine to flash on the new February firmware. No changes on the kernel side.

Flash away :)
[Google Pixel 6 Pro] nilhem:
nice work
[Google Pixel 6 Pro] State.of.mind:
No you no longer have to disable this especially if you're using the latest Canary build of Magisk.
[Google Pixel 6 Pro] Poesini:
I tried to manually flash 1.7.0 on ProtonAOSP (don't have GAPPS, so can't instal FKM/EXKM) and can't boot after... Had to rollback
[Google Pixel 6 Pro] irule311:
Hey there, is there any way to build without running `repo init -u https://android.googlesource.com/kernel/manifest -b android-gs-raviole-5.10-android12-d1 && repo sync`? Reason being is that repo syncs 16GB of files over and fills Github Actions runner's disk space. How much of that is actually needed to compile the kernel? Are you aware of any other method to compile the kernel with a lightweight toolchain?
[Google Pixel 6 Pro] DespairFactor:
you can manually pull all the repos, but what is the point? You need every part of the manifest.