• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Kernel | Android 10 | One UI 2.5 | FUF5/FUH1] BeastMode Kernel v2 for N960F | v2.12 | 20211024

Search This thread

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,035
2,914
ykkfive.blogspot.com
You're welcome, overall Performance seems to be equal than before. Decreasing read speed doesn't feel bulkier than previous version.
As expected the performance is the same as before. I don't usually do storage benchmarks for non F2FS platforms because they will be obviously not as fast as they can possibly be. Not much else to say. These are pretty useful tweaks though. Keep it up man.


glad to hear at least it performs on par with the previous one, as more and more features added the performance could be affeced especially some tracing functions have been introduced

anyway, thanks for you guys' time as i cannot check every aspects every time i release a new version. of coz i would like to see perfomance gain each time but it's not guaranteed. so keep me informed or otherwise we wouldnt have a revised version based on the previous built which out performed as much as 30%

so pls continue to provide me feedbacks and tell me if you like it

thanks
 
Either way, the same previously known issues remain, and they can be quite bad for gaming and work performance. I'll do the usual summary.

1: CPU only goes to 2886MHz in single core (I have found 2964MHz as maximum frequency in the sys files but it isn't in the freq table so it isn't used for single core). Dual core and Quad Core are at 2314MHz and 1794MHz respectively. Pushing Dual at 2496 or 2652MHz and Quad at 2314MHz will dramatically increase performance at a moderate battery life cost (2314MHz was originally the intended Quad Core mode frequency of the 9810, and in fact, above that, diminishing returns suddenly appear.).

2: System throttles at 70°C. It is an extremely conservative choice considering we are overclocking a phone. Throttling causes a bug that makes the user unable to reach 2002MHz on small cores (Hard caps at 1950MHz even if I try to change in hKTweaks). Same for GPU, but the hard cap frequency varies there. Putting 90°C is a good balance between safety and maximum possible performance.

3: GPU frequency just does whatever it wants. Rising the minimum frequency to anything higher than 260MHz in an attempt to get more gaming performance doesn't work. Boost frequency threshold at 15% doesn't seem to make the GPU boost aggressively either.

4: If the GPU overclock is ever enabled again, it seems that there is a 775MHz frequency in the table. It would bring huge benefits to gaming. 598MHz is meh. It's just an extra 26MHz so.

That's all. The first 3 are bugs. The last one is just a suggestion.
 
Last edited:

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,035
2,914
ykkfive.blogspot.com
I am using this version since yesterday night, and it's definitely working well. Less heating and screen used to get non-responsive with the earlier version. But no such case with the newer version so far.

you mean compared with 2.10?
i didnt notice any huge differences except better battery consumption, could be due to there were too many internal builts for self testing, but it's a bump for you guys with about 10 builts skipped 😄
 

amit_coolcampus

Senior Member
Mar 30, 2013
273
35
Delhi
Samsung Galaxy Note 9
you mean compared with 2.10?
i didnt notice any huge differences except better battery consumption, could be due to there were too many internal builts for self testing, but it's a bump for you guys with about 10 builts skipped 😄
Yes 2.10 vs 2.11. My phone used to get over heated and then no response on touch. I dont know why. But it was random, normally it worked fine. Once touch was non-responsive, then only hard restart was the way. This one is working fine, fingers crossed.
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,035
2,914
ykkfive.blogspot.com
Either way, the same previously known issues remain, and they can be quite bad for gaming and work performance. I'll do the usual summary.

1: CPU only goes to 2886MHz in single core (I have found 2964MHz as maximum frequency in the sys files but it isn't in the freq table so it isn't used for single core). Dual core and Quad Core are at 2314MHz and 1794MHz respectively. Pushing Dual at 2496 or 2652MHz and Quad at 2314MHz will dramatically increase performance at a moderate battery life cost (2314MHz was originally the intended Quad Core mode frequency of the 9810, and in fact, above that, diminishing returns suddenly appear.).

2: System throttles at 70°C. It is an extremely conservative choice considering we are overclocking a phone. Throttling causes a bug that makes the user unable to reach 2002MHz on small cores (Hard caps at 1950MHz even if I try to change in hKTweaks). Same for GPU, but the hard cap frequency varies there. Putting 90°C is a good balance between safety and maximum possible performance.

3: GPU frequency just does whatever it wants. Rising the minimum frequency to anything higher than 260MHz in an attempt to get more gaming performance doesn't work. Boost frequency threshold at 15% doesn't seem to make the GPU boost aggressively either.

