yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
yeah but it's only for Snapdragon:

I'll update all firmware + DTS in next build, maybe helps. I've some idea.
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
Wait this is for snapdragon only not for exynos
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
If dev say idea that would be great idea :v
[Samsung Galaxy S8 & S8+ Cross Device Development] spdrfx:
Guys, any idea, why my read and write speed is sooo low?
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
Your storage less then 15gb that why get so slow try to get space up or make a backup
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
I am use latest test kernel when i test it on full stock thermal no mod like thermal paste or other stuff i always get reboot

Maybe cause i set dvfs 100°c

I always get reboot when multi threading test

And the freq is 2.8 big cpu 2ghz little cpu

Gpu 764mhz dvfs 100°c

Zram 100%

Swappiness 160

Other stock

For gpu step

683mhz 670mv

764 705mv

For 838mhz i never get it stable whatever the voltage when it goes 100% load that always get super LAG or maybe stuck frame but for the audio still running not same like my old mainboard
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
@ up

Wait for new build, it'll fix everything.

Maybe because you changed read_ahead_kb ?

I suggest to set @ 512 KB for max speed.

Next release will allow even 1024 KB for higher speed.
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
@ace2nutzer

reached 102hrs uptime using latest, and i don't think it'll stop for my usage pattern..
[Samsung Galaxy S8 & S8+ Cross Device Development] madhatter57:
Re: the issue I mentioned before with system UI crashes had to do with a 3rd party launcher, not kernel. So for ms the only thing that's not perfect is screen rotation, which I still experience lag. But it might be also because I use mostly under clocked values to save battery.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Im 2d stable with the latest test build and last time i charged it, not doing much on the phone but its still up.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yeah screen rotation require both CPU clusters to be at max freq. For some reason long time ago I had removed this enforcement to save battery. Also the service surfaceflinger was moved to little only to save battery. As it turned out, after I've checked how screen rotation works on stock kernel, both things needs to be reverted to stock to make rotation fast. So it'll be finally fixed in next build.

@rtyuakatsuki

Did you already test if it fixes the green tint issue if you test both resolution in Android settings 1080 and highest 1440 ? Because 1440 uses higher lcd freq and therefore higher voltage, but not much.. maybe it needs even higher freq. If that works, there is a chance to provide a software fix for such half broken screens.
[Samsung Galaxy S8 & S8+ Cross Device Development] spdrfx:
No, i didnt change it. I just delete few old backups, and its working fine :)
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
I've test 720 1080 1440p all of them still same issue maybe this hardware has burned out ic controller lcd but for touchscreen normal and no problem
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
But you said issue is fixed if you increase brightness ? I'll try if I can reproduce the issue by reducing lcd freq and voltage.
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
Not at all dev that still green but quiet green almost not see able but still there my lcd issue is when the screen turn off and turn below 4 second that will green but if more then 4 that normal but not at all normal when dark when dark that got some pixlated picture
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
for gfx bench car chase i get 27 fps
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
@ace2nutzer

its 149hrs uptime now.. what do i do?

manually reboot and grab last_kmsg?
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yes ! Which build was it ?
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
a2n_kernel_g950x_9.x_2022.09.06.zip

edit: last_kmsg attached
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
How did you the log ? It's empty.

But it's not a big problem since it works stable. Thanks for testing.
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
is it not working? i've reattached with txt file..

i normally shut it down and booting it back

or did i do it wrong? should i turn it off by force?
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
For last_kmsg log it's required to reboot. The log is in RAM (1MB buffer), if you reboot it'll survive, but if you power off, RAM data is cleared.
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
awww man.. ok i'll do a reboot tonight after work
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
No thanks ! - It's really not needed.
[Samsung Galaxy S8 & S8+ Cross Device Development] madhatter57:
From all the different TCP algorithms available on this kernel, any idea what might be the best to ensure stable calls with video on messaging apps over a network that usually has a lot of lost packets?
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
Maybe you can try one by one to get best algorithms
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Try cubic, bic and westwood+.
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
i tried westwood+ on this kernel for about 4 days, cubic is definitely better for mobile network AND wifi with lots of drops..

