• 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.14b2-FIXED | 20211121

Search This thread
you mean a phone reboot or just like a crash which restart from the boot animation? if the latter it should be rom related

yeah will take a look at that later. nevertheless it's 1950 vs 2002 only, and it wont last very long at that frequency, although i can understand your frustration
So it is not a crash because the phone does not do a full reboot (turns off and then shows Samsung Galaxy note 9 logo to then boot normally). It simply exits the operating system and goes back to the Samsung pulsing logo to then go in the operative system normally. App settings like HWtweaks ones are kept. It’s a fast reboot, on lineage OS it is literally an option.
 
Also it's obvious that 2002MHz on the little cores can't be sustained. The throttling happens as soon as the CPU temperature is >70°C. When stressed to 100% on both small and big cores, the CPU will reach 70°C within 10 seconds at a 24°C ambient temperature. Rising that throttling point at 90°C or 95°C if we want to go aggressive, would nearly eliminate throttling from the system running at 1794MHz on big cores and 2002MHz on small cores. That would yield performance improvements of around 9% CPU speaking (Big cores throttle at 1586MHz and small cores at 1950MHz at >70°C).

Also there is also the GPU problem. To give you an example

Me: Puts minimum GPU frequency at 572MHz
Also me: Opens a game
GPU: 260MHz
Me: :mad:

In fact the boost frequency doesn't seem to work. Even with the booster governor and with the boost frequency put at 15% usage, even when my GPU is over 50%, the frequency isn't the one the boost frequency one. It's always lower in games. I don't know why this happens but it hinders performance.
 

moderndaycowboy

Senior Member
Oct 4, 2015
200
34
Smyrne
Yeah they happen some times when I switch from Wi Fi to Mobile data while on plane mode. But that is not something that annoys me. What bugs me off is that as soon as the phone goes >70°C on CPU, small cores are FORCED to go at 1950MHz instead of the peak 2002MHz and I can't change it back to the peak frequency. You really have to rise the throttling frequency of the CPU once you are done working on system file improvements bro.
I had it too, try to change Selinux to permissive.
 

moderndaycowboy

Senior Member
Oct 4, 2015
200
34
Smyrne
I did so after your suggestion. Not sure what it should change though
we discussed your problem with one of s9 dev. He said "when selinux see there is root, it locks all the apps"
also I looked at the logs after the issue happened, logs say " system impiles root"
I think the issue is high possibly related with selinux state, if none works,

go back to Alexis 1.8 and BM R154 combination.
 
we discussed your problem with one of s9 dev. He said "when selinux see there is root, it locks all the apps"
also I looked at the logs after the issue happened, logs say " system impiles root"
I think the issue is high possibly related with selinux state, if none works,

go back to Alexis 1.8 and BM R154 combination.
we discussed your problem with one of s9 dev. He said "when selinux see there is root, it locks all the apps"
also I looked at the logs after the issue happened, logs say " system impiles root"
I think the issue is high possibly related with selinux state, if none works,

go back to Alexis 1.8 and BM R154 combination.
But are you referring to the frequency issue or the fast reboot one? If it is for the latter, I really don’t care all that much. I don’t know what locking all the apps means since everything worked just fine with enforcing. Now I am on permissive. This is my main phone, I can’t just change ROM every 2 weeks lol. If the problem remains, I’ll stick with it. It’s not a dealbreaker issue.

Right now I am on Alexis ROM 3.0 and I don’t think I’ll change. I don’t want to miss out on the improvements the dev will make to this kernel either. It’s too much to lose for too little to gain.
 

moderndaycowboy

Senior Member
Oct 4, 2015
200
34
Smyrne
But are you referring to the frequency issue or the fast reboot one? If it is for the latter, I really don’t care all that much. I don’t know what locking all the apps means since everything worked just fine with enforcing. Now I am on permissive. This is my main phone, I can’t just change ROM every 2 weeks lol. If the problem remains, I’ll stick with it. It’s not a dealbreaker issue.

