yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] golightlygl:
I think the answer is simply that a combination of factors contribute to the lockup.

Let's wait for a day and see if the power management issues susggested solve the problem with Neo's drivers. If they do, then that may give Neo a clue to how to solve the driver problem. In the meantime, it would give us a chocie of what to sacrifice (driverpack or power management) to get a lockup-freee device.

But as I say, let's wait for a day first to see how my test progresses.
[Touch HD Windows Mobile ROM Development] makbil:
Good idea. I will also install Xanny's ROM with the drivers and compare to the same version I have now but without the drivers.

Hopefully, these tests will narrow down where the problem lies.
[Touch HD Windows Mobile ROM Development] bmer:
By "Lock" I mean it was not possible to start my pda ( after stopping it with a short push on the upper button ... usual way to stop it ...) . No light, nothing .... just one way to escape >>> open it and take the battery out and in !!! Then pda starting again (equivalent to soft reset). When I tweaked the screenlock and install S2U2 the problem seemed to vanish !!! ( by the past situation I had to open the pda at least 3 times a day !!!)
[Touch HD Windows Mobile ROM Development] bodgeman:
I have been suffering fro this "lockup" problem for a while (see previous posts in this thread) and could only be sure to avoid them by switching from Sense to Windows Default. However, 3 days ago I changed my power settings to turn off "auto adjust backlight" and have not had any problems since. I know this may be coincidental, but previous to this I was getting lockups several times a day. This is all on unmodified Xanny's 1.7b.:confused:
[Touch HD Windows Mobile ROM Development] jtf420:
i confirm too.. but llots of battery drain..

trying my luck with reg. changes and HD tweak setting
[Touch HD Windows Mobile ROM Development] makbil:
So you are saying that the system files are overwritten and can't be recovered, as opposed to new files and registry tweaks. Can you confirm this please? Xanny is thinking of making the driver pack uninstallable for those of us who have problems. From what you have said here, uninstalling will not be possible and Xanny should be made aware of this.
[Touch HD Windows Mobile ROM Development] golightlygl:
Well, Christmas morning and mnet's reg changes have not saved me from lockups (although they did drain the battery faster).

