yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] andes83:
Hi I'm another victim of this lock up issue it's not really common though I try a lot of ROM's and it's often when I go to sleep at night in the morning i get the dark screen.What I've "isolated" from my experience is that it happened more often on Miri's test ROM's (new versions 23xxx and 28xxx on 28xxx happened on two versions 28011 and 28014 ROM's)the apps that I install are always the same I don't do backups only a few times and can't find any connection between backups and lockups.My cure for this has always been change of ROM's until I bump again on this problem.I've treated this as a bug and waited for new releases as I didn't know it's that common for other users.I cannot give any proper information about other ROM's as i flash a lot of them but for sure never happened with Phamquang's ROM's that's for certain.To be honest my guess is that it has something to do with cache and memory settings or something the cookers do to "boost" the performance (cause no one likes a slow rom) ....but that's just shooting in the dark .
[Touch HD Windows Mobile ROM Development] Oemie:
Hmm...i have had three to four lockups per day after having the rom on my Balckstone for a week i think..

I really can't have all the lockups because i have to be reachable.

I went to another rom and the lockups started the same day...so i got a tip to flash a stock rom.. i did that and the lockups were gone for a whole day.. the rom was faster and everything seemed oké, till i started to read this topic..i got my first lock again..

Conclusion must be don't read this topic :D..:mad:

Annoying it is, i am going to try latest nrg and/or Phamquang rom and see what it will bring. I really like manila 2.5, so i hope nrg's wont give me lockups..
[Touch HD Windows Mobile ROM Development] Marne Jr:
Evreyone got his own "ways" to scape from lockups ... but what we really knows is that it is there ... waiting for ... and when you are not more expectaing it ... then it cames back !!!

One thing is certain for me ... I WILL NEVER BUY A LEO TOUCH HD 2 IF I KNOW IT IS POSSIBLE TO CAME BACK !!!

It looks like that film of friday 13.... in which there is a Jason that allways come back ... not matter someone do !!!
[Touch HD Windows Mobile ROM Development] Marne Jr:
Youtube...

What about many of us making a short movie with each one lockups and than we put it on youtube and collect the links and send to HTC asking for a solution ?!!?

I think it would be a good solution if this post don´t bring a definitive and all resolutive answer ...
[Touch HD Windows Mobile ROM Development] makbil:
Two things:

1- We are not using official HD ROMs. HTC will just tell us - rightly - to use official ROMs and don't flash unsupported custom ROMs, or buy an HD 2 :)

2- The videos will all be the same - a black screen :)
[Touch HD Windows Mobile ROM Development] makbil:
This is an interesting piece of information. It's interesting, because unlike you, Miri's ROMs are the only ones where I never have a lockup. I haven't tried PhamQuang ROMs as I have a different problem with that ROM, one of my applications does not run on it!

