yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] andes83:
Hi Makbil no i didn't flash stock ROM's or use MTTY before Miri's i was a long time with Dutty's Holy Grail 2.5 manila (I guess for two weeks or so) and I was extremely happy with it never had lockups or anything but of course I got interested in the newest builds and started flashing on Miri's 28011 (otherwise the ROM's are great I was really dissapointed by the blackouts) I had the lock up the same night of the flash .Now I'm on Kwbr's 3.2.3 6.5 and haven't had any lockups for two days.Just to make my lockup problem clear cause I see there are different kinds is that when my phone goes to "sleep" for a long time (at night) in the morning the screen is black the phone is on (you can see the light) but you can't do anything only soft reset so I thing it's the "non hardware related" kind.
[Touch HD Windows Mobile ROM Development] miancule:
I am just wondering - how are you guys flashing your ROMS ?

USLP or HardSPL - I am using USPL, and it might be just that the original SPL (1.54/1.56/1.59) is not a good match for the ROM. That could explain why some people are never witnessing the lockup. Dunno.. I am just speculating.
[Touch HD Windows Mobile ROM Development] makbil:
Currently I'm using HSPL. It doesn't matter whether you use USPL or HSPL.

One thing is becoming clear: the lockup I've described in the OP is experienced by a number of users, all on the latest M2.5 ROMs. From my experience, the version of radio used is irrelevant, happens with all radio versions. It has also started happening within the past few months, with the newer Manila 2.5 ROMs.

This problem may be more widespread than we realize, the only puzzling thing is why it affects only some people.
[Touch HD Windows Mobile ROM Development] bodgeman:
I am using HSPL and am encountering these problems - strangely random, but often after long periods of sleep (after HD is plugged in at night - in the morning the screen is "luminous" but needs the battery pulling to reboot)
[Touch HD Windows Mobile ROM Development] mwaldi3:
I have exactly the same described problem as Makbill! I think you are right this is a wide spread problem and seems to go through stages where it happens frequently or maybe once or twice a day?

I flash using Hspl am running Xannys Evo 1.6 and radio 1.17. I have experienced this with a lot of the 2.5 roms I have flashed.

I also use PIM backup to restore my contacts and Shashimi. I will try it again without either of these....

Thanks for starting this thread... I thought like many others that it was a hardware issue but maybe it is software related.

As a note I am flashing using Windows 7 x64.
[Touch HD Windows Mobile ROM Development] 3lixir:
As far as I can see the only difference between users assuming they have the same rom installed and no apps is operator and location, perhaps people could list their operator and whether or not they experience freezing to see if there's a link there?
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Not sure its as simple as operator and location. 2 people using Orange living in UK, one has freezing issue, the other doesn't.
[Touch HD Windows Mobile ROM Development] vjeta:
I have exactly the same problem, black screen with light after sleep, have to remove battery,...

One thing I noticed is that it happenned more frequently if you install gfxboost.

With this program = 4 - 5 lock ups in a day

Without this program = 1 or 2 lock ups in a week

This is with every coocked rom I trie.

My operator is movistar, in spain, but I don't think this is an operator related issue because it never happenned to me with stock roms and with manila 2.1 roms.

We need to find out a solution, because if not i'm going to throw my hd out of the window.
[Touch HD Windows Mobile ROM Development] elmutchi:
I kind of noticed that when locked up the screen is in same state as it is for a brief moment in between rotation from portrait to landscape.

Maybe the rotation script or g-sensor is linked to that.

And I noticed it happened a couple of times while I was grabbing my phone => accidentaly rotating the screen maybe.

Note: it happens rarely I gotta admit, but still is annoying.
[Touch HD Windows Mobile ROM Development] t0k0m0k0:
super... i am not alone!!!

Great idea to have this topic ;) , I have exactly this problem since... 4 days! and I have flash my rom 4 times... in 4 days... :eek:

Affirmative

Negative...

I have tried at first last xannytech stable ROM version... and I had the problem. So I though it was Manilla 2.5 related, but with the last Topix on wm6.5 I have the same issue. And I have seen on the last Dutty HG Rom wm6.5+TF3D2.1

references:

- Xannytech 2.3.1B Sys 21885 http://xdaforums.com/showthread.php?t=565290

- Topix 3.2.3 sys 21884.5.0.85 http://xdaforums.com/showthread.php?t=460640

- Dutty ROM: 5.2.21869.5.0.82 see here in comments http://htcpedia.com/duttys_hd_sense...a83ccf5/soft/htc-blackstone-rom?page=4?page=4