It looks like the uninstallable driverpack is the way to go. Makbil, I know your on the EVO thread (I prefer the Grid Leo) but I assume the driverpack benefits are the same. How much more sluggish is your test rom without it?
[Touch HD Windows Mobile ROM Development] ogistoev:
I think that lockup have something to do with active data connection when device goes to sleep. I use only wi-fi and turn it on-off manually and my HD locked up only once for more than week usage-when I forgot to turn off wi-fi connection and try to wake up after a few hours. (Xanny's ROM 1.7B). So maybe that's a Windows bug and should wait a new release of 6.5.3.
[Touch HD Windows Mobile ROM Development] makbil:
It's very hard to tell the difference, if there is any. EVO 1.8 without the diver pack is just as fast as EVO 1.6 or maybe faster. However, that is based on the way I use my phone, you may see some differences in the pictures and music tabs.

As for the uninstallable driver pack, NeoS2007 said it could not be uninstalled, if that is the case then there remains only 2 options:

1- Chefs can make an extra ROM without the drivers

2- NeoS2007 can modify the driver pack cab file so that it can be uninstalled.
[Touch HD Windows Mobile ROM Development] ultimatepichu:
Quite agree with this.

I got my first lock up few hours ago. I never have this before. Just now I forgot to turn off my wifi and got the lock up. Maybe it's a combination error in between the graphic driver and wifi?

I'm using XannyTech's Grid Evo 1.7c
[Touch HD Windows Mobile ROM Development] makbil:
Still, the common element seems to be the graphic driver pack.

To test this, I'm going to turn on Wi-Fi for a couple of hours to see what happens.
[Touch HD Windows Mobile ROM Development] band27:
I can be the testing variable that has flashed (Xanny 1.7-with Neo Drivers onboard) via SD storage.

Update

:

• 30 min. with wifi on while devices sleeps

Will wake after 1 hour and report results.

Progress Report

:

• turned on device with wifi in the back with absolutely no glitches
[Touch HD Windows Mobile ROM Development] makbil:
After several hours, I seem to have no problem if I leave Wi-Fi on.
[Touch HD Windows Mobile ROM Development] ultimatepichu:
you're now using rom with or without the graphic driver?
[Touch HD Windows Mobile ROM Development] band27:
Yes, that's right! Take a look at his signature.....special version 1.8 without drivers for testing purposes.
[Touch HD Windows Mobile ROM Development] makbil:
That's correct, thanks to Xanny for his cooperation. Almost 5 days now and not a single lockup or any other problem.

Xanny is considering making the video driver pack uninstallable, if that is possible.

As far as I can determine, the driver pack seems to be the common element in my lockup problem. Perhaps alone it does not cause this but combined with Manila 2.5 the lockup will occur.
[Touch HD Windows Mobile ROM Development] band27:
The other variable that I have done and I know Makbil has done as well is used Mtty to clear device. Not sure if that is a variable we want to explore.

Potential Variables

:

• graphic drivers ...vs... no graphic drivers

• flashing from pc ...vs... sd card

• cleaning device using mtty ...vs... flashing stock ...vs... none of these

What all members already do is Hard Reset at least once after flashing....I've done it twice but the above variables

are different for everyone and I'm sure there are more variables.

I have

: the drivers (Xanny 1.7 rom)...flashed via sd card...and used mtty in the past (2 flashes ago) and I have no lock ups at all.....at least so far.
[Touch HD Windows Mobile ROM Development] jtf420:
Salaam Makbil!

your opinion plz: should the XT 1.8(no neoS2007 driver pack) be made public for other lockup haunted users!

may be we'll (god forbid.. i pray) have diff results ..

p.s. reg tweak didn't work.. i still get lockups! :(
[Touch HD Windows Mobile ROM Development] makbil:
MTTY is the same as flashing a stock ROM. It does correct issues that can cause lockups but those lockups are due to other reasons. In my case, using MTTY does not help, I still get lockups if the ROM contains the driver pack.

I was also concerned about the difference between flashing from PC and from the SD card but I've talked to Fallen Spartan, who has an HD dedicated to flashing ROMs :) and probably flashes every single ROM that comes out, he doesn't think there is a significant difference between these 2 methods of flashing and I agree with him. If the method of flashing was responsible for this lockup, I should have it with all ROMs not just those that have Manila 2.5 + the driver pack.
[Touch HD Windows Mobile ROM Development] makbil:
I know that for the time being Xanny is planning to make the driver pack uninstallable in his next ROM, I'm waiting for confirmation from NeoS2007 whether this is possible or not - he already posted that it's not possible, I just want to confirm.

The decision on making the test ROM public is up to Xanny, it wouldn't be right for me to comment on that.
[Touch HD Windows Mobile ROM Development] Marne Jr:
When I had lockups it usually occured when device was hot and it usually was hot when I used wifi for more than 15 minutes ... Then wifi had association with lockups but was not the cause .. how I know it ?

Because when I got this lockup I putted my HD on refrigerator for 10 minutes and it turned back without take battery off .... and in others situations like after flashing a rom when the device was hot there allways was more chance of it got a lockup ...

But problens can be different from one to another device and maybe there are many different factor that can increase risk of a lockup from one to another and I think this is the main reason this thread still going on without a specific answer ....

Hope this post can help anyway...

Bye.
[Touch HD Windows Mobile ROM Development] band27:
Excellent and good to know that those variables mentioned can be excluded from the mystery lockup equation.
[Touch HD Windows Mobile ROM Development] bzpwhx:
Hello just my finding:

when I try to use hd tweak on newest roms 2.5 trying to put "sleep" mode off during a call it seems that it touch something else and my hd start to freeze. Not the home manila freeze just a totally black screen freeze during the sleep mode...

mmmm if I don't use hd tweak seems to run without any freeze...

:confused:
[Touch HD Windows Mobile ROM Development] makbil:
Just checked this on my test ROM. Xanny has already set all 3 call sleep mode options to disabled. Anyway, I installed HD Tweak and run it. I'll report if I get the lockup.
[Touch HD Windows Mobile ROM Development] hadryen:
Actually I need an explanation on what the lockup really is since I am still experiencing problems.

I tried Eclipse (manila 2.5) Sunrise (manila 2.1). L26THDV4, LeoStone 18 Dec, etc... with or without manila 2.5's rom and I get always the same problem.

My phone has HSPL 1.56 OliNex and i do Hard Reset once (or twice) after each rom Install, and i still get a problem.

Either

- after a while the phone stop responding and when i restart it (either by pressing the reset button or removing battery) it either do not restart (get stuck at the "smart mobility" screen... annoying, have to do a hard reset again...) or it restart directly in initiatlization mode...

- or it crash while in use (specially when using myphone or when watching/editing the contacts

It might be an issue with the PIM management, specially since they get cleared after each problem... but i don't know, i'm a newby...

so either way, i have once more to put back all contacts and mails and else, using both MyPhone and Msn messenger (yes, my main mail is hotmail, i know, it's a shame).

It is very time consuming but for the last days i had no other choices, (thanks god i'm unemployed so have plenty of time... this might be the only upside...)

And I can't put a stock rom again since the HTC website does not recognize my blackstone's serial number (WTF???) and for no reasons, I can't download the rom's on rapidshare or else because theses ****ing websites keeps on telling me that my IP already reach the maximum amount of download for the day, ****ing flatmates...)

so I'm stuck trying roms...

I'm going to try Miri's rom as there is no Neo Driver pack inside according to Makbil .

Thanks guys for all the good work anyway.

http://www.nokia.com.sg/find-products/products/nokia-1650 that looks like my next phone...
[Touch HD Windows Mobile ROM Development] Pzander:
Same error after installing stock ROM

I recall getting this error after running Android on my Blackstone:

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

BUT I also upgraded to newer 6.5.3 ROM from Miri, so can not tell which one caused the error in the first place.

I have made SEVERAL hard resets and nothing helped.

I get intermittent lockups even after restoring to stock ROM and stock SPL. But it seemed to be in combination with the latest version of S2U2 (at that time v2.21). I uninstalled it and have no power management turned on and the device have been running fine for 24 hours now (cross my fingers).

Question: Anybody else that have this problem that also have been trying out Android? Do you run S2U2?

/Patrik
[Touch HD Windows Mobile ROM Development] misa.fisa:
I had also this problem

Hello I had also this problem. On begining I get this 1x per 2 days but after 1 monts I have this problem every 20 minutes. I try everiting all roms. On end I flash original stock rom (BlackStone_HTC_WWE_EastEurope_1.56.479.0

Windows Mobile 6.1)and make test with this rom. After flashing was HD stable. But in 4-5 days I get again this type of problems. I go to warranty service with and in 2 weeks I get back HD with have new Display and New Main Board(new imei and serial nr.) Now I use Miri rom and no problem.
[Touch HD Windows Mobile ROM Development] makbil:
Check post #1 for an explanation on this lockup type.

Just a couple of points which may help you:

1- You can get stock ROM from here or here..

2- There are a number of reasons why a lockup can occur. To rule out other reasons, I suggest you first flash a stock ROM, hard reset, then install your ROM of choice, hard reset and start using. For troubleshooting purposes, it's a good idea to not restore anything from a backup and only use MS My Phone or Outlook to restore your data. Also refrain from doing any customizations until you have a chance to determine the state of the ROM.

This specific kind of lockup does not happen on M2.1 so I'm guessing that flashing a stock ROM will cure your problem.
[Touch HD Windows Mobile ROM Development] makbil:
I did try Android but as far as I know it just boots up a kernel, does not flash any NAND area. Also it would not explain why only Manila 2.5 ROMs should suffer from this lockup.

I've never used S2U2.
[Touch HD Windows Mobile ROM Development] makbil:
Your problem seems to be different, glad it's fixed. This lockup type should not have happened on a stock ROM.
[Touch HD Windows Mobile ROM Development] kostas66:
Hi makbil,

I use Xanny's 1.7 EVO and I am suffering of lockups...

Did you noticed improovements with your 1.8 without drivers version ??

I hope yes !

Merry Christmass and Happy New Year !

K

PS: After some other days of use I can confirm that there seems to be NOT a connection between lockups and blutooth on/off... but it was obvious...
[Touch HD Windows Mobile ROM Development] makbil:
The Evo 1.8 I use is not the final version but I can say that it has no lockups whatsoever, the lockup problem is cured. Also, it's probably the fastest 6.5.x ROM I've used.

Merry Christmas and a Happy New Year to you too :)
[Touch HD Windows Mobile ROM Development] kostas66:
Great !!

I hope Xanny will release it soon !!

Thanks

K

PS: Sorry, maybe this was i little off topic...
[Touch HD Windows Mobile ROM Development] Marne Jr:
--------------------------------------------------------------------------

Hi Makbil I privated messag this to you, but then I think it could be helpful to others...

On previous post we saw that we have different kind of lockups ...

When my device was in a lockup I could hear the volume sound that it releases when pressing volume button ... I could feel it short vibrate when holding long end key (to terminate data...). I could even answer a call and terminate it, but I could not see anything (black screen....).

In your kind of lockup can you hear or feel anything ?

Can you answer a call ?

Cause if we can press buttons to do some things work when in a lockup I stated that after install clean ram and rename the shortcut to it to "long_power" and put this shortcut in windows folder ... when in a lockup I can make clean ram level 3 runs by long pressing power button and restart htc sense without restart device and maybe scape from a lockup ... what do you think about that ?

I am waiting new lockup to see if it works ... but I was 12 days without it ... and I don't know when it will happen again. If someone could test it too it would be nice.

I think the best for lockups is to find a cure more than the exact cause... but of course that to find the cause may be helpful in find cure, but not necessarily it has to be in this way !!!

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

Tipically type "b" lockup ... just flash original rom and send it back to HTC they will replace main board or give you a new phone ..

I leave in Brazil and HTC do not support touch HD here .. so I have to live with this problem until I buy a HD 2 (i am waiting just to be sure that there will be no kind of lockup on it).
[Touch HD Windows Mobile ROM Development] kuwait:
There are several suggestions that I may do regarding lockups cause .

1)Communication with the SIM card fails due to dirty contacts. That I had noticed on many mobile phones and it always lead to freezing.

2)Static electricity which shortcuts some point on the touch screen.

