[Galaxy Ace II Android Development] ace2nutzer:
@ doctormord:

but .. it works well!

You have to look at it longer and wait .. sometime commutes it is a bad habit .. it comes up again .. and after few seconds down .. that again is normal and right so .. because from time to time the kernel work (load) and consumption is increasing .. everything correctly!

@ borkins:

with NT App u can only UV / OV up to step 5

1,3625 V is maybe not the max voltage ! from 0x35 to 0x3f it shows 1,3625 V so we thinking it's all the same voltage .. but no !!

During my 1000 Tests, i have found that 0x3a - 3f the phone is much more unstable ! the max. stability i have is on 0x39 !! And Again: 0x35 = 1,3625V and 0x39 theoretically: 1,4125 V I don't know what is here wrong... we all wait what cocafe said when he is back !

When u set the voltages manually with terminal Emulator, ADB .. then leave the Slider to 0.0mV in NT App !

Tips vor OC / UV / OV / Stability:

Set in NT App CPU voltages to: 0.0mV

Set cpu min. freq 200Mhz and max. 800 Set ondemand governor !

Now, beginn at 200 Mhz (step0) and set the voltage in 25mA steps lower.. u see when u have FC, freezes or reboots !

To test stability.. run various Stability test ! (CPU, GPU/CPU) Later open an app.. without stability test, then the freq. is scaling.. it switches very fast.. 200, 400 600 etc. and u have FC or reboots !! That is: in scaling mode (ondemand) we need more Voltage !! (from my experience: on scaling it needs 25mV more) To test this.. is very simple.. just open and close (fast) all apps what u have for around 10 minutes for each step.. and when all was ok.. no FC etc.. then u need to add + 12.5mV on this stable Voltage ! For Example: Stable was 0x35 -----> 0x36 or 0x2f ----> 0x30 or 0x29 -----> 0x2a or 0x2b ----> 0x2c !! So i Hope u understand this :D:D When u done.. next step .. and next... till u have problems :D for me: till 1150 is ok !! And when u are done in...then set max. cpu 1000 and test it again with the same technic... then 1050 .... till 1200 Mhz ! 1250 Mhz is not recommended by cocafe ! And don't forget: set Voltage first then freq. and bevore u make further with the next step.. toggle Offline mode / online mode.. that's make good load to test stability.. i has many time the error: com.android.phone FC !... then add + 12.5mV.. and test again.. but after this FC with android.phone u need to reboot the phone !! because the process don't restart automatically !!!

This is to make sure that the step is 100% stable.... it is very dangerous when u undervolt to much.. it can damage the hardware !! Be careful !

Here is my CPU / GPU Voltages script for init.d:

(just for reference / helping)

#!/system/bin/sh
sleep 90

# enabling set voltage on arm step 3

echo set_volt=1 > /sys/kernel/liveopp/arm_step3

# CPU undervolting

echo varm=0x0d > /sys/kernel/liveopp/arm_step0
echo varm=0x0d > /sys/kernel/liveopp/arm_step1
echo varm=0x1d > /sys/kernel/liveopp/arm_step2
echo varm=0x23 > /sys/kernel/liveopp/arm_step3
echo varm=0x2f > /sys/kernel/liveopp/arm_step4
echo varm=0x33 > /sys/kernel/liveopp/arm_step5
echo varm=0x36 > /sys/kernel/liveopp/arm_step6
echo varm=0x36 > /sys/kernel/liveopp/arm_step7

# GPU undervolting

echo 0 vape=0x18 > /sys/kernel/mali/mali_dvfs_config
echo 1 vape=0x18 > /sys/kernel/mali/mali_dvfs_config
echo 2 vape=0x18 > /sys/kernel/mali/mali_dvfs_config
echo 3 vape=0x1c > /sys/kernel/mali/mali_dvfs_config
echo 4 vape=0x1c > /sys/kernel/mali/mali_dvfs_config
echo 5 vape=0x1c > /sys/kernel/mali/mali_dvfs_config
echo 10 vape=0x29 > /sys/kernel/mali/mali_dvfs_config
echo 11 vape=0x29 > /sys/kernel/mali/mali_dvfs_config
echo 12 vape=0x29 > /sys/kernel/mali/mali_dvfs_config

# set cpu max freq. @ 1150 MHz and min freq @ 400 MHz

echo "400000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo "1150000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq

# set gpu clock @ 540Mhz

sleep 3
echo 537600 > /sys/kernel/mali/mali_gpu_clock

#

Anyone can try this.. but this i luck if it works or not !