Weeb Kernel

Search This thread

idkwhoiam322

Senior Member
Apr 19, 2015
578
1,336
DxyIh9y.jpg
Indroduction:
Weeb Kernel is based on latest CAF with a minimal import off OnePlus's provided source code to retain functionality.

Feel free to ask for any feature requests, but if I think something is useless or doesn't provide any benefit to warrant its addition, I will NOT add it, irrespective of how many people ask for it.

Code:
/*
 * Your warranty is not void (Thank you OnePlus!).
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this Kernel
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 */

Supports:
- Custom ROMs on 9, 10
-- WiFi will not work on ROMs that use qcacld as a module ( eg. Omni, Treskmod Pie )

Reporting Bugs:
If you want to report any bugs, please post a logcat and dmesg(using an app like syslog), thank you!

Features:
- Here

Downloads:
- Github Releases

Telegram Channel: Weeb Announcements
Join me in my Café: // Weeb Karamel Café //

Flashing Instructions:
- Simply flash the kernel
- If you have magisk AND if you are on android 10, reflash magisk after flashing the kernel

Reason behind the name?
Well, I originally even thought about making this because of some mates in a weeb telegram chat. I'm aware of a kernel of the same name by raphielscape which is now renamed, and she was okay with me using this name.

Credits and Thanks:
- raphielscape for inspiration and dealing with my extremely stupid questions ( she is my sensei ;) )
- osm0sis for AnyKernel3
- nathanchance, Akhil Narang, MSFJarvis, kdrag0n, celtare21 et al for their help in totally random places :d
- The Linux Foundation, CAF and OnePlus for the code

Sauce: Ketchup and Mayo Mix

Version Information:
Stable Version: Weeb Kernel v3.00 CodeName Ricardo
Release Date on XDA: 05-11-2019

P.S I don't care about OT XD

El Psy Congroo~
 
Last edited:

idkwhoiam322

Senior Member
Apr 19, 2015
578
1,336
2361 Why can not I set the frequency more? There is always a reset to 2361 MHz

Doesn't work on OxygenOS, but I had a friend confirm that it works fine on Non OxygenOS based ROMs(he tried on CodeName Phoenix Pie, specifically). It's limited by the perfdaemon and I'm not sure how to deal with it if it's even possible. I mean, it even boosts the small cluster just fine ._.
 

mp3deviant721

Senior Member
Jan 4, 2013
1,205
547
Ooh. Another wild EAS kernel appears!

Just flashed on Lineage 15.1 and its seems pretty smooth even without dynamic stune boost. I love the fact that its based on RedFlare, gonna try this out for a few days. ?
 
  • Like
Reactions: idkwhoiam322

idkwhoiam322

Senior Member
Apr 19, 2015
578
1,336
Ooh. Another wild EAS kernel appears!

Just flashed on Lineage 15.1 and its seems pretty smooth even without dynamic stune boost. I love the fact that its based on RedFlare, gonna try this out for a few days.

Thank you for your kind words.
I just want to clarify that the kernel does, in fact, support dynamic stune boost, unless you mean you have it set at zero, which is something I'm trying myself in private builds XD, and can confirm it's still smooth.
 

mp3deviant721

Senior Member
Jan 4, 2013
1,205
547
Thank you for your kind words.
I just want to clarify that the kernel does, in fact, support dynamic stune boost, unless you mean you have it set at zero, which is something I'm trying myself in private builds XD, and can confirm it's still smooth.

It's not showing in my kernel app for some reason then. I'll try clearing the app's data and report back.

Edit: still not showing up. I'm using EXKM, I'm guessing it's supposed to show up in the app? I was running RedFlare before and that kernel was showing stune boost settings fine...
 
Last edited:

idkwhoiam322

Senior Member
Apr 19, 2015
578
1,336
It's not showing in my kernel app for some reason then. I'll try clearing the app's data and report back.

Edit: still not showing up. I'm using EXKM, I'm guessing it's supposed to show up in the app? I was running RedFlare before and that kernel was showing stune boost settings fine...

That's very weird since it's there in my private builds, which I'll post when 4.4.159 is out, testing some values till then. I don't think I've added anything that could've affected that in my own builds. Do they not show up at all in cpu>boost settings?

Edit: It shouuuuuuuuuuld be fixed in the next build ._.
 