I have following problem time to time. Touch screen stop to respond including the 4 buttons down. But the hardware buttons work. I can switch off the screen. But even after switch OFF/ON of the screen it still does not respond. It does not respond even after soft reset.

Further I had noticed (with switched off screen) a small dot on the screen that is with different color , more dark then rest surface. This is a shortcut on the touch screen which activates it permanently. Due to resistive touch screen allows only single touch the second real touch is not accepted.

When I pass my finger several times on the dot (with switched off screen) with a light pressure the dot disappears, After that when switch on the screen touch function works like usual.

However twice after above event happened I had lockup the same like described in the first post. When try to start the phone screen remains black and no one of the buttons respond including hardware buttons. It starts working after removing and putting back the battery.

So my second suggestion is that static electricity applied on the touch screen may cause the lockup.
[Touch HD Windows Mobile ROM Development] makbil:
But then I would have to ask, is Manila 2.1 immune to static electricity?

There can be a number of issues all leading to a lockup but according to what we have found out so far, the specific one we are investigating here requires Manila 2.5 AND the driver pack to be working together.
[Touch HD Windows Mobile ROM Development] makbil:
No, no and no ;)

If it is dark, I can see that the backlight has turned on but there is absolutely no response from the phone. Although the caller hears the phone ring, the phone never rings and the call is never logged.

