yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Mongoose is the big CPU and Apollo is the little CPU. But AFAIK the little doesn't have temp sensor, because it doesn't cause much heat.

Write "1" to cpu_dvfs_debug, then set 95°C and run Geekbench 5... after that check cpu_dvfs_max_temp .. there you can see all configured temps for big CPU. There is also a peak_temp.

Note: if the benchmark just crashes it means the freq was too high.

While if it reboots while bench is over 50% means all 8 cores runs at 100%, then it means DVFS driver failed and reboot caused by hardware overheat protection. Otherwise if it hits the shutdown temp then it'll cleanly shutdown. In that case you should report this and use a lower temp like 90°C. Geekbench up to 50% level runs only 1 big core at 100%. While over 50% like a said all 4 cores plus all 4 little cores. Therefore it's likely to crash over 50% because it's likely that just one core of the 4 cores will do some miscalculation. To fix this you could try to find out which core actually fails and exclude him or them ... then you could run 2,7 or 2,8 GHz stable with 3 or only 2 cores. But it doesn't make much sense ... because you get better performance with all 4 cores at some lower freq. For hardcore tuning maybe useful if you have a task that is just single threaded and you need max speed.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I am starting to suspect that it's simply the overheat protection reboot kicking in. I know very well that at over 50%, Geekbench starts to test multi core. And at 88%, the most intensive test begins. There probably are no CPU miscalculations at up to 2704MHz (Miscalculations are easy to identify. The phone just locks up and you need to force reboot, unlike overheat protection, which reboots abruptly), because my ASV level is higher than my friend's ASV 6 on big CPUs and he can run 2704MHz more stable than me. The catch being that he has an S8+ while I have a regular S8. He can dissipate heat far faster than my phone due to chassis size difference.

Running CPU throttling test at 2574MHz and 95°C CPU DVFS, the CPU still throttled very damn hard. Down to 2157-2002MHz. At once it even reached 98°C, and that's basically 2°C off the overheat protection kicking in.

The Exynos 8895 apparently runs very hot. But this might be the cooling system's fault. It's a single heat pipe and it's embarassingly small. My N960F has no such issue on CPU throttling test, and it's modified and overclocked too. Never exceeds 68°C on CPU only load. It's very odd that developers on the Exynos 9810 managed to hack (or at least so it seems) the voltage table and undervolt the entire SoC, while S8's voltage table is still locked to everybody. Undervolt would help this SoC big time, especially for who plans to only use the frequencies available on stock.

GPU runs pretty hot too, but not as hot as the CPU. Nowhere near as hot.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Are you sure it's rebooting due to too high temp ? If so you should report this with last_kmsg. Because this should never happen with the new DVFS driver. Use latest kernel. Check screenshot.

Basically the logic is:

You set CPU DVFS max temp 95°C.

If temp is over 95 it'll reduce cpu freq by one step. If it's still over 95 after the next check which is every 8ms ... (but it can be maybe longer since kthread sleeps every 8ms in order to not block all the time 1 CPU core for only DVFS driver) the again one step down ... once temp is under a threshold it'll go one step higher.. and so on till it reaches agai the user max freq. This works very well with stock freq 2314 MHz. But with higher freqs the temp jumps very fast and it's possible that the temp goes over 115°C and phone will reboot by hardware protection. (No shutdown!)

Tjmax 100 is only the official max allowed temp where the manufacturer tells you up to this temp it's safe and stable.

Avoid shutdown temp 105 .. means at this tenp the freq will be set to the lowest 741 MHz to try to avoid shutdown or even reboot. Performance drop is still better than a reboot. Then shutdown temp is 110 .. if the previous protection failed because of OC ... then it'll shutdown at 110. If even this fails, it'll reboot once it hits 115 or even 120°C !.

Both, shutdown or even reboot should never happen and i consider this as a software bug, not hardware failure. In my case it doesn't happen to shutdown or reboot at 95° 2,7ghz + 1,9ghz and GPU to 572 MHz as well 95°C max. I can pass Geekbench, 3D mark and antutu 3d mark without any issues.

