yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Freak07:
Max frequencies will be used when there´s enough load and no thermal throttling is happening.

The powerhal/thermal-hal/framework sets the cpufreqs dynamically, users are not supposed and can´t change max frequencies manually via kernel managers as your changes will be overwritten almost instantly depending on what´s happening on the device.

If performance is needed they will be set to max, if not they will be restricted by different functions.

A combination of those allows this kernel to perform better in max performance scenarios (e.g. faster app launch times), while keeping the device a tiny bit cooler than stock configuration.

There´s no need to worry about benchmark scores, for geekbench etc. The kernel is tested for basically every release with better tools/benchmarks than those available in the playstore.
[Google Pixel 6 Pro] Freak07:
the usual TTL additions/features are enabled in the kernel.

you need to do some research on XDA if those can allow you to bypass whatever restrictions you´re operator is imposing.
[Google Pixel 6 Pro] Justarandomguy:
Amazing! The scores still are amazing, nothing to worry, I admire your work and the great job you are doing, thanks for everything <3
[Google Pixel 6 Pro] Divine Bicycle:
Is June firmware `13 (TQ2A.230505.002)` for the Pixel 6 Pro?
[Google Pixel 6 Pro] felek73:
No ...230505 - 05 in the middle stands for may
[Google Pixel 6 Pro] w_tapper:
does the kernel overclock the cpu/gpu at all? if not it would be nice if it did
[Google Pixel 6 Pro] michaely123:
@Freak07 *Update* I have not had any crashes with 1.0.5_6, 1.0.6_3, or 1.1.0.
[Google Pixel 6 Pro] Freak07:
Thank you very much for the kind words!

No it doesn't.

GPU overclock doesn't really give any benefit as it gets throttled very fast. Unlocking one more freq is probably the better term.

CPU overclock is not stable.

Depending on the binning even slight overclocking will result in crashes.

Thanks for the feedback. That's nice to hear. Thanks for all the testing!
[Google Pixel 6 Pro] Flyview:
Since we're on the topic, what about undervolting? Is that still a thing?
[Google Pixel 6 Pro] Nayem-Mahfuz:
I would like to know as well. I tried with the SetCpu app(As this is the only app that can control voltage that I know of) but it's not compatible with newer android version.
[Google Pixel 6 Pro] w_tapper:
undervolt would be better considering how hot tensor g1 runs
[Google Pixel 6 Pro] Divine Bicycle:
Hmmm, it seems I have to update again then.
[Google Pixel 6 Pro] Freak07:
Undervolting introduces instability just like overclocking. Voltages are chosen dynamically by the ECT depending on the binning of your SoC.

I explored a bit into the area and it seems there´s no way to change voltage as they´re restricted by the ECT. So kernel changes in that regard are just overruled by firmware from deeper anyway.
[Google Pixel 6 Pro] chewy74:
Anyone running the most recent kernel on June LineageOS for oriole without issues?
[Google Pixel 6 Pro] Flyview:
Damn, that's sad. Of course it could introduce instability but it's always fun to find that limit haha. Is there a way to find out the binning of your SoC?
[Google Pixel 6 Pro] Deeglifsay:
if I'm flashing with kernel flasher do I flash to both slots or just the active slot?
[Google Pixel 6 Pro] phaino00:
The active slot is the one to flash.
[Google Pixel 6 Pro] Nayem-Mahfuz:
How do I mount both slot?
[Google Pixel 6 Pro] phaino00:
I am not certain what you are asking?
[Google Pixel 6 Pro] shag_on_e:
So does anyone know if the newest Magisk canary finally works or should we continue to stick with the stable?
[Google Pixel 6 Pro] idark11:
Both versions work without problems.
[Google Pixel 6 Pro] Rachid.Ala:
Is there a way to enable battery saver mode without installing cleanslate app ?

Is it a sysfs node or something I can enable somehow in the terminal for example ?

I don't have much time to look at sources to see how it works but I guess cleanslate app just enable it and doesn't ddo anything special ? Or am I totally wrong ?

Thank you for your help and your amazing kernel.
[Google Pixel 6 Pro] Freak07:
The CleanSlate config app leaves no cpu footprint at all, the config app just writes a config file to the storage after tapping the save button, which the kernel reads so it knows which features are enabled/disabled.

The CleanSlate companion app (which several cleanslate features need that are userspace related) leaves an extremely small footprint regarding CPU usage and reports userspace events so the kernel can know what´s happening (e.g. notifications arriving, proximity, if camera app is opened etc).

