• 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.11c6 | 20210920

Search This thread

otaking71

Senior Member
May 11, 2009
64
78
since i can't seem to find it anywhere else...would you happen to know where i can see the stock voltage table for all of the cpus and gpu?
 

otaking71

Senior Member
May 11, 2009
64
78
and i read your comment in freeza's original thread...long time lurker...but i'm also in your boat...having to replace my sprint note 4...and went this route....man so much has changed. I think _A LOT_ can be gained by having a proper kernel. I'm more than willing to be a guinea pig if you need a good one that will give you good feedback. I just hate how the 64 bit phones and their locked bootloaders really thinned out the dev community =/
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
2,982
2,903
ykkfive.blogspot.com
and i read your comment in freeza's original thread...long time lurker...but i'm also in your boat...having to replace my sprint note 4...and went this route....man so much has changed. I think _A LOT_ can be gained by having a proper kernel. I'm more than willing to be a guinea pig if you need a good one that will give you good feedback. I just hate how the 64 bit phones and their locked bootloaders really thinned out the dev community =/

first, i would like to apologize for the delay.... i was busy fixing my router, just recovered part of it about half an hour ago... the files were ready but i need to compare them and change them from hex to dec for you

yeah the changes were so.... i cant think of a word to describe it atm, but a few yrs ago when i looked at the system partition it made me sick really.... lib, lib64, fake lib, etc. then p & q, changes in SAR, different build.prop files (there r 3 or more co-exist in a device), some rollbacks in q from r etc, all these things are kinda a joke imo, not to mention the bootloader thing, and those snapdragon soc....

anyway, right now i am taking a break after a tough challenge with my router, and the network access resumed bascially. i will post the original values later

lastly, thanks a lot man, i am more than happy to put u in the tester list tbf 😄
 

otaking71

Senior Member
May 11, 2009
64
78
first, i would like to apologize for the delay.... i was busy fixing my router, just recovered part of it about half an hour ago... the files were ready but i need to compare them and change them from hex to dec for you

yeah the changes were so.... i cant think of a word to describe it atm, but a few yrs ago when i looked at the system partition it made me sick really.... lib, lib64, fake lib, etc. then p & q, changes in SAR, different build.prop files (there r 3 or more co-exist in a device), some rollbacks in q from r etc, all these things are kinda a joke imo, not to mention the bootloader thing, and those snapdragon soc....

anyway, right now i am taking a break after a tough challenge with my router, and the network access resumed bascially. i will post the original values later

lastly, thanks a lot man, i am more than happy to put u in the teste
between the change in the bootloader....the change in scheduler behavior....and ALSO going having these phones with multiple core types....the learning curve is beyond steep. I used to keep a spare note 4 for parts...I might get a spare n960f if this picks up. I saw the gpu voltages stock...and the scaling makes 0 sense....i'd hate to see what the cpu side looks like. From what i've understood...the asv values are derived from silicon..while eas values are in the kernel?
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
2,982
2,903
ykkfive.blogspot.com
between the change in the bootloader....the change in scheduler behavior....and ALSO going having these phones with multiple core types....the learning curve is beyond steep. I used to keep a spare note 4 for parts...I might get a spare n960f if this picks up. I saw the gpu voltages stock...and the scaling makes 0 sense....i'd hate to see what the cpu side looks like. From what i've understood...the asv values are derived from silicon..while eas values are in the kernel?


oops i got it wrong, i cant give you those values atm. all i can tell is the default voltage for gpu should be 800 max, looks like have to trace for the values in the source codes
 

otaking71

Senior Member
May 11, 2009
64
78
oops i got it wrong, i cant give you those values atm. all i can tell is the default voltage for gpu should be 800 max, looks like have to trace for the values in the source codes
i did find those. and it's not only 800 max...it's 800 across the board stock. it's the cpu voltages i've not seen any sign beyond andrei's article on the note 9 on anandtech. thanks for your responses.
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
2,982
2,903
ykkfive.blogspot.com
i did find those. and it's not only 800 max...it's 800 across the board stock. it's the cpu voltages i've not seen any sign beyond andrei's article on the note 9 on anandtech. thanks for your responses.

