yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S8 & S8+ Cross Device Development] Arnz09:
I tried this already and doesn't work on codm but thanks. 😇

Where can I find the installation file of that please?
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
Can i get your CPU driver, im planning on making a kernel myself?
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
In Magisk app there is module section, just search for viper and install it.

Sure you can, just cherry-pick commits you need. If you publish the kernel here on XDA or other forums just give proper credit like "CPU .... - thanks @ace2nutzer"
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
Thanks!
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
just search at magisk app type viper that show bunch of viper choose the latest
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
OK guys I'm trying to make a new release that should fix high quality audio when using too much filters and slow screen orentation. Other than that I'm missing something else ?
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
@ace2nutzer

i don't know if this has been asked, but does it overlap/conflict if we set the kernel to performance mode but we also activate the optimized performance in the device care app?
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
No problem since it changes different things.
[Samsung Galaxy S8 & S8+ Cross Device Development] Arnz09:
There is no search option in my magisk app. There is only install from storage.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
"Optimized performance" in the settings of the phone is simply another way to say "no power saving".

As far as I'm aware there is literally nothing that the "high performance" and "optimized performance" presets change that affects performance itself. Samsung, like always, just gives fancy names to basic functions.

Power saving at least does save power, though, makes the processor scale a little more conservatively (spoiler, it's already extremely conservative even in high performance).
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
In fact it doesn't change CPU speed at all, even not with original kernel lol.

I suggest to keep "optimized" (icon disabled).
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
if there is no option to search your app is the latest magisk you need magisk23 apk
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
This is exactly why i asked, if i enable medium or maximum power saving there's this checkbox that says "limit the CPU maximum speed at 70%"

i've been using medium power saving since day 1 i use this phone and never noticed how it'd be if i put this on optimized mode lol.. but since i'm using your kernel i forgot to turn that on, so i need to reaffirm that it won't conflict this kernel's optimizations

should i keep it on optimized / high perf mode? or should i just turn it on and see? :)
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Personally I constantly am on High Performance. Since If I want power saving, I just go in Kernel settings and cap CPU frequency. Power saving mode or others are just pointless with the A2N Kernel manager. So I just keep high performance because it's probably the "most default" factory performance profile there is.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Nope, the default for max speed is "optimized" @ FHD+. If you set "high performance" then it uses higher resolution which is IMHO pointless on the phone itself, since you will not see any difference, but just reduced speed due to higher processing for higher resolution. But you can set FHD+ if you need to boost brightness of +10%. But I can't recommend it since it can burn your screen when using it for long time at max brightness.
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
How do i implement this driver? I'm not very used to work with custom drivers and there is very minimal information on the internet.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
For which device and kernel version ?

Any git repo where you want to add custom drivers ?

What do you mean by a CPU driver ?

We use here a custom CPU ondemand governor and a custom CPU DVFS driver. In addition we use also a hack for voltage control over ACPM DVFS firmware.

Anyway, of course you need some know-how. You can't just copy-paste drivers to other devices. You need to cherry-pick commits and then you need to make some adaptions to fix compile errors and to make it properly work. All the custom drivers here are almost device specific and not really generic.
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
I am building a kernel(Kolumn) for the G950F for android 12 (Lineageos 19.1) and i'm basing it off of this kernel that somehow works for android 12: https://xdaforums.com/t/kernel-q-aosp-oneui-2-r4-rad-kernel-g95x-f-n-fd.4172683/

But that particular kernel hasn't very good performance and that's why i want to use the performance mods from the a2n kernel and particularly the DVFS driver to boost the CPU performance and also whatever makes the GPU that fast but that is not as important.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
For GPU we use the same patches. (ondemand governor and DVFS thermal driver) I think you can just cherry-pick a few commits, they should apply cleanly since it's the same source code.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Love to build my own, but have 0 knowledge 😔
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Same. I'd ask Ace to give me permission to cherry pick his commits and try to adapt them to an A10 One UI 2.5 Kernel for N960F. Though I'd mainly pick the Custom DVFS driver to allow up to 100°C on GPU and CPU. However for GPU I think I'd have to come up with something new. Because it seems that E9810 devices don't have an issue applying voltage changes on GPU or CPU. They have an issue rising GPU frequencies (Basically the opposite issue that G95XX devices had). For example, you can try to apply any frequency above 598MHz on the GPU, the system will just ignore it and run 598.

Fortunately, there is one great developer working for the N960F forums, and I work with him.

My whole passion with phone modding is something that originated from the fire of intense frustration.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
You need to start from scratch.

First of all you need a great notebook with an efficient Linux distro.

I suggest to use latest lubuntu, 64bit if your CPU supports 64bit.