It looks like a problem of "last drivers" version, or "last kernel", or something like that.... And Manilla 2.1 is concerned too

i'm not a specialist but obviously there is something in common between those ROM

Affirmative and if it comes to be more often I will have to find quickly a solution!!!

After almost 6 months with a very nice use of the ROM Dutty wm6.5 R9 I had never never this problem.... so it is NOT a hardware problem (or the flash have destroyed my HD... I didnt see the smoke... seriously!)

Finally, as you see from the last affirmation, this is not due to the operotor neither...

hope this would help...

about the screen rotation, i dont think so...

so this doesnt look like a specific kitchener problem... but sounds like more general... any ideas from professionals?
[Touch HD Windows Mobile ROM Development] onesolo:
I once had this happened but only after installing a Xanny rom with Leo. I don't remember the version, but I know that after a day or two I flashed with miri's v12, and since on I never had again a lockup.

I'm now on the verge to update to a new rom and probably going to install again a rom from Miri
[Touch HD Windows Mobile ROM Development] jigners:
this is what I dont understand, why so many people still flash Man 2.5 ROMs,

when after so much bug fixing and this "LOCKUP" problem, although - fair play

to the ROM Chefs as they monitor their threads closely and help out with

problems. To me Man 2.5 will never reach the level of stability and speed

that many of us enjoy with a Rhodium Port.

I understand People always love to experiment and likes to see what's over the

hill, this brings out the creative in all of us, but Im sure their should be an equal

number of people who are happy and content with stable Rhodium ports, but to

my surprise this is the contrary.

99% of all Rhodium Man 2.1 Sense Port ROMs Ive tried never had experience lockup
[Touch HD Windows Mobile ROM Development] andes83:
The problem is that it's randomly occurring and it's tough for me to remember all the little things but for sure it was always on a fresh ROM and every time the first night so it's not something that happens after a lot of use it appears soon after the flash . Manila 2.1 was never mentioned till now but I see it's affected too so my theory "Leo software on HD is bad" goes down the drain.I also thought about the NO DATA fixes that almost every new ROM has so that the device doesn't try to connect automatically every time.But I can't figure out why it always happens in sleep mode.....what apps are active then or what app can activate when the phone is asleep isn't that the sole purpose of "sleep" mode that nothing happens on your device and to "wake up" by itself only on incoming call, sms or email .... Now I don't have that problem but I don't know if I'm happy or sad cause it can occur at any moment when I'm not expecting it.
[Touch HD Windows Mobile ROM Development] James62370:
I concur with the above. It usually happens when the phone has been in sleep mode for a long time. Strange, it appears to occur more when you let the phone sleep on it's own, without hitting the power button and plugged in, after many, many hours, I experience this lock up.

It is quite annoying especially when you depend on the alarm to wake you up. I've been using XannyTech's and NRG Rom's for the most part...

Hope there is a solution soon.
[Touch HD Windows Mobile ROM Development] makbil:
I can confirm that I also never had a lockup with Miri's ROMs. I was thinking it may have been a coincidence but apparently not. Now I'm using Miri's test version, in my 3rd day and still not a single lockup. On the other hand, I had several lockups within the first day using another ROM with the same windows version and possibly the same Manila files.
[Touch HD Windows Mobile ROM Development] MJRL:
The first lock up i had was with manila 2.1 and after some weeks of use, the only thing that i never did before was to drain the battery complete.

I was using L26 rom.

Then i had 2 lockups more using manila 2.5 with xany rom's, the first time i flash and didn't install anything only arranged programs and folder with totalcommander, when i power the device the screen its black.

The second time, i flashed to stock rom, hard reset, then install radio 1.14, then flashed with uspl xanny Evo1.6b, hard reset.

After configuration i have to turn off the device, didn't install anything, when i power up, the device was locked with black screen, take the battery out and power again, no problems.

Since then i've installed all my app and even some mods (B4all) and the device never locked again, with the same rom, i'm using this rom since release.

:D
[Touch HD Windows Mobile ROM Development] makbil:
Correct, If it is going to happen, it will happen within the first 24 hours of flashing a ROM.

I'm still not sure about that. Personally, I've never had it on a M2.1 ROM, so until we get some more confirmation, I'd like to keep the M2.1 case on standby. That specific lockup may have other causes, possibly some customization or excessive flashing without flashing a stock ROM in between.

