yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] mh297:
I've only ever had this issue with kwbr's TOPIX 3.0.2 a wm6.1 Sense 2.1 firmware. Used other firmwares (wm6.5.x with Manilla/Sense 2.1/2.5) without issue since but returned to TOPIX 3.0.2 as I like its speed and functionality. The lockups are back on a 48 hourly basis.
[Touch HD Windows Mobile ROM Development] bodgeman:
My serial number is: HT949KD00370

Part number: 99HHC014-00

Unknown if locked or not
[Touch HD Windows Mobile ROM Development] makbil:
Looks like it is the bold part that changes, may designate the intended market though...

Part number: 99HHC013-00

I got mine online from the USA but on the box it lists European countries, so probably it originated in Europe.
[Touch HD Windows Mobile ROM Development] Oemie:
I first experienced it with the Xannytech rom 1.6 but only after 5 to 6 days of use. Then it started to happen, so i switched to two PDAviet roms that have the latest Manila Manila 2_5_19211622_1 (New Leo 1.49).

These roms are the only ones that have 22_1 @ the end. One of these roms had it, the other one i didn't try anymore cause i firstly blamed latest manila.

Most cookes here use Manila 2.5 19211619.

It is to bad because except for the useless icons that are in the Telstra Manila, the Manila is more nice (eyecandylike) and zoom function is back in the camera!

Again i will see what nrg rom does, till now 20 hours of use everything is oké..:rolleyes:
[Touch HD Windows Mobile ROM Development] Marne Jr:
Ok, you are probably all right !!!

And I realise that I might got a different kind of lockup than yours ...

What I really know is that I would can not help else with this post for a while because I don't have more lockups ... since August having it 3 or 4 times a day... I did Mtty and then returned to official rom ... Even that I had one soft lockup... than I readed somewhere in this forum that if you lock your device with long end key push before press power button to make device sleep you should have no more lockups (since you disable automatic sleep) ... and then I did it .. and 5 days with official rom and now 24 hours with 21885 V15 (manila 2.5) of Miri rom and no lockups at all ...

