[Galaxy Ace II Android Development] ace2nutzer:
Yes, 600Mhz is removed ..

but powersave is already @ 600Mhz :)

the profile=0 manipulates the 800Mhz step @ 600Mhz ... but u'll still see 800Mhz when u check CPU freq with some CPU Stats tools !

But it runs @ 600Mhz.

and balanced, revert it back to 800Mhz ...

so all right now ...

anyway, next kernel will have this script ... because it's more generic and it's also possible to start an profile mixed up ...

because the old one respect, or better say it aspect that the profiles are switched the same way as it does when u switch them over quick settings ... namely:

balanced --> perfor. --> powersave ... ---> balanced ---> perf. and so on.

But with new script it'S more easier to understand what it going on ... and u can jump from powersave to perform. directly..

looks like that:

#### CM Performance Profiles ####

on property:sys.perf.profile=0
# Powersave
# CPU 150/600Mhz GPU 250Mhz
write /sys/kernel/liveopp/arm_step01 ddropp=25
write /sys/kernel/liveopp/arm_step01 pll=0x0005014E
write /sys/kernel/liveopp/arm_step01 varm=0x1d
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 800000
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 150000
write /sys/kernel/mali/mali_boost_low 249600
write /sys/kernel/mali/mali_boost_high 249600

on property:sys.perf.profile=1
# Balanced
# CPU 150/800Mhz GPU 250/400Mhz - Stock Freq's - Kernel default
write /sys/kernel/liveopp/arm_step01 ddropp=100
write /sys/kernel/liveopp/arm_step01 varm=0x25
write /sys/kernel/liveopp/arm_step01 pll=0x00050168
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 800000
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 150000
write /sys/kernel/mali/mali_boost_low 249600
write /sys/kernel/mali/mali_boost_high 399360

on property:sys.perf.profile=2
# Performance
# CPU 150/1000Mhz GPU 250/500Mhz
write /sys/kernel/liveopp/arm_step01 ddropp=100
write /sys/kernel/liveopp/arm_step01 varm=0x25
write /sys/kernel/liveopp/arm_step01 pll=0x00050168
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 1000000
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq 150000
write /sys/kernel/mali/mali_boost_low 249600
write /sys/kernel/mali/mali_boost_high 499200

#### End CM Performance Profiles ####

## Available Freq's for the Profiles:

# CPU:

# 150000
# 800000
# 1000000
# 1100000
# 1150000
# 1200000
# 1250000
# 1300000

# GPU:

# 798720
# 748800
# 698880
# 652800
# 599040
# 549120
# 499200
# 449280
# 399360
# 349440
# 299520
# 249600

#

Also it's now possible to boot up with an other profile than balanced ... by passing those line at the bottom of build.prop:

# powersave
sys.perf.profile=0
OR:
# performance
sys.perf.profile=2

and if u edited now the script in /ramdisk that performance is now 1200 Mhz, and u set sys.perf.profile=2 in build.prop, then it'll boot completely @ 1,2Ghz which allows to boot faster of curse, especially after wipe dalvik-cache or installing an ROM update .. this will speed up the boot time.

Also u can pass:

write /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq 1200000

to user_recovery.rc and set permission to system:system 644 then recovery will run with 150/1200Mhz CPU ... this allows faster backups and restore, also installing things.

But of course, only do that, if u really now @ 100% that such high CPU OC is stable for your Device !