Last edited:

mp3deviant721

Senior Member
Jan 4, 2013
1,205
547
I see stune boost settings now!

Edit: now I see min CPU speed is at 806 for the big cluster and 518 for the small. I can't change it manually, it always goes back to those speeds.
 

Attachments

  • Screenshot_EX_Kernel_Manager_20180929-120235.png
    Screenshot_EX_Kernel_Manager_20180929-120235.png
    136 KB · Views: 736
Last edited:
  • Like
Reactions: idkwhoiam322

idkwhoiam322

Senior Member
Apr 19, 2015
578
1,336
I see stune boost settings now!

Edit: now I see min CPU speed is at 806 for the big cluster and 518 for the small. I can't change it manually, it always goes back to those speeds.

Yeah, fixed that xd

Yes, I'm aware. I've been using this the last 2-3 days and it seems to be better in my opinion, especially if you watch videos and stuff to avoid unnecessary boosting. These are the stock Qualcomm values and I haven't seen any real drop in battery life. I'll try this for one build and decide whether I want to keep it or go back to 300 or 230 MHz on 1.9. I don't think we're actually gaining anything by setting it any lower, but time will tell :)
 

mp3deviant721

Senior Member
Jan 4, 2013
1,205
547
Yeah, fixed that xd

Yes, I'm aware. I've been using this the last 2-3 days and it seems to be better in my opinion, especially if you watch videos and stuff to avoid unnecessary boosting. These are the stock Qualcomm values and I haven't seen any real drop in battery life. I'll try this for one build and decide whether I want to keep it or go back to 300 or 230 MHz on 1.9. I don't think we're actually gaining anything by setting it any lower, but time will tell :)

