yashsingh1/xdaforums huggingface dataset:
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
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 :)
[OnePlus 5 & 5T Cross Device Development] mp3deviant721:
Interesting. Does OOS use those values too or is it strictly a Qualcomm thing?
[OnePlus 5 & 5T Cross Device Development] sleepwalking0593:
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. Dirty Unicorns

This will help you much better.

Thank you
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
Beta for the next release, fully rebased with a much better performing kernel/sched and unnecessary stuff removed. If you want to try it out, feel free to leave some (positive and/or negative) feedback!

Downloads: OOS // Custom // Omni

Note: No hax variants for betas. So, crdroid and DU aren't compatible.

At the top of my head, changelog would be reworked eas implementation, cfq upstreamed, zram disabled, oos upstreamed, caf upstreamed, f2fs upstreamed, LTS upstreamed, bunch of fixes here and there, some backports from 4.9, 4.14 CAF, ULPS support, KCAL, top-app/schedtune.boost locked at 1, no cpu_boost or dynamic stune boost by default, latest aosp clang.

Using AFH cuz only stable goes into gdrive.
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
Reuploaded, sorry about that. Don't know why OOS was rejecting the hardcode, but it's hardcoded stune 1 now.
[OnePlus 5 & 5T Cross Device Development] Z-Blade:
Been on the beta for about 24 hours now, so far pretty happy with what I see and no bugs encountered. I did do a full clean install of 9.0.5 OOS just before flashing the kernel so it performing extremely well right now on a fresh rom install.
[OnePlus 5 & 5T Cross Device Development] fjsferreira:
Beta working beautifully on latest oos beta.
[OnePlus 5 & 5T Cross Device Development] flatratte82:
Same for OOS 9.0.5 stable. No lags or issues so far.
[OnePlus 5 & 5T Cross Device Development] jc1266:
Hi .. can you share yr setting on this kernel .. currently I oos beta also , thanks in advance .
[OnePlus 5 & 5T Cross Device Development] fjsferreira:
Just turned on fast USB charge, nothing more.
[OnePlus 5 & 5T Cross Device Development] espionage724:
How does the F2FS support work?

I'm using LineageOS 16.0. I have some Data I want to keep for a bit, and right now my /data partition is ext4 still. Cache however I formatted to F2FS from TWRP, but upon doing that, LOS doesn't boot (stays at boot animation).

Can I do that (/data as ext4, /cache as f2fs), or do both need to be the same filesystem? Or is LineageOS not supporting f2fs?

This is with the latest beta-r66 kernel posted a few posts back.

Edit: Here's what I managed to figure out

/cache needs to be ext4 no matter what

/vendor gets set to ext4 when flashing LOS, and can't be changed afterwards

/data can be F2FS

if /data is F2FS, arter97's f2fs fstab needs to be flashed in order to boot

If /data is F2FS with arter97's f2fs fstab flashed, you aren't encrypted out-the-box; not sure if encryption on F2FS is supported

With twrp-3.3.0-0-20190427-codeworkx-cheeseburger, arter97's f2fs TWRP tools zip doesn't work and won't format /data properly; no idea what's up, but it's not needed for successful boot
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
Yes, the kernel supports f2fs. Prior to arter's kernel, mine was the only one fully upstreamed with kernel/common and arter's Rapid GC. :P

There is no reason to convert anything other than data to f2fs, ROM support isn't exactly required, that's the point of arter97's fstab modification zip. AFAIK, on our device, f2fs doesn't support FBE, FDE *should* be possible but I don't think anyone has tried.

This is what a friend did to get on f2fs:

backup + twrp stuff + flash ROM + format /data to f2fs + fstab zip + magisk + kernel.

He did it with blu_spark twrp
[OnePlus 5 & 5T Cross Device Development] dsahai:
Trying the new beta now. So far so good!
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
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
[OnePlus 5 & 5T Cross Device Development] fjsferreira:
Hum, wifi not turning on with latest beta weeb on oos stable... I see the ko file is no longer included in the zip, is this why?
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
hmm I'd have thought using arter's commit for inlining it would've worked just fine. Can you try dirty flashing ROM and reflashing kernel? If not, I'll just revert back to modules :/
[OnePlus 5 & 5T Cross Device Development] flatratte82:
WiFi works fine on my side.

I'm on OOS 9.0.5
[OnePlus 5 & 5T Cross Device Development] destro63x:
No issues with wifi here.....Open Beta 31
[OnePlus 5 & 5T Cross Device Development] djport1973:
Installed on op5 with havoc 2.4. For the moment everything is fine.

Enviado desde mi ONEPLUS A5000 mediante Tapatalk
[OnePlus 5 & 5T Cross Device Development] fjsferreira:
I will try dirty flashing the rom first. Should've done that before complaining :)
[OnePlus 5 & 5T Cross Device Development] dsahai:
Damn...oh well :)
[OnePlus 5 & 5T Cross Device Development] 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.
[OnePlus 5 & 5T Cross Device Development] destro63x:
Using custom 19.2 here
[OnePlus 5 & 5T Cross Device Development] 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.
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
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.

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.
[OnePlus 5 & 5T Cross Device Development] Dimontiman:
Everything smooth