At this point I can safely say that Xanny's ROM without Neo's driver pack is immune from the lockup problem, just as Miri's was which also does not include the driver pack.
[Touch HD Windows Mobile ROM Development] gigaboss:
I have this bug with Xanny's ROM but not with NRGZ28's which doesn't include Neo's driver pack, so I guess it has something to do with it...
[Touch HD Windows Mobile ROM Development] mnet:
It is possible that this problem might be due to running an incompatible operating system... A hard-reset only formats the NAND storage, however there are other kinds of 'memory' that the OS interacts with. For example there are registers directly on the chipset. It is possible that the 3D driver in the android build interacts incorrectly with the chipset, thereby causing some registers to get 'stuck' on an incorrect value, therefore causing a problem with the 3D driver in WinMo. The fact that it only happens on M2.5 roms is explainable by the fact that M2.5 relies much more on hardware-accelerated 3D functions, and the specific function that is causing the lockup is perhaps not used in M2.1.

This is all speculatory, but i think it warrants further investigation. Has everyone who is having these specific kind of lockups run an android build on their blackstone?
[Touch HD Windows Mobile ROM Development] hadryen:
I'm always using myphone and/or activesync.

I tried Miri's rom with manila 2.5 and so far, it's working fine (touching wood...). it might indeed be an issue on some motherboards (assuming there are various HD series...) and Neo's driver pack...