Interesting. Does OOS use those values too or is it strictly a Qualcomm thing?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 59
    DxyIh9y.jpg
    Indroduction:
    Weeb Kernel is based on latest CAF with a minimal import off OnePlus's provided source code to retain functionality.

    Feel free to ask for any feature requests, but if I think something is useless or doesn't provide any benefit to warrant its addition, I will NOT add it, irrespective of how many people ask for it.

    Code:
    /*
     * Your warranty is not void (Thank you OnePlus!).
     *
     * I am not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this Kernel
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at me for messing up your device, I will laugh at you.
     */

    Supports:
    - Custom ROMs on 9, 10
    -- WiFi will not work on ROMs that use qcacld as a module ( eg. Omni, Treskmod Pie )

    Reporting Bugs:
    If you want to report any bugs, please post a logcat and dmesg(using an app like syslog), thank you!

    Features:
    - Here

    Downloads:
    - Github Releases

    Telegram Channel: Weeb Announcements
    Join me in my Café: // Weeb Karamel Café //

    Flashing Instructions:
    - Simply flash the kernel
    - If you have magisk AND if you are on android 10, reflash magisk after flashing the kernel

    Reason behind the name?
    Well, I originally even thought about making this because of some mates in a weeb telegram chat. I'm aware of a kernel of the same name by raphielscape which is now renamed, and she was okay with me using this name.

    Credits and Thanks:
    - raphielscape for inspiration and dealing with my extremely stupid questions ( she is my sensei ;) )
    - osm0sis for AnyKernel3
    - nathanchance, Akhil Narang, MSFJarvis, kdrag0n, celtare21 et al for their help in totally random places :d
    - The Linux Foundation, CAF and OnePlus for the code

    Sauce: Ketchup and Mayo Mix

    Version Information:
    Stable Version: Weeb Kernel v3.00 CodeName Ricardo
    Release Date on XDA: 05-11-2019

    P.S I don't care about OT XD

    El Psy Congroo~
    24
    New beta based on Hentai r54 is up!

    Changelog:
    - Switched to Drone CI ( Hence the reset in the rVersion, sorry for that but this CI is up to 6x faster than my older one )
    - Merged LTS 4.4.184
    - Silenced some more logging
    - More sched backports
    - Reverted some ( more than you'd think ) questionable sched changes
    - Updates to schedutil governor
    - Exposed CIB input boost values to userspace, feel free to configure them. Note that these will also be used to boost PER FRAME and not only for input, so don't bother changing the duration.
    - Memory leaks fixed by kerneltoast
    - Bumped top-app/schedtune.boost to 5
    - Reconfigured qcacld-3.0 options

    Anykernel changes:
    - Remove build.prop changes ( will be reset to stock on flashing kernel )
    - sync with AK3 source

    Downloads:
    - OOS
    - Custom
    - Omni
    24
    Weeb Kernel v2.45 CodeName Quincy

    New stable based on Hentai r178 is up!

    Changelog:
    - Now compiled with bare metal GCC 9.1 compiled by kdrag0n ( hence the reduction in size )
    - Merged latest OnePlus OB changes
    - Merged LTS tag 4.4.185 from kernel.org
    - Merged latest CAF msm8998 tag LA.UM.7.4.r1-05300-8x98.0
    - Merge latest CAF QCACLD tag - LA.UM.7.3.r1-07900-sdm845.0
    - Switch to sdm845 qcacld based on tag LA.UM.7.3.r1-07800-sdm845.0
    - Merged latest kernel/common f2fs changes
    - Reverted potentially not properly done brickport of mainline vmalloc for the sake of stability
    - Fix plug_in causing windoze to ask for device to be formatted
    - Add back biasing to big cluster on stune boosted tasks
    - Several performance improvements from kerneltoast
    - Enabled cpu input boost on OOS
    - Added KLAPSE 5.0 by tanish2k09
    - Remove charging logs by 0ctobot
    - Update stune_assist to latest and improve it ( see next )
    - Basically killed userspace cpu freq and stune modifiers ( init, powerhal, sched_boost etc. )
    - Introduce cpuset_assist by yaro
    - Restrict foreground to just 0-3 to reduce task contention for top-app tasks on big cluster
    - Sync some changes from kernel/common android-4.4 branch to sdcardfs and cpuset
    - Silenced some more logging
    - More sched backports
    - Reverted some ( more than you'd think ) questionable sched changes
    - Updates to schedutil governor
    - Exposed CIB input boost values to userspace, feel free to configure them. [ Default cpu input boost settings: 1036/1132 MHz for 500ms ]
    - Memory leaks fixed by kerneltoast
    - Reconfigured qcacld-3.0 options
    - Update dynamic memory allocation commits to kerneltoast's latest
    - Disable DEBUG_KERNEL
    - Disabled DEBUG_FS
    - some ufs ricing from essential phone and wahoo
    - sched/fair ricing from CAF
    - readded a ( should be ) safe cpuset commit
    - relax qcacld-3.0 workqueues
    - hack some icnss wakeups

    Anykernel changes:
    - Bumped to Anykernel3
    - Removed kernel config changes ( thanks to cpuset assist and stune assist )
    - Added build.prop tweaks ( if you don't want to deal with some minor visual issues,
    then remove "debug.hwui.renderer=opengl" in vendor/build.prop and reboot ) ~ thanks to Kuran

    Downloads:
    - OOS
    - Custom
    - Omni
    24
    Weeb Kernel v2.10 CodeName AURA​

    Downloads:
    OxygenOS // Custom ROMs // Omni based Custom ROMs (OmniROM, TreskMOD)

    Changelog:
    - Rebased cleanly on OnePlus's source again, removed a lot of commits I considered as bloat
    - Compiled using AOSP Clang 8.0.8
    - Linux Upstream 4.4.176
    - Upstreamed to latest CAF tag [LA.UM.7.4.r1-04700-8x98.0]
    - F2FS upstreamed to kernel/common [February] along with some improvements from arter97
    - NTFS R/W support
    - Reset LMK to android 4.4 state and improved on that.
    - Several ZRAM Improvements
    - SELinux: Disable auditing
    - Some minor enhancement memes
    - lz4 upstreamed
    - relaxed some wakeups
    - removed some unnecessary code
    - Cleaned up more OnePlus code
    - Improvements to dynamic schedtune boost by joshuous and RenderBroken
    - Improvements to devfreq
    - Upstreamed kthread
    - RCU Upstream
    - Added vdso32 support
    - CAKE as default net qdisc (thanks to kdrag0n)
    - Added High Brightness Mode
    - Several improvements to kernel/sched [Tweaked EAS implementation - thanks to KuranKaname for the backports]
    - Kernel Hardening patches from CopperHeadOS
    - Some other minor security related stuffs
    - Tweaked default settings
    - BFQ "backported" from 4.9 by me and set as default
    - kgsl backports (thanks to celtare21)
    - Improvements to kernel/sched
    - Reverted 2 commits from upstream that caused Sony Dualshock 4 controller connectivity issues (failure to connect at all) via Bluetooth
    - Moved to using a 100 Hz timer
    - Enabled USB Fast Charging (DISABLED by default)
    - Disable KALLSYMS since we have useless pstore, and this allows us to have a significantly smaller kernel image
    - Performance cluster underclocked to 1958400 kHz - Does not affect performance significantly but has improvements in device temperature and some decent improvements in battery

    Default setup:
    top-app/schedtune.prefer_idle = 1
    foreground/schedtune.prefer_idle = 1
    top-app/schedtune.boost = 0 [My reason for the top-app schedtune.boost being zero is that we do not really need any boosting when nothing significant is going on, for example, watching a youtube video, or the network indicator changing every second or so. For this reason, I have set it to 0, it does not seem to affect UX in my testing and should be just fine.]
    Dynamic Schedtune Boost = 15 [Duration: 1500ms]
    top-app/schedtune.sched_boost = 15
    CPU Boost = 1036/1056 [Duration: 500ms]

    ZRAM Tuning:
    swappiness = 8
    dirty_ratio = 5
    dirty_background_ratio = 2


    If you feel I've missed out something or something is wrong, feel free to ping me.
    20
    Weeb Kernel v2.22 CodeName: Pandemonium

    Downloads:
    OxygenOS // Custom ROMs // Omni based Custom ROMs (OmniROM, TreskMOD) // Hax (CodeName Phoenix, Dirty Unicorns)

    Changelog:
    - Compiled using AOSP Clang 9.0.1
    - Upstreamed to latest CAF tag [LA.UM.7.4.r1-04800-8x98.0]
    - Revamped EAS implementation [Thanks to Josh for the base and several backports by Kuran and some by others and me]
    - Moved to using a 625 Hz timer
    - Re-enabled KALLSYMS
    - Added ULPS mode
    - Performance cluster underclocked to 1958400 kHz - Does not affect performance significantly but has improvements in device temperature and some decent improvements in battery [Disabled by default]

    Default setup:
    top-app/schedtune.prefer_idle = 1
    foreground/schedtune.prefer_idle = 1
    top-app/schedtune.boost = 0 [My reason for the top-app schedtune.boost being zero is that we do not really need any boosting when nothing significant is going on, for example, watching a youtube video, or the network indicator changing every second or so. For this reason, I have set it to 0, it does not seem to affect UX in my testing and should be just fine.]
    Dynamic Schedtune Boost = 15 [Duration: 1500ms]
    top-app/schedtune.sched_boost = 15
    CPU Boost = 1171/1056 [Duration: 500ms]

    ZRAM Tuning:
    swappiness = 8
    dirty_ratio = 5
    dirty_background_ratio = 2

    Kernel variants:
    #oos:- This is for OxygenOS. It should also work for HydrogenOS but it's not tested directly by me. I'm typically using this myself.
    #custom:- This is for ROMs that use Lineage's implementation of the Qualcomm WLAN Module, that is, inlined and WITHOUT Sultan's hacks.
    #omni:- This is for ROMs that use CAF's implementation of the Qualcomm WLAN Module, that is, as a module. eg. Omni, Treskmod
    #hax:- This is for ROMs that use the Qualcomm WLAN Module as inline and with sultan's hacks to make it load during device init call. eg. CodeName Phoenix, Dirty Unicorns

    Note:
    Unfortunately, none of these work with each other, so each variant is for itself. Pick the right one before reporting that wifi doesn't work, thanks. Also, note that sometimes, on Pie, the ROM might just reject the WLAN module for no good reason and it's not unique to our device. I've seen and confirmed that this issue happens on other 4.4.x devices like Whyred as well.
    To solve this, simply reboot or reflash the kernel. If neither of these work, dirty flash the ROM and then kernel again. If you're flashing Magisk, please flash it BEFORE the kernel to retain ramdisk changes (if) made by the kernel.



    Announcement:
    As of this release, I've decided to move the source to the [raphielgang] organization repository.
    You can find the new source link for stable builds here.
    Major thanks to @raphielscape and the rest of the people for their help. :)