4: If the GPU overclock is ever enabled again, it seems that there is a 775MHz frequency in the table. It would bring huge benefits to gaming. 598MHz is meh. It's just an extra 26MHz so.

That's all. The first 3 are bugs. The last one is just a suggestion.

will look into these as i mentioned before since this one was focused on the file system updates. hopefully we can push it further after the ext4 problem just mentioned got fixed
 
  • Like
Reactions: TechNoobForSale

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,035
2,914
ykkfive.blogspot.com
Yes 2.10 vs 2.11. My phone used to get over heated and then no response on touch. I dont know why. But it was random, normally it worked fine. Once touch was non-responsive, then only hard restart was the way. This one is working fine, fingers crossed.

that's weird.... i have never faced that kind of problems before even with test builds. could it be dirty flashing custom roms?

anyway, glad to hear it finally get solved
 
Also to add that while trying to make my phone use F2FS I got such a big L. Thank God I had backups. I had changed system, cache and data to F2FS. So I formatted the phone. Tried to boot like an idiot forgetting I had...deleted the damn system with the conversion LMAO. I was on stock One UI 2.5 and Kernel Version 2.11c6. I have returned the partitions to EXT4 and also while trying to put the backup on the phone in TWRP I noticed I couldn't move the system emmc.win file because it's over 4GB. Making me unable to move the backup. Though I have others that I should be able to restore since their system is smaller. I am going to restore this EXT4 backup and hope it brings everything back to normal.

The bad part however is that the system_image.emmc.win file is 4.8GB therefore can't be moved on the phone. And having no system, I definitely can't move that. So what I wanted to ask you is that if the system.ext4.win files will be enough for me to restore the system. I don't even know if I should make the vendor partition F2FS too.
 
Last edited:
I will try to move on AlexisROM One UI 2.5. With my phone unusable I can't keep providing benchmarks for your Kernel versions. Therefore I have to do absolutely everything I can.

Edit: Moving over to AlexisROM was successful. However being unsure whether it supports F2FS or not I will stick with EXT4 for the time being.
 
Last edited:

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,035
2,914
ykkfive.blogspot.com
I will try to move on AlexisROM One UI 2.5. With my phone unusable I can't keep providing benchmarks for your Kernel versions. Therefore I have to do absolutely everything I can.

Edit: Moving over to AlexisROM was successful. However being unsure whether it supports F2FS or not I will stick with EXT4 for the time being.
so you have restored your phone now? i mean at least it is working properly atm ?
there are something that need to be done before going f2fs, i will tell you later why
 
so you have restored your phone now? i mean at least it is working properly atm ?
there are something that need to be done before going f2fs, i will tell you later why
Yes I managed to restore my phone from the soft brick status. The whole problem was actually due to a distraction mistake I made. It’s working and fine now though. But I am on EXT4 because I am not sure if the Alexis ROM 3.0 supports F2FS.
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,035
2,914
ykkfive.blogspot.com
Yes I managed to restore my phone from the soft brick status. The whole problem was actually due to a distraction mistake I made. It’s working and fine now though. But I am on EXT4 because I am not sure if the Alexis ROM 3.0 supports F2FS.

don worry, all (or most) custom roms, as well as stock rom, by default will format partitions to ext4, so you wont brick it. on the other hand, your f2fs partitions will be reformatted back to ext4 when you install a rom. although it's not ideal, you have to live with it unless they change the way how they handle the file system

for f2fs, you will need to modify the fstab.xxxxx file under vendor/etc/ by adding entries to tell the system to mount the partitons as f2fs or otherwise the mount process will fail

i don wanna talk about this too much as it is out of my control and out of the scope of a thread talking about kernel, since this should be discussed in the rom's thread in my humble opinion. however there are some good tutorials regarding how to convert from ext4 to f2fs though

i hope you will understand my situation
 
don worry, all (or most) custom roms, as well as stock rom, by default will format partitions to ext4, so you wont brick it. on the other hand, your f2fs partitions will be reformatted back to ext4 when you install a rom. although it's not ideal, you have to live with it unless they change the way how they handle the file system

for f2fs, you will need to modify the fstab.xxxxx file under vendor/etc/ by adding entries to tell the system to mount the partitons as f2fs or otherwise the mount process will fail

i don wanna talk about this too much as it is out of my control and out of the scope of a thread talking about kernel, since this should be discussed in the rom's thread in my humble opinion. however there are some good tutorials regarding how to convert from ext4 to f2fs though

