[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Yeah, finally ! - That's great hehe.

As for restoring of custom settings:

I think that should be possible, but a bit tricky and maybe unsafe and that's why i ended up with that solution.

That would only work if there is internet connection immediately after entering the SIM PIN.

That means i've to create a loop function that waits for device comes online and the risk is that, it could stop or get killed if the phone is on heavy load, because it would be a java process / activity, which as i said could get killed if the RAM is full. Since it's a background process, it's likely that it gets killed and you end up with a non optimized phone while you think all custom settings was applied.

I know you say just add toast notification, but for sure you don't want to watch all the time the screen in the hope the toast will appear. Instead you could just open the app directly after entering the PIN.

Isn't it much faster ?

That's for now, maybe i get better idea how to manage this, but for now i don't have much better idea.

Yeah perfection needs his time sometimes.

In some benchmarks it's nearly at the same level like the S20 ! :cool:

But with both clusters and GPU OC'ed to the max and DVFS temp at 95 °C.

With kernel defaults yes. Kernel defaults is optimized for good battery life and tries to keep the device cool.

There is no need to mess with HMP or CPUSETS, it's already very well optimized. By default foreground uses all 8 cores. You can see this while running Geekbench for CPU .. starting at 50 % of the bench progress, all 8 cores are used. You can verify this while it's running, connect your phone to your PC and start ADB .. type "top"

You will see cpu load gets up to 800 % means 8 x 100 %.

With older kernel the max was 400 % and therefore Multi-Core Score was low.

Nope, this was because dex optimization (ODEX compilation) was done only @ Little CPU and only while the phone is charging. And unfortunately even only with just one thread instead at least 4 threads.

And therefore it took a few days till everything was compiled in machine code.

On latest realese i've patched it to force run on big CPU, still only one thread, but better than nothing. It's AOSP Bug and was fixed in later Android versions.

That means it'll optimize faster on latest kernel.

In addition if you guys follow my tips and checked those flags like:

dalvik.vm.isa.arm64.variant=exynos-m1

after wiping dalvik cache it'll create machine code optimized instructions set for our CPU. Not just defaults (lower performance)

You can read more informations on how ART works and how it should be configured here. All the tips for best performance are already applied to this kernel.

For instance we use "speed-profile" instead raw "speed" flag in order to not waste RAM.

As for the last thing:

like i was promising some time ago, all the users who helped me out in any way in fixing bugs, are allowed to ask for a free license to get full access to all premium features in this kernel.

What you need to do:

send me a pm with one or two links to your post were you contributed to this project to help. Like reporting bugs with attached logs.

Note: i do accept only reports with proper logs, but in certain situation i'll accept also those without logs if it was useful as well.

Right after the random reboot, open the red A2N app and in-app menu tap on "Debug" then "last_kmsg".

This will create "last_kmsg.gz" to your internal sdcard.

Just attach it here.