[Galaxy S3 Neo Original Android Development] helloyello:
Good to know I can ask you for help instead of flashing my phone ;) Will send you a beer next time !

Well, I only have this phone running Android 9 (LOS16) and I also fear that the Simple System Monitor is doing something wrong with displaying that simple graph. Not only the frequencies are high, but the system load too (grey graph), so, basically it could create the high load on itself wile executing the shell scripts in the background to gather the CPU stats on Android 9, maybe due to some stupid (security) checks available only in Android 9.

I couldn't find a way to get the franco kernel manager (not sure if it's free) apk, not using Google Services and franco's site looks down:

https://francokernel.app/

There's no background app that could push the CPU, checked & overchecked a few times.

Will check the dev history on github, thanks for the link.

Not sure I can follow why the interactive governor is configured the way it is now in LOS16, with those variables set (multi_enter_load / multi_enter_time / multi_exit_load / multi_exit_time) that look to be applicable for the modern heterogeneous hexa/octa-core CPUs, where there are a few (2) lazy and power efficient cores usually online for normal operation and then a bunch of performant (different ARM architecture) cores that are activated only rarely - when the load is very high.

ATM I'm using the ondemand governor as it seems to improve the battery life (still too early for a conclusion). It feels a little lazy (demanding apps like Firefox), pretty much like stock ROM, but I don't mind that, I have 20-50ms time to wait for Firefox to display/refresh the page.

Will also try the interactive governor, the way I presented some posts ago - inspired by the J3-2016 setup.

I reported the high CPU temperature the first time I tried LOS16 (some tens of posts ago) and I'm sure is the CPU because it feels hot in the region where it is located on the PCB. Not very hot, but really warm after a few tens of minutes of intensive usage - Firefox browsing/youtube playback/ surveillance cameras playback. This doesn't happen with stock ROM and I've switched now a few times between LOS16 and stock, always paying attention to this aspect. Today I used the phone intensivelly for about 30 minutes with the ondemand governor and it doesn't look to get hot, will observe it further.

I had the suspicion that the ondemand governor only applies for the first 2 cores, core 3 & 4 being either inactive or maxed out and went on to do some investigation & comparison between the J3-2016 (using interactive governor) and the S3Neo - LOS16 ondemand. I switched to using adb on USB, because typing directly on the phone in console is really painful.

J3-2016:

j3xlte:/ $ cat /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus
0
j3xlte:/ $ cat /sys/devices/system/cpu/cpu0/cpufreq/related_cpus
0 1 2 3
j3xlte:/ $

S3Neo:

s3ve3g:/ $ cat /sys/devices/system/cpu/cpu0/cpufreq/affected_cpus
0
s3ve3g:/ $ cat /sys/devices/system/cpu/cpu0/cpufreq/related_cpus
0 1
s3ve3g:/ $ cat /sys/devices/system/cpu/possible
0-3

Under Linux - normal kernel, the cpu scaling governor creates a sys entry where it stores the policy, sort of:

/sys/devices/system/cpu/cpufreq/policy0/

There it's also defined how many cores are used/affected/possible..etc I couldn't find such entries/records in the "handicapped" Android and not sure now how&where does the scaling governor take the values.