Does anyone have any Overclocking horror stories?

[k2snowboards88]

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.

[Cardcaptor_RLH85]

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 ^_^

[DeniaL]

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.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.

[xenos]

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

[k2snowboards88]

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.

[k2snowboards88]

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.

[sketchcards]

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... :D

[bhang]

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

[bhang]

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

[slayu]

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

[maati]

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.

[slayu]

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 for the advice, i'm thinking about using memaid.