• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

Okitavera's Kernel for Mi 9 SE - v8.4

Status
Not open for further replies.
Search This thread

ntstatis

Member
Nov 29, 2012
17
19
Hi there, I've been using your kernel and loving it. However there's a tiny hickups in the compression algorithm settings (I think) it defaulted back to lz4 after reboot no matter what, other parameters works just fine. Tried it with FKM/EXKM with a startup delay on 10 second.
I thought it was just worth mentioning. Cheers!
 

okitavera

Senior Member
Jan 6, 2016
436
808
Malang
okitavera.me
Hi there, I've been using your kernel and loving it. However there's a tiny hickups in the compression algorithm settings (I think) it defaulted back to lz4 after reboot no matter what, other parameters works just fine. Tried it with FKM/EXKM with a startup delay on 10 second.
I thought it was just worth mentioning. Cheers!
Hello :D

You need to enable apply on boot on zram state too, not just the compression.
Also, because changing zram parameters is actually re-creating zram setup, it's better to set it up as early as possible, it because zram is still fresh and still doesn't get filled by android apps :)
 

okitavera

Senior Member
Jan 6, 2016
436
808
Malang
okitavera.me
I knew it was something silly...and on my end. Thanks.


Nah it's not, it is a great question.
Sometimes android are inconsistent, especially since the one that modifying the kernel or zram parameters is not the kernel app only, but also the android system (init), and several magisk kernel tweaker modules like LKT/FDE (if you use it).
So there's a chance that your manual setup is racing with them, and that's why you set the delay to 10s isn't it
 

ntstatis

Member
Nov 29, 2012
17
19
Nah it's not, it is a great question.
Sometimes android are inconsistent, especially since the one that modifying the kernel or zram parameters is not the kernel app only, but also the android system (init), and several magisk kernel tweaker modules like LKT/FDE (if you use it).
So there's a chance that your manual setup is racing with them, and that's why you set the delay to 10s isn't it
I see...
I did use LDE before, doesn't make a lot of difference tbh so I drop it.
 

okitavera

Senior Member
Jan 6, 2016
436
808
Malang
okitavera.me
Hello everyone, today I already upload an another updates for the kernel :D

Changelog (v6.1)
- Merge Upstream Linux 4.9.189
- Merge CAF tag LA.UM.7.8.r1-06700-SDM710.0
- Revert several AOSP Q beta cgroups changes
- Reduce unused debugging on goodix_ts even more to lower overheads
- Security enhancement: disable coresight and unexport debug symbols
- Re-enable support for any type of ramdisk (fix bootlove issues on non-miui system)

Downloads

Notes
This update doesn't fix MIUI Developer ROM 9.8.x weird speaker bug.
But don't cry. I'm not your mama, and there's another ROMs that works better like crDroid and MIUI Stable.
sshh... Pixel Experience, XenonHD, and Resurrection Remix are still in the development process, which means we will get an another great roms :>
 
Last edited:

okitavera

Senior Member
Jan 6, 2016
436
808
Malang
okitavera.me
Hi, what rom do you recommend for this kernel?
Any ROM other than MIUI Developer based ROM.
So, for now there's just :
- MIUI Stable
- crDroid

How you can indistinguish between miui stable and developer based rom ?
just look at the version number.
MIUI Developer has 3 digits. e.g: 9.7.25
but MIUI Stable use 4 instead. e.g: 10.3.4.0
 

elpaablo

Senior Member
Nov 18, 2017
291
114
I see good potential for XenonHD ROM. It's very fast and light. It's still experimental so there's no fingerprint and a few bugs (actually I've only found 1 so far, nothing important) but there are also features working out of the box (like SIM management) that don't work on crDroid. Now I'm trying to install a custom kernel. Kowalski is having issues. Let's try Okita and see how it goes.:)

---------- Post added at 07:24 PM ---------- Previous post was at 06:56 PM ----------

Yeah... both kernels are having issues with XenonHD for now. But I'm still keeping the ROM.
 

okitavera

Senior Member
Jan 6, 2016
436
808
Malang
okitavera.me
Hopes for the Xiaomi.eu dev


you should comment at here instead : https://github.com/MiCode/Xiaomi_Kernel_OpenSource/issues/1123
spamming is much better lmao

I see good potential for XenonHD ROM. It's very fast and light. It's still experimental so there's no fingerprint and a few bugs (actually I've only found 1 so far, nothing important) but there are also features working out of the box (like SIM management) that don't work on crDroid. Now I'm trying to install a custom kernel. Kowalski is having issues. Let's try Okita and see how it goes.:)
Yeah, I believe if the ROM developers is working together it would be much faster, but now they're just working individually.

I use crDroid for now btw, so far so good.
And looks like I'll make this kernel exclusively for aosp-based ROM instead,
Since following MIUI updates without even getting a source updates from Xiaomi are just makes a headache :crying:
 
  • Like
Reactions: elpaablo

okitavera