Keep you posted if I have an issue with Miri's rom but I hope not.

Thanks for the advices.
[Touch HD Windows Mobile ROM Development] jtf420:
i've used Android.. but in later stages of my Lockup story..

Lockup's started since Dutty R7 .. and at that point of time, i thought, most probably others tought too, that these is a minor bug, SR helps comeback, why bother, we're too excited with Manila 2.5 :-D

and i'm sure.. tht i've tried Android(tuxhero alpha) after having lockup's

But anyways ur point is a valid one! .. sad we don't know all command sets that work with blackstone on MTTY ..
[Touch HD Windows Mobile ROM Development] Pzander:
Take a look at the Androis thread and you will see that they have loads of problems with the backlight, loads....And in my case I still have the problems on WinMo 6.1 (not as severe but still there). of course it could be a hardware problem as well. I have contacted HTC Support and they have asked me to send in my phone as it is still on warranty. I need a replacement though :-S
[Touch HD Windows Mobile ROM Development] hadryen:
I never used any Android related roms so it's not the reason of my problems, which, so far, have stopped happening since i started using Miri's rom (ok, i did it yesterday, so it's been working for the last 36 hours...)
[Touch HD Windows Mobile ROM Development] kostas66:
The Miri's version without neos driver ?

If yes, this seems to confirm again that also other 6.5 roms without neos drivers should be ok !!!

K

PS: By the way this lockup thing is really strange... I had no lockups for a couple of days, then it happened 3 or 4 times in a day, then now (I often use clean ram, but I don't think it is relevant...) it is not happening since 3 days... who knows...
[Touch HD Windows Mobile ROM Development] makbil:
Miri does not use the driver pack. So far all the information gathered here indicates that the driver pack needs to be present for this lockup to occur.

The explanation above about Manila 2.1 not using the 3D drivers like M2.5 makes sense. The idea of some registers being stuck is an interesting idea but may be a little far fetched (I hope) as it would mean a hardware fault has actually occurred on our HDs.

Android is not a ROM that is flashed on the HD, it runs as a kernel in memory, my personal opinion is that I find it unlikely for it to cause permanent hardware damage.

Actually, I think I know just the right person to ask: Fallen Spartan, have you ever used the Android on your HD?
[Touch HD Windows Mobile ROM Development] Zydol:
Hi

I'm on Miri's rom from the last 3 day's no one lockup. Now I'm sure that the problem it's neos drivers. With Miri rom I have exactly the same settings and backups like in Xanny roms, and others.

Makbil, how You think, when Xanny can shared his rom withouth neos drivers?
[Touch HD Windows Mobile ROM Development] makbil:
I don't know. However, he is aware of the situation and I think he will find a way to present us with an option to use the ROM without the drivers.
[Touch HD Windows Mobile ROM Development] Pzander:
Take a look below. There might be a common issue with Android using the 3D engine as there is a lot of problems with getting the HD to wake up. An update: I reverted back to stock ROM and SPL and uninstalled S2U2 v 2.21. My device has been running fine for 2 days now. My idea is that something is written in persistent memory on the Touch HD when running Android orNeos driver or TouchFlo 2.6?

http://xdaforums.com/showpost.php?p=5008681&postcount=636

Quote:

Originally Posted by aavan

That's weird because on tux's build we had the android splashscreen running.

And no, I never activated 3D before, since I don't even have Touchflo or any other 3D app on my WM ROM (and nothing changed on my phone between this build and tux's one).

Well, maybe earlier versions didn't use the 3D engine, but the current does anyway.

But still I think I broke the GPU chip memory, since someone reported to me it is broken on raph too.
[Touch HD Windows Mobile ROM Development] jytan:
Makbil, I know you've experienced the lock-ups on Dutty's WM6.5 Leo Holy Grail R0 (as have I). I can't find any mention of whether the driver pack was cooked with that rom, but I didn't think it was?