Develop Bugs

[Kernel] Lightspeed 0.1.1 - Faster than fast enough.

FOR 1.5 ROMS ONLY.
Thanks to teknologist, maxisma, toastcfh, and all those who contributed to cracking the CPU open for overclocking.
Looking at the CDMA forums, it seems they were a step ahead of us with their kernel speedups. With help from their work, and particularly, from toastcfh, I've been able to patch and compile a kernel based on teknologist 1.9 with added features and speed.
Added features and changes so far:
- BFS, brainfuck scheduler. Basically, helps the CPU respond faster.
- Overclock. Up to 768MHz is enabled, but defaults to a safer 595MHz. It should be compatible with SetCPU. Be sure to use the custom setting.
- Deadline I/O scheduler. It should make file read and write operations a tad faster. We'll see if it really does.
Git repo: http://github.com/Soaa-/-lightspeed/tree/master/kernel-hero/
It runs at 595MHz! How do I make it faster?
Download and install SetCPU. It's available for free on xda-developers, but you can support the author by buying a copy on the market. Launch SetCPU and pick the custom option.
My phone doesn't wake sometimes! Or, it wakes and the crashes!
Use SetCPU and set the CPU governor to 'performance'. Try lowering the clock speed if the problem persists.
Can I flash this on recovery?
The first overclocked kernel was available only as sources, and binaries had to be flashed manually. Lightspeed comes as a standard update.zip package to be flashed through recovery though.
Does Wi-fi work?
Yes.
Does compcache/ramzswap work?
No idea. I don't use it.
Is it noticeably faster?
Yes. This isn't a 5% increase in speed, where the difference is only seen through benchmarks. Most phones can handle 691MHz, which is a 30% increase in speed. The lucky ones who can clock up to 768MHz get a 45% increase. The net result is a more responsive phone.
Does the CPU frequency scale to usage?
It can, if you keep the ondemand CPU governor. However, there have been reports of instability using the ondemand governor, so the performance governor is recommended instead.
Do you accept donations?
Not yet, as my work so far has just been putting other people's work together. My priority now is to make our phones better, not to make money.
0.1.1
Integrated setcpu.txt into update.zip.
0.1
Initial release

Hi,
Looks great! Does it work in 2.1 roms?
Greetz

I want to know also
Does it work on 2.1 oms ??

Sorry, the kernel is made for 1.5 ROMs only. The only decent kernel for 2.1 is still the same leaked one from a while back, I think.

ok, gonna try it now on a 1.5 rom, with setcpu.
let you know if speed is there

i use a stock rom, and have the recovery menu so can i put the zip on the sd card and then flash it ?

I am also interested in a guide on how to install/flash this properly.

Just like knudsen81 said. Everything working perfect with CPU running on 595Mhz.

From what I see, it should be flashed like all other kernels so just like ROM or radio.
Does this kernel scales overclocking depending on CPU load? For ex. lowers when idle or screen turned off.

ZeppeMan said:
Just like knudsen81 said. Everything working perfect with CPU running on 595Mhz.
Click to expand...
Click to collapse
when setcpu launches, it doesnt have the "auto detect" option
when i click on custom, it shows 528 max and no more..
what am i doing wrong here?
flashed the update.zip like a normal rom/radio btw.

Good job! looking forward for testing. What's actually missing from making overclocking work with 2.1?

mixxy said:
when setcpu launches, it doesnt have the "auto detect" option
when i click on custom, it shows 528 max and no more..
what am i doing wrong here?
flashed the update.zip like a normal rom/radio btw.
Click to expand...
Click to collapse
I used Overclock widget to see the speed of the CPU. I only wanted to confirm if the 595Mhz was true
Also Linpack score went from 2.3 to 2.6.

