Database Users

Longterm disadvantages to overclocking?

Has anyone noticed any long term disadvantages to overclocking the Wizard? Does the battery life permanently decrease? What speeds are you running yours at, and how long have you been doing it? Have you noticed anything at all which indicates it's not good for the hardware?
Cheers

reply
i believe that it's safe to overclock the mda...just set it at an acceptable rate (264mhz for me) and make sure not to run the battery all the way down...if you overclock the settings too high the device will freeze and reset (this is a fail safe procedure it goes through), so there is no need to worry...also don't overclock the settings too low as the phone becomes disfunctional when too low (about less than 132mhz for me)...the screen flickers because it's not being refreshed quick enough (my guess)...hope this helps...

I would set it to 240. I have done before, i'm just wondering if it's a bad idea leaving it permanently set to that level?
Cheers

yea you should be fine at that speed, but if you want you can overclock it higher if it will let you...just make sure that the phone is stable when using it...like i said in my earlier post my device is oc at 264mhz

Cool, thanks for your replies. How long have you had yours overclocked for? Do you use Smartskey?
Cheers

My self i ownly use it when need the extra speed, only with some games and wmv video files. I think it definitely lowers battery life and i would have worries about overclocking all the time and the long term effect it has on the processor (not so important if you only keep your wizard for a year and then change with a new contract - what i do new device once a year!) I found good speed gains with the registry wizard - http://forum.xda-developers.com/viewtopic.php?t=39725
have not found overclocking produces that much extra speed.

My self i only use it when need the extra speed, only with some games and wmv video files. I think it definitely lowers battery life and i would have worries about overclocking all the time and the long term effect it has on the processor (not so important if you only keep your wizard for a year and then change with a new contract - what i do new device once a year!) I found good speed gains with the registry wizard - http://forum.xda-developers.com/viewtopic.php?t=39725
have not found overclocking produces that much extra speed.

Mine is also set at 264 24/7. Battery still lasts me all day. Been doing it since the oc program was found which I guess has been a couple of months.

