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

[ykkfive]

I see would like OP to reconfirm it.

ps if you simply mean this knox 0x0, it's done by rom modders

 

[dreamboyhđ]

Can I ask if this kernel can be used for N960N, thanks

 

[otaking71]

i'm finally back..haha..life has been kicking my ass...glad to see others picking up and chiming in.

As with regards to the gpu, this thing _SHOULD_ in theory be able to get into the 800+ mhz range as arm was touting 850 mhz on an older process for this gpu design. YKK knows my thoughts on what needs to be done to fully utilize it. There's _DEFINITELY_ a stupid amount of performance left on the table.


The main thing that still bugs me is how none of the kernels seem to behave the consistently across multiple kernel managers. I got a partial compile, last time I spoke to ykk. I'll eventually figure out how to get a compile so I can contribute more technical stuff.

 

[ykkfive]

Can I ask if this kernel can be used for N960N, thanks

one user has repoted it works with n960n before, you can search this thread for his reply
and, from what i can see, there were many downloads came from korea too but honesty i cant guarantee because i don own a n960n. sorry about that

 

[ykkfive]

i'm finally back..haha..life has been kicking my ass...glad to see others picking up and chiming in.

As with regards to the gpu, this thing _SHOULD_ in theory be able to get into the 800+ mhz range as arm was touting 850 mhz on an older process for this gpu design. YKK knows my thoughts on what needs to be done to fully utilize it. There's _DEFINITELY_ a stupid amount of performance left on the table.


The main thing that still bugs me is how none of the kernels seem to behave the consistently across multiple kernel managers. I got a partial compile, last time I spoke to ykk. I'll eventually figure out how to get a compile so I can contribute more technical stuff.

welcome home, no 7 cristiano ronaldo!

oh, sorry... haha

yeah that's great and i knew you dont want ppl to give you a hand and throw everything to you unless you have to, coz you will try it youself and look for a solution first. am i correct? (say yes pls or it will be embarrassing...)

tbh it will be a boost since my note9's screen turned greenish before and i really scared to perform any risky experiment on my note9...

 

[TechNoobForSale]

welcome home, no 7 cristiano ronaldo!

oh, sorry... haha

yeah that's great and i knew you dont want ppl to give you a hand and throw everything to you unless you have to, coz you will try it youself and look for a solution first. am i correct? (say yes pls or it will be embarrassing...)

tbh it will be a boost since my note9's screen turned greenish before and i really scared to perform any risky experiment on my note9...

To be honest I think the green tint is not related to the GPU, but rather, the display itself (my S8's broken display has a very intense green tint and it doesn't display anything, however the phone works and is responsive). I've experienced GPU instabilities on phones before and they manifest themselves as artifacts or total system freeze (More often than not the second).

You can tell a GPU-issued crash from a CPU-issued crash because the GPU crashes WON'T automatically restart the phone, while CPU crashes do. Either way don't even bother lmao. Pushing the Mali to 850MHz on this thing is going to cause the temperatures to rise very high, unless there is some miracle in the architecture I'm not aware of. The highest I've seen is 775MHz and I still believe that is a very pushed overclock, but 598MHz isn't enough either.

Basically what you should do is rise the throttling threshold to 90-95°C. That is going to increase our headroom greatly. As of now it's at 70°C, and it hinders performance a lot (during heavy gaming my phone will start to lose performance extremely fast due to that).

Either way we should keep GPU stuff for later because the main problem in the Exynos 9810 is how stupidly underclocked and hindered the CPU is.

Basically like your roadmap states. You wanted to add F2FS support, you did it. One of the objectives are complete. Now you are working to fix the ext4 and system stuff, then we should move on CPU related stuff and then GPU.

 

[otaking71]

lol...ykk.. you are indeed correct.

technoob...which kernel was this? and did they actually put in correct voltages for those speeds? if they just said eff it and did max voltage then you'd definitely run into temp issues. it would be crazy if they did it with the joke of a stock voltage table. overclocks won't help this cpu much at all. the problem with this chip is that it runs hot and _NEEDS_ to be fed. The biggest gains are going to come from the ram tbh. With that wide a core...on top offeeing agpu...thatyou need more memory performance.

 

[TechNoobForSale]

lol...ykk.. you are indeed correct.

technoob...which kernel was this? and did they actually put in correct voltages for those speeds? if they just said eff it and did max voltage then you'd definitely run into temp issues. it would be crazy if they did it with the joke of a stock voltage table. overclocks won't help this cpu much at all. the problem with this chip is that it runs hot and _NEEDS_ to be fed. The biggest gains are going to come from the ram tbh. With that wide a core...on top offeeing agpu...thatyou need more memory performance.

Alright so. The Kernel that reached such crazy clock speeds for the GPU was the Zeus Kernel (Private Edition). However it only runs on the Oreo OS and the overclock are way too pushed and not all devices could handle it, causing phone reboots, which confused people.
Also, you are mistaken. And I need to specify some things.
Firstly, Exynos 9810 has been underclocked by Samsung, which means that by rising frequencies, we are just getting back what they took away from the device we paid for. The M3 cores are indeed very, very power hungry. But you have to expect a power requirement and heat output increase when doing intensive tasks anyways, on any device. The 9810 was meant to run at 2.9GHz in single core, 2.5GHz in dual core and 2.314GHz in tri and quad core. It has been underclocked to 2.7, 2,3 and 1.8 respectively. The small cores were meant to run at 1.9GHz. They got underclocked to 1.8 too.