mixxy said:
when setcpu launches, it doesnt have the "auto detect" option
when i click on custom, it shows 528 max and no more..
what am i doing wrong here?
flashed the update.zip like a normal rom/radio btw.
Click to expand...
Click to collapse
Create a file named setcpu.txt at the SD card (so it will be /sdcard/setcpu.txt)
and enter the following into that file:
Code:
96000,115200,134400,153600,172800,192000,211200,230400,249600,268800,288000,307200,326400,345600,364800,384000,403200,422400,441600,460800,480000,499200,518400,537600,556800,576000,595200,614400,633600,652800,672000,691200,710400,729600,748800,768000
This will allow setting frequencies from 96 to 768 MHz via SetCPU

Thanx 4 the great work.
2 questions.
first, what does "Git repository" means and when will u release it?
second, can i flash it over Modaco 3.2 through recovery mode?
sorry 4 my bad english.

k0rner said:
Create a file named setcpu.txt at the SD card (so it will be /sdcard/setcpu.txt)
and enter the following into that file:
Code:
96000,115200,134400,153600,172800,192000,211200,230400,249600,268800,288000,307200,326400,345600,364800,384000,403200,422400,441600,460800,480000,499200,518400,537600,556800,576000,595200,614400,633600,652800,672000,691200,710400,729600,748800,768000
This will allow setting frequencies from 96 to 768 MHz via SetCPU
Click to expand...
Click to collapse
thanks for the help, lets try this out and see what happens =P

worked like a charm, thanks a lot =)

Does the camera work?

Camera, WiFi should work because it's an (old) 1.5 Kernel.

