yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I don’t understand why on AnTuTu V7 GPU performance is lower too. Maybe it’s from lack of HMP, but GPU score is as low as it was on Android 8 with old drivers at 572 now
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Doesn’t look like it’s due to CPU. GPU is just about 10% slower in any AnTuTu workload at 572. Now I need 683 to keep up (86,000 vs 92,000). Probably it’s because MIF is no longer at max frequency while running the GPU benchmark, because cpu is at low frequency. Maybe it’s also due to disabled shader cores hotplugging
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
Yes same like @TechNoobForSale

The perfomance get slow down

Especially when booting up

The phone so laggy for some user have 4 social media apps
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
We wait. R62 will fix all of this
[Samsung Galaxy S8 & S8+ Cross Device Development] TeKeyTech:
It would be a godsend to add this feature because my poor s8 is flickering nonstop at low brightness but I still don't want to let this device go because it's got good specs and performance
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
Use pwmfree app bro it will fix it for you
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Well then there is no need to add a workaround in kernel for some broken screens, if that really works, because it'll drain more battery without PWM. lol
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
Hmmmm i am not sure for that dev because i habe been use pwmfree app maybe like 4 month and there is no battery drain and tge fact is my battery is fine still get 4h sot for social media acrivity using default settings
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
Is your app open source? If not are you planning to open source it when this kernel reaches EOL? I could use some stuff like sysfs paths and controlling your dvfs driver that I'm implementing from it.
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
If there is really no drawbacks, then I will add it to my kernel ig. Also morosound is included ad you requested.
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
Nice buy i've been sell my s8 plus :) and now i use lg v50 but soon i will buy again s8 plus i hope i can be so luck get best silicon yo get stable at highest peak freq of gpu
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
I dont think ace will make his app sources public. Its a a2n full app is payed after all so yea, reason are obvious.
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
But this kernel has almost reached EOL so it is more reasonable than before EOL.
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
Nope 8895 still have some magic there dev always see some chance to improve time to timw this phone
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
There is always room for improvement, especially in software. But I thought ace stated he would stop updating this project soon.
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
If he still use s8 and it will be update

Major or minor
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
Well, this kernel is awesome so I hope he does not quit.
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
I guess he will not quit except there is no room to improve but dev still figuring out how to overlock ram freq it can be improve s8 on par with s9
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
R62 soon online, with bug fixes and improvements.

And R63 maybe one day with RAM OC 1,80 @ 2,10 GHz.
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
RAM OC? This is too good to be true

Edit: But shouldn't ddr4x be able to handle a lot more than 1.8 ghz?
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I don’t know. Other than MIF OC, I don’t see much room for better performance anymore. We must remember that E8895 like all Exynos has very bad BSP and in the end that affects our experience under any aspect. It would take a superdeveloper to unleash the theoretical potential of most Android phones out there (Making drivers and software from literally scratch). Ace can only do so much, and he already did it all and then some more.

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.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Ace won’t stop until he gets that working ☠️☠️☠️ It got personal. That would be the nail in the coffin for my 9810 lmfao

A very important note is that I predict a MIF overclock to increase GPU performance noticeably in some workloads. Our GPU has about 18GB/a of bandwidth out of the total system 28GB/s. In modern games and some benchmarks, this is a major limitation and in fact 839MHz does little benefit in front of a bandwidth limitation.

Also ace don’t forget about bringing heterogeneous mp and little cores hotplug back plz
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I did see phones pushing LPDDR4X higher so it’s definitely possible.
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
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.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
That would still suffice.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
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.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Ooo spicy

Ace is unstoppable. He is now the S8Nutzer
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Time to benchmark. I'll run Geekbench 5 to inaugurate the new upcoming Kernel version :cowboy:

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.
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
My phone has been sold out hoho
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Now nobody can compete with me 🧨🧨
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
Haha i have a lighter os. But it will take years to get a good enough kernel :cry:
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
Meh -_- i am on 855 now but soon i will take note tho and fully watercooling it
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
U still can’t compete. Lighter OS won’t help you with throttling 🧨
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
My fridge will 🧨
[Samsung Galaxy S8 & S8+ Cross Device Development] 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?
[Samsung Galaxy S8 & S8+ Cross Device Development] 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.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
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.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
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
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
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.
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
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
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
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 🤣
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Peltier creates water, you will **** up your SoC
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Managed to max out big and little cpu freq but gpu min frequency refuses to stick to 572000 lmao
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
You need to enable GPU always on in A2N app, then it's static 572 MHz if you set min freq like max freq.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I already did it but min freq reverts back to 260000 when I try to change it. Maybe it’s because I have boost on? But I don’t think so at all. Maybe script for gpu is different
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Post your script.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I didn't make a script since I have no clue how to do one. I explored files a little and found User freq limit files in CPU policy 0 and 4 and set those to the frequency I wanted. It worked for CPU but doesn't for GPU.