Same logic for GPU.
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
Hmmm i f you think that caused by temp i have some suggestion for you

I have been mod thermal cpu on my phone instead usinh thermal pad i use alumunium plate maybe the thick is +- 2 or 4mm and you use thermal paste that will make your phone better but remember when modding your thermal paste be sure look at left of processor there is a sensor i think some little styrofoam you must make them have same height and same pressure to make the thermal sensor have correct temp
[Samsung Galaxy S8 & S8+ Cross Device Development] incognitonk:
The multitasking performance is very bad with the 12-15 kernel. The phone cannot keep two apps in memory at the same time like messenger and instagram. Apps are also much slower to start than before.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Don't worry, it'll be all fixed in next build. (Today)
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Unfortunately I don’t have what it takes to commit such a replacement, as I don’t have the tools to remove that damned back of the phone. That’s why I have workarounds for it. I keep the phone as cool as possible by using a Funcooler Pro with low ambient temperature to my advantage. Unfortunately this approach can potentially be detrimental to the battery, but it’s the only one I have that works, and it allowed me to pass Geekbench 5 at 2654MHz instead of 2574MHz. 2704MHz still was unsuccessful. 2808MHz was an instant system freeze. Despite all of this though, I would be getting record breaking results even at 2574MHz CPU and 572MHz GPU if only ace allowed the user to tune scaling to his liking and totally disable DVFS. He underestimates the usefulness of MIN FREQ in both games and benchmarks (especially games). I know that there is no Ill intent though, because his clever frequency scaling improves UX performance DRAMATICALLY (around 43%) compared to stock, while having a FAR better idle battery life. But if there’s scaling, there’s stutter, and that’s a rule in games. They are better played at one frequency. He placed immense amounts of effort to reduce the time that it takes the CPU to go from min to max to only 10ms (in comparison, a stock Exynos 9810 takes 400ms). But that’s good for daily usage. Games and benchmarks will perform worse because of that. They expect the highest (or at least one frequency) to be used before the scaling even has the opportunity to realize “oh this app needs more juice”.

I am not asking Ace to redo everything. I am just asking to give users the kind of freedom you’d expect the masses to want. Why does the on demand governor only allow me to go down to 40% as a threshold to use the maximum frequency? Why can I not put it to 10% or less through the app? Why can’t I tune minimum frequencies? DVFS in this case NEEDS to stay on, so I don’t criticize the removal of the chance to disable it, since apparently this 8895 overheats dramatically fast, but either way, this kind of freedom would allow users who want performance alone at the cost of battery life (me, for instance) to thrive! For now it’s just battery life guys friendly.

Either way this is a temp issue. It’s hardware. He can’t solve it. I have to.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Can’t use latest pre release kernel. I had a very negative experience with it. I’ll wait next actual release and test.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I will now run Geekbench 5 on 2,7+1,9. I most likely expect the phone to shut down due to overheat protection. In that case, I don’t know if there will be a last_kmsg. Maybe it could also reboot due to overheating. We will see. Kernel version is 06 12 as it’s the best performer for me.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
last_kmsg of a freeze + reboot at 2704MHz Mongoose and 1898MHz Apollo (Crash due to Mongoose). last_kmsg scenario was in normal usage right after boot, opening a random app. Geekbench 5 crashes in the same way at 53% (freeze + reboot), so I believe the last_kmsg would be the same for both cases. Kernel version is 06 12. I am not using 15 12. Bad experience. If you could tell me if it's due to temperatures or a CPU instability, I'd appreciate a lot.

Though if it's a CPU instability, I'd think it's safe to assume that the ASV table is a joke.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Set GPU DVFS to 95°C, is like having it disabled. Because in my bench tests, peak_temp was never higher than 85°C for GPU.

Lowest up_threshold + GPU Boost enabled. With that config GPU will run most of the time at max_freq. If you see lags, it's likely not caused by GPU, but rather from CPU DVFS throttling or RAM was too full, or it has to actually compress RAM.

