Weeb Kernel

[djport1973]

Installed on op5 with havoc 2.4. For the moment everything is fine.

Enviado desde mi ONEPLUS A5000 mediante Tapatalk

 

[fjsferreira]

I will try dirty flashing the rom first. Should've done that before complaining

Sent from my OnePlus 5 using XDA Labs

 

[dsahai]

Beta r151 is up! ( Just waiting on next CAF tag for release at this point, almost the same as SDM660 but I don't want to merge QCACLD changes from SDM660 tag so I'll just wait for the MSM8998 tag)
Changelog since r66:
- sched improvements [ from caf 4.14 by me, kuran; 4.9 by kuran, and some minor stuff ]
- some power saving improvements by kerneltoast
- Dsiabled CPU_BOOST
- Removed DYNAMIC_STUNE_BOOST
- Properly fake sched_boost to do nothing
- Hardcode ( still changeable by userspace ) as much as possible in the kernel as possible. Only cpusets remain.
- 1036 min frequency for the small cluster [ I've seen battery and performance improvements with this change ]
- disabled IPC logging
- some memory leaks fixed
- some mm patches thanks to okhttp backported from 4.9
- All variants now use qcacld as inline but separate variants remain
- some fixups to some ufs related modifications by kerneltoast by kerneltoast ( yes this is right grammatically )
- Merged SDM660 tag LA.UM.7.2.r1-06900-sdm660.0 ( No qcacld )
- Merged Android Security Bulletin — May 2019 tag.


Please lemme know if there are any stability issues. I'll remove the ASB merge, there were too many conflicts but I think I resolved them correctly.

Downloads: OOS // Custom // Omni








should've waited XD

Damn...oh well

 

[fjsferreira]

Still no wifi after dirty flashing stock oos first. What magisk are people using? I'm using 19.1 stable in a decrypted op5...

I self compiled the kernel (with just led control added), could this be it? It shouldn't make any difference.

Sent from my OnePlus 5 using XDA Labs

 

[destro63x]

Using custom 19.2 here

 

[Tilman]

Working fine here - the latest beta. No issues with wifi. Maybe you can add Zen & Maple I/O schedulers if you get time? Also, an option for users to stick to 300-300/500-816 Mhz as minimum Cpu frequency, would that be possible?
I was using BluSpark for a long time, and loving the smoothness of this kernel. Thanks for your work.

 

[idkwhoiam322]

Working fine here - the latest beta. No issues with wifi. Maybe you can add Zen & Maple I/O schedulers if you get time? Also, an option for users to stick to 300-300/500-816 Mhz as minimum Cpu frequency, would that be possible?
I was using BluSpark for a long time, and loving the smoothness of this kernel. Thanks for your work.

Why do you want io schedulers that perform worse?
I'll think about 518/806 but I'm not going to support frequencies lower than that including 300/300 as they're detrimental to performance and battery life. I might test again though before deciding.

Still no wifi after dirty flashing stock oos first. What magisk are people using? I'm using 19.1 stable in a decrypted op5...

I self compiled the kernel (with just led control added), could this be it? It shouldn't make any difference.

Sent from my OnePlus 5 using XDA Labs

Most likely I'll just revert to modules.
What source did you compile the kernel from? Do you have it pushed? I Can have a look then.

 

[Dimontiman]

Beta r151 is up! ( Just waiting on next CAF tag for release at this point, almost the same as SDM660 but I don't want to merge QCACLD changes from SDM660 tag so I'll just wait for the MSM8998 tag)
Changelog since r66:
- sched improvements [ from caf 4.14 by me, kuran; 4.9 by kuran, and some minor stuff ]
- some power saving improvements by kerneltoast
- Dsiabled CPU_BOOST
- Removed DYNAMIC_STUNE_BOOST
- Properly fake sched_boost to do nothing
- Hardcode ( still changeable by userspace ) as much as possible in the kernel as possible. Only cpusets remain.
- 1036 min frequency for the small cluster [ I've seen battery and performance improvements with this change ]
- disabled IPC logging
- some memory leaks fixed
- some mm patches thanks to okhttp backported from 4.9
- All variants now use qcacld as inline but separate variants remain
- some fixups to some ufs related modifications by kerneltoast by kerneltoast ( yes this is right grammatically )
- Merged SDM660 tag LA.UM.7.2.r1-06900-sdm660.0 ( No qcacld )
- Merged Android Security Bulletin — May 2019 tag.


Please lemme know if there are any stability issues. I'll remove the ASB merge, there were too many conflicts but I think I resolved them correctly.

Downloads: OOS // Custom // Omni








should've waited XD

Everything smooth

OB 31 OOS

 

[Tilman]

Why do you want io schedulers that perform worse?
I'll think about 518/806 but I'm not going to support frequencies lower than that including 300/300 as they're detrimental to performance and battery life. I might test again though before deciding.

Well in my previous phone, Z5 Premium, mostly every dev suggested these I/O schedulers including even TripNDroid. Anyway, I'll take your word for it about CFQ.
Thanks for considering the lower frequency ranges.

 

[idkwhoiam322]

Well in my previous phone, Z5 Premium, mostly every dev suggested these I/O schedulers including even TripNDroid. Anyway, I'll take your word for it about CFQ.
Thanks for considering the lower frequency ranges.

I'll be honest, anyone that includes every single cpu, iosched governor out there doesn't really know what they're doing lol [ Not that I'm a pro dev or anything, I'm very new to this stuff ]
HMP needs a properly tuned interactive, and EAS - schedutil. I have patches all the way from Linux 5.x ( thanks to Kuran (celtare21) and very few from ) that make it even better.
The same for io scheds. CFQ with upstream patches outperforms others overall and Google recommends it too and uses it themselves.

 

[idkwhoiam322]

Build r185 is up!
Changelog since r151:
- Dropped ASB and sdm660 tags
- Merged latest msm8998 tag "LA.UM.7.4.r1-05100-8x98.0".
- Merged several stuff from Q (p2,3,3a)
- Fixed dt2w issue some might've had
- suntan ricing
- Went back to modules for OOS and omni builds

Please lemme know about stability. If all is good, I'll push as stable.
Downloads: OOS // Custom // Omni

 

[falleny]

So good... sounds like we will have a stable build very soon.... thanks

 

[fjsferreira]

Build r185 is up!
Changelog since r151:
- Dropped ASB and sdm660 tags
- Merged latest msm8998 tag "LA.UM.7.4.r1-05100-8x98.0".
- Merged several stuff from Q (p2,3,3a)
- Fixed dt2w issue some might've had
- suntan ricing
- Went back to modules for OOS and omni builds

Please lemme know about stability. If all is good, I'll push as stable.
Downloads: OOS // Custom // Omni

Yay wifi working again in my setup. Thank you.

BTW, any reason to not add led customization? Stock oneplus notification led rate is stupidly slow, it's asinine. Not a complaint as I build the kernel myself with that added, but to be able to customize led fading rate is so damn useful and doesn't affect performance or security in any way.

 

[idkwhoiam322]

Yay wifi working again in my setup. Thank you.

BTW, any reason to not add led customization? Stock oneplus notification led rate is stupidly slow, it's asinine. Not a complaint as I build the kernel myself with that added, but to be able to customize led fading rate is so damn useful and doesn't affect performance or security in any way.

I can have a look at it later AFTER this stable release. As far as I can remember, it caused some issue on custom ROMs, but I don't remember what it was.

 

[falleny]

Flash last beta on oos stable 9.0.5 so far so good...thanks Dev

 

[str8str]

Is there a reason I can't change minimum CPU? Has option for down to 300 but won't take

 

[idkwhoiam322]

Is there a reason I can't change minimum CPU? Has option for down to 300 but won't take

I'm rejecting all frequencies below 1036/806, that's why.

 

[valeriee]

Is stable release coming soon?

 

[idkwhoiam322]

Is stable release coming soon?

Hopefully. 4.4.180 is already pushed for review ( see https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git/log/?h=linux-4.4.y ) so I'll wait for that and for a few more days to ensure everything is fine then push.

 

[idkwhoiam322]

Weeb Kernel v2.314 CodeName BEHEMOTH​

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

Changelog
- Dependency on Magisk removed. Kernel modifies a file in vendor to adjust cpusets ( defaults for most things hardcoded in kernel, users free to modify them )
- Updated toolchain to AOSP clang 9.0.3
- Latest LTS merged from kernel.org - 4.4.180
- Latest CAF and QCACLD tag - "LA.UM.7.4.r1-05100-8x98.0"
- Latest f2fs merge from kernel/common
- Latest f2fs related commits ( like rapid gc ) from arter97 as per May 15 2019
- Latest fixes for clang support
- Used latest GCC and clang to fix several code issues detected
- Cleaned up some OnePlus code
- kanged pixel 3 cpusets
- Disabled CAF CPU_BOOST
- ULPS mode for display
- Disabled audit
- HZ 100
- Lower touch latency
- kerneltoast's ( aka sultanxda ) devfreq boost driver
- Removed qos code added by oneplus
- Redone EAS implementation - seems to work much better now as reported by users and seen by myself
- Several EAS backports from higher kernel versions ( 4.9, 4.14, 4.19, some from mainline too )
- schedutil updated with several patches from higher kernel versions
- Some softirq backports from mainline that improved jitter
- CRC32 backports by arter97
- RCU and cpufreq backports by celtare21
- Several improvements from p2 and p3/a Q tag
- Disabled a ton of unnecessary logging
- top-app schedtune.boost locked at 1
- Removed unused frequencies ( All frequencies below 518400 and 806400 have been removed )
- Stune_assist v2 by YaroST12 ( used to set prefer_idle values to 1 for foreground and top-app )
- cpuidle, kgsl, mdss, qos and ufs power efficiency improvements by kerneltoast
- Fake sched_boost proc to fool userspace since I'm not using dynamic stune boost
- Removed excessive debug bloat from qcacld
- hax variant dropped
Full feature list: https://github.com/whoknowswhoiam/weebmsm8998-pie/tree/README#features