[Kernel][04.01.2022][Android 11] Kirisakura 1.0.0_R for Asus Rog Phone 2 aka Yoda

[dvijetrecine]

I'm just quite sceptic about how much this would affect the battery, but I like the idea. Some opinions? Did someone try it with Kirisakura flashed?

i can answer you that also: it works with kirisakura

 

[uriii13]

i can answer you that also: it works with kirisakura

Just to be clear for the community: this is totally parallel stuff to the dev work and it's nothing to do with the dev. Everybody that does this, does this at their own risk

 

[Freak07]

i can answer you that also: it works with kirisakura

yes it should just work as it does on stock. The charging driver is not changed in any way.

Just to be clear for the community: this is totally parallel stuff to the dev work and it's nothing to do with the dev. Everybody that does this, does this at their own risk

Exactly. That’s also why I won’t give much input to this topic. I don’t like to play with these things as I’m no expert on the topic of batteries nor do I have any means to do long term testing with the batteries/charging method as on OEM does.

 

[dvijetrecine]

Exactly. That’s also why I won’t give much input to this topic. I don’t like to play with these things as I’m no expert on the topic of batteries nor do I have any means to do long term testing with the batteries/charging method as on OEM does.

thanks for the answer. i looked a bit into charging driver but oh boy, that was a lot of code. thought maybe you could help a bit but i understand your concerns

 

[Freak07]

Update to 3.2.0

Hey guys and girls,

Here´s the next update for the Rog Phone 2.
Just like the last release for the Rog Phone 3 I´m sure a lot of people will be interested in this.
Two very interesting changes in this release.

The display commands were changed so visibility in dark scenes is improved when viewing any content on dark scenes.
Brightness dimmer functionality is included in the kernel and enabled by default now. No need for a magisk module that seemingly caused issues for a lot of people. (never for me though)
You can disable brightness dimmer by setting /sys/module/msm_drm/parameters/bl_dimmer to "N". It´s set to "Y" by default as it is enabled.
You can fine tune the lowest brightness value via /sys/module/msm_drm/parameters/bl_min. Default value is now "3". Default value on stock is "64". You can set it to anything below "64", to your liking.

These changes to the display also shift colours a bit. That means the "dark, red-blueish hue" from the ROG 2 is reduced and the screen looks more natural/neutral. I compared a lot with other devices and think I finally found a good spot, that´s hopefully acceptable for everyone.
I´m sure some will like the way the screen behaves on stock. That´s why there will be several flashable zips. So if you prefer the look on stock, you can still use it.
I encourage everyone to try the new display for a few days during regular usage. I adjusted to the colours looking a bit more neutral after a few days, and now I think it looks way better.
There´s always splendid to fine tune the display to your liking.


The second big change is another one. This release provides an option to use 144fps instead of 120fps on your ROG2, just like on the ROG 3.
When flashing this kernel.zip your device will run at 144fps when choosing the 120fps option in setting.
Keep in mind that there might be a certain risk involved when running it daily on 144fps.
There´s also a difference between the panel drawing at 144fps and an app rendering at 144fps.
Game genie or browser tests provide a possibility to check. Some apps rendering is limited to a certain framerate, even though the panel has a higher refresh rate.

2 new items by freak 07

photos.app.goo.gl

The zips are labled the following:

custom = custom roms running Android 10
144fps = 120fps option will run at 144fps
newsetting= new display setting


Choose according to your liking.


Detailed changelog below and on github.

thanks to @uriii13 for testing the kernel with me prior to release!



Kernel backend PSI-Support and PSI-Enable Magisk-Module:

2.6.0 introduced kernel-backend PSI support .Asus enabled the userspace low memory killer in the stable firmware update. However they do not use it with PSI like the Pixel 4 and google intends, but with vmpressure levels.
If you´re interested in this topic here is more information.
I personally like the PSI-approach way better and I think google did some excellent work there.
If you want to enable this feature just flash the PSI-Enable Magisk-Module via Magisk Manager, when you´re on 2.6.0 or higher and reboot.
If you say I like the approach from Asus just don´t flash it.

I´d advise everybody to read the instructions in the OP and follow them. They are written for a reason, because they ensure everything will be working as expected.
Kernel is made for the latest stock rom from Asus, you must update your phone to the most recent Asus update, before flashing the kernel.

Enjoy!


Changelog:

- implement brightness dimming functionality into the kernel (make sure to remove the brightness dimmer module in magisk manager, before flashing the kernel in case you are using it)
- 144hz refresh rate
- improve visibility in dark scenes

I wish you all a nice day/evening!


Download is below

Download:

Disclaimer/Important:

Kernel for the Stock Firmware by Asus (make sure you´re always on the latest firmware)
Kernel: https://www.androidfilehost.com/?w=files&flid=324225

Kernel for Custom Roms based on Android 10 (please note vibration only works properly on omni based custom roms)
Kernel: https://www.androidfilehost.com/?w=files&flid=324224