Thank all the support and help ... hope everyone can find some "cure" for each lockup ...
[Touch HD Windows Mobile ROM Development] golightlygl:
OK I turned off all notifications and sounds and still suffered a lockup overnight (although interstingly it didn't seem to leave the screen backlight on). So I guess we can rule out sound.

I assume everyone suffers a lockup overnight with the phone unused for several hours (if you plug it in to charge and have it set to never turn off on power, be sure to turn off the screen with the power switch to be sure of a golld ol' lockup).

If that's the case, can I ask everyone to just confirm that data reception is the key locking event. Please turn off wireless and use NoData to disable GPRS and 3G access. Then leave your phone in suspend mode overnight. If I'm right, then your phones will all be fine in the morning. Please report back here so we can at least focus our efforts some more.

In the meantime, I am posting on Xanny's forum to see if what the part numbers are for those not suffering the lockups (Incidentally, mine is 99HHC046-00)
[Touch HD Windows Mobile ROM Development] vjeta:
"Please turn off wireless and use NoData to disable GPRS and 3G access. Then leave your phone in suspend mode overnight. If I'm right, then your phones will all be fine in the morning. "

I think you are right!

I've this lock ups during the day using data connection, push mail,... but NEVER at nights, while I've all wireless connections turned off always.
[Touch HD Windows Mobile ROM Development] chinhe:
Hope this Post by MikeChannon helps :)
[Touch HD Windows Mobile ROM Development] fuithecat:
using windows default Today

Great thread.

I had lock ups ever since flashing roms, using Xanny's rom since 1.9 and currently 2.3.1B, all had lockups. Always happens during device idling. At least once everyday and up to 3 times and had to take out the battery. I did a flash of the stock ROM before flashing Xanny's rom (Chinese ROM) and still had lockups.

My touch hd is from Hong Kong.

I saw someone suggested that to try the default windows Today instead of Sense 2.5, so I gave it a try yesterday, so far its been around one day and no lock ups so far. This together with the fact that I never had lock ups using stock Chinese roms, perhaps indicates that this is not a hardware problem, but a sense 2.5 problem.
[Touch HD Windows Mobile ROM Development] chinhe:
for me its true, even on hermes flashing days it Happened, they call it sleep of death.. the rom is being overloaded that sometimes the processor cant process too many applications so it hangs even on standby mode, remembering that almost 99,9% of applications we have cooked in our HD now is ported from other devices that has different OEMDrivers for their specific HArdwares.. or maybe its due to the usage of the phone..
[Touch HD Windows Mobile ROM Development] jtf420:
nice reccomendation! thnx

just flashed to XT1.7 ..will wait for lockup and then try the ActiveSync trick!

can we make a list of programms that use or invoke Active Sync!

mail app

push mail

pc sync

time sync

wht else!
[Touch HD Windows Mobile ROM Development] Oemie:
You are right, it is definitely not a hardware problem. Mybe hardware romrelated but not just HW.

I am on latest NRG rom and i haven't had any lockups.. Also not overnight, for 48 hours no lockups.

But i will continue testing till tomorrow and then i am going to switch to latest Xanny rom 1.7..this because i can't coop with my addiction anymore :D
[Touch HD Windows Mobile ROM Development] bodgeman:
Just to confirm I also ran windows default for 36hrs with no lockups - switched back to Sense 2.5 and have had three in a 6-7 hours. I agree with fuithecat looks that the problem definitely lies in Sense 2.5 and not in hardware. All this on Xanny's 1.6b.
[Touch HD Windows Mobile ROM Development] makbil:
Not a hardware malfunction but perhaps a difference in board revision. Otherwise how can we explain that some people never have any lockups? It could be as simple as using different manufacturer's components in different HDs, hence one brand works but the other brand does not. I wish we had more info on this.

From previous posts it's almost confirmed that M2.5 is to blame, which is in line with my observation. But what exactly in M2.5? As I posted before, using same WM and Manila versions, I have consistent lockups in one ROM and no lockups in the other. The visual difference is the size of the ROM, the smaller size works without a problem.

Using the information we have from the posts above, I'm inclined to think that we should also be looking at M2.5 components dealing with communication and activesync.
[Touch HD Windows Mobile ROM Development] makbil:
Very interesting find. Although the post by mikechannon is about 3 years old and activesync is part of WM not M2.5. As users have reported, the lockup seems to disappear when not running M2.5, so I think it is unlikely this will be a solution to our problem.
[Touch HD Windows Mobile ROM Development] matt.d.reid:
Blackstone lockup/freeze issues

Hi all,

What a great thread….

Apologies if my thread is out of synch (pardon the pun) with the other posts on this topic…

I am experiencing the Blackstone freeze/lockup issue as well and whist I am experiencing similar characteristic issues to others have described I have other problems associated with my freeze/lockup issue.

My problem started about early Nov with the screen becoming non responsive and freezing. At first I thought the phone was dead as I noticed the top light was off as well. The problem was generally solved with a soft reset or battery removal etc. I was not too concerned as I was about to travel for 6 weeks and the phone would be buried in my bag for the duration of the trip. Then I started to use my phone to listen to music on the plane and it would take several attempts to get it to boot up and often it would be that the phone would start up but the screen would be blank. Eventually it would wake up with the power button pressed several times. This has considerably got worse with the freeze occurring constantly and it cannot be woken up. It does ring if the phone is called but cannot be answered. Occasionally a reminder in the calendar will wake the screen up but before you know it, it goes to sleep. It will not activate when plugged into the PC and active synch cannot detect its presence so I can’t even do a ROM update….Nor can I put the phone into boot mode or do a hard reset…

I am totally out of ideas, so any suggestions would be greatly appreciated as I am almost at the point of throwing it out the window and getting on eBay and buying a new Leo or heaven forbid – get an iphone…

My Blackstone was bought in the UK so I assume it’s a Euro build and the current ROM is Dutty’s Leo R11 and I was not using HTC Sense and home screen was set to the Windows default.

Last I must mention that the home screen was also showing an error box displaying something like ‘Microcorp error please update firmware’

I hope someone out there can assist!

Matt
[Touch HD Windows Mobile ROM Development] Oemie:
So at this time i have my touch running for more then 48 hours and not a single lockup, Really nothing strange or buggy happens. I dim the light manually or by power button. I have my phone running all night and nothing happens so i am not sure what i can do more..i leave the rom on for another 24 hours and then i will go to Xanny rom 1,7 and see what happens
[Touch HD Windows Mobile ROM Development] makbil:
I suggest that you flash a stock ROM and test for a while, if the problems disappear then you can flash your favorite ROM again. If you are still having these problems with a stock ROM, unfortunately your HD may have a hw problem.

You can find the stock ROMs here. V 1.56 is WWE version.
[Touch HD Windows Mobile ROM Development] MJRL:
I didn't had anymore lockups with xany 1.6b, only a few hours after flash.

If you guys are pointing to M2.5 disable it in today and test, but i also had lockups with manila 2.1 in the past.

My device

S/N: HT849KD09385

P/N: 99HHC018-00 B

Bought in Portugal locked to TMN and unlocked by HTC Code
[Touch HD Windows Mobile ROM Development] matt.d.reid:
Hi Makbil

Yeah that was the intent to flash a stock ROM and give that a go but seeing activesynch can't detect the phone I can't flash it....Is there another way to flash?

matt
[Touch HD Windows Mobile ROM Development] MJRL:
Search for flash sd card metod
[Touch HD Windows Mobile ROM Development] matt.d.reid:
Cheers but seeing I can't see the screen I have no idea if I have it in bootloader mode just as I can't preform a hardreset...
[Touch HD Windows Mobile ROM Development] ClydeB1:
I'm luckily not suffering from these afflictions, my P/N (for what it's worth) is 99HHC0