here u r

572000=700000
546000=693750
455000=662500
338000=625000
299000=612500
260000=600000

ie the gpu volt is not undervoltaged by default

yeah may be u r right, 800 may not be the max value but by design
 
Last edited:

otaking71

Senior Member
May 11, 2009
64
78
here u r

572000=700000
546000=693750
455000=662500
338000=625000
299000=612500
260000=600000

ie the gpu volt is not undervoltaged by default
Have you verified that the undervolt is actually working? I'll start testing it myself on how the other things interact. I've always run my phone slower than stock...and I can already reproduce some really weird glitches just via forcing certain frequency combinations. I think I'm getting a feel for how effed up the 9810's power implementation is. It's rather intertwined.
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
2,982
2,903
ykkfive.blogspot.com
Have you verified that the undervolt is actually working? I'll start testing it myself on how the other things interact. I've always run my phone slower than stock...and I can already reproduce some really weird glitches just via forcing certain frequency combinations. I think I'm getting a feel for how effed up the 9810's power implementation is. It's rather intertwined.

from what i can tell is the changes in the voltage settings are stored in the voltage table, so it should be applied
i too undervolt stock values all the time but i dont find any glitches (except antutu), perhaps you can try to adjust the governor and it's settings like high speed delay or high speed load, i find these 2 help
 
Last edited:

otaking71

Senior Member
May 11, 2009
64
78
it's not an undervolt issue. I found the issue on other kernels. I just tried yours a few hours ago and yours seems to be the only one that works with newer stuff and has any type of undervolt. I only underclocked. It seems to be how the clock domains work on this thing. BTW, I can't seem to actually get the gpu to undervolt with the mtweaks app....what app are you using?
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
2,982
2,903
ykkfive.blogspot.com
it's not an undervolt issue. I found the issue on other kernels. I just tried yours a few hours ago and yours seems to be the only one that works with newer stuff and has any type of undervolt. I only underclocked. It seems to be how the clock domains work on this thing. BTW, I can't seem to actually get the gpu to undervolt with the mtweaks app....what app are you using?

so you think this kernel suits you better or not? coz some ppl prefer other features or results, it's not uncommon, and i would love to hear feedbacks whether it is good or not

btw what "newer stuff" are you talking about?

actually i don use kernel manager as i prefer init scrips (i am a command line guy). it is just for showing the results to the users easily. the kernel manager is a fork of mtweaks called thunder tweaks 9810

and if you reallywant to test the undervolt things, try pushing up the lower 3 freqs volt and leave the phone idle or with a few touches and you should feel the heat, this is relatively safe since undervolting too much will cause the phone crash while over volting it below the highest voltage supported/needed should be fine
 
Last edited:

otaking71

Senior Member
May 11, 2009
64
78
so you think this kernel suits you better or not? coz some ppl prefer other features or results, it's not uncommon, and i would love to hear feedbacks whether it is good or not

btw what "newer stuff" are you talking about?

actually i don use kernel manager as i prefer init scrips (i am a command line guy). it is just for showing the results to the users easily. the kernel manager is a fork of mtweaks called thunder tweaks 9810

and if you reallywant to test the undervolt things, try pushing up the lower 3 freqs volt and leave the phone idle or with a few touches and you should feel the heat, this is relatively safe since undervolting too much will cause the phone crash while over volting it below the highest voltage supported/needed should be fine
oneui / android 10..

and there's definitely something bugged about the kernel.

using an app i could not adjust the voltages at all via the slider on mtweaks or thundertweaks....that corrected itself once i did a wipe and reinstall of the alexisrom and the kernel. I haven't been able to replicate that behavior since. I suspect this was a magisk screwing things up from udates and crap.

i did see the kernel wouldn't boot noblerom at all..and even on the clean reload of alexisrom...if you change any of the gpu speed settings...the voltage sliders completely disappear until reboot. this behavior happens on both mtweaks and thundertweaks

I suspect it's a similar bug to the offlining of a core you mentioned on the previous page..

as for what I want...I want my undervolts.....but there's more to the tuning that I even realized initially. the eas scheduler thing is a WHOLE another animal.

