Development [Kernel][12.08.2023][Android 13.0.0 Stable]Kirisakura_Raviantah 1.1.4 for Pixel 7/Pro aka "Pantah"

[Freak07]

If i use a log silencer magisk module, will that affect the kernel/companion in any way?

I wouldn't use any module like this.

I remember when Samsungs were first rooted with magisk, some models needed this because the log space would fill up. On pixels not so much. The log space doesn't run out. I believe most those are also not maintained anymore because they don't need them anymore. Magisk has been updated so much since a few years ago. Unless your running on debug, you don't need to worry about logs. That is the way to actually fix your phone if you have issues. Looking at the logs. The other guy is right, don't use this module at all. Or anything like it.

as @TotallyAnxious said there´s no reason to use the module. as @dd805bb added, there´s no way to debug if there are no logs.
There´s no excessive logging done and omitting the logging that is being done won´t have any benefits that you´ll notice during regular usage. (e.g. battery life improvements, because I think this is what most users are after when they flash mods like this)

 

[mccbrandon]

Good day @Freak07 I've been running the kernel for a while now and loving it, great battery, loving the clean slate features thankyou and I appreciate the work

 

[anthonnyb98]

Hello @Freak07, could you clarify if this kernel is compatible with KernelSU? I mean if I can continue using su kernel, after su kernel is installed.

 

[Freak07]

Hello @Freak07, could you clarify if this kernel is compatible with KernelSU? I mean if I can continue using su kernel, after su kernel is installed.

No, I´d need to compile the kernel with KernelSU patches included.

Using prebuilt GKI KernelSU or a custom kernel is exclusive to one another.

KernelSU is based on code that ends up in a modified GKI kernel image which is part of the boot.img.
This kernel ships boot.img amongst other images. Therefore I´d need to include the KernelSU changes to my source and build my kernel with those patches.

At the moment there are no plans to do that as I simply lack the time to maintain more builds. However this is just the current state. If KernelSU gets more mature and refined in the future I might consider doing those builds.

 

[shizonic]

June update is online.

 

[krkhaha]

Hi bro. There will be some update for that great kernel or just flash it on new factory update?

 

[Ghisy]

@krkhaha, since this is a feature drop, it may be best to wait until @Freak07 checks the source for potential changes. Better be safe than sorry!

 

[Freak07]

Just like @Ghisy said, since this is a QPR bump it's better to wait until I update the kernel with the updated source for the June QPR/feature drop release if you don't want to face any issues.

If your comfortable flashing back to stock conditions and feel adventurous feel free to try.

Source for June stable has not been pushed yet. It's getting late here. They'll either push source later during my night or tomorrow.

I'll try to update the kernel as soon as possible, but since life is crazy busy at the moment I'll try to do it tomorrow evening.

Wish everybody a nice day/evening

 

[krkhaha]

@krkhaha, since this is a feature drop, it may be best to wait until @Freak07 checks the source for potential changes. Better be safe than sorry!

Off course. You're right.

 

[FERCH_pro]

You can somehow comment on the moment that adaptive brightness does not work with your core. and the brightness changes on its own at a random moment?

 

[Freak07]

You can somehow comment on the moment that adaptive brightness does not work with your core. and the brightness changes on its own at a random moment?

Did you flash on June firmware or u preview? You might want to wait until I updated the kernel for the June QPR bump.


There are no problems with adaptive brightness on my end. Everything works as expected.

Currently running a test version for June firmware, which will be released later today in the evening when I get back home again.

 

[Diofyz]

You can somehow comment on the moment that adaptive brightness does not work with your core. and the brightness changes on its own at a random moment?

It works fine for me. Also pixel may dim screen after some time if it's bright and phone gets hot.

 

[Tracker31]

gonna push June update after you release new version of kernel, cuz I skipped may release for some reasons

 

[Freak07]

Update to Raviantha 1.1.0

Hey guys and girls,

