yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] jacox123:
I have been using both the Topaz drivers as well as the Mikenificent drivers. Both promised to work fine but after a day or two they started to lock up mij HD Touch. It now happens 3 -4 times a day. I will go back to a WM6.5 with sense 2.1 as this should not give these problems.

I don't know why the lockups increase over time. I use my HD as telephone, agenda (using active sync to sync with Google Agenda), email and for navigation using iGo with HyperGPS for TMC, al on a daily basis. Can this also be reason for the lockups?

I really like Sense 2.5 interface and would like to use it but when my HD becomes unreliable using it, I may need to go back to 2.1......

Hope you can use this feedback.
[Touch HD Windows Mobile ROM Development] golightlygl:
Just to be clear - these drivers are very low level and I don't think they should be installed and uninstalled like apps. To test properly I would suggest flashing a non-driver ROM (eg Xanny 2.5) and run for a few days. Then install one or other of the drivers (I'm using Mikenificent without problems) for a fee days.

If you want to try a differemt driver I would recommend flashing back to new ROM state before installing.
[Touch HD Windows Mobile ROM Development] makbil:
It's also not a good idea at the moment to install more than 1 driver.

One development is that Neos2007 has confirmed in this post a report by another user that if you manually lock your HD using WM lock, the lockup doesn't occur. This may be significant, pending some more confirmation by users troubled with the lockup problem..
[Touch HD Windows Mobile ROM Development] f.cervera:
HD LOCKUP

Hi all :

I'm experiencing a sort of lockup that I'm not sure It has to do whit this thread :

It always happens when charging and the HD is switched off. After few hours the small led on the power button gets stuck on green light, and there is no way of wake-up the device.

Only removing the battery will work.

This happens whit MIRI 18, last Xannitech, Flashmore and last MIRI beta...

I had to step back to MIRI 15, which is running fast and 100 % stable, never had any issue.

Anyone else having this ??
[Touch HD Windows Mobile ROM Development] vita56:
+1

I have exactly the same issue. This happens with MIRI 18, Xannytech 2.4 and 2.5. :-(
[Touch HD Windows Mobile ROM Development] makbil:
This did happen to me a few times but I doubt it is a driver issue as the phone is off to begin with.
[Touch HD Windows Mobile ROM Development] cduijker:
i think he means the phone is in standby and not fully turned off...
[Touch HD Windows Mobile ROM Development] f.cervera:
No cduijker, makbil is right.

It happens only when the phone is fully turned off, so drivers are not concerned.
[Touch HD Windows Mobile ROM Development] vita56:
It happens when the phone is suspend, not fully turned off, in my case.
[Touch HD Windows Mobile ROM Development] makbil:
Getting a lockup when the phone is fully turned off and when it is in suspend mode are two different issues. The first case may be a battery issue or a hw issue or a bad flash issue, hard to tell. It never really bothered me, I can handle one lockup while turning the phone on as long as I don't get them during use :)
[Touch HD Windows Mobile ROM Development] f.cervera:
Your discourse does make sense, I'm with you makbil.

I think I should flash MIRI R 18 again, perhaps I've got a bad flash...

I'll post how It goes.
[Touch HD Windows Mobile ROM Development] makbil:
Just to be on the safe side, flash a stock ROM first.
[Touch HD Windows Mobile ROM Development] thinkpader:
no problem on stock rom

Hey everyone,

thanks Makbil for this thread,

i used to experience differents issues on the different roms, the most annoying is the restart of the device with cooked roms. i just reverted to the latest stock rom and everything is really fine,

no more restarts

battery is getting more power, i know that this have to do something with the build and the version of the manilla, but it's better than with 6,1 winmo and Sense on cooked roms.

i didn't install Ndrive, on the stock rom, and i don't know if this had any conflict on the others roms as it was always executing install just after the install of the rom, but with the stock rom, the programe didn't execute the auto-install script.

i miss the miri roms, it's just two days, but the stability and autonomy of battery is of big help for productivity.

i hope this feedback could help somehow as all your post;

thanks a lot.
[Touch HD Windows Mobile ROM Development] makbil:
thinkpader, Ndrive should not cause this. If you decide to flash a custom ROM again, I suggest you also format your SD card first (FAT32), just to make sure the problem is not related to the card.

I've tested the latest ROMs by Miri and Xanny and they both work without issues on my HD. Any WM 6.5/Manila 2.5 ROM will be a bit slower and will use more battery than a ROM with WM6.1/M2.1 but I think it's worth it.
[Touch HD Windows Mobile ROM Development] NiGhTTraX:
Booya !

I've been having the lockup issue ever since I upgraded to WM 6.5 with the Holy Grail R0. I've tried the fix on this thread a while ago and never had the issue again. So thank you so much guys for making it possible. I hope everyone who has the issue finds this thread and applies the fix. No more freezing when you're in a meeting and have to check an email. No more freezing when you put an alarm to wake you for an even more important meeting and you end up running half-dressed through the house to find your keys. I can finally enjoy WM 6.5 on my HD now. Thanks again !
[Touch HD Windows Mobile ROM Development] HenkV:
Still a lockup with Mikeficent drivers

I'm using the nice and easy Laurentius26 HDLEOV4 Ultimate serie

Removed the Neo drivers and used Mikeficent drives.

Stil I get a lockup every few day''s

So fro me it seems not the solution, any idea's ?
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Personally I use the chainfire drivers which a number of people have reported no lockups with. Maybe give them a try ;)
[Touch HD Windows Mobile ROM Development] makbil:
How did you remove the Neos drivers?
[Touch HD Windows Mobile ROM Development] HenkV:
Still Lockup with Mikeficent drivers

