do not worry, friend! it is not related to kernel at all...it is a Magisk API issue.
Stock Rom (debloated)thank you for answering my Questions.
so after reflashing and Fiddle around with some ROM, im down to 2 Choices:
i still dont know which one better since its similar. any insight from the Senior here?
i will Try and Flash this Custom Kernel afterward.
i use my phone for Daily Call, Lots of Whatsapp for updating work progress. some browsing and Gaming(not to much)
Did you (again) set gpu min freq to the same value as max freq ?Report reboot when open facebook ......
Gpu min max 572
You have filesystem error on /data partition.Report reboot when open facebook ,menu marketplace
I was think because of my settings
Big cpu 2.7
Little cpu 1.8
Gpu min max 572
Dvfs 95 all
But i report it to sure because of my settings is too extreme or else reason
Dev, it was absolutely not to press to solve, indeed you are doing a great job ultimately to listen to us all and we are happy with it.@Devil90
i've tried a lot of things, but it's a hard to find issue.
Anyway, it's related to the mess caused with our buggy HMP implementation.
It's already much better than the Samsung version, but the drawback is this bootscreen glitch.
I believe it's caused by the init process, it's loaded at first for executing ramdisk (bootscripts).
And the problem is that the cpuset stuff is mounted too late and even if i move the init process from "0-7" (all cores) to "0-3" (little) it's possible that it has then some child processes that will again run on all cores and this causes the glitch. Now i'll try if i can manage it anyway, it's like impossible mission lol.
Ouh 2 days ago i clean install alexis rom format data tooYou have filesystem error on /data partition.
Sometimes such errors are autofixed on boot.
Anyway if the driver can't repair it on boot, then it's likely that it'll reboot again.
If so, the only way to fix it is to format /data.
If reboot still occour even after formatting then it's likely that your eMMC is broken.
Note: filesystem errors only happens if one of the 2 situation will happen:
1. After a dirty shutdown/reboot, mostly caused by too high/unstable OC.
2. if the eMMC is simply at his end of lifespan.
Dev, it was absolutely not to press to solve, indeed you are doing a great job ultimately to listen to us all and we are happy with it.
However I agree, in the end it is just a nuisance (at least for me who often restart the device) and in any case it does not imply errors, let's not talk about having that Samsung hmp setting that is really worth it.
However, I have noticed in some tests that with zram disabled it happens rarely or almost never, perhaps due to the less weight in loading the zram driver? Obviously it's just a guess.
Ouh 2 days ago i clean install alexis rom format data too
Thx for sure me my reboot is caused by me thx dev
Edit: and how about LMK that has fixed? Can i change it?
I don't have the full kernel but i have the init.d code hehe for LMK i found code on some thread and its wrong code when i checkNo problem.
LMK wasn't buggy at all, but it's considered to be unstable if it's tuned too tight.
The Android system needs a certain amount of free RAM to work properly.
by default it was set to 64 MB, that means there's almost always at least 64 MB free RAM to make space for new memory allocations like opening a new app that wasn't actually in RAM.
If this value is too low it can cause severe lags and freezes and in the worst case scenario it could even freeze the whole system for long time, so that you've to reboot.
According to my experience this happened quite often in old Android devices with low amount of RAM and moreover with too old unstable kernel.
Now maybe such extreme behaviour will never happen again, but who knows.
As i said default was 64 MB and i've changed to 128 MB because the smallest app has around 150 MB. (required RAM size)
And some bigger apps have 200 - 300 MB RAM requirement.
So if you don't care about multitasking and want always a snappier phone, then set 256 MB.
Otherwise for multitasking set 64 - 32 MB. 16 MB maybe works as well, i didn't test it so far, but i guess that you'll face some latencies once the RAM is completely full.
Also how you want to set it ? - Do you have the full version ?
And the ability to encrypt data over the NX kernel
I hope next update can do oc gpu
First impressions that my S8 is much more snappy and doesn't have some micro lag that came with the stock one, plus the apps seem to open faster.
I haven't downloaded the kernel control app yet, and I'm with the basic settings, the only problem is that I have bad battery life, with the same use as before, from 0-100% I managed to do " only "3 hours of active screen, while before I even reached 6 hours.
I really didn't remember.. Remind me of your answer