i hope you will understand my situation
To be honest as far as I'm aware for ROMs like LineageOS, you can simply format the partition to F2FS and the ROM installer will simply write on that since Lineage does support F2FS. And either way there are different setups for F2FS. Like putting only data and cache as F2FS (which still grants the vast part of the speed boost), while system remains EXT4 if F2FS is unsupported.

Either way yeah you're right and I understand you. I've already fixed my phone and EXT4 does the job nearly as good as F2FS in 2021. We can easily close this little parentesis and move on. You know the drill with my observations lmao.
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,035
2,914
ykkfive.blogspot.com
To be honest as far as I'm aware for ROMs like LineageOS, you can simply format the partition to F2FS and the ROM installer will simply write on that since Lineage does support F2FS. And either way there are different setups for F2FS. Like putting only data and cache as F2FS (which still grants the vast part of the speed boost), while system remains EXT4 if F2FS is unsupported.

Either way yeah you're right and I understand you. I've already fixed my phone and EXT4 does the job nearly as good as F2FS in 2021. We can easily close this little parentesis and move on. You know the drill with my observations lmao.

yeah you are right
and tbh that's why when i heard f2fs is rom dependent at first, i was so shocked. although i understood why later since the fstab has been moved from the initrd to /vendor
 
  • Like
Reactions: TechNoobForSale

