Since its a proven fact that no Amlogic CPU can go above 1536mhz (link ), is there a way we can enforce the cpu to cap @ 1536 instead of going to 2016 (Of course the cpu never goes to that speed but maybe its using the voltage for the virtual speed) ?
would changing this section inside init.amlogic.board.rc have the desired effect?
from
on boot
setprop ro.radio.noril true
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 2016000
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 96000
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor hotplug
write /sys/class/freq_limit/limit 0
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_dflt_freq 2016000
To
on boot
setprop ro.radio.noril true
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 1536000
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 96000
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor hotplug
write /sys/class/freq_limit/limit 0
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_dflt_freq 1536000
I did a test with Antutu and while score was the same on both runs (give or take), Antutu still showed the cores having a max speed of 2016 (and the cores going up to that speed). My cheap powermeter was showing 0.5-1w less consumption with the 1536 setting during the various tests but i am not sure how valid that is because i have the box connected with 5ghz wifi and maybe that is the reason for the flactuation (or my meter is not very accurate)
I used a custom image with fixed root and fully debloated (no crap running in the background). Box is a95x (s905x 2/16)
Can anyone else confirm this? Is there any other way to do it properly?