I've been lurking on these forums since I got my diamond, about 5 months ago, and i would like to say, I would have sold my diamond about 2 weeks after buying it if it wasn't for all the knowledge and tools available here. Thank you.
Now, I've been flashing my phone every so often, with ROMs such as Swtos, Panosha, Duttys, AZTOR, Wildberry, Dia Diut, and most recently (wherein the problem lies), NATALY 2.1, Cloudy 1.0 and udK Syrius R3.
Now with these latest three roms (2.03?), i started to encounter a similar problem over and over again, without exception. If I try to launch a program while another is using the CPU, the phone will begin to crash. First it will become unresponsive, then programs will no longer open, and eventually, the only thing that can be done is a soft reset.
For example, the alarm will activate (klaxon), i'll flip the phone, and hit off. Now I know the problem has begun because though the phone has returned to the home screen, the title bar may still show the image from the alarm. Now the phone will work like its cpu is being heavily engaged and I can never reach task manager to see what it is. The hard volume keys frequently cause the phone to begin behaving in this manner. Soft reset only solution again. TF3D still animates, but programs will never appear on the screen if you try to launch them.
Same sort of effect on Cloudy's and udK's, except after the soft reset, the phone would begin to reinstall the rom again, as if some sort critical error occurred.
I have a DIAM130, and i've heard that to install 2.03 base ROMS (such as NATALY2.1 and Cloudy, is that correct?) you should first install a 2.03 SPL and a 2.03 stock ROM, then upgrade the SPL, then the ROM.
The latest SPL i've seen here is 1.93, and installing this increased the stability of these ROMs from 30 minutes to about 1-2 days, but the same problem occurs.
(also, haven't been able to find a stock 2.03 ROM on here... am I blind/illiterate?)
Latest addition to this problem (first occurred a few minutes ago after the phone began reflashing itself again after the aforementioned problem): Windows began the usual first-time boot customization procedure, and is now giving me an error: Run FILEOP \Windows\Menu_FILEOP_Operator.txt failed.
Is there some sort of corruption or hardware failure going on?
Well, thanks in advance
EDIT: Problem solved by reflashing stock SPL and 2.03 ROM, then flashing what I wanted. The impression i get from the pros here is that I flashed a ROM which wrote to some memory location that shouldn't have been written to.
Related
I seem to be having some biig issues with my tilt and was hoping for someone to shed some light on the situation for me, I have a tilt, now running on hyperdragon IIIr , hard spl 3.56 and a emonster radio, ever seince I've unlocked it and flashed the a rom I've ran into oone of two issues 1. rom works fine with exception to heavyish lag on typing that forces me to type slow (E.G. duttys 19716 hybrid) and I do a lot of typin so the lags is a big issue 2. running currrrently beforemention hyperdragon IIIr and emonster radio, (although I've had the issue on other radios) and it runs fine at first, I tap the power button don't use it for 20 mins or so then when it turns back on it either steps in from dark to bright and will be VERY unnresponsive like having to tap the windows button 20x times before I get one tap I've been flashing like a madman tyig tofind a rom that generaly works... PLEASE HELP
Learn to use search. I, as well as many other people, have the lag issue. It's been mentioned before.
The other issue could be either your device, ROM, or radio. Change to an official radio. If you still have the same problem, try going back to the stock ROM. If the problem continues to exist, it could be your device.
If it turns out to be the radio, simply change radios.
If it's the ROM, address it in the ROM's thread, not in a new one in a different forum.
If it's your device, you had better learn how to get it back to it's OEM state, provided you have a warranty.
Also, spacing, punctuation, and spelling tend to be helpful when seeking help. I'm not saying it has to be perfect, but it's nice for it to be understandable without having to analyze it twice.
Now, run along and play.
mr4r4n said:
I seem to be having some biig issues with my tilt and was hoping for someone to shed some light on the situation for me, I have a tilt, now running on hyperdragon IIIr , hard spl 3.56 and a emonster radio, ever seince I've unlocked it and flashed the a rom I've ran into oone of two issues 1. rom works fine with exception to heavyish lag on typing that forces me to type slow (E.G. duttys 19716 hybrid) and I do a lot of typin so the lags is a big issue 2. running currrrently beforemention hyperdragon IIIr and emonster radio, (although I've had the issue on other radios) and it runs fine at first, I tap the power button don't use it for 20 mins or so then when it turns back on it either steps in from dark to bright and will be VERY unnresponsive like having to tap the windows button 20x times before I get one tap I've been flashing like a madman tyig tofind a rom that generaly works... PLEASE HELP
Click to expand...
Click to collapse
It almost sounds like you installed an application that is causing your device to freeze up. Also, remember to hard reset after flashing. If you can please list the applications and sips you have installed and maybe someone can point out the culprit.
trust me spelling is never normally an issue but im typng from the device, unfortunatly I don't have a home computer at the moment. I've used search, I just haven't come across anything that matched my situation, the best working rom so far was duttys apr 29 hybrid. I've done some different radios and if anyone would be able to id love to read whatever setups you guys have on your devices thatwork and whatever issues you guys may be having btw my hard spl is 3.56 as well. I mean alll I wanted was 6.1 style messaging a good strong antenna (emonster is working well) if the roms fome with extras cool, if not its all good, I just need the device to work, thanks for all you help people
and btw the issue with the major slowdown is after flash (and hard reset) when I first tap the power button to put it on my belt for later no apps installed
This will be tedious, but try going back to AT&T Stock and see if you're still having an issue with the slowdown. Also, you might want to try looking for the Tilt Keyboard fix and trying that first. I still have lag with it, but it's worth a shot before you go back to stock.
If you still have issues with the stock ROM (try the stock SPL too if you can, there's instructions for going back to OEM you can click here to see those)
If you have the issue with everything set to stock, it's your device itself. If the problem goes away after reverting to stock, then try re-doing the whole SPL and flashing process for the ROM of your choice. At that point, you may wish to consider addressing your issue in that ROM's thread.
you are a genius, i ran it from the beginning and started it from scratch, i started with a light rom the new Hyperdraggon IIIr emonster rom and then hard spl'd at 3.29 (after i did the whole re stock and unlock process) im guessing i might not have done it right from the start and or the 3.56 spl might have been the problem also but its acting sufficiently well now i will keep you guys posted thanks for the support
I have 3.56 and have no problems. I almost always use a light rom and throw EVERYTHING onto my storage card. You also might trying running Pocket Mechanic
Hi all,
Recently received a replacement diamond after my previous ones touch screen stopped responding correctly, and this new one has its own fun problem, i stupidly didn't test the new one for no more than an hour, and decided to upgrade the rom to the exact same configuration as my previous diamond that worked fine for months, with the unsigned hard spl, the recommended radio, and the diamond project rom, after a few hours of running the device intermittently resets while not in use, and resets randomly on certain applications - such as changing the time of the alarm sometimes resets the device, i have tried re-doing the hard spl n radio, and numerous roms, i have found some rare posts on the net that sound similar where taking the battery out over night is suggested, something to do with volatile, although i didn't believe this i did try to no success. Any suggestions? many thanks!
Hi Guys,
I am facing a strange problem since a few weeks. My Blackstone sometime does not switch back on again when I press the Power Button after it was suspended(=NOT switched off).
The only way the get it running again is removing the battery and putting it in again. After that the device takes a really long time to boot. Stays at the Smart Device Screen (with ROM info displayed) for about 30 - 40 seconds.
This happened about 4 times the last 6 weeks.
All ROMs used were from LEO - all kind of different versions. It also happen with the newest one 3.2
SPLs: HSPL, HSPL 1.56, SPL 1.56
Did anyone else notice such a behavior? Do you think this is a sign of a Hardware problem, or could it be software related?
Greetings,
Tommi
got that often when i do something stupid with it ie installing some software wrongly.
ive had to hard reset it each time, but luckily i had sprite backup before that at some point. and it works then
posted twice
Hi! For a while I've been searching for a reason why my phone seems to freeze almost daily while charging or before / after I snooze a morning alarm. And sometimes during the night, maybe it's random. By freeze I mean the phone is sleeping and when I push the power button nothing happens. The only way to restart it is to take off the cover and either remove the battery or press the little reset button.
I use itje's ROM with standard WM6.5 and Manila 2.1. I tried diferent builds and newer Leo ROMs, but I always get the same problem. It didn't happen some time ago when I was using WM6.1 + Manila 2.0.
While searching in the forums for solutions, I noticed there are some users with the same random freezes using various ROMs from different chefs. But most of the users don't seem to have this problem, which is weird. I guess the hardware should be the same, so does anyone have any idea why this freezing happens only to some of us?
I tried different methods and ROMs, countless hard resets and re-flashes, even additonal Stock-SPL and Hard-SPL, but nothing seems to work. It even happens if I install no other programs and don't have the SD inserted into the phone, only my SIM card. So it's not from external programs (like G-Alarm) either.
Well, any helpful information or advice? Thanks!
I am experiencing the same problem. If anyone got a solution for this, please share.
Regards, Eduardo.
i have the same problem to but only with the cooked wm 6.5 roms and higher not with the rom that came with my x1
i get the same problem. i'm using itje's Touch I-T Xperience 15 6.5
Now I flashed a WM6.1 ROM with Manila 2.1 to see if I still get the problem. Do you think our phones have a problem with the Windows 6.5 builds or maybe the problem is with Manila?
Did anyone try to live with one of these ROMS for a few days with Manila disabled to see if you still get the freeze? Maybe I'll try this also after I finish my 6.1 test. It's very annoying that we don't even know the cause for this freeze yet...
have the same problem when using 6.5 but when on 6.1 nothing of the kind...
Just to share. Some chefs have mentioned this and I myself can attest to it.
I was using 2 ROMs that were free of the problem more than 24 hours , Touch X 10.8.2 and Valkyrie 4.5.502. And both times I managed to cause the "standby of death" by using 2 different alarm programs, G-Alarm and Klaxon. Once I activated alarms using these programs, within 3-4 hours my phone froze.
That's my experience anyways. Some ROMs by default will die without doing anything, so I'm not sure about those. But if you have a stable ROM and want to avoid it, I think it should be fine.
Well, I can confirm that on various itje 6.5 ROMs I get the standby of death without installing any alarm program. I didn't install ANY programs, for what it's worth. And others can use G-Alarm 2.3 and don't get this freeze.
Didn't use Valkyrie ROMs yet. I'm testing now Touch X 10.8.2 and I have G-Alarm 2.3 installed. Let's see if it dies in the next 48 hours while on a 6.1 build...
Here is my experience...
I never got standby freeze issue(never used G-alarm/Klaxon), but i do get black screen or garbled screen issue randomly while receiving call irrespective of the ROMS(wm 6.5/6.5.1).
Only one time almost a week i didnt face this issue, then later problem repeated. So i realized that week i've used COM4 build. So for testing it i tried again same one for a week and problem didnt exists. Since the ROM which i used has default X1 dialer which i didnt like at all.. so got updated to other ROM and started face the same issue
Maybe some of us have a slightly different harware in our X1 that triggers this freeze, but only in WM 6.5?
So far the WM6.1 + Manila 2.1 is working fine, lots of customizations made by me after flashing too. G-Alarm managed to wake me up OK.
Darkchaser said:
Just to share. Some chefs have mentioned this and I myself can attest to it.
I was using 2 ROMs that were free of the problem more than 24 hours , Touch X 10.8.2 and Valkyrie 4.5.502. And both times I managed to cause the "standby of death" by using 2 different alarm programs, G-Alarm and Klaxon. Once I activated alarms using these programs, within 3-4 hours my phone froze.
That's my experience anyways. Some ROMs by default will die without doing anything, so I'm not sure about those. But if you have a stable ROM and want to avoid it, I think it should be fine.
Click to expand...
Click to collapse
Well you can count Valkyrie 4.5.502 out because i installed it yesterday and this morning after my alarm went off about 20mins later the phone frooze. I have been experiencing this for the past months and i REALLY hate this phone now. I have tried all sorts of tricks from reseting the phone around 9pm to just not running ANY program and it still freezes. I have tried all sorts of roms with the exception of Touch X 10.8.2. I guess i might as well give that one a try. I will keep an eye on this thread for a solution.
On an older Valkyrie TR build I was getting the problem and I fixed it by doing a soft reset with the SD card out, waiting for everything to load up and run nicely, then inserting the card again. Went to the music tab and waited for it to load all my tunes and the same with photos. Didn't have the problem after that, but I was only on that ROM for about a week.
I thought it may be related to usb port driver issues in WM6.5, but it could also be the audiomanager in manila or some conflict between a WM6.5 process and a manila process.
Anyway, will be trying 4.4.81TR Valkyrie and see...
But the biggest question is why some (most) people never have this problem...
Never seen this problem on WCX 22001 Pure wm6.5 rom and I'm using it for about one month. I've installed many apps and my X1 works great with battery about 2-3 days using WIFI, BT, and all other stuff. No Manila - no problem in this case. It's an older build of WM6.5 but with newer builds WCX Rom users didn't complain about freezing problem or alarm issues.
So maybe it's Manila?
Today I wanted to flash Itjes newest ROM but I'll wait for solution couse my phone should wake me up today
Can program your phone Lockscreen has frozen the rechargeable device. Best before charging you restart your phone and not run any programs.
yes i get this problem too.. every morning my phone is off.... so it really needs to be looked into.. it seems to occur from more recent builds of 6.5..
i was previously using a wild child pure rom from about 3-4 months ago (6.5 early build)... this issue never happened...
then recently i upgraded to the V11 Unoff series and now it occurs.. and is obviously occuring for a lot of people with other recent builds of 6.5...
if the solution is ever found please let us know....
I might be completely off here... but I used to have this problem often, in addition to having slide to unlock malfunction on me, even with the newer rom builds.
When I unchecked the boxes that said display owner information/notes when device is turned on, both problems were gone - it might just be a coincidence though and I've only been testing it for 2 days.
Hey guys,
I've been having the same problem, only that this are the situations in which I faced the issue with my X1i (and managed to replicate the freeze):
-Receiving SMS while charging (no pc conection)
-Charging while alarm goes off (again no pc)
-When task or appointment announcement sets itself to sleep (i.e: you ignore it) while charging. (go figure, no PC)
-When after ignoring (not hitting dismissed button) task or appointment screen shuts off (Running on battery)
I've also gotten the problem in other situations, but i couldn't replicate them. The only Thing I did notice was that there is a growth in the rate this happens over a span of 3 days after flashing/hard reseting. In my case, it was one increment per day (ie: 1st day, happened once; 2nd day, twice; 3times the 3rd day.. then, i reseted or replicated, so my statistics went down the pipe )
Other thoughs: what radio are you guys using? maybe we can narrow it down to a radio as well. Thus far I've seen it narrowed it down to Manila 2.5, but then others do not have this (and then there me, with Manila 2.1, that has it ). I changed my radio y-day and hasn't happened yet (xing fingers though...) wil try to replicate tomorrow after my alarm wakes me up
My info:
X1i Black (came with R3 generic UK ROM, Radio. 1.14...)
Issues happened with: Radio 1.10.25.18 (Installed with NRG's ROM vOCT 28)
ROM info: (see signature..)
Manila: v2.1.191...
Current radio: 1.14...
Carrier: AT&T US
I tried to contribute as much info I could get about this issue... hope we can get it solved.
I'll try to flash again a WM6.5 version to see what radio will be installed. This week I needed my phone WORKING , so I used a 6.1 ROM.
I didn't find a pattern for my freezes, but I think it mostly happened while charging from the outlet, or in the morning before the alarm went off (very bad thing to happen), or after I snoozed the alarm (again, very bad).
I read somewhere that it's useful to format your SD card before flashing. I don't see how this could help, but I'll try to flash via USB or from another newly-formated SD card. I always flashed with kovsimg.nbh on the SD root and I only formatted it when I got the phone, 9 months ago...
Also, some say it's good to flash first an original ROM, hard reset, then install the custom ROM again. I tried that, even stock-SPL and hard-SPL again, but didn't seem to work. Maybe I had 48 hours without freeze, but then it started again.
@8SE8 - I never had those options checked, so we can rule that out I guess.
I have been reading about this issue here and in another forum - mainly
because I had seen it only one single time. It actually occured when I was
loading the device during the night. I do not remember which ROM it was
exactly, except that it was an itje ROM with Manila 2.5.
Then, I went back to Manila 2.1 and WinMo 6.1, Touch_X 10.X.X. Must say,
that is still my fallback ROM, it feels extremely fast, it is stable, memory
usage is low - what else to wish?
Next, I went to the multilanguage Rhodium based Manila 2.1 and WinMo 6.5
from itje in my own language. After installing FM Tuner, a correct dialer and
some tweaks, it is also very fast and stable, memory usage at 50%. No more
soft resets since almost a week now, no "stand-by of death".
The difference to others is maybe: I do not flash using the SD card, always
with the USB connection. Is this provoking the difference? I cannot imagine,
but this is what I can contribute here.
Hello everyone,
Yesterday I installed the official upgrade from HTC for my Diamond 2. Besides my personal settings, I installed a task manager from this site. Now, my phone has continiously 'Sleeps of death'. Sometimes he wakes up after 5 minutes or more. I opened the taskmanager and I took a look to the processes and everything was ok, except Manilla, which had a CPU usage of 97%.
I have a WWE edition phone.
Can someone help me with this? I searched for 'Sleep of death', but those issues are from july 2009 and at that time there was no upgrade yet.
EDIT: I deïnstalled the Task manager already .
I have restarted the device once again and now I looked from the beginning to the processes. It seems that first services.exe uses a CPU from 90% and higher and after a few minutes, this decreases and then manilla goes to CPU usages of 95% and higher.
First question will be:
Did you hard reset after you flashed your new ROM?
O, I though that flashing a new ROM goes hand in hand with a hard reset. I didn't. Why is it necessary?
Reminence of the old ROM will remain as the RUU flash doesn't completely overwrite 100% of the blocks. A hard reset will almost always resolve any issues.
Issue still not solved
Ok,
I've just executed a hard reset. The problem is still there. After the first soft reset, required for some adjustements, he had again a SOD.
What is wrong?
I assume you are not HSPL'd as you are installing stock upgrades, correct?
Did you download the upgrade from HTC's site using your S/N?
There are a few things you can try.
You can reflash the upgrade. Always HR after.
You can download MTTY and perform a "task 29" which will wipe your flash drive and provide a clean platform to flash to.
or, reflash to your stock ROM, then try to reflash the upgrade.
Also, search on SOD as there may be other fixes that I am not aware of.
The typical cause is driver incompatability.
I always install the official upgrades after downloading them from the official HTC site with my serial number.
I'll try your method and after that I'm going to report it here if it was helpfull.
Thank you!
Possible solution
I just read the topic about the problems with the HTC sms application. Well, I discovered, that this app also causes my problems, becaus it loads all smses all at once, every time I have to use it. It just seems that this HTC app isn't made for such a large numbers of messages.
The solution can be found in this topic, I think: 631449
I'll try this...
EDIT:
Ok, I found the solution! It was indeed the HTC messaging app what caused my problem! I installed the 'Zenyee Disable HTC Messaging 1.2' application and now my smses at loaded within seconds! I hope that HTC will come with an update for this app soon. It was very nice, but I can't handle a 1000 messages.
My mum had 3k+ smses in her TD2, and was experiencing lag.
I upgraded the ROM to stock WM 6.5 2.53.707.4 (Manila 2.5.20113030.0), (no other programs installed)
and then restored the trimmed-down 1k+ smses via MyPhone
Sense was extremely sluggish. The phone started having the Sleep of Death - soft reset and power on, power off after 5 seconds, power on for 1 second, power off for 10 seconds - power on - SOD!
The problem was solved by turning off Sense (from Today), and disabled the HTC Messaging with "Disabling HTC Messaging in manila 2.5" by zenkinz. The cab didn't work, but edited the registry manually and is now running the SMS Patch - it works fine now. Snappy on and off, runs programs smoothly.
I think that Sense 2.5 was never meant to handle thousands of SMSes.