Other overclocked kernel works faster than this one (and with this one i've freezed ..) ..
With the other linpack gives me 3.2 3.3
with this 2.6 at max ..
:/

Flemmard said:
Other overclocked kernel works faster than this one (and with this one i've freezed ..) ..
With the other linpack gives me 3.2 3.3
with this 2.6 at max ..
:/
Click to expand...
Click to collapse
Have you set the cpu to 768? because the other kernal runs at 710 by default where as this runs at 595 but can be clocked all the way up to 768.
Please read the forums before complaining it doesn't do something.

help needed SETCPU problems

Hey guys im having trouble with my phone when setcpu is running. When ever i come out of lock screen it takes a few seconds to be able to do stuff on my phone, like its waking up from sleep. Also some times i get this message and it has to reboot.
"Sorry activity htc sense (in application HTC Sense) is not responding."
Im running the 2.6.32.15 king # 4 kernel.
My set CPU settings are on 1.15 GHz max and 460800 MHz min. Im running conservative at the moment but it does it on other scaling like performance and on demand. my setting for screen off is 460min 614 max.
Is there anything im doing wrong? or should i be using a different kernel? What kernels are the best? Thanks

I would bump up the lower end to about 600. I have have issues lower than that coming out of sleep.

im running virtuous 2.7
power saving kernel
Main Profile is 245-998 ondemand
Screen Off is 245-384 ondemand
I do not have that problem... but it would be a lie if I told you i didn't before!
I was having this problem you are talking about when my main profile was set to conservative.
EDIT: Back up your setcpu + settings in titanium... Uninstall it (or freeze it) and see if the kernel can run it just fine cause it probably will. Most kernels already have the settings for optimum performance and even the devs who make them (like hydra) say that it will work best without setcpu.
Source: http://www.hydrakernel.net/hydra_kernels_information.htm
"I recommend not using the setcpu controls or governor with these kernels. Let the stock governor do the work. If you have setcpu installed I recommend clearing out the settings before flashing the kernels. You can use it to monitor cpu speeds or an app from the market called systempanel if so desired."

[Q] HAVS + CPU Control & [Q] Battery Applications

I have a HAVS kernel (Net's 4.2.2 SBC CFS Aggressive HAVS) and as I understand it any sort of CPU Tweaking application will cause conflict and probably a system crash, correct?
Also, can some recommend me any applications that compliment Juice Defender well. I have Juice Plotter already. I am looking for an aggressive auto task killer that's customizable along with any other suggested applications. Thank you!

A system crash is a possibility but they will basically just counteract each other and either make your battery life worse or give a performance hit.
SetCPU helps dynamically underclock/overclock based on certain scenarios. You can set what scenarios you want. Another option is AutoKiller. It isn't Auto Task Killer. Its a different application. Not quite sure how this works but you can research it. However Froyo does a good job managing most applications.
But if you are looking for customization I would go with SetCPU and AutoKiller

Thank's however since I'm running a HAVS kernel I won't use SetCPU. However I will look into Autokiller. Thanks

Vulf said:
Thank's however since I'm running a HAVS kernel I won't use SetCPU. However I will look into Autokiller. Thanks
Click to expand...
Click to collapse
o.o a ton of people use set cpu with havs... its not setting voltages... its setting the cpu speed...

I just installed setcpu and ran it. My phone crashed about 10 seconds after I allowed root access. Tried twice more with same results.

aimbdd said:
o.o a ton of people use set cpu with havs... its not setting voltages... its setting the cpu speed...
Click to expand...
Click to collapse
Its the governors that conflict. Not sure on the exact technical specifics but think of it like OCing a comp.
Some mobos have dynamic OCing. They adjust voltages based on CPU draw. If SetCPU sets CPU speed but HAVS reduces voltage... it would cause a crash. Its always better to have one thing deal with both CPU and voltage.
I'm not a full blown expert with kernels and how they function. All I know is to not mess around with SetCPU + HAVS kernels. It was always unstable or a massive battery drain for me based on my testing.

sekigah84 said:
Its the governors that conflict. Not sure on the exact technical specifics but think of it like OCing a comp.
Some mobos have dynamic OCing. They adjust voltages based on CPU draw. If SetCPU sets CPU speed but HAVS reduces voltage... it would cause a crash. Its always better to have one thing deal with both CPU and voltage.
I'm not a full blown expert with kernels and how they function. All I know is to not mess around with SetCPU + HAVS kernels. It was always unstable or a massive battery drain for me based on my testing.
Click to expand...
Click to collapse
Setcpu does not do anything that a user with root access and terminal emulator can't. Setcpu does not actively do anything related to cpu speed or voltage in way shape or form. What setcpu does do is set the min and max speed the cpu can scale to and the parameters specific to the governor (up-threshold for one).
The governors also don't conflict with setcpu because setcpu does not do anything that a governor does.
The only things setcpu does is allow you to specify what governors and cpu speeds to use during screen on/off, charging, and battery levels through the use of a gui.
Technically setcpu does not interfere with havs its the settings that cause the issues. Again, what setcpu does any root user with te can do. If you issue the wrong settings in te and your device "crashes" is the user going to blame the settings or te? With the way some people are they would probably claim te interferes with havs instead of realizing that the setting combo they issued is not stable.
Setcpu is a great gui to tweak cpu parameters but don't confuse it with an app that actually controls the dynamic cpu frequency scaling or its voltages.

lovethyEVO said:
Setcpu does not do anything that a user with root access and terminal emulator can't. Setcpu does not actively do anything related to cpu speed or voltage in way shape or form. What setcpu does do is set the min and max speed the cpu can scale to and the parameters specific to the governor (up-threshold for one).
The governors also don't conflict with setcpu because setcpu does not do anything that a governor does.
The only things setcpu does is allow you to specify what governors and cpu speeds to use during screen on/off, charging, and battery levels through the use of a gui.
Technically setcpu does not interfere with havs its the settings that cause the issues. Again, what setcpu does any root user with te can do. If you issue the wrong settings in te and your device "crashes" is the user going to blame the settings or te? With the way some people are they would probably claim te interferes with havs instead of realizing that the setting combo they issued is not stable.
Setcpu is a great gui to tweak cpu parameters but don't confuse it with an app that actually controls the dynamic cpu frequency scaling or its voltages.
Click to expand...
Click to collapse
Ahh there. someone more knowledgable then me explains it perfectly.
I've run set cpu plus haves kernel for the last month... as have almost everyone using savagedzen.. thats what they recommend. If it was causing issues i am sure we would know by now. 100%stable... 0 random reboots! (well... accept for when i didn't follow directions xD)

aimbdd said:
Ahh there. someone more knowledgable then me explains it perfectly.
I've run set cpu plus haves kernel for the last month... as have almost everyone using savagedzen.. thats what they recommend. If it was causing issues i am sure we would know by now. 100%stable... 0 random reboots! (well... accept for when i didn't follow directions xD)
Click to expand...
Click to collapse
I believe you and am not discrediting you but how come when I run SetCPU on a kernel with HAVS, it crashes? (Tried 4.3.1 and 4.2.2.) I moved the maximum value from the default 944 by maybe one or 2 notches up and the device freezes and crashes. Maybe Netarchy's kernels aren't compatible with CPU Tweaking programs? Anyone out there running a Netarchy Kernel w/ HAVS + SetCPU successfully?

Vulf said:
I believe you and am not discrediting you but how come when I run SetCPU on a kernel with HAVS, it crashes? (Tried 4.3.1 and 4.2.2.) I moved the maximum value from the default 944 by maybe one or 2 notches up and the device freezes and crashes. Maybe Netarchy's kernels aren't compatible with CPU Tweaking programs? Anyone out there running a Netarchy Kernel w/ HAVS + SetCPU successfully?
Click to expand...
Click to collapse
Again, it is not setcpu it is your settings. You said you moved the slider "one or two notches up" (overclock) from the default 944? The evos default max is 998. Either way, with what you said you are overclocking and your device cannot handle the overclocked speed.
Like I said, you can do the exact same thing that setcpu does through terminal emulator. Instead of blame setcpu you should observe the speed/governor combo you are using.
I can oc my evo to 1.26 on my personal kernel without it rebooting on certain governors but on others it would reboot randomly and I don't set cpu parameters through setcpu, I use te, init scripts, and tasker.

lovethyEVO said:
Setcpu does not do anything that a user with root access and terminal emulator can't. Setcpu does not actively do anything related to cpu speed or voltage in way shape or form. What setcpu does do is set the min and max speed the cpu can scale to and the parameters specific to the governor (up-threshold for one).
The governors also don't conflict with setcpu because setcpu does not do anything that a governor does.
The only things setcpu does is allow you to specify what governors and cpu speeds to use during screen on/off, charging, and battery levels through the use of a gui.
Technically setcpu does not interfere with havs its the settings that cause the issues. Again, what setcpu does any root user with te can do. If you issue the wrong settings in te and your device "crashes" is the user going to blame the settings or te? With the way some people are they would probably claim te interferes with havs instead of realizing that the setting combo they issued is not stable.
Setcpu is a great gui to tweak cpu parameters but don't confuse it with an app that actually controls the dynamic cpu frequency scaling or its voltages.
Click to expand...
Click to collapse
Couldn't have said it better. The common misconception around these parts is that SetCPU has some negative effect on kernels with HAVS and this is just untrue.

Maybe I'm getting some terrible luck. I've always gotten negative results from using both SetCPU and HAVS. Tried different settings and recommended settings from others. As well as trying to tweak it myself. Not working so I just removed it and HAVS worked better on its own.
Sorry for the misinformation.

sekigah84 said:
Maybe I'm getting some terrible luck. I've always gotten negative results from using both SetCPU and HAVS. Tried different settings and recommended settings from others. As well as trying to tweak it myself. Not working so I just removed it and HAVS worked better on its own.
Sorry for the misinformation.
Click to expand...
Click to collapse
The common practice with setcpu is to use it to underclock when sleeping. Depending on the governor you use (besides powersave) you are actually causing the cpu to struggle when completing tasks if you limit the max to 245 for example. During sleep if it needs to perform a task and that task would normally complete in 1 second at 998 mhz imagine how much longer it would take if it was capped at 245.
I have had better results not underclocking while sleeping. I would suggest using setcpu to specify to use the conservative governor when sleeping, ondemand/interactive/smartass when screen on (depending on which one you want), and interactive/ondemand while charging without under/overclocking at all and using the default freqs (245 - 998). I'm certain you would be surprised at how your evo behaves after that.

I don't know though... if race to idle applied here why would phone manufacturers ever under clock their phone? It kind of confuses me. Rti applies to computers but not phones? doesn't make sense.

aimbdd said:
I don't know though... if race to idle applied here why would phone manufacturers ever under clock their phone? It kind of confuses me. Rti applies to computers but not phones? doesn't make sense.
Click to expand...
Click to collapse
My last post may have been a bit confusing so I will clarify. When I said underclock I was referring to the practice of capping the max freq to 245 which is what most people do. If you cap the freq at 245 you are essentially underclocked all the time and would cause your cpu to work harder.
The evo underclocks automatically when the cpu load is low enough (idle for example) to save on power, reduce temps, and to basically keep the system running. But I would assume that most of us who have used setcpu have seen how lousy the evo runs when it can't scale up (locked at 245) when using the evo. The governors will underclock the cpu on their own if the device reports it does not need the higher freqs and this occurs during sleep/screen off as well.

Ugh this is quite frustrating. Perhaps it's the current kernel I'm using that's the problem?

Vulf said:
Ugh this is quite frustrating. Perhaps it's the current kernel I'm using that's the problem?
Click to expand...
Click to collapse
Have you done testing to make sure your phone plays well with the more aggressive kernel? If using SetCPU is causing your phone to reboot then you may want to adjust your overclock, switch to the less aggressive kernel, or update to the newest netarchy SBC powered kernel; 4.3.2.

freeza said:
Have you done testing to make sure your phone plays well with the more aggressive kernel? If using SetCPU is causing your phone to reboot then it you may want to adjust your overclock, switch to the less aggressive kernel, or update to the newest netarchy SBC powered kernel; 4.3.2.
Click to expand...
Click to collapse
I'm not sure how I would go testing my kernel? I mean I've been using it since yesterday morning and there haven't been any FC's/phone crashes or anything strange so I guess the aggressive HAVS works well with my phone. I'll try upgrading to 4.3.2. I'm assuming it works fine for you?

freeza said:
Have you done testing to make sure your phone plays well with the more aggressive kernel? If using SetCPU is causing your phone to reboot then it you may want to adjust your overclock, switch to the less aggressive kernel, or update to the newest netarchy SBC powered kernel; 4.3.2.
Click to expand...
Click to collapse
This.
Very sound advice and yes some evos can't undervolt as well as others. Always remember too that the stock kernel for the evos use CFS. If you are using a bfs kernel that could also cause issues. Some evos run better with bfs versus cfs but it's really going to come down to the amount of time you want to put into testing and confirming what your evo likes.

Vulf said:
I'm not sure how I would go testing my kernel? I mean I've been using it since yesterday morning and there haven't been any FC's/phone crashes or anything strange so I guess the aggressive HAVS works well with my phone. I'll try upgrading to 4.3.2. I'm assuming it works fine for you?
Click to expand...
Click to collapse
Yeah, it does. How far are you trying to overclock before your phone freezes/reboots?

[Q] Kernels ain't working for me

Hello there,
I've been flashing kernels since I was in LeeDroid Froyo and got no problems. However since I switched to GB based roms such as RCMix3D and TB Fusion, my phone always freezes when I try setting Kernel-Lee-V3.1.1-2.6.35.13-CALLREC or MDJs v19 to maximum overclock so I have no choice to but to stay on stock kernel. I have no ext3/ext4 partition on my SD card in case you ask.
Current ROM: TB Fusion 1.1.2
Radio: 12.54.60.25U_26.09.04.11_M2
Any idea what should I do to solve this issue?

golokipok said:
Hello there,
I've been flashing kernels since I was in LeeDroid Froyo and got no problems. However since I switched to GB based roms such as RCMix3D and TB Fusion, my phone always freezes when I try setting Kernel-Lee-V3.1.1-2.6.35.13-CALLREC or MDJs v19 to maximum overclock
Click to expand...
Click to collapse
uoooo this is sooo dangerous for your handset... u can "smoke" it...
Any idea what should I do to solve this issue?
Click to expand...
Click to collapse
yes, your handset freezes because the overclock that u do its too high... underclock it at 1200-1400mhz & try...
and configure SET CPU features... like the standby status, etc....but do it with common sense....
think about that DHD proccessor goes by default at 1gz, really when we overclock the processor we are putting in danger the security of our device

SERGI.3210 said:
uoooo this is sooo dangerous for your handset... u can "smoke" it...
yes, your handset freezes because the overclock that u do its too high... underclock it at 1200-1400mhz & try...
and configure SET CPU features... like the standby status, etc....but do it with common sense....
think about that DHD proccessor goes by default at 1gz, really when we overclock the processor we are putting in danger the security of our device
Click to expand...
Click to collapse
Haha! I know that overclocking is quite dangerous. Back on the froyo days, my phone is quite stable around 1.8ghz so I'm just wondering why is this happening (maybe my phone's processor is starting to fry up? ). Is there any effect if I'm using smartass profile on those kernels I've mentioned?

