[Kernel | Android 10 | One UI 2.5 | FUF5/FUH1/FUJ2/FUK1/FVC2/FVH1] BeastMode Kernel v2 for N960F | v2.18f1a3 | 20230223

[TechNoobForSale]

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

Also,
Undervolt GPU by 10-15% and run 572MHz more frequently. Then i think Note9 GPU could have same score with the 9820 in AnTuTu V9. Which only less by 26%.

Also if you found a way to disable the CPU DVFS, or at least increase that horrid 70°C throttling point, we are going to get around 8% extra CPU performance.

 

[TechNoobForSale]

After tweaking here and there, I have done these after all:
Disable app: device care, game optimizer, game launcher, game plugin, and at last
DVFS. I done it by these steps below

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

And for the result: Truck Simulator Ultimate significantly has lower frame drop

Trying to remove the permissions to the DVFS files doesn't work. They turn themselves back on


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

So it seems that the DVFS was at the fault for the Minimum and maximum GPU frequency doing whatever it wanted. With it disabled, the GPU sticks at 572MHz at all times if I put the minimum at such a number. However after reboot, said changes revert back to normal.

 

[TechNoobForSale]

Results of the tests with the GPU DVFS disabled:
Ambient Temp: 22°C
Chassis Temp: 15°C (26°C under load, 30°C hotspot)
Tools: Xiaomi FunCooler Pro

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

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

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

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

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

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

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


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

 

[ykkfive]

Results of the tests with the GPU DVFS disabled:
Ambient Temp: 22°C
Chassis Temp: 15°C (26°C under load, 30°C hotspot)
Tools: Xiaomi FunCooler Pro

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

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

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

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

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

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

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


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

so it works, rite?
you can add the changes to an init script as it will roll back after reboot

btw i just installed a new build, better kill me, my screen turned into something like an old tv with full screen of snowflakes... i am afraid it's about to die....

 

[TechNoobForSale]

so it works, rite?
you can add the changes to an init script as it will roll back after reboot

btw i just installed a new build, better kill me, my screen turned into something like an old tv with full screen of snowflakes... i am afraid it's about to die....

Then why not install the old one and check if it gives you the same issue?
Also no idea how to do an init script. Either way not much of an issue for me, because I guess you already realized that the DVFS is as good as gone.

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

 

[ykkfive]

Then why not install the old one and check if it gives you the same issue?
Also no idea how to do an init script. Either way not much of an issue for me, because I guess you already realized that the DVFS is as good as gone.

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

yeah of coz i did, i installed an old build and it's fine now
it made me more certain that i have loss in the lottery, very likely hardware problems
for first it turned green in recovery when idle months ago, then now with the snowflakes. but even though it's a bad contact with the cable of the screen, i couldn't fix it by myself

 

[TechNoobForSale]

yeah of coz i did, i installed an old build and it's fine now
it made me more certain that i have loss in the lottery, very likely hardware problems
for first it turned green in recovery when idle months ago, then now with the snowflakes. but even though it's a bad contact with the cable of the screen, i couldn't fix it by myself

Usually the lottery thing only applies to the processors. The behaviour of your screen is really weird. I guess that you should make the overclock options something that can be configured by the user in OS so that we can test it for you if your phone has failed the lottery

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

 

[trevinutomo]

yeah of coz i did, i installed an old build and it's fine now
it made me more certain that i have loss in the lottery, very likely hardware problems
for first it turned green in recovery when idle months ago, then now with the snowflakes. but even though it's a bad contact with the cable of the screen, i couldn't fix it by myself

Is it possible that ur screen's flex cable damaged? If that so, then after swap it with new one surely solve those green screen and snoflakes

 

[trevinutomo]

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

 

[ykkfive]

Usually the lottery thing only applies to the processors. The behaviour of your screen is really weird. I guess that you should make the overclock options something that can be configured by the user in OS so that we can test it for you if your phone has failed the lottery

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

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

i did nothing unusual actually but upstream the linux kernel

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

 

[ykkfive]

Is it possible that ur screen's flex cable damaged? If that so, then after swap it with new one surely solve those green screen and snoflakes

it could be, but i am lacking the technique to repair it

 

[ykkfive]

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

no problem mate, as i always said, i need inputs
however not all can be ported due to different linux version etc
anyway i will take a look at that later. thanks

 

[TechNoobForSale]

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

 

[ykkfive]

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

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

 

[TechNoobForSale]

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

LMAO. Take it nice, relaxed and easy man. Best of luck for everything. U got this

 

[ykkfive]

Then why not install the old one and check if it gives you the same issue?
Also no idea how to do an init script. Either way not much of an issue for me, because I guess you already realized that the DVFS is as good as gone.

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

oh btw, you guys mentioned 70C throttling point, where did you find it, i mean the 70C?

 

[TechNoobForSale]

oh btw, you guys mentioned 70C throttling point, where did you find it, i mean the 70C?

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

 

[ykkfive]

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

alright, coz i couldnt find the 70C specified so i believe it could be arrived by some calculations or affected by other hardware

in fact i have applied most of the oc things before but when tested the performance dropped quite significantly. so i removed them before releasing those builds

 

[TechNoobForSale]

alright, coz i couldnt find the 70C specified so i believe it could be arrived by some calculations or affected by other hardware

in fact i have applied most of the oc things before but when tested the performance dropped quite significantly. so i removed them before releasing those builds

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

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

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

 

[ykkfive]

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

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

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

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

anyway, these will be addressed next