[Samsung Galaxy S8 & S8+ Cross Device Development] ace2nutzer:
Re-install the App, as it works fine for me.

No.

Thanks for your Report ! Noted.

OK, try this: Set zRam at 0 %, then Open the Android ROM Settings .. then Device management (or so) and tap on Storage .. then "Clean"

to remove all the temp files and cache files from all apps.

Once it's done, reboot to TWRP and tap on Wipe ---> Advanced Wipe ----> select ONLY wipe dalvik-cache + cache. and wipe it.

reboot to the system and be patient.

I sugggest to do this every time u feel that the phone becomes slowness for no reason or it starts lagging.

Then it should be fast and smoother.

If u feel Multitasking is bad, set 25 % zRam.

If it doesn't help much, then 50 % zRam.

Now before u test Multitasking u should wait till zRam is completely ready for use. Because if the 25 % was full = 919 MB .. and u change the size ... then it'll first decompress those 919 MB ... and this takes a few minutes .. (up to 5 - 10 minutes) during this time your Phone will heat up a bit ... because decompression runs on all 8 cores. Anyway u can also reboot the Phone ... that's maybe faster.

Or to check when it's done, install form Play "Terminal Emulator" and type:

free -m

there you can see info about RAM and swap.

so 50 % zRam is done and ready for use when u see 1847 for total swap.

Tip: instead to type every time free -m, just type "r" (repeat command).

If above tips, didn't help, u can try this last Pro-Tip, before u wipe data:

Type in terminal:

su
echo 65536 > /proc/sys/vm/extra_free_kbytes

This will set it to 64 MB which is the default on Stock Kernel ... but i had set it to 0 MB .. because for me it's like a waste of RAM ...

those 64 MB are always free, and only rarely shortly used ... then the VM will make those 64 MB instantly available and of course triggering the LMK (low-mem-killer) and some Apps cache will be wiped or even killed if needed. Personally i like to have the RAM completely fully used = less CPU cycles = better battery lifetime ... but anyway ... if this really would fix such micro laggs then i'll set it back to stock in next kernel update.

u can also try with 8, 16, 32 MB, or even 128 MB ? Just find out what is the lowest Value that is enough for fixing laggs ...

Just calculate MB * 1024 = kbytes ...

so for 32 MB u should type: 32768

Please post what lowest values worked best for you !

WTH is extra_free_kbytes tunable ??

From the Kernel Documentation:

It's for making the scrolling more smooth ... so to fix laggs. (nothing to do with multitasking)

Every time u touch the screen ... e.g. because u're scrolling an web article or PDF file ... then it'll force CPU speed at max freq even if it's actually not really needed on the load side. Because scrolling can't cause real 100 % CPU load so that the CPU Governor can set cpu at such high freq. so because of that, it would lagg ... There u can adjust ad which max freq it should jump immediately ... and how long it should stay at this boosted freq ... for maximum smoothness u should keep the freq at max ... and duration at 1500 or even better at 2000 ms.

The problem is, this will drain a lot of battery ... because if your fingers are almost all the time on the screen ... so only keeping your finger on the screen, but actually doing nothing ... then the CPU freq is forced all the time at max speed (or the adjusted Value from you ---> input boost freq ... then when u remove your finger from the screen, the freq still stay at this max freq for the time it's set in ---> input booster duration.

Here the same, the longer time the more smooth, but higher battery draining.

Stock was 832 / 858 Mhz at 500 ms ... that's quite too low, that's one of the reason why stock kernel laggs like hell. :)

On the current logic, the small CPU is always boosted at max Freq ... because it has only the same speed like big cpu at 850 MHz ... that's why it doesn't make any sense to use lower Values .... because max freq is allready very low.

That's why we adjust only the BIG CPU.

:good: :good:

Strange, no idea, i didn't mess with that.