was hoping to try BBR since it was google's 😆
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Hey @ace2nutzer, sorry for the bother but this is more of a question of how you managed to assign voltages to 683MHz, 764MHz and 839MHz on GPU.

Mustafacoo (the xxTR Kernel dev) stated he used all the GPU commits you posted on our Github repository for the R19 Mali driver, as well as even the R26 (couldn't on R32 since Samsung changed some things) and defined all of them on the GPU table.

But he said that he can't apply all of it because "the frequencies >598000 have no ASV value"

I think he refers to the voltages being 0 at 683, 764 and 839. We had this issue too. How can he solve it? If you don't mind me asking
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
How looks stock DVFS table ? is it like our here ? - I mean GPU Freq in the table is up to 839 MHz but just voltage zero or even Freqs are missing ?

We don't mind about ASV value at all.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I'll let you know. Thanks for taking the trouble to be willing to give tips. I really really appreciate it
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Mustafacoo stated that max value on the table is 598MHz, which is why is a bit hard for him.

Trying to change the frequency value from asv table only changed the time in state frequency shown but in reality it was still running the max from stock table (598MHz)

Personal observation, this behavior reminds me of devfreq driver, and if it turns out to be, it’s big trouble.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Okay then it's harder to hack. It has nothing to do with devfreq. I saw a few days ago he was trying to add missing steps in ECT table, but that will not work out, because fvmap is initialized first, and the ECT driver takes freq and voltage info from fvmap driver. I would try to add those missing freq steps the same way for voltage hack. If it doesn't work you may need to fill up more things like PLL, the same way in fvmap.c driver.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I’ll tell him, thank you
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
6,5 days stable
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
whoaa.. loads of commits for next build 😍
[Samsung Galaxy S8 & S8+ Cross Device Development] madhatter57:
Hi ace, my Phone is randomly shutting down recently, Im aware it might be a hardware problem bug nevertheless I'm providing a log, should it be something that can be improved in the kernel.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
No idea, but kernel just decided to reboot to LPM (offline charging):

<14>init: Received sys.powerctl='reboot,lpm' from pid: 3636 (/system/bin/lpm)
<14>init: Reboot start, reason: reboot,lpm, rebootTarget: lpm
<0>exynos-snapshot: normal reboot starting
<6>argos_cpuidle_reboot_notifier called
<3>mif: shm_reboot_notifier: Set magic code as 0 because of kernel reboot!
<7>[@]fimc_is_reboot_handler:++
<7>[@]fimc_is_cleanup++: shutdown(0), reboot(1)
<7>[@]fimc_is_reboot_handler:--
<7>[@]fimc_is_shutdown++: shutdown(1), reboot(1)
<7>[@]fimc_is_cleanup++: shutdown(1), reboot(1)
<0>reboot: Restarting system with command 'lpm'
<0>exynos-snapshot: normal reboot done
<0>sec_reboot (0, lpm)
<0>exynos_reboot: Exynos SoC reset right now

It's wrong, you forgot to edit to cpu_lit_volt.

Also you shouldn't use my voltage table, every phone has its own.

Change voltages based on your own voltage table, otherwise it doesn't make much sense.
[Samsung Galaxy S8 & S8+ Cross Device Development] madhatter57:
That's weird, do you reckon there's something wrong with the hardware? It's been a bit hotter recently, and I'm actually fearing it might die soon...
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
No, nothing weird, it was just a clean shutdown initiated by ROM or any app.

Received sys.powerctl='

reboot,lpm

' from pid: 3636 (/system/bin/lpm)

That cmd "reboot,lpm" is not coming from kernel.

I suggest to see how it'll work with next kernel release.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yes, you didn't unlock the kernel. You can run this cmds after A2N passed license check, or in init.d.a2n and it'll run after A2N passed the check on boot.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yeah, that looks fine now. Btw: as it turned out, for now UV/OV only supports CPU-lit-big and GPU. The other freq voltages are managed by devfreq driver and there is no way (for now) to change voltage or freq.

Actually still trying to hack RAM OC .. but I don't have much hope, it's too much hard. When I give up, I'll upload new release, it's basically ready.
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
wow i like how you work dev soon when new release uploaded i will make video review for it
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
near 7hrs SOT, with mario kart & netflix combo ..

why does it last longer while watching something instead of playing games?
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Becus games are resource hogs, but watching something doesnt use much resources, except if you watch something on twitch becus its rlly unoptimized and it causes too being a resource hog.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Gaming cause high CPU/GPU load, while playing livestream video not. If fact you can watch video with almost CPU/GPU running in idle at min freq, because they use hardware decoders. At least on stock ROM that is the case.

On some custom ROMs hardware decoders can't be used, instead they use software decoders and that will use high CPU load.
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
hmmmm i think time to go stock :v
[Samsung Galaxy S8 & S8+ Cross Device Development] madhatter57:
Ok let's see... The other day something really strange happened, phone went dead and would show the charge lighting every now and then, no LEDs even. Only after holding different key combinations for a really long time I could take into download mode, and after some more minutes into recovery mode. Reinstalled kernel and devbase ROM, and from there I could get it back to normal again.
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
what version did you use? 2022.09.06 is very stable on my end
[Samsung Galaxy S8 & S8+ Cross Device Development] madhatter57:
Latest, generally quite stable here as well
[Samsung Galaxy S8 & S8+ Cross Device Development] madhatter57:
It happened again, phone randomly turned off, it was charging. Maybe too hot? I'm attaching new log should it be useful for you.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
These voltages would crash my phone faster than lightning lmfao
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Those temps are excellent for 2808MHz. You should run benchmarks.
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
yups

hmmmmm if like that maybe you can tune for yourself

tips : UV the freq 1 by 1 from your default and test it for 1 min or 2 min with thermalthrottle test
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I already tuned for myself. My little cores are very bad. At 2002MHz I need 1.29V to run stable. It's just a -10mV uV compared to stock 1.3V
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
okey then lets get more UV because i have uv my almost big core hehe i cannot go more 600mv or 0.6v
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I uVed my Big cores on all steps already, and again, I wasn't as lucky as you.
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
how much you get ? -50mv?
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Around that, and only on the middle frequencies. Higher OC and lower frequencies got unstable if I tried to push
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
that would be nice for you btw are your default voltage same like dev have ? because my mine all of the freq is overvoltage
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
1,3 V for 2 GHz step is hardcoded from me. Stock voltage was 1,13 V or smth like that and never worked stable.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Yeah but again, 2002MHz for me started getting unstable at 1.28V, so, the hardcoded voltage was quite close to the actual capability of my SoC.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
I forgot my stock voltage table, but as a reference I remember my 2314MHz stock voltage. 1.025V
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
after longtime tune i think is best for regular use like using maps whatsapp ,open some unstable app marketplace yeah more then enough

before UV lag and struggle to use the phone

after UV almost no lag but still there much² more smooth
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Passed 2 weeks stable, so guess test kernel 09-06-22 is stable as a rock
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Something oftopic, i can notice ppl on xda are more helpfull than on the windows mdl forum damn, got some issues with some things and they just freaking ignore me on mdl😑 glad this forum isnt like mdl
[Samsung Galaxy S8 & S8+ Cross Device Development] madhatter57:
Random reboot.

These are getting more frequent, coupled with random shutdown I reported before. Tell me, should I be looking at buying a new phone or is there a chance this might be caused by some software or kernel?
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
are you sure you're using 2022-09-06 ? cos that version's uptime passed 2 weeks without issue

edit: read your attached last_kmsg, i might read it wrong but there sre lots of lots of files not found by the system, it might be a sign of corruption.. i suggest doing an fsck (e2fsck) on your partitions, mainly the system one

maybe @ace2nutzer could clarify ?
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Same here, 3 weeks stable with an shutdown mean while becus i forget charge the phone lol
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
true, it was rock stable until my netflix wouldn't boot coz the DRM stuff can't be detected, i had to restart 😛

@ace2nutzer do you know what service/processes does the DRM depends on? i've exerienced this twice within a week, i know it's not kernel issue but just wild guessing you might know the issue/solution
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
I know it depends on the safetynet pass and the drm L version, but specific services and processes idk
[Samsung Galaxy S8 & S8+ Cross Device Development] madhatter57:
Apologies as I didn't realise there was a test version available, I was on latest stable. Trying latest test now
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
No. Don't ever assume an Android phone has no errors or warnings in dmesg / logcat. Every Android phone has it, but we devs know what errors/warnings are critical and should be fixed and which we can safely ignore. In that case, you can ignore them as they are just some left overs from previous Android version, which are left for reference/compatibility reasons or just because Samsung/Google was too lazy to clean it up, never mind just ignore them.

DRM is in this kernel always L3, because of the removed DRM lib.

So there shouldn't be any issues at all as long as SafetyNet passes.

Other than that, I've no idea what could cause still issues sometimes, as I don't use DRM stuff. (Always busy with kernel development lol)
[Samsung Galaxy S8 & S8+ Cross Device Development] madhatter57:
Unfortunately the problem still persists with latest test kernel. Random reboot/shutdown, usually happens when using phone plugged in and it gets a bit hot (I limit maximum charging temperature to 38 degrees now , charging at 2600mah)
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
i suspect there's something wrong with your filesystem, as i mentioned earlier.. there's a lot of system files not found and also e2fsck failing entries..

checking them out won't do harm.. or if you prefer a cleaner way you could reflash the whole rom with full wipe

but if you choose not to do both, atleast try resetting the kernel configurations to default and start with recommended values and see how it goes
[Samsung Galaxy S8 & S8+ Cross Device Development] madhatter57:
Thanks for the suggestions, it is funny because I did a clean install of the ROM recently, but I shall try again.... Do you mean a full wipe excluding data and storage, right?
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
i think the rom you flash is corrupted or something else and also its better to use full stock rom and debloat it using luckypatcher
[Samsung Galaxy S8 & S8+ Cross Device Development] madhatter57:
Hey thanks for the suggestion, what I flashed was latest devbase ROM which is supposedly full stock. Is there a simple way to install full stock ROM using twrp? Perhaps if you prefer and have availability to send me some information privately that would be much appreciated !!
[Samsung Galaxy S8 & S8+ Cross Device Development] Twiq:
what i meant by full wipe was formatting /system and /data

then flash the rom and kernel.. this is a real pain, i know :D
[Samsung Galaxy S8 & S8+ Cross Device Development] rtyuakatsuki:
for that i don't know about stock rom flashed in twrp sorry bro
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Istg I have no idea what people are talking about. I had 0 random reboots in weeks except for those I caused by testing undervolt. This thing is like the most stable stuff ever.
[Samsung Galaxy S8 & S8+ Cross Device Development] Ryujin96:
Agreed dude
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
So after some testing I came to the conclusion that 839 and 764MHz on GPU in my personal use case scenario are unfortunately a hit or miss. Doesn't matter what voltage I assign to it, it will eventually just force reboot at some point or another, in some cases (not all of them, but most). Basically the GPU is capable of handling 764 and 839MHz but Samsung just didn't put in the hardware to handle it for long periods of time (unless somebody has got the luck to have an incredibly high ASV G71). Well, 683MHz is still a 25% overclock.

Admittedly I didn't try to run the benchmarks in battery idle, which may solve the issue. But I never really used that function, so I have no idea how it is used.
[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Next release will be lots better. ;-)

Just plug the original AFC charger or use any other USB charger that can supply at least 3 A @ 5 V or 1,67 A @ 9 V, then enable battery idle in A2N app and that's it ! There is no longer needed to set current @ max value since it's done automatically, (I'd patched that in some older release)

PS: max battery charging temp should be at least @ 40°C to avoid power drop.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Got it. Thanks.

Either way my bad. I did some more extensive testing, and it turns out it was simply the benchmark I was using to be garbage, as I managed to be stable even at 839MHz through several GFXBench runs. And thanks to that, I gathered CONCLUSIVE GPU performance data for the first time about this device. And I want to share it here, as a token of gratitude.

I ran so many benchmarks that in fact I reached the GFXBench TESTING LIMIT, so unfortunately I couldn't do a variety of simulations for 764MHz and above, since it was locked.
[Samsung Galaxy S8 & S8+ Cross Device Development] TechNoobForSale:
Here is a part of the data I gathered.

Galaxy Note9's Mali G72 MP18 @572MHz (For comparison!):

1080p Driver Overhead 2 (OpenGL ES 3.0) Offscreen: 26fps (1,545fps)

1080p ALU 2 (OpenGL ES 3.0) Offscreen: 102fps (6,115fps)

1080p T-Rex Offscreen: 134fps (7,481fps)

1080p Manhattan 3.0 Offscreen: 80fps (4,930fps)

1080p Aztec Ruins (Normal Tier, OpenGL ES 3.1) Offscreen: 32fps (2,036fps)

1080p Aztec Ruins (Normal Tier, Vulkan 1.0) Offscreen: 30fps (1,914fps)

Galaxy S8's Mali G71 MP20 @546MHz (Stock):

1080p Driver Overhead 2 (OpenGL ES 3.0) Offscreen: 19fps (1,142fps, CPU bottlenecked)

1080p ALU 2 (OpenGL ES 3.0) Offscreen: 94fps (5,633fps)

1080p T-Rex Offscreen: 120fps (6,747fps)

1080p Manhattan 3.0 Offscreen: 72fps (4,461fps)

1080p Aztec Ruins (Normal Tier, OpenGL ES 3.1) Offscreen: 29fps (1,833fps)

1080p Aztec Ruins (Normal Tier, Vulkan 1.0) Offscreen: 24fps (1,526fps)

Galaxy S8's Mali G71 MP20 @572MHz

1080p Driver Overhead 2 (OpenGL ES 3.0) Offscreen: 19fps (1,156fps, CPU bottlenecked)

1080p ALU 2 (OpenGL ES 3.0) Offscreen: 99fps (5,968fps)

1080p T-Rex Offscreen: 124fps (6,929fps)

1080p Manhattan 3.0 Offscreen: 74fps (4,596fps)

1080p Aztec Ruins (Normal Tier, OpenGL ES 3.1) Offscreen: 30fps (1,904fps)

1080p Aztec Ruins (Normal Tier, Vulkan 1.0) Offscreen: 25fps (1,588fps)

Galaxy S8's Mali G71 MP20 @683MHz

1080p Driver Overhead 2 (OpenGL ES 3.0, running with M2 Cores at 2496MHz) Offscreen: 20fps (1,224fps)

1080p ALU 2 (OpenGL ES 3.0) Offscreen: 118fps (7,096fps)

1080p T-Rex Offscreen: 135fps (7,582fps)

1080p Manhattan 3.0 Offscreen: 83fps (5,154fps)

1080p Aztec Ruins (Normal Tier, OpenGL ES 3.1) Offscreen: 34fps (2,191fps)

1080P Aztec Ruins (Normal Tier, Vulkan 1.0): 29fps (1,833fps)

Mali G71 MP20 @764MHz:

1080p Driver Overhead 2 (OpenGL ES 3.0, Running with M2 Cores at 2574MHz) Offscreen: 21fps (1,269fps)

1080p ALU 2 (OpenGL ES 3.0) Offscreen: 132fps (7,915fps)

Mali G71 MP20 @839MHz:

1080p ALU 2 (OpenGL ES 3.0) Offscreen: 144fps (8,656fps)

ALU 2 benchmark seems to perfectly reflect each performance increase by percentage, for example a 50% increase in clockspeed is almost a 50% increase in score on ALU 2 benchmark, which means this thing highlights the pure GPU performance increase. The other game benchmarks are treated in the 683MHz sections, as I couldn't run them on 764MHz and 839MHz due to GFXBench limit, but we got a curve, and we can calculate the theoretical scores starting from there.

So fellas, yes. We did it. Ace did it. We are faster than Galaxy S9, a lot.
[Samsung Galaxy S8 & S8+ Cross Device Development] spdrfx:
Hello Ace, do you plan to implement custom voltage settings to the control app?