Top Liked Posts

  • 1
    No. It’s the manager not being able to control the DVFS. The DVFS is doing as it pleases. If you disable it in sys/devices/platform/17500000.mali by removing read and write permissions from “dvfs “, “dvfs max lock” and “dvfs min lock” you will be able to use the frequencies you set up. (You have to use a root file explorer. A decent one). Unfortunately it’s a temporary solution, as it resets every reboot.

    I assume DVFS is also the thing dropping frequencies for no reason on the CPU. If it’s not a timer nor temperature related
    Confirmed

    Disabling DVFS by revoking all read and write access making GPU run at any freq we set in hKTweak (even 572Mhz all the way long). Plus we need to disable game booster, game optimizer and friends. Those thing make instant re enable DVFS by itself (not even until reboot).
    1
    i will go back to the sources
    so in the mean time, pls discuss and share any thoughts, findings and results

    but also please note that, since the introduction of cpu/gpu oc things in the past was a failure which degraded the overall performance, i decided to drop those tweaks and started over again, which was reflected in v2.10 i believe. so chances that some of the controls, not limiting to cpu/gpu oc, may not work properly, were partially done or have been rolled back to stock basis

    please be patient and hope that they can be solved later

    thanks
  • 1
    i'm finally back..haha..life has been kicking my ass...glad to see others picking up and chiming in.

    As with regards to the gpu, this thing _SHOULD_ in theory be able to get into the 800+ mhz range as arm was touting 850 mhz on an older process for this gpu design. YKK knows my thoughts on what needs to be done to fully utilize it. There's _DEFINITELY_ a stupid amount of performance left on the table.


    The main thing that still bugs me is how none of the kernels seem to behave the consistently across multiple kernel managers. I got a partial compile, last time I spoke to ykk. I'll eventually figure out how to get a compile so I can contribute more technical stuff.
    1
    Can I ask if this kernel can be used for N960N, thanks
    one user has repoted it works with n960n before, you can search this thread for his reply
    and, from what i can see, there were many downloads came from korea too but honesty i cant guarantee because i don own a n960n. sorry about that
    1
    i'm finally back..haha..life has been kicking my ass...glad to see others picking up and chiming in.

    As with regards to the gpu, this thing _SHOULD_ in theory be able to get into the 800+ mhz range as arm was touting 850 mhz on an older process for this gpu design. YKK knows my thoughts on what needs to be done to fully utilize it. There's _DEFINITELY_ a stupid amount of performance left on the table.


    The main thing that still bugs me is how none of the kernels seem to behave the consistently across multiple kernel managers. I got a partial compile, last time I spoke to ykk. I'll eventually figure out how to get a compile so I can contribute more technical stuff.

    welcome home, no 7 cristiano ronaldo!

    oh, sorry... haha

    yeah that's great and i knew you dont want ppl to give you a hand and throw everything to you unless you have to, coz you will try it youself and look for a solution first. am i correct? (say yes pls or it will be embarrassing...)

    tbh it will be a boost since my note9's screen turned greenish before and i really scared to perform any risky experiment on my note9...
    1
    lol...ykk.. you are indeed correct.

    technoob...which kernel was this? and did they actually put in correct voltages for those speeds? if they just said eff it and did max voltage then you'd definitely run into temp issues. it would be crazy if they did it with the joke of a stock voltage table. overclocks won't help this cpu much at all. the problem with this chip is that it runs hot and _NEEDS_ to be fed. The biggest gains are going to come from the ram tbh. With that wide a core...on top offeeing agpu...thatyou need more memory performance.
    Alright so. The Kernel that reached such crazy clock speeds for the GPU was the Zeus Kernel (Private Edition). However it only runs on the Oreo OS and the overclock are way too pushed and not all devices could handle it, causing phone reboots, which confused people.
    Also, you are mistaken. And I need to specify some things.
    Firstly, Exynos 9810 has been underclocked by Samsung, which means that by rising frequencies, we are just getting back what they took away from the device we paid for. The M3 cores are indeed very, very power hungry. But you have to expect a power requirement and heat output increase when doing intensive tasks anyways, on any device. The 9810 was meant to run at 2.9GHz in single core, 2.5GHz in dual core and 2.314GHz in tri and quad core. It has been underclocked to 2.7, 2,3 and 1.8 respectively. The small cores were meant to run at 1.9GHz. They got underclocked to 1.8 too.

    According to my expectations and estimations, the Exynos 9810 would be able to match the 9820, clearly while consuming much more power, but not as much as you would expect! To my eyes, the 9810 was an amazing processor. Mistreated by Samsung so badly. The potential is off the charts. RAM can only yield an improvement if overclocked. This device already has plenty of it.
    1
    The m3 core is effectively 6 instructions wide. Yes it has 12 pipelines, but it can only feed 6 per cycle. At that rate, your memory bandwidth requirements just to feed a single m3 core fully is 4bytes per instruction x 6 pipelines x 1800 mhz = 43 GB of bandwidth. Additional clock speed is useless if you can not get data into the cpu. It can't process data that it can't access. This is on top of fighting with the gpu for bandwidth.

    There's a lot more to actual performance vs benchmark performance. Benchmarks can easily be swayed by using different data sets.
    Doesn't matter. It was meant to run at a certain clockspeeds, and I've seen the analysis of the very respectable Andrei Frumusanu. Pushing the M3 cores to 2.3GHz in Quad Core mode yielded incredible performance increases. And funnily enough, that is the highest frequency before diminishing performance returns happen. In line with the clockspeed. Pair that with a RAM overclock, and this system will become a beast. The M3 cores had such a wide architecture it actually bested the stock Cortex A76. I don't test phones only with benchmarks, and I don't do "Real world" tests or "speed tests" either since they are extremely unreliable. I use the best and most objective benchmarks at hand (Geekbench 5, 3DMark, GFXBench and PCMark) and games the likes of Genshin Impact, Honkai Impact, Call of Duty Mobile, Battle Prime and Asphalt 9 just to mention some. Games are the perfect example of CPU and GPU having to work together, and this phone right now doesn't perform too hot in them due to the stupidly low thermal throttling point (70°C). Now I am not an architecture rat that knows every single detail of the transistors in the processor. But I do know that there is much more to this processor than Samsung unveiled. And rising clockspeed is one of the many steps to getting the true potential of this processor. Then comes what you mentioned. It's all of this together. It's not one or the other. This is how held back this processor was. And it's about time we wake it up.
  • 11
    Hi all,

    It's ME again, being inactive for a few years due to my health conditions since Android Marshmallow! Today I would like to present you something I wanted for so long... an updated kernel for One UI 2.5! To be honest, I knew there were a lot of changes since MM, but not until these days I realized how troublesome they are, including rooting a device these days!! ( just rooted my N960F/DS running stock pie for more than a year ;) )
    OK, here we go!!


    This is an update to the BeastMode Kernel vR154 originally developed by @freeza and patched with latest Samsung One UI 2.5 kernel sources.

    Some of the features from R154 include:
    - enforcing kernel (switchable between enforcing/permissive)
    - cpu/gpu oc
    - dt2w (double tap to wake)
    - wireguard support


    However, due to my health conditions, I cannot spend too much time to update this kernel everyday although I am jobless, nor to have frequent updates as what @freeza did to his BeastMode Kernel. So please don't expect things will come very often. Thank you



    Special notes for BeastMode Kernel v2 initial release:
    - in the initial release (v2.02) there is no fix nor new feature added to the BeastMode Kernel vR154, as it servers as an update for new One UI 2.5 ROMs released by Samsung only
    - for existing features, problems or solutions, please visit the original BeastMode Kernel thread by @freeza
    - new features will be added in later releases



    BeastMode Kernel v2:
    - built with EVA GCC 12 and Proton Clang 13.0.0
    - for cts profile/safetynet fix, please install the Universal SafetyNet Fix by @kdrag0n



    Planned features:
    - more IO schedulers
    - more governors
    - OC/UV
    - f2fs (DONE!)



    If you like this, please consider donating a loaf of bread or something to support my living or buy some treats for my old dog @ https://paypal.me/ykkfive ( I don't need coffee or beer :giggle: ). Thanks!



    Important Notes:
    if you are using a kernel manger, please go to here and see if you are affected



    Downloads:
    Changelog and downloads in post #2



    Credits:
    Big thanks to @freeza for allowing me to use his work and publish this update
    Samsung open source
    @evdenis
    @yarpiin
    @Da-BOSS
    @flar2



    Source code:
    github
    5
    NOTE: I am not responsible for bricked devices, loss of data, etc. Flash it with your OWN RISKS and ALWAYS DO A FULL BACKUP first



    Changelog and Download (NO mirror please):
    *** TWRP 3.3.1.0 is recommended


    20210920 - v2.12
    - for FUF5/FUH1 (NOTE: 2 different versions)
    - updated to latest samsung FUH1 sources
    - fixes for slow ext4 performance due to bugs introduced by ext4 and kernel updates
    - IMPORTANT: please set the io scheduler to noop as to increase the ext4 performance


    Downloads (mediafire) *make sure you get the right version for your rom (you can check your rom version by tapping on the dialer, and type *#1234# and read the AP shown):
    FUF5
    BM-Kernel-v2.12-FUF5-magisk_patched.zip (patched with Magisk 23.0)
    boot.img (no root)

    FUH1
    BM-Kernel-v2.12-FUH1-magisk_patched.zip (patched with Magisk 23.0)
    boot.img (no root)








    20210920 - v2.11c6
    - for FUF5/FUH1 (NOTE: 2 different versions)
    - updated to latest ext4 and f2fs
    - full f2fs support (cache and data partitions tested, system not yet tested) ** MAKE SURE you know how to go f2fs first
    - linux upstream to 4.9.280
    - some other tweaks and patches


    Downloads (mediafire) *make sure you get the right version for your rom (you can check your rom version by tapping on the dialer, and type *#1234# and read the AP shown):
    FUF5
    BM-Kernel-v2.11c6-FUF5-magisk_patched.zip (patched with Magisk 23.0)
    boot.img (no root)

    FUH1
    BM-Kernel-v2.11c6-FUH1-magisk_patched.zip (patched with Magisk 23.0)
    boot.img (no root)







    20210818 - v2.10
    - revised from the beginning with updates to FUF5
    - cpu oc/uv
    - gpu overclock/under voltage removed (awaiting fixes)
    - some changes reverted
    - Wake Gestures and Boeffla wakelocks included
    - bring back the performance from initial release (up to 23% or more with multi cores, and nearly 3x memory performance when compared with v2.04) ** thanks for reporting this issue



    Downloads (mediafire):
    BM-Kernel-v2.10-magisk_patched.zip (patched with Magisk 23.0)
    boot.img (no root)





    Previous releases:



    Known Issues:

    20210730:

    (I) for version up to v2.05, the following features do not work as expected due to my mistakes

    - Wake Gestures including double tap to wake (dt2w), swipe to wake (s2w), etc
    - Boeffla wakelocks
    - These problems will be fixed in the next version soon
    .
    FIXED. Please accept my sincere apology

    (II) in v2.05 default gpu voltage may incorrectly show the modified values as default values in kernel manager

    (III) since v2.04m the performance is not as good as v2.03 due to the introduction of some kernel changes





    20210730 - v2.05a
    - Wake Gestures and Boeffla wakelocks problems fixed
    - no other changes, bugs fixing release of v2.05







    20210729 - v2.05
    - updated with Samsung FUF5 sources just released
    - no other changes
    - REMOVED, superseded by v2.05a







    20210726 - v2.04m
    - compatible with FUF5 (** may have problems if you use lockscreen or samsung account with possible fix here. ALWAYS do a full backup first)
    - overclocked: cpu little to 2002000Mhz, gpu to 598000Mhz
    - undervoltaged: cpu/memory
    - gpu undervoltage support awaiting a fix
    - linux upstreamed to 4.9.250
    - cherry picked some kernel tweaks
    - for undervolting the gpu, you may go and read my settings here awaiting a fix






    More Previous releases:


    20210628 - v2.03
    - added "magisk detected" BASIC fix to prevent apps trying to detect if magisk is installed (only some of the detections are prevented)
    - you can see the difference by installing an app from google play store called "Дія" issued by Ministry of Digital Transformation of Ukraine

    before applying fix
    after fix applied


    - for more info, please read:
    https://darvincitech.wordpress.com/2019/11/04/detecting-magisk-hide/
    - for a comprehensive solution (NOT TO BE SUPPORTED/DISCUSSED HERE):
    https://forum.xda-developers.com/t/magisk-detected-on-bankapp-solved.4258245/
    IMHO, if there's nothing bothering you, you can ignore this comprehensive solution atm. but of coz it's up to you









    20210621 - v2.02 (init release)
    *** Special announcement for Dr.Ketan ROM Q16 - 20210623 ***
    it seems there are some compatibility issues with Dr.Ketan ROM Q16 and this kernel, due to the fact that Q16 is based on N960FXXU8FUE1 while this kernel is N960FXXS8FUE5. As a result you may not be able to login to Samsung Account, or have cts profile/safetynet issue. So please MAKE A FULL BACKUP before proceed.


    - updated with N960FXXS8FUE5 sources
    - tested with stock rom UE5, Dr Ketan Q16 with some patches
    - working properly with DevBase 7.4 and Alexis ROM 2.8 from users feedbacks
    *** make sure you have flashed N960FXXS8FUE5 AP, BL, modem etc



    .
    3
    20210920 - v2.11c6 released
    for fuf5 and fuh1 respectively
    3
    Now I migrated bm v2.02m + Alexis 2.8 combination. All seems decent for now. Still boeffla and double tap sections are missing. But it's okay.
    Here is the devchecks ram performance attachment. (on v2.02)

    I am going to perform antutu and geekbench and post here.
    u mean 2.04m?

    I am on v2.05

    Ram performance is decreased, confirmed with doing devcheck comparison and antutu bench.

    tap to wake and sleep options are gone.
    boeffla options are gone.

    Accordig to Devcheck,

    Cmemcopy: around 5000 Mb/s
    Cmemset: aroud 7500 Mb/s

    on R154 these were 10000 MB/s and 15000 Mb/s respectively.

    Cpu an GPU performance are good.

    I am on Alexis 2.9 Note 9 SM N960F


    And also the voltage table that given by dev is passed two full antutu bench. No crashes.
    i have did some tests today and yes, 2.02 is the fastest one, it was the original one without any "enhancements" in other aspects like cpu/gpu overclocking. it is not unusual that these enchancements can be beaten by the one without in terms of performance. it all depends on the usage, and more importantly everthing comes with a price. so you may find it at stock max speed outperforms an overclocked cpu due to the heat generated (which trigger the mechanism to lower the cpu freq as to cool it down). eg a 10 seconds task running with 2000Mhz may be better than 3 seconds with 2400mHz plus 7 seconds with 1700Mhz. you see what i mean? of coz, once again, it depends on the usage and the way of using it like benchmarking or daily use

    anyway, thanks for your feedbacks, as well as others. without you guys' feedback i couldnt discover the bugs myself

    also, i may consider to make an extreme version, which will be rebased on 2.02 with FUF5 but without any unneccessary changes for those who focus more on the speed due to different usage patterns if there are demands for it. but in general, 2.02 is still working fine with FUF5 except samsung account login issues for some users i believe

    on the other hand, i will continue to cherry pick some useful changes to optimize it in general for the main stream version

    thanks
    3
    EDIT 20210804
    a more aggressive gpu voltage settings is posted here awaiting a fix



    BM-Kernel-v2.04m released

    20210726 - v2.04m
    - compatible with FUF5 (** may have problems if you use lockscreen or samsung account with possible fix here. ALWAYS do a full backup first)
    - overclocked: cpu little to 2002000Mhz, gpu to 598000Mhz
    - undervoltaged: cpu/memory
    - support gpu under voltage
    - linux upstreamed to 4.9.250
    - cherry picked some kernel tweaks
    - for undervolting the gpu, you may refer to my initial safe settings below and adjust them by yourself. there are still rooms to undervolt, but it is suggested you do it bit by bit, and one by one and test the new voltage before next