[KERNEL] [Android 12] [v12.5] MVK - Maximum Velocity Kernel

[ctfrommn]

Sorry, I misspoke....Techpack are files needed, not a module. That is the repo they come from though. They're in my 12 source, they're just ignored and not pushed.

 

[cengkyyyy]

Build is 100% stable. Those settings arent changeable and/or are disabled. This kernel is designed to be used as is, not tweaked by users.

user like tweak a device, why ?? flash kernel for tweaked, but the kernel cant tweak, haha

 

[ctfrommn]

user like tweak a device, why ?? flash kernel for tweaked, but the kernel cant tweak, haha

User can flash a different kernel then or build one with whatever tweaks you prefer.

 

[ctfrommn]

v12.2 is up. This is another massive rework including updated, simplified optimizations, removal of tons of commits that werent helpful (or were harmful) to performance, and many other changes. This performs significantly better and battery life (especially idle drain) is also much better.

Side note.....due to temporary circumstances I will be sticking with the 3a XL for now and will look at updating next year at some point so this kernel will be full steam ahead for now.

 

[NinjaCoool]

v12.2 is up. This is another massive rework including updated, simplified optimizations, removal of tons of commits that werent helpful (or were harmful) to performance, and many other changes. This performs significantly better and battery life (especially idle drain) is also much better.

Side note.....due to temporary circumstances I will be sticking with the 3a XL for now and will look at updating next year at some point so this kernel will be full steam ahead for now.

Works good on my Pixel 3a! Non-rooted and running Naptime.

 

[quan2812]

p.s. sorry for bold, my PC does not allow me to make text normal for some reason​

v11.13.1 Works for me on android 12, the only unusual thing is that it would not boot from the first attempt after the update.​

My path (skipping obvious things, like enabling USB debugging):​

1) starting with: sargo, Android 11, MVK 11.12+magisk, unlocked bootloader​

2) OTA update to Android 12​

3) reboot, all works, no magisk, no root, all stock​

4) reboot to bootloader​

5) fastboot boot MVK_Sargo_v11.13.1_magisk_patched.img, first time fails when loading​

6) repeat: fastboot boot MVK_Sargo_v11.13.1_magisk_patched.img (without booting to stock kernel using power+down combo)​

7) Booted correctly to the main screen​

8) adb reboot bootloader​

9) fastboot flash boot MVK_Sargo_v11.13.1_magisk_patched.img​

10) first time fails when loading​

11) just wait for the reboot, looks like a boot loop, but it is not​

12) all good, Android 12, MVK 11.13.1+magisk, unlocked bootloader​

13) update magisk from the Magisk Manager (Canary channel)​

14) same double (or ever three times?) reboot​

15) final: Android 12, MVK 11.13.1+magisk23001. All major functionally seem to be fine: phone, camera, wi-fi, Bluetooth.​

In addition, all of my magisk packages seem to survive and work correctly​

Can I ask you? After update OTA my bootloader is locked or unlocked?
Ps: I unlock bootloader and update OTA after that.

 

[ctfrommn]

Kernel has nothing to do with the bootloader. It will stay in whatever state it was before flashing.

 

[nowster]

I've had a few spontaneous framework reboots with 12.2 (back to Google logo without going through bootloader) due to OOM conditions. It killed the net process running DNS lookups.

Extract from tombstone:

Cmdline: /system/bin/netd
pid: 22634, tid: 9757, name: Dns_101_10234  >>> /system/bin/netd <<<
uid: 0
signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
Abort message: 'terminating with uncaught exception of type NSt3__112system_errorE: thread constructor failed: Out of memory'

I've gone back to December 2021 stock for the moment (even though it has glitchy video).

 

[ctfrommn]

Never had a reboot so no idea

 

[johnwazhere]

Update link to Android 12 version, found it on your Android file host account tho.

 

[tt_rockt]

I wish you a happy new yeah. Lets do another round around the sun. Oh yeeah, I am glad, that you will go on with this great kernel. Thank you so much for sharing.

 

[ctfrommn]

v12.3 is up. Nothing too special this month, just normal updates.

 

[blksith0]

So how does the installation process fit-in with flashing a magisk-patched boot.img? What's the proper order of operations there?

 

[ctfrommn]

Its in the OP, but basically.......

abd reboot bootloader
fastboot flash boot "full kernel name"
fastboot reboot

Thats really al it is, no different than flashing any boot image

 

[Roarmaster]

@ctfrommn Hi, it looks like your MVK_Sargo_v12.3_magisk_patched.img isn't actually patched with magisk. When i look into magisk, it says uninstalled, but the kernel itself is installed when i check with EX kernel manager.

I've also tried patching your kernel boot img with magisk, but no luck.


Edit: same with MVK_Sargo_v12.2_magisk_patched.img

 

[ctfrommn]

@ctfrommn Hi, it looks like your MVK_Sargo_v12.3_magisk_patched.img isn't actually patched with magisk. When i look into magisk, it says uninstalled, but the kernel itself is installed when i check with EX kernel manager.

I've also tried patching your kernel boot img with magisk, but no luck.


Edit: same with MVK_Sargo_v12.2_magisk_patched.img

I just flashed that build and it's definitely rooted so something is going on on your end.

 

[Roarmaster]

I just flashed that build and it's definitely rooted so something is going on on your end.

Yes, you're right. Before flashing your kernel image, i was on magisk canary. It seems that i cant go back to stable magisk for some reason. I tried patching the latest stock jan sargo boot.img from google with magisk stable (23) and it doesnt work either.

I also tried flashing the entire stock factory image without wiping and i still cant install magisk stable (23). Look's like im stuck on magisk canary for now.


Edit: It looks like patching your 12.3 img works with magisk canary. In retrospect, to get magisk stable working, i probably had to uninstall magisk canary through the magisk app first before flashing magisk stable. Thanks!

 

[ctfrommn]

Just use the unpatched version if you want to use Canary.

 

[Roarmaster]

Just use the unpatched version if you want to use Canary.

Yep, thanks. One question, does your kernel include disabling pwm(pulse width modulation) or enabling DC dimming? According to notebookcheck(website), our pixel 3a uses pwm under 99% brightness.

In EX kernel manager, is that the same as changing the pulse frequency under k-lapse settings? Or does it have something to do with the backlight dimmer option?

 

[ctfrommn]

Yep, thanks. One question, does your kernel include disabling pwm(pulse width modulation) or enabling DC dimming? According to notebookcheck(website), our pixel 3a uses pwm under 99% brightness.

In EX kernel manager, is that the same as changing the pulse frequency under k-lapse settings? Or does it have something to do with the backlight dimmer option?

No idea what either of those are.