There´s no sysfs node to control the CleanSlate features, just the config file created by the CleanSlate config app.

In theory you can uninstall the CleanSlate app after you set the features once. You just need to backup and copy back the file uci_user.cfg after uninstalling back to it´s proper location.

storage/emulated/0/Android/data/org.cleanslate/csconfig/cache

However and now there´s the big but:

This new feature is one that needs the companion app to work correctly. Because the kernel can´t know which app is launched and what´s happening in userspace.

So the Battery saver without any extras, just the main config is working by just having the config file.

I´d suggest to just leave the CleanSlate apps enabled and hide them in launcher with Pixel Launcher Mods mod from Quinny899. You save yourself a lot of trouble.
[Google Pixel 6 Pro] Rachid.Ala:
Thank you so much 👍👍
[Google Pixel 6 Pro] spr33:
Sorry for possible OT post but I've just bought Cleanslate Configuration and wondered if I need to do anything else besides enabling Battery Saver (and running Kiri kernel) to get the battery savings working? I don't see that they're working when using CPU Float to check CPU speeds. I've enabled Battery Saving and set it to 3 and it's still ramping up to to max freqs (which I wouldn't expect).

Ignore me! Turns out there's a save button and that requires pressing before changes will take effect.
[Google Pixel 6 Pro] ada12:
I tested and cpu in gs101 for prime cluster support max freq 2850000hz instead stock 2802000hz ( max freq cpufreq_domain2 is set in gs101-b0.dts )

2850000hz is already enabled in dm-table@0006 of gs101-cpu.dtsi so its unlocking 1 more freq.

for gpu same 848mhz is enabled in table but for gpu_dvfs_max_freq its 800000 instead 900000 ( value used for enable 848mhz in gs201 ) by importing additional change for 848mhz from gs201 its work in unlocking 1 more freq . I no notice real difference about thermal in gaming.

increasing to 2850000hz instead 2802000hz could require update EAS value in gs101-cpu but its already outdated by google in stock kernel source ( not kirisakura fault for all user reading that ) , when google have update EAS value in 2021 max freq is 2630000hz for prime cluster actually in stock its 2802000hz.

its could be interesting to adapt freqbench like sultan did for gs201 https://github.com/kerneltoast/freqbench in gs101 for update EAS values.
[Google Pixel 6 Pro] Chris_caron25:
Had my first crash since the update, been on 1.1.0 since the 14th. I believe at the time of the crash I switched to snapchat with the recent app gesture

and thank you for all the awesome work you do on the kernel!
[Google Pixel 6 Pro] Freak07:
yes, both can be enabled quite easily in dts.

Google/Samsung updated ect so tensor is stable on the high freqs.

Enabling those freqs will result in hitting the thermal ceiling more quickly. I already tried it.

It´s especially noticeable during regular usage in hot ambient conditions.

During benchmarks the thermal ceiling will also be hit more quickly.

This negates any performance improvements in unlocking one more GPU step during most 3d operations, (e.g. gfx bench, 3d bench). If a run finishes without hitting either the kernel thermal ceiling or the thermal hal thermal throttling you get higher scores.

Same is true during gaming. Thermal ceiling is hit quicker, so throttling happens earlier.

CPU is similar. If you cool the phone down, as long as the workload doesn´t hit the thermal ceiling of the kernel or the thermal hal, you get higher scores. If the phone is already warm, throttling will just happen faster.

There´s not much to be gained by unlocking more freq steps, as freqbench just showed that mid and big cluster get increasingly more inefficient the higher the freq.
[Google Pixel 6 Pro] dark2099:
Anyone tried 1.1.0 on the July update?

EDIT: Decided to be a guinea pig, flashed on the A1 July update, booted fine, will report if I run into any issues.
[Google Pixel 6 Pro] Freak07:
Update to Raviantha 1.1.2

Hey guys and girls,

So here´s the next release for stable July firmware! Not many kernel changes from Google this month, just a few security fixes, but this is pretty much standard for non QPR/feature bump releases.

Most of those fixes I merged already in advance, patches that aren´t device specific we already had months in advance by merging kernel/common and linux-stable.

We´re moving this weekend, so my time to reply to posts/questions might be limited during the next days. But it was lucky google released it yesterday instead of next Monday. :)

There are loads of improvements again in this release. The biggest changes address the scheduler/cpu governor to improve performance especially on Android systems. See here for more details.

