yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] makbil:
I see what you mean but I only used Tux's version for a very short time and never gave it another try as it needs to mature quite a bit.

Manila 2.5 can still run without any issues provided that the driver pack is not installed (Xanny's test ROM and Miri's ROMs). So the explanation (as suggested by mnet, I think) is that Neo's Driver pack accesses some of these registers which are normally not used by Manila 2.1 and 2.5. Maybe, but we need more info on this.
[Touch HD Windows Mobile ROM Development] makbil:
Yes I did but I'm not sure if I had manually installed the drivers on Dutty's ROM or not. It was way in the beginning of this issue and I hadn't used MTTY yet :)
[Touch HD Windows Mobile ROM Development] mnet:
I have created a cab that removes cooked-in Neos drivers and installs the stock 3d driver:

http://rapidshare.com/files/326969808/mnet_blackstone_stock_3d_driver.cab
[Touch HD Windows Mobile ROM Development] golightlygl:
Just to report on my PM exchange with mnet whilst he was very kindly preparing this CAB.

I can confirm that this CAB replaces the cooked-in file libgles_cm.dll with a stock version from 14th April and adjusts the regsitry to point to the file.

I have it on test and will report in 24-hours whether Xanny's ROM with this CAB fix cures the lockups. Of course I'll leave it on longer test but my experience shows me that if this lasts 24 hours then it should last forever!
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Sorry I haven't been about lately, what with Xmas and a family tradegy it has left me with little or no time to spend.

As for your issue with lockups, as explained I do not experience them, but I have used Android, and your right it is a kernal in memory. However it can easily be removed by a hard reset and I've found no long term issues as a result from using Android. Admittently I'm not too experienced on this, but I follow the Android threads regularly. Yes, Android still has some issues and is still a work in process, but it wouldn't cause these issues. I know others users who have removed Android and also don't experience lockups, but I also know some that do experience lockups before they used Android and after they removed it.
[Touch HD Windows Mobile ROM Development] Pzander:
Lockup

My device worked until just now (for almost three days). The screen did not turn on, but pressing the power button repeatedly (many many times) got it to turn on. The strange thing was (and I have experienced this before after getting the problem) that when the screen turned on the picture was upside down and inverted. Pressing the power button twice restored it correctly.

I have no clue why my device got the lockup this time as I run on stock ROM and not S2U2. I removed the USB cable, out the device in my pocket for 10 munites and after that screen did not turn on.
[Touch HD Windows Mobile ROM Development] z_rudy:
I'm using Miri 6.5 M2.5 Version 12 (yes, haven't felt like updating yet). I'm not going to read all the 27 pages of this thread but I just want to say what happens to my phone which could mean something possibly?

I have noticed over several nights, I place my phone near my laptop's charger while it's charging and I sleep. The next day, my phone is locked up. This happens several times, so I thought I could unplug the charger for once night and see what happens. Well, no lockup.

Maybe it's from an emf from the charger or I don't know what. Are people experiencing the problem, placing their devices near other electronics devices for extended periods of time?
[Touch HD Windows Mobile ROM Development] Oemie:
Is it possible to attach your cabfile? Cause RS won't let me download..:mad:

EDIT: oke managed myself, and here it is..;)
[Touch HD Windows Mobile ROM Development] makbil:
Great. I will put this info on post #2.
[Touch HD Windows Mobile ROM Development] makbil:
All this information tells me that the reason for your lockup has to be something else. You should never get this specific lockup on a stock ROM.
[Touch HD Windows Mobile ROM Development] kostas66:
Hi all,

after the first 24hrs with a ROM without neos driver everything still ok, no lockups...

Will let you know what happens.

Happy new year to everybody !!

K
[Touch HD Windows Mobile ROM Development] band27:
Yes, true.....agreed!

...so now I still have the same rom (Xannytech 1.7c) that froze a couple of times but this time I removed the use of Manila as I'm using SPB Shell and no freezing what so ever.

Could Manila be the culprit ?
[Touch HD Windows Mobile ROM Development] Pzander:
So does this mean that there is NO way a program or ROM can write in a persistent memory?
[Touch HD Windows Mobile ROM Development] makbil:
I'm not saying that. The specific lockup we have happens with Manila 2.5 and Neo's driver pack. You can have your HD lockup due to a number of reasons not related to this and usually displaying different symptoms.
[Touch HD Windows Mobile ROM Development] makbil:
Yes but with the addition of the driver pack. I see kostas66 is also testing the same ROM as me and seems to have the same experience. It's been over a week now and I haven't had a single lockup.