10

-00. Hopefully it helps in some small way.
[Touch HD Windows Mobile ROM Development] ClydeB1:
But I've used Sense 2.5 since it came out and I use all of Xanny's Sense 2.5 roms and never 1 lockup, so I can't see how it can definitely be Sense and not hardware. Perhaps it lies in a combination or with apps. There has to be a common factor somewhere.
[Touch HD Windows Mobile ROM Development] golightlygl:
Thanks ClydeB1. We know that many of you are not suffering the same problems and this is what makes finding the cause so frustrating. Some people seem to think it might be related to faulty NAND chips in a region that's only accessed by Sense 2.5 but I (personally) think this unlikely.

I'm honing it down to an issue with data reception whilst the unit is in sleep mode. At least if we can narow down apparent "random" freezes to a reproducable, specific set of circumstances then maybe cleverer folk than I can try and figure out what's causing it.
[Touch HD Windows Mobile ROM Development] ClydeB1:
@golightlygl, no problem, good luck in the quest for the proverbial needle in the haystack. For what it's worth, I always set up data to disconnect after 15 sec using HD Tweak. If you think it is related to data perhaps you want to play with that option.
[Touch HD Windows Mobile ROM Development] makbil:
You can flash from the SD card, if your SD card works (Transcend doesn't work). Here is a good guide.

If you are having screen problems even in bootloader mode, most likely there is a hardware problem with your HD.
[Touch HD Windows Mobile ROM Development] makbil:
Perhaps the correct (non technical) definition is:

Some HDs are more sensitive to some M2.5 ROMs ;)
[Touch HD Windows Mobile ROM Development] Marne Jr:
Have you used MTTY before going from windows default to Xanny 1.6 ?

I would recommend it to you ...
[Touch HD Windows Mobile ROM Development] Marne Jr:
Ok man you are the one I think I can help, cause your problem seems to be exactly like mine (including the Microp error that I solved using USPL instead HSPL) ... I think you have type "b" lockups (if we can call this way) ... but I need to confirm it ... so:

Just to confirm ...

Is your manila 2.1 ?

How long have you been since your flashed official rom for the last time ?

Have you ever used Mtty ?

Do you have activesync running when looks app runing in task manager ?

Do you usually lock your device (that we can do by long end key push) before put it to sleep ?

Have you got any lockup with official rom ?

Solution:

1) Don't throw away your blackstone I think I can help you ...

2) Answer above questions ...

3) Read all this thread from the begin

I had been form august to december surviving with 4 lockups a day (on true I just could survive with it because I didn't putted it to sleep any more ... I passed the days with screen turned on and battery life of 18 hours and recharging it everyday....) and now I have none for the last 6 days and I really know they are gone ...
[Touch HD Windows Mobile ROM Development] Marne Jr:
Are you on a constant lockup that can be solved by taking off battery isn't it ?

One of the lockups I got lasted 4 hours and take off the battery didn't helped .. and then I putted in the freezer of refrigerator for about 8 to 12 minutes and it waked up from that hard lockup ... then I hard reseted it and flashed official rom ...

Have you got black screen that cann't be solved by taking off battery ?
[Touch HD Windows Mobile ROM Development] odm3xda:
I've been using touch hd since the very first day it was out and have been using cooked 6.5 for quite some time and i never had this issue except once and it was with manila 2.1 and not 2.5 and it happened only when i installed s2u2 and enabled the framed caller id and i did uninstall s2u2 and it never happened again. if you have that or any s2 software installed on your 6.5 winmo try uninstalling it and softreset and use the phone for quite some time and check if it happens still

Regards
[Touch HD Windows Mobile ROM Development] Oemie:
Oké after "testing" for 3 days i am going to try Xannytech rom again, we'll se what happens:D:mad::confused::mad:
[Touch HD Windows Mobile ROM Development] bodgeman:
I did the same as you, in as much as I got lockups (Xanny 1.6b) switched to windows default for 36 hrs (no lockups) switched back to Sense (got lockups)

THEN last 24hrs on Xanny 1.7b running sense (flashed to stock Rom 1st) - NO LOCKUPS SO FAR!:D

(you are far more patient and thorough than me!)

Keeping my fingers crossed;) - good luck
[Touch HD Windows Mobile ROM Development] bodgeman:
Well, i was obviously tempting fate... as within 30 mins of my last post my HD locked again (Xanny 1.7b)!