So here´s the next release for stable June firmware! June update was a QPR/Feature bump release so there were a few kernel changes from google as well.
Most of this I merged already in advance, patches that aren´t device specific we already had months in advance by merging kernel/common and linux-stable.
There are loads of improvements to various subsystems that result in better performance and experience in this release.
Loads of patches to maple tree, which was introduced in an earlier release in case you want to check. All the latest developments from linux kernel regarding maple tree are included in this release, some of them affect especially android other are just general improvements as the code is still quite "young". I linked most of the relevant patchset in the changelog below.
Thanks to @ada12 teo util awareness was properly wired up with the pixel_sched governor. This results in better performance and more efficiency, that´s very rare but it´s one of those changes that seems to be actual magic (more information with loads of test results about this here).
There´s another patchset that aims to reduce overhead during cpuset switching, this happens on several occasions, e.g. camera launch, device unlock.

I´d like to write more and in detail, but I simply lack the time at the moment. Please check the changelog and my github for more information.

Powerhint module is updated as well, please make sure to flash/update.





Important:

Make sure to flash the powerhint module attached to this post via magisk manager if you haven´t already done so.
Please note that this release is not for the QPR Beta firmware or dev preview, but the stable android 13 firmware!
Please make use magisk stable if you don´t know your way around bugs and don´t want to actively help debugging magisk development.
You should download magisk stable only from official magisk release site!
Latest platform tools have issues flashing super.img, please use platform tools 33.0.3 when updating your firmware

There are other small improvements as well. Please check my github for those.

The kernel is made for stable A13 firmware, not beta.

I wish everyone a nice day.


Changelog:

- Linux-Stable bumped to 5.10.183
- bump clang to 17.0.2 stable
- bump f2fs-stable to latest
- further improve maple tree/per-vma locks introduced in an earlier release
- improve preallocations from maple tree (affects especially android)
- reduce necessity to rewalk the maple tree
- backport various patchsets from latest linux related to maple tree and vma type safety, patchset 2
- improvements to memory management from 6.1 kernel common
- improvements to MGLRU (check first post for more info about MGLRU)
- reduce overhead
- improve page allocation
- improve performance and efficiency by properly wiring up pixel_sched with teo util awareness (thanks @ada12 for spotting this!)
- update to cpuset/cgroup subsystem (speeds up camera launches, device unlocks etc as cpusets are switched on those conditions, patches reduce overhead in those conditions)
- scheduler improvements
- other fixes please check github



Download:
Attached to release post as AFH is currently down.

Make sure to update and keep the powerhint module installed via Magisk Manager!


If you´re coming from another kernel restore stock boot.img, dtbo.img, vendor_kernel_boot.img and vendor_dlkm.img before flashing. Thank you.

Make sure to meet the requirements and read the OP as well as the FAQ before flashing.

I wish everybody a great day/evening!
Have fun, enjoy the kernel and your phone.



If you like my work please consider a donation.
Donations are not mandatory but very welcome.
If you like my work and want to buy me a coffee/green tea: http://paypal.me/freak07

 

[swieder711]

Installed both files on the June update. Silky smooth. Thanks.

 

[Tracker31]

Thank you very much. I did the whole update from april to june with all this stuff in about 20 minutes. First minutes working well. Good job!

 

[PreviousGod]

Hi guys, I want to get more battery usage from my 7pro.
Is this the kernel i should install?

 

[ffuser1]

Hi guys, I want to get more battery usage from my 7pro.
Is this the kernel i should install?

Everyone's usage is different, but most here would likely say that you'll have better battery life and smoothness/responsiveness. Read the FAQ a few times before starting, as you will need to wipe data the first time only.

 

[PreviousGod]

Everyone's usage is different, but most here would likely say that you'll have better battery life and smoothness/responsiveness. Read the FAQ a few times before starting, as you will need to wipe data the first time only.

Alright, thank you i'll be back if Something goes wrong hahah

 

[Newtonsart]

I need help, my device is not updating. it sais that i have no space left. what can i do?

I executed the following command:
fastboot update --disable-verity --disable-verification image-cheetah-tq3a.230605.012.zip

And this is the output:
extracting system.img (838 MB) to disk... took 4.435s [liblp] Partition system_a will resize from 0 bytes to 879353856 bytes extracting system_dlkm.img (0 MB) to disk... took 0.000s [liblp] Partition system_dlkm_a will resize from 0 bytes to 348160 bytes extracting system_ext.img (367 MB) to disk...ziparchive W 06-15 01:34:29 20938 20938] Zip: unable to allocate 385347584 bytes at offset 0: No space left on device fastboot: error: failed to extract 'system_ext.img': I/O error

Please I dont want to lose my stuff