Did you install a stock ROM or use MTTY before flashing Miri's ROM?
[Touch HD Windows Mobile ROM Development] bodgeman:
Just had my first lockup after three days (after MTTY). Its disappointing, if not unexpected. For me the biggest problem is that i use my phone as an alarm clock for work (i'll have to invest in a £3 one from Wilkinson and dispense with my £450 multifunction device). This may become the biggest problem for the Chefs to overcome if it becomes an issue for many users.
[Touch HD Windows Mobile ROM Development] Marne Jr:
For sure it would be the similar videos, but with many example for all around the world ...

As I said on my first post I AM AT OFFICIAL ROM AND I DID MTTY BEFORE FLASH IT and was still having lockups...

If I do not have a lockup now it is because I am not pressing power button without lock it by long end key ...

I think you have a soft lockup type "a", but as I saw on other posts it seems that more people are having harder lockups even with official stock rom ...

To be more official I am using the first official stock ship rom with SPL 1.14 that is the rom in which I got fewest lockups but it still occurs if I press power button to make it sleep without long end key lock...

I am not sure if there are most people with soft lockups like yours or hard and annoying lockups like mine....

Let's stay here for a long to see what it shows !!

Bye.
[Touch HD Windows Mobile ROM Development] kostas66:
Something I noticed (I did not serch the posts of this thread): while the phone is "lockupped" and the screen is "dark, but on" (a note: I also had at least twice a lockup with the screen on, showing the home, but not responding...) the radio of the phone is still perfectly working... one hour ago somebody was ringing me, he was waiting for me to answer, but my phone was "dark and silent...".

As usual after taking out the battery and turning on the phone everything was ok again...

Regards,

K
[Touch HD Windows Mobile ROM Development] makbil:
You have a different problem mate. The lockup described in the opening post should not occur with the stock ROM.

You have a very valid point though, it would be very helpful to determine what kind of lockups people are having. Let's give the thread a few more pages, then I might add the types of lockups you suggested in the opening post, looks like it will be helpful.

One of my objectives in this thread is to make the distinction between general lockups and the specific lockup condition that occurs only on Manila 2.5 ROMs.

We still seem a long way away from this but if we could find the reason why some M2.5 ROMs are causing lockups, for sure we would accomplish quite a task :)
[Touch HD Windows Mobile ROM Development] chobanu:
Beg to differ. I had lockups on 23540 until i installed mnet's cab. Now i have been using the 23540 for more than a day and I didnt have a single lockup. If I dont report back anything else, than this was the solution for me.
[Touch HD Windows Mobile ROM Development] makbil:
chobanu, thanks for the input. Did the ROM you are using have some video drivers installed? mnet's cab just restores them to stock drivers, it doesn't change any system files as far as I know.
[Touch HD Windows Mobile ROM Development] makbil:
Yes, even though they are supposed to be the same, I suspect that there are some minute differences between HDs.
[Touch HD Windows Mobile ROM Development] makbil:
Quite a number of users are having lockup issues with the new OS versions. This is a sys problem and not related to the video drivers in any way.
[Touch HD Windows Mobile ROM Development] schurem:
My Blackstone has started crashing a lot lately. So i tried mnet's drivers. The thing just crashed again on me, and does not seem to wake up at all. Have i just bricked my very expensive little gadget?

I'm running:

RUU_Dutty_s_HD_WM6.5_R9_5.2.23016.5.3.0_1.59.709.0_Radio_52.62.25.34_1.14.25.24_Turbo_MSVC
[Touch HD Windows Mobile ROM Development] MJRL:
Try to run Task29 before you flash.

http://xdaforums.com/showthread.php?t=653604

Thats an old rom, there are better things around now.
[Touch HD Windows Mobile ROM Development] kieboy:
i have been experiencing massive lockups with Topix 3.5.9 then flashed to 3.5.10 and installed Neos latest driver cab, no lockups so far..been using for two weeks...phew!
[Touch HD Windows Mobile ROM Development] makbil:
You are running an older ROM which means the lockups are not related to the new sys versions. It's possible that something may have corrupted.

Same as MJRL, I suggest that you run Task 29 and flash again. You may also want to try first with your SD card out, just to eliminate the possibility that the lockup is caused by something in the SD card.

When things go drastically wrong, the best thing to do is to run task 29 and format the SD card as well.
[Touch HD Windows Mobile ROM Development] schurem:
Thanks for the replies. I have flashed first the stock rom, then a newer one. The phone seems to be OK now. thanks again 07
[Touch HD Windows Mobile ROM Development] mnet:
I have been having lockups after using the latest topaz drivers. So I did some testing and found something strange. If I put the device to standby with the manila home screen clock and weather animation visible (3 program icons mode), I get lockup. BUT if I hide the clock (9 program icons mode) and then put the device on standby, I don't get lockups!

You can try this if you are still having lockups.
[Touch HD Windows Mobile ROM Development] makbil:
I'll keep this in mind. Currently with G10's v4.01, I'm not experiencing any lockups but this is definitely worth trying. So does this imply the clock flip or the weather update animation as the culprit?
[Touch HD Windows Mobile ROM Development] mnet:
Probably. For example it could be that the 3d driver is not being activated when the device "wakes up" to perform mail retrieval, weather update, etc. So in that case the device locks up when manila tries to perform the weather animation (while the screen is off).

I have been lockup-free for weeks now after using this trick.
[Touch HD Windows Mobile ROM Development] dempie:
i have lock-up after lock-up..

have tried different roms, used task29.. done a hard reset.. flash stock rom... use different radio versions..

what to do? i get sick of it!

