[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
12-22 16:39:20.408 18885 18885 E AndroidRuntime: Process: com.samsung.android.kgclient, PID: 18885

Did you any modification to the ROM? kgclient is if i'm not wrong something to do with knox. Did you install any patch to get secure folder working ?

Anyway, i believe it's also some sort of incompatibility with latest security patches. I think if we use this kernel on some older Android 9 versions, then it could work stable.

Because i've some hints here ... after every soft reboot, in logcat i see this error:

12-22 16:39:21.061 17709 18808 E CONSCRYPT: ------------------Untrusted chain: ----------------------
12-22 16:39:21.062 17709 18808 E CONSCRYPT: == Chain0 ==
12-22 16:39:21.062 17709 18808 E CONSCRYPT: Version: 3
12-22 16:39:21.062 17709 18808 E CONSCRYPT: Serial Number: 688c81596b3eba1b36f67520d5737abf9da4a44e
12-22 16:39:21.062 17709 18808 E CONSCRYPT: SubjectDN: CN=localhost
12-22 16:39:21.063 17709 18808 E CONSCRYPT: IssuerDN: CN=localhost
12-22 16:39:21.063 17709 18808 E CONSCRYPT: Get not before: Sun Aug 15 10:01:20 GMT+02:00 2021
12-22 16:39:21.063 17709 18808 E CONSCRYPT: Get not after: Sat Sep 14 10:01:20 GMT+02:00 2024
12-22 16:39:21.063 17709 18808 E CONSCRYPT: Sig ALG name: SHA256withRSA

It's somehow related to this:

https://android-developers.googleblog.com/2018/03/cryptography-changes-in-android-p.html

and i've no idea what i've to patch in ROM or kernel.

Thanks for reporting server is up, I fell asleep then.

Sure, some features will not work properly.

You should try to find out what changes is causing this issue.

I've only Linux and Win Xp, so i can't test Dex.

The kernel installer removes those files from system:

delete_recursive("/system/vendor/lib/libsecure_storage.so");
delete_recursive("/system/vendor/lib64/libsecure_storage.so");
delete_recursive("/system/bin/sysinit");
delete_recursive("/system/bin/sysinit_cm");
delete_recursive("/system/app/SecurityLogAgent");
delete_recursive("/system/priv-app/Rlc");
delete_recursive("/system/priv-app/KnoxGuard");
delete_recursive("/system/priv-app/TeeService");
delete_recursive("/system/app/mcRegistry/ffffffffd0000000000000000000000a.tlbin");
delete_recursive("/system/ffffffffd0000000000000000000000a.tlbin");
delete_recursive("/system/lib/libvkjni.so");
delete_recursive("/system/libvkjni.so");
delete_recursive("/system/lib/libvkservice.so");
delete_recursive("/system/libvkservice.so");
delete_recursive("/system/lib64/libvkjni.so");
delete_recursive("/system/libvkjni.so");
delete_recursive("/system/lib64/libvkservice.so");
delete_recursive("/system/libvkservice.so");
delete_recursive("/system/lib/libvkjni.so");
delete_recursive("/system/libvkjni.so");
delete_recursive("/system/etc/init/bootchecker.rc");
delete_recursive("/system/app/KnoxAttestationAgent");
delete_recursive("/system/priv-app/KnoxContainerDesktop");
delete_recursive("/system/priv-app/KnoxCore");
delete_recursive("/system/priv-app/KnoxDesktopLauncher");
delete_recursive("/system/priv-app/knoxanalyticsagent");
delete_recursive("/system/priv-app/knoxvpnproxyhandler");

Once it's working, try to delete one by one those files manually, ... you can do this in TWRP using ADB .. it's very easy.

Mount /system in twrp and run:

adb shell
rm -r /system/vendor/lib/libsecure_storage.so

if you get error: file not found or so, then try to remove the next file.

then reboot to system and test Dex.

If it doesn't work now, then you found the culprit and you should report it here, then i can update the kernel installer.

If not, reboot again to TWRP and delete another file:

adb shell
rm -r /system/vendor/lib64/libsecure_storage.so

Again, reboot to the system and test.

With 572 MHz running sling shot extreme, it only has a peak of 85 °C. So it doesn't throttle at all if you set GPU DVFS 95 °C. Maybe 683 MHz could hit 95 °C.

As for the voltages > 572 MHz: i've already tried it to add voltage to those steps with 0 mV in the DVFS voltage/clock table to 850000 which is the max voltage for the GPU voltage regulator. But it freezes instantly once i start geekbench COMPUTE bench.

gpu_asv_table shows me voltages all assigned, but i guess the GPU don't care about those DVFS voltages and still uses the voltage taken from binary in SRAM. Which are copied from here "exynos8895_acpm_dvfs.fw". So probably the proper way to hack is to write the missing voltages directly in the SRAM. And since it's binary, not readable source code, I don't know which bits i've to manipulate.

Maybe another way is to get rid of CAL_IF and the ACPM stuff, and use custom freq_table for clocks and voltages. But requires some know-how about the clock generator (PLL) and the same for voltage regulator. Honestly, i've no more time for try and error as it's very time consuming. If some of you can provide a patch from similar SoC, then i can try to port this to dreamlte.

I'm planning to support the Note8 as well, but after this kernel is stable. I don't want to push a unstable kernel to the Note8 users.