Your experience with overclocking?

[Gegenpapst]

Hi!

Has anyone yet found out good values for the overclocking? Can the overclocking damage the Prophet (O2 XDA Neo)?

Does the overclocked CPU drain more battery power?

[rodigezstyle]

that tool is great to overclock the profhet to 240-250 Mhz
you must test it what for you the best config !

[dnts]

I've been overclocking my JAMin since day 1 (about 6 weeks now) and with great results. I have set it up to overclock @240MHz all the time (do a search for the instructions) and it's been stable, quick and with no major impact on battery life.
Since the last ROM update - the JAMin has been stable with no spontaneous soft resets. Just great.
Nir

[Gegenpapst]

is the rom-update available for the o2 xda neo, too?

[rodigezstyle]

noch nicht wenn es rauskommt findest du es hier...
http://www.o2-online.de/o2/kunden/technikundeinst/exclusive/xda/xdaneo/index.html

[aleksandr]

The only upgrade you'll get is Imates, qtek s200 or dopods. O2 sucks as far as upgrade concern. Especially in germany. This so called tech support guys still think that you’ll kill the device if you upgrade it! At least this is what they been telling me! The bottom line, get an update, get “fixed” RUU, search forum, and run an update. You’ll loose german rom though unless you back it up using aWizard.

[bombomtr]

My S200 overclocked about 5 weeks by now. 276 MHz cause spontaneous softreset once or twice per day. 264MHz works fine; it is my current overclock speed. I don’t think it may cause battery drain, but something drains battery randomly. My suspect is Communication Manager.

[mhojlo]

I'm using smartskey to overclock. When set to 240 it crashes. Anyone knows why? I'm also using O2 and i've made some standard registry hacks (cache size).

[shivam]

264MHz works for me too.

What programs do we use for benchmarking to see what outperforms what

[s2tephen]

I can overclock up to 240 but when I connect to active sync 4.1 it keep dropping its conection

[jarel]

When overclocking above 234 Hz w/ BatteryStatus or 216 with Omapclock,... I get strange dots and color in camera...

Anyone having same problem? :(

[RaptorRVL]

Well in the topic about upgrading to one of the latest roms I saw a lot of people having problems with the camera and overclocking. So it seems to be happening when overclocking for sure. Not much you can do about it except clocking it back when you want to use the camera :)

[seneca]

I have the same Problem. Thats why I use applicationbased clocking with Batteriestatus, setting Kamera and Coolcamera to 195 mHz.

cu seneca

[RaptorRVL]

Yeah, same here btw totally forgot to mention that.
I use batterystatus with the CPUscaler option on. At the moment I have it automaticly scaled up to 221mhz when needed. But indeed all the camera apps have it set back at 195.

Not quite sure to what speed I can go safely. Mostly need somewhat more speed with the navigation on in the car. Although that uses the device 100% for sometimes hours. So since most of the people go up to 240 I just though 220 might be a safe number :) No problems so far.
Anyway, I'm interested in making it a little bit faster. But an overclock of over 20% just seems too much (or too good to be true :) )...

[jarel]

I have the same Problem. Thats why I use applicationbased clocking with Batteriestatus, setting Kamera and Coolcamera to 195 mHz.

cu seneca



Uppss, ... sounds great. But I can not find any applicationbased clocking in my BatteryStatus plug-in.... What else do I need?

Thanks in advance.


Jarel

[niker]

I have a O2 Neo. and currently is overclocked at 260 mhz. no problem so far.

[seneca]

Uppss, ... sounds great. But I can not find any applicationbased clocking in my BatteryStatus plug-in.... What else do I need?


You need the Version BatteryStatusPlus.Beta1.0.03.zip of BatterieStatusPlugin at the first Message of this Thread (http://forum.xda-developers.com/showthread.php?t=270751)

cu seneca

[jarel]

Thanks Seneca...

I had the non.beta version installed, thus not having those options... Is this Beta version stable/well-proven? Why don't they ibnclude this functionaility in the "definitive" non-beta version?

Thanks again, great forum and great support!


Jarel :)

[seneca]

After finishing the Beta Phase, it will be included in an extendet Version.
On my NEO/Qtek it is very stable. But read the Thread. There are the answers.

cu seneca

[vsc]

With respect to overclocking it has been stable for a long time. With regards to other features they appear to be stable, hence the change to beta status.

The only question is how high you can overclock your specific device. You will need to use trial and error. Note that as the device get hot, the max overclock speed drops. It's a physics thing.

Thanks Seneca...

I had the non.beta version installed, thus not having those options... Is this Beta version stable/well-proven? Why don't they ibnclude this functionaility in the "definitive" non-beta version?
Jarel :)

[RaptorRVL]

Next to overclocking, how about underclocking? I have my device at 100mhz currently, scaling up to 220mhz.

I did notice that when I use the device as standard with 195mhz it uses 83-84mA. When overclocking to 220mhz it uses 88-90mA.
Clocking it to 100mhz uses 68mA. That's with bluetooth/wifi off and brightness set to 50% and the device doing nothing with the screen on.

But that's quite a lot of change in the power consumption. Most interesting however would be looking at what the device uses when you put it in standby. But I got quite different numbers everytime I tried to look. Maybe downscaling doesn't make a difference at all in standby, because perhaps the cpu is also put a bit on standby. Anyone have more info about this?

[LordDeath]

Next to overclocking, how about underclocking? I have my device at 100mhz currently, scaling up to 220mhz.

I did notice that when I use the device as standard with 195mhz it uses 83-84mA. When overclocking to 220mhz it uses 88-90mA.
Clocking it to 100mhz uses 68mA. That's with bluetooth/wifi off and brightness set to 50% and the device doing nothing with the screen on.

But that's quite a lot of change in the power consumption. Most interesting however would be looking at what the device uses when you put it in standby. But I got quite different numbers everytime I tried to look. Maybe downscaling doesn't make a difference at all in standby, because perhaps the cpu is also put a bit on standby. Anyone have more info about this?

the more i underclock, the more flickering i can see on the display. it is not everywhere but it is there. so i underclock it to 162mhz at the moment and on load it boosts up to 273mhz. i have no idea about the performance improvement, because this device is overclocked since its first day :rolleyes:

[prysm]

Hello

I was wondering if overclocking helps improve the response time of the camera. I tried to clock it at 200Mhz a few times and did not notice much difference.

Has anyone investigated an optimum overclocking to improve the camera response time?