Don't forget, you're wizard is only overclocked when it is active (i.e. not in standby mode). When your wizard goes into standby, it automatically goes back to the default 180mhz. Only when you bring it out of standby does it overclock again (assuming you're running it with smartskey with the option of overclocking on wakeup)

i'm using smartkey to constantly run at 264mhz...i have been doing this for a month now...like i said there is not really any problems with the batt unless you run it down totally...there was a post about this in the overclocking thread...the process is set low so that the phone will have a longer batt life...this was also stated in the overclocking thread...theoretically there is more wear if you overclock it since you are making the processor work harder, so use it at your own risk! if you want to be on the safe side then use smartkey and the overclocking prog in the same directory...then use total commander's note pad (while the ini file is highlighted) and change the value lower when you don't want it to constantly run at 264mhz or whatever speed you want to overclock or underclock at...just use it when needed, but i overclock mine constant 264mhz with great results combined with tweaks2k2, registry wizard, and of course the tmobile custom rom ...internet is a blast...just wish i could get it to run like the IE in a pc
anyways hope this helps out a bit further...

activesync
your activesync will hang allot if you overclock, I have noticed this.

DOnt know why.
For some reason i stumbled onto something, im sure its been mentioned b4 but when running Wisbar advance with a Windows vista skin done by xcillion, i am able to overclock my cingular 8125 to 288mhz at a stable rate with no problems at all, can run warcraft 2 full speed with over 50 units battling it out on screen, almost doubles browsing speed and i can run all the emulators including SNES at full speed with sound. when i dont have wisbar advance running i cant go past 240mhz clocking speed. I wonder has anyone else noticed this or gone higher than 288 without a freeze. Also, my battery life runs steady for a full day of browsing the internet talking on mobile messanger and listening to music at half volume for a full day.

Re: DOnt know why.
xSoNiCcRaCkErSx said:
For some reason i stumbled onto something, im sure its been mentioned b4 but when running Wisbar advance with a Windows vista skin done by xcillion, i am able to overclock my cingular 8125 to 288mhz at a stable rate with no problems at all, can run warcraft 2 full speed with over 50 units battling it out on screen, almost doubles browsing speed and i can run all the emulators including SNES at full speed with sound. when i dont have wisbar advance running i cant go past 240mhz clocking speed. I wonder has anyone else noticed this or gone higher than 288 without a freeze. Also, my battery life runs steady for a full day of browsing the internet talking on mobile messanger and listening to music at half volume for a full day.
Click to expand...
Click to collapse
hey sonic, where did you get your copy of warcraft 2 for windows mobile ?
I've never heard of warcraft for Windows mobile, how does it run on a 240 MHz overclock?

I got it from the Wargus engine. i can email you the files if need be, i dont want to jeprodize this sites reputation. The game last time i checked was free though...

Actually I'm not sure if it's the overclocking issue or not but ...
For couple of weeks now my Wizard's red led is on all the time, not like it is when your battery is very low but about half of this brightness. I'm not really worried about that, it doesn't change much but it may be connected with overclocking (it was 240 for about a month).
Another thing - once I had sth like 110% speed of every tone played, either a phone call or an incoming message.
It doesn't really matter to me since it's still working fine but it may mean that overclocking isn't that safe as we might think.
TroLoo

Does anyone have any Overclocking horror stories?

I've just begun overclocking my 8125. starting at 220 and i'll work my way up slowly to a maximum of 265 if possible.
I was wondering if anyone had any horror stories that would make me change my mind about overclocking. Like permanantly damaged devices. I've searched the forums and cant find a single one, which leads me to beleive that it truly is completly safe. But i thought i'd start this thread to make sure.

The worst that I've had happen to me (or heard of happening to someone else) with overdoing the overclock is the device showing the 'white screen of death' which just forces you to soft-reset your device. It's really not anything that bad ^_^

k2snowboards88 said:
I've just begun overclocking my 8125. starting at 220 and i'll work my way up slowly to a maximum of 265 if possible.
I was wondering if anyone had any horror stories that would make me change my mind about overclocking. Like permanantly damaged devices. I've searched the forums and cant find a single one, which leads me to beleive that it truly is completly safe. But i thought i'd start this thread to make sure.
Click to expand...
Click to collapse
i've been overclocking at 242 or 260 for over 2 months now and I haven't had any problems. My sweet spot is 242, it runs GREAT on this speed and it is a tad more stable than 260.

It is possible to brick your device if you try a speed to fast. 240 is perfectly safe, anything above that can be unstable.

I know its possible to fry a chip through overclocking. I remember frying one of my amd k6-2 processers awhile backl. I just find it odd that even though its possible to fry your wizard. and so many people overclock, that i haven't heard one story about a wizard being broken this way.

I know its possible to fry a chip through overclocking. I remember frying one of my amd k6-2 processers awhile backl. I just find it odd that even though its possible to fry your wizard. and so many people overclock, that i haven't heard one story about a wizard being broken this way.

Been running mine @ 240 for a while now and everything seems fine.
My phone is mainly on stand-by during the day, but when I do use it for extended periods (evenings and weekends) I use Wi-Fi a lot and read a lot of ebooks which can be quite power consuming - however, the overclocking seems to have no noticeable affect on the phone other than making it quicker...

afaik
MOST "PORTABLE" CPU'S CAN MUCH FASTER THAN THEY DO BUT AT THE COST OF POWER THE CPU'S ARE "UNDERCLOCKED" TO SAVE POWER
SORRY MY CAPS IS STUCK AND i JUST NOTICED IT...
BHANG

afaik
MOST "PORTABLE" CPU'S CAN MUCH FASTER THAN THEY DO BUT AT THE COST OF POWER THE CPU'S ARE "UNDERCLOCKED" TO SAVE POWER
SORRY MY CAPS IS STUCK AND i JUST NOTICED IT...
BHANG

overclocking after standy freezes for a while!
This query is not related to the thread, but forgive me as I didn't want to start a new one.
I've smarskey with the overclock feature enabled and omapclock.exe running nicely. It hasn't been giving me trouble at all. However, I've one problem..
After the phone goes in standby after a period of inactivity and when I hit the power button again to use the phone, I notice a freeeze in time display. It takes a while before time changes from say 11:30 to 3:30.
I know Smartskey 'wakes' up the overclocking process again and this maybe the reason why my phone somewhat freezes for a very brief period after I disturb the standby mode, but I was wondering if anyone has a solution to this, its kinda annoying.
Thanks

Does not sound that bad, I think your problem is that you can't just take your phone out to have a look at the time :wink: am I right?
Well perhaps that would really be kinda annoying.
But it also sounds like there is no real solution to this. Just try reinstalling the apps, certainly there is a software conflict (if this is not a normal effect).
Perhaps you can also use another possibility than smartskey. I think BatteryStatus and OMAPScaler also have options to overclock at wakeup.

thanks..
maati said:
Does not sound that bad, I think your problem is that you can't just take your phone out to have a look at the time :wink: am I right?
Well perhaps that would really be kinda annoying.
But it also sounds like there is no real solution to this. Just try reinstalling the apps, certainly there is a software conflict (if this is not a normal effect).
Perhaps you can also use another possibility than smartskey. I think BatteryStatus and OMAPScaler also have options to overclock at wakeup.
Click to expand...
Click to collapse
thanks for the advice, i'm thinking about using memaid.

uh...Jasjar issue perhaps...can't find any info on this.

Well hello there xda Community,
I decided to purchase a i-mate JasJar (HTC Universal) a while back. I have noticed that just about any ROM I install on here doesn't seem to perform very well, even some of the very best ones. I have a feeling that it is the CPU that may have been damaged in some way. I do not know for sure. Some issues that I've experienced go as; pauses in videos I play (audio, sometimes picture), sometimes songs pause for almost 10 seconds...It acts as if the whole device freezes up. Runs very slow when I run Skype (NEWEST VERSION) with nothing else running. Freezes sometimes when incoming call comes in if I'm using an application...ALL THE PROBLEMS I JUST STATED OCCUR SHORTLY AFTER SOFT RESET...and/or when there is a lot of free ram. I have also read in other posts of owner's jasjars booting up in five seconds...is this common, I'm generally waiting, oh...say around 30 to 45 Seconds...and btw, I've tried just about every tweak and tune up for the Jasjar (no improvment) CPU Speed up, RAM Cache increased....no luck,
I'm curious to know if this is how the device was designed to run or if this is just an isolated issue on the exact piece of equipment I'm using...
Any help or advice would be of any importance to me...Thanks

I too have a jasjar. On the skype issue, I use XCpuscalar 2.95 AND SET THE DEVICE SPEED TO 520 and the cracles disappear. I think the video issue you are having could be the device increasing and decreasing cpu speed depending on cpu usage so setting it on 1 cpu speed should help. Goodluck!

What is it with emulators?

I know that the Ameo throttles the CPU back (but I'm not happy with having PHM installed all the time, as I don't trust it to properly slow the machine down), but why do so many emulators fail on the Ameo?
Pocket Plus/4 is really, really choppy and unreliable.
Pocket Atari seems to work sometimes, but at other times I get speaker popping and no functional emulator.
Pocket C64 is just useless and doesn't support the keyboard, it seems; and setting up the controls seems to cause fuss for the sound, too.
This is supposed to be a fast machine, so I'm baffled by the apparent slowness when it does run an emulator. Pocket Plus/4 especially drops to 4% speed; I thought the CPU was supposed to catch up to the demand!

And tried with PHM anyway, still no better.
I just tried the exact same installation of Pocket Atari on the Universal with WM6 installed. It's working quite well; I'm currently playing Rescue on Fractalus (XEGS ROM).
Is it a memory management thing, or Microdrive, or something else?

RichardKAthena said:
And tried with PHM anyway, still no better.
I just tried the exact same installation of Pocket Atari on the Universal with WM6 installed. It's working quite well; I'm currently playing Rescue on Fractalus (XEGS ROM).
Is it a memory management thing, or Microdrive, or something else?
Click to expand...
Click to collapse
On the Universal you probably installed it to the SD? If so, have you tested it on the SD of the Athena? I also noticed a few slow downs on my Athena and I have a Universal also to compare to. I have to redo my Universal because it's running very slow so I can't compare at the moment. I have read on the forums that users have noticed a performance increase with some WM6 installs. This could be a factor but I also think that the SD card is faster than the microDrive. Try it on the SD if you already haven't and see how it goes.

ltxda said:
On the Universal you probably installed it to the SD? If so, have you tested it on the SD of the Athena? I also noticed a few slow downs on my Athena and I have a Universal also to compare to. I have to redo my Universal because it's running very slow so I can't compare at the moment. I have read on the forums that users have noticed a performance increase with some WM6 installs. This could be a factor but I also think that the SD card is faster than the microDrive. Try it on the SD if you already haven't and see how it goes.
Click to expand...
Click to collapse
I don't have a miniSD, I tried it on internal memory (which I'd expect to be fast) with exactly the same results.
Broken Sword demo runs beautifully from Microdrive; maybe a bit of lag on audio. PocketAtari should be less reliant on the Microdrive than any large game.
I definitely think WM6 feels snappier (though my machine did get sluggish; perhaps the memory leak issue mentioned), but there are some WEIRD glitches going on here. One of the most telling things was when messaging popped up; directly before corrupting PocketAtari's screen with a notification, the messaging application's "activation" caused PocketAtari to run at full speed.
I think there must be some CPU "optimisation" going on within the WM5 build on the Ameo, and I don't think PHM actually cured it for me (I tried forcing the CPU fast for PocketAtari, and just forcing the CPU fast overall).