oh well - I'll have to try a manila 2.1 Rom.:confused:
[Touch HD Windows Mobile ROM Development] stathis95194:
OK guys, i have been using WM6.5 ROMs with Sense 2.5 for quite some time now and never had a lockup. After i flashed HD+Leostone ROM 2 days ago i started having lockups (2 in 48 hours).

I flashed back to my previous ROM PhamQuang's V84 and the lockup is still there.

The only thing different that HD+Leostone had was that it included Radio 1.13.25.24, which i never had on my device.

I have now flashed back Radio 1.14.25.24 and i will report my results.
[Touch HD Windows Mobile ROM Development] makbil:
You should probably flash a stock ROM. I highly doubt it is the radio that is to blame.

As for the other point, I've never used s2u2 software, so that can't be the problem. As I've mentioned before, this specific type of lockup happens even on a virgin ROM, no sw installed, no customizations, no data synced, not even an SD card in.
[Touch HD Windows Mobile ROM Development] makbil:
Maybe it's a coincidence but after almost a week without any lockups, today I installed the Neos2007 drivers and tonight I had my first lockup. If the lockups keep happening then the video drivers will be high on my list of suspects.
[Touch HD Windows Mobile ROM Development] Oemie:
Wow, i think you are going in the right direction. Sinds Xanny rom has no YouTube sound for me it was easy to handle my adiction. I am on latest NRG rom now for more then 4 days and i had no lockups. I think NRG doesn;t use the neodrivers.

So is there a way to uninstall neodrivers from a rom where they are cooked in?

Or maybe it is possible to override them with neoBeta 2...:confused:
[Touch HD Windows Mobile ROM Development] golightlygl:
Has anybody managed to perform this test to see the outcome? It wouold be very useful to know that I'm not following the wrong track. My further testing has narrowed it down even further and I am prety sure that I have a (sort of) reproducable scenario as follows. With NODATA turning off the mobile data connections but WiFi active, I seem to have suffered nothing (only six hours though so still inconclusive).

I believe that the reproducable scenario is as follows:

Screen asleep for an (as yet undetermined) period of time - about half an hour to an hour or so.

Activesync over a mobile data platform (turn wifi off to be sure)

Incoming mail via Activesync

I will experiment further on the wifi/3G/GPRS seetings as it may be only GPRS or HSDPA etc. that causes the problem. With detailed info, I am hopeful that one of the ROM chefs may be able to help us but I really need more people to confirm if the scenario is reproducable on different phones. If we can narrow this down, then the next thing to do is try Makbil's suggestion of a ROM without NEOs drivers to see if the drivers are the fourth variable in the equation.

Testing these variables in a controlled fashion takes a day at a time so I really do need some help.
[Touch HD Windows Mobile ROM Development] makbil:
Well, after a few lockups last night, I uninstalled the Neos drivers and no lockups yet. I'm going to wait until tomorrow night and reinstall the Neos drivers to see if the lockup comes back.

As for your question, you can't uninstall something that is cooked into the ROM, so not possible.
[Touch HD Windows Mobile ROM Development] makbil:
golightlygl, in addition to your test, have you installed the Neos drivers?
[Touch HD Windows Mobile ROM Development] golightlygl:
I'm on Xanny's ROM so the Neo drivers are built in. Tomorrow morning (assuming my current setup survives the night) I will flash a ROM without Neo's drivers and then turn data on again. Apart from Miri's do you know of any other Neo-free Sense 2.5 ROMs?
[Touch HD Windows Mobile ROM Development] Zydol:
Hi