Senior Member
Jan 6, 2016
436
808
Malang
okitavera.me
Hello everyone :)
Finally....I decide to drop the support for MIUI (any miui-rom) on the version 7.0.
For now, the features are same as before, but much more cleaned-up for custom AOSP ROMs users.

Changelogs 7.0
- Rebased to CAF kernel.lnx.4.9.r14 with Linux Stable 4.9.189 merged in
- Reworked Xiaomi patchset, dropped unused MIUI-things and non-grus patches.
- Migrate to CAF's camera driver (thanks to @krasCGQ for providing the patches)
Changelogs 7.0-r2
- Fix "phone is starting"-loop issues on XenonHD

Download

I am so sorry guys, especially for those who are MIUI fans. I just can't keep up with MIUI anymore.
When we got the fixes, it only last 1-2 weeks (or 3 if we just lucky) before they broke the system again, it's like they don't want to support the opensource community and publishing source code are just to play safe and avoiding license violation.
So that's why I'm deciding to stop it, hope you guys understand it.
 
Last edited:
Status
Not open for further replies.

Top Liked Posts

  • There are no posts matching your filters.
  • 39

    eHjVLwZ.png


    Intro
    Okitavera's kernel is a custom kernel based on CAF Kernel with specific patches from Xiaomi.
    Aims to provide stability, security, and other benefits from having a regular patches from Linux Stable, CAF, and Google.

    Features
    • Merged patches from :
      • Linux Stable currently on: v4.9.197
      • Google's kernel common: android-4.9
      • CAF specific fork for for Snapdragon 71*, currently on: LA.UM.7.8.r1-07100-SDM710.0
    • Dynamic SchedTune boost
    • BBR and Westwood TCP congestion-avoidance algorithm (optional)
    • Exposure Adjustment (DC Dimming)
    • AVB and SafetyNet bypassed
    • KCAL, KLapse, Vibration control, and Sound control
    • Check GitHub commits for more
    • TL;DR : The best custom karamel (arguable)

    Compatibility (v8.4)
    • AOSP-based custom ROM (Pie)
    • MIUI 10 and 11 (Stable or Weekly. Pie, NOT THE Q)

    Downloads
    Zach said this link should be bigger and as you can see he's right


    Installation
    • Backup your dtbo and boot partition.
    • Flash the kernel.zip file via twrp

    Credits and Thanks to
    • Linus, The Linux Foundation, Google, CodeAurora, Xiaomi
    • arter97
    • celtare21
    • faust93
    • flar2
    • franciscofranco
    • kdrag0n
    • kerneltoast
    • krasCGQ
    • nathanchance
    • osm0sis
    • pengus77
    • RenderBroken
    • ... and all of the contributors from commits and patches on my git


    XDA:DevDB Information
    Okitavera's Kernel, Kernel for the Xiaomi Mi 9 SE

    Contributors
    yuneharuka
    Source Code: https://github.com/okitavera/msm-4.9-grus-okita

    Kernel Special Features: Family friendly, no overclocked.

    Version Information
    Status: Stable
    Current Stable Version: 8.4
    Stable Release Date: 2019-10-19

    Created 2019-05-26
    Last Updated 2019-10-19
    15
    Breaking news.

    Xiaomi already publish the Mi A3 (or Mi CC9, CC9 Meitu, whatever you named it, Xiaomi) Kernel source code.
    It basically uses the same base as ours, and after some hours of inspection,
    me and @pengus77 got a few things from Mi A3 and Mi 9 source code that can be ported to fix several issues on this device (like the brightness, fod, etc) :)
    14
    Good Bye :D

    Hello everyone!
    Unfortunately, I have to stop the development for Mi 9 SE due to device change
    smile.gif

    The kernel sources for this device still available at my GitHub page if you want to fork or even just looking around.

    Thanks for all the support given and see you later :)
    14
    Hello everyone!

    Here's the update notes for v4.0

    Changelogs

    - Add Sound Control for our Speaker
    - Fix overlapped call and notification values on haptic control
    - Cleanup debug bloat on Wi-Fi driver as much as possible
    - Cleanup some unused xiaomi changes on driver departments (camera and fragmention)
    - Removed schedutil_pixel (blu_schedutil and default schedutil is more than enough)
    - Adjust Dynamic Stune Boost default to 10%
    - Turned-down Performance cluster to 748MHz
    - Keeping boosted freq that based on touch input a litte bit longer
    - Enable workqueue power saving by default
    14
    Hello everyone!

    Here's the update notes for v4.5

    Changelogs

    - Upstream kernel to 4.9.185 (android-linux-stable)
    - Allow enforcing deepest cluster idle state selection
    - Use power efficient workqueues on the vmstat and audio-kernel
    - hardcode dirty_expire_centisecs to 30s (https://android-review.googlesource.com/c/platform/system/core/+/938362)
    - Add IPA_RM12 and IPA_WS to the default block list (thanks to @pengus77 for more wakelock block list)
    - Updated Goodix GT9886 firmware from MIUI Dev
    - Cleaned-up unused touchscreen driver

    Notes
    I can't fix the short brightness bugs on MIUI Dev yet, so lmao yeah.