[KERNEL] [A.9] A2N Kernel for Galaxy S8/S8+/Note8 (Exynos) [CPU/GPU OC/UV] [Charger Control] [Thermal Control] [R62]

[TechNoobForSale]

My pc has LPDDR4 and I did an oc to get it from 2666mhz to a tiny bit less than 3000 so yea. But just to be noted here: LPDDR4X is the memory interface, not the speed or quality of the actual ram dies and this is getting pretty old so I would not be suprised if the memory caps out at something like 2000 mhz.

That would still suffice.

 

[ace2nutzer]

......

What concerns me is what happens when kernel actually reaches EOL. What will be of the app? Will it keep working? Will it die? This is a Kernel I paid for so at least I’d like to keep its functions.

I'm still using my S8. You don't need to worry about EOL. I'll keep this kernel and app alive as long as possible. R62 is ready and actually we are testing the stability.

If someone want a preview of R62 can test the attached kernel for S8.

 

[TechNoobForSale]

I'm still using my S8. You don't need to worry about EOL. I'll keep this kernel and app alive as long as possible. R62 is ready and actually we are testing the stability.

If someone want a preview of R62 can test the attached kernel for S8.

Ooo spicy

Ace is unstoppable. He is now the S8Nutzer

 

[TechNoobForSale]

Time to benchmark. I'll run Geekbench 5 to inaugurate the new upcoming Kernel version

For the time being I'll patiently wait for the return of Game Mode and Little Cores hotplug. I need to test AnTuTu V7 and 3DMark too, to verify if GPU performance is back to normal.

 

[rtyuakatsuki]

Time to benchmark. I'll run Geekbench 5 to inaugurate the new upcoming Kernel version

For the time being I'll patiently wait for the return of Game Mode and Little Cores hotplug. I need to test AnTuTu V7 and 3DMark too, to verify if GPU performance is back to normal.

My phone has been sold out hoho

 

[TechNoobForSale]

My phone has been sold out hoho

Now nobody can compete with me

 

[opensourcefreak]

Now nobody can compete with me

Haha i have a lighter os. But it will take years to get a good enough kernel

 

[rtyuakatsuki]

Now nobody can compete with me

Meh -_- i am on 855 now but soon i will take note tho and fully watercooling it

 

[TechNoobForSale]

Haha i have a lighter os. But it will take years to get a good enough kernel

U still can’t compete. Lighter OS won’t help you with throttling

 

[opensourcefreak]

My fridge will

 

[opensourcefreak]

@ace2nutzer ehm, this is my first time doing a kernel and I have this annoying issue that I can't find an answer to by googleing my device does a pretty massive oc on bootup and crashes pretty quickly as a result. I'm guessing you dong have this issue?

 

[TechNoobForSale]

Maybe a thing that Ace could do to slightly improve UX experience on this E8895 is to implement hotplugging mechanism similar to what is seen on E9810. But that might not be worth it and would only help a few benchmarks. Also would need to be meticulously well tuned in order to properly use boost frequencies for exampel when opening an app.

 

[ace2nutzer]

@ace2nutzer ehm, this is my first time doing a kernel and I have this annoying issue that I can't find an answer to by googleing my device does a pretty massive oc on bootup and crashes pretty quickly as a result. I'm guessing you dong have this issue?

Sorry, but I've no longer the time for teaching newcomer developers.

Maybe a thing that Ace could do to slightly improve UX experience on this E8895 is to implement hotplugging mechanism similar to what is seen on E9810. But that might not be worth it and would only help a few benchmarks. Also would need to be meticulously well tuned in order to properly use boost frequencies for exampel when opening an app.

Nope, the current algorithm is already fine.
When you open an app it'll be moved to big CPU and all 4 cores are at max_freq for 1 or 2 secs. I don't see the reason why it should improve speed by hotplugging cores. And this works even without "CPU boost (incl. input booster)" enabled.

 

[TechNoobForSale]

Sorry, but I've no longer the time for teaching newcomer developers.



Nope, the current algorithm is already fine.
When you open an app it'll be moved to big CPU and all 4 cores are at max_freq for 1 or 2 secs. I don't see the reason why it should improve speed by hotplugging cores. And this works even without "CPU boost (incl. input booster)" enabled.

But is the workload of the app opening spread evently across all 4 Big cores or is it depending from the app? Because if it depends on the app, an app that relies on single thread from opening would benefit from 1 of the 4 Big Cores hotplugging to 2808MHz for example.

If task is shared across cores makes me wonder why E9810 has an hotplug mechanism in the first place. Maybe **** Samsung software as always

Either way I hope Little core hotplug and game mode come back soon. Game mode is essentially the best for performance. A fixed frequency is always better for performance than an algorithm that scales. No matter how fast and efficient. It's like comparing a car that has gas pedal constantly pressed vs a car with a driver that only accelerates when needed

 

[ace2nutzer]

But is the workload of the app opening spread evently across all 4 Big cores or is it depending from the app? Because if it depends on the app, an app that relies on single thread from opening would benefit from 1 of the 4 Big Cores hotplugging to 2808MHz for example.

It doesn't matter at all. The more cores you have ready for a process, the more faster the app will appear. You can test yourself, even if you hotplug only one core from the big CPU, you will already notice that everything will be slightly slower (no matter what you do with the phone), but never ever faster my friend.
Because it's never just one thread = 1 core. There are always tasks from the ROM and kernel backend that are required to make the app open.

