[KERNEL][4.4.111+][for Android 9] A2N Kernel for Galaxy S8 / S8 Plus / Note8 Exynos [R57]

[TechNoobForSale]

No, no and no. As long as you don't go outside the A2N app, you are safe with every setting. The worst case is unstable setting, that's all. And the only thing is that it'll increase the heat and therefore will throttle down to 764 with a lower voltage. But as long as even with 839 MHz it'll stay below the adjusted DVFS max temp, you will benefit from higher speed. And of course it'll increase power usage.
More power --> more heat (--> better cooling) --> higher speed.

I know how it works Ace. I’m just asking because heat isn’t the only thing that can kill a processor. It’s also voltage. Either way if 850mV is fine, then I can most definitely run 839.

 

[ace2nutzer]

I know how it works Ace. I’m just asking because heat isn’t the only thing that can kill a processor. It’s also voltage. Either way if 850mV is fine, then I can most definitely run 839.

Yes you can pretty safe use 839 MHz.

I've found this interesting article., about how much voltage a CPU can take.
They say up to 1,4 V it's safe with proper cooling or like here with proper DVFS driver. I couldn't find much info about GPU, but it should be the same, since they are in the same nm.
As you can see for CPU we can set max 1,4 V. And for GPU only 1,0 V.
It's even possible to push the GPU @ 1,4 V but it's not worth it, because 839 MHz @ 1,0 V is already very hot in full load. Also I've capped to 1,0 V for GPU, because I think that nobody needs more than 1,0 V to make 839 MHz stable. And honestly if 839 MHz won't work stable even @ 1,0 V, then it's really better to use 764 MHz instead to run the phone to the hell for just having a bit of more speed as compared to 764 MHz.

 

[rtyuakatsuki]

Waiting for R55 Hehe
Gpu improvement at gaming
Moroaudio maybe :v from Noxxxious source code
Cpu stability
Memory management
Higher usage bus for GPU
Maybe that for the update :>

 

[ace2nutzer]

Waiting for R55 Hehe
Gpu improvement at gaming
Moroaudio maybe :v from Noxxxious source code
Cpu stability
Memory management
Higher usage bus for GPU
Maybe that for the update :>

Yes, new changelog Is similar to this.
And you guys already know it, if I miss my own timeline for releasing new build then it means like always I'd decided in last minute to fix more things and to add more useful features.

 

[TechNoobForSale]

Yes, new changelog Is similar to this.
And you guys already know it, if I miss my own timeline for releasing new build then it means like always I'd decided in last minute to fix more things and to add more useful features.

Ace isn't going to stop squeezing this Exynos 8895 until he can send people to Mars with it

 

[TechNoobForSale]

Exynos 9810 is making numbers this is pretty powerful. I think I should try hard to get 1900 on my S8. But 2000 is impossible with my bins. It’s funny because what our E8895 can achieve at 2808MHz with many sacrifices, E9810 can reach at just 1690MHz no problem.

 

[Twiq]

@ace2nutzer
wait what? does that mean that for all this time memory management readahead IO were capped at 128k randomly?

 

[ace2nutzer]

Yes seems so. And do you know what previous patch about __GFP_NOWARN will fix?

 

[Twiq]

Yes seems so. And do you know what previous patch about __GFP_NOWARN will fix?

i'll try to guess.. blkcg is related to memcg which maps memory for subsystems IO, if it's buggy or leaking then it could lead to page allocation failures resulting many things as filling up memory with junks and causing OOMs? no?

edit: forgot to say that considering the other patch is in the cfq io scheduler, then it's a fix for IO scheduler (edit 2) queue-ing??

 

[TechNoobForSale]

So


I tried to challenge a Snapdragon 888 S21 FE with my S8 at 2314MHz in app launch speed.





It didn't go well

 

[Twiq]

So


I tried to challenge a Snapdragon 888 S21 FE with my S8 at 2314MHz in app launch speed.





It didn't go well

i bet that s21 has less installed apps than your s8

 

[TechNoobForSale]

i bet that s21 has less installed apps than your s8

Nope. It has more. Way more. But we both optimized the phones for the run right before the test.

It just shows, the immense single core performance advantage that the X1 Core grants the 888. It wasn't even a challenge. At 2314MHz the 8895 just couldn't hold a candle. I didn't want to run 2704MHz since it would be Quad, and quickly drags the phone to 100°C. This is the stuff that would require a single core boost. But I strongly believe that even at 2808, it would have lost.

I tried with my Exynos 9810 at 2314MHz too, and, surprisingly, it actually kept up.


Meanwhile my 835 took the worst beating out of all. The 8895 did way better.

 

[Twiq]