Since google does not use standard schedutil, but their own iteration called pixel_sched this change was integrated into googles governor so we can profit from it.

The Android 14 beta contains a lot of scheduler changes in googles vendor hook system. I merged all of those patches, evaluated their impacted and kept all that were good.

A few negatively impacted performance by quite a big margin for certain scenarios like app launches. Those were reverted and excluded. Hopefully it´s still a WIP by google, but let´s see.

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.

Important:

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:

- Include July source drop

- Linux-Stable bumped to 5.10.186

- bump clang to 17.0.3 stable

- introduce runnable boosting, wire it up with pixel_sched

- beneficial scheduler improvements from Android 14 beta included

- integrate some scheduler changes to the powerhal

- fixes/improvements to RCU subsystem

- improvements fixes to MM

- patches for f2fs

- other fixes please check github

Download:

Attached to release post as AFH is currently down.

Make sure to keep the ak3 helper module installed in Magisk Manager and do not delete it!

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
[Google Pixel 6 Pro] -Happy Feet-:
Is that normal with this Kernel the high load?
[Google Pixel 6 Pro] Freak07:
No, although kernel manager apps can be deceiving in that regard. The live view can add enough load so freqs are being pushed in some cases. That said in EXKM I see my device idling constantly on basically only lowest freqs if I don't touch it.

Best to check CPU usage with top command in terminal.

grant su access by typing "su" in terminal, followed by "top".

Rotate to landscape and check if anything stands out on top constantly.

It's probably an app or service stuck in background.
[Google Pixel 6 Pro] -Happy Feet-:
Okay thx. I think Kernel manager or anything also are not recommend.
[Google Pixel 6 Pro] Utini:
Flashed and working fine so far.
[Google Pixel 6 Pro] euplio:
It's a stupid question but I would like to be sure not to make any mistake. How to update the kernel? Can I update via OTA the software before and then flash the kernel?
[Google Pixel 6 Pro] phaino00:
Once you update your factory image/software (ota or otherwise). Just flash the kernel like you normally would after the update of factory image/software.
[Google Pixel 6 Pro] Legitsu:
running on on my Pixel 6 with Evolution X rom (yee yee unsupported and what not) no issues to report
[Google Pixel 6 Pro] euplio:
Hi @Freak07 many thanks for your kernel. Really appreciate your hard work and dedication! Just one question for your: do you think FDE.AI can generate any conflict with your kernel? I really used to love that mod and I would try it on my pixel 6 pro. Many thanks
[Google Pixel 6 Pro] Legitsu:
don't try on todays evo ota something broke compat

edit: seems like the ota was just JANK: Reloading rom and reinstalling the kernel seems to have corrected it

if you have issues on custom roms I recomend reinstalling the rom as per there instructions To both slots: then try reinstalling the kernel (make a backup first obviously)
[Google Pixel 6 Pro] Legitsu:
would it be likely to someday intergrate kernelSU support so we can finally stop fighting with google and safetynet/magisk

What is KernelSU? | KernelSU

A kernel-based root solution for Android GKI devices.

kernelsu.org
[Google Pixel 6 Pro] acidspider:
We can dream I guess.....
[Google Pixel 6 Pro] Freak07:
Fighting with google starts the moment you unlock the bootloader. Unlocking the bootloader trips safety net since device attestation.

Magisk just allows you to fix that, and some apps in return detect rooting/magisk specifically.

Once KernelSu gets more popular the same cat and mouse game will start, as there will be ways to detect it and hide the detection.

Yes, don't use apps/scripts or tweaks like this please. :)

Thanks for the report :) other users going the same path might benefit from this!
[Google Pixel 6 Pro] Legitsu:
thats the entire point of kernelSU its kernel level nothing below kernel level has any real way of detecting it (when using Sulist) as for safety net yea thats eventually going to be hard to bypass but for the moument there are fixes. you can evade 90% of most root detection using things like magisk alpha and shamiko/lsposed

I like control over my device and I also like stil being able to use my device

I am camp :if I have root nobody else has it:

____

still no issues with evox to report other then the usb 2.0 fast charging toggle is grayed out non-issue as nobody should be using that anyway
[Google Pixel 6 Pro] Suavie103:
Off topic but does anyone have a patched july 6 pro boot image?
[Google Pixel 6 Pro] Freak07:
For the moment there are fixes for safety net, just like for magisk.