RichardKAthena said:
I don't have a miniSD, I tried it on internal memory (which I'd expect to be fast) with exactly the same results.
Broken Sword demo runs beautifully from Microdrive; maybe a bit of lag on audio. PocketAtari should be less reliant on the Microdrive than any large game.
I definitely think WM6 feels snappier (though my machine did get sluggish; perhaps the memory leak issue mentioned), but there are some WEIRD glitches going on here. One of the most telling things was when messaging popped up; directly before corrupting PocketAtari's screen with a notification, the messaging application's "activation" caused PocketAtari to run at full speed.
I think there must be some CPU "optimisation" going on within the WM5 build on the Ameo, and I don't think PHM actually cured it for me (I tried forcing the CPU fast for PocketAtari, and just forcing the CPU fast overall).
Click to expand...
Click to collapse
Wow, sounds like it's a CPU scaling issue indeed. Have you tried to disable the internal scaling using something like PHM? Not allowing it to manage the speeds but just disable the internal system and see what happens.

ltxda said:
Wow, sounds like it's a CPU scaling issue indeed. Have you tried to disable the internal scaling using something like PHM? Not allowing it to manage the speeds but just disable the internal system and see what happens.
Click to expand...
Click to collapse
Yep, still choppy as anything. Thing is it appears that if I disable scaling and leave it at that (and don't let Scale Engine run), then it stays at 104MHz! But even running at 624MHz - surely plenty for a 1MHz 6502 machine to be emulated - it's running at 4% speed!

We can now overclock our phones!

Couldn't really see any discussion on this yet, and personally it's in a location on the forum that I rarely visit but I've found an overclock tool that is slowly becoming very good indeed for our processors. Link to thread is here. I'm soo far up from 528Mhz to 748Mhz (been stable for the past 6 hours no problem). Just make sure to follow the thread (instructions are linked to ensure overclock remains applied through scripts and 3rd party apps). Should take no longer than 30mins for a well versed user to set up. Please don't try this if you haven't got a clue what you are doing as there is soo much scope for error and dead phones! You may also need to customise any scripts to your specific phone/software build. CDMA phones as usual are different from what I've heard. But anyway good luck, I'm gonna keep trying to push the Mhz up (aiming for 850Mhz ).

Not sure its a good idea to go past 700 mhz,our phones run hot as it is under capacity,as with gaming rigs heat is your Enemy,the cooler you keep it the faster.

It's actually remained pretty cool, and when it's in my pocket it's only running at stock clocks anyway. Only when I'm using it does it get to the full 748Mhz. Running wifi router and charger and temps are not noticeably hotter than usual...

um... ive been clocked up to 787 highly stable for the last like 2 weeks. No heat problems, no battery problems, just insane speed.
recommendations: Download v1, not v2. ESP if you dont know what you're doing. Then download the zip im attaching, there's 2 mortscripts in there and a registry addition, THESE MUST BE IN THE STORAGE CARD ROOT. use the regisitry addition FIRST (just associate w/e regedit software you use, then run the .reg file in total commander), then go back to total commander, edit the .mscr "Toggle_boost" and adjust the value boost = "x" to whatever value you want the phone to OC at, eg boost = 41 is 787mhz which is stable for me, test yours out.
THEN, open and install rhodiumkbdcontrol (attached), reboot, go to settings>system>keyboard config> add key
1st pick which key you want to be the OC boost swtich, I have it mapped to my PTT button. click the plus sign, drop down menu, run program, then highlight "run program" in the list then click "..." then type in
Program: \windows\mortscript.exe
Arguments: "\storage card\toggle_boost.mscr"
This time you wanna use the power key.
same general instructions except
Program: \windows\mortscript.exe
Arguments: "\storage card\boost_off.mscr"
then plus sign again, drop down menu, default key action, and click extended emulation. THEN hit update config. should work like a charm, also autoover clocks to 610, the boost button with send you up the w/e the boost = "x" is set to, and then back again, most find 710mhz to be the stable point, and feel free to ask questions

sorry, heres the zips

wouldnt overclocking also gives you a higher chance of frying your CPU chip? cuz ive seen it happened in PCs i just idk about PPCs

I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!

miked79928 said:
I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!
Click to expand...
Click to collapse
Yeah could you hook that up? I think posting it here would be best but pm'ing works just as well
Edit:
I just read threw the above links and guides and was wondering if there is a more automated way of setting this up rather than having to link it to a button press. I'm guessing this has not been figured out yet (or the guides would have mention of it ). Just curious.

dantegl36 said:
Yeah could you hook that up? I think posting it here would be best but pm'ing works just as well
Click to expand...
Click to collapse
Here is the best way I have found to do it. I take absolutely no credit for this:
http://forum.xda-developers.com/showpost.php?p=7354283&postcount=627

Check it!
Outlaw78a said:
Not sure its a good idea to go past 700 mhz,our phones run hot as it is under capacity,as with gaming rigs heat is your Enemy,the cooler you keep it the faster.
Click to expand...
Click to collapse
I have used this, NRG also does. I have NEVER had any problems and mine is as high as 787 as long as I'm running it which is constantly.
XITruthiX said:
um... ive been clocked up to 787 highly stable for the last like 2 weeks. No heat problems, no battery problems, just insane speed.
Click to expand...
Click to collapse
100% agreed. Been running at the highest speeds with NO problems, no batt drain, no heat probs, nothing.
XERO_Racer said:
wouldnt overclocking also gives you a higher chance of frying your CPU chip? cuz ive seen it happened in PCs i just idk about PPCs
Click to expand...
Click to collapse
Not unless you are having excessive heat problems. Since there are basically no people reporting these problems, I wouldn't worry.
miked79928 said:
I agree that there are virtually no ill effects to this. When unlocked, I have my phone running at 787 mhz. While it is locked or sleeping it throttles down to 604 and eventually 528 mhz. I have noticed no extra heat nor extra drain on the battery. Just blazing fast speed! Sense 2.5 is virually not laggy at all! CHT 1.8.5 is so smooth and quick even with the aminations enabled!
If anyone is interested in the automated clocking process, I can help by giving my set-up that is working flawlessly on the ROM in my signature!
Click to expand...
Click to collapse
Once again as stated earlier, 100% agreed.

Do I have to keep plugged in?

miked79928 said:
Here is the best way I have found to do it. I take absolutely no credit for this:
http://forum.xda-developers.com/showpost.php?p=7354283&postcount=627
Click to expand...
Click to collapse
I thank you for this, but I'm not sure how to implement it. I have installed Mortscript, I've copied the code into a file I called overclock.mscr and modified the code reflect the reg values on my Tilt 2. and I've placed the script on the root on my SD card. I've installed MSM7kCpuSpeed on to my SD card. How do I make the script run automatically?
Thank you!

I take no responsibility for w/e happens to your phone with this advice.
Try putting a pointer in your start up to the over clocking script. Its highly unstable and could brick your phone or require a hard reset... thats why I do it with a toggle switch, i dont mind manually applying the OC with a hard key knowing its safe, esp because the situations where I actually NEED 787mhz are less common than needing to just wake the phone to answer a call or make a txt message.

I just want to say that I have been running android on my tilt 2 overclocked at around 750 for a few months now with various builds and i know a lot of other users who have as well with no problems, i am going to try this out, thats what i pay for insurance for hehe
..and after reading more i may have spoken too soon because i missed the posts where i saw that you can brick your phone with OC in WinMo easily enough if you are not careful, so tread with caution

dirtypiratehooker said:
I just want to say that I have been running android on my tilt 2 overclocked at around 750 for a few months now with various builds and i know a lot of other users who have as well with no problems, i am going to try this out, thats what i pay for insurance for hehe
..and after reading more i may have spoken too soon because i missed the posts where i saw that you can brick your phone with OC in WinMo easily enough if you are not careful, so tread with caution
Click to expand...
Click to collapse
Just a note, I'm not sure the insurance would cover burning a custom ROM into the phone, or overclocking the CPU. And if the chip is fried you can't burn the stock ROM back in. But then, they probably couldn't figure out it was updated without in stalling a new CPU. Umm, it would probably work.

Would a .cab for this ever be conceivable?

At this point, we have finally got a script that will work for most Rhodiums, Topaz (Diamond 2), and a few guys with other phones seem to be having good luck.
The device has to have Mortscript installed, and nettrip's MSM7 v2.
It is a single script solution that requires no pre checks in the registry, no key/button assignment, and you can change the speed settings from the script instead of the registry.
It throttles the OC up and down for calls, lock, and sleep, to avoid freezing on wake up and in a call. Some problems that still need to worked out by nettrip in the script. I don't envy him the work as the script(s) were bad enough. Four of us have hit that original script (by jpc) from about page 13.
You copy the script to the SD or the device root, create a shortcut to the file, copy the shortcut to Windows\Startup directory, reset/reboot the device and you are off.
You can use the MSM7 app to read the OC, but you should make sure to exit the app before sleep, lock, or power off, as it will error on reboot if left open.
To be honest, you never have to open the MSM7 app, as the script controls it in the background.
I believe the script is set for a low over clock. 691. My experience has been a 710 average, but a lot get a stable OC at 750+. I am running 748 and I think I will stop there. A 200MHz overclock will just have to do.The phone does not get hot, though with intense use, it does get warmer. Never warmer than when the battery is charging, tho.
I am running the nrg Sense Reference ROM, 23xxx based on Sense 2.5. I added the CHT 1.8x and the editor to save a few MHz, no biggy.
The overclock allows the Sense to work MUCH smoother, actually noticeable as even the weather animation is smooth.
And all the vid players seem to work better.
I have noticed NO extra battery drain than usual.
The script is only a stop gap measure until nettrip finishes his app, but it does work well with little effort. WAAAAY better now than even last week.
However, use the script at your own risk, as you can get too Medieval on the OC. Some guys are running 800+, more nerve than I have.
Anyway, if interested in the script or want to read some more about the app, you can start here
http://forum.xda-developers.com/showthread.php?t=725290&page=89
post #882 has the script.
Plenty of instructions on how to use (and make changes to the settings) in the last 30-40 pages.

Sorry if this is already explained, but can someone tell me in simple details how to keep my overclock at 729mhz even after screen lock or sleep mode? I've tried to follow previous posts but it keeps reverting back to 528mhz after locking and sleep.

Ok so this seems legitamite,everyones checking in with no problems.
other than the increased risk factor that always accompanys speed,
it seems our ppc's cpu was underclocked beforehand ?
i will try this and see if i get a gpu boost as well.
but ivr already experienced my phone overheating to the point
of shutting itself down,and the god-damned orange light is permenantly on...