At least 2 - 4 GB RAM is enough for just building kernels, for building ROMs you need 16 - 32 GB RAM. After that you can start to clone (download) kernel sources and start to build a kernel without any mods, just to see if it builds and boots up on the device successful.

Hmm do you mean this developer ? - As I can see he had already cherry-picked my commits for voltage hack. Also he is trying the same way to hack/override GPU Freq limit of 598 MHz. No idea if this works, since I'd never the need to do this. Fortunately here on S8 this wasn't needed, since default Freq table already allows high enough OC.

Sure you can cherry-pick commits.

Have fun !
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Zeus Kernel? No, I know that developer though, and his Kernel too. But the issue is that I’ve never seen him show up again, and it seems his Kernel doesn’t support A10 afaik, but if it did, I’d surely be using it. I work with the developer called ykkfive.

I don’t think there is a need to hack the higher GPU frequency, because he managed to actually put in the table frequencies above 598, but for some reason the system just ignores them.

I have a Notebook with 8GB of RAM and Dual Core i5 4200U, supports 64 bits and its running Linux Mint. Is that an efficient distro?
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Upon checking better I noticed that the enforced release of this Kernel supports One UI 2.5 but I have no idea if it would work. Because I am on Alexis ROM. And while it is based on the stock rom 2.5, it has some ports from newer Samsung devices.

Well, I guess I can try. If it doesn’t go well, I can just flash my old Kernel.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Alright.

Yeah often it's not that easy. You need to grep the whole source code for "598000". If everything is already edited for higher Freq, then check this commit.

Yes, it is. You could even use zRam @ 100 %, but 8GB is already enough. In my case I use 4 GB RAM @ zRam 100 % with LZ4, basically the same driver like we use here on a2n kernel lol.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
DAMN? That commit is quite extreme. 3016MHz on the M3 cores is groundbreaking, would that be even stable?

Also I noticed it’s the same commit of the developer’s Kernel you’ve shown me before.

So that Kernel has room for some extreme overclocking.

Also I noticed that it has 839MHz GPU. Does that actually work even?

Because if it does, I’ll try to switch immediately

Hoping I don’t fcking kill my phone ☠️
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Well thing is that the E9810 has a 70C limit on the Mongoose 3 cores, and it already quite consistently reaches it at 1924MHz (OC’ed quad core frequency, N9 has really good cooling), but 2886MHz single core already does like mid 50s in temp. 3016 alone will require a LOT of power. I wonder if he raised the DVFS temp like you did. I need to look into it. Because even though I don’t know how to write a kernel, I do know how to somewhat read that commit.

I wonder why this developer didn’t post his work on XDA.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Just ask him .. but in the commit message he says "testing" ... but that could work, because he just hacked it the same way like voltage. (thanks to my idea)

Because that table is not only for voltage, but also for Freq and even PLL, but last one is more complicated and needs to know more stuff how Freq gets calculated .. then you could even play with PLL. Once you understand how PLL is coded, you can theoretically code it for 5 GHz .. but yeah of course it would never run stable, but Freq will be set !

removing this 70C limit is not hard. 9810 should have better power for voltage regulators .. so it should reach higher speed than on S8 here.

You don't need to write you own kernel, or do you want to be the Linus Torvalds 2.0 ? lol - Just download source code, edit, build and flash, that's it.

Hmm maybe because he is still working on it or it isn't stable yet.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Ace you better have not shown me the Kernel commit I was looking for but that I never found. Because this could be it. The true power of Exynos 9810…that I’ve been seeking for 4 years, ever since I discovered they strangled that SoC. I NEED this phone. A matter of self satisfaction. I’ll get a new phone soon anyways, but if I lose this one, it’ll be pure pain 🥶🥶🥶

I’ll do it…but what will be the cost? 😂😂😂

I’ll wait a little longer maybe, to see if he posts it on XDA, maybe it’s incomplete like you say. If he does, I will show my friends that I was not wrong 4 years ago. E9810 is not like 8895. It’s a chained beast. But maybe now it won’t be the case anymore.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I don’t think I have enough brainpower to be Linus 🤣🤣

But I have enough determination to show the iPhone friends I have THAT I WAS RIGHT!
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
How is the DVFS driver packaged?

As a loadable kernel module or a part of the source code?
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
It's built-in. For CPU DVFS check the cpufreq commits history. If you don't care about governor optimizations and suspend CPU Freq stuff, then you can start with commit "Disable stock DVFS and optimize". But note that you may need to make some small adaptions if you don't want to use ondemand governor.

For GPU DVFS check this commits history.

Note: cherry-pick commits always from old to new, otherwise you get merge errors.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Ace I actually had a question, if it’s even possible or relatively easy to implement.

