[Kernel | Android 10 | One UI 2.5 | FUF5/FUH1/FUJ2/FUK1/FVC2] BeastMode Kernel v2 for N960F | v2.17k2 | 20220522

Search This thread

amit_coolcampus

Senior Member
Mar 30, 2013
330
45
Delhi
Samsung Galaxy Note 9
remember to disable sync too
SmartSelect_20220125-151809_EX Kernel Manager.jpg

Which sync among both are you referring to?
 

turbomann

Senior Member
Apr 20, 2014
231
61
When I set big cluster at any value over 2002mhz it returns to 2000mhz magically 🥴, i reflash kernel and do nothing..
 
Last edited:

turbomann

Senior Member
Apr 20, 2014
231
61
Smart pack kernel and Franko kernel manager do the same behaviour. I try to set big cluster up to 2ghz and goes down at 2ghz every time I tried. Reflash kernel not solve the problem.

Android 10 ketan rom.

Update: the value in kernel manager gets stucked at 2ghz but the real value of cpu works well.
 
Last edited:
Smart pack kernel and Franko kernel manager do the same behaviour. I try to set big cluster up to 2ghz and goes down at 2ghz every time I tried. Reflash kernel not solve the problem.

Android 10 ketan rom.

Update: the value in kernel manager gets stucked at 2ghz but the real value of cpu works well.
@ykkfive I think this should be a disclaimer in the Kernel post because there's still people who don't know.

@turbomann

Exynos 9810 Big Cores only go to max 2886MHz when one core is used. The frequency you can tune in Smartpack Kernel Manager and Franco Kernel manager is only for Quad Core which is 2002MHz max.

Single Core load: 2886MHz (Already OCed from stock 2704MHz)
Dual Core load: 2314MHz (Same as stock. Maybe could go to 2652MHz)
Quad Core load: 2002MHz (only this you can change, stock is 1794MHz)

Running all big cores at 2886MHz will be very useful for frying eggs on your phone or making the battery go very big (2314 to 2886 power consumption doubles).

It's not a bug. It's CPU architecture. We have some releases that do 2314MHz on Quad and it's stable but heat production is bigger and the profit you get is not big enough because it throttles too fast. Needs an increased control temperature.
 

turbomann

Senior Member
Apr 20, 2014
231
61
@ykkfive I think this should be a disclaimer in the Kernel post because there's still people who don't know.

@turbomann

Exynos 9810 Big Cores only go to max 2886MHz when one core is used. The frequency you can tune in Smartpack Kernel Manager and Franco Kernel manager is only for Quad Core which is 2002MHz max.

Single Core load: 2886MHz (Already OCed from stock 2704MHz)
Dual Core load: 2314MHz (Same as stock. Maybe could go to 2652MHz)
Quad Core load: 2002MHz (only this you can change, stock is 1794MHz)

Running all big cores at 2886MHz will be very useful for frying eggs on your phone or making the battery go very big (2314 to 2886 power consumption doubles).

It's not a bug. It's CPU architecture. We have some releases that do 2314MHz on Quad and it's stable but heat production is bigger and the profit you get is not big enough because it throttles too fast. Needs an increased control temperature.
Oh ****. I know it but stress blinds me 😂. I thinked that tune frequency was on single core max. The strange thing is float cpu meter shows freq above 2002mhz in big cluster but appears to be the freq of 1 core x4 because is the same value always for the 4 big cores (at high freq). Actually limited big CL to 2314mhz eventually it shows 2314 in 4 big cores.

Anyway, cpu max freq works ok, kernel manager shows 2002mhz stucked but if you put max freq to 2600 avg, the max single core freq adjust to this freq (confirmed with the cpu float monitor). That shows that the max freq you tune applies to single core, not only quad core engage. But monitor shows the 4 cores at 2600 when the reality is one single big core at that freq.

Any float cpu meter trustable to see real core freq applied to single and dual core use?
 
Last edited:
  • Like
Reactions: TechNoobForSale
Oh ****. I know it but stress blinds me 😂. I thinked that tune frequency was on single core max. The strange thing is float cpu meter shows freq above 2002mhz in big cluster but appears to be the freq of 1 core x4 because is the same value always for the 4 big cores (at high freq). Actually limited big CL to 2314mhz eventually it shows 2314 in 4 big cores.

Anyway, cpu max freq works ok, kernel manager shows 2002mhz stucked but if you put max freq to 2600 avg, the max single core freq adjust to this freq (confirmed with the cpu float monitor). That shows that the max freq you tune applies to single core, not only quad core engage. But monitor shows the 4 cores at 2600 when the reality is one single big core at that freq.

