Weeb Kernel

idkwhoiam322

Senior Member
Apr 19, 2015
578
1,332
0
@idkwhoiam322 what do you think about F2FS? I used it on some of my old devices and it really made a difference but nowadays it's rare to see a device using it. I even tried to format the /data partition of my OP5 to F2FS but TWRP gave me an error and it did not work =(
The latest stable release of mine does NOT support F2Fs because I did not intend to add support for it until I had merged in all the changes from Google (from kernel/common) and arter97. I have added support for it in the future builds (2.1x) which should be released in the upcoming days, if all goes well.
I have not tried it myself, but I have confirmed that it boots. You'll need to use arter97's zips from his OnePlus 6 or MiPad 4's xda thread (they are generic - not device specific), to boot properly. A friend of mine has been running f2fs on his own kernel (not public) with pretty much the same changes for a while now without any issues, so t should be just fine.
Most apps use SQLite for database purposes, so there will certainly be a difference in usage. The reason people do not use it as often now is because of instability concerns, but these issues seem to have been addressed by Google and the F2FS maintainers in upstream (all backported to 4.4.x all the way from 5.0-rc's thankfully :D).
 
  • Like
Reactions: angourakis

Sinaptik

Senior Member
Mar 31, 2010
181
32
48
Evreux
Amazing battery life with this kernel with medium/heavy usage. Using Pico gapps from xXx helps so much with battery
No offense but are you really considering those stats as "amazing"?
I mean it's just standard or even worse then standard battery backup, nothing impressive I would say.
You're probably running with the original battery and it's probably worn.
If you consider there's a real improvement, do you have similar stats screenshots without Weeb to compare?
 

8hodgsonkh

Senior Member
Jan 16, 2014
480
169
0
23
Carlisle
No offense but are you really considering those stats as "amazing"?
I mean it's just standard or even worse then standard battery backup, nothing impressive I would say.
You're probably running with the original battery and it's probably worn.
If you consider there's a real improvement, do you have similar stats screenshots without Weeb to compare?
It's amazing for what it is compared to other kernels. I use YouTube vanced a lot. Have loads of battery hogging social media tinkering at my battery when screen is off. Also my battery health is only 80% according to OP diagnostic

I can get 6-7 sot without using YouTube vanced usually. %11/h screen on and 0.8% screen off

Other kernels I had like 15-16% screen on and 2-3 screen off but I don't have any old screenshots since I don't change kernel and play around anywhere near as much as I used to
 
Last edited:

Z-Blade

Senior Member
Jan 29, 2012
550
242
63
Perth
No offense but are you really considering those stats as "amazing"?
I mean it's just standard or even worse then standard battery backup, nothing impressive I would say.
You're probably running with the original battery and it's probably worn.
If you consider there's a real improvement, do you have similar stats screenshots without Weeb to compare?
You just need to take his word for it. Everyone uses their phones differently so it makes it near impossible to compare your experience with others. I have tried a few EAS kernel but in my opinion, this is by far the best EAS kernel I have tried with the best battery life.
 
  • Like
Reactions: 8hodgsonkh

idkwhoiam322

Senior Member
Apr 19, 2015
578
1,332
0
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.
 
Last edited:

flatratte82

Senior Member
Dec 15, 2010
160
55
48
I have an issue installing weeb 2.10.
The installation abort with error 1 when unpacking and installing the ramdisk.
I have magisk 18.1 installed.
Is there anything I can do about this?
 

idkwhoiam322

Senior Member
Apr 19, 2015
578
1,332
0
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. :)
 
Last edited:

sleepwalking0593

Senior Member
Jul 25, 2017
1,031
283
83
Noida
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 300 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 = 1036/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. :)
After every reboot the phone high brightness mode is enabled automatically have to disable it manually everytime on codename phoenix.