According to my expectations and estimations, the Exynos 9810 would be able to match the 9820, clearly while consuming much more power, but not as much as you would expect! To my eyes, the 9810 was an amazing processor. Mistreated by Samsung so badly. The potential is off the charts. RAM can only yield an improvement if overclocked. This device already has plenty of it.

 

[otaking71]

The m3 core is effectively 6 instructions wide. Yes it has 12 pipelines, but it can only feed 6 per cycle. At that rate, your memory bandwidth requirements just to feed a single m3 core fully is 4bytes per instruction x 6 pipelines x 1800 mhz = 43 GB of bandwidth. Additional clock speed is useless if you can not get data into the cpu. It can't process data that it can't access. This is on top of fighting with the gpu for bandwidth.

There's a lot more to actual performance vs benchmark performance. Benchmarks can easily be swayed by using different data sets.

 

[TechNoobForSale]

The m3 core is effectively 6 instructions wide. Yes it has 12 pipelines, but it can only feed 6 per cycle. At that rate, your memory bandwidth requirements just to feed a single m3 core fully is 4bytes per instruction x 6 pipelines x 1800 mhz = 43 GB of bandwidth. Additional clock speed is useless if you can not get data into the cpu. It can't process data that it can't access. This is on top of fighting with the gpu for bandwidth.

There's a lot more to actual performance vs benchmark performance. Benchmarks can easily be swayed by using different data sets.

Doesn't matter. It was meant to run at a certain clockspeeds, and I've seen the analysis of the very respectable Andrei Frumusanu. Pushing the M3 cores to 2.3GHz in Quad Core mode yielded incredible performance increases. And funnily enough, that is the highest frequency before diminishing performance returns happen. In line with the clockspeed. Pair that with a RAM overclock, and this system will become a beast. The M3 cores had such a wide architecture it actually bested the stock Cortex A76. I don't test phones only with benchmarks, and I don't do "Real world" tests or "speed tests" either since they are extremely unreliable. I use the best and most objective benchmarks at hand (Geekbench 5, 3DMark, GFXBench and PCMark) and games the likes of Genshin Impact, Honkai Impact, Call of Duty Mobile, Battle Prime and Asphalt 9 just to mention some. Games are the perfect example of CPU and GPU having to work together, and this phone right now doesn't perform too hot in them due to the stupidly low thermal throttling point (70°C). Now I am not an architecture rat that knows every single detail of the transistors in the processor. But I do know that there is much more to this processor than Samsung unveiled. And rising clockspeed is one of the many steps to getting the true potential of this processor. Then comes what you mentioned. It's all of this together. It's not one or the other. This is how held back this processor was. And it's about time we wake it up.

 

[pizzadox11]

Whys the front led isn't fading unlike the original version of the kernel

 

[pizzadox11]

I forgot to mention that you did a very good job overall

 

[babyboy3265]

Can I ask if this kernel can be used for N960N, thanks

Wondering the same thing.. And also if the KERNEL will function well together with NOBLE ROM 1.5?

 

[JC1126]

Wondering the same thing.. And also if the KERNEL will function well together with NOBLE ROM 1.5?

It'll not boot in Noble, coz the kernel isn't permissive afaik

 

[ykkfive]

Whys the front led isn't fading unlike the original version of the kernel

yes it is breathing, should be the same

 

[ykkfive]

Wondering the same thing.. And also if the KERNEL will function well together with NOBLE ROM 1.5?

according to this post, it works for n960n
https://xdaforums.com/t/kernel-andr...-n960f-v2-11c6-20210920.4294493/post-85591827

 

[TechNoobForSale]

On the long term (have been using my phone with 2.11c6 now for nearly a month now) the Kernel is stable and the battery life feels like it is the same as stock (I use a performance-like status where CPU is constantly at max frequency and GPU is enabled, which SHOULD consume more power when the phone is being used, yet the battery life is just the same as stock, so there might be an efficiency improvement in this Kernel). Apart from some random fast-reboots when I enable mobile data, the experience is great. So yeah the testing for this release is complete now. Waiting for the next one.

 

[ykkfive]

On the long term (have been using my phone with 2.11c6 now for nearly a month now) the Kernel is stable and the battery life feels like it is the same as stock (I use a performance-like status where CPU is constantly at max frequency and GPU is enabled, which SHOULD consume more power when the phone is being used, yet the battery life is just the same as stock, so there might be an efficiency improvement in this Kernel). Apart from some random fast-reboots when I enable mobile data, the experience is great. So yeah the testing for this release is complete now. Waiting for the next one.

yeah i find the battery last a bit longer. before, when i surfed the net for an hour, it consumed around 15%. now when i used it for about 60 min, its about 10% and 13-15% for 90 min

some random fast reboots??

 

[TechNoobForSale]

yeah i find the battery last a bit longer. before, when i surfed the net for an hour, it consumed around 15%. now when i used it for about 60 min, its about 10% and 13-15% for 90 min

some random fast reboots??

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.

 

[ykkfive]

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.

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