So, Manila 2.5 alone does not cause a lockup.
[Touch HD Windows Mobile ROM Development] band27:
With this observation, will chefs no longer embed these 3D drivers within there future Rom's? Is the word out?... or is 1 week's worth of trying differing scenarios not enough to conclude?
[Touch HD Windows Mobile ROM Development] bodgeman:
HI mnet,

I am probably doing something wrong.. as when i try to install this cab I get a message "Installation was unsuccessful. The program or setting cannot be installed because it does not have sufficient system permissions"

could anyone assist please?
[Touch HD Windows Mobile ROM Development] kartalgurhan:
yes, same here......
[Touch HD Windows Mobile ROM Development] makbil:
Did you try after disabling Manila from settings/today ?
[Touch HD Windows Mobile ROM Development] makbil:
Obviously it's up to the chefs. The catch here is that not everyone suffers from this issue. I would hope that at least they will find a way to make them uninstallable.
[Touch HD Windows Mobile ROM Development] Zydol:
the same :(
[Touch HD Windows Mobile ROM Development] makbil:
You can't delete files that are in the ROM. This cab will only restore manually installed driver pack to stock drivers.
[Touch HD Windows Mobile ROM Development] mnet:
Sorry I made some modification to the cab I sent to golightlygl that caused it not to work... Here is a 100% working cab. You can confirm that Neos drivers are no longer used by the non-smooth concentric circle pattern in manila wallpaper_009, after installation of this cab:

http://rapidshare.com/files/326951268/mnet_blackstone_stock_3d_driver.cab

makbil is right you can't delete files in ROM, only replace them...Some dlls from Neos drivers remain in the windows folder, however they are no longer used due to registry modifications, so the above cab works for sure.

cheers
[Touch HD Windows Mobile ROM Development] Zydol:
I hope it will be ok, I tre ;) with 2.4 B Xanny's
[Touch HD Windows Mobile ROM Development] bodgeman:
That did the job - thanks for your help. After many false starts, and my own over optimism, I hope that your solution can help till the final cause and resolution is found. I like Xanny's Roms and would prefer to use these.
[Touch HD Windows Mobile ROM Development] golightlygl:
Overnight success!

OK, I have used mnet's fabulous patch to replace the driver and so far no lockups on Xanny's 2.4b ROM.

That includes the critical overnight period where I could previously guarantee a lockup. Of course I was using the original version mnet supplied me which is the one he has since re-posted. I attach it here as a CAB. I will keep it on test for a day or two.

If it keeps working as I think it will, I suggest that makbil might want to amend his first post to include the fix.

I might then get wantonly destructive and see if chainfire's HD2 graphics drivers have the same negative effect!

Many thanks to makbil for nailing down the problematic driver, Xanny for helping him prove it, mnet for the fix and everyone else for their contributions.
[Touch HD Windows Mobile ROM Development] makbil:
Thanks. Updated info in post #2.
[Touch HD Windows Mobile ROM Development] mnet:
If you are having problems with Neos drivers you could try xperia x1 drivers. x1 is practically identical internally to the blackstone (hence the compatible radios), but it comes with proper ati 3d drivers. But the dlls have to be resigned first to run on the blackstone.

Neos drivers come from slightly different devices such as the topaz and x2, hence creating incompatibilities in some configurations.
[Touch HD Windows Mobile ROM Development] makbil:
Excellent news. I've modified posts 1&2.

If we do have any new developments, I'll modify the first 2 posts as necessary but I really think that we've finally nailed down the problem. Let's see what everyone's experience is with mnet's cab installed.

I wish to thank everyone who has contributed to this thread, especially Xanny for providing a test ROM and mnet for making the cab and XDA for being here.
[Touch HD Windows Mobile ROM Development] HorstDCC:
Hello golightlygl,

Since you've pointed me to this thread I'll try and interlace my data. I've been testing daily for this specific problem for over two months so I've just read this entire thread with all my attention. (I wish I had known about this thread sooner :).)

I can confirm the assumption below. More specifically without Px Internet this exact type of lockup never occured in any test of a configured ROM that otherwise had lockups.

