yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] JanSchotsmans:
I only had this with Dutty and Miri's 21xxx series with Manila 2.5.

Once I went to 28xxx series, from PDAViet, Energy etc, this hasn't happend again.

So I'm guessing its WM6.5 21xxx and 23xxx related rather then manila.

Also, it happens far less when you use a lightweight (short and low bitrate) sound for notification.

It seemed to happen for me whenever the "new mail" or "new sms" notification was supposed to sound.

When putting a very short sound, it stopped freezing. When putting back a long sound, it would freeze up more often.
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
A number of people have stated that they get issues with cooked roms (while others don't) if they are constant flashers, and the common solution would be to flash a shipped rom and then back to cooked. As I stated above I've been fortunate enough not to experience this so haven't had the need to flash a shipped rom. But from reading users issues this isn't a clear cut problem as it doesn't affect everyone
[Touch HD Windows Mobile ROM Development] makbil:
I've ruled that out. I always install the same set of applications, same email etc.

Never have this issue on stock ROM or Manila 2.1 ROM, only on later M2.5 ROMs, so it has to be related to M2.5 somehow.

Xannytech has been very helpful, comparing ROMs where I had this issue with a few ROMs where I don't have it, it seems that the problematic ROMs are larger in size. So perhaps there is a problem with the NAND memory and the bigger size ROMs use it whereas the smaller size ROMs do not use it. This is the reason why I mentioned hw revision as a possible cause.
[Touch HD Windows Mobile ROM Development] makbil:
It does happen on a bare ROM, no data sync, no SD card, no applications installed. Just flash a new ROM and wait, it will happen.

I guess it would be OK to mention here that currently the only ROMs where I don't have this issue is with Miri's ROMs (which are smaller in size than others).
[Touch HD Windows Mobile ROM Development] termignoni:
wow.. luckily i came through this topic before i sent my HD for repairs.. and i thought it was the touch screen that has malfunctioned..

u are right, it only happens when the device wakes up from sleep.. if ur lucky, u could press half the screen and re-calibrate the screen.. if ur not, then hard reset is the only way for u to re-calibrate ur screen..

currently using;

GridLeo 1.7 (1.2.5.30),

OS (5.2.21869)

Manila 2.5.19201130.0,

Radio (1.14.25.24)
[Touch HD Windows Mobile ROM Development] makbil:
This doesn't appear to be the same issue. If you take the battery out and restart your HD, things should get back to normal - for a while. This never leads to a hard reset.

For your case, I suggest you flash a stock ROM and test with it for a while.
[Touch HD Windows Mobile ROM Development] termignoni:
As you say, removing the battery or soft reset resolves the issue, but not for long before it happens again (unresponsive screen after sleep, but backlight lights up when i tap the screen)..

this is what is going on with my HD.. until one day, even after soft reset, i could not enter my pin or even access the calibration screen as i could only "tap" the top half of the screen..

after many soft resets, i could only "tap" the top half.. hard reset resolved my problem until a couple of days back, where the problem seems to start again.. this has been going on since last month, and out of the blue..
[Touch HD Windows Mobile ROM Development] makbil:
I never got as far as having to do a hard reset but I guess it is possible after extended use.

I recommend you flash a stock ROM, use it for a while. When you are sure you don't get the lockups any more, flash your favorite custom ROM again. This should prove that the culprit is ROM related and not a hw problem with your HD.
[Touch HD Windows Mobile ROM Development] termignoni:
i suspect it's a ROM issue as well, as i never had this issue with any other ROMs with the old Manila.. i'm gonna flash to the stock ROM tonite and see how things go.. but even so, i might take more than a week before it's showing signs of mis-calibration..
[Touch HD Windows Mobile ROM Development] makbil:
If you do have this problem on a stock ROM, then definitely it's a different problem. Just remember to flash the stock ROM by running the executable and not through running the BlackstoneRUUWrapper + nbh file manually.
[Touch HD Windows Mobile ROM Development] bodgeman:
I've had this problem for the past couple of months whatever Rom i use and whatever software i install.However, I did the MTTY thing to clear ALL the memory then reinstalled my favourite cooked rom (Xannytech ROM Grid Evo Turbo 1.6 (Internal Rel. 3.2.5.48)) and have had no problems for 2 days! hooray.

http://xdaforums.com/showthread.php?t=540290
[Touch HD Windows Mobile ROM Development] termignoni:
any reference to this "MTTY thing" u did? i might give a try 1st..:)
[Touch HD Windows Mobile ROM Development] makbil:
I also did the MTTY thing but had the lockup within 24 hours on Xanny's Evo 1.6. Keep a close eye on this, if you don't have it within a few days your problem may have been cured :)