and I understand the ramifications of undervolting...it's just shocking how badly optimized samsung has left it. I actually intend on figuring out the proper voltage scaling curve for mine....and possiblying figure out a rough safe adjustment based on the avs/asv (whatever you wanna call it) bin tables (this is why i want that data)

I was able to hit top 1% of exynos note 9 on the 3dmark gpu benchmark via some minor frequency tuning last night by underclocking the cpus while forcing the phone to stay in the top mif clock domain. I figure if we get a proper voltage curve...we can allow some real overclocking of this thing and see what it can REALLY do.
 
Last edited:

ykkfive

Inactive Recognized Developer
Jul 25, 2010
2,982
2,903
ykkfive.blogspot.com
oneui / android 10..

and there's definitely something bugged about the kernel.

using an app i could not adjust the voltages at all via the slider on mtweaks or thundertweaks....that corrected itself once i did a wipe and reinstall of the alexisrom and the kernel. I haven't been able to replicate that behavior since. I suspect this was a magisk screwing things up from udates and crap.

i did see the kernel wouldn't boot noblerom at all..and even on the clean reload of alexisrom...if you change any of the gpu speed settings...the voltage sliders completely disappear until reboot. this behavior happens on both mtweaks and thundertweaks

as for what I want...I want my undervolts.....but there's more to the tuning that I even realized initially. the eas scheduler thing is a WHOLE another animal.

and I understand the ramifications of undervolting...it's just shocking how badly optimized samsung has left it. I actually intend on figuring out the proper voltage scaling curve for mine....and possiblying figure out a rough safe adjustment based on the avs bin tables (this is why i want that data)

it is weird that "if you change any of the gpu speed settings...the voltage sliders completely disappear until reboot. this behavior happens on both mtweaks and thundertweaks"

well, i have never experienced the problem with gpu setttings, EXCEPT that as i mentioned before, these kernel mangers save the settings incorrectly, or prehaps in a different manner than i want to. for example, some of the cores will be disabled when the profile is saved, even though you didnt touch anything in the cpu tab/page


i dono if it's the magisk's problem or not, but i have been using magisk 23 since i rooted my n960f and without any problem. i have tested with dr ketan's q16 and now superstable 19 and everthing is fine exception some minor bugs from the roms installed

btw, fuf5 is imminent with updated sources from samsung
 

otaking71

Senior Member
May 11, 2009
64
78
it is weird that "if you change any of the gpu speed settings...the voltage sliders completely disappear until reboot. this behavior happens on both mtweaks and thundertweaks"

well, i have never experienced the problem with gpu setttings, EXCEPT that as i mentioned before, these kernel mangers save the settings incorrectly, or prehaps in a different manner than i want to. for example, some of the cores will be disabled when the profile is saved, even though you didnt touch anything in the cpu tab/page


i dono if it's the magisk's problem or not, but i have been using magisk 23 since i rooted my n960f and without any problem. i have tested with dr ketan's q16 and now superstable 19 and everthing is fine exception some minor bugs from the roms installed

btw, fuf5 is imminent with updated sources from samsung
I just know I haven't saved a profile yet on the phone. I know you make the change in the app..leave and come back in...sliders go poof. It would take somebody who has coded a kernel manager type app to give any more insight. I just do know I've been able to explicitly replicate this one on 3 installs now.
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
2,982
2,903
ykkfive.blogspot.com
I just know I haven't saved a profile yet on the phone. I know you make the change in the app..leave and come back in...sliders go poof. It would take somebody who has coded a kernel manager type app to give any more insight. I just do know I've been able to explicitly replicate this one on 3 installs now.
ok i see what you mean, and yes I use them to show those possible under volt values only as i set them in init scripts actually. so this explains why i didnt notice those bugs you mentioned

btw, thanks for asking for the default values, looks like i have found something very interesting
 

otaking71

Senior Member
May 11, 2009
64
78
ok i see what you mean, and yes I use them to show those possible under volt values only as i set them in init scripts actually. so this explains why i didnt notice those bugs you mentioned

