Related
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?
that tool is great to overclock the profhet to 240-250 Mhz
you must test it what for you the best config !
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
is the rom-update available for the o2 xda neo, too?
noch nicht wenn es rauskommt findest du es hier...
http://www.o2-online.de/o2/kunden/technikundeinst/exclusive/xda/xdaneo/index.html
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.
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.
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).
264MHz works for me too.
What programs do we use for benchmarking to see what outperforms what
activesync dropout
I can overclock up to 240 but when I connect to active sync 4.1 it keep dropping its conection
Camera problem when overclocking...
When overclocking above 234 Hz w/ BatteryStatus or 216 with Omapclock,... I get strange dots and color in camera...
Anyone having same problem?
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
I have the same Problem. Thats why I use applicationbased clocking with Batteriestatus, setting Kamera and Coolcamera to 195 mHz.
cu seneca
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 )...
seneca said:
I have the same Problem. Thats why I use applicationbased clocking with Batteriestatus, setting Kamera and Coolcamera to 195 mHz.
cu seneca
Click to expand...
Click to collapse
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
I have a O2 Neo. and currently is overclocked at 260 mhz. no problem so far.
Uppss, ... sounds great. But I can not find any applicationbased clocking in my BatteryStatus plug-in.... What else do I need?
Click to expand...
Click to collapse
You need the Version BatteryStatusPlus.Beta1.0.03.zip of BatterieStatusPlugin at the first Message of this Thread
cu seneca
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
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
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.
jarel said:
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
Click to expand...
Click to collapse
I've noticed that when using CPU intensive applications such as games or video, the frame rate drops dramatically while using the touch screen. As soon as I remove the stylus from the touch screen, or when the touch screen receives no input, the speed increases back to "normal". Has anyone else noticed this before? It seems to me like there are still some drivers that need some major updating. I hope the bugs and performance issues will be resolved with this device soon. This device feels underpowered for the hardware is has in it. I'm guessing with some further optimization it will be able to perform much faster (I hope).
BTW, I have the HTC branded version, with ROM version 1.15.405.5
prsnow said:
I've noticed that when using CPU intensive applications such as games or video, the frame rate drops dramatically while using the touch screen. As soon as I remove the stylus from the touch screen, or when the touch screen receives no input, the speed increases back to "normal". Has anyone else noticed this before? It seems to me like there are still some drivers that need some major updating. I hope the bugs and performance issues will be resolved with this device soon. This device feels underpowered for the hardware is has in it. I'm guessing with some further optimization it will be able to perform much faster (I hope).
BTW, I have the HTC branded version, with ROM version 1.15.405.5
Click to expand...
Click to collapse
I have the same problem when K-Rally is running.
I've noticed the same problem when playing K-Rally. When I remove the stylus from the screen game run appreciably faster.
Same here guys, but on my Hermes/Tytn which also has the same processor!
Use google and you'll see that some sites recommend that you install these applications that are running slow (Krally for example) on your memory card instead of the main built in memory, and then try it!
I noticed this first when I installed Krally on the Tytn and it seemed slow when using the stylus. On my friends Asus P525 it runs so smooth and fast!
I havent botherd buying a memory card yet as I dont intend to keep the Tytn so therefore I'm unable to test whether or not the above method works.
If you guys can then test it and post your results here.
Thanks.
Guys some bad news,
I've tried installing Krally on a memory card and playing on it but still the problem remains! As soon as you touch the screen with a stylus the game slows down and returns to normal when you remove the stylus!
Not good at all!
DO you have the same problem:
I can't play KRALLY (neither other games as emulated games(mario kart snes)) because i can't push to buttons at the same time. If i'm pushing for example the button to accelerate, once i push a button to turn it stops....That really sucks....When i Had my i-mate JAM i didn't have such problems.
It would be nice to be fixed
use auto-accelerate and auto-turbo... and just directional pad to turn left and right i solved playing like this
Same Problem here! I tried to play PocketQuake and some other games, but every time i use the stylus everything slows down.
But the biggest problem is, when i use the buttons especially the "D-pad" after some pressing of this button (8-10 times) the whole trinity crashes!
Are there people having this problem too?
Maybe someone could test pocketquake too, or test if the dopod rom solves this problem.
Greetings,
Borbosch
Interesting, cpu is going 45% as soon as you touch the screen (see screen capture).
I don't think my previous devices had this "feature", I will check and compare with their behaviour.
We should also check with hermes to see if it's the same.
Can you imagine your PC using half is processing power when you click with the mouse?
meroupow said:
Interesting, cpu is going 45% as soon as you touch the screen (see screen capture).
I don't think my previous devices had this "feature", I will check and compare with their behaviour.
We should also check with hermes to see if it's the same.
Can you imagine your PC using half is processing power when you click with the mouse?
Click to expand...
Click to collapse
Yeah, this is quite frustrating. I really hope HTC or whoever is developing new ROMs already know about this issue, because it really needs to be corrected.
I had sent e-mail on support with this issue.
I've noticed that the frame rate slow down dramatically then I run the game (such as K-Rally,Sky Force by INFINITE DREAMS - http://www.idreams.pl/main.php) and use stylus to control the game. As soon as I remove the stylus from the touch screen the image become smooth. This not happen If I use buttons to control the game.
I install the same game to ASUS P525 PDA phone. The frame rate slow down not happen on ASUS P525 then I use stylus to control the game and the game run smooth.
Would you improve this problem or how can I improve it?
Click to expand...
Click to collapse
This is the answer:
Regrettably as the seems you mention about are made by a 3rd party, I can't comment on there compatibility with you P3600.
I suggest you refrain from using your Stylus to control them as this affects the frame rate.
If you have any further issues with the software I suggest you contact the software manufacturer.
Thank you for your enquiry, Should you have any other problem, please do not hesitate to call us. Your Local number can be found at http://www.europe.htc.com/support/cs_by_phone.html
Best regards,
HTC Support
[email protected]
http://www.htc.com
Click to expand...
Click to collapse
So they do not think that this issue their problem.
It is clearly not a problem related to the games. If you mention the games to HTC of course they will say: it's not my fault, it's their fault as everybody tend to do.
It is probably more simple to talk about the cpu consumption when pressing the screen which shouldn't occur and that is slowing down ANY application.
Another email
I'll send an email to HTC about this also to see if we can get a better response. I'll post the reply when I get it.
meroupow said:
Interesting, cpu is going 45% as soon as you touch the screen (see screen capture).
I don't think my previous devices had this "feature", I will check and compare with their behaviour.
We should also check with hermes to see if it's the same.
Can you imagine your PC using half is processing power when you click with the mouse?
Click to expand...
Click to collapse
This is indeed a lousy driver. While all other 2.8" HTC devices exhibit this problem in most games, the speed doesn't decrease THIS bad on, say, the HTC Wizard overclocked to 240 MHz and running K-Rally - not even at the standard 195 MHz, where, with the touchscreen constantly pressed, the CPU usage of gwes.exe increases to 17% (measured using the AKU3.2 ROM).
I've also quickly measured the CPU usage increase of gwes.exe (or, for that matter, anything) on my HP iPAQ 2210 (about 0.5% only) and my HTC Universal (no noticable CPU usage increase at all).
All in all, this problem only seems to be acute with the QVGA PPC PE devices of HTC.
prsnow said:
I'll send an email to HTC about this also to see if we can get a better response. I'll post the reply when I get it.
Click to expand...
Click to collapse
Great, I'll do it too as from the press; hope I'll receive some useful response.
[email protected] said:
Regrettably as the seems you mention about are made by a 3rd party, I can't comment on there compatibility with you P3600.
I suggest you refrain from using your Stylus to control them as this affects the frame rate.
If you have any further issues with the software I suggest you contact the software manufacturer.
Click to expand...
Click to collapse
Yes, the usual, "canned" answer. I'll explain them how the CPU usage can be reliably benchmarked and will also post them my measurement results, which DO slow it's HTC that has a buggy driver, NOT the third-party apps.
Menneisyys said:
This is indeed a lousy driver. While all other 2.8" HTC devices exhibit this problem in most games, the speed doesn't decrease THIS bad on, say, the HTC Wizard overclocked to 240 MHz and running K-Rally - not even at the standard 195 MHz, where, with the touchscreen constantly pressed, the CPU usage of gwes.exe increases to 17% (measured using the AKU3.2 ROM).
I've also quickly measured the CPU usage increase of gwes.exe (or, for that matter, anything) on my HP iPAQ 2210 (about 0.5% only) and my HTC Universal (no noticable CPU usage increase at all).
All in all, this problem only seems to be acute with the QVGA PPC PE devices of HTC.
Click to expand...
Click to collapse
I'e continued benchmarking my other Pocket PC's; neither the Dell Axim x51v (A12 ROM) nor the Fujitsu-Siemens Pocket Loox 720 did exhibit any kind of CPU usage increase with the stylus down.
I'll do the Trinity benchmarks on Monday (unfortunately, I don't own the device, it's my employer's and don't have access to it during the weekends). If it indeed turns out to be resource-hungry, I'll publish an article on the matter, which HTC can surely not ignore any more.
Menneisyys said:
I'll do the Trinity benchmarks on Monday (unfortunately, I don't own the device, it's my employer's and don't have access to it during the weekends). If it indeed turns out to be resource-hungry, I'll publish an article on the matter, which HTC can surely not ignore any more.
Click to expand...
Click to collapse
Thanks Menneisyys, that would be extremely appreciated.
meroupow said:
We should also check with hermes to see if it's the same.
Click to expand...
Click to collapse
The answer unfortunately is yes! As mentioned in my first post the Hermes also suffers from this just as bad! I've simply given up playing Krally. All I play now is worms which is playable as its not a speed intensive game.
Its such a shame though, because on my mates asus p525 which is like a year old now, Krally runs so fast
Damn HTC. This will probably be the last HTC product I'm going to own!
Keep us updated and yes doing those tests sounds a pretty good idea.
Dead Cell.
Hi all,
I would like to know if anyone of you has already overclocked their beloved HTC Touch.
If yes, would you please post some screen captures of your Xcpuscalar configuration? (If I set it >220, my Touch reboot after a few seconds of use)
Which solution is the most reliable? XCPUScalar or OMAPClock?
Thanks a lot!
Max
for an omap use this instead : http://www.chi-tai.info/cs_BatteryStatus_XDA_Neo_WM5_iM_cs.htm
I am using xscalcpu w/o problems so far. i think mine is clocked to 400mhz and no problems so far (which means in the last 2 hours).
I am using xscalcpu w/o problems so far. i think mine is clocked to 400mhz and no problems so far (which means in the last 2 hours).
geek78 said:
for an omap use this instead : http://www.chi-tai.info/cs_BatteryStatus_XDA_Neo_WM5_iM_cs.htm
Click to expand...
Click to collapse
Thanks a lot... It works like a charm!
rklosinski said:
I am using xscalcpu w/o problems so far. i think mine is clocked to 400mhz and no problems so far (which means in the last 2 hours).
Click to expand...
Click to collapse
400mhz???! I doubt that.....most overclock up to 240 max...please enlighten me and share your settings
hell, im just reading what the display states w/o thinking too much about it.
Mine is set at 264 and works fine.
To bad it goes back to 186 when it goes to sleep :-(
Mine is set to 240 and works without any problems.
Cheers
LB
cyrilp said:
Mine is set at 264 and works fine.
To bad it goes back to 186 when it goes to sleep :-(
Click to expand...
Click to collapse
heya cyrilp,
would suggest you use batterystatus (link above), where you can easily set it to wakeup at the choice of speed.
if you're just using teh omapclock.exe then you'll have to insert wakeup @ speed in notifications.
Yes i juste did, it's perfect.
Thanks a lot !!
on my today's screen battery status instead of 260 MHz shown 60 MHz , on yours ?
Mine dispalyed 60 also till I realise it is the text size as there is a service provider overlapping cpu speed
Is it dangerous overclocking the Touch?
And do you notice any major improvement?
Actually I've noticed that if I overclock my Touch > 247MHz (with BatteryStatus), I'll have some sort of "stripes" visible on the 3D Cube background.
Am I alone with this?
stripes
never encounter with stripes problem on 3D cube when overclocking
maxoueb said:
Actually I've noticed that if I overclock my Touch > 247MHz (with BatteryStatus), I'll have some sort of "stripes" visible on the 3D Cube background.
Am I alone with this?
Click to expand...
Click to collapse
YAP TATS wta i heard from other resource too.
tried 247 and 260 MHz , no stripes
stesa said:
tried 247 and 260 MHz , no stripes
Click to expand...
Click to collapse
I OC to 286mhz for 3 days already and without any glitches. I love this baby with WM6 and 286mhz. It is as responsive as my Palm 650 !!
which program did u use to overclock the elf?
thx.
How do you all get your Wing's to hit 270 ect? I can't go past 221/228 without having crashing problems. If I go for 240 or higher its White scree/Black screen or squiggles. Do i just have a weak phone or something?
huh. i use 286, its crazy stable enough.
Are you still stock rom? its possible that there are stability problems.
Install touchit 2.0 for wings. Awesomelicious.
Then try again.
It's the same rule that applies to any and all processors, every one of them is different. Some just don't overclock as well. Some overclock to crazy numbers.
Mine will go to 312 with no problem but there seems to be an optimal number for each one. It's a question of trying dif. settings. 260 seems to be about right for mine.
I am running touchit 2.0, and am using battery status for an overclocker. i havent tried over 240 but i know at 240 it just goes haywire. anyone else having mem hog issues with touchit 2.0? i start out with 24-25megs on a fresh boot but within a couple hours 0 apps running i'm down to like 10, before even hitting 24hrs i get down to 2.5megs of free memory and i dont have anything running. anyone else having this problem? or do i have a ghetto ass wing from t-mobile?
i got crash on 280+, but undred that is OK -- (normal herald, no wing)
flyinbird93 said:
I am running touchit 2.0, and am using battery status for an overclocker. i havent tried over 240 but i know at 240 it just goes haywire. anyone else having mem hog issues with touchit 2.0? i start out with 24-25megs on a fresh boot but within a couple hours 0 apps running i'm down to like 10, before even hitting 24hrs i get down to 2.5megs of free memory and i dont have anything running. anyone else having this problem? or do i have a ghetto ass wing from t-mobile?
Click to expand...
Click to collapse
I have the same problem. But I guess this is the wrong thread :S
At the risk of sounding really dumb, what does "overclocking" do for my device?
Thanks.
it makes your phone process things faster at the risk of overheating your processor mine is at 286 no problems but if your going to overclock you might as well pagepool it and then it runs pretty good
I use batterystatus on dynamic between 156 and 273.
I've noticed that anything under 156 causes that "buzzing" noise that the wing makes ...
Mine is at a constant 299. 312 Freezes it.
Hi,
I'm experiencing freezing with games on my hero.
For some type of games the phone just restarts.
With Angry birds it freezes (so I have to pull the battery out).
I've tried floyo and villainrom. I have this problem with both.
What can cause this?
dare2k said:
Hi,
I'm experiencing freezing with games on my hero.
For some type of games the phone just restarts.
With Angry birds it freezes (so I have to pull the battery out).
I've tried floyo and villainrom. I have this problem with both.
What can cause this?
Click to expand...
Click to collapse
My only idea is overclocking above what your device can handle. Try setting the max speed to 528Mhz (no OC) and check if this solves your problem (if yes you can slowly raise the speed up and see up to what speed your device is stable).
Thanks for the tip.
I'm trying it out right now will report back if it still occours.