Didi you flash from SD card or from the PC?
[Touch HD Windows Mobile ROM Development] makbil:
Here :) . My results are on page 50.
[Touch HD Windows Mobile ROM Development] termignoni:
thank you..:)

btw, this time i flashed using PC instead of the SD card..

one more thing to add, the first time i did my hard reset, i restored my device using PIMBackup (restored everything).. within 24hrs, it happened again..

the 2nd hard reset, i restored only my Contacts and till now (after 3weeks), only it's starting to happen again..

i don't know bout u, but this is how it's happening to me..

- at first, u'll notice a slight mis-calibration while typing an sms or selecting something (after screen calibration, everything went fine)

- then, after a few days, same thing happens (can't tap the bottom part, soft reset and screen calibration solved this)

- and today, after my device woke up on sms, i could not unlock (using the default WM6.5 lock screen - had to soft reset twice, then calibrate screen)
[Touch HD Windows Mobile ROM Development] hadryen:
sorry to bother you, the answer is probably easy to find, still, I can't find a stock rom for my blackstone... and the HTC website refuses to let me download one (as my serial is supposedly not correct...)

Thanks a lot.

ps : will I have to downgrade SPL (it's currently 1.56 OliNex if i well remember) to install a stock rom?
[Touch HD Windows Mobile ROM Development] ClydeB1:
You can find many shipped stock roms here

Yes, if you are using spl 1.56.Olinex you will need to flash to a spl that matches the rom you choose, unless you are only wanting to flash to clear up the phone and are going to flash back to cooked thereafter. You can also find the procedures to revert to stock spl here(at end of post).
[Touch HD Windows Mobile ROM Development] stathis95194:
Here you can find ship ROM's

http://wiki.xda-developers.com/index.php?pagename=HTC_Blackstone_Versions

If you are on 1.56 Olinex you can flash any ROM for Blackstone, even shipped ones without any problems.
[Touch HD Windows Mobile ROM Development] mnet:
I have used Neo's drivers previously on miri's roms and currently on my own manila 2.5 rom and never experienced lockups. However the fact that this happens during standby implicates drivers as the possible culprit, because during standby mode applications are shutdown while some drivers remain active.

I suggest comparing the keys under HKEY_LOCAL_MACHINE\Drivers\ between roms that have the lockup problem and those that don't. There are some driver 'tweaks' that are popular among some cooks, but of course these are not tested by htc and therefore make the device susceptible to problems like these.

I highly suspect power management keys as the possible culprit. On stock roms, HTC disables power managements on some components:

[HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms]
"DisablePowerManagement"=dword:1

[HKEY_LOCAL_MACHINE\Drivers\SDCARD\ClientDrivers\Class\SDMemory_Class]
"DisablePowerManagement"=dword:1

[HKEY_LOCAL_MACHINE\Drivers\SDCARD\ClientDrivers\Class\MMC_Class]
"DisablePowerManagement"=dword:1

HKEY_LOCAL_MACHINE\Drivers\SDCARD\ClientDrivers\Class\NAND_Class
"DisablePowerManagement"=dword:1

[HKEY_LOCAL_MACHINE\Drivers\SDCARD\ClientDrivers\Class\SIM_Class]
"DisablePowerManagement"=dword:1

see if "DisablePowerManagement" is set to 0 on the roms that have this problem.

Also this might be related to a popular 'sd tuneup' tweak. Compare the keys under HKEY_LOCAL_MACHINE\Drivers\BuiltIn\SDHC and HKEY_LOCAL_MACHINE\System\StorageManager\FATFS between roms that have this problem and those that don't.
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Nice direction to look at, I'll have a look to see if anything stands out, though I'm finding it hard to test as I do not suffer from these lockups
[Touch HD Windows Mobile ROM Development] golightlygl:
I've currently switched from Xanny to NRG to see if that makes a difference so can't test the registry entries yet. So far 14 hours and no problem so that looks encouraging.

neoS2007, to be clear about the device "not waking up". What often happens is that the by operation of the power switch from sleep, a backlight of sorts switches on but with a blank screen. One can see the backlight by looking towards the bottom of the screen where a glow appears.

Everyone, I know I keep banging on about this but there is definitely a correlation (at least on my device) with 3G/GPRS data. Having extensively tested with data off on Xanny's ROM with no problems, as soon as I switched it back on I had lockups every hour.

I am totally convinced that whatever problem it may be with the drivers, a lockup is only triggered when a 3G/GPRS data fetch occurs (i.e. mail delivery, weather update etc.) although a data fetch does not force a lock.

It would be helpful if someone expereincing lockups could just turn off their data for a day (use NoData cooked into Xanny's ROM) and see if they have a trouble-free day.

Makbil, I'm intrigued about Xanny's Neo's-driver free ROM for you. How does it affect day-to-day performance?
[Touch HD Windows Mobile ROM Development] jtf420:
REG detail of my THD

[HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms]

"DisablePowerManagement"=dword:0

[HKEY_LOCAL_MACHINE\Drivers\SDCARD\ClientDrivers\Class\SDMemory_Class]

"DisablePowerManagement"=dword:0

[HKEY_LOCAL_MACHINE\Drivers\SDCARD\ClientDrivers\Class\MMC_Class]

"DisablePowerManagement"=dword:0

HKEY_LOCAL_MACHINE\Drivers\SDCARD\ClientDrivers\Class\NAND_Class

"DisablePowerManagement"=dword:0

[HKEY_LOCAL_MACHINE\Drivers\SDCARD\ClientDrivers\Class\SIM_Class]

"DisablePowerManagement"=dword:0

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\SDHC]

"IsCardInserted"=dword:00000001

"Flags"=dword:00000000

"DMAChannel"=dword:00000000

"DMAIrq"=dword:00000024

"DMA_IST_Priority"=dword:00000096

"SDIOIrq"=dword:0000001e

"SDIO_IST_Priority"=dword:00000097

"PollingTimeout"=dword:00000100

"CardDetect_Thread_Priority"=dword:00000098

"CardDetectGPIO"="F"

"CardDetectMask"=dword:00000020

"CardDetectFlag"=dword:00000000

"CardDetectControlMask"=dword:fffff3ff

"CardDetectControlFlag"=dword:00000000

"CardDetectPullupMask"=dword:ffffffdf

"CardDetectPullupFlag"=dword:00000020

"CardReadWriteGPIO"="H"

"CardReadWriteMask"=dword:00000100

"CardReadWriteFlag"=dword:00000100

"CardReadWriteControlMask"=dword:ffcfffff

"CardReadWriteControlFlag"=dword:00000000

"CardReadWritePullupMask"=dword:ffffffbf

"CardReadWritePullupFlag"=dword:00000040

"HandleBusyFinishOnCommand38"=dword:00000001

"DmaTransferTimeoutFactor"=dword:00000008

"DmaTransferTimeoutConstant"=dword:00003000

"CardDetectThreadPriority"=dword:00000096

"IClass"="{8DD679CE-8AB4-43c8-A14A-EA4963FAA715}"

"Prefix"="SDH"

"Dll"="sdhc.dll"

"Order"=dword:00000021

[HKEY_LOCAL_MACHINE\System\StorageManager\FATFS]

"CacheSize"=dword:00001000

"Flags"=dword:00000044

"CacheDll"="diskcache.dll"

"Util"="fatutil.dll"

"EnableCache"=dword:00000001

"Paging"=dword:00000001

"Dll"="fatfsd.dll"

"FriendlyName"="FAT FileSystem"
[Touch HD Windows Mobile ROM Development] makbil:
Well, I'm on my second day using Xanny's test ROM and still not a single lockup :)

As someone who has consistently had to deal with the lockup issue, I would say this specific ROM does not have the lockup issue and it does have Manila 2.5.19211619 and WM 6.5 28014 but not the Neos driver pack.

So in my experience with both Xanny's and Miri's ROMs, WM 28x and Manila 2.5 together do not cause lockups, however if you add the driver pack the HD will lockup.

If you take Manila 2.5 out, no lockups with Manila 2.1 or just using Titanium.

At this point, I think there are 3 contributing factors to this lockup issue:

1- Manila 2.5

2- Neos's Driver pack

3- Perhaps some subtle hardware differences in our HDs.

Looks like all 3 have to be present for the lockup issue to occur.
[Touch HD Windows Mobile ROM Development] mnet:
Try setting all the "DisablePowerManagement" to stock value (dword:1). See if you still have lockups.
[Touch HD Windows Mobile ROM Development] makbil:
In Xanny test ROM, this value is "0" but there are no lockups.
[Touch HD Windows Mobile ROM Development] mnet:
I thought you already established that all roms have no lockup when Neo's drivers are not installed? Regardless of any other factors...

Now we are trying to find out why a small minority of user are having problems with the driverpack. Since the problem happens only in standby, I suggested that it might have something to do with power management. Furthermore, some users have indicated that this seems to be related to data synchronization, which specifically implicates this key:

[HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms]

"DisablePowerManagement"=dword:1

Although it would be best to restore all the Power Management keys I mentioned in my previous post to stock values...

Btw, although the notion of "subtle hardware differences" can be a tempting easy explanation for such problems; it is highly unlikely that there would be any differences between devices--never mind differences that actually affect the functioning of drivers.
[Touch HD Windows Mobile ROM Development] makbil:
Yes, actually I wrote that to confirm what you were saying, sorry for the misunderstanding.

So what you are saying is that the driver pack and the above registry values may be a factor. I will definitely check this when Xanny comes up with his new ROM with the driver pack. Since I've established that EVO 1.8 without the drivers works without a problem, it should be easier to troubleshoot the same ROM with the drivers included.

The notion of hardware differences has to be taken into consideration, by that I don't necessarily mean different components but perhaps a revision on the motherboard. This is the only logical explanation so far that can explain why some do and some don't get the lockup issue, even when they are on the same network.
[Touch HD Windows Mobile ROM Development] mnet:
Even if some HDs use a different part number for a certain component (which is highly unlikely considering the design and manufacturing process of a device such as the HD), that would not affect the functioning of graphics drivers as these only concern the chipset. All MSM7200A/MSM7201A chipsets (the "1" is just because of a patent issue) share an identical graphics core (7201A have crippled video recording FPS due to the aforementioned patent--otherwise they are identical). All HDs have a MSM7201A chipset. Furthermore, Neo's drivers work on any MSM7200A/7201A device, such as the Diamond which DOES have different part numbers from the blackstone (for components other than the MSM chipset). If you take that into consideration, you can see why it is practically impossible that a subset of HDs have a problem with graphics drivers, while all other MSM7200/1A devices do not.

I don't mean to be combative or anything--just want to help in getting to the bottom of this issue, and ruling out the possibility of hardware causes can be helpful.

The different experiences among users could be due to a difference in the tasks that run during standby (just a possibility)
[Touch HD Windows Mobile ROM Development] Osir1s:
I may be misinterpreting your statement or your objectives but reitterating the general problem, there are several posts, mine included stating that lockups occur w/o the driver pack being installed. My lockups have been significantly reduced going back to WM 21882 Manilla 2.5 but on 28XX builds with Manilla 2.5, I had frequent lockups. In both cases NO driverpack was installed.

Prior to moving to 6.5/manilla 2.5 based roms I never experienced these issues.
[Touch HD Windows Mobile ROM Development] makbil:
Yes, I understand what you are saying and thanks for your help. It's just that in view of so many unknowns, I don't think hw should be completely ruled out, until we get some facts to the contrary.

I know that in the case of the Sony Ericsson P990, there were subtle hw differences between devices, revision number was indicated on the box as well, so it's not entirely unlikely.

We are just brainstorming here, so any suggestion is welcome.
[Touch HD Windows Mobile ROM Development] NeoS:
I couldn't have put it better. A question though: Is the Blackstone the ONLY device running WM6.5.X and Manila 2.5, combined with the driverpack that has this issue? Or does the Topaz and other MSM7201A devices also suffer from this?
[Touch HD Windows Mobile ROM Development] t0k0m0k0:
sorry to disturb the specialists' discussion about manila 2.5 only, but from my personal experience i can tell that:

- installing xannytech grid leo 2.3 rom i had the lockup issue during 2 days (several times)

- then flashing topix 3.2.3 with manila 2.1 and wm6.5 (and weather on home page) i had a first and last lockup during the first day of use... and nothing at all since 1 week of use... (without any other flash or something like that).

if it can helps about activesync: i use autosync and autocheck emails with gmail (imap and activesync server) each 10mins. I have disabled the "MS directpush" option in communication manager which could have been left enabled during the first use of both roms...

about the "too much flashing" reason on hardware health... I've only flashed my HD 4 or 5 times... i dont think it can be the reason...
[Touch HD Windows Mobile ROM Development] golightlygl:
These are interesting ideas, mnet. I shall be keeping my NRG ROM for the next 24 hours just to see if no lockups occur. Interestingly, this key is set to "1" in the NRG ROM. If all is OK, then I will reflash Xanny's ROM with the NEOs drivers and reset these power management parameters for a test over Christmas.

What is the practical effect on battery life of restoring these settings (although if a practical effect is that I keep NEOs drivers, and my mail sync and get no need to reboot, I can live with an hour or two of less life).
[Touch HD Windows Mobile ROM Development] fuithecat:
Just want to report that I tried the following as suggested

[HKEY_LOCAL_MACHINE\Comm\AsyncMac1\Parms]

"DisablePowerManagement"=dword:1

with Xanny's 2.3.1, and it didn't help. Still experiencing lockups. So far I had been using the default 6.5 today screen for 5 days without probloms. Looking forward to seeing someone nail this problem.
[Touch HD Windows Mobile ROM Development] paplino:
Hi Makbil,

No lockup experienced whatsoever, I'm still using Dutty's latest Sense 2.1 ROM (dated November 5, if I'm not mistaken). Always flashed with SD. I've started experiencing some issues with the device, for instance, while watching a movie (hosted on the SD card, so no networking involved), the devices "flashes" quickly on and off, as if I would have pressed the power button. Playback of the movie continues after this "blinking", the device remains responsive. Other than that, no problems.

I cannot tell you exactly what sort of hw revision is in my device, all I can say is that I bought it, new, in Prague (CZ), in last weeks of July. If you can tell me where to look, I can check for more detail and let you know.

Best regards,

Paplino
[Touch HD Windows Mobile ROM Development] makbil:
This specific issue only happens with Manila 2.5, so you should be immune.
[Touch HD Windows Mobile ROM Development] miniterror:
dont know if it helps but i have never had one of those lockups

and im using my rom for a couple of months now

im using the m2.5 rom from nrg dated as 23-09

i always instal neos his driver pack

the softwareinfo tells me this

os version:5.2.23016

manla version:2.5.19192828.0

protcol:52.62.25.34u

edit i have had it whit some roms but cant remember wich they where since i flashed a lot of roms(and still doing)
[Touch HD Windows Mobile ROM Development] hadryen:
had the lockup while using roms cooked with manila 2.5 (eclipse and L26). Since i use the Sunrise rom (manila 2.1), the phone is working perfect...)

i load from computer, HSPL (as explained in the tutorial), hard reseted, it kept on crashing with manila 2.5's rom...

good luck to find the issu, thanks.
[Touch HD Windows Mobile ROM Development] hadryen:
Thanks a lot!!!
[Touch HD Windows Mobile ROM Development] loop69a:
Hello,

I'm following this thread since the beginning and here is my experience so far:

I installed Miri 21885 Manila 2.5 Rev 15.0 (NoHtcMessage) from the PC over an old Dutty 1.7 and hard reset. Then restored only contacts/text messages from a Sprite Backup and installed NeoDrivers.

I let defaults setting for power management, set weather fetch every 8 hours. Nothing else was scheduled to fetch data such as mail.

I had a lockup (white/grey screen while pressing the power button) every morning for 4 days.

Since I have disabled the "today timeout" and the weather fetch, my phone never opens data connections on its own especially while in sleep mode and no lockup anymore (5 days).
[Touch HD Windows Mobile ROM Development] jpcicno6:
I was using Dutty's Holy Grail R0 Leo Edition and it was locking up 2-5 times a day for me and SMS' stopped being sent from my phone

Flashed Energy Leo Rom (cant remember which version) and although the locking stopped (for the 1 day I used it) I still could not send sms

Now I am using MaryOne's Leo Rom for around a week and it locked up once so far and no prob's with sms
[Touch HD Windows Mobile ROM Development] golightlygl:
loop69a,

Thanks for that confirmation. The TODAY TIMEOUT issue was I discovered and used with Dutty's 1.9 ROM. It hasn't worked for subsequent ones if I use data connections. Your ROMs behaviour since uncheckign the weather fetch confirms my beliefs that data fetch has something to do with this.

I have just survived a 24 hour period with the EnergyRom (which I believe does not have Neo's drivers). I will now reflasdh back to Xanny's 2.4b and implement mnet's full power management recommendations. I will report back as everyone starts tucking into the Christmas turkeys.
[Touch HD Windows Mobile ROM Development] bmer:
Rom Eclipse 2

I used HD Tweak to uncheck " lock pda when stopped " then I installed S2U2 ....

Now everything seems to work fine !!!!

Maybe the soft used to lock the HD with Manila 2.5 is not compatible with the

HD ????
[Touch HD Windows Mobile ROM Development] mnet:
that makes sense because HD's drivers were never designed to work with the wm6.5 lock screen, and there are known problems with backlight.dll on wm6.5
[Touch HD Windows Mobile ROM Development] golightlygl:
Just realised what the "lock" meant. I have never used WM 6.5 lock screen so that is not the cause in isolation.

bmer, can you confirm that you were experiencing lockups as described in the first post - or some different type of crash.
[Touch HD Windows Mobile ROM Development] makbil:
There are some interesting suggestions in the past few post. They could all be part of the remedy for this lockup issue but still doesn't explain why on Xanny's ROM without the drivers I never get a lockup whereas on his ROM with the drivers I started getting the lockups within a few hours. I made sure to do the same things on each ROM and Xanny confirmed that this is the only difference apart from a few new packages that shouldn't affect this issue.