Instructions how to flash the kernel can be found in the OP!
But look at this post too

PSI-Enabler-Magisk-Module: https://www.androidfilehost.com/?fid=4349826312261798764
Only for Android 10 Stock Rom running a custom kernel with PSI enabled! Flashable via Magisk Manager!


Have fun, enjoy the kernel and your phone.

If you like my work please consider a donation.
Donations are not mandatory but very welcome.
Coffee and Green Tea is what keeps the development going: http://paypal.me/freak07

 

[reg66]

You little beauty, cheers!!

 

[shorbah]

is it working on omin a11 ?

 

[533y4]

is it working on omin a11 ?

Im wondering the same thing. lol Once i get Omni 11 working, I'll experiment.

Does not work!!!

Can we get R support with this beast of a kernel?

 

[Santhonius]

What is the panel model of the rog 2? Is it the same as rog 3? Wanted to do some self research before trying 144hz

 

[533y4]

What is the panel model of the rog 2? Is it the same as rog 3? Wanted to do some self research before trying 144hz

I will say this much, tho I believe this is more SOC based than panel based... The phone struggles to keep 144hz unless x mode is activated. This goes system wide. Chrome would shuffle between a range of 118-144hz/fps. X mode makes everything solid now. Just found that interesting. 120hz barely had any fluctuation at all no matter what.

 

[ausaras]

> You can fine tune the lowest brightness value via /sys/module/msm_drm/parameters/bl_min. Default value is now "3".

I modified the value to "2" but it always resets back to "3" after reboot. Is it because the value cannot be lower than "3"?

Or, it is a problem with my text editor? I use MiXplorer's built-in code editor to modify the value.

thank you!

 

[Freak07]

> You can fine tune the lowest brightness value via /sys/module/msm_drm/parameters/bl_min. Default value is now "3".

I modified the value to "2" but it always resets back to "3" after reboot. Is it because the value cannot be lower than "3"?

Or, it is a problem with my text editor? I use MiXplorer's built-in code editor to modify the value.

thank you!

The value defaults to 3 on every reboot. I don't think it will make a difference if set lower than 3 anyway.

If you want the value to stick across reboots, either create a script or create a "user setting" in exkm that sets it to your desired value on each boot

 

[chindu.rs68]

Air triggers work in this rom ?

 

[killerdvd]

Air triggers work in this rom ?

This is only a kernel, not a rom. Air triggers work great with stock rom and this kernel.

 

[Arthuer]

The value defaults to 3 on every reboot. I don't think it will make a difference if set lower than 3 anyway.

If you want the value to stick across reboots, either create a script or create a "user setting" in exkm that sets it to your desired value on each boot

This fine with latest update stock rom ? .75

 

[muadeepmuadeep]

Dear Sir,

I've got some Questions:

1.- Can I install without Rooting?
2.- Works with the latest Stock Rom (17.0240.2103.75- 25-MAR-2020)?
3.- What are the exactly steps to do it if yes without rooting

Looking Forward To,
Muadeep

 

[Freak07]

What is the panel model of the rog 2? Is it the same as rog 3? Wanted to do some self research before trying 144hz

you probably won´t find any documentation about the panel as there´s basically nothing available. if you find anything interesting let me know.
the panels are probably very similar.

I will say this much, tho I believe this is more SOC based than panel based... The phone struggles to keep 144hz unless x mode is activated. This goes system wide. Chrome would shuffle between a range of 118-144hz/fps. X mode makes everything solid now. Just found that interesting. 120hz barely had any fluctuation at all no matter what.

yes indeed you´re right. The phone seems to can´t keep up rendering chrome at 144fps when the screen is not touched and no interaction with the phone is happening, thus the powerhal is not boosting the frequencies.

X-Mode raises the minimal cpu frequenices a bit, so the phone can´t idle on the lower frequencies hence it consistently renders chrome at 144fps.

This fine with latest update stock rom ? .75

Dear Sir,

I've got some Questions:

1.- Can I install without Rooting?
2.- Works with the latest Stock Rom (17.0240.2103.75- 25-MAR-2020)?
3.- What are the exactly steps to do it if yes without rooting

Looking Forward To,
Muadeep

Question 1 and 3 are answered if reading the first post.

It works for me with the latest stock rom on the .75 update. But if you want to avoid random issues that I might not yet have faced, it´s generally recommended to wait until I publish an update with the new source code merged.

Asus has not yet uploaded the source code for the .75 firmware.

 

[ausaras]

I think the .75 firmware has been pulled.

I saw it last week on ASUS website. But today, it is not there anymore.

 

[Freak07]

I think the .75 firmware has been pulled.

I saw it last week on ASUS website. But today, it is not there anymore.

No it's still there on the server. The website just hasn't been updated yet, it was never visible on the website for me.

https://dlcdnets.asus.com/pub/ASUS/ZenFone/ZS660KL/UL-ASUS_I001_1-ASUS-17.0240.2103.75-1.1.229-user.zip

 

[Freak07]

update for new firmware soon