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

[Kernel | Android 10 | One UI 2.5 | FUF5/FUH1/FUJ2] BeastMode Kernel v2 for N960F | v2.15a | 20211207

Search This thread
So maybe if we could undervolt CPU by 5-10% and run Cortex A75 at 2886MHz more frequently. Than i think Note9 CPU could win the 10% slower than 9820 in AnTuTu V9.

Also,
Undervolt GPU by 10-15% and run 572MHz more frequently. Then i think Note9 GPU could have same score with the 9820 in AnTuTu V9. Which only less by 26%.
Also if you found a way to disable the CPU DVFS, or at least increase that horrid 70°C throttling point, we are going to get around 8% extra CPU performance.
 
After tweaking here and there, I have done these after all:
Disable app: device care, game optimizer, game launcher, game plugin, and at last
DVFS. I done it by these steps below

Step 1: Download ES File Explorer from the Google Play store. It is a free download.Step 2: Slide out the left drawer, under tools turn on Root Explorer.Step 3: Now head on to the System partition, then the sys folder. The exact location you want to end up in: sys > devices > 17500000.maliStep 4: Find the file dvfs and then long press it. You want to now open up the permissions dialog by going to: More > Properties > PermissionsStep 5: Now uncheck all of the permissions on the permissions dialog so no box is ticked.Step 6: Now do the same for two other files in the same folder dvfs_min_lock and dvfs_max_lock. Unchecking all of the permission boxes.

And for the result: Truck Simulator Ultimate significantly has lower frame drop
Trying to remove the permissions to the DVFS files doesn't work. They turn themselves back on


Nvm it applied. I wonder if this is reset every reboot though.

So it seems that the DVFS was at the fault for the Minimum and maximum GPU frequency doing whatever it wanted. With it disabled, the GPU sticks at 572MHz at all times if I put the minimum at such a number. However after reboot, said changes revert back to normal.
 
Last edited:
Results of the tests with the GPU DVFS disabled:
Ambient Temp: 22°C
Chassis Temp: 15°C (26°C under load, 30°C hotspot)
Tools: Xiaomi FunCooler Pro

3DMark:
IceStorm Unlimited: *50,378* (50,000 barrier broken. 17% faster than the average Note9)
GPU test 1: 317,1fps (Peaks registered at 323+fps)
GPU test 2: 221,9fps
CPU test: 102,2fps (Peaks registered at 106+fps)

SlingShot Extreme Unlimited (OpenGL ES 3.1): 4,390 (17% faster than the average Note9)
GPU test 1: 34,2fps
GPU test 2: 15,2fps
CPU test:
Part 1: 57,9fps
Part 2: 35,3fps
Part 3: 18,6fps

Wildlife Unlimited: 2,364 (Average, expected)
GPU test: 14,2fps

PCMark, Work 3.0 Performance: 9,386 (Almost 52% faster than the average Note9, faster than a 9820)
Web Browsing 3D Score: 6,916
Video Editing 3.0 Score: 6,612
Writing 3.0 Score: 10,583
Photo Editing 3.0 Score: 22,796
Data Manipulation 3.0 Score: 6,605

I avoided GFX Benchmark as it is very GPU specific, and like highlighted by 3DMark Wildlife, there would be 0 improvement since the Max Frequency is the stock one.