SO you can have higher speed if DVFS for CPU doesn't kick in, but like the other user being said, you need proper cooling system. Everything else is quite nonsense to discuss. it's like you said, chassis is very small and just paasive cooling system.

Not the best. Just don't forget it's a damn phone with stunning performance and features. It's NOT a hardcore gaming console.

It causes bad performance if it's too low.

If it's too low, i'll switch freq too often, causing bad performance. Optimal is 45%.

Those tunables are already very well calculated by me and adapted to this phone. It's not copied from other kernels without ot test. If you want the gov to check load and switch freq more faster, you could tune sampling_rate.

Test yourself what works best.

Kernel default is 40000 (40ms) you can set it lower up to "sampling_rate_min" (8ms). But same problem, it'll make CPU idle very bad and freq will switch like crazy between min_freq and max_freq. But try yourself.

e.g.

set to 20 ms:

echo 20000 > sampling_rate

Because it serves nothing.

Having min_freq low, will switch more aggressively and faster to max_freq. If you increase min_freq it'll stay more time to min_freq even if you reduce up_threshold. Also it drains more battery, but i know you don't care.

CPU freq scaling with min_freq and max_freq has nothing to do with DVFS. DVFS uses pm_qos locks over CPU scaling.

My DVFS driver didn't fail, also not caused by too high temp. Reboot caused by kernel panic. (memory management issues) Wait for new build, it should fix it.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Hold it. You're telling me the reboots are not being caused by CPU or temperatures, but by the memory issue everybody is complaining about? 😕

Odd. This doesn't happen at 2574MHz.

Also who cares the phone would stay more at the minimum frequency if I raised it? I don't want to raise it a little bit.

I'd like to make it the same as the maximum stock frequency, or higher, if I feel like it 😂.

Yes. I am that fixated with performance.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yes. For nearly 1 year ...

But finally i found out what is the problem.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
I wonder what it causes
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Hypothetically, if even that doesn't fix the crashes at 2704MHz when benchmarking, I'll send another last_kmsg. I need to see this through.
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
Crash at high freq caused by the VRM on motherboard it can't give much power to the chipset and go shutdown forcely

I had 0 voltage at gpu if more then 572mhz

And got shutdown if more then that if you want to use 2,7 ghz cpu use charger and cooler make the phone cool first and try for me that work 2,7 with little throttling to 2,3 ghz and raise up to 2,6 stable at a second now if you want extreme performance no throttling teardown you phone and take the board use big or small heatsink or you can use peltier same like i use peltier to cool my phone and got 16°c just for 10 min or less depends how much volt i give to cooling system

Edit:

Of course use SAMSUNG DEX mirroring the screen use mouse and keyboard voila android mini pc the most powerfull OC chipset
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
GPU frequencies above 572MHz are 0mV because they simply have no voltage assigned. That's it. Once Ace hacks the ASV table, he will be able to tune it. Also I doubt it's a power issue. Most modern devices will throttle their performance down as much as possible in case of insufficient power delivered to the processor. In this case, it just shuts down. It shuts down at 2704MHz even in UX experience, which should require not a lot of energy despite the high frequency. Samsung DEX uses a lot of resources, therefore I won't use it as it will signfiicantly hinder benchmark and gaming experience. I have a Funcooler Pro, which is a thermoelectric cooler pad that can cool my phone's chassis down to 12°C (battery suffers at that temperature) and it's what I use for my benchmarks. 2574MHz is rock stable but I still got one random reboot, due to Kernel Panic, I suppose. Besides, how would 2574MHz be stable but 2652MHz be unstable if it's just a less than 4% higher clockspeed? Are these frequencies THAT inefficient compared to stock 2314MHz? I don't think so.

If it will crash again, I'll send a last_kmsg to Ace so he can see if it's because of what you suspect or because of the Kernel Panic, or because of general OC instability, which should be extremely unlikely, as many S8s should be able to pull 2652MHz or higher.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Either way, thanks to Ace's efforts to make S8 great, we reached the ballpark of the Exynos S9. We are not quite there fully yet, but we are in the lower average side, which is a gigantic victory. Ace makes miracles, really.