First I loaded a stock rom then the Laurentius26 HDLEOV4

Did a hard reset, all to factory defaults.

I removed the Neos drivers with the cab from mnet and loaded the Mikeficent drivers.

I will try the chainfire drivers , let you know what is happening.

Hope this will work cause I'm pretty happy with Laurantius.
[Touch HD Windows Mobile ROM Development] makbil:
Looks like you did everything right. It's strange because I did not have any lockups with Mikenificent Drivers.
[Touch HD Windows Mobile ROM Development] golightlygl:
TouchLockPro is now giving a problem

Having been lockup free since removing neos drivers (and also since installing Mikenificent's drivers) I recently installed Touch Lock Pro 2.11 and lo and behold my lockups began again (exactly the same type as per Post 1)

I have uninstalled and they have gone.

Since TLP doesn't even use any 3D effects, I can only assume that both Neo's drivers and TLP access some register somewhere (or high memory location) that is casuing the problem.

I will post this to the TLP thread to see if there's any assistance forthcoming. But those few of you still expererincing lockups, are you using TLP? And is anyone using TLP who is lockup-free?

I really thought this issue was behind me. I'm still on Xanny's 2.4b but might try flashing 1.9 and see if that makes any difference.
[Touch HD Windows Mobile ROM Development] mnet:
You guys should try the new topaz manila 2.5.20113030

I think it solves the lockup issues
[Touch HD Windows Mobile ROM Development] 574ND410N3:
indeed that could be a solution

since i flashed a new rom with new manila, no lockups for 2 days ( and counting :) )
[Touch HD Windows Mobile ROM Development] MJRL:
I've already posted here, i didn't have any lockup for a long time, but today when i press the power button my phone was stuck in grey/dark screen. Then after take the battery out my phone crash after received a call...

Since then its ok, i couldnt find any thing to cause it, i didn't did anything diferent from usual...
[Touch HD Windows Mobile ROM Development] malson:
..

The best solution for this problem is to claim the repair of equipment. I have a new motherboard and display. No problems since then I have.
[Touch HD Windows Mobile ROM Development] MJRL:
My phone only have standard rom for a few hours, and sometimes when i flash a new rom, i flash standard rom, so i don't know if that appens with standard rom.

And its more dificult in my case, this thing only appens 3 or 4 times, if i send it to repair even with default rom, i bet they don't do anything and send me the same hardware again, cause they can replicate it, only with very luck this could happen when the phone it's in repair.
[Touch HD Windows Mobile ROM Development] malson:
Intervals problems were always shorter and shorter on different ROM. I use USPL. I did flash the original ROM and sent for repair. Since then I have repaired the phone. Was replaced motherboard and display. Then I have no problems with the phone. And improved battery life.
[Touch HD Windows Mobile ROM Development] makbil:
You should be aware that you may run into problems with the warranty if you send in the device with a custom ROM on it :)