Right now I am on Alexis ROM 3.0 and I don’t think I’ll change. I don’t want to miss out on the improvements the dev will make to this kernel either. It’s too much to lose for too little to gain.
Yeah I mean the latter one. The problem you have experienced recently can damage to your cpu, because it gets to near 85 degrees. Also it is like a random reboot that can damage the rom files etc
If I were you, I wouldnt take that risk.
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,091
2,934
ykkfive.blogspot.com
we discussed your problem with one of s9 dev. He said "when selinux see there is root, it locks all the apps"
also I looked at the logs after the issue happened, logs say " system impiles root"
I think the issue is high possibly related with selinux state, if none works,

go back to Alexis 1.8 and BM R154 combination.

can you explain in more details please? "when selinux see there is root, it locks all the apps". and how it affects the freq etc?

edit also i couldnt find any info about "system implies root". where did you find it? logcat?
 
Last edited:

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,091
2,934
ykkfive.blogspot.com
Also it's obvious that 2002MHz on the little cores can't be sustained. The throttling happens as soon as the CPU temperature is >70°C. When stressed to 100% on both small and big cores, the CPU will reach 70°C within 10 seconds at a 24°C ambient temperature. Rising that throttling point at 90°C or 95°C if we want to go aggressive, would nearly eliminate throttling from the system running at 1794MHz on big cores and 2002MHz on small cores. That would yield performance improvements of around 9% CPU speaking (Big cores throttle at 1586MHz and small cores at 1950MHz at >70°C).

Also there is also the GPU problem. To give you an example

Me: Puts minimum GPU frequency at 572MHz
Also me: Opens a game
GPU: 260MHz
Me: :mad:

In fact the boost frequency doesn't seem to work. Even with the booster governor and with the boost frequency put at 15% usage, even when my GPU is over 50%, the frequency isn't the one the boost frequency one. It's always lower in games. I don't know why this happens but it hinders performance.

if you meant the gpu boost param found in most kernel manager, that means, eg
if you set min 299, usage = 15%, boost = 572
that would mean:
gpu min freq is 299. when the usage is 15%, boost it to 572 if possible
that's all.

i am not sure if this rule will remain active once triggered, since it depends on other settings etc. but if if is set to sustainable, then in theory it wont go down no matter what the situation is except cooling points come into effect, and it sounds not reasonable. isnt it?
so in your case it looks like you want to set it as min=572

previously when interactive governor was used, i supplied with something like below
if 15% go to 300, if 30% go to 450, if 50% go to 600, if 70% go to max
 
Last edited:

moderndaycowboy

Senior Member
Oct 4, 2015
200
34
Smyrne
can you explain in more details please? "when selinux see there is root, it locks all the apps". and how it affects the freq etc?

edit also i couldnt find any info about "system implies root". where did you find it? logcat?
Yeah for once, I looked at logcat but it was deleted months ago.

Selinux realizes there is a security breach, and the breach is rooting the phone. After that Linux locks all the apps, no app is openable, and the phone heats wildly. I don't know why it is heating up.
I never see that issue after I put selinux to permissive. Also this heating up and locking thing never happens on ONE UI 2.1 roms such as Alexis 1.8, the problem only occurs on one UI 2.5 roms
 
if you meant the gpu boost param found in most kernel manager, that means, eg
if you set min 299, usage = 15%, boost = 572
that would mean:
gpu min freq is 299. when the usage is 15%, boost it to 572 if possible
that's all.

i am not sure if this rule will remain active once triggered, since it depends on other settings etc. but if if is set to sustainable, then in theory it wont go down no matter what the situation is except cooling points come into effect, and it sounds not reasonable. isnt it?
so in your case it looks like you want to set it as min=572

previously when interactive governor was used, i supplied with something like below
if 15% go to 300, if 30% go to 450, if 50% go to 600, if 70% go to max
Yeah that is correct. But I use the booster governor instead and the scaling just doesn't work bro. If I put at 15% load, use 572MHz, it just won't. It vibes at 260MHz at low usages. It doesn't go to 546-572 until usage is above 90%. Interactive Governor also seems to perform better than Booster, which is why I use it. But it still behaves super bad in games.