Once hardware attestation is fully enforced it's not about detecting root, unlocking the bootloader trips it and KernelSu won't change it.

Then there will be the next workaround and the story repeats. :)

To answer the original question: At the moment there's no KernelSu support and no support planned short term, but it might change at one point in the future. :)
[Google Pixel 6 Pro] sharkie405:
July, 6 pro, patched-boot image is attached.
[Google Pixel 6 Pro] Suavie103:
Thank you so much
[Google Pixel 6 Pro] djo_5296:
forgot to send my logs here from last week, so this is using 1.1.0 while on June update. Gonna update to 1.1.2 and will be using July update after making this post
[Google Pixel 6 Pro] euplio:
Hi guys. Noob question here, can you please help me updating to July software release and then update the kernel? I'm now on June stock firmware with the previous kernel release. Thank you
[Google Pixel 6 Pro] abalam:
Question: How do I return back to stock?

Answer: Extract boot.img, dtbo.img, vendor_boot.img, vbmeta.img and vendor_dlkm.img from the matching factory image provided on googles download page.

If you disabled verity/verification previously there´s no need to flash the vbmeta.img when restoring.

If you want to stay rooted make sure to flash a boot.img that has been patched with magisk.

Flash those images via fastboot/fastbootd and you will be back on stock kernel. If you don't know the fastboot commands to flash the images, check the instructions how to flash those images in post #4.

Alternatively dirty flash the whole firmware without wiping by using either the android web flash tool, a factory image or a full OTA image. If you disabled the vbmeta flags, don't forget to disable them again (or tick the correct options on the web flash tool) after flashing a full firmware package and re-root.
[Google Pixel 6 Pro] Legitsu:
yes thats a pixel 6 beating a pixel7 running evox and kirisakura in both single and multi thread tests

Google Pixel 7 Benchmarks - Geekbench

Google Pixel 6 - Geekbench

Benchmark results for a Google Pixel 6 with an ARM ARMv8 processor.

browser.geekbench.com
[Google Pixel 6 Pro] FallibleElf2988:
Works great even in 2023! My Pixel 6 is on July 2023 Update as well as its rooted
[Google Pixel 6 Pro] aimsjahan:
Please

do NOT quote OP,

it's annoying.
[Google Pixel 6 Pro] shoey63:
It's his first post.

Give him a break . . .
[Google Pixel 6 Pro] aimsjahan:
I understand. It was kind of impulsive reply. @FallibleElf2988, I hope you did not take it personally!
[Google Pixel 6 Pro] Flyview:
The battery saver through the CleanSlate Config app is no longer working to cut max CPU frequencies for me anymore. I updated to both Kirisakura 1.1.2 and the Config 3.2.16 at the same time so I'm not sure which is causing the problem. Can anyone else confirm?
[Google Pixel 6 Pro] Freak07:
Works just fine on my end here using the same versions.
[Google Pixel 6 Pro] snake218:
Hi. I'm not 100% sure if i had a reboot, but i will share the logs. Pixel 6, latest kernel. Yesterday i clicked on the "lockdown" option on power menu, I'm not sure if i hit restart instead, but when i lifted my phone it was rebooted.
[Google Pixel 6 Pro] -Happy Feet-:
@Freak07 you wrote "Make sure to update and keep the powerhint module installed via Magisk Manager!" Is that the AK3 Helper Module“ or an different App?
[Google Pixel 6 Pro] Freak07:
Copy paste error from pixel 7 release post again... 😄

It's the ak3 helper module that's get automatically flashed on pixel 6, while it's a separate zip on pixel 7.

Thanks for spotting, I corrected it.

Yeah it rebooted indeed, I can see it on the log as you described, you shut the screen off and shortly after the reboot was triggered.

It's not a kernel panic itself, but the APC watchdog triggered a reboot as it probably detected an unrecoverable issue happening.

I don't know what exactly happened, as I think one would need additional tools/access to the soc internals to be able to debug this. There's a warning in the mali GPU driver triggered, a bit before the issue happened, might be related/might be not.

Maybe the issue happened way before the watchdog triggered and the log doesn't reach back that far.

