[Galaxy S I9000 Android Development] existz:
Well, it just depends on how you use your phone...if u don't use alot of CPU intensive apps, then yes its not going to do much for u...but with running emulators, some games..etc.. that actually use the full potential of the CPU, then overclocking helps out alot.. As for being dangerous, it would take years and years before you see any side effects from ocing, the 2 main things that contribute to ocing being dangerous is heat and voltages... with most people, they can UV 1.2ghz below what the voltages are for stock 1ghz and temps are the same as stock..so there shouldn't be anything to worry about... now as for those that use tegrak app, oc higher...etc, honestly its no concern here, i do not support anything other than the oc/uv that's used in the kernel.. the only app that's actually supported is Voltage Control/Control Freak..as the UV code is wrote for VC , so any third party voltage/frequency adjusting is not supported., the only OC i support is the 1.2ghz in the 1.2ghz version.. I cannot tailor to everyone's needs or to their device, but what's used in Talon is a good medium and works fine for the majority of people.. Even using tegrak app to oc to 1.2ghz and UV is not supported, i don't know how tegraks app works and it uses a seperate module than what's used in the kernel (and all of you can thank tegrak for not sharing sources) , so even 1.2ghz is not the same as setting 1.2ghz with VC.. Other than that, there's nothing i can really do..the oc/uv code used in talon has been tested alot and is a perfect medium, but there are a few out there that cannot oc..there's nothing i can do about that.

As for 5 freqs and 6 freqs, I've mentioned this numerous times, and wont be switching to 6 steps unless alot of changes are made. Keeping it the same number as stock frequencies helps ensure that everything is scaling like it should be and that the correct DVFS settings are applied the way they were ment to be ...for example on stock frequencies L2 would be 400mhz, if u add another step then L2 becomes 800mhz, there's alot of these settings through out the source, and i do not know where tthey are all at, so just adding in the extra step can cause USB, cpufreq driver, wifi, touch driver..etc..etc run at double the speeds it was ment to, which can cause instability and other issues..so unless someone can 110% say they know where every single one is in the source, i wont be changing it..and honestly there's really no point in having the extra 1ghz step when using 1.2ghz, its only skipped through for a brief second from time to time, which can cause things to not be as smooth as without it.. We use the ondemand governor and it scales "mainly" from min to max, briefly hitting one or two of the others from time to time when scaling up/down, so the extra step is just causing it to take longer to get to max clock, or to jump down to min clock. Things do not work the way they did on froyo with conservative governor, where it only scaled to a certain frequency when it was needed, so with that then yea, 1ghz might serve a point..but with ondemand and the way things scale in talon, the extra step is useless and just slowing things down... The only reason it would be needed would be as mentioned above, to keep some load off of 1.2ghz so a couple people can oc with lower quality devices (which most that oc really never need the extra CPU power anyways), but ur only talking about seconds/minutes of use over hours/day of use.. again, i cannot tailor to meet everyone's needs, only the majority..