Geekbench 5:
Single: 689 (Average. In the past I managed on stock ROM a score above 720. It's all about that 2886MHz being used more often)
Multi: 2,074 (Average, sometimes I do 2,100+, LITTLE CPU throttled to 1950MHz :mad:)
Compute: 4,759 (Useless score to me, but it's here anyways)

AnTuTu V9: 444,001 (21% faster than the average Note9)
CPU: 129,255 (21% faster than the average Note9, Little CPU throttled to 1950MHz :mad: )
GPU: 132,410 (10% faster than the average Note9, however SD845 defeats this by 24%)
MEM: 81,955 (33% faster than the average Note9)
UX: 100,381 (27% faster than the average Note9)


We have got room for improvement. Especially that 70°C throttling threshold.
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,100
2,940
ykkfive.blogspot.com
Results of the tests with the GPU DVFS disabled:
Ambient Temp: 22°C
Chassis Temp: 15°C (26°C under load, 30°C hotspot)
Tools: Xiaomi FunCooler Pro

3DMark:
IceStorm Unlimited: *50,378* (50,000 barrier broken. 17% faster than the average Note9)
GPU test 1: 317,1fps (Peaks registered at 323+fps)
GPU test 2: 221,9fps
CPU test: 102,2fps (Peaks registered at 106+fps)

SlingShot Extreme Unlimited (OpenGL ES 3.1): 4,390 (17% faster than the average Note9)
GPU test 1: 34,2fps
GPU test 2: 15,2fps
CPU test:
Part 1: 57,9fps
Part 2: 35,3fps
Part 3: 18,6fps

Wildlife Unlimited: 2,364 (Average, expected)
GPU test: 14,2fps

PCMark, Work 3.0 Performance: 9,386 (Almost 52% faster than the average Note9, faster than a 9820)
Web Browsing 3D Score: 6,916
Video Editing 3.0 Score: 6,612
Writing 3.0 Score: 10,583
Photo Editing 3.0 Score: 22,796
Data Manipulation 3.0 Score: 6,605

I avoided GFX Benchmark as it is very GPU specific, and like highlighted by 3DMark Wildlife, there would be 0 improvement since the Max Frequency is the stock one.

Geekbench 5:
Single: 689 (Average. In the past I managed on stock ROM a score above 720. It's all about that 2886MHz being used more often)
Multi: 2,074 (Average, sometimes I do 2,100+, LITTLE CPU throttled to 1950MHz :mad:)
Compute: 4,759 (Useless score to me, but it's here anyways)

AnTuTu V9: 444,001 (21% faster than the average Note9)
CPU: 129,255 (21% faster than the average Note9, Little CPU throttled to 1950MHz :mad: )
GPU: 132,410 (10% faster than the average Note9, however SD845 defeats this by 24%)
MEM: 81,955 (33% faster than the average Note9)
UX: 100,381 (27% faster than the average Note9)


We have got room for improvement. Especially that 70°C throttling threshold.
so it works, rite?
you can add the changes to an init script as it will roll back after reboot

btw i just installed a new build, better kill me, my screen turned into something like an old tv with full screen of snowflakes... i am afraid it's about to die....
 
so it works, rite?
you can add the changes to an init script as it will roll back after reboot

btw i just installed a new build, better kill me, my screen turned into something like an old tv with full screen of snowflakes... i am afraid it's about to die....
Then why not install the old one and check if it gives you the same issue?
Also no idea how to do an init script. Either way not much of an issue for me, because I guess you already realized that the DVFS is as good as gone.

Also it did work, but in games (and for 2 minutes, since the phone goes 70°C pretty fast and throttles, and I get a little pissed). For benchmarks? Not so much, because they already make the GPU boost very high to begin with.
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,100
2,940
ykkfive.blogspot.com
Then why not install the old one and check if it gives you the same issue?
Also no idea how to do an init script. Either way not much of an issue for me, because I guess you already realized that the DVFS is as good as gone.

Also it did work, but in games (and for 2 minutes, since the phone goes 70°C pretty fast and throttles, and I get a little pissed). For benchmarks? Not so much, because they already make the GPU boost very high to begin with.

yeah of coz i did, i installed an old build and it's fine now
it made me more certain that i have loss in the lottery, very likely hardware problems
for first it turned green in recovery when idle months ago, then now with the snowflakes. but even though it's a bad contact with the cable of the screen, i couldn't fix it by myself
 
yeah of coz i did, i installed an old build and it's fine now
it made me more certain that i have loss in the lottery, very likely hardware problems
for first it turned green in recovery when idle months ago, then now with the snowflakes. but even though it's a bad contact with the cable of the screen, i couldn't fix it by myself
Usually the lottery thing only applies to the processors. The behaviour of your screen is really weird. I guess that you should make the overclock options something that can be configured by the user in OS so that we can test it for you if your phone has failed the lottery

What did you change exactly in the new build that could've caused this problem anyways?
 

trevinutomo

Member
Oct 13, 2016
28
4
yeah of coz i did, i installed an old build and it's fine now
it made me more certain that i have loss in the lottery, very likely hardware problems
for first it turned green in recovery when idle months ago, then now with the snowflakes. but even though it's a bad contact with the cable of the screen, i couldn't fix it by myself
Is it possible that ur screen's flex cable damaged? If that so, then after swap it with new one surely solve those green screen and snoflakes
 

trevinutomo

Member
Oct 13, 2016
28
4
Terribly sorry, doesn't mean to be rude, ykkfive. I found that A2N kernel for S8 could have DVFS settings that allow max throttle threshold to be set depending CPU Freq we want to be. Is it possible to make it happen in Exynos 9810?
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,100
2,940
ykkfive.blogspot.com
Usually the lottery thing only applies to the processors. The behaviour of your screen is really weird. I guess that you should make the overclock options something that can be configured by the user in OS so that we can test it for you if your phone has failed the lottery

What did you change exactly in the new build that could've caused this problem anyways?

yeah your are right, but that happen in other hardware too

i did nothing unusual actually but upstream the linux kernel

yes, for me, the performance now is very good already, provided that i dont play games and i use it for an hour or two per day, so it's just for you guys
 
Last edited:

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,100
2,940
ykkfive.blogspot.com
Terribly sorry, doesn't mean to be rude, ykkfive. I found that A2N kernel for S8 could have DVFS settings that allow max throttle threshold to be set depending CPU Freq we want to be. Is it possible to make it happen in Exynos 9810?

no problem mate, as i always said, i need inputs
however not all can be ported due to different linux version etc
anyway i will take a look at that later. thanks
 
Last edited:
True. I actually wonder how did I forget to tell you. The A2N Kernel allows a level of customization never seen before since the developer also created his own software for it. He charges a buck or so for it, but I’d pay (and I did pay) gladly for this stuff lmao. Most notable features are how he allows people to adjust throttling temperature on CPU and GPU and, if desired, disable GPU DVFS. He pushed the Exynos 8895 so far it can rival and defeat a Snapdragon 835. Perhaps you could either study his Kernel or ask him for tips, he seems like a nice lad from my impression.
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,100
2,940
ykkfive.blogspot.com
True. I actually wonder how did I forget to tell you. The A2N Kernel allows a level of customization never seen before since the developer also created his own software for it. He charges a buck or so for it, but I’d pay (and I did pay) gladly for this stuff lmao. Most notable features are how he allows people to adjust throttling temperature on CPU and GPU and, if desired, disable GPU DVFS. He pushed the Exynos 8895 so far it can rival and defeat a Snapdragon 835. Perhaps you could either study his Kernel or ask him for tips, he seems like a nice lad from my impression.

ok i remember that kernel now, it's on the cards but i don have time to review it yet (i have bookmarked too many 😅 )
 
  • Like
Reactions: TechNoobForSale

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,100
2,940
ykkfive.blogspot.com
Then why not install the old one and check if it gives you the same issue?
Also no idea how to do an init script. Either way not much of an issue for me, because I guess you already realized that the DVFS is as good as gone.

Also it did work, but in games (and for 2 minutes, since the phone goes 70°C pretty fast and throttles, and I get a little pissed). For benchmarks? Not so much, because they already make the GPU boost very high to begin with.

oh btw, you guys mentioned 70C throttling point, where did you find it, i mean the 70C?
 
oh btw, you guys mentioned 70C throttling point, where did you find it, i mean the 70C?
Observation. As I executed benchmarks, I noticed that the LITTLE CPUs are forced to 1950Mhz as soon as 71C CPU temperature is reached (can’t set 20002 anymore without reboot) big cores drop too but it’s not forced anymore as soon as I go under 71. Zeus Kernel apparently is aware of this and has an experimental fix for the little cores forcing themselves at 1950
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,100
2,940
ykkfive.blogspot.com
Observation. As I executed benchmarks, I noticed that the LITTLE CPUs are forced to 1950Mhz as soon as 71C CPU temperature is reached (can’t set 20002 anymore without reboot) big cores drop too but it’s not forced anymore as soon as I go under 71. Zeus Kernel apparently is aware of this and has an experimental fix for the little cores forcing themselves at 1950
alright, coz i couldnt find the 70C specified so i believe it could be arrived by some calculations or affected by other hardware

in fact i have applied most of the oc things before but when tested the performance dropped quite significantly. so i removed them before releasing those builds
 
alright, coz i couldnt find the 70C specified so i believe it could be arrived by some calculations or affected by other hardware

in fact i have applied most of the oc things before but when tested the performance dropped quite significantly. so i removed them before releasing those builds
You can simply verify it yourself bro. OC the little cores to 2002, run Geekbench 5 or antutu v9, then go to hktweaks and you’ll see the little cores max frequency is forced at 1950. No calculations or anything. I ran the benchmarks, got done with it, noticed CPU little dropped to 1950 as soon as 70C was passed. It’s clearly a threshold. It has to be stored in some file somewhere. The performance dropped because with the oc things, you most likely hit the 70C so fast, so hard that your cpu most likely dropped the frequency very hard to cool down. That’s how throttling works.

again, you can check the Zeus kernel details to see that there is a “possible fix for 2002mhz” or something like that. I’ve seen some guy in this thread saying that it’s the cache frequency’s fault @ykkfive

if there is a file with that temp threshold, I’ll find it.
 
Last edited:

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,100
2,940
ykkfive.blogspot.com
You can simply verify it yourself bro. OC the little cores to 2002, run Geekbench 5 or antutu v9, then go to hktweaks and you’ll see the little cores max frequency is forced at 1950. No calculations or anything. I ran the benchmarks, got done with it, noticed CPU little dropped to 1950 as soon as 70C was passed. It’s clearly a threshold. It has to be stored in some file somewhere. The performance dropped because with the oc things, you most likely hit the 70C so fast, so hard that your cpu most likely dropped the frequency very hard to cool down. That’s how throttling works.

again, you can check the Zeus kernel details to see that there is a “possible fix for 2002mhz” or something like that. I’ve seen some guy in this thread saying that it’s the cache frequency’s fault

i mean the "70C" doesnt exist in the sources, so it could be affected by say an increase in gpu temperature etc and thus triggered it . from the sources i found the 1st warning temperature is 85 if i remember it correctly. so chances that there were something else triggered, or as a result of something which prevent the cpu to arrive at the first warning temperature, cant tell at this point

besides, i found that the relationship between the cpu and gpu are very closed, meaning that if you oc the cpu, the gpu will be affected as well. that's why you may find that i have removed the gpu oc but left the cpu oc there

anyway, these will be addressed next
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    record breaker!!
    max 128k, min 107k

    btw, builds updated with fuj2 sources coming soon, with some addressed the gpu driver
    Screenshot_20211130-205403.jpg
    2
    Can you suggest a best profile for battery saver? I'm using EX kernel manager but I don't know how to config a profile properly. Please give me advice. Thanks.
    i don use kernel manager, but i can share with you my settings

    my aim is to make it as efficient as possible
    so,
    for the big cores, i set max=max, min=9xx
    while for the little cores max=the freq above the big cores' min freq, and min=min

    so that it will provide a smooth transition from the little to the big cores by letting the big core min freq covers part of the little cores max freq

    since the big cores are more efficient l let them do those heavy tasks by lowering the max freq of the little cores. ie if needed, go big pls, and i will further enhance this (big cores bias) in the future

    for the gpu,mi set it to min=266, boost to 3xx when the loading is above 30%. you can adjust these numbers according to your needs to avoid lagging while save some battery (note you can scroll the screen to see if it is smooth enough for you)

    usually it will consume about 8% battery for surfing the net for an hour

    hope it helps
    2
    I followed your advice and turned off everything. Hope you are ready for some weird results. The situation did not change, however I noticed that:

    - heavy throttle takes place when the cpu temp is below throttling point? (screenshot 1)
    - performance gain when the temp is 70 degrees (screenshot 2)

    Dr Ketan has just released a new update so I am curious to check the behavior of the stock kernel on his rom, after I will flash beast of course (edit: just noticed that new rom is on FUJ2 base so I might skip custom kernel flash until the next update).
    Which version to be installed on FUJ2, Nov security patch Dr ketan ROM?


    i have made one for fuj2, will upload it later
    daxx busy installing and reinstalling the phone due to a crash before. it made me sick!

    will try to answer other questions later

    sorry about that
    1
    sorry for my bad english. your kernel has already rgb option. just others (saturation contrast value and hue) not added. thanks by the way.
    no not your problem, my mother lanugage is not english either 😄
    i just dont know what we have right now except rgb so I asked what's missing (ps i dont use all the functions myself)
    1
    First thing that comes to mind is that temperature reading in third party apps (CPU Throttling test, CPUFloat) is still broken. Only Hktweaks can see it. Where is the temperature file? For both CPU and GPU. Maybe I can sort out something to address it

    due to changes in permissions, need root access to access them
  • 12
    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


    20211130 - v2.15a
    - patched with latest FUJ2 sources
    - some more tweaks
    - IMPORTANT: please set the io scheduler to noop (by default) 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.15a-FUF5-magisk_patched.zip (patched with Magisk 23.0)
    boot.img (no root)

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

    FUJ2
    BM-Kernel-v2.15a-FUJ2-magisk_patched.zip (patched with Magisk 23.0)
    boot.img (no root) - RE-UPLOADED









    20211121 - v2.14b2-FIXED
    - FIXED no sound ocasionally after reboot (tested for more than 10 reboots)
    - added PELT
    - undervolt including memory/bus, etc
    - gpu oc to 598 again
    - many other performance and battery saving tweaks, as well as other that I could not remember
    - swithed back to 250 HZ due to the no sound bug
    - 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.14b2-FIXED-FUF5-magisk_patched.zip (patched with Magisk 23.0)
    boot.img (no root)

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

    FUJ2
    BM-Kernel-v2.14b2-FIXED-FUJ2-magisk_patched.zip (patched with Magisk 23.0)
    boot.img (no root)









    Previous releases:


    20211120 - v2.14b2
    - REMOVED due to an old minor bug was re-introdecued which occasionally produce no sound after a reboot
    - pls download the v2.14b2-FIXED above







    20211024 - 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)







    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