With the many beta's I've seen the type 'b' lockup appear and disappear on Laurentius26 ROMs. I tested with many of the contributing factors and as this thread confirms there are a few. I'm currently holding my breath because I had actually eliminated NEOS drivers as the culprits. Since L4RC7 I was quite sure we were not going to re-encouter this problem (selfish thought, because my HD seems to be sensitive to it). And with the final V4 I didn't have a single lockup in 10 days ... until yesterday (3 times). I've been redoing all my described tests today to find out whether it is a coincidence or the dreaded lockup.

As a sidenote: I've read about the suspected difference in the chipsets but I didn't read about anybody suspecting the battery controller (hardware-software combo). Since bodytemp, charge, power setting and mode all contribute tho the phenomen I wouldn't rule it out as a cause.
[Touch HD Windows Mobile ROM Development] makbil:
Thanks for your valuable input. However, your last comment still can't explain why only Manila 2.5 is effected as Manila 2.1 is immune to this lockup.

As someone who has consistently had the lockup problem with Xanny's ROMs, it tells me a lot when I've not had a single lockup with Xanny's no driver test ROM, same reported by kostas66 who is also using the test ROM.
[Touch HD Windows Mobile ROM Development] HorstDCC:
:) True, I'm assuming that we might not all have the same batteries and then it is at least a candidate for explaining why only some HDs are sensitive. In itself it isn't an explanation for the lockup.

And agin, I only make this assumption because I tentatively concluded that either we have a hardware difference (and thus different behaviour to drivers and configuration) or we are in different network situations (and then we should find a pattern).

If I would have had an opportunity to test this, I would have.

How wonderfull it would be to be certain (after all this time).
[Touch HD Windows Mobile ROM Development] golightlygl:
Well I'm satisfied that the three days I've been running with mnets uninstallation cab has cured my lockup problem.

I shall now begin experimenting with other 3D drivers to see if we can improve the performance. mnet suggested using the Xperia X1 drivers so I'll look at that and also at Chainfire's new ones.

But I am happy to declare lockup problems solved on my machine. It would be good for completeness if others can confirm if the fix has worked for them.
[Touch HD Windows Mobile ROM Development] bodgeman:
I have had no lockups since using mnets uninstallation cab! 2 days+ and also trying to replicate conditions - (leaving HD plugged in overnight, alarm set, e-mail fetch every half hour, weather auto fetch every hour) all on Xanny's 1.7b.

If this i a solution, seems so, thanks to all on this thread for cleverly working out this puzzle!:D
[Touch HD Windows Mobile ROM Development] jtf420:
Installed MNET's cab on XT EVO 1.7

after installing.. THD stopped at BootSplash.. did a soft reset. It started up fine. then Post 1st time installation customisation started. Screen alignement etc.

after the customisation was finished.. THD restarted and finally Sense started.

Had to run network configuration setup (for 3g/edge/gprs settings) .. entries in stock tab were reverted to default ones(Stock). home screen quick lincks also reset to blank.

In windows program menu.. some shortcuts had duplicated ..Comm.Manager, Calendar, Contacts and xdaShutdown.

will report back .. if any lockup occurs

Thnx Makbil,Xanny..Mnet and everybuddy else in here :)

Happy New Year well wishes to you all!
[Touch HD Windows Mobile ROM Development] makbil:
Indeed, it looks like we do have the solution.

Again, thanks to everyone who have contributed.
[Touch HD Windows Mobile ROM Development] makbil:
I have a feeling something went wrong there. Can others who used mnet's cab confirm this? It looks like you had a hard reset - sort of.

Happy New Year everyone.
[Touch HD Windows Mobile ROM Development] bodgeman:
This was not my experience. I had no noticeable difference after reboot (after installing mnets cab) except no lockups (hooray!). To be honest i don't even notice any difference in graphics performance. So all good here.

Happy new year!:D
[Touch HD Windows Mobile ROM Development] jtf420:
yes! a hard reset but of a strange character...not all progs installed on phone memory was lost, and in the start menu had links to progs installed with reg info in windows memory...

but to be true...whatever it was...it was good...it made lockups go away

this Lockup ghost will be locked up in 2009

wishing you all a year2010 free of lockups...in your phone..in mind ..in life :)
[Touch HD Windows Mobile ROM Development] Zydol:
Me too, 2 days and everything working perfect :D

But it's steel interesting, whe this lockup hapend just to some blackstone ?

Happy New Year !!!
[Touch HD Windows Mobile ROM Development] Elmao:
My Blackstone didn't lockup since i installed the MNET uninstaller. I have a horribly looking background now, but i can totally live with that.

