Originally Posted by _n0p_

128-1344, ondemand.

Which kernel did you use Sergei?

DSC Team Phoenix Universal

Originally Posted by _n0p_

DSC Team Phoenix Universal

Is it capable over 1267 MHz for overclocking?

Originally Posted by sinan33

Is it capable over 1267 MHz for overclocking?

You see, in previous kernel builds I made an error in stepping table values, so 1267 was actually 1344, and 998 was 1075.
Now I fixed it.
Sorry

Originally Posted by _n0p_

You see, in previous kernel builds I made an error in stepping table values, so 1267 was actually 1344, and 998 was 1075.
Now I fixed it.
Sorry

So how can i set it from init.postboot.streak.sh?

Quite simple.

 #CPU
echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 70 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/up_threshold
echo 30 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/down_threshold
echo 200000 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/sampling_rate
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/sampling_down_factor
echo 128000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
#echo 245760 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 998400 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 50 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/freq_step

in postboot.

Change "conservative" to "ondemand", 998400 to 1344000.
Reboot.
Note that I personally find overclock more stable with undervoltage on.
Refer to Phoenix Universal kernel in DSC thread on enabling UV manually.
More, kernel sets high frequencies using 384 and 768 MHz as middle values, so it may be safe using ondemand - TPS chip should handle it.

Also, let's move this discussion elsewhere, as it's off topic here. Thank you.

Originally Posted by _n0p_

Quite simple.

 #CPU
echo "conservative" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 70 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/up_threshold
echo 30 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/down_threshold
echo 200000 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/sampling_rate
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/sampling_down_factor
echo 128000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
#echo 245760 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 998400 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 50 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/freq_step

in build.prop.

Change "conservative" to "ondemand", 998400 to 1344000.
Reboot.
Note that I personally find overclock more stable with undervoltage on.
Refer to Phoenix Universal kernel in DSC thread on enabling UV manually.
More, kernel sets high frequencies using 384 and 768 MHz as middle values, so it may be safe using ondemand - TPS chip should handle it.

Also, let's move this discussion elsewhere, as it's off topic here. Thank you.

Thank you Sergei,i was using these settings Just changed 1267200 to 1344000

Originally Posted by hunderteins

LuckyPatcher and other programs have a problem with optimized dalvik-cache for classes that aren't verified. So I set up

dalvik.vm.dexopt-flags=v=a,o=v,u=y,m=y

it is like: verify=all dexopt=verified uniprocessor=yes registermaps=yes

Now LuckyPatcher works again, the boot takes not really more time, cache-size is the same as before and this uses register mapping. I'll give it a try a week or two.

have a nice weekend,
hunderteins

Thanks for all your work, is this now confirmed as a definitive tweak that doesn't break anything?