You know how our E8895 can’t handle 2808MHz on all CPU cores due to power limitations?

Is it possible for this device to adopt the E9810 model for frequency scaling? Which is a high frequency on single core, a lower frequency on dual core, and even lower in quad core mode. Which would work according to the needs of the phone and turns off cores when going single or dual threaded, to handle the higher frequencies.

You get what I mean. Is this even possible, or does it require specific hardware support that E8895 lacks? Because if this is possible, it could yield a degree of performance improvement
[Samsung Galaxy S8 & S8+ Cross Device Development] Adbnpk2013:
can you implement voltage sliders for CPU too in the app, just like you did for GPU frequencies for undervolting purposes?
[Samsung Galaxy S8 & S8+ Cross Device Development] madhatter57:
That would be cool
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
I don't know what you mean. Power limit is by hardware, we can't force higher power in software mode.

Yes it's possible and probably I can do this by myself without to look in S9 source code. But honestly I doubt if that method is ever faster than the DVFS driver we use here. Turning off cores for just having a bit faster single core is a big pain in ass since context switching would be an overkill. Wait, is that now another Samsung mistake? Even if there you want to run a single thread app, there are still a lot of services and real-time kernel threads that want to access that CPU core as well. That means the kernel need to share 1 core for a lot of threads = very bad user experience. I tried to run 4 x little + 1 x big cores .. and the phone feels already slower when you just open an app.

No, sorry.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
It is and isn’t a mistake at the same time.

On E9810, the single core boost appears to be used especially when opening apps, game loadings and gaming in general.

In thermally constrained situations like ours, it is a nice thing to implement, but just like you said, the improvement might be way too little to be worth adding. E8890 had the same logic as E9810 too.

If implemented properly, and working with the DVFS you made, it would make the phone a bit faster in loadings and app opening. But that’s it. Since at this point we are practically at the E8895 limit, I thought this was something somewhat worth at least mentioning.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Thanks for the idea and passion to try to improve it even more.

But I really doubt the faster app opening is coming from that new driver.

App opening + game loading doesn't required real 4 core @ 100% load. Therefore it isn't not needed at all to turn off cores, simply because it isn't a problem to hold all 4 cores at max Freq without to throttle, especially if throttling start at 100°. As you can see it's a quite useless driver. Port my DVFS driver on that S9, get rid of turning off cores and then compare benchmark scores and you will see you get higher scores on both single + multi thread, 100%.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Agreed. And about the S9, Ehhh I wouldn’t bet on that one Ace. It’s a challenge that even a God like you wouldn’t be able to accomplish. Let alone me.

I’d high key bet money on it. E9810 can’t run all big cores at advertised top speed because it consistently crashes the phone + it overheats badly. Your DVFS would 100% improve multi core, but not single core if you dump single core boost.

Ironically the kernel of the developer you suggested me to look at the other day, has issues with multi core performance, while single core is fine.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yeah, exactly the same like on stock S8 kernel if you try to use higher clocks than 2314 MHz.

Nope, 1 thread @ 1 core is still slower than running 1 thread on 4 cores. Because there is more room for kernel threads and other stuff.

Having 3 cores almost low loaded or almost in IDLE doesn't increase power consumption or temperature at all, or lets say very minimal.

There is no boost at all, 4 x 2,7 GHz is still faster than 1 x 2,7 GHz ... no matter if single or multi thread. I don't see the boost I get if I turn off cores ... ?! - That way you just lower the performance and also efficiency. Yes, that would even drain more battery of course. Therefore never ever turn off cores. See on GPU there we have 20 cores. Yeah there is a reason why ... the more cores the better.

Disabling cores is a big regression for me.

Aha, well I don't know him at all. I just saw he was using voltage commits from me, that's all.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
You don’t get what I meant.

Exynos 9810 cannot handle 4x2704. Heat production is excessive and power requirement is too much for battery to handle. M3 cores are gigantic compared to the puny M2 cores in the E8895.

So to engage multi threading, E9810 drops to 4x1794 (in stock kernel, but it was meant to be 2314, then Samsung underclocked the hell out of it). 4x2314 is still much better than 1x2704. But it will never be better than 4x2704 (which is impossible to reach, to my eyes).
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
We can't hold 4x2,7Ghz as well. At least not for a few secs @ 100°C. But till it reaches 100°C we are on full 4x2,7GHz. And once it's just 95°C it allows again 4x2,7Ghz. That's our advantage that we try to use highes Freq possible as much as possible. Checks for temp happens every 8ms.

Yeah now you say it right.

On stock kernel it goes from 2314 MHz @ 1469 MHz for a while ... or something like CPU < 40°C than the stock DVFS driver removes that cpufreq lock and is allowed to use again real max of 2314 MHz. While we use more aggressive and also we don't reduce too much the freq.