So yeah, what's reasonable for me is to set the minimum to 572MHz


too bad it doesn't work. Literally. It doesn't. It just goes back to 260MHz as soon as I get into a game. It totally ignores the rules and changes the value back to 260MHz on its own. It's a little bit annoying if you ask me. Actually it is very annoying lol. The cooling point also, is set at 71°C. It's very low, needs to be rised.
 
Last edited:
Yeah I mean the latter one. The problem you have experienced recently can damage to your cpu, because it gets to near 85 degrees. Also it is like a random reboot that can damage the rom files etc
If I were you, I wouldnt take that risk.
I've seen in HkTweaks that my ROM has security features for file integrity enabled. So far I haven't had file loss either way. I am on permissive now though. Also 85°C is a high temperature for a mobile CPU but not a dangerous one. Dangerous is >95°C. Which is why I'd really appreciate having the throttling point of this kernel rised. It would yield great performance improvements and the phone wouldn't suffer any damage. Besides, those fast reboots didn't cause any high temperature issue in my phone.
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,091
2,934
ykkfive.blogspot.com
Yeah for once, I looked at logcat but it was deleted months ago.

Selinux realizes there is a security breach, and the breach is rooting the phone. After that Linux locks all the apps, no app is openable, and the phone heats wildly. I don't know why it is heating up.
I never see that issue after I put selinux to permissive. Also this heating up and locking thing never happens on ONE UI 2.1 roms such as Alexis 1.8, the problem only occurs on one UI 2.5 roms
sounds like a bug though, it shouldnt block all apps in the first place
 

moderndaycowboy

Senior Member
Oct 4, 2015
200
34
Smyrne
sounds like a bug though, it shouldnt block all apps in the first place
Yeah that is not clear still, idk what to say.

Now I am using Alexis 2.9 and BM v2.10 and I'd say, this is the best combination so far.
I set kernel to permissive and I never face any random freeze and afterward reboot.

Ps: was using Alexis 1.8 and Bm R154. This is the 2nd best combination I think.
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,091
2,934
ykkfive.blogspot.com
Yeah that is correct. But I use the booster governor instead and the scaling just doesn't work bro. If I put at 15% load, use 572MHz, it just won't. It vibes at 260MHz at low usages. It doesn't go to 546-572 until usage is above 90%. Interactive Governor also seems to perform better than Booster, which is why I use it. But it still behaves super bad in games.

So yeah, what's reasonable for me is to set the minimum to 572MHz


too bad it doesn't work. Literally. It doesn't. It just goes back to 260MHz as soon as I get into a game. It totally ignores the rules and changes the value back to 260MHz on its own. It's a little bit annoying if you ask me. Actually it is very annoying lol. The cooling point also, is set at 71°C. It's very low, needs to be rised.

never tried booster before. just played for a short while under normal usage (scrolling) but didnt notice anything
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,091
2,934
ykkfive.blogspot.com
Yeah that is not clear still, idk what to say.

Now I am using Alexis 2.9 and BM v2.10 and I'd say, this is the best combination so far.
I set kernel to permissive and I never face any random freeze and afterward reboot.

Ps: was using Alexis 1.8 and Bm R154. This is the 2nd best combination I think.
i set to enforce all the time, no problem so far
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
3,091
2,934
ykkfive.blogspot.com
I've seen in HkTweaks that my ROM has security features for file integrity enabled. So far I haven't had file loss either way. I am on permissive now though. Also 85°C is a high temperature for a mobile CPU but not a dangerous one. Dangerous is >95°C. Which is why I'd really appreciate having the throttling point of this kernel rised. It would yield great performance improvements and the phone wouldn't suffer any damage. Besides, those fast reboots didn't cause any high temperature issue in my phone.

may be i will make one for you to test later
 