Can't get 839MHz stable on AnTuTu V7 for GPU no matter what I try lol. Went up to 860mV and it still didn't work, so I don't think it's going to. 839MHz is very situational. 764MHz works in vast majority of the cases
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
You need to use user_min_clock, not gpu_min_clock.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Yeah I know but it refuses to edit it. Says that there was an error saving the changes. Maybe I’ll just look into it tomorrow
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Are you trying to edit a sysfs interface with a root explorer using a text editor?
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
Put some right voltages and make no water done there is much insulation to do that
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
Wait really you edit it with text editor ?
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Well it worked for the CPU so 🤣🤣
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Hmm never heard that this method works. Maybe it's a very smart editor and did actually understand that it's a kernel interface and you wanted to do "echo 572000 > user_min_clock".

So did you check with a CPU app and the Freq was really at max for at least 30 sec? Because I don't think that it really worked out.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Yet it actually worked. Yes I did make sure. However for GPU it did not work. However it allows me to edit gpu min freq (not user min freq) but after the edit it reverts back to default. I’ll record lol
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Alright, pretty strange.

As for gpu_min_freq: it has no effect, it shows only the value from user_min_freq to make the ROM or lets say the stock DVFS happy. lol
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
For evidence here you go. I show that it works for CPU, but not for GPU. Maybe they work different.

Also, you can say very strange. But plz DONT change this. It's my only way of emulating a performance governor, you know since I'm a noob even with Terminal.

😔
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Took a long while to upload
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Well, that's really cool, I didn't know that.

As for user_min_clock, I didn't try it (yes I've the same root explorer) but I think that works as well, just delete everything and write only the freq to the interface. This is also the way how it works over script, we write only the freq into it, so without the info-text.

Note: the GPU governor doesn't really like to have (min_freq == max_freq). That means it could trigger a random reboot!
[Samsung Galaxy S8 & S8+ Cross Device Development] opensourcefreak:
What governor?
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Our default ondemand gov by me.

btw: maybe I can fix it, when I've more free time.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Thank you. Well to appeal to the GPU governor I could simply put min freq to something close to max. Maybe 455MHz.

You may say this is a battery powered device and needs power saving and other stuff. But you know by now I'm a performance freak lol. I treat my phones like I treat a PC. All MAX (Within cooling limits).
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yes this works, but honestly this won't make it better than keeping the default of 260 MHz.

A smaller min_freq will cause to switch to max_freq (if boost is enabled) sooner, because it'll trigger the up_threshold sooner.

A bigger min_freq can handle more load and therefore it'll stay longer time at min_freq.

Just enable CPU/GPU boost and enable GPU always on.

This is already enough to make games smoother. (and increasing DVFS temp of course)

To make it really better it would require to adapt the algorithm, such as up and down thresholds.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Yea that's what I currently have going anyway. It works fine. Your DVFS actually does its job of scaling with load properly in games. Unfortunately I'm traumatized by Samsung's atrocious 94% high-speed GPU threshold on default DVFS (at least on 9810). So I'd rather keep frequency at max much like on a PC to escape the Samsung curse in games :ROFLMAO:
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
You need to set stock freq in ramdisk like this:

on early-init
# set stock max_freq
# BIG
write /sys/devices/system/cpu/cpufreq/policy4/user_scaling_max_freq 2314000
# LIT
write /sys/devices/system/cpu/cpufreq/policy0/user_scaling_max_freq 1690000

;)
[Samsung Galaxy S8 & S8+ Cross Device Development] leonidasZ953:
Any news for R62 mate?? ✌😎
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
It’s finished. They are bug testing
[Samsung Galaxy S8 & S8+ Cross Device Development] Ian095:
Interested in this though was wondering, this specifically is to be used with the stock Android 9, OneUI 1.0? Suppose you cannot install a custom rom potentially based on Android 9 build Samsung has, if that even exists?