Basically the custom DVFS driver increases and decreases allowed max freq like an old conservative / dynamic cpu governor, means step by step and not a forced fixed freq.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Again, the difference here is that Exynos 8895 can handle 4x2704 even though it overheats. Exynos 9810 though just can’t supply enough power for 4x2704. It will crash like E8895 4x2808.

Therefore, E9810 in custom kernels usually goes for 4x2106/4x2314 instead. Maybe even 4x2496 is possible, as Andrei Frumusanu did it, but that’s about it.

E9810 is an intricate SoC with a lot of hidden power. And nobody so far managed to master its potential, unfortunately. Frankly, it would actually take somebody as skilled as you to give it some justice. I’m just hoping that the developer of xxTR Kernel sorts out the cpu performance issue. My previous custom kernel literally performs better, despite being technically far less advanced.
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
Why is there no kernel at all that allows overclocking of the "small" cores?
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
This kernel allows to OC little CPU from 1,7GHz @ 2GHz.
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
Is that also a part of the DVFS driver?

Aah there in the a2n kernel control it is, but can you overclock those without the a2n kernel control?
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
No.

First you need to unlock the kernel with the full version, then you can set settings also over ADB. Or if you build kernel by yourself it's already unlocked then and you can use ADB.
[Samsung Galaxy S8 & S8+ Cross Device Development] Adbnpk2013:
is it not possible or the outcome will be not benificial ?
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Not much benefit i think. Also I don't know how many users still use this kernel and how many of them want CPU voltage control. Also the request was not specific, should it be only for OC Freqs ? Anyway, I'm working on new release ... maybe OC will be more stable. @TechNoobForSale I found out 2x2,8 works almost stable .... (+ 4x2,0 Ghz little) but the benefit is just 10 points+ on single thread score, multitasking is much worse then ... see screenshot. Also found new bug, when OC both CPU/GPU like hell @ 100°C then I get weird freezes in 3Dmark. Even with fully charged battery + on cable usb 2.0 500 mA. Yeah I know, that not much, but it's somehow annoying that hardware just fails here. My guess is that it needs some higher voltage for dvfs_mif + dvfs_int. Maybe you can try in the meantime ? Later I'll perform that test as well. That remembered me old times when you OC'ed your desktop PC like hell and at some point it was needed to increase northbridge chip and RAM voltage to make it stable. (Especially for FSB OC)

Also I try for the last time to OC RAM as well. Maybe we can break our own world record once again lol.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Geekbench 4 and Antutu would benefit from MIF OC. Geekbench 5 not so much. Maybe even general usage, since GPU relies on MIF for memory I think, it should improve indirectly GPU performance.

Honestly I reached hellish temperatures myself with high gpu and cpu oc but I didn’t freeze in 3DMark slingshot extreme unlimited. It is voltages. Because the higher temp goes, the higher the voltage needed to make a component stable. It’s how transistors work. My PC i7 4790K at 4.7GHz is stable at 1.3V, but if it crosses 90C, at any time, and never otherwise, it crashes.

Also currently due to summer, reaching new records will indeed be a challenge.
[Samsung Galaxy S8 & S8+ Cross Device Development] Adbnpk2013:
you are right about the usage of this kernel by users; it will be futile to go through all the trouble for no significant benefits. i was wondering if through CPU undervolting we could squeeze out a bit more battery life. perhaps you could add voltage sliders starting from base frequency 2314Mhz up to 2808Mhz for big cores and the same for little in the future if you get free time at your hands.
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
Nah i have a fridge
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Ok
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
nah i have peltier cooler + watercooling that can cool the phone at 20c at 4 min

but these day i can't do overclock because i don't have thermal paste and i have idea when i buy thermal paste i see pc easter channel ii forgot the name channel, he use diamond powder to thermal paste and mix it after that mixed and magic happen at full load cpu i3 gen 4 doesnt 't goes up no more then 50 when not use diamond powder to thermal paste that can touch 80c

diamond powder price is less then 10 buck i see on the comment section
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
You have the potential to easily outclass all of our scores. But until you fix your equipment, you can’t break records.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
@rtyuakatsuki

You could even try to use peltier element to put back some wasted battery power by the heat back to the battery, reducing power consumption.

If you try of course first check output voltage from peltier if it's ok for battery. So I guess you know what you do. Peltier element can handle up to 200°C but not permanent, permanent maybe 150°C. So DVFS 100°C should be perfect to create some power lol.
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
@ace2nutzer I implemented your driver to my kernel and it boots but refuses to overclock, have I missed some step or or something? Any ideas?