may be i will make one for you to test later
I would really appreciate it if you can. The benchmarks results for the current version of the Kernels you know already, since I do them frequently to study the performance differences between each release. I'll tell you how much the higher throttling point will benefit performance. Also to be honest it shouldn't even be that hard. At least as far as Snapdragon is concerned. Because on Snapdragon devices there is a simple file regulating the way throttling works. It's called Thermal Engine or something, and it can literally be edited while you are in OS. I don't know if Samsung made things more complicated for Exynos though. It should still be a bunch of variables though.

It should yield around 8% CPU performance improvements on sustained loads. And again, it would open the pathway to future CPU overclocks that bring the CPU in multi core at >1794MHz. Optimally at 2314MHz in Quad Core and Tri Core mode and 2652MHz for dual core which are the originally intended frequencies for this SoC. More optimizations to keep the M3 cores fed as well would allow us, with all of that, to match and beat Snapdragon 855 in CPU performance according to my expectations. And I am not kidding.
 
Last edited:

trevinutomo

Member
Oct 13, 2016
28
4
The problem here is.. either the maximum thermal in One Ui is too low or the game optimization app limitation that makes any kernel couldn't reach more than 2,9Ghz CPU Clock and 572Mhz GPU Clock.
 
  • Like
Reactions: TechNoobForSale

Top Liked Posts

  • 1
    For a long time, I don't visit your thread :) . I'm looking forward to test new kernel FUJ2 from you.

    Remember to take care of your health.

    just uploaded

    yeah i will, thanks mate
    1
    Yes, what I meant was that even for the battery these are pretty low readings. I think that the kernel performance is heavily affected by the ROM that is used and maybe I will switch to Alexis ROM for a more debloated environment (Using Ketan at the moment).

    What makes me a big impression is the smoothness of the UI when the phone is charging and when it is on battery. When I have the phone on the charger, everything seems to work much faster. While on battery, speed is always reduced (of course I am not on battery saving mode or something like this). This goes for both stock and custom kernels that I have tried, but maybe it is just me or Samsung has really messed up with the idle / max timings on this chip.

    And it may sound weird, but after using your settings on 2.14b fixed, I only got 333000. Tested 2.10 with default settings and got 383.000. Maybe my phone is crazy :p

    it should be faster on odexed rom since pie, noticably faster , expecially if you further optimize the apks with the app provided by samsung (ahh... i have forgotten the name of that app), or by command line. the launching time of the app is reduced greatly imo
    1
    YKKFIVE WILDIN LMAO










    But I’m into it 🤠

    Yet, there is still stuff to do before 2964 can actually make sense.

    For example more tuning so that the single and dual core frequencies are used more. Because as of now I see the processor still boosting to the mid 2,5GHz instead of 2886MHz in some lighter single core loads. Forcing 2886 in that case would grant us a nice boost in single core performance.

    But we are on our way to make our beloved Note9 dominate the competition😎


    right, that is one of the few things i wanna fix first
    1
    But now it’s all ok, right? Again, I think it’s a problem with new OS or data on phones. My Note 9 when I just bought it scored very low too but after some days it got much better

    Be careful man. If you mess up a CPU overclock and the system freezes, nothing happens, it will just reboot. But coding mistakes are what does this mess. But you most likely learned from your mistakes and got even better. That’s how we do experience with these phones 💪
    Trial and failure, and eventually a huge victory. And one after the other

    right, everything's fine but i still have tons of settings and tuning to do. that's why i hate installing a new rom
    yeah i knew that, thanks
  • 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
    Hi Dev, I didn't see any issue with the latest version. Its been almost a week and this one is working amazing. Thank you.
    great
    1
    So finally I decided to try your kernel, as I see great potential. Noob question here, but I am not sure if the kernel has been installed correctly, please see the attached picture. With ExKernel manager, I am able to set the I/O governor to noop, but not the CPU governor. As well, in the phone info it does now show BM Kernel, but only the stock kernel. Finally, I cannot find the RGB fade option. I am using Dr Ketan's Q17 Pro.

    Thanks in advance for your help :)

    it's not bm v2 kernel. try twrp 3.3.1.0
    if success it shoud show beastmode kernel v2
    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
    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
  • 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


    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)








    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)








    Previous releases:


    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