If task is shared across cores makes me wonder why E9810 has an hotplug mechanism in the first place. Maybe **** Samsung software as always

The kernel has a CPU scheduler that tries to balance load on all available cores, at least on the same CPU. This is to improve performance and efficiency. Hotplugging cores is never a good idea.
Even if only 2 cores are actually loaded at 100 % and the other 2 are loaded at 5 % each others .. then it's not a big problem to keep them running at max_freq .. because a core that's not loaded at 100 % will never cause too much heat. Also it's not possible to run any core with different clock from the others on the same CPU domain. So if you hotplug them, then the other 2 cores that was already loaded at 100 %, will need to serve the tasks from the other 2 cores .. so in the end performance drops at 90 % (minus 2 x 5 %). And this is by hotplugging 2 cores from the same CPU. Oh chit!, next painful problem: it doesn't even save much battery, because it's not possible to power off some cores without to power off the whole CPU. They are only offline, but still powered up.
As you can see, there is almost no advantage on doing so.

Either way I hope Little core hotplug and game mode come back soon.

You mean big cores hotplugging. I had to remove this feature because the power consumption just increases instead to decrease. Test case was to measure the power consumption while streaming music over wi-fi with screen OFF. One time normal and one time with big cores offlined. Therefore ....

Game mode is essentially the best for performance. A fixed frequency is always better for performance than an algorithm that scales. No matter how fast and efficient. It's like comparing a car that has gas pedal constantly pressed vs a car with a driver that only accelerates when needed

Yeah I agree with you, but it's actually a battery powered phone and not a PlayStation with constant power.
Anyways, a real gaming mode doesn't required kernel support at all.
You can write a simple script that uses same min_freq as max_freq for CPU and GPU. This will keep RAM as well at max_freq.
Just put this script to your homescreen and then use an app like SMANAGER or TASKER to run the script or even to automatize the process.

 

[rtyuakatsuki]

Yeah I agree with you, but it's actually a battery powered phone and not a PlayStation with constant power.
Anyways, a real gaming mode doesn't required kernel support at all.
You can write a simple script that uses same min_freq as max_freq for CPU and GPU. This will keep RAM as well at max_freq.
Just put this script to your homescreen and then use an app like SMANAGER or TASKER to run the script or even to automatize the process.

This is will be my next project using s8 for mining crypto direct peltier to the SOC it must be no throttling at all must hmmmmm soon i will find cheap mobo s8 hehe

And you @TechNoobForSale
My benchmark will be in world recors

 

[TechNoobForSale]

It doesn't matter at all. The more cores you have ready for a process, the more faster the app will appear. You can test yourself, even if you hotplug only one core from the big CPU, you will already notice that everything will be slightly slower (no matter what you do with the phone), but never ever faster my friend.
Because it's never just one thread = 1 core. There are always tasks from the ROM and kernel backend that are required to make the app open.



The kernel has a CPU scheduler that tries to balance load on all available cores, at least on the same CPU. This is to improve performance and efficiency. Hotplugging cores is never a good idea.
Even if only 2 cores are actually loaded at 100 % and the other 2 are loaded at 5 % each others .. then it's not a big problem to keep them running at max_freq .. because a core that's not loaded at 100 % will never cause too much heat. Also it's not possible to run any core with different clock from the others on the same CPU domain. So if you hotplug them, then the other 2 cores that was already loaded at 100 %, will need to serve the tasks from the other 2 cores .. so in the end performance drops at 90 % (minus 2 x 5 %). And this is by hotplugging 2 cores from the same CPU. Oh chit!, next painful problem: it doesn't even save much battery, because it's not possible to power off some cores without to power off the whole CPU. They are only offline, but still powered up.
As you can see, there is almost no advantage on doing so.



You mean big cores hotplugging. I had to remove this feature because the power consumption just increases instead to decrease. Test case was to measure the power consumption while streaming music over wi-fi with screen OFF. One time normal and one time with big cores offlined. Therefore ....



Yeah I agree with you, but it's actually a battery powered phone and not a PlayStation with constant power.
Anyways, a real gaming mode doesn't required kernel support at all.
You can write a simple script that uses same min_freq as max_freq for CPU and GPU. This will keep RAM as well at max_freq.
Just put this script to your homescreen and then use an app like SMANAGER or TASKER to run the script or even to automatize the process.

I can tell already that if Ace ever worked on Exynos 9810 devices, first thing he will kill off is cpu single/dual/triple core load frequency hotplug lmfao. Anyway thank you for the informations

Hotplug in some cases can be useful in my experience, but it’s far from the most efficient strategy. Meanwhile you look to do everything perfect as always. I think it’s good this way

 

[TechNoobForSale]

This is will be my next project using s8 for mining crypto direct peltier to the SOC it must be no throttling at all must hmmmmm soon i will find cheap mobo s8 hehe

And you @TechNoobForSale
My benchmark will be in world recors

Peltier creates water, you will **** up your SoC

 

[TechNoobForSale]

Managed to max out big and little cpu freq but gpu min frequency refuses to stick to 572000 lmao

 

[ace2nutzer]

Managed to max out big and little cpu freq but gpu min frequency refuses to stick to 572000 lmao

You need to enable GPU always on in A2N app, then it's static 572 MHz if you set min freq like max freq.