Well, as you have said, the email, SMS and phone functions are never asleep and they do seem to respond to the operator, the problem is with the next level, the phone rings but the necessary modules to get the ringtone working and wake up the HD are frozen. If you look at the first post of the radio thread, it looks like the problem may start at the ril driver level.

Rotation was mentioned as a possible cause, I find this unlikely as Manila 2.5 ROMs do not have rotation enabled at the home screen and I always leave my HD there and still had the lockup.

Gfxboost could be a suspect. Perhaps it should be investigated further. I'm not so sure at the moment but I think Xanny took it out of his last ROM but I still had a lockup.
[Touch HD Windows Mobile ROM Development] bodgeman:
this was not the case for me after MTTY and HSPL to Xanny Evo 1.6b - it was around 60 hrs before i had the first lockup (thought it was cured!). before this it was within a day.
[Touch HD Windows Mobile ROM Development] bodgeman:
Is this the same problem? - it sounds a little different with the lockup occuring straight after flash and power up rather than a period of sleep.
[Touch HD Windows Mobile ROM Development] MJRL:
Yes its the same, except the first lockup with manila 2.5 that was almost after a flash, the first time with manila 2.1 was after recharge, and the last one with manila 2.5 the same.
[Touch HD Windows Mobile ROM Development] makbil:
But if you flash a stock ROM before or use MTTY, is the M2.1 lockup cured?
[Touch HD Windows Mobile ROM Development] MJRL:
No, i didn't flash the stock rom before flash M2.1, only with the grid evo 1.6b last flash, i've flashed stock rom.

I didn't try MTTY metod, since my device it's ok for now, if some more lockups will happen i will try that.
[Touch HD Windows Mobile ROM Development] bodgeman:
just happened again as i was reading - i'm gonna do a MTTY and find a suitable Manila 2.1 to try or one of Miris test Rom's. Its a shame as Xannys 1.6b is my favourite Rom so far. I'll let you know if i get any further lockup's:(
[Touch HD Windows Mobile ROM Development] Marne Jr:
There is nothing to do with rotate ... cause I disabled G-Sensor and still ocurred ...

I stayed 5 days with stock rom and just pressing power button to make it sleep after I lock my device with long end key and lockup was gone ... Since August I had never been 5 days without lockups ... Today I flashed Miri 21885 with 2.5 manila rom and doing the same procedure to make it sleep and still no lockups ...

I hope never see this disgrateful lockups again ...

*PS: I did Mtty procedure before both of flashing and I was thinking that Mtty could be the solution, but I tryed 3 sleeps with power button without lock device first and 1 of then let me on lockup ... so ....
[Touch HD Windows Mobile ROM Development] Marne Jr:
It would be very nice if people could answer a test to see what is the main kind of lockup ... for example:

a) Have you ever had lockup (even one) with any manila not 2.5 ?

b) Have you ever had a lockup with official stock rom ?

c) Have you ever had a lockup after flashing a rom after Mtty procedure?

d) Have you ever had a lockup after make the devices sleep after lock it with long end key ?

For me it would be very claryfing if we know the statitistic of this answers ...

I really don't know if most people have lockups with just manila 2.5 .....
[Touch HD Windows Mobile ROM Development] Marne Jr:
I have seen some people that are on Manila 2.5 for some months and had never seen any lockup at all ...
[Touch HD Windows Mobile ROM Development] gigaboss:
I think I'm experiencing the same issue here, but I never wrote down with which roms it happened, the only thing I know is that it happened today, with Xanny's latest rom, and that to me, it seems that it would always happen, certain roms have the issue, others don't, I think that I had this issue before Manila 2.5, but I'm not sure, would that mean that it's hardware related?
[Touch HD Windows Mobile ROM Development] bodgeman:
a. No

b. No

c. Yes

d. No

I'm starting to think that it may be a hardware problem (due to the fact that so many 2.5 users do not seem to have this issue) but i'm gonna try a 2.1 or even a stock rom after MTTY to see if it stops the problem.
[Touch HD Windows Mobile ROM Development] MJRL:
a)yes

b)no, but only use stock rom for a few hours :D

c)Didn't try mtty procedure

d)don't lock the device
[Touch HD Windows Mobile ROM Development] bodgeman:
I've just thought i would switch to windows default instead of HTC Sense and see if it still stalls (still on Xanny's 1.6b with lockup problem). Not being technically minded this is probably pointless (let me know) but may be relevant IF i don't get a lockup anymore (could mean hardware rather than software?)
[Touch HD Windows Mobile ROM Development] jtf420:
HTC lockHD