Nope. It has more. Way more. But we both optimized the phones for the run right before the test.

It just shows, the immense single core performance advantage that the X1 Core grants the 888. It wasn't even a challenge. At 2314MHz the 8895 just couldn't hold a candle. I didn't want to run 2704MHz since it would be Quad, and quickly drags the phone to 100°C. This is the stuff that would require a single core boost. But I strongly believe that even at 2808, it would have lost.

I tried with my Exynos 9810 at 2314MHz too, and, surprisingly, it actually kept up.


Meanwhile my 835 took the worst beating out of all. The 8895 did way better.

welp, can't beat nano tech advancements.. 10nm vs 5nm lol
not to mention the ram bus speed differences

 

[ace2nutzer]

i'll try to guess.. blkcg is related to memcg which maps memory for subsystems IO, if it's buggy or leaking then it could lead to page allocation failures resulting many things as filling up memory with junks and causing OOMs? no?

edit: forgot to say that considering the other patch is in the cfq io scheduler, then it's a fix for IO scheduler (edit 2) queue-ing??

No, it's a fix for the memory allocation failure warnings you saw in last_kmsg or dmesg. And hopefully this will fix also rare bootscreen glitches.

So
I tried to challenge a Snapdragon 888 S21 FE with my S8 at 2314MHz in app launch speed.
It didn't go well

Toch boost duration enabled at least to 1000ms? And btw in recent releases the touch boost freq for both big lit CPU was reduced to be more efficient for battery. If you set over scripts to allow boosting at max freq then apps should open faster. (Especially if you use OC) but for me it's fast enough.

 

[TechNoobForSale]

No, it's a fix for the memory allocation failure warnings you saw in last_kmsg or dmesg. And hopefully this will fix also rare bootscreen glitches.

Toch boost duration enabled at least to 1000ms? And btw in recent releases the touch boost freq for both big lit CPU was reduced to be more efficient for battery. If you set over scripts to allow boosting at max freq then apps should open faster. (Especially if you use OC) but for me it's fast enough.

Mate Ace I'm not complaining about speed. It's buttery fast. Boost duration was all maxed out as far as I remember. Recent release may optimize it a bit more, but I was trying to strike WAAAY above our weight class there

I wasn't trying to challenge an S9, or an S10, or even an S20. It was an S21 bro LMAO. It isn't even something merely about processor speed.

It's UFS 2.1 vs 3.0
It's 1794MHz vs 3200MHz MIF
It's one high performance Core made to run at high frequencies vs 4 Cores running at a lower frequency

You did so good that our E8895 can outperform in speed some E9820 devices and most E9810 in these daily tasks (It surpasses my E9810 Note 9 in terms of performance consistency, too), but bro, 4 generations ahead, that's just straight up mission impossible.

I just did the test to have fun, lmao. But I was really curious, to be honest.

 

[Twiq]

No, it's a fix for the memory allocation failure warnings you saw in last_kmsg or dmesg. And hopefully this will fix also rare bootscreen glitches.

close enough

well anyway if you really fixed it then it means we'll have better and memory efficient kernel.. not saying that it isn't currently, but more fine tuned

i hope you're enjoying the developments

ps: my screen cracked, it still works fine tho, fixing it almost costs half the price of a secondhand s8, this suckssss

 

[TechNoobForSale]

close enough

well anyway if you really fixed it then it means we'll have better and memory efficient kernel.. not saying that it isn't currently, but more fine tuned

i hope you're enjoying the developments

ps: my screen cracked, it still works fine tho, fixing it almost costs half the price of a secondhand s8, this suckssss

Our S8 may be old, but it's still a piece of art, and so is the screen, that's why it's so expensive

 

[ace2nutzer]

@ twiq
Yes you was close.
@TechNoobForSale
I know you are not saying it's too slow.
But you was trying to make a race without to give full-gas hehe, that's why I told you about CPU not running at max freq. 1456/1703MHz lit/big for touch boost.

 

[Pistero07]

hello good afternoon, I am experiencing a problem connecting a samsung syncmaster sa300 monitor. (via samsung dex with hub) the monitor flashes, shows an image and turns off, continuously as shown in the video. I connected this same monitor to a netbook and it works perfect.

 

[ace2nutzer]

hello good afternoon, I am experiencing a problem connecting a samsung syncmaster sa300 monitor. (via samsung dex with hub) the monitor flashes, shows an image and turns off, continuously as shown in the video. I connected this same monitor to a netbook and it works perfect.

Probably wrong resolution or missing driver for the hub.
What is the model name of this USB hub? (maybe missing driver)
Did you test if it works with the stock kernel?
Also did you try to change resolution in Android settings?
And one more: in A2N app --> screen --> try to change resolution for Dex.