This specific problem never happens on a stock ROM, so if you are having lockups while on stock ROM, then you should definitely send in for repairs, otherwise it may just be a waste of time and most likely you will get the same device back, untouched.
[Touch HD Windows Mobile ROM Development] d190176:
i'm tired from lockups. tried many roms - problem still with me. the only thing installed myself - htc EzInput.

occurs when phone rings, or power button pressed. once had an endless vibration when locked. can be once in a week or 5 times in a day.

the one thing i noticed - it happens if phone stays for a long time untouched. 50\50 that it will not wake up if left for a night uncharged.

sorry for english. not my favorite.
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Have you tried changing drivers? You can find them on first post in this thread
[Touch HD Windows Mobile ROM Development] d190176:
no. i did not. i read a lot about this. i see that people have this trouble, or have not. with same roms. xanny's, fo example. looks like hardware problem. i heard that installing stock rom or formatting solve problem sometimes. i'll try today. if i drunk enough. otherwise, i'll smash my htc to the wall and purchase iphone. that will be a shame.
[Touch HD Windows Mobile ROM Development] makbil:
I'm currently beta testing Miri's WM 6.5.x with Manila 2011 and had a lockup just this evening. If it happens again, I think it will need to be investigated deeper. Being beta software, I'm not too concerned at the moment as I've been lockup free since we found the solution.
[Touch HD Windows Mobile ROM Development] 574ND410N3:
Hmm.. i thought the new Manila 2011 would solve the problem..

on Miri's Roms i ever had lockups.. so i tested an other custom Rom

Energy BLACKSTONE WM 6.5.x 23529 with Manila 2011

since i flashed this rom.. never had lockups for a week

so what could be the difference... is Miri doing some mistake in cooking Roms..

or Energy Roms do know something that others dont know :P
[Touch HD Windows Mobile ROM Development] makbil:
I don't think it's fair to say that. First of all, this is beta software, second I didn't have any further lockups.

However, I'm still keeping an eye on these new versions. Following Xanny's thread, a number of people seem to be having this issue with these versions. It's hard to come to a conclusion in such an uncontrolled environment, you never know what people are doing with or installing on their phones.
[Touch HD Windows Mobile ROM Development] 574ND410N3:
sry.. i didnt meant it that bad.. i respect their work and time effort

i tried many things to deinstall to fix the lockup problem

and tried many things to install to get into the lockup issue... but with no success

what i want to say that its maybe cook-related problem... but maybe not

its hard to define the problem bcuz im not a cooker.. and its better if I dont shout it out loud like a moron :) ... it is just an idea

grz*
[Touch HD Windows Mobile ROM Development] Artpro:
My HTC had the same problem with all ROM's (inclusive with original one). When i turn off the phone with top button or let him go to sleep and trying to switch on again, no response and the only thing i can do to make him wake up was soft reset or remove the battery.

Well.. now are 24 hours without lockup (before, no 5 minutes without lockup).

What i did was simple. I remove the battery for almost 48 hours and i deactivate from HD Tweak "Power Saving" (i am not so sure this was the reason of repair).

I use Cloudy 1.3 ROM, but before remove the battery for almost 48 hours i had lockup with this ROM too (i used all latest ROM's from the xda including the original one from Orange website).

For now i am happy.
[Touch HD Windows Mobile ROM Development] xyz69:
I have experienced such problem (Chinese Rom) in this way:

After updating the wm6.1 to 6.5 (Devilstone Rom), firstly I started having an unstable HD phone, e.g. slower/system hanged while sending SMS/using opera, even failed sending Sms, etc.

Till one day, my phone started showing an error message that keep asking me to turn off/reset my phone. Not only this msg is annoying, but also it drains out the battery rapidly.

Just before giving up my Backstone to iPhone, I just give a try as last chance for updating to another Chinese Rom called "Zoey Rom". In the 1st few weeks, my comment is really "wow". No matter the speed of system, switching apps/sending mails/sms are all amazing.

The only problem is that the power button on top of my phone started not working then. That means I cannot turn on/off my phone by pressing this button anymore. Fortunately, I have managed to pull out the stylus instead of take out the battery each time in waking up the screen.

So far, the battery still drains quickly. I hope my experience can help some of u in finding the solution.
[Touch HD Windows Mobile ROM Development] makbil:
xyz69, before flashing a custom ROM, did you flash a stock ROM first or use MTTY to format the flash memory (NVRAM)? This is a recommended procedure to get rid of any corrupt memory locations which may cause problems. You should also do one hard reset after flashing.

There are also a few WM sys versions that are known to cause lockups, try to stay away from them :)
[Touch HD Windows Mobile ROM Development] xyz69:
Thanks Makbil for your advice. Although I did not flash my phone with a stock ROM, I did hard reset twice after flashing a Zoey ROM.