a) Have you ever had lockup (even one) with any manila not 2.5 ?

b) Have you ever had a lockup with official stock rom ?

c) Have you ever had a lockup after flashing a rom after Mtty procedure?

d) Have you ever had a lockup after make the devices sleep after lock it with long end key ?

a) No

b) No(but used rarely to notice it)

c) Yes

d) No Don't Lock

MTTY results (i'm afraid to post it on the parent forum..thread owner scares me)

Cmd>set 14 0

HTCST ÚÈÒHTCE

Cmd>task 29

Format BINFS start

Fill RSVD information for block 288 to 321

CE start sector=0x14, total sector of CE and TFAT=0x14

CE start start block=321, total block=3775

ERASE block 288 FAIL !!!

ERASE block 890 FAIL !!!

ERASE block 1070 FAIL !!!

ERASE block 1372 FAIL !!!

ERASE block 1554 FAIL !!!

ERASE block 1939 FAIL !!!

ERASE block 2002 FAIL !!!

ERASE block 2470 FAIL !!!

ERASE block 2619 FAIL !!!

ERASE block 3074 FAIL !!!

ERASE block 3150 FAIL !!!

ERASE block 3393 FAIL !!!

ERASE block 3718 FAIL !!!

ERASE block 3728 FAIL !!!

Write 0xFF start page=0x5040, total page=0x3AFC0

Format BINFS end

same results(with fails) everytime...

we got diff block erase failures..this makes the situation more complicated :( and interesting :)

##observations:

#. Lockups started from the time Dutty's R6-7 (did anybuddy have a lockup with distorted dispaly: checkered b&w screen ..back then?)

#. XT1.6 locked up more frequently than XT1.5(it worked without a lockup for 5 days until i installed the home screen mods)

#. MIRI roms are the ONLY lockup free ones for me.

#. Seems like the THD becomes the sleeping beauty ..only when it tries to wake up to sound a notification(incoming call,sms,alarm)

##proposal

#. Find a way to ascertain H/W rev./build type from S/N no. P/N no. thr mus be some way.

p.s. Post #6 convinces me somewhat.. anybuddy else agrees with the point made by JanSchotsmans !
[Touch HD Windows Mobile ROM Development] thefatalrisk:
I agree 100%. I experience the exact same issues in the OP, and have only started occuring lately with xannytechs latest roms (havnt tried any other roms).
[Touch HD Windows Mobile ROM Development] makbil:
Flashing a stock ROM should have the same effect as using MTTY, theoretically.
[Touch HD Windows Mobile ROM Development] makbil:
I wish it was that simple. It's entirely possible to have a lockup on a M2.1 ROM if you have done extensive flashing and have not flashed a stock ROM somewhere in between or used MTTY.

If testing for M2.1, make sure that you flash a stock ROM first. My experience tells me that this specific kind of lockup will only happen on some M2.5 ROMs. Other lockups may be due to excessive flashing, the NAND area becomes corrupt but once a stock ROM is flashed (which actually includes the MTTY process) this is cured.
[Touch HD Windows Mobile ROM Development] andes83:
There's a lot of people complaining about Xannytech ROM's could it be that somewhere in his ROM lies the hidden "culprit" as it's got a lot of programs preinstalled?My flash method has always been HSPL and always from my computer and all in all I do the same things when I flash my phone I thought of the variant a "bad flash" (something that it's not under the control of the user or cook) but I don't think it's that . Also has anyone tested if the blackouts occur on a ROM that has no applications installed by the user just the ROM?
[Touch HD Windows Mobile ROM Development] makbil:
This is a very good idea that I was thinking myself, definitely worth a try.

The only catch is (perhaps a chef could enlighten us) that some Manila files may still be running even if Sense is disabled. At least it would narrow down the suspects.
[Touch HD Windows Mobile ROM Development] makbil:
I know what you mean, I had a run in with him myself ;)

What you have posted is exactly what I was looking for. You have way more fail locations than I do. This makes me wonder if we really are dealing with a hardware issue where the NAND area gets corrupted. I'm an electronics engineer and have done some microprocessor based system designs, so I can say that if everything on our HDs was the same, the results should have been the same. There is something different, either with the board or with the microcode, there really is a physical malfunction or the MTTY does not work properly.

Same for me.

Also when you press the power on button or pull the stylus out to wake the device.