Any float cpu meter trustable to see real core freq applied to single and dual core use?
CPU float is actually the best out there if you want a monitor you can keep everywhere. Devcheck is an app that is able to check frequencies and offline cores much more accurately but again, it’s not on screen.

Also yes, the tune frequency is for single core max but only after it passes the quad core max freq. below that, it sets both.
 

Top Liked Posts

  • 1
    no.why do you need that in fstab?
    There are new instructions to install Magisk
    https://topjohnwu.github.io/Magisk/install.html#instructions

    I tried to install TWRP recovery and then use your kernel
    on their webpage https://twrp.me/samsung/samsunggalaxynote9.html
    they said
    This device uses dm-verity!



    This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
    1
    No, even if I re-flash the magisk zip from twrp, it doesn't install
    1 try install magisk as "apk", you may need to rename the file. you may also consider uninstall it after the installation to get a clean installation
    2 flash the boot.img (no root), then install magisk

    tell me if it works for you
  • 3
    20220522 - v2.17k2 released
    2
    20220522 - v2.17k2 released
    NOTE
    NOT compatible with alex 3.3 (with may updates)
    will send email to samsung for latest source for may
    1
    Hi guys kinda new to the whole custom kernel thing since ive only use custom rom (dr ketan q18), just wondering if i can use this kernel without root? Something like flashing this kernel then leave it be, any advice would be appreciated. Thanks
    I haven't tried but there is a non-root version of this kernel. I would just back up and give it a go, if anything just restore. Just make sure you're on the right build before flashing.
    1
    Hi guys kinda new to the whole custom kernel thing since ive only use custom rom (dr ketan q18), just wondering if i can use this kernel without root? Something like flashing this kernel then leave it be, any advice would be appreciated. Thanks
    up to q18 (fuj2) atm
    1
    Hey excuse me but i how did you manage to download it ? the bitly links arent working for me
    which one you want to download?
  • 15
    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 (partially done)
    - 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
    @faux123
    xxmustafacooTR


    Source code:
    github
    8
    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




    20020526
    NOTICE: many of the links below were blocked by bit.ly for unknown reasons. up to now the latest 2.17k2 links are not affected. i have reported to them already





    Changelog and Download (NO mirror please):

    *** TWRP 3.3.1.0 is recommended


    20220522 - v2.17k2
    - NOT compatible with alex 3.3 with may updates, screenlock and samsung account problems may occur
    - patched with latest N960FXXU9FVC2 source
    - fixed gpu table max freq and other related stuff
    - all gpu frequencies shown
    - big cores single 2886000, big cores triple/quad 2314000 (Tip: overclock may damage your phone, you have been warned)
    - 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.17k2-FUF5-magisk_patched.zip (patched with Magisk 23.0)
    boot.img (no root)

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

    FUJ2/FUK1
    BM-Kernel-v2.17k2-FUJ2-magisk_patched.zip (patched with Magisk 23.0)
    boot.img (no root)

    FVC2
    BM-Kernel-v2.17k2-FVC2-magisk_patched.zip (patched with Magisk 23.0)
    boot.img (no root)










    20220122 - v2.17i
    - cpu oc big cores quad to 2002000
    - cpu oc little cores to 2002000
    - preset cpu uv for frequency < 2000kMhz
    - preset gpu uv for frequency < 500kMhz
    - added dynamic fsync: performs fsync only when screen is off for maintaining data integrity (make sure to enable both fsync and dynamic fsync options)
    - raised some internal values:
    -- little cores will go to 2002000 instead of staying at 1950000
    -- big cores will go back to higer frequencies after throltted when temperature drops
    - added frandom
    - some more tweaks i cant remember
    - 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.17i-FUF5-magisk_patched.zip (patched with Magisk 23.0)
    boot.img (no root)

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

    FUJ2/FUK1
    BM-Kernel-v2.17i-FUJ2-magisk_patched.zip (patched with Magisk 23.0)
    boot.img (no root)









    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) - RE-UPLOADED

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

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









    Previous releases:


    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)








    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




    .
    5
    ok guys, sorry to keep you waiting so long

    due to the latest linux kernel upstreams being applied together with those uv introduced before, we faced some problems with the artifacts. they are not major problem tbh but who knows. it will be a disaster for me to redo the changes again and again if it becomes a serious problem

    i had to decide whether we keep the uv or continue with the upstream. and after many tests i decided to ditch those kernel patches, at least for now

    i will then continue what i wanted to do with this kernel

    btw, the release build is ready, but i want to wait for the latest fuj2 patches from samsung as i dont want to release another build shortly after this one. i will send them an email later

    anyway, we will have some improvements this time again! so stay tuned!

    thanks



    edit
    here's a teaser from my hard working tester @TechNoobForSale. thanks so much for your time and efforts
    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