As I am a not an IT expert at all, would be grateful if you can send me the link/thread/file so that I can get a better understanding on these steps in flasing a stock ROM.

100 million thanks & will get back to you later for the outcome.
[Touch HD Windows Mobile ROM Development] chobanu:
I had good success with Lost in Asia 28014 rom - run it for a few months without a single lockup. Now for the past few days, I am playing with new roms - 23540 and manila 2.5.012 - so far i tried 3 roms and all resulted in lockups followed by hard resets and on one occasion it didnt even want to fiinish booting from hard reset - had to recover it from bootloader. I think manila is to blame here and I uninstalled the video drivers - hope it will sort it out, if not, I am going back to 28014 and wait until 235 branch will mature more.
[Touch HD Windows Mobile ROM Development] makbil:
Sorry for the delay.

Here is the link for the flashing tutorial.
[Touch HD Windows Mobile ROM Development] makbil:
This is definitely a WM sys issue. I've been using sys 23541 for a few days now and no lockups. Try to avoid ROMs with 23540 and 23534.
[Touch HD Windows Mobile ROM Development] MJRL:
Why some people have lock ups and others don't?

Why people have lockups with 23529?

Why people have lockups with older sys?

I've had lockups with old L26 roms, and do everything by the book, install original rom, softreset, install coocked rom soft reset, even try for a few days without install anything.

And why some people have ringtones problems and others don't, even after a fresh install?

In my opinion some blackstones with some combination sys/rom corrupt the rom and origin the lockups, its like some hardware that corrupt the OS even without oc, i remember a lot of motherboards with some chipset corrupt the OS, and the ram and hdd where ok.

:D
[Touch HD Windows Mobile ROM Development] makbil:
This is not the same behavior I get, never had the screen misalignment and the device does not wake up, just the screen lights up slightly but you can't see anything.

I suggest you try MS My Phone instead of PIM backup, see if that makes a difference.
[Touch HD Windows Mobile ROM Development] bodgeman:
I flashed from PC. This ROM is great and the only problem i encountered was the lock-up. Fingers crossed, it has been cured. (I know as i'm writing this I'll go and pickup my HD and it wont come on!;))

i'll let you know if it stays cured.
[Touch HD Windows Mobile ROM Development] miancule:
I can confirm this.

It happens to me with every WM 6.5/Manila 2.5 ROMs I flashed - the frequency, though, varies - it can happen in the first 2 hours after flashing or in 2 days, but it still happens.

It happened even when flashing a stock ROM (hard reset, etc) before flashing the WM 6.5/Manila 2.5 ROM (hard reset, etc).

It never happened with WM 6.5/Manila 2.1 - so I assume it has something to do with Manila 2.5.
[Touch HD Windows Mobile ROM Development] Marne Jr:
Hi everyone !!!

I am very exciting about this post cause it will help us to stay more close to the cause of lockups and to find some "cure" ...

It´s great to see that lockups is a thing that can happen with anyone and that we are not "alone" and that it could be not a thing that make us going to sell our blackstones ...

At the start of the post I could see a really nice definition of lockups and a clear difference from freeze ...

But it could be more detailistic and I think that we could have to have sub posts ...

Some people just have specific lockups with specifics manilas or roms... and we could call it Type "a" lockup ... others (including me) have a hard lockup that occur even with stock rom (type "b") ... I have no doubt that this type ("b") has a strong hardware component since I got my HD on march and after two big drops to the floor in august lockups starts and had never got any until that date and it has never stopped to hapend since that month (august) no matter what I do ... I readed on service manual of HD that main board damage and instability on amperage of eletronic components can be the cause ...