The following benchmarks have been conducted on Alexis ROM 9.3 and A2N Kernel 0612 and ext4 file system on all partitions. Mongoose at 2574MHz, Apollo at 1898MHz and GPU at 572MHz. No ZRAM (performance drop). Actively cooled. G950F.​
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
So basically apart from a few defeats, we are pretty much on par with an S9. And this is at 2574MHz, not even 2704MHz like many other people can sustain.

Geekbench 5:

G960F (Average, reported by Nanoreview):

Single: 562

Multi: 1812

G950F (This):

Single: 430

Multi: 1800

On par where it counts.

AnTuTu V9:

G960F (Average, reported by Nanoreview): 312,869

G950F (This): 338,590 (There's potential to go >340,000)

Icestorm Unlimited scores for G950F are unknown.

Slingshot Unlimited:

G960F (Average reported by UL Benchmarks): 4016

G950F (This): 4131

Slingshot Extreme Unlimited (Unlimited, not regular):

G960F (Average, reported by UL Benchmarks): 3605

G950F (This): 3242

PCMark, Work 3.0:

G960F (Average, reported by UL Benchmarks): 6257

G950F (This): 8251 (Dramatically better User Experience when doing daily tasks)

GFXBench 5 won't be compared as the official site does not report the offscreen results. So it's up to people to compare.

PCMark, Storage 2.0:

G960F (Average, reported by UL Benchmarks): 7149

G960F (This): 8620

Pretty neat overall, huh? Ace is better than a whole paid team of phone software developers. Unironically. He's paid too, but I'd buy his software over and over again. It's a warranty.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
I agree, the normal dev team are hired brainless monkeys, ace is a mastermind compared to them. Also neat the performance with this kernel beats the s9 with a s8😄
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Ace is HIGHKEY somebody from another planet. There is actual effort, calculations, time and research spent into this Kernel. If ONE developer asking for donations to go on can push a phone to the next generation level but a whole team can't, it should make you think, about the current state of phones.

If this dude got the hands on an S9,S9+ or Note9, he'd slay an Exynos 9820, I ASSURE YOU. Because the Exynos 9810 is an SoC that has been VERY strongly held back by Samsung, and it deserves far more love and attention from the community compared to what it gets.

I don't know Ace's future plans, but if he happens to get his hands on a device that out of pure coincidence I already own, and he decides to develop on it, my hand will be already at my wallet.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
By plugging my S8 in, I manage to get a stable overclock to 2652MHz. 2704MHz still crashed, and it really looked like a CPU crash. 2652MHz passed AnTuTu and gave me a slightly higher score. Maybe if it still was due to Kernel panic, the next release will fix it.
[Samsung Galaxy S8 & S8+ Cross Device Development] Grainroot:
yes i agree with you very much
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
The only thing that makes me sad is that the smaller S8 just can't keep up lmao. Peak stable Overclock is 2574MHz. 2652MHz when plugged in, 2704MHz can't be sustained. All the S8+ seem like they mostly can do 2704MHz. Golden samples can pull 2808MHz and there isn't anyone that can do that to be seen yet.

I could've gotten higher scores and managed to truly match an S9. But unfortunately it seems it's not up to me to reach that achievement :p

But I opened the path to make people with better S8 attempt to do so. Ace did truly did it. He made a phone reach the performance of its newer counterpart.
[Samsung Galaxy S8 & S8+ Cross Device Development] pranil60:
yes, I talked to those monkeys from other kernel development groups.. those silly guys don't even do anything about temperature control just releasing stock kernel with god knows what changes with updates.. and tried to convince them that they should try this kernel and dev is always active to help. but replied me with what comes out off boosting your device with temperature raising high and battery drain, I said in that kernel everything's controlable upto your preference like controlling the water with the valve unlike this just on and off controlling in your kernel.. removed me out of disrespect.

btw using 2.7ghz with 55% zram in latest release. no issue at all..
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I think that Ace’s level of skill is dedication is very rare amongst XDA developers, that’s the thing. They just can’t make something at Ace’s quality level. This community shouldn’t create such sharp divisions between developers. They should work together to create unified Kernels and ROMs. Such a group would represent a massive development colossus and with proper lead, there’s no telling how high any phone could be pushed.

Either way, there are many things developers on XDA do that I don’t like. For instance, port ROMs and focusing excessively on Android updates instead of working on Kernel side. Port ROMs are basically a “how to introduce bugs in your development” tutorial. Then there’s people focusing on making Lineage OS 17,18 ecc for what, a GT i9300, instead of developing a Kernel that first focuses on making the damn phone smooth to use to begin with. Idk what’s up with people
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
New build is up!

Changelog

Kernel V. 2021.12.20

Fixed random reboots

CPU/GPU: governor update

CPU/GPU: DVFS update - for stability & performance

SELinux: removed fake enforce (enable MagiskHide in Magisk)

Phone status: official (fake)

Wireguard: source update

A2N Kernel Control V. 3.9

Bug fixes

Improved performance

Improved stability

Updated settings

--------------------------------------------------------------------------

Important release info for stability fix:

1.Check post #1 for new installation method!

2. If you are using a non Samsung stock ROM and you flashed at least one time A2N kernel on top, then you have two options:

1. Flash first the same custom ROM you are currently using, then flash latest A2N kernel on top and finally flash magisk.zip.

2: Download patch.zip and replace the files inside the folder "system" with the files from your currently used ROM, but grab the files from the original ROM.zip, don't use the files from your phone!). Then repack the patch.zip and flash it. Finally flash A2N kernel and then magisk.zip

Once your ROM is properly patched, you don't need to flash the patch.zip on every A2N Kernel update.

This will fix also secure folder, if the custom ROM support it.
[Samsung Galaxy S8 & S8+ Cross Device Development] madhatter57:
i tried to create the updated patch.zip with the files from the kernel i use and compressed it using my macos. When i tried to flash it on twrp i got invalid zip format. Can you please advise on a good way to repack the .zip on a mac that will work?
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Make sure that you don't change the structure. In addition try with 7zip.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
@ace2nutzer guess making a patch zip for devbase isnt possible becus devbase use a system.img file so there isnt rlly a folder. Guess with extracting the file its possible but not rlly sure if that is gonna work out.

Edit

Got it extracted and the putted the files in the patched zip folder, hopelfully one of the zip apps doesnt f** up the structure or something.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Just flash your ROM.zip then latest A2N kernel on top. You don't need to create the patch.zip. Or if you find it useful to have a patch, you can grab the files from the phone, but only if you didn't flash any custom kernels on top.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Well got a the files from the extracted system.img file so yea, hope the new created zip file works becus its zipped with a android zip archiver so i have my fingers crossed for it else i flash the rom zip again.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yeah, you even don't need to wipe anything since you would flash the same ROM on top.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
True, and i got a bootloop when i flashed the editted patched zip, when i flashed the one from you it fixed it, so i dont know what goes wrong and what i did wŕong😕

I litterly used the same files from the rom what exists on my phone so yea..
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
@ace2nutzer i found out that the kernel is the problem or isnt compatible with devbase 7.4 UCDUG2, becus i get a bootloop when i flash it, the patched zip what i editted isnt the problem what causes it. I reflashed the rom also with the system wiped with or without the patched zip file and it causes still a bootloop. Tested it also with nx kernel to verify it. So i guess something is wrong with kernel or with the flashable zip of the kernel or the kernel isnt compatible with the devbase build what i use. I checked also if the file was corrupted when downloaded but it was fine, it correspond with the md5 file
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
OK then use other ROM. Here with stock ROM works fine. Using zram 100% setting.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Okay great, well ill look into it again when im awake. Btw which version of devbase do you use? Or which version is known it works with a2n kernel?