I agree but we need some info on how to associate these numbers with rev. levels.
[Touch HD Windows Mobile ROM Development] makbil:
I also had the lockups with Xanny's ROMs but he was very helpful in trying to determine what the cause may be, unfortunately no results yet.

His is not the only ROM though, I also had in on Dutty's HG 0, NRG and the Mary One ROMs, although haven't used the last two for extended periods.
[Touch HD Windows Mobile ROM Development] makbil:
Yes, a fresh install, no SD card, no data sync, no emails setup and no programs installed, didn't even change the region but still had the lockup within a couple of hours.
[Touch HD Windows Mobile ROM Development] Oemie:
I am on NRG latest 2.5 rom and i haven't had lockups today..

I'll be back when i have some news on that but for now i keep testing this rom and see what happens.

Nrg has by default auto back light turned off, maybe that is also important..

I have set it to auto for a couple of hours now..

He uses mylight 0.4 (you can get it @xda) maybe this helps Xannytech rom, but it consumes lots of battery power..

I was on 100% this morning and now i am on 16% Haha:D..I have used NRG quiet a bit, so i know it is the backlight that consumes..

Anyway, i will be back later..

Xanny's rom also started to crash a couple of times a day after i think 5 days of use of his rom..:confused:
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
ok, I've checked with 6 mates who use Xanny roms, 4 of them have not experienced these lockups including myself, the other 2 have

So I don't think its just rom related, I believe Makbil is on the right track with M2.5 and possibly hardware related. Excessive flashing also isn't conclusive as I would probably be near the top for excessive flashing and as stated previously, I don't experience this :confused:

1. Think we can rule out GFXBoost and Neos drivers as people experience these lockups with and without them

2. Can also rule out specific roms as stated above

My guts telling me its the latest manila files with m2.5, or possibly the latest build versions. Would be interesting if we could confirm if any or all builds have this lockup, ie 21xxx, 28xxx, 23xxx etc
[Touch HD Windows Mobile ROM Development] golightlygl:
I have had problems with Xanny's ROMs since 1.9 (Manila 2.5). For 1.9 and 2.0 I found a solution that worked without boubt (reproduced below)

However, since version 2.1, this fix has not solved the problem. I too think there must be something related to the hardware: not an fault, but something in the spoec. of the affected machines which is not in unaffected machines. Maybe if we can all list our serial numbers, that might help to identify a batch (mine is below).

Does anyone with better hardware/software knowledge think that the unlocking method is worth investigating?

For reference, I have experienced the problem with a freshly installed ROM and no further applications or registry fixes. I have not tried a stock from for so long that I can't say what happened then. I have also had the problem with almost all radio versions (1.12, 1.13, 1.14 and 1.17)

The only time I have managed to avoid a lockup is by turning off data fetches. In fact, moe specifically, turning off any kind of mail fetch, be it IMAP or ACTIVESYNC. This lead me to think that JanSchotsmans idea might have some merit - except that my new mial notification is the tiny MENUPOP sound (just a click).

I will try and see what happens if I leave data and mail fetch on but disable all notification sounds. Unfortunately, my best "testing" time is overnight as the phone is in use most of the day so it may take a few days to get this information out. I also wanted to experiemtn with Laurentius26's new V4 ROM.
[Touch HD Windows Mobile ROM Development] golightlygl:
One other thing: I used XDASHUTDOWN to change the power-off button from "sleep" to "lights out" - but that made no difference.
[Touch HD Windows Mobile ROM Development] bodgeman:
OK its about 15 hours since switching to windows default rather than HTC Sense (following a couple of lockups on xannys 1.6b) and so far no problems at at. I'll keep it going, even though i dont like this interface etc.

(just to recap this is without reflashing to stock or MTTY since encountering lockups)
[Touch HD Windows Mobile ROM Development] makbil:
WM version doesn't make a difference. Using the same 28xx build on 2 different ROMs, I get no lockups in one ROM and consistent lockups in the other.
[Touch HD Windows Mobile ROM Development] makbil:
My serial number is: HT92HKD02537

Part number: 99HHC013-00

Unlocked

Someone may want to check the part number as well to see if they are the same (should be for HDs sold in Europe)
[Touch HD Windows Mobile ROM Development] jtf420:
S/N : HT916KD00513

P/N : 99HHC028-00 D

i bought it in Kiev Ukraine.. and most probably a branded one.. but it's already unlocked as it had russian rom on it (unofficial at that time) :)