I'm using a SM-G955F, has issues with displaying notifications, must have difficulties clearing ram properly as apps often have to reload and often lose my place on an app due to this. Hoping this kernal would resolve those issues? Though I like using good lock to customise things as well, so try to stay on Samsungs build.
[Samsung Galaxy S8 & S8+ Cross Device Development] george343456:
can you give G955X release? I want to test stability
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Hi, it works on every Android 9 ROM that you can find for S8/S8+/Note8 phone.

Yes this kernel has much better RAM management than stock kernel.

But I suggest to wait for R62 which will be released in 3 (or more) days.

No sorry, i've already a tester for S8.

Please wait for R62, it'll work very well and likely we will breake our own world record once again.

So get prepared guys!

@TechNoobForSale

Is it really so funny? - You don't believe it? :D
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Lmao Antutu V7 for CPU at STOCK freq made Ace’s DVFS fail. @ace2nutzer

Went from 79C to 106C in a split second and then phone shutdown. It heat up faster than DVFS could read (This is wrong)
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Its not that I don’t believe it. You always surprise me. In a good way. If it actually improves scores even more, I’m all for it…though I was making such a good run and DVFS failed and ruined it….

Unless it happened because min freq is set as 2314. But I doubt it. Throttling should override that (turns out this is right)
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Confirmed. Setting user minimum at 2314/1690 basically disables throttling

Holy **** this means the phone crossed 110C before forcing itself off
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
No idea what was the issue, but if the phone was shutting down, then you touched 110 °C, otherwise it rebooted just due to miscalculations, so unstable freq or volt.

Anyway, I'm reworking the whole DVFS for CPU/GPU.

New release will have a big boost.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
No it was my fault, let me explain.

Apparently setting user min freq impacts throttling. So if you set 1703 as min for example, cpu can NEVER go below that, even if it reach throttling 100C threshold. It can’t be overrided in fact now that I dropped min, it ran stable. It’s insane how hot stock frequency runs. It would surpass 120C if left unchecked. Such bad cooling from Samsung
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Hmm, well that's really strange. Normally it shouldn't happen.

I only test the driver by running min_freq as stock.

And yes that's right, stock freqs without a DVFS throttling kernel-thread will go over 120 °C and reboot due too miscalculations by too much heat.

But up to max 115 °C it can run stable. New driver will power off @ 115 °C. In my case without any limits it reboots @ 118 °C. So that's why I set 115 °C shutdown temp in order to be able to perform a clean shutdown.

Otherwise it can cause filesystem corruption.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Are you sure these temps are relatively safe? They seem extremely high
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
See here on stock kernel source. It's for CPU/GPU max 115 °C allowed.

That's why the phone feels pretty hot with the stock kernel.

Also with the stock kernel we get 1694 multi-core score in geekbench.

Such high score is only possible if you keep the CPU all the time @ 100 °C while benching. Temps over 100 °C are in both A2N and stock kernel only peeks for a few ms, that's why it's "safe".

But you're right, 115 °C is too close on ☠️.

I'll revert to 110 °C for shutdown temp.

And yes, we'll still break the record. :ROFLMAO:
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
If only we had good references for what these SoCs are capable of. But OEMs never disclose anything. Like how much is too much for voltage for each component of the chip, how much is too hot, and so on. E9810 GPU OC was unlocked but it requires higher voltages than E8895 did, and it leaves me confused.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Well that's not hard to find out.

For mobile CPU (my old Intel core duo) has a Tjmax of 100 °C (official stated by Intel) and for our SoC it's likely the same since it reboots at 118 °C. Also such temp sensors my have a tolerance of + - 5 %. E.g. a Intel i7 with 10 nm like our E8895 has also Tjmax 100 °C. Reference see here.

Also each core has a sensor, so we have 4 different temp values for our big CPU. The interesting thing in source code is that we can configure to use: min, avg or max temp value.

I've set it to "max" to be safe, so to not overheat other cores. (Same for GPU)

Also good to know: the difference between cores on the same CPU can be up to 10 °C.

Oh cool! Can you show me the repo? It could help for RAM OC on E8895.