My lockups with stock rom usually happens 3 times a week (so so) ... but after I started flash rom it become harder going to 4 times a day and become more dificult to scape from then ... and now I think I am having type "a" PULS "b" lockups ... Since 3 week a go I`ve been got so hard lockups that can last for about 3 hours that even hard reset could not bring it back ... than I putted it to refrigerator (5º celcius) for 15 minutes and it turned back (i don´t recomend it ... but I was so frustrated that this what I did...) From there ... I discovered that many steps can stop lockups on my situation and now I got 3 days without lockups... I can list 10 things and a big one that stops fully lockups type b ... I will flash ROM 6.5 with manilla 2.5 to see if it prevents lockups type "a" too ...

But at this point I ask for rewrite the start post putting the differences of type "a" and type "b" lockups, cause they are different in cause and treatment (I think I write like this cause I am a doctor and now HD is my patient...).

Hope we can help each other and stay with HD !!!

Bye.
[Touch HD Windows Mobile ROM Development] makbil:
My intention was to investigate what you call type a lockups, so for the time being I'd like to keep it confined to that specific case. Other lockups or type b as you call them, can have various reasons unrelated to the first case.

By all means, please list the steps you take to prevent type b lockups, I'm sure it will be of help to some users.
[Touch HD Windows Mobile ROM Development] Marne Jr:
Ok, but is very difficult to me to list what is useful for type "a" or type "b", since I am having both ...

I have to start from type "b" cause when having hard lockups I flashed stock rom with 3 hard resets before and 3 hard resets after and then I didn´t installed anyhing to think that If any lockups appear it would be type"b" ...

I will be on this way until I got NO more lockup and this steps will be a kind of lockup cure... than I will flash roms + radio + third party softwares and then If any lockups occurs it will be type "a" ...

For type "b" I did this steps below and seems I will not have lockups anymore (use original SPL and stock ROM and Radio):

1)Disable auto ajust backlight

2)Disable turn off back light if inactive for: (seconds)

3)Disable turn off device if inative for: (minutes)

4)Disable auto lock device (I did it with twak app 0,54)

5)The most important: I NEVER PRESS POWER BUTTOM TO MAKE DEVICE SLEEP UNLESS I HAVE LOCKED IT WITH LONG END KEY PUSH ...

After all of this My device never sleeps spontaneously and I have no more lockup ...

Since august it is the first time I can pass 3 days without a lockup ... but I will wait more 3 days to state that type "b" lockups cure is this ...

Before that I was just locking my device with long end key push and letting the backlight turned on but it increased 12%\day on battery drain...

Maybe someone could make a .cab (push button) to put on quicklinks that can make backlight goes from custom levels like level 1 to 5 on just one push ... Example: 5 in use and after push goes to 1 to not use and then one push and got 5 again... and it could looks like the light button to turn on and off light in a room....

After I will try the other many things that I know increase chance of have a lockup to see what we can do about type "a" lockup ...

I don´t know but I think this kind of type "b" lockup is rare since I just know me and few others to have it !!!

Bye.
[Touch HD Windows Mobile ROM Development] Marne Jr:
Hi,

I did not understood ... You said "it happened even when flashing a stock ROM" ... then you said "it never happened with manila 2.1" ... but why you concluded it`s a manila 2.5 issue if it happens with your stock ROM ? Is your stock ROM on manila 2.5 ?
[Touch HD Windows Mobile ROM Development] makbil:
I think he meant flashing a stock ROM before a custom ROM.
[Touch HD Windows Mobile ROM Development] miancule:
That's exactly what I meant, thanks :).
[Touch HD Windows Mobile ROM Development] kartalgurhan:
makbil:

I get EXACTLY the same problem you described in the 1st post. My favorite ROM is Xannytech GridEvo 1.6B and I always come back to it after trying newly released ROMs every once in a while and I ALWAYS get this lockup issue.

However, if I first flash Dutty's 6.5 Leo R7 once and do 2 hard resets and then flash Xannytech Evo 1.6b, followed by 2 hard resets...and no more lockup issue!

I don't know why this works but it does!

-I confirm that I use exactly the same SW group and same mail settings..etc.

-I always use my pc to flash

-I recover my configuration using SASHIMI and "PIM Backup" for contacts and calendar

best wishes, kolay gelsin.