OB 31 OOS
[OnePlus 5 & 5T Cross Device Development] Tilman:
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.
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
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.
[OnePlus 5 & 5T Cross Device Development] 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
[OnePlus 5 & 5T Cross Device Development] falleny:
So good... sounds like we will have a stable build very soon.... thanks
[OnePlus 5 & 5T Cross Device Development] fjsferreira:
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.
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
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.
[OnePlus 5 & 5T Cross Device Development] falleny:
Flash last beta on oos stable 9.0.5 so far so good...thanks Dev
[OnePlus 5 & 5T Cross Device Development] str8str:
Is there a reason I can't change minimum CPU? Has option for down to 300 but won't take
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
I'm rejecting all frequencies below 1036/806, that's why.
[OnePlus 5 & 5T Cross Device Development] valeriee:
Is stable release coming soon?
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
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.
[OnePlus 5 & 5T Cross Device Development] 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
[OnePlus 5 & 5T Cross Device Development] str8str:
Hi I'm curious about how the lower frequencies are detrimental. My big cluster uses 230 most then 300 then 422 and small 364,441 seems to be the fav. Phone runs great

The only thing and I have no clue what causes it but sometime it's a little stubborn to wake up. As you see these lower ones are used
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
Have a look at this commit by kerneltoast ( sultanxda ) : https://github.com/kerneltoast/andr...mmit/e034b8f7299e9e3b2d6f5a3fc931982b00ca6a91

He calculated the efficiencies of each frequencies based on time taken for some ( equal ) work done and power costs and you can clearly see that the lower frequencies are terrible in terms of efficiency. They also cause increase in power consumption actually. During video watching, frequencies jump a lot and that costs power. Overhead in schedutil governor, cpuidle, general scheduling does not help either.
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
Small misspell in anykernel.sh. Thanks to [MENTION=5893314]shadowstep[/MENTION] for pointing it out. Fixed and re-uploaded. Times when ONE character can make a difference >.> Please dirty flash ROM and reflash the kernel. I apologise for any inconvenience.

Was a big release and I'm going to take a break for a while. Need to catch up on some sleep :)
[OnePlus 5 & 5T Cross Device Development] str8str:
Very confusing. So what seems to be the magic numbers
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
I'm sticking to 518/806 ( Qualcomm defaults ) for the min-frequencies and letting find_best_target() and biasing performance cores with top-app/schedtune.boost 1 to do the decision making on what should be used.

