[Captivate Android Development] SetiroN:
I'm sorry I ended up teasing you guys, it really wasn't my intention at all... gotta love the decication of some tho, I really appreciate it! :)

Unfortunately the forums logged me out while I was replying and attachments disappeared. As I started reuploading, I got a call for an emergency at work and I literally had to run; if you saw me online later on, I was just browsing from my phone.

Anyway by the time I got home Xcaliburhand's update was out and I decided to skip 1.51 altogether and go straight to 1.52

Well, that remains to be proven. If you're referring to team whiskey's manhattan project, it was a misinterpretation on their side: 1.6GHz was just displayed, not actually set, and benchmark scores were only higher because they were slowing down system time

Looks just like a ****ed up lagfix, nothing odin w/ repartition (or oneclick) can't solve.

Hardware damage from overclock at normal volts is highly unlikely.

v1.5.2 OUT

DELETE USER GENERATED SCRIPTS IN /system/etc/init.d/ BEFORE UPGRADING

(remember it's necessary to unlock higher frequencies from both freq_table and Xan's app)

- implemented Xcaliburinhand's wired headset fix (only works with mic'ed headsets, not with stereo earbuds)

- mount /system R/W - could be dangerous, but solves script creation issues

- optimized frequency jumps for better battery life

- optimized RAM utilization (minfree tweaks)

- workaround for the highest frequency step being sometimes briefly used during bootup and recovery operation

- effectively set 1200MHz as the default frequency

- corrected wrong display of highest frequency in Quadrant

- included frequencies scheduler script in the CWM zip package, with a small visual aid

- reorganized performance levels with a few additions:

1600MHz CPU	200MHz GPU	1350mV

1552MHz CPU	194MHz GPU	1350mV

1504MHz CPU	188MHz GPU	1350mV

1464MHz CPU	183MHz GPU	1300mV

1456MHz CPU	208MHz GPU	1300mV

1400MHz CPU	200MHz GPU	1300mV

1344MHz CPU	192MHz GPU	1300mV

1288MHz CPU	184MHz GPU	1300mV

1200MHz CPU	200MHz GPU	1300mV

1000MHz CPU	200MHz GPU	1275mV

800MHz CPU	200MHz GPU	1200mV

400MHz CPU	200MHz GPU	1050mV

200MHz CPU	200MHz GPU	950mV

100MHz CPU	100MHz GPU	950mV

One of the various internal clocks regulates the GPU's as well as other internal components' frequency. Lower clocks have a chance to cause instability as well, so you might want to try an higher step with the GPU closer to stock (200). Those internal components play mostly a role in benchmarks like Linpack, although actual performance during normal use relies predominantly on CPU clock.

***RESET ALL UV SETTINGS BEFORE UPGRADING TO HIGHER VERSIONS***

***IF YOU'RE HAVING SLEEP DEATH ISSUES, REVISE UV SETTINGS***

*** FINDING YOUR OVERCLOCK ***

In order to enable a certain frequency two requirements must be met.

Your target frequency:

- has to be equal or lower than the "Limit max clock to" value in Xan's Voltage Control

- its corresponding value in /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table has to be set to '1'

and

- you need to switch /sys/devices/system/cpu/cpu0/cpufreq/update_states to 1 (it'll immediately go back to 0) to actually enable the new table

Those files can either be manually edited or modified through an 'echo' command, which is much more convenient if you're in front of a PC and able to use ADB.

Let's say you want to enable 1344MHz - first of all, set Voltage Control's max clock to 1600MHz (don't worry that frequency is not going to be set unless specified on the freq table, it's just an upper limiter), now let's take a look at the frequencies:[/b]

1600MHz CPU	200MHz GPU	1350mV
1552MHz CPU	194MHz GPU	1350mV
1504MHz CPU	188MHz GPU	1350mV
1464MHz CPU	183MHz GPU	1300mV
1456MHz CPU	208MHz GPU	1300mV
1400MHz CPU	200MHz GPU	1300mV
1344MHz CPU	192MHz GPU	1300mV
1288MHz CPU	184MHz GPU	1300mV
1200MHz CPU	200MHz GPU	1300mV
1000MHz CPU	200MHz GPU	1275mV
800MHz CPU	200MHz GPU	1200mV
400MHz CPU	200MHz GPU	1050mV
200MHz CPU	200MHz GPU	950mV
100MHz CPU	100MHz GPU	950mV

1344MHz corresponds to the 7th value:

adb shell
$ su (authorize on the phone)
# echo 0 0 0 0 0 0 [color=red]1[/color] 0 1 1 1 1 1 1 > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
# echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/update_states

Frequency enabled. Is it stable? Good, let's try 1400:

7th value back to 0, 6th value to 1, update_states to 1

# echo 0 0 0 0 0 [color=red]1[/color] [color=blue]0[/color] 0 1 1 1 1 1 1 > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
# echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/update_states

Done.

Find your frequency bearing in mind GPU clocks different from 200MHz have a chance of causing instability.

*** MAKING VOLTS AND FREQUENCIES STICK THROUGH REBOOTS ***

You may need to navigate /system/etc/init.d/ with root explorer and mount r/w first. If you don't have it use ADB or a terminal emulator:

adb shell
$ su
# mount -o rw,remount /dev/stl9 /system
# chmod 777 /system/etc/init.d

To automatically enable additional frequencies on boot, after updating Xan's app to v2.0rc2, recreate the boot script with your preferred max frequency set.

Then go edit (or create if you didn't flash from cwm) /system/etc/init.d/S99_freq_scheduler.sh inserting 1 for frequencies you want to be enabled and 0 for those you'd like to disable:

#!/system/bin/sh
#SET OC - below are GHz decimals (i.e. 1.60GHz, 1.55GHz, 1.50GHz and so on)
#60 55 50 46 45 40 34 28 20 00 8 4 2 1
echo 0 0 0 0 0 0 0 0 1 1 1 1 1 1 > /sys/devices/system/cpu/cpu0/cpufreq/states_enabled_table
echo 1 > /sys/devices/system/cpu/cpu0/cpufreq/update_states