somebody please help! :(:confused:
[Touch HD Windows Mobile ROM Development] makbil:
I recommend flashing a stock ROM and testing for a few days. If you still have lockups it may be due to a hardware problem.

This should be a good starting point to troubleshoot the problem, if you have no lockups we'll take it from there.
[Touch HD Windows Mobile ROM Development] miniterror:
i have been thinking about the lockup

i havent heard it before so it might be something

most chefs(including me) do xip tuning

if you go out and google xip tuning

there is a file that has something to do with encription of memorycard

also many chefs(including me) have a tweak to disable memorycard slot

maybe it has something to do with those two factors

if the file is removed from the xip it misses something to read the memory card

if you turn of the screen with the tweak on it want to do something with the memory card

if it fails it could go into lockup

as everybody has different sd cards it might explain why some people have it and some people dont:-o

maybe it has nothing to do with the matter but it whas something that popped up my head so i thought it would share my thought
[Touch HD Windows Mobile ROM Development] dempie:
i have this problem on 3 HD's...

the only thing i do with these:

- HR -> stock rom -> HR -> custom rom -> HR

- install cookie home tab

- use an background from the sd card (maybe that's the problem as you said above)...?!
[Touch HD Windows Mobile ROM Development] core7x:
i also having this problem. what can i do is dont use htc sense and only titanium interface.

i also suspect with driverpack + htc messaging client ...

lockup during active sms [htc messaging client] + htc sense + driverpack
[Touch HD Windows Mobile ROM Development] dempie:
hmmzz.. i don't use HTC messaging... so for me isn't that the problem..
[Touch HD Windows Mobile ROM Development] kwbr:
Don't know if this has been discussed before but one possible cause is the ManilaDesktop.dll used in order to get hardware buttons working on hd. I use the same os base for my hd and hd2 and only hd, manila 2.5 roms seem to suffer from the lockups once in a while.
[Touch HD Windows Mobile ROM Development] ultimatepichu:
You mentioned 3 HDs and all having lock-ups after you did the same thing.

To verify the validity of miniterror's statement, can you check if all three of the sd-cards having the same brand, same class, and same size?
[Touch HD Windows Mobile ROM Development] kwbr:
It is certainly not caused by removing dll's from the xip in most cases. What dll would that be? At least I don't remove things (neither does miri if I am right). Like I said, I have a feeling replacing manila files/dll's is causing the lockup problems on HD. Manila version 2.5 was never released for HD so all fellow chefs need to mod that in order to get the hardware keys working. I have a strong feeling this is causing the problems.
[Touch HD Windows Mobile ROM Development] ultimatepichu:
Well, my knowledge of these things is limited compare to you all, but the only thing that I'm curious is that why lock-up only happens to some devices?

1. If it's manila issue, supposedly it affects everyone and all should get lock up but it didn't seem to be the case.

2. If it's the hardware difference as suggested by other people, unless our Blackstone is working at its threshold performance that causes lock-up, else I can't imagine how it affects the device. Besides, I was one of the victim of the lock-up but no longer one (finger crossed) so i exclude the possibility of HW as culprit.

3. I don't like to bring this up (again, and it's pointless) but it's also not about the graphic driver because not everyone facing it.

well, that's my summary of this issue.
[Touch HD Windows Mobile ROM Development] dempie:
hmmzz.. sometimes i use a rom without lock-up.. then when i use a newer version, i get lock-ups.. when i go back to the older rom (which doesn't have lock-up), i still get lock-ups on that rom... looks like some files are still on the phone after flashing..

and yes, all the 3 Blackstones have the same SD-card (which you get with your HD)

please, how can we solve the problem? every rom i flash now, have lock-ups... (i even tried task29, without succes)
[Touch HD Windows Mobile ROM Development] kwbr:
I also don't believe the lockups are caused by screendrivers. E.g. Neo did a fantastic job for HD owners.

I find replacing the manila dll's a bit tricky. One other thing that is discussed lately is the way files and modules are dumped from rom images. We all use the same tools dumping .dio images and the like. It is said the lockups can be caused by bad memory allocation which causes unpredictable errors. Strange thing is I never suffered the lockups on HD nor on my Elfin or HD2 while others seem to get an headache. Maybe it partly depends on the applications you run.
[Touch HD Windows Mobile ROM Development] Pfeffa-rah:
Ik had lockup issues once. They stopped when I stopped using the preinstalled Opera browser (version 9).

Every time I used it, my HD would lockup AFTER I quit Opera. Sometimes minutes after, sometimes hours after.

Really EVERY time I used it.

Since I stopped using Opera in NEVER locked up again...

Opera Mobile 10 Doesnot cause lockups and works great....

grtz,

Pfeffa-rah
[Touch HD Windows Mobile ROM Development] dempie:
hey.. here an enschedeër too :)

sounds great.. i'm sure i'm gonna try this too!

i'm getting sick of the lock-ups!

btw.. which cab did you use for this?!
[Touch HD Windows Mobile ROM Development] dempie:
hmmzz.. think this could be the/a reason for the lockups...

trying opera 10 now, till now no lock-up...

what do the cookers think?!
[Touch HD Windows Mobile ROM Development] _7_:
I hope you are right, because the way different members & chefs advise to flash is not really as simple as it was a couple months back.

Back then there was the "flash a stockrom first" discussion and now it's the task29, flash stockrom, 7 x hard reset, 50 push-ups while, flashing, cook a 20 pound lobster, soft reset, invite your girlfriend over and do task69, soft reset afterwards, etc. etc.

Maybe we can now go back to flashing 50 different roms in a row before ever doing a stockrom- or task69. Would be a nice right?

Greetz
[Touch HD Windows Mobile ROM Development] makbil:
Maybe this will help you somehow, Miri's ROMs are the only ones I've never had a lockup with - ever. Currently using G10's ROM and no lockup with that either but I haven't used is as long as Miri's ROMs.

I think we should also keep in mind that we are not faced with a single cause for lockups. In the earlier part of the thread, Neos drivers were shown to cause lockups (purely based on the fact that mnets program to remove those drivers fixed the problem for many users) but that also seems to be a specific case. I'm having lockups with most newer ROMs without any drivers and customizations, so this time the problem is somewhere else, possibly with the mods as you suggested.

As much as I still favor the HD over HD2, unfortunately it look like we have pretty much reached the limit for our HD, so from now my target will be to find a stable ROM with the least number of problems and stick with it - which will probably still involve flashing and testing new ROMs :) I'm not yet entirely convinced that I want to go WM7 way, so I should still be with my HD for some time.

