[Galaxy Ace II Android Development] ChronoMonochrome:
R2.7.5

New build is up :)

Changelog:

not so much for now, so it's still R2.7.x

- partially reverted LiveOPP voltage autocalibration. To be honest, I'm tired to write and test the newest and newest algorithms of calibration, which do not live up to expectations. Somehow it was stable even without calibration on old builds with LiveOPP 1.0.1. Current liveopp voltage reverted to that one, that was used in TeamCanjica's kernels. Now it recalibrates only 800 and 1000 MHz steps (these steps used AVS voltage in LiveOPP 1.0.1). Also removed some unneeded steps, now 200 MHz is minimum scaling cpufreq. As it turned out, there's no big difference in power consumption between 100 MHz and 200 MHz, and probably even less between 30 and 100.

- fixed unstable mali tunables and added interface mali_scaling_dynamic

echo 1 > /sys/kernel/mali/mali_scaling_dynamic

When mali_scaling_dynamic is used, mali will scale between mali_boost_low and mali_boost_high using all steps between these mentioned. mali_stats provides statistics about mali utilization on each step.

- removed some GPU freq steps

I also found a trick to overclock PLLDDR even more than 975 MHz. Still imperfect, as it requires to use shell script, but hopefully stable:

#!system/bin/sh
set -x

# Abb-ponkey doesn't have its own wakelock
# so as temporary dirty approach, we use there dt2w wakelock while the script running.

echo Y > /sys/module/doubletap2wake/parameters/use_wakelock
echo 1 > /sys/module/doubletap2wake/parameters/enable

MINFREQ="/sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq"
MAXFREQ="/sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq"

MINFREQVAL=`cat $MINFREQ`
MAXFREQVAL=`cat $MAXFREQ`
echo $MINFREQVAL > $MAXFREQ

echo 1 > /sys/kernel/abb-ponkey/emulator
sleep 2
echo 0x5017f > /sys/kernel/liveopp/pllddr
sleep 0.5
echo 0x50180 > /sys/kernel/liveopp/pllddr
sleep 0.5
echo 0x5018f > /sys/kernel/liveopp/pllddr
sleep 0.5
echo 1 > /sys/kernel/abb-ponkey/emulator

echo $MAXFREQVAL > $MAXFREQ

echo N > /sys/module/doubletap2wake/parameters/use_wakelock
echo 0 > /sys/module/doubletap2wake/parameters/enable

Before you run this script, make sure that no any processes are causing big load on CPU even in idle(usually multimedia scanner may cause huge load on CPU, wait until it'll complete its work or kill it manually), otherwise it may reboot. Don't turn off screen(if you plan to run it via adb).

When this script is running, the screen will turned off itself for 3,5 seconds, don't touch anything in this time, a screen will be then turned on automatically. After all you can adjust PLLDDR in limits 0x50181 and 0x5019x (x - last digit - 0,1,2... etc. the maximum stable freq is still unknown, and maybe will turn out after some tests). It seems only 0x50180 value cause reboot. [MENTION=4832589]cocafe[/MENTION], [MENTION=3329816]mkaluza[/MENTION], [MENTION=4996458]1N4148[/MENTION], any ideas how to fix it?

Don't move this script to init.d, since it may cause bootloop (screen and some related clocks needs to be powered down during running script, but this is not possible at boot).

What is benefit from all that? See the Nenamark test result. :D

My settings: CPU 200-1200 MHz Dynamic, GPU 512-716 MHz Dynamic scaling, DDR 1121MHz.

(tweaks for mali)

# sleep 30 # uncomment this line, if you would like to add it to init.d

echo 0 > /sys/module/mali/parameters/mali_debug_level
#echo 6 > /sys/module/mali/parameters/mali_oskmem_allocorder
echo 50331648 > /sys/module/mali/parameters/pre_allocated_memory_size_max

MALI=/sys/kernel/mali

# workaround of voltage override by NT app

chmod 755 $MALI/*
echo idx=6 > $MALI/mali_boost_low
echo idx=9 > $MALI/mali_boost_high
echo threshold=48 > $MALI/mali_boost_low
echo threshold=150 > $MALI/mali_boost_high
chmod 444 $MALI/*

Well, somewhere I read that ace2 development now is dead.

I hasten to assure this is not true, while we develop the kernels :p

Well, I think ours mali400 performance now has increased as strong as it was possible ever :)

Regards, Chrono