If it happens again feel free to send another log.
[Google Pixel 6 Pro] Flyview:
You're right. I was so excited to try the new CleanSlate camera functions that I completely forgot to actually flash the kernel after flashing the July update, rooting, and CleanSlate update. Oops! Thank you!
[Google Pixel 6 Pro] acidspider:
what camera functions does the cleanslate app offer?
[Google Pixel 6 Pro] Flyview:
You can now remove the battery saver (CPU freqs cap) exception when the camera is in use. By default the battery saver does not apply when the camera is in use.
[Google Pixel 6 Pro] fillwithjoy1:
Hey everyone, I did the massive mistake and installed Raviantah 1.1.2 on my P6P running June. How do I get myself out of this? (Fastboot somehow not reading adb mode)
[Google Pixel 6 Pro] iwearthebelt:
Sorry , I was reading your post and hit reply by accident . Hopefully someone will know how to get you out of that if you haven't figured it out already .
[Google Pixel 6 Pro] digger16309:
Can you use Android Flash Tool to reflash June factory image without wiping data?
[Google Pixel 6 Pro] fillwithjoy1:
Nah I fixed it https://xdaforums.com/t/soft-bricked-pixel-6-pro-solved.4607567/
[Google Pixel 6 Pro] slickrasta:
Everytime I update my Pixel 6 to the monthly update via flash.android.com then install Kirisakura kernel using KernelFlasher my RCS Messages begin to fail. They work via SMS fine and after a week or so the issue seemingly resolves itself and RCS continues to work. I'm in Canada if that matters. Does anyone have an idea as to what the cause and/or what a solution could be? Clearing Messages cache does not help.
[Google Pixel 6 Pro] fillwithjoy1:
Just let RCS do it's job I guess. If you want to speed up the process, you can open the settings panel and check the RCS status. However don't keep forcing it to reconnect, or Google will temporary ban you from using it for a couple of days.
[Google Pixel 6 Pro] Flyview:
The problem is you're in Canada 😂. Haha kidding. Highly doubt this would be related to the kernel!
[Google Pixel 6 Pro] slickrasta:
RCS Status is always Connected, even when it fails. I just have to resend as SMS constantly for them to go through. I updated 10 days ago and it still intermittently fails. Ironically the messages I send are to Pixel, Android and iPhone users there's no specific patterns it just seems random.
[Google Pixel 6 Pro] fillwithjoy1:
hey i remember checking your post a while ago, where you shared the shell command to check all ACC configurations and find the ones where idle mode works. Could you send it here again? Thanks
[Google Pixel 6 Pro] AlDollaz:
Try AccA. It's a front end for ACC. Makes configuring much easier. Just FYI. 😁👍🏻
[Google Pixel 6 Pro] fillwithjoy1:
It was the command acc -t p
[Google Pixel 6 Pro] enerGy:
What the hell have you been smoking dude. Its a kernel for a start, you literally just joined the forum and you are adding these weird ass posts about for no reason. Posts to boost your scores or AI lmao!
[Google Pixel 6 Pro] Legitsu:
bot reported

bot reported
[Google Pixel 6 Pro] Badger50:
And deported! 😉
[Google Pixel 6 Pro] Legitsu:
is there any way to get more volume out of the device at the kernel level?

maby give something some more juice lol god the speakers on thise device are under powered
[Google Pixel 6 Pro] digger16309:
Viper4Android (search XDA)

The same developers also put out Wavelet in the Play Store. It has some of the same functionality, including a +5dB gain. Viper4Android may have more though I'm not ruining it.
[Google Pixel 6 Pro] Legitsu:
pretty sure viper is abandoned vaporware. I haven't had any luck getting it to work on anything newer then android 10
[Google Pixel 6 Pro] digger16309:
I don't want to hijack this thread, but V4A is repackaged at least twice and I know many had it working in at least A12. Agreed it is not easy though.
[Google Pixel 6 Pro] Legitsu:
I don't think fake gain in post is a solution it needs to be set at the driver/audiohal level if possible

so I guess joshuadoes beat me to it:

[MOD] Pixel Tensor Audio Decompressor

WARNINGS! It goes without saying, your decision to use this module comes with risks. For example, playing at high volumes can lead to increased heat production, and may be unfavorable in environmental conditions most affected by our continuously...

xdaforums.com
[Google Pixel 6 Pro] iwearthebelt:
I've had great results with Wavelet, great sound and volume control .
[Google Pixel 6 Pro] Legitsu:
wavelet doesn't work on the phone speakers
[Google Pixel 6 Pro] iwearthebelt:
yes it does . works on the phone speaker , bluetooth, devices , and wired devices. Makes a great difference . You just need to be rooted and follow the directions when setting it up .