Small update: I misinterpreted on how this magisk-bypass for applying modifications without magisk should be working so currently cpusets don't apply right. Should be perfectly fine on custom ROMs, but CAF's default cpusets are a bit harsh. Will rectify ( already done thanks to 0ctobot and kdrag0n's patience in explaining everything to me and I'll push an update later today or tomorrow whenever I'm in the mood, but soon enough :) )
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
Weeb Kernel v2.315 CodeName BEHEMOTH​

Downloads: OxygenOS // Custom ROMs // Omni Based Roms

Changelog

- Silenced an annoying logger

- Fixed cpusets not applying properly ( thanks to 0ctobot and kdrag0n for their explanation and patience )
[OnePlus 5 & 5T Cross Device Development] Sparda333:
First time seeing this kernel am interested could you tell me about it compare to stock OOS kernel.
[OnePlus 5 & 5T Cross Device Development] Z-Blade:
All of the info you need to know is in the OP, if you want to know what all of that mean you will need to use Google and find out (I don't know what half of the stuff in OP really means). This is a flash and forget kernel, majority of us don't really touch the default settings.

Best thing to do is just flash it and give it a try, from my point of view, this is the best kernel for me.
[OnePlus 5 & 5T Cross Device Development] Tilman:
Should the values under dev/cpuset/*/cpus be the same as in the file init.target.rc in the kernel zip file? Cause for me they're not the same values.
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
Which version? And what ROM? And could you tell me what cpusets you have?
[OnePlus 5 & 5T Cross Device Development] Tilman:
The latest 2.315 version and stock OOS 9.0.5.

For Audio-App CPUs are 0-7.

Background CPUs are 0-3.

Camera-Daemon CPUs are 0-3.

Foreground CPUs are 0-7.

Restricted CPUs are 0-7.

System-Background CPUs are 0-3.

Top-App CPUs are 0-7.
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
hmm strange.

Could you reflash and send me a dmesg as well as your /vendor/etc/init/hw/init.target.rc?
[OnePlus 5 & 5T Cross Device Development] Tilman:
Here you go.
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
Thanks! I think I know why. I'll give you a build to try in a while and check if you don't mind. If that doesn't work, I'll probably move back to making magisk a requirement, but it should. As far as I can understand, the timing is the problem.
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
Try this one, please:

https://drive.google.com/file/d/1kOtS-sz7SihQZmxfAOzlj_sFM4xjV4VG/view?usp=drivesdk
[OnePlus 5 & 5T Cross Device Development] Tilman:
Really appreciate your dedication to solve this as soon as you can.

Yes this build works, all values are applied correctly.

Also couldn't see this directory "write /dev/cpuset/system/cpus 0-1,6-7". Maybe you can delete this line?
[OnePlus 5 & 5T Cross Device Development] str8str:
This fix only sold to oos? Or custom as well
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
Depends on the ROM so I'll keep it :p Thanks so much, will release with the fix in few once I'm fully awake XD
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
Technically all but most custom ROMs apply proper cpusets anyways so it's not a big problem for them.
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
Weeb Kernel v2.316 CodeName BEHEMOTH​

Downloads: OxygenOS // Custom ROMs // Omni Based ROMs

Changelog:

- Actually fix cpusets ( there was an issue with the timing of applying them )
[OnePlus 5 & 5T Cross Device Development] Izzy2004:
Hey. I just wanted to say thanks. I'm running crdroid and this and everything is very smooth and fluid. I had a touchscreen issue but it is completely fixed and very responsive again. Thanks my man im glad I chose this arbitrarily because of the anime chick.

Cheers!
[OnePlus 5 & 5T Cross Device Development] espionage724:
Flashed 2.316 custom on LineageOS 16.0 (lineage-16.0-20190513-microG-cheeseburger); after booting and entering my pin, I'm stuck at "Phone is starting..."

Rebooting doesn't fix it. Cache/Dalvik wiped from TWRP. Can't quite remember the last kernel or LOS version combination I tried, but this kernel did work on LOS 16.0 before.
[OnePlus 5 & 5T Cross Device Development] sleepwalking0593:
ROM issue. It's a LOS bug
[OnePlus 5 & 5T Cross Device Development] zydezh:
能不能开启下zram？我的OnePlus5只有6gram，After opening some software, the memory usage of the phone is very high，像QQ微信
[OnePlus 5 & 5T Cross Device Development] str8str:
Is this still in development
[OnePlus 5 & 5T Cross Device Development] Lxeon:
sir, how can i enable zram? i want keep more app on background, thanks you.
[OnePlus 5 & 5T Cross Device Development] Z-Blade:
Get yourself a Kernel Management app and you can use that to customise the ZRAM to liking.
[OnePlus 5 & 5T Cross Device Development] Lxeon:
no any options for zram by using ex kernel or kernel adiutor
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
https://github.com/RaphielGang/weebmsm8998-pie/blob/pie-r2/arch/arm64/configs/weeb_defconfig#L1207

It's disabled.
[OnePlus 5 & 5T Cross Device Development] Lxeon:
oh..ic, thx.
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
New beta based on Hentai r565 is up!

Changelog since Stable 2.316

- 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.183 from kernel.org

- Merged latest CAF msm8998 tag LA.UM.7.4.r1-05300-8x98.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 ( Use EXKM or something else for now, FKM support soon )

- 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

Anykernel changes:

- Sync with source ( Now updated to anykernel3 )

- Add some neat build.prop tweaks from kuran kaname that improved jitter a lot

Downloads:

- OOS

- Custom

- Omni
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
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
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
New beta based on Hentai r122 is up!

Changelog:

- Fixed several memory leaks by kerneltoast

- update dynamic memory allocation commits to kerneltoast's latest

- merge latest kerneltoast commits

- disable DEBUG_KERNEL ( hence the smaller zip )

- disabled debug_fs ( further reduction in zip size )

- disabled per frame cpu input boost

- default cpu input boost settings: 1036/1132 MHz for 500ms

Anykernel changes:

- sync with AK3 source

What to check?

- Device boots?

- General stability and performance ( report if any panics cuz suntan fixed several )

Downloads:

- OOS

- Custom

- Omni

I'd love it if I got more feedback just like I do on telegram. Helps me understand what changes are good and what should be altered/removed as my usecase is not the same as everyone else's.
[OnePlus 5 & 5T Cross Device Development] h4waii:
Wrong thread!
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
It's a unified kernel so tbh you can post about it in either of the threads.
[OnePlus 5 & 5T Cross Device Development] str8str:
So it booted and is sleeping like a baby. Don't see any issues yet. I'm on custom
[OnePlus 5 & 5T Cross Device Development] dd0s:
So much better than last build, congrats
[OnePlus 5 & 5T Cross Device Development] mp3deviant721:
R122 is being pretty good. No issues so far and performance is good.
[OnePlus 5 & 5T Cross Device Development] adefigo:
Latest kernel has problems with "Reading Mode" on OOS Beta. Screen gets black, even after reboot. Had to flash stock kernel to be able to deactivate reading mode again.

Sorry no log as I'm on the road.
[OnePlus 5 & 5T Cross Device Development] jordirpz:
+1
[OnePlus 5 & 5T Cross Device Development] idkwhoiam322:
Confirmed and found the cause. Thanks.
[OnePlus 5 & 5T Cross Device Development] sjamie:
That was fast. You're amazing!