btw, thanks for asking for the default values, looks like i have found something very interesting
I'll explain the bug i found with the cpu clock speeds I've found...it's not tied to your kernel at all.


If you look at the exynos9810.dtsi file...it shows the clock domains for both the cpu and the memory memory interface controller (MIF) The same clocks are listed in gpu dvfs table in gpu_exynos9810.c.

If you force the mif clock domain to be lower than the gpu's desired domain...it reboots the phone. This has some interesting ramifications. I remember hearing the battery limited/power saving mode would force the memory controller to run at half speed...which are the speeds of the mif we see listed with the small cores. In theory, we should be able to ignore this and gain a bit of performance with a change here.
 

ykkfive

Inactive Recognized Developer
Jul 25, 2010
2,982
2,903
ykkfive.blogspot.com
I'll explain the bug i found with the cpu clock speeds I've found...it's not tied to your kernel at all.


If you look at the exynos9810.dtsi file...it shows the clock domains for both the cpu and the memory memory interface controller (MIF) The same clocks are listed in gpu dvfs table in gpu_exynos9810.c.

If you force the mif clock domain to be lower than the gpu's desired domain...it reboots the phone. This has some interesting ramifications. I remember hearing the battery limited/power saving mode would force the memory controller to run at half speed...which are the speeds of the mif we see listed with the small cores. In theory, we should be able to ignore this and gain a bit of performance with a change here.
thanks for your inputs. i am aware of this overriding problems in a few areas but either i couldnt fix them before or partly due to too many changes are involved which i couldnt make it quickly at the moment. so i preferred to tune the queuing things first, and try to use the big cores if possible. that's what I planned
 