Let's just remember that we are not looking for a single cause for the lockup problem (it would be excellent if it turned out that way) but try to identify and list those that are experienced by a significant number of users.
[Touch HD Windows Mobile ROM Development] miniterror:
i have loked at this

http://www.techparaiso.com/windows-...and-speed-up-your-windows-mobile-phone-device

they say to remove mencfil.dll wich is for storage card encryption

not quite sure what storge card encryption is

this midday i whas reading this and there is said it is caused by how the .dio file is dumped for the xip/sys

that can be found here http://xdaforums.com/showpost.php?p=6334196&postcount=27
[Touch HD Windows Mobile ROM Development] dempie:
ok.. this will solve the lock-up you think?!
[Touch HD Windows Mobile ROM Development] miniterror:
lol that of the .dio file might be the thing

as most of the time chefs downlaod sys/xip packages instead of .dio files(i have never used one)

if one person makes those packages and uplaod it here it will be used by alot of chefs:-o

so it could be treu
[Touch HD Windows Mobile ROM Development] dempie:
maybe you can :)
[Touch HD Windows Mobile ROM Development] Menjic:
I notice a little different things so here you go maybe some can put together all we notice and tel us all what is the real problem and how to fix it.

I have Touch HD but symptoms are same on all HTC SOD devices

I did folowing

1. Task29 - RUU that wipes all remaining data after this you stuck on smart mobility screen - device can not power up, and nothing else is displayed, just splash screen no rom version no radio version just splash it can stay for days on that

2. flashed custom rom, TOPIX

3. hard reset, hard reset, hard reset .....

4. set up device time and stuf, synced my contacts and did not installed anything

Device work without sod for day maybe.

Then when I change manila tabs order -> SOD

When I charge and unplug USB - > SOD

When I talk to someone, and recieve SMS and and pres power too fast like power on power of and power on again in 3 sec -> SOD

When I charge on PC USB screen dims not power of just dim, and Top LED is stuck on green if battery was 100% or orange if it was below 100% -> SOD

If I have SOD for any reason, it does not help to just reset device, to bring it on again I have to take out battery for at least 5-6 times.