golokipok said:
Haha! I know that overclocking is quite dangerous. Back on the froyo days, my phone is quite stable around 1.8ghz so I'm just wondering why is this happening (maybe my phone's processor is starting to fry up? ).
i hope that the processor works or not works (don´t crashes a little bit...)
but the reason of your freezes maybe (almost sure) because froyo & gingerbread don´t works at the same form, and gingerbread need more resources & stability for to work correct... don´t forget that the kernel manages the hardware...
if u force it......... u know what can happen...
golokipok said:
there any effect if I'm using smartass profile on those kernels I've mentioned?
Click to expand...
Click to collapse
it´s possible, take this explanation, read and judge by yourself what´s the better cpu governor...
smartass (Best explanation i've found paraphrases to: based on interactive, but better.)
----
ondemand
Available in most kernels, and the default governor in most kernels. When the CPU load reaches a certain point (see "up threshold" in Advanced Settings), ondemand will rapidly scale the CPU up to meet demand, then gradually scale the CPU down when it isn't needed. - SetCPU website
conservative
Available in some kernels. It is similar to the ondemand governor, but will scale the CPU up more gradually to better fit demand. Conservative provides a less responsive experience than ondemand, but can save battery. - SetCPU website
performance
Available in most kernels. It will keep the CPU running at the "max" set value at all times. This is a bit more efficient than simply setting "max" and "min" to the same value and using ondemand because the system will not waste resources scanning for the CPU load. This governor is recommended for stable benchmarking. - SetCPU website
powersave
Available in some kernels. It will keep the CPU running at the "min" set value at all times. - SetCPU website
userspace
A method for controlling the CPU speed that isn't currently used by SetCPU. For best results, do not use the userspace governor. - SetCPU website
Interactive
The 'interactive' governor has a different approach. Instead of sampling the cpu
at a specified rate, the governor will scale the cpu frequency up when coming
out of idle. When the cpu comes out of idle, a timer is configured to fire
within 1-2 ticks. If the cpu is 100% busy from exiting idle to when the timer
fires then we assume the cpu is underpowered and ramp to MAX speed.
If the cpu was not 100% busy, then the governor evaluates the cpu load over the
last 'min_sample_rate' (default 50000 uS) to determine the cpu speed to ramp down
Click to expand...
Click to collapse

Thanks for the info
SERGI.3210 said:
because froyo & gingerbread don´t works at the same form, and gingerbread need more resources & stability for to work correct... don´t forget that the kernel manages the hardware...
if u force it......... u know what can happen...
Click to expand...
Click to collapse
You have mentioned about those "resources", is there any special measure that I need to do or what? I'm using the smartass profile on those kernels but still *sigh*
Anyway, I've observed on your sig that yours is overclocked @ 1.8ghz even though you're running GB, me envy

golokipok said:
have mentioned about those "resources", is there any special measure that I need to do or what? I'm using the smartass profile on those kernels but still *sigh*
Click to expand...
Click to collapse
you only should do a good over/underclock & set the correct cpu governor for your daily use....
well, you know ho is @MDeeJaay? the developer of MDJ kernels and roms...
he explained smartass with this words:
SMARTASS GOVERNOR - is based on the concept of the interactive governor.
I have always agreed that in theory the way interactive works - by taking over the idle loop - is very attractive. I have never managed to tweak it so it would behave decently in real life. Smartass is a complete rewrite of the code plus more. I think its a success. Performance is on par with the "old" minmax and I think smartass is a bit more responsive. Battery life is hard to quantify precisely but it does spend much more time at the lower frequencies.
Smartass will also cap the max frequency when sleeping to 245Mhz (or if your min frequency is higher than 245 - why?! - it will cap it to your min frequency). Lets take for example the 998/245 kernel, it will sleep at 245.
golokipok said:
, I've observed on your sig that yours is overclocked @ 1.8ghz even though you're running GB, me envy
Click to expand...
Click to collapse
no, no buddy... i only show the max speed nothing more... i set my cpu concretly like this;
CPU GOVERNOR:interactive
MAX SPEED:1113 MHZ
MIN SPEED:245 MHZ
PROFILE: screen off; 245 MHZ max.
245 MHZ min.
in adition i´m going to modify my syg LOL

haha..thanks again. I'm gonna try playing with the frequencies to see which will suit me
i hope someone can make a stable 1.8ghz kernel without the freeze

IT´S POSSIBLE but i don´t want to try it LOL
i love a lot my DHD

[q] htc wildfire s overclock

I have htc wildfire s ...i hav rooted ...i want to overclock it 806 mhz.....pls tell me the procedure to overclock..
I am using htc wildfire rom ..pls help

First you need a kernel that supports overclocking.
If you using a stock Rom then look for the kernel that matches your Android version eg. 2.3.3 or 2.3.5 you will find them in the development section posted by Jikantaru
If you install a custom Rom then it will most likely have an overclockable kernel baked in.
To change clock settings I recommend 'no frills CPU' search it in the market or you could use set CPU.
Once you install one of the above apps then change the min and max sliders to the desired frequency.

if we over clock it much does it effect the speed or hardware of the phone?

Your phone may hang.
There is SetCPU for XDA members:
http://forum.xda-developers.com/showthread.php?t=505419

RRRb50 said:
if we over clock it much does it effect the speed or hardware of the phone?
Click to expand...
Click to collapse
You will definitely get better performance and it shouldn't cause you any problems.
Use no frills CPU I find its better than set CPU, when restarting your phone set CPU doesn't keep your overclock settings even though its set on boot.
As for the govonor settings I would choose smartass2 and noop for the scheduler.
I would keep the minimum frequency on 245MHz it can go lower but it could cause some issues (lag and slow unlocking and waking)
Note: not all cpu's are capable of running at the same speed, I'm lucky mine can run at 806MHz but some people have issues.
If you notice any problems like freezing etc, then drop the speed to a lower frequency until you find the sweet spot for your CPU.

I had mine at 806 MHz with no problems
Sent from my NookColor using xda premium

so it wont cause hardware problems only lagging and other stuff

RRRb50 said:
so it wont cause hardware problems only lagging and other stuff
Click to expand...
Click to collapse
Should be fine mate.
But remember if in the very unlikely event something does go wrong I wont be held responsible.

youll have to need an overclock kernel for that. (and a rom which supports one)
go for dust kernel or cake kernel! These two are well known for high end kernels!