Overclocking Killing Elfs?
My Elf recently died. It was only 2 years old. I think for the price of these things they should last more than a couple of years. However; that being said am wondering if running an over-clock software sent it to an early grave. Here is a list and sequence of events:
1) Running Blue Elves 5
2) Used BatteryStatus software for overclocking
3) Over-clocked CPU to 260 max—using CPUScaler so that when resting was at 99
4) About 6 months before it died noticed from time to time (and with increasing frequency) that the time clock was behind time when I turned on the backlight but would correct itself within a second or two
5) 2 months before it died began to shut itself off—or just powered off by itself. Would take it out of my pocket and restart it and would be fine
6) Towards the end of its life this became more frequent—sometimes twice a day
Anyone else experience this sequence of events using over-clocking?
With my new Elf (yes, hate the death, love the HTC products) have now not over-clocked it, have however used CPUScaler so it rests at 99 which I think gives me longer battery life. Therefore only runs up to 201.
i,m having the exact same problems as you described. so now i know my device will die in +/- 6 months. i also use overclocking softwarea (2 years now). but my problems started after installing cleanram.
ikbenhier said:
i,m having the exact same problems as you described. so now i know my device will die in +/- 6 months. i also use overclocking softwarea (2 years now). but my problems started after installing cleanram.
Click to expand...
Click to collapse
To what speed are you overclocking? How long have you been overclocking?
i,m overklocking to 247 for about 2 years (homescreen ++). the last 2 months i overclocked my elf to 260. but my divice became to unstable i had to clock it back yo 247.
did you install any other software just before your device died? i think {on my divece} it has to do something with memory. because after i installed cleanram and start using it, i start to notice the issues you described. now i,m not using cleanram anymore and the problems where gone. it still occours that my elf hangs, but i think that has something to do with the fact that some softwares i installed are written for newer devices with more speed/memory. i,m pushing my elf to/over the max with the result it slowly dies.
i for instance have the problem that i can,t hear who is calling me. i have to use a headset or switch to speaker when calling
ikbenhier said:
i,m overklocking to 247 for about 2 years (homescreen ++). the last 2 months i overclocked my elf to 260. but my divice became to unstable i had to clock it back yo 247.
did you install any other software just before your device died? i think {on my divece} it has to do something with memory. because after i installed cleanram and start using it, i start to notice the issues you described. now i,m not using cleanram anymore and the problems where gone. it still occours that my elf hangs, but i think that has something to do with the fact that some softwares i installed are written for newer devices with more speed/memory. i,m pushing my elf to/over the max with the result it slowly dies.
i for instance have the problem that i can,t hear who is calling me. i have to use a headset or switch to speaker when calling
Click to expand...
Click to collapse
hi in my htc elf i used omapclock on 150 to 270....very stable, fast...for your problem go to hard-reset to reboot....fun...
ikbenhier said:
i,m overklocking to 247 for about 2 years (homescreen ++). the last 2 months i overclocked my elf to 260. but my divice became to unstable i had to clock it back yo 247.
did you install any other software just before your device died? i think {on my divece} it has to do something with memory. because after i installed cleanram and start using it, i start to notice the issues you described. now i,m not using cleanram anymore and the problems where gone. it still occours that my elf hangs, but i think that has something to do with the fact that some softwares i installed are written for newer devices with more speed/memory. i,m pushing my elf to/over the max with the result it slowly dies.
i for instance have the problem that i can,t hear who is calling me. i have to use a headset or switch to speaker when calling
Click to expand...
Click to collapse
No, I was running Blue Elves ROM for the most part. No other software seemed to cause any problems. Was using SKTools as my cleaner, backup, etc. Seemed to work fine and didn't seem to creat any problems. Am using it on my current Elf with no problems.
psycoy said:
hi in my htc elf i used omapclock on 150 to 270....very stable, fast...for your problem go to hard-reset to reboot....fun...
Click to expand...
Click to collapse
How long have you had it overclocked? In the beginning mine also was very fast and stable. Took about a year and a half before I began to see signs of problems, small at first--such as the clock delay in showing the correct time. I think (maybe I'm wrong) that was the beginning of the end for my Elf. BTW, dead Elfs are great backup battery chargers.
Related
Is it bad for the cpu of my qtek200 to overclock it? for example run it at 230mhz?
lordsinasina said:
Is it bad for the cpu of my qtek200 to overclock it? for example run it at 230mhz?
Click to expand...
Click to collapse
use the search function , you can easly overclock it to 260
over clocking issue
Hello all,
I have purchased a used prophet, unfortunately the person who sold it to me did not use it for approx 3 months, so what i did naturally is as soon as i purchased it i have up graded to WM6 Touch rom. I have activated the over clock feature which worked great.
After a few hours my battery suddenly died, it turned up that the battery needed to be changed after i purchased a new one i released my phone kept hanging and becoming slow and sluggish, i started to hard reset and re-install roms and so on, then i remembered that i have set my cpu speed before it dead to approx 65 Mhz. So i re-installed the over-clock app and set it back to 195, now it works great....
so be carefully
well first of all i apoligize for my english..
so.. i have problem with my herald with battery drain.. i dont know what's the problem. ive tryed pdaviet 1933 and 1938 bulids, 3 versions of Touch-it and my own touch-less compilation but i every rom average power consumption is ~200ma instead of 30 (from wizard or universal) and battery is dying in 10-12 hours...
i am sure that is not any of 3rd party apps that i installed.. some process must use cpu all time. sometimes (but rarely) it falls to ~50ma (checking with acb powermeter) but i dont know when or why...
i cant find any wm5 rom in net :/ i mean ANY.. i want to try is this problem exist only on wm6 and maybe it is possible to cook wm6 rom with some files from wm5..
my unit have signs of fall and maybe it is hardware problem but i googled problem and i see i'm not alone
please - if someone have wm5 rom on harddrive please upload it and send me link.. well i cant use rapidshare at home..
http://www.phm.lu/Products/PocketPC/TaskMgr/
this task manager let you see the processes
i know this prog and killed every process that is not needed for system to work.. :/
i have tried to disable some devices and services but i doesnt have much time to test every single file.. first of all i want to try wm5 to check that the problem exist there or not..
Which Radio ROM are you using? That might be the problem.
no, thats not problem - ive used some 2.9x (i dont remember) and now 3.0x but powerconsumption is too big even in flight mode. its diffrent kind of problem..
ivanmmj said:
Which Radio ROM are you using? That might be the problem.
Click to expand...
Click to collapse
Yes, that can be one problem. Older radio versions can result in unneccessary power-drain. But mine reads +105 to +115mA when idle. CPU usage is 2-4% when idle. I don't know the stats of wizard/universal, but, battery life of my unit is just fine. Lasts me a full working day with ~10% left to spare
My radio is the latest(03.07.90)
so imagine that wizard (almost same hardware) can have power consumption less than 30mA.. so can live 3-4days...
and service manual for herald claims that power consumption in idle mode must be less the 50 (as far as i remember) or you must replace MB
my battery is ust 5days old(bought a new one few days ago from boxwave)
edit: WM5 dopod official ROM is there on the FTP(i hope so)(uploads>herald)
<i'm stupid> i didnt checked uploads folder... :S thanks! currnetly downloading but i am going to work :/
thats not battery, bt, wifi, 3rdparty software or hardware problem. all heralds wm6 have huge power consumption and i dont know why... i'll check wm5 tomorow..
@slimag: first check if this drain is there in wm5 too If yes, I'll be going straight back to WM5, if it can give me 3days battery life
kdskamal said:
Yes, that can be one problem. Older radio versions can result in unneccessary power-drain. But mine reads +105 to +115mA when idle. CPU usage is 2-4% when idle. I don't know the stats of wizard/universal, but, battery life of my unit is just fine. Lasts me a full working day with ~10% left to spare
My radio is the latest(03.07.90)
Click to expand...
Click to collapse
The newest radio actually drains more battery...
I've had my Herald at 8mA...
Most of the time it's between 30-200mA when I'm overclocking...
ivanmmj said:
The newest radio actually drains more battery...
I've had my Herald at 8mA...
Most of the time it's between 30-200mA when I'm overclocking...
Click to expand...
Click to collapse
But, ivan, even with the flight mode, it is reported that there is not (much) change in mA consumption
kdskamal said:
But, ivan, even with the flight mode, it is reported that there is not (much) change in mA consumption
Click to expand...
Click to collapse
Everyone's best guess is that it's a bug with the radio attempting to regain a signal even when in flightmode.
so which radio do you recomend? i had 2.97 before and onestly i dont see any diffrence after upgrade. i'll try 2.94.
and the funny thing - i disassemled my herald and clean every part and now its not 180-200ma but 100-150
next day. next rom, next radio... no diffrence :/ i didint checked wm5 yet but i flashed my herald with 2.94 radiorom and powerconsumption is still at ~180...
whole day and lowest point was 130ma.. quite anoying..
slimag said:
next day. next rom, next radio... no diffrence :/ i didint checked wm5 yet but i flashed my herald with 2.94 radiorom and powerconsumption is still at ~180...
whole day and lowest point was 130ma.. quite anoying..
Click to expand...
Click to collapse
Have you checked the WM5 rom and experienced the same drain?
kdskamal said:
Have you checked the WM5 rom and experienced the same drain?
Click to expand...
Click to collapse
no :/ i've got crazy week and passed only 2 of 6 exams yet... i've got 3 cooked roms (on my own) and thats wm5. i tried once to flash with wm5 but i'm stupid and i've forgot to cut out spl/ipl and then there were new problems with my pc (graphic card just comited suicide..) so i dont know yet..
couple things ive seen..
1) 2.94 radio is batteryfriendly and reception is good.
2) sometimes after reset before i go to bed power consumption is less than 30 (~10mA) and then i receive sms and it jump up to 100mA... :/
3) the only process that take cpu (about 5%) is Shell32.exe . i'm not sure is this primary process but in wizard it takes no more cpu than any other process at idle...
i really need more time.. i've got tousands of ideas for a custom good rom and no time at all...
slimag said:
no :/ i've got crazy week and passed only 2 of 6 exams yet... i've got 3 cooked roms (on my own) and thats wm5. i tried once to flash with wm5 but i'm stupid and i've forgot to cut out spl/ipl and then there were new problems with my pc (graphic card just comited suicide..) so i dont know yet..
couple things ive seen..
1) 2.94 radio is batteryfriendly and reception is good.
2) sometimes after reset before i go to bed power consumption is less than 30 (~10mA) and then i receive sms and it jump up to 100mA... :/
3) the only process that take cpu (about 5%) is Shell32.exe . i'm not sure is this primary process but in wizard it takes no more cpu than any other process at idle...
i really need more time.. i've got tousands of ideas for a custom good rom and no time at all...
Click to expand...
Click to collapse
Maybe you just have a faulty phone. It's not happening to most of us and it's across multiple ROMs.
sooo i passed already only two exams and 6 more are waiting for me but i cant wait..
i tried today to flash my device with wm5 once again and i cant make it works... device doesnt boot up (unlike my ported wm6.. it hangs on boot screen for now but i think i can bring it to live in few days)
i cut out wm5 os and make nbh again like for wm6 with htctool and wm6 works but wm5 shows only first boot screen after format fat and after reset its.. well.. its just dont turn on at all.. only way is to go to bootloader again and flash with another rom..
maybe wm5 doesnt wor with ipl/spl 4.xx?
does any one ported any wm6 rom? i'm currenlty trying to make a paradox (from wizard - 37,4mb ram free) works but im thinking about using some files from wm6.1 for hermes.
what files from herald are necessary from xip and from oem drivers?
currently im doing some researches with battery drain caused by camera driver (sk35..) maybe i'll cut out camera from final rom (i dont use it at all)
Where to begin....
I have had my wiz for about a year now (maybe longer) and everything was running fine. Nothing special installed really. I've Sim and CID unlocked, flashed to 1.1 and then flashed again to Mr. Frazzz's XDA Mobile 6 (awesome btw) and had been running that for quite some time with battery status as the only other thing I've really added.
One night I was out and managed to hit my touch screen on a table and it shattered. Things ran fine for a while (could still see considering the touch is seperate from the LCD) and managed to use it as a phone using shortcut keys. Then i started getting problems like slowing down etc and I figured it was partially due to the duress of a cracked touch screen making the phone think it was having a part of the screen pushed (or not there) so i finally had the screen, both the touch and lcd, replaced. Shortly after, I noticed the phone would freeze up randomly. (this is also about the time i switched from t-mobile to at&t prepaid) Sometimes it would do it 3 or 4 times a day and the only remedy is removing the battery. Sometimes it will go for over a week without any issues. Any ideas? Im ready to melt it.
Here's what I've done thus far with no results:
Reflashed to official t-mobile 2.26 and then flashed to Mr. Frazzz's WM6. I've re-installed battery status and then came across a thread stating that the latest version of which might be causing hangups....so i gimped it at first, using only settings I had known to work before with no issues and later uninstalled the whole thing. Still having the same problems.
I have the WM6 radio fix for cingular and 2.69.11 radio as well.
One thing I do notice is that, everytime i make a call and receive the system message stating what that call had cost me, it can cause weird things to happen if I was in the process of doing something else. Not sure that's part of the issue though considering the phone will just be sitting in my pocket when it does randomly freeze.
Is it possible that my mem card is just being jostled and causing issues? or that somehow the powerbutton is being adversely affected inside my pocket if the phone gets flipped upside down? Anyone and everyone's imput would be greatly appreciated, especially if Mr. Frazzz has any input. BTW, this has happened using both WM6r3 and r5 by Mr. Frazzz. I upgraded to r5 this last time i reinstalled WM6.
I'm guessing battery status is doing it. Same thing happended to me, did a hard reset, installed all my programs again excluding battery status and everything is fine.
Is there something else I can install that will overclock for me when the phone is active and kick down the speed when idle?
I also used battery status for the disable proxy thingie when wiFi is on.
Well...Overclocking is never safe and the manufacture of a cpu has clocked a cpu at a set speed. Why, because it is more stable. So anything past the stable speed will bound to be unstable. I overclock mine to 260 and still do not notice a boost so either you leave it at 195 and run smoothly or make it "faster" and have more issues. Your call.
Hi,
Searching why my D2 is dead some mornings whereas the batteries are good on the evening, I found out that the D2 freezes at 23h55 - and that sort of deadlock consumes the batteries during the night.
It's now 3h20AM, I have put the screen on (D2 was in standby mode, screen being off) => it mentions 23h55, and it is frozen (no response either with the stylus or the buttons).
To what could that freeze at that very particular time could be linked to?
I must add that sometimes during the day the clock is desynchronized (10 minutes late for instance, as if the phone has entered a deadlock during 10 minutes and came back to life after...)
(I created this particular thread from the batteries problem one:
http://forum.xda-developers.com/showthread.php?p=4780101#post4780101
as this one is a very specific behaviour, not related to 3G or common optimizations regarding batteries).
Markot said:
Hi,
Searching why my D2 is dead some mornings whereas the batteries are good on the evening, I found out that the D2 freezes at 23h55 - and that sort of deadlock consumes the batteries during the night.
It's now 3h20AM, I have put the screen on (D2 was in standby mode, screen being off) => it mentions 23h55, and it is frozen (no response either with the stylus or the buttons).
To what could that freeze at that very particular time could be linked to?
I must add that sometimes during the day the clock is desynchronized (10 minutes late for instance, as if the phone has entered a deadlock during 10 minutes and came back to life after...)
(I created this particular thread from the batteries problem one:
http://forum.xda-developers.com/showthread.php?p=4780101#post4780101
as this one is a very specific behaviour, not related to 3G or common optimizations regarding batteries).
Click to expand...
Click to collapse
it's scared of the midnight ghost hour so it stalls before it gets there?
seriously though, i would check/delete the alarm registries (and any other time based notification you can think of)
I remember people getting ghost alarms (which would often freeze their phones) in WM5 (http://forum.xda-developers.com/archive/index.php/t-242103.html)
good luck
I had the same problem, unfortunately only found a hard reset resolved the problem.
That's indeed what I've done 2 days ago, since then all runnin' fine (let's wait for 1 week to be sure, sometimes I hadn't any problem for an entire week).
I can't think of other suspects than RTremote and Galarm that were the only "sleeping" programs I had on my D2...
In the past I also saw my phone waking up at midnight, yesterday that wasn't the case.
Problem still there :-(
My phone froze Sunday evening at 23h54 (time still mentioned as it was after midnight).
This time the phone was charging, whereas being full the battery led remained orange (last times even no charging, the freeze occurred).
Only the power button was still working as previous times (to put the screen on/off).
My configuration is the following:
- Model: Touch Diamond2 T5353 (French Orange)
- ROM: 1.39.406.1 (49068) FRE (date 16/06/2009 - official 21/07/2009 HTC ROM)
- Radio version: 3.43.25.19
- Protocol version: 61.20t.25.10U
- SPL Olinex 1.83
- Lock on (code to be entered after 5min max to be enable to use the phone)
- No "dormant" application installed (as could be RTremote or Galarm)
- Applications installed: Resco Explorer (+plugings), Resco Audio recorder, Diamond Ati D3D drivers, Microsoft .NET CF 3.5, Marathon, LSD2008 Lite, GPS2Blue, ShakeAndSave, Hologram, TaskMgr, dwRuler, hdWobble, PowerRadio.
I can’t see what the source of the problem is… Any ideas?
Any similar behaviour on your phones?
Hello!
I had the same issue and realized that it was Galarm that "haunted" my Diamond 2 every night at around 23:58
As long as you don't have the above application, I would suggest a hard reset and then check D2 without installing any apps for the first night
Hello,
i have the same Problem as Markot. Only the Power-Button works. No timebased App is installed. The problem is in most cases the TD2 is connected to a charger, not only on midnight.
Bye MyPass
Hi all,
I think I got it!
Actually, to be more comprehensive with my "flashing history", I did first, some months ago, the ROM flashing with SPL Olinex 1.33 (HTC official WM 6.1).
Then I discovered "the bug" I described in this thread (and in another thread before, the battery leaks, finding my phone dead in the morning...)
Doing a hard reset did not change anything.
2 weeks ago, I decided to try the official HTC WM 6.5 release (I previously installed SPL 1.83 after having installed WM 6.1).
But not completely satisfied, I put back WM 6.1 WITH SPL 1.83 THIS TIME.
And it's working fine since then, no freeze anymore during 1,5 week.
So the problem was related to flashing WM 6.1 with SPL 1.33 - whereas when doing it with SPL 1.83, all runs like a charm.
Another clue is the blinking led on sms received (default behaviour): after flashing WM 6.1 with SPL 1.33, I have never seen it. After flashing WM 6.1 with SPL 1.83, the blinking appeared.
Cheers.
Guys,
If you are using Galarm, there is a register value "midnightwakeup", try to set it "false"
i made a hardreset and the problem was solved
i had this problem last night. as you expect i was very veri surprized. almost to be late for work. anyway, since i have bought the phone it did nothave such problem. This may be the problem "Setings tab->All Settings ->personal -> phone ->Time Zones Tab." i have remembered that i played with this particular setting last day. now i have disable it and we will see what will happen tonight.
look at yours TD2 and if this thing is checked, then unchecked it. it may help. At least wount harm
no problem so far, after unchecking this setting.
Hello,
I am owner of HTC P3600 from last 12 months and i used custom roms too all was working fine and before 2 days i found that whenever i leave the HTC for few hours it hangs and when i press the standby button to wake it up nothing appears on the screen and i have to reset it to start it again.
Updates:
Ok i re flash the Hard SPL, Radio and Rom and until now (in last 24 hours) it don't hangs.....
Update 2: I think the battery is the problem as the battery time is decreased from 3 days to just 1 and a half day and it freeze now while charging....
Any solution? anyone experience the same problem?
Help please with your views...............
I have a similar problem. My HTC started crashing after a rom update. However, i think it is not crashing due to software...
Well, the software is more CPU demanding, so it heats more than before. Also, i started using backlight properties set to high (i need to set to low again), which again highly heats the PDA. Finally, when charging the battery tends to get very hot. All this put together causes the CPU to overheat and crashing.
At least, from my experience, when it crashes it is always very hot.
razpowa said:
I have a similar problem. My HTC started crashing after a rom update. However, i think it is not crashing due to software...
Well, the software is more CPU demanding, so it heats more than before. Also, i started using backlight properties set to high (i need to set to low again), which again highly heats the PDA. Finally, when charging the battery tends to get very hot. All this put together causes the CPU to overheat and crashing.
At least, from my experience, when it crashes it is always very hot.
Click to expand...
Click to collapse
Sounds like a radio rom problem. Try to reflash radio.
Thanks for the advice!
I will reflash the radio rom.
If it solves the problem i will update my post here so everyone else knows how to solve this kind of problem.
it helped ? reflashing the radio rom ?
lol you ****up your phone hahahahahahahha
No, it did not helped. Probably it is an hardware problem.
The pda was intensively used connected to the computer, because it was used for software developing.
I think it is broken, hehe.