But if I just push reset button and wait device would eventually power on after 10 min seating dead - noting happens, then I feel vibration but screen is black again, device works, people can call me.

Until I pull battery out and put back few times 5-6 times and then it is normal until next SOD.

Then device works without SOD for day or two depends on what I am doing with it :)

NOW I CAN NOT CHANGE SIM ! Here in Bosnia and Herzegovina we have 3 network providers but only 2 cover whole country but it is expensive to use other network when all people that I communicate with use one network

I could try copy my sim to blank new one, or request from network to give me new SIM with my old number.

Settings GSM-AUTO did not make any difference for me.

one time when I turn OFF manila and leave just winmo menu without anything on home screen - empty just status bar, I received inproc or whatever is called ERROR, which is said that have something whit connectors between motherboard and other tings in phone, so I disassembled it all the way clean connectors and everything with alcohol and reassembled it and ERROR did disappeared but SOD stays.

radio rom did not make difference.

I notice that SOD's are less frequent when battery is more than 50% charged, but this maybe just in my head

my WIFI is allways OFF, I do not use 3G, MMS or any kind of internet activity over mobile network - because it is too expensive on my network. I would use WIFI but I managet to cut my WIFI antenna cable when I disassembled my blackstone, so until I catch some time to change the cable I am without WIFI wich is maybe good thing to troubleshoot SOD :)

I think that SODS is less frequent when I increase time for standby and time for run something while in standby in Advanced config.

Huh I think that is all from me, if I remember something I will post it.

Thanks in advance for any help.

And sorry on bad English.
[Touch HD Windows Mobile ROM Development] Menjic:
One more interesting thing!!!

I did not read anywhere this, when I expirience SOD and constantly pressing power then home than power again, repeat that three steps few times, screen comes on and I have up side down picture of everything but not touch just lcd.

If anybody understand me. Touch reacts as normal orientation but lcd displays up side down picture - manila tabs are up but when I swipe finger down they react in reverse if I swipe to right tabs going left :)

Then I again press power button to go to standby and again to wake device and then it is normal everything works.

I repeated this 4 times.

This would mean that SOD is caused by graphics driver ???

Is anybody reading this ???

=============================================================

Device is Touch HD T8282 from Orange, bought in London if it means something.

Kwbr_Topix_3.6_Sense2.5_WM6.5_no_htcMsg

OS Version : 5.2.21901 (21901.5.0.92)

Manila version : 2.5.20121225.0

ROM version : kwbr topix 3.6 WWE

ROM date : 04/08/10

Radio version : 1.17.25.09

Protocol version : 52.69.25.37U
[Touch HD Windows Mobile ROM Development] TRNSLN:
OMG it looks like a horror film... "Light of screen gets on in the dark...." :):):):D
[Touch HD Windows Mobile ROM Development] Menjic:
:D:D:D Just it is not film it is so real and annoying thing.

But now maybe solved :) read this
[Touch HD Windows Mobile ROM Development] makbil:
I've never had the upside down screen, just unresponsive.

At least for me, yes it was the screen drivers. Using kwbr's latest ROM I don't get these lockups anymore.
[Touch HD Windows Mobile ROM Development] Simon_WM:
Sorry but whats ?

SOD ?
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
I believe he means the dreaded "Screen of Death". Depending on scenario it could be black SOD or green SOD. Google it or search XDA for it
[Touch HD Windows Mobile ROM Development] Simon_WM:
Owww, so its like BSod, for windows ?
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Indeed, Black Screen of Death
[Touch HD Windows Mobile ROM Development] makbil:
Hey Fallen, how are you doing?

Now I have been having an affair with an HTC Desire HD and almost forgot about this thread. I still have my HD and been using kwbr's ROM on it with WinMoSpeed giving it a little push. Haven't had a single SOD with that ROM.

I need to catch up with what happened here, then maybe I should edit the OP, perhaps put a safe configuration there so people can test their devices to see if they still have this problem.

Nice to see you holding the flag :D
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
I too have moved on to the Desire Z but I always pop in here most days to check out and help when I can

I'm still a winmo geek at heart, hence why I also got a HD7 lol
[Touch HD Windows Mobile ROM Development] makbil:
You have described the exact condition that occurs with the lockup I'm investigating.