Top Liked Posts

  • 1
    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
  • 3
    20210920 - v2.11c6 released
    for fuf5 and fuh1 respectively
    2
    Also for people's happiness right now I am running a variety of Benchmarks to study how much the performance of the device was increased. Version of the Kernel is latest as of now. GPU overclock not possible, therefore 572MHz max. Games are not tested as of now as the improvements aren't too remarkable for me to be able to see any visible improvement even if I wanted. I'll have to overclock in order to see. I am on stock One UI 2.5 Android 10.

    NW: I dialed small cores's frequency back to 1798MHz from this Custom Kernel's stock 2002MHz for the first tests, but so far I still see an improvement that ranges between 5 to 10% in all benchmarks.1798MHz to 2002 is roughly a 12% overclock either way and the small cores are very weak, so the difference wouldn't be too astonishing. The phone is also actively cooled down so that peak output is ensured.

    Geekbench 5:
    Single Core: 698
    Multi Core: 2157

    These values are in line with the stock Kernel. However I now get them more frequently and they are still in the "rare zone" for Exynos 9810 scores.

    PCMark, Storage 3.0
    Storage score: 6183 (Equal to average. Expected since there is no claimed storage performance boost. Noted though that the singular Storage 3.0 benchmarks have shown improvements that could even go as far as 50%. Therefore the overall score may not be fully accurate).

    PCMark, Work 3.0 score: 6872 (Roughly 12% above the average. Some individual tests almost got a 20% boost)

    AnTuTu:
    Total: 420.414
    The score is roughly 5% higher than the best I could get on the stock Kernel (400.786)
    The GPU score increased by 3%. CPU increased by roughly 4%. Memory performance increased by about 10%. User experience too about 10%.

    3DMark, Icestorm Unlimited:
    Total: 46.574
    This is roughly a 5% improvement over stock average. Not much to say.

    3DMark, Slingshot Extreme Unlimited (OpenGL ES 3.1):
    Total: 4.335
    This is in line with the stock kernel, even though it defeats 92% of all other Samsung Galaxy N960F.

    3DMark, Wildlife Unlimited:
    Total: 2.367
    Perfectly in line with the average, beating 51% of the N960F devices. GPU is not overclocked and no particular optimization or driver update is applied to it according to the developer, so this has to be expected as this is exclusively a GPU intensive benchmark.

    CPU Throttling Test:
    Average: 107.159GIPS
    Max: 125.479GIPS
    Min: 89.341GIPS

    This is perfectly average.

    GFXBench:
    High-Level Tests:
    1080p T-Rex Offscreen (ES 2.0): 132fps (This is average)
    1080p Manhattan Offscreen (ES 3.0): 80fps (Unknown)
    1080p Manhattan 3.1 Offscreen (ES 3.1): 47fps (This is in the margin of error above average)
    1080p Car Chase Offscreen (ES 3.1): 29fps (Unknown)
    1080p Aztec Ruins Offscreen (Normal Tier, ES 3.1): 31fps (Unknown)
    1440p Aztec Ruins Offscreen (High Tier, ES 3.1): 11fps (This is average)

    Low Level Tests:
    1080p Texturing Offscreen: 7.419 MTexel/s. (This is average)
    1080p Driver Overhead 2 Offscreen: 33fps (This is average)
    1080p ALU 2 Offscreen: 100fps (Unknown)
    1080p Tessellation Offscreen: 71fps (Unknown)



    Battery life under the benchmark's stress: In line with what people would expect from stock. Probably just a little bit lower. But it's not nothing upsetting. (Reminder this is at stock frequencies).

    Verdict: The Kernel overall even at totally stock frequencies offers fair improvements compared to the stock firmware. Further optimization would help the phone greatly increase its CPU performance, I will give sources following this.

    Tips for the developer: There is plenty of work that has to be done in order to solve Samsung's horrible work with Exynos 9810, which is in reality a very powerful SoC, cursed with an horrible Governor, slow hotplug, scheduler system and conservative power choices. I suggest to check out the analysis of the very respectable Andrei Frumusanu, which tweaked the Exynos 9810's CPU and extracted its full performance, and opened a path to even wider possibilities.


    these are the sources that may give useful tips for this kernel's future development. Unless, the developer already applied said improvements in the Kernel but refrained from openly stating it. RAM overclocking may also be another thing to keep in mind, as another developer, ace2nutzer, considered that possibility on Samsung Galaxy G950F and G955F. Some useful tips may also be found in the Endurance Kernel, made by developer Eamo5, like the 16ms PELT Half-Life. Support for F2FS would also grant an hefty boost in storage performance. However that file system seems very unstable by nature and I would see why its implementation would end up being impossible.

    NW: CPU load is not visible even on N960F devices. This is to answer a person who couldn't see said data on their N960N. Application used to monitor System stats is CPU Float. CPU and GPU temperature is also not given out by the system, making it impossible for me to fine tune any type of overclocking in order to extract the most out of the Kernel.
    2


    well, thanks very much for your suggestions. in fact i am still trying (and learning) to make it better in some aspects. but also, as i said, there are some trade offs so that's why (partly) i have removed the gpu oc for now, for instance

    and about the performance/benchmarks, wow, just like reading a review. and for those i have tested before you have almost reached my peak numbers already

    and yeah i have read those articles before, and most of them were implemented by other kernels on github already and cherry picked into this kernel. on the other hand i am still trying to patch the f2fs thing, and gpu oc plus other tweaks are still on the list including scheduling and memory etc but these will take time to implement and test

    anyway, once again, thanks for your inputs mate!

    ps i didnt aware the loadings/stats are not shown anymore since i dont rely on those kernel managers but init scripts to make the changes, i will take a look at that too
    2
    You're right. I apologize that I forgot about your busy schedule. Then there is no problem for me to keep providing benchmarks and gaming numbers. I can actually provide far more details than beforehand. So you can even stop benchmarking to save some time. I'll do it.

    And yes. The +30% results are actually achievable with your Kernel, but not with the stock frequency range (attention, no overclocking intended). With the stock range, aka 650-1794MHz big and 455-1794MHz SMALL, PCMark still sees a tangible 11% improvement. Going for such wide frequencies ranges with Samsung's scheduler is a bad idea because it's slow in ramping up the frequency (410ms to go up to 1794MHz from min according to Andrei). And in my experience, just raising minimum small frequency to about 1GHz and minimum big frequency to about 1.2GHz minimum brought that increase to the 29% I mentioned. Putting it in a performance-like status (which means no transition across frequencies at all) gave me results so high I ACTUALLY managed to beat an Exynos 9820 and almost match a Snapdragon 855 in PCMark, which is a daily usage benchmark, which made me extremely impressed and you should be too.

    And this wouldn't even be detrimental to battery life. Like you said before, the flexibility of the Custom Kernels comes from this. We can put whatever we want, when we want it. And profiles furtherly make that easier. So that one can put power saving measures when needed, and full performance also when needed. It's a win-win! And these results wouldn't have been achieved with the stock Kernel, even with performance governor. Because it lacks all the tweaks this one has. All that has to be done right now is this bug fixing.

    As you add the tweaks bit by bit, I will test the new releases and tell you how it's going. And one last note, if it is even possible, if you have the time for it, try to make it possible to tune the frequencies of the single/dual and quad core frequencies of the big cores. Because as of now it is basically impossible to overclock them and gain multi core improvements. That is honestly my only request together with a revision of the thermal and power throttling systems, because they appear to be interfering with my Kernel settings (Little CPU max frequency, GPU frequency irreversibly. Throttling threshold APPEARS to be at 70°C on CPU. Making it tunable would be great.). The current governors for the Mali GPU also are super conservative (and raising minimum frequency to 572MHz doesn't affect the GPU's behaviour, as it ignores it and goes at the frequency it wants AS SOON as I enter a game), just like Mali GPUs in general. Performance governor would make gaming buttery smooth when used. There is a lot of work to do, but this is just the very beginning, you have been back in the game for what, 2 months? And you have already done all of this. You can do great things. Believe in the potential of this Exynos 9810 because it does have it. It's all about pulling it out. And I'm glad to see I can free your schedule a bit. Again, good luck with everything mate.

    no problem and thanks mate

    and regarding the time needed to pump up the cpu, there has been some tunings deployed for the 9810 custom kernels like reducing the number of cycles or time per wait etc, so it should be quicker than the stock one. also for the gpu, try changing the interactive governor settings as to when to push it up and at which freq

    i am currently working on updating the file system stuff and it's almost done. once it's finished, together with a few basic stuffs i will go back to the cpu, gpu and freq things since they can affect the overall performance badly. so i don want to build on top of these like before where i have to redo most of the changes in case of problems arise

    once again thanks for your help
    1
    Okay, I only have one more question. This Kernel enables BIG cores to be overclocked up to 2880MHz. However according to Andrei. (An anand tech fella who did investigations on Exynos 9810), the Big cores only go at 2704MHz on single core. They dial back to 2314MHz in dual/tri core workloads and then they go at 1794MHz at quad core. This means that achieving 2.8GHz is actually impossible on all cores, right? How far should I be able to go though? Your Kernel locks the BIG cores at 1.8GHz which means only the small cores are actually overclocked. Is there something I am overlooking? I use Franco Kernel Manager to control the kernel. And it says all the 4 cores go at max 1794Mhz. Do they boost up to 2.89 in single core workloads? I noticed that it boosted to 2860MHz for a second or so on a single threaded workload. But that's not at 2890MHz and I have no clue regarding the other stats. Does changing that 1794MHz in my Kernel manager only refer to the quad core frequency? If I raise it is it going to mess everything up?

    right, 2.8 for 4 cores is not possible. the max freq will drop when more than 1 cores are used, and so on, and max at 17xx when 4 cores are used. if you read the cpu time in those kernel manager, u should see 27xx is non zero, meaning that 2.7 is achievable but not lasted for too long unless u restricted to single core

    i have seen 1 core max at 27xx so far but i did not pay too much attention on it becoz it is only less than 3% difference. more i found that the linkages between cpu, mem, gpu are tight which will pump up the heat. so in real practice, ocing too much may not necessarily means it runs faster since there are cooling points and when these cooling points are reached the freq will be forced down. chances that it may run faster in general say at 2.1 max due to less heat is generated but still maintaining a good performance. however it depends on how you will use your phone

    actually i am still changing these numbers, just like in the latest build, i have removed some changes to make the phone run faster as it should be

    this may not answered all of your questions but feel free to ask anytime
  • 10
    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):


    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


    gpu_voltage.jpg