[Galaxy S3 Neo Original Android Development] helloyello:
I'm not asking you to help with the log, but since you're in contact with the devs, you could talk and point them to the issues users are reporting, publicly on this thread, with the LOS16 on S3 Neo. That's in case the devs actually care about the feedback provided for their work and don't just "hide" under the comfort given by that pseudo-scientific crypto powered mess called Telegram.

Just in case someone cares, I've uploaded the latest tombstone (audioserver crash dump) on Mediafire:

http://www.mediafire.com/file/61qeyx1j2iao45k/tombstone_13/file

The only edit I made (privacy) - changed the BT headset MAC Address to: BT:MA:CA:DD:RE:SS

I've resolved the Gallery display, had to clean the entire Cache in TWRP, don't know why it didn't work with the selective per App cleanup (Gallery/Downloads/DownloadManager,&co).

On the high battery usage, I've been studying a little what could cause the rather short uptime life compared to stock ROM and I believe it's caused by the CPU frequency scaling driver & settings. Worth reminding that the S3Neo under LOS16 eats around 1% battery per minute under intensive browsing and it gets really hot - even with my personal workaround to limit the max CPU frequency on standard levels at 1401600.

I own 3 Android devices powered by quad core Cortex-A7 CPUs, the S3Neo running LOS16, a J3-2016 running LOS (Android 7) that has a cheap Spreadtrum SC9830 and a tablet running stock KitKat 4.4 (no CyanogenMod/LOS available) that has the same Qualcomm MSM8228 CPU as the S3Neo.

Found the Simple System Monitor App and used it to analyze the running apps, CPU loads and CPU frequencies on all these three devices:

https://play.google.com/store/apps/details?id=com.dp.sysmonitor.app&hl=en

And learned that the S3Neo under LOS16 always keeps 2 cores at (almost) maximum speed, even for displaying some simple graph in Simple System Monitor.

Attached the graphs on all 3 devices.

Went further and inspected what frequency scaling driver the devices are using and found out that both the J3-2016 and S3Neo are using the interactive driver, with different settings. The J3-2016 is also very old/used, but has a higher capacity battery (2600 mAh). Still, the J3-2016 has decent uptime life (4-5 days) on comparable usage and doesn't overheat like the S3Neo.

The tablet is using the ondemand governor and it's a little lazy, but the battery holds ages.

Here's a comparison table with the interactive governor settings between J3-2016 and S3Neo:

Values	J3-2016	S3 Neo

target_loads:	85	70 998400:80 1094400:90
hispeed_freq:	1350000	1094400
go_hispeed_load:	90	90
above_hispeed_delay:	25000	25000 1094400:50000
min_sample_time:	40000	50000
sampling_rate:
sampling_down_factor:	50000
up_threshold_any_cpu_freq:
up_threshold_any_cpu_load:
sync_freq:	0
----
Additional:
----
io_is_busy:	1	0
timer_rate:	40000	30000
timer_slack:	40000	80000
enforced_mode:	0
mode:	0
multi_enter_load:	360
multi_enter_time:	80000
multi_exit_load:	360
multi_exit_time:	320000
param_index:	0
single_enter_load:	90
single_enter_time:	160000
single_exit_load:	90
single_exit_time:	80000
up_threshold_any_cpu_freq:	0
up_threshold_any_cpu_load:	0

With the observation that some values defined in LOS16 on S3Neo have little sense when it comes to balancing the performance/power usage and available documentation.

Available documentation:

Qualcomm Engineering document:

https://developer.qualcomm.com/qfile/28824/lm80-p0436-3_processor_governor_guide.pdf

CPU Governors explained

https://xdaforums.com/showthread.php?t=1767797

Android 7:

https://android.googlesource.com/ke...1.0_r0.2/Documentation/cpu-freq/governors.txt

Android 9:

https://android.googlesource.com/ke....0_r0.91/Documentation/cpu-freq/governors.txt

There are some obscure/Samsung specific settings that I couldn't find info about. However, according to this post:

https://xdaforums.com/showpost.php?p=60519534&postcount=343

- multi_enter_load = DEFAULT_TARGET_LOAD * num_possible_cpus() / 2;

Thats Samsung code in the interactive governor. Normally, it isn't there. And on Quadcore and less phones it isn't needed, but on Octacore handsets it's actually not a bad idea to have.

At the moment I'm overriding the default LOS16 settings with the following lines:

echo 1401600 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 1 > /sys/devices/system/cpu/cpufreq/interactive/io_is_busy
echo 85 > /sys/devices/system/cpu/cpufreq/interactive/target_loads
echo 25000 > /sys/devices/system/cpu/cpufreq/interactive/above_hispeed_delay
echo 1 > /sys/devices/system/cpu/cpufreq/interactive/sampling_down_factor
echo 40000 > /sys/devices/system/cpu/cpufreq/interactive/min_sample_time
echo 40000 > /sys/devices/system/cpu/cpufreq/interactive/timer_rate
echo 40000 > /sys/devices/system/cpu/cpufreq/interactive/timer_slack
echo 0 > /sys/devices/system/cpu/cpufreq/interactive/multi_enter_load
echo 0 > /sys/devices/system/cpu/cpufreq/interactive/multi_enter_time
echo 0 > /sys/devices/system/cpu/cpufreq/interactive/multi_exit_load
echo 0 > /sys/devices/system/cpu/cpufreq/interactive/multi_exit_time
echo 0 > /sys/devices/system/cpu/cpufreq/interactive/single_enter_load
echo 0 > /sys/devices/system/cpu/cpufreq/interactive/single_enter_time
echo 0 > /sys/devices/system/cpu/cpufreq/interactive/single_exit_load
echo 0 > /sys/devices/system/cpu/cpufreq/interactive/single_exit_time

But it's too early to tell a difference, I only used the phone today for 1-2 hours and the battery level is at 81%.

I'm really considering to use (or at least get inspired) the stock ROM CPU scaling governor together with its configuration and would be thankful if someone that is still running stock could provide me with the following outputs (console - shouldn't need root):

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor

1. If it's interactive, then list the options:

ls -al /sys/devices/system/cpu/cpufreq/interactive/

and the values:

cat /sys/devices/system/cpu/cpufreq/interactive/*

2. If it's ondemand, then list the options:

ls -al /sys/devices/system/cpu/cpufreq/ondemand/

and the values:

cat /sys/devices/system/cpu/cpufreq/ondemand/*

With my recent S5Neo flashing crash - flash chip got destroyed, phone bricked - I'm a little afraid to flash too many times the S3Neo, already did it 6-8 times with the back and forth between stock ROM and LOS16. That's why I'd be thankful for some help from the ones still running stock ROM.