I'm on Xanny 2.4. And the last 2 days I have 8 lockups :mad::mad::mad:
[Touch HD Windows Mobile ROM Development] golightlygl:
OK, but don't whinge. We're trying to help each other out here. Read the thread and contribute by testing.
[Touch HD Windows Mobile ROM Development] ClydeB1:
Looks like you are making progress in identifying one half of the problem at least. If Neo drivers are the "common denominator" it would still be interesting to establish what else causes this to happen. I mean, I have always used the Neo drivers and am yet to have even one lockup (touch wood :p) so what else is it that triggers the problem, ie why do some users have the problem and others not?

Although for those experiencing the lockups I'm sure that knowledge that you will only have to avoid the Neo drivers (again, IF this is found to be the likely cause) to prevent lockups will be enough for all of you I'm sure.
[Touch HD Windows Mobile ROM Development] golightlygl:
ClydeB1, can you confirm whether the other issues in my posts apply to you? i.e.:

Do you use Activesync over 3G/GPRS to fetch mail (wifi turned off) and receive a mail this way after the phone has been to sleep for an hour or so?
[Touch HD Windows Mobile ROM Development] ClydeB1:
No I don't use Activesync over 3G/GPRS to retrieve mails, I just receive my normal G-Mail's over 3G/GPRS.
[Touch HD Windows Mobile ROM Development] golightlygl:
OK thanks. That's promising. Tonight I will turn 3G back on and turn off my Activesync email and just receive with IMAP - I will also leave Xanny's rom with Neos' drivers.

If all is good overnight, then I'll try a non-Neo ROM tomorrow and turn Activesync back on.

I think we're closing in.
[Touch HD Windows Mobile ROM Development] drakkard:
I had also many lockup with the kitchen ROM Eclipse 2.0 from MIAMMIAM.

Only one solution for device work again => hard reset, not great...
[Touch HD Windows Mobile ROM Development] makbil:
Just for the record, I also only use 3G/GPRS, never use Activesync for emails and don't sync to Outlook.

Still no lockups after uninstalling Neos drivers. Another idea that comes to mind is that could it be possible there are different revision graphics chips in our HDs or a revision on the motherboard that affects how it works? Perhaps that could also explain why some are not affected by the lockups - assuming that Neos drivers are responsible for the lockups, not yet confirmed.
[Touch HD Windows Mobile ROM Development] matt.d.reid:
Hey thanks so much for the reply... Ok so my answers are as follows:

Is your manila 2.1 ? No - Manila 2.5

How long have you been since your flashed official rom for the last time ? at the mo have not been able to flash at all

Have you ever used Mtty ? No not sure what Mtty is?

Do you have activesync running when looks app runing in task manager ? yes but no joy.

Do you usually lock your device (that we can do by long end key push) before put it to sleep ? Normally lock device via start menu but was set via long key end push.

Have you got any lockup with official rom ? currently unable to flash but will attempt to flash via SD card method tomorrow.

Really appreciate your assistance.

Matt
[Touch HD Windows Mobile ROM Development] Zydol:
Sorry golightlygl, but I read all pages in this thread and Xanny, every day. I'm testing a lot off rom's. And bee sure, if I will find something what can be usefull for all of us I'l write this emedetly.

Makbil, how did You uninstaling the drivers? :confused:

Just to owerwrite with previous version? or You change rom?
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Interesting stuff, though I do have Neo drivers installed, also use 3G/GPRS, never use Activesync for emails but do occasionally sync to Outlook and like ClydeB1 I'm yet to have a lock up (touchwood).
[Touch HD Windows Mobile ROM Development] makbil:
I'm currently using Miri's ROM where Neos drivers aren't included. If you are using a ROM with the driver built in, you can't uninstall it.
[Touch HD Windows Mobile ROM Development] makbil:
Want to trade HDs ? :D

That is why I think there is a strong possibility of hardware being part of the issue.
[Touch HD Windows Mobile ROM Development] Zydol:
That I was think, btw, how is situation with lockup, on Miri's ? tooday I have "just" 2 f..... lockup. Now I'm back to ship rom. How You think, can we ask Xanny to cook some of his rom, without Neos' :confused:I know that He dont like too make something personal....:( but maybe
[Touch HD Windows Mobile ROM Development] captvictor12:
HD wont start up

Hi, I have recently installed miri rom 21885 WITH MANILA 2.5.I am facing a terrible problem that my HD black out at any time. Then i have no option but to take out the battery & restart it. Again while it is starting up it hangs up at the Smart mobility screen. I have to take out the battery & restart again. I am stuck up in this loop please help me.