[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Sure, configure the kernel properly for your usage and flash always latest A2N Kernel.

Nope, Freq and voltage table is still locked and actually we can only use the hardcoded table so far at least ...

When it's hacked, then for sure ! - So there is still a lot of performance to unlock lol.

No, don't worry.

No, as i already said many times, even if you OC little CPU to the stable 1900 MHz, it reaches only the same speed like the big CPU running at 950 MHz, yes it has only the half of speed compared to the big CPU.

see here:

which is not a surprise since it's smaller as the half size of the big CPU.

For almost all apps 4 cores are just fine ... because so far a can't see an app that keeps all 4 cores busy all the time, or better say all the time ... so even not to mention 8 cores at the same time at 100 % load. The only apps that really uses all available cores at the same time are just benchmarks.

Right now did a simple check how many threads the app "Maps" uses ... it's around 100 - 150 threads. But again, they will never run all together at the same time .. even if you have a CPU with 150 cores, most of them are just very short and small tasks (threads) so that they are very quickly executed, no matter if 4 cores or 150 cores.

Anyway, a single program only can run on just one CPU, because the other CPU has his own L1 cache and so on .. So in the end it's never possible to run a single app in both CPUs at the same time.

But it's possible to move an app from little to big, accordingly to the needed performance.

Last one was the job from the stock HMP driver, but unfortunately it never worked properly so that after long fighting i'd decided to disable this auto moving of tasks and simply assigning taks by hand (hardcoded). Simply as that: performance critical apps (all foreground apps) will always run on big CPU and all small threads and services like audio, GPS, wifi, RIL, all background services and so on, are all running always on little CPU.

Of course tasks, that are locked in one CPU group, will always be able to use all 4 cores, but this is auto managed by the kernel scheduler.

At this way we also kill the latencies introduced when moving apps between both CPUs .. and many other annoying bugs introduced with HMP. ;)

This kernel works as well for overloaded phone with 1000 apps, you only need the proper end-user config. That means you need to configure "Low Memory Killer" to a smaller value for multitasking ... or bigger value for games.

WARNING: don't try to configure the LMK aka minfree values with other apps from store... it's a very bad idea if you don't have much how know about Linux/Android memory management !

Even if you use the default profiles (presets) it's very likely of 99 % to screw up memory management. Because it's also needed to update accordingly the "extra_free_kbytes" vm tunable.

So if you never heard "minfree(6 values) and extra_free_kbytes(1 value)" then let them better in peace or learn first what they do and how it works. In my app you only need to adjust one value which will set "extra_free_kbytes" and the other 6 values will be set accordingly, that's user friendly and noob friendly, and yeah i forgot and fail-safe ! :cowboy:

lol it's not because the file is read-only, i can make it read-write, but it serves nothing.

Thanks ! i'll check it later.

I'm trying to increase from 85 to 100 °C since it's stable up to real max 115 °C.

It's a bit hard .. as i've to very quickly read temp sensor and then reduce Freq if it's over our threshold ... lol ... we are working here in the milliseconds range .. aka real-time kernel-thread.

it serves nothing, the only change would be more heat and battery draining.

Thanks you too for helping with bug reports and logs ! - I'll check it later.

Thanks for your support ! Hmm, honestly this is not the sense of full version, it should work as well with kernel defaults.

So there is something wrong, i do suggest to provide a last_kmsg from demo app after a random reboot. The more logs we've, the better and faster we'll have a perfect, fast and stable kernel.

Thanks for the report ! - last_kmsg.txt is required from demo app.