But i would also be happy to have some alternate drivers that fix this issue.
[Touch HD Windows Mobile ROM Development] Fallen Spartan:
Just wanted to say well done to everyone who worked on this issue and found a working solution

Rick
[Touch HD Windows Mobile ROM Development] jtf420:
3 days and 2 nights.. MNET got rid of lockup bites! :)
[Touch HD Windows Mobile ROM Development] makbil:
Excellent news. So the solution is conclusive.
[Touch HD Windows Mobile ROM Development] Oemie:
The Solution is!! I am on Xanny rom again for 2 days now and no lockups. First i tried without the fix (just checking) and in the morning after one night there was the lockup again (after 10 days NRG rom without the neodrivers and without the lockups). So i installed the MNET sollution and everything is fine now.

I am very happy, thnx MNET!!
[Touch HD Windows Mobile ROM Development] Z3rO`:
Today this specific lockup (backlight on but black screen, then after a while unresponisve manila home) happened to me after I flashed Flashmores 1.6 Rev3.

It was the first time this ever happend with a rom, and it locked up multiples times already. Going to try the cab now and report back if it helped.

[edit]Wow, it really DID help. Never had any problem with neo's driverpack before. Must be rom specific. Thx guys[/edit]
[Touch HD Windows Mobile ROM Development] oluwaponmile:
This lockup have happened to me no matter what I rom I used except Miri roms (probably because D3D the driver was not cooked in.

I am currently on PhamQuang and v87 and it has happened everyday in the last three days and only way to get back to my phone will be to remove the battery.

I will give this cab a try and report back.

In the meantime, many thanks for all the people who has been working on this fix including the testers

Cheers
[Touch HD Windows Mobile ROM Development] fuithecat:
I also like to report that after installing the cab file since several days ago, I have not experience the lockup using Xanny's rom. Hurray!!

This is a great forum.
[Touch HD Windows Mobile ROM Development] makbil:
There was an interesting suggestion by blacktdm on the driver thread that I don't think has been tested here.

He thinks that the lockup occurs with the drivers in combination with animated weather at the home tab.

It would be interesting for those who still have the lockups to test this first.
[Touch HD Windows Mobile ROM Development] mnet:
I had the lockup for the first time a few days ago. The only change I made was decrease the interval on my IMAP account from 2hr to 1hr... Anyway, that prompted me to investigate the 3D drivers, and I have been using stock topaz 3D drivers for a few days now without any lockups. I will prepare a cab for these drivers if anyone want to test them.
[Touch HD Windows Mobile ROM Development] mnet:
Driver attached below. It gives good performance with manila 2.5, makes the background smooth and seems to be stable so far.

If you installed my previous blackstone driver cab then uninstall that first and soft reset before installing this.
[Touch HD Windows Mobile ROM Development] makbil:
I'm going to flash Miri's REV 17 tonight. It does not contain the video driver pack, so it will be a good opportunity to try this cab. Thanks mnet.

Edit:

It's been a day with Miri's Rev 17 and I'm convinced it works without glitches. So time to test this baby. One question, is the installation cab you have provided reversible, that is can it be uninstalled? In short, do I need to backup the original files and if so which ones.
[Touch HD Windows Mobile ROM Development] Zydol:
Hi Guys,

After 2 weeks with MNet cab, I have toonight lockup :eek:. I'm still on xanny 2,4 B. I dont install any new aplication. Strange, dont You think?
[Touch HD Windows Mobile ROM Development] dedalum:
Hi, on sturday i had the first lockup, and today the second, I have the latest lurentis rom, and of course I installed a week ago the cab of this tread, I think it's another thing what is making our hd's to lock.
[Touch HD Windows Mobile ROM Development] robwiel:
was using dutty's leo latest build, lockups started exactly after midnight 2009/2010 new years eve, switching to miri for now
[Touch HD Windows Mobile ROM Development] Elmao:
Blame me for not reading the instructions carefully, but i can tell you this is VERY important :)
[Touch HD Windows Mobile ROM Development] jacox123:
Tried the Topaz drivers today and up until now my phone has NOT locked up. Will see tomorrow if this helps. Performance seems to be good as well.
[Touch HD Windows Mobile ROM Development] golightlygl:
Thanks mnet.

I will be installing Xanny's 2.5b tonight (now without Neos drivers). When that shows stable for a few days I will try your drivers.
[Touch HD Windows Mobile ROM Development] adrimaxi:
Hi all, I got a Blackstone on Sunday Orange branded...

My first reflex was to try new rom...

So I used th flashmore 1.7 and then dush-more 2.0 with lockup issues... So I read part of this thread and flash with miri 's rom v18...

So I tried to see what was happening.

Sometime the luminosity was at the lowest level, and sometime black screen with tactile response... But since this morning I can't get it back to work.... Please help me!

At boot, no more screen so I can't hardreset or flash the rom....

Adrien
[Touch HD Windows Mobile ROM Development] NeoS:
Yes, that's strange. Is the driverpack cooked into Xanny's 2.4b?
[Touch HD Windows Mobile ROM Development] NeoS:
Could you post which cab you installed?
[Touch HD Windows Mobile ROM Development] adrimaxi:
Please help me, I am stuck the devise can't boot I only have a vibration at starting...

And a black screen...
[Touch HD Windows Mobile ROM Development] jtf420:
no lockups yet.. XT 1.8 with htc messaging
[Touch HD Windows Mobile ROM Development] makbil:
You have a different problem.

Easiest way for you to fix this is to first flash a stock ROM, then flash the ROM of your choice, the problem should be fixed unless you got a hw issue.
[Touch HD Windows Mobile ROM Development] makbil:
I've been using Mikenificents drivers for a few days now, no lockups.
[Touch HD Windows Mobile ROM Development] Zydol:
Yes, was included, now I'm on 2.5 Xanny( without your drivers neo), and I going to short holidays, we will see, what hapend. Ciao guys
[Touch HD Windows Mobile ROM Development] mnet:
Yes the cab is uninstallable.

Btw NeoS2007, perhaps the reason why the lockups happen is because d3dm localhook is set to d3dm_ati.dll in your drivers. I think localhook is supposed to point to htc_d3dm. htc_d3dm then acts as an interface to d3dm_ati.dll when needed. htc_d3dm/libgles_cm probably talk to d3dm_ati when needed.
[Touch HD Windows Mobile ROM Development] makbil:
I had a lockup immediately after installing this driver at the first reset :(

Going to keep testing for a while longer to see if it was a one off quirk.

Edit: The Topaz drivers keep causing me lockups, it has happened a few times already. I'm uninstalling them, will test for a while then try Chainfire's drivers.
[Touch HD Windows Mobile ROM Development] makbil:
So far my observation regarding the reliability of all 4 drivers is:

Chainfire and Mikenificent drivers are safe, no lockups

Neos and Topaz drivers cause a lockup on my HD if used on a Manila 2.5 ROM.
[Touch HD Windows Mobile ROM Development] Bruns86:
This problem comes up every time... My experience is that when you "Lock" your HD(longpress end-key for me or click "Lock" in the startmenu), the HD will not lockup when you wake the HD after a while... Tried this with a few roms... Latest LEO v4, Mikeficent and XannyTech and with NEOv3 drivers.. Only have a lockup if i forgot to "Lock" my HD!!

I'm now on XannyTech 2.5 with Mikeficent drivers, did not have an lockup for 4 days now!!
[Touch HD Windows Mobile ROM Development] makbil:
If you check post #2, Mikenificent and Chainfire drivers seem to be safe. The lockup only occurs with Neo's and Topaz drivers.
[Touch HD Windows Mobile ROM Development] ultimatepichu:
I doubt that. I installed it and got my 2nd lockup in my life, or, 1st lockup with mikenificent driver within 1 hour. I'll look around see if it's still coming after me.

EDIT: in XT Grid Leo 2.5d. :D
[Touch HD Windows Mobile ROM Development] balaji.admin:
I have cooked a rom without NeoS driver WM28014. Then installed Mikenificient Test driver. After 1day got the LOCKUP issue. Manila 2.5 Home screen was filled with lot of cloud moving animation. But I never had Lockup issues with NeoS driver.

/Balaji.
[Touch HD Windows Mobile ROM Development] golightlygl:
Balaji,

That does not sound like the lockup issues related to Neo's drivers that is described in detail in post 1 of this thread.

I have had Mikenificent's drivers on Xanny's 2.4b with Neo's drivers removed for several days now with no problem.
[Touch HD Windows Mobile ROM Development] makbil:
As golightlygl has said, I have also used the Mikenificent and Chainfire drivers for quite some time now without a single lockup.

If you have not had a lockup with the Neo's drivers before, your HD may also be immune to that specific issue. Perhaps it is related to the ROM you have cooked.

Please check posts #1 & 2, the results posted there have been confirmed by quite a number of users, all suffering from this specific lockup issue with the drivers.