Database Develop

Touchscreen unresponsiveness - BRICK?

Okay, so to those of us who have problems with screen ignoring/being very slow with screen taps and/or buttons, read on.
I flashed ROMeOS ROM and started having problems where I would tap on something, and it would ignore it. I would keep tapping and tapping, but nothing happened. Sometimes, even hardware buttons were ignored, about 40% of the clicks. I never had that problem with Dutty's Diamond ROM or WM6 ROMs. Issue seems to be related to latest 6.1 builds... or so it seemed at the time.
After pulling out half of my hair, reflashing all kinds of ROMs, reflashing to latest HardSPL, etc etc... I almost threw my kaiser at the wall.
First I thought it's TouchFLO, then I thought that it's the latest 6.1 ROMs.. then I thought it's related to 3.56 HardSPL.. well eliminating those factors one by one DID NOT fix the problem. Right now I went 100% to stock ROM (one it came with) and AT&T's original SPL. I started having sound problems (w/e radio I tried did not work) so I flashed Hyperdragon Wm6.1 ROM.
About 90% of the problem is phone ignoring ANY kind of touchscreen taps/drags.
About 10% of the time its the hardware buttons that have the problem - for example I push "call" (or any other softkey) button, and nothing happens, while touchscreen could be working fine at that time. In about 10 seconds, hardware buttons would start working again.
Some information that was gathered from this thread and personal research:
It looks like problem is NOT related to the following:
- POWER. Connecting phone to AC power does not solve the problem. Subjectively, it may improve it a little.
- BLUETOOTH/WIFI. Problem persists with EVERYTHING disabled and phone being in Airplane mode.
- PARTICULAR 6.1 ROM. I had this problem on ANY 6.1 ROM I tested (and I tested all the way from AT&T almost-official WM6.1).. maybe that's why they didn't release it?
- OPERA browser. Some people never had Opera and they still have this problem (please confirm this!).
- SPB/WISBAR interface software. Although having Wisbar stuff does make it a lot worse for me.. and I still have the problem without SPB or WISBAR installed.
- S2U2 screen lock. Still had the problem w/o S2U2 installed.
- iGo 2006 or iGo 8. Many users with this problem never used iGo.
Problem MAY be related to the following (needs more research, please help):
- Original SPL versus HARDSPL 3.XX
- WM6.0 versus WM6.1 (I don't think I had any problems running original AT&T 6.0 ROM, but I did have sound (radio) problems, so had to flash 6.1). Several users report that WM6.0 is immune to this problem.
- A combination of running WM6.1 with latest HardSPL?
- Custom ROM VS Original ROM. Perhaps problem is in the tweaks to the registry.
- Simple things like overtime connection weakening in touchscreen connection to the mainboard. Whoever can open a Kaiser could try to replug/clean it and report back to us.
- Radio version. Should be easy to test, just need to reflash all kinds of older radios and see if problem persists.
Please make sure that you test your phone with some touchscreen intensive games/software a lot for AT LEAST 3-4 days. I had it happen several times where it would be fine after reflash for about a day or so, and then it would come back in full force.
BRICK?
In my case, running HTC WM6.0 ROM with HTC SPL DID NOT fix the problem, I can even say it made it worse. Touchscreen would respond to about 10% of the screen taps. Tap pressure doesn't make any difference.
Also, running AT&T stock shipped ROM with stock shipped radio and SPL did not fix it. I guess at this point, nothing will. Waiting for replacement tilt.
Hope nobody else will get it as bad as I did. All I can say is... make those relfashes count.

Hmm isn't Touch Flo one of the cool things with the Kaiser??? How do you navigate in programs now it's disabeled?

DarkDvr said:
Okay, so to those of us who have problems with screen ignoring/being very slow with screen taps - I think I've found a fix. Here's a little background:
I flashed ROMeOS ROM and started having problems where I would tap on something, and it would ignore it. I would keep tapping and tapping, but nothing happened. Sometimes, even hardware buttons were ignored, about 40% of the clicks. I never had that problem with Dutty's Diamond ROM or WM6 ROMs. Issue seems to be related only to latest 6.1 builds.
After pulling out half of my hair, reflashing all kinds of ROMs, reflashing to latest HardSPL, etc etc... I almost threw my kaiser at the wall.
So if you have similar problems - try using Shnaps' Advanced Config to disable the TouchFLO altogether.
Another thing that I've used is PocketMechanic to clean up the notification queue. After fresh install of HypreDragon (latest as of Aug 5), I had 46 duplicate notifications. Removing those seemed to ease the problem, but NOT fix it. Disabling TouchFLO seemed to finally fix it.
I hope this helps somebody. I'll update this thread if I keep having this problem..
Click to expand...
Click to collapse
Thanks for the head's up! I'll definately try that tomorrow (danish time).

Foxhunter123 said:
Hmm isn't Touch Flo one of the cool things with the Kaiser??? How do you navigate in programs now it's disabeled?
Click to expand...
Click to collapse
Never really caled for it, I use my hardware buttons (D-pad) to scroll, I find TouchFLO to be too unreliable... maybe it's just me, but nothing beats a hardware button which you actually "PUSH".

spip72 said:
Thanks for the head's up! I'll definately try that tomorrow (danish time).
Click to expand...
Click to collapse
Do you have the same problem?

Hello,
First off thak you for the post. Ive got two identical Tilts both with the exact same radio/boot/roms. One has this issue and the other doesnt. I will be disabling it on the one havong the issue and report back! Thanks much!!!

I was also having this problem. my biggest complaint was my keyboard was all over the place. Sometimes it wouldnt see key strokes at all, other times one key hit would register as 3 or 4.
Sent a few test messages and This seems to have helped.
THANK YOU!!!
My Kaiser was getting close to being flashed back to a WM6 rom or quite possibly embedded in a wall.

where do you find cab for touchflo? I was looking for that but could not find it.

tamkhanh said:
where do you find cab for touchflo? I was looking for that but could not find it.
Click to expand...
Click to collapse
seek and you shall find.
It's all over the place.

Try playing around with the TouchFLO sensitivity options in KaiserTweak
i upgraded to official 6.1 about two weeks ago...
i recently started having the "missed taps" problem...
i have a feeling that KaiserTweak has something to do with the issue...if memory serves, i don't remember experiencing the issue BEFORE i played with the "TouchFLO->Sensitivity" and "TouchFLO->Finger Pressure" options...i just launched KaiserTweak right now and its showing those values as set to defaults where as i could've sworn i changed them to the advised settings a day or two ago approximately when i started experiencing the issue...just a point to clarify, i was only playing around for no particular reason and my taps were not problematic before
i've just changed them to the advised settings and did a soft reset to see if these are the kind of settings that are forgotten after a soft reset...but they stuck...so i'm gonna observe this for a couple of days with the advised settings effective and see if they have reverted to defaults on first sight of the issue...i'll report back here if that happens because that would be a pretty strong correlation...almost enough to prove cause and effect

Well, problem is, last time I've used KaiserTweak was like a year ago, so my touchscreen problems cannot be linked to KaiserTweak. I don't even have it on my tilt.
Also, it's definitelly not a touchscreen itself, since this problem is application-dependent. Once again, S2U2 and Opera are immune to this problem. Windows' build-in apps (file explorer, bottom bar, etc) all suffer from it.

I've noticed this too, but I've found a slightly longer tap seems to make things reliable for me.. Instead of a quick 'jab' if I sort of touch it, it seems to be better.
and keyboard too I've noticed.. I mostly notice it with the hard keys rather than the keyboard, but I don't use the keyboard a lot.
I'll try looking for duplicate notifications, what else will do that besides MemMaid? I might reinstall it, it was handy. I previously found phoneAlarm would grow notifications over time, I suppose I need to watch for that anyway.

khaytsus said:
I've noticed this too, but I've found a slightly longer tap seems to make things reliable for me.. Instead of a quick 'jab' if I sort of touch it, it seems to be better.
Click to expand...
Click to collapse
True, if I keep pushing on the screen button, in about 5 seconds it will be clicked. But that's ridiculous, i gotta say.
I'll try looking for duplicate notifications, what else will do that besides MemMaid?
Click to expand...
Click to collapse
I use PocketMechanic - good stuff. Has lots of useful functions, including notification queue cleanup and analysis.

Just had another "seizure" - touchscreen would not respond AT ALL for several minutes. No matter what or how I tap - complete ignore.
After couple of minutes it started working again.
Interesting that S2U2 worked fine. Seems that windows just chooses to ignore touchscreen input.

I'm forced to return to WM6.0 ROM...
Please, anybody look into this.. phone is becoming to be unusable - I can't even enter a phone number.

DarkDvr said:
Do you have the same problem?
Click to expand...
Click to collapse
Yeah it's really bad here. I've tried all sorts of tricks, including:
Re-install 6.1
Re-install 6.1 with the recent radio update found on the e-club
Install SPL 3.56
Disable HTC today screen
Kaisertweaks - tweaks on and off
Disable radio completely (seems to help, but makes the device useless)
Disable activesync
Disable quickgps
For now, I've done 2 things that seems to help:
- Disable the HTC task manager - improves the responsiveness
- Kill the MSTLI.EXE process - improves on the number of freezes
But I still experience freezes, and it's really getting to me. I need a responsive device, not this c****

ASCIIker said:
i upgraded to official 6.1 about two weeks ago...
i recently started having the "missed taps" problem...
i have a feeling that KaiserTweak has something to do with the issue...if memory serves, i don't remember experiencing the issue BEFORE i played with the "TouchFLO->Sensitivity" and "TouchFLO->Finger Pressure" options...i just launched KaiserTweak right now and its showing those values as set to defaults where as i could've sworn i changed them to the advised settings a day or two ago approximately when i started experiencing the issue...just a point to clarify, i was only playing around for no particular reason and my taps were not problematic before
i've just changed them to the advised settings and did a soft reset to see if these are the kind of settings that are forgotten after a soft reset...but they stuck...so i'm gonna observe this for a couple of days with the advised settings effective and see if they have reverted to defaults on first sight of the issue...i'll report back here if that happens because that would be a pretty strong correlation...almost enough to prove cause and effect
Click to expand...
Click to collapse
My device is currently without kaisertweaks, and I still have the freezing issues.

DarkDvr said:
Well, problem is, last time I've used KaiserTweak was like a year ago, so my touchscreen problems cannot be linked to KaiserTweak. I don't even have it on my tilt.
Also, it's definitelly not a touchscreen itself, since this problem is application-dependent. Once again, S2U2 and Opera are immune to this problem. Windows' build-in apps (file explorer, bottom bar, etc) all suffer from it.
Click to expand...
Click to collapse
I concur, it is application specific. I tried to run the "Task manager" from Fdcsoft to see if it was related to a process eating up all the CPU. But the problem doesn't occur while the application is focused.

DarkDvr said:
Never really caled for it, I use my hardware buttons (D-pad) to scroll, I find TouchFLO to be too unreliable... maybe it's just me, but nothing beats a hardware button which you actually "PUSH".
Click to expand...
Click to collapse
TouchFlo is way too unreliable to me too.

DarkDvr said:
True, if I keep pushing on the screen button, in about 5 seconds it will be clicked. But that's ridiculous, i gotta say.
I use PocketMechanic - good stuff. Has lots of useful functions, including notification queue cleanup and analysis.
Click to expand...
Click to collapse
Oh wow, not a LONG PRESS, literally a 'touch' vs a 'tap'. What you describe would be seriously annoying.
Thanks for the suggestion, I'll look at it

Is there any "safe mode" for HTC Diamond?

Hi guys
I did a mistake and I increased the cash size of my Diamond too much. So, when I turn it on, it gets stuck at the green "windows page" (FLO3D does not start). So is there any "safe mode" so I can fix the registry without flashing the whole thing?

I have installed SBSH iLauncher and selected "always" safe mode prompt whenever soft boot. So far each time safe mode function well until I installed Microsoft Reader v2.4.1 few days ago. The device cannot boot up and finally display a screen saying something like I might have shut down the device wrongly or installed some software not compatible. I am forced to hard reset the device and installed everything again. The Monocube Safe Mode v2.x still cannot work in WM6.1 device. Same thing happen to Spb Pocket Plus since it is using the same Safe Mode. I am afraid there is only SBSH iLauncher offers safe mode, but it still cannot prevent my device from poor installation. Perhaps it might help not to load certain Today Plugin only when the safe mode prompt. For some scenario the device just cannot boot up the safe mode and there is no other alternative but to hard reset.

What do you mean by safemode????
There is no safemode in WM6. Hard reset and do it right the next time.
Cheers!

sensorama said:
What do you mean by safemode????
There is no safemode in WM6. Hard reset and do it right the next time.
Cheers!
Click to expand...
Click to collapse
SBSH´s iLauncher as well as SPB´s PocketPlus DO provide an option for a safe mode on the WM platform......they do this by not loading today plug-ins and other certain modules, that can mess up your OS....
I think, there´s even a very good article about it in the WIKI of this forum. However, SPB´s products are still NOT oficially supporting WM6.1......

michi123 said:
SPB´s products are still NOT oficially supporting WM6.1......
Click to expand...
Click to collapse
That said, I can confirm that the safe-mode function of SPB Pocket Plus does work fine on the Diamond.
To the OP, as discussed there are safe-mode programs available, however they require installing before you need them...
Mathew

sensorama said:
Hard reset and do it right the next time.
Click to expand...
Click to collapse
+1
Although, as posted above, there is a way....
More interesting though, is what do you do when you've f*cked your device to the point it won't boot up, and you don't already have those programs installed? A way to edit the registry offline while the device is bricked would be nice... Like the PSP has the battery hack, a similar thing here would be nice. After all, the Diamond didn't come free, in fact there are quite pricey $$$, and there are many other things I would prefer to use as a paperweight before the Diamond.
I wonder if the ROM update software could be modified to allow editing the registry? I don't know enough about the way in which it functions internally, but someone here surely does. If it could, you could obviously reverse harmful changes and save yourself from hard-resetting and losing all those settings you took days to complete to perfection... Then you could relax a little more.. IF the IPL and SPL are working then you should be able to do anything within reason, am I right?

salada2k said:
+1
Although, as posted above, there is a way....
More interesting though, is what do you do when you've f*cked your device to the point it won't boot up, and you don't already have those programs installed? A way to edit the registry offline while the device is bricked would be nice... Like the PSP has the battery hack, a similar thing here would be nice. After all, the Diamond didn't come free, in fact there are quite pricey $$$, and there are many other things I would prefer to use as a paperweight before the Diamond.
I wonder if the ROM update software could be modified to allow editing the registry? I don't know enough about the way in which it functions internally, but someone here surely does. If it could, you could obviously reverse harmful changes and save yourself from hard-resetting and losing all those settings you took days to complete to perfection... Then you could relax a little more.. IF the IPL and SPL are working then you should be able to do anything within reason, am I right?
Click to expand...
Click to collapse
Yea, see what you are saying. A kinda off-line regedit would be nice.
Well the future will tell. then again... its not that big hustle to reinstall your pda/diamond/whatever.... so im not that bothered.
cherrs!!!!

sensorama said:
What do you mean by safemode????
There is no safemode in WM6. Hard reset and do it right the next time.
Cheers!
Click to expand...
Click to collapse
You don't seem to have read the sticky thread on reading the available information before asking / stating something... I've published several articles on Safe Mode. The Wiki even has a dedicated category at http://wiki.xda-developers.com/index.php?pagename=Systems programs, Safe Mode booting etc on safe mode apps...

michi123 said:
I think, there´s even a very good article about it in the WIKI of this forum.
Click to expand...
Click to collapse
Thanks

i also got stuck on the boot screen after a faulty aplication.
but after removing the sim , it went ok and i could uninstall the aplication.
worth the try

yep, recommend hard reset. spb pocket plus safemode works fine on touch pro

I have installed this piece of crap on my HTC Diamond (Blackberry connect WM6 pro 4.0.0.90) and now its stuck on boot screen (HTC logo).Is there ANY WAY to make htc working without hard reset?

Or,is there any way to save my personal data (contacts,photos,etc)and after that to do hard reset?

safe Mode for windows mobile
There is a way to restart in safe mode.You have to install SPB Pocket Plus for that.

Xperia Boot problems?

Hi guys, I have had my Xperia a few days now, it's a Vodafone that I hae flashed the Generic UK software to (without HardSPL) it seems to work ok but I am having a few problems. First of all, whether or not the phone will boot is hit and miss, it will get to the today screen and lock up as soon as the clock on the today screen loads. Hitting the reset switch under the cover will reboot it and it will generally boot fine, usually on every second boot.
Another problem I have is that Shell32.exe crashes a lot as does explorer.exe Shell32.exe seems to crash when installing and uninstalling applications, it does not always happen but it's happened a few times so far and is becoming irritating.
I am going to reinstall the firmware image and leave it a day or two without installing any apps to see if the problem is resolved. If anyone has any posible ideas I would appreciate it. Thanks.
Edit: I have renamed thread to remove the reference to boot problem with memory card inserted because after having removed the memory card the problem still persists so I gues it's unrelated.

Shell32.exe error
I also am having issue with shell32.exe crashing, the problem is repeatable everytime I go into the today screen options, as soon as I exit, regardles of which panel I went in from, shell32,exe crashes and I have to reboot the phone. Sometimes the only way to do so is to remove the battery. Any changes that I have made in the today screen do show up after the reboot. This is really annoying me now as shell32.exe is an important system process. Any thoughts, or shall I just hard reset.

R2AA
I'd make sure you're updated to the GENERIC UK R2AA ROM, if you're already on it, get a new copy of it from here, reformat your mem card and flash the phone again.
I seem to be OK now and not getting the shell32.exe crash anymore. Still having various other problems with it stopping responding (barely anything installed, and nothing really running) but not much more I can do, just learning to deal with it because i can't do with the stress of worrying about it. It's Windows, so expect it to suck.

i was on my R1A, had this problem, Hard reset it and the problem still exist...
Upgraded to the official R2AA10 and guess what? the problem is still there....
What is it that actually causing this problem? im planning on selling my X1 because this problem is so irritating....

Strange
mr_sheen said:
i was on my R1A, had this problem, Hard reset it and the problem still exist...
Upgraded to the official R2AA10 and guess what? the problem is still there....
What is it that actually causing this problem? im planning on selling my X1 because this problem is so irritating....
Click to expand...
Click to collapse
Strangely, I stoppped having this problem a long time ago. I ran on R2A and R3A for a long time without any trouble now, I think it was due to a common program we were having installed because I use different programs than I used to and I havn't seen it happen since I last posted about having the problem.
Stick with a fresh install and see how it goes, install your apps slowly until it doesn't happen anymore.
I can't remember the exact programs I used to use but I have a feeling it was related to homescreen plugins or some such.
Let me know what programs you use maybe we can find a common denominator.

alias_neo said:
Strangely, I stoppped having this problem a long time ago. I ran on R2A and R3A for a long time without any trouble now, I think it was due to a common program we were having installed because I use different programs than I used to and I havn't seen it happen since I last posted about having the problem.
Stick with a fresh install and see how it goes, install your apps slowly until it doesn't happen anymore.
I can't remember the exact programs I used to use but I have a feeling it was related to homescreen plugins or some such.
Let me know what programs you use maybe we can find a common denominator.
Click to expand...
Click to collapse
Okay, so after hard reset, i always install my program again one by one...
Strangely, the error always happen the FIRST time i install any program that uses today plugin...at first i thought it was SPB Wireless, then after another hard reset i installed Beejive, and the same error occurs...
Now mine is a little bit stable, mainly because i dont touch the today setting anymore....i (forcefully, despite the error ) installed Pocket digital clock, SPB Pocket Plus, and SPB wireless....
Its been fine for the last 2 days...without touching any of the today settings...
What is it that actually causing the problem? so strange....

mr_sheen said:
Okay, so after hard reset, i always install my program again one by one...
Strangely, the error always happen the FIRST time i install any program that uses today plugin...at first i thought it was SPB Wireless, then after another hard reset i installed Beejive, and the same error occurs...
Now mine is a little bit stable, mainly because i dont touch the today setting anymore....i (forcefully, despite the error ) installed Pocket digital clock, SPB Pocket Plus, and SPB wireless....
Its been fine for the last 2 days...without touching any of the today settings...
What is it that actually causing the problem? so strange....
Click to expand...
Click to collapse
Well, I never used SPB wireless when i had that problem, but i did use Beejive, Vito Sound Explorer (has a today plugin) HomeScreen++ and Wisbar Advance Desktop (saw a few crashes with this). Saw the problems a lot back then.
When I only ran Homescreen++ I never saw the problem.
I am running 6.5 now so i can't test it for you I'm afraid to find the exact problem, but I'd certainly keep hold of your Xperia because it's definately just caused by a 3rd party app/plugin.

alias_neo said:
Well, I never used SPB wireless when i had that problem, but i did use Beejive, Vito Sound Explorer (has a today plugin) HomeScreen++ and Wisbar Advance Desktop (saw a few crashes with this). Saw the problems a lot back then.
When I only ran Homescreen++ I never saw the problem.
I am running 6.5 now so i can't test it for you I'm afraid to find the exact problem, but I'd certainly keep hold of your Xperia because it's definately just caused by a 3rd party app/plugin.
Click to expand...
Click to collapse
the weird thing is, i ran all my program above for about 4 months on my R1A and no problem occurred....everything was good.
Then i tried to install SPB phone suite, but the installation stopped at 3/4 because the software wasnt signed or something like that (strange, i got it from SPB site), and it just left me some today plugin but withoun any name...it was blank....my today plugin order was in a mess too...i soft reset, it was okay....but i soft reset it again later that day and thats when the problem happened...
I found it strange that it still happens after hard reset and even after Rom change...especially to ANY program that uses today plugin....weird...

Try using R2A_10 or later, I never had any problems from then on, I'm running gtrabs R3A/6.5 atm, although it hasa bunch oof problemsof its own.

alias_neo said:
Try using R2A_10 or later, I never had any problems from then on, I'm running gtrabs R3A/6.5 atm, although it hasa bunch oof problemsof its own.
Click to expand...
Click to collapse
im using the official R2A10 at the moment....the problem still exist the first time i put all my software back....
But it seems stable now for the last 2 days...if the problem occurs again, i'll post it up here,,,

Re: PARANOIDANDROID 3.00 | Only Rom on Android capable of Hybrid mode 02/11
Edit: XDA freak out

decalex said:
ya, that's not gonna happen, BUT, xposed framework mod works on TW based ROMs, and u could always go that route if u want per app DPI. I'm a big fan of PA's implementation though. Xposed works great but a little more tedious.
Click to expand...
Click to collapse
How did this got here?

Lmao, I have noo idea.

Diamond is running extremely slow - TouchFlo won't start

Suddenly my Sprint HTC Touch Diamond is running extremely slow. TouchFlo 3D will not start. Various things runs extremely slowly like tapping on the start menu takes like 20-30 seconds to come up.
Rebooted several times. Turned off TouchFlo. Phone's still as slow as molasses?
What to do? Flash the ROM? If so, which I'd hate to do, where do I get the original Sprint based ROM?
Update: For some reason \Windows\manilla.exe never gets run. If I run it by hand then Touch Flo comes up. But it's still kinda slow.
Who/What starts manilla.exe?

Simply do a hard reset, this will reset everything back to original rom as in a factory reset.
http://www.hardreset.eu/htc_touch_diamond_hard_reset_soft_reset_en.html

That would be wonderful if I didn't customize things. But I have - heavily. And I'll need to reinstall all my apps. I was hoping not to do that...

defaria said:
That would be wonderful if I didn't customize things. But I have - heavily. And I'll need to reinstall all my apps. I was hoping not to do that...
Click to expand...
Click to collapse
But this is the most likely reason it is running slowly... Needs a hard reset and start again - and be judicious with what you re-install.

Before doing a hard reset, have you tried a soft reset??
A soft reset for heavy users is almost required dally in some cases to release the memory from being attached to programs and the OS which is consider to be called "Memory Leaks." A typical problem for all 6.1 Roms.
This slow and sometimes unresponsive behaviour was what also experience as well. There are programs that help memory find it's home but sometimes a good old fashion soft reset is what's needed.
Last thing: Make sure that when you have flashed a new ROM to ALWAYS do a HARD RESET immediately. Not sure if you followed that procedure in your last flash. IF not, I'm afraid a soft reset might not be sufficient to remedy this issue for you.

Riker88 said:
But this is the most likely reason it is running slowly... Needs a hard reset and start again - and be judicious with what you re-install.
Click to expand...
Click to collapse
This is exactly what I was trying to avoid. A computer doesn't suddenly go from running OK to dog slow when you have not changed anything (I only rebooted/soft reset). The running of manilla.exe doesn't suddenly disappear.
Everything I install I install for a reason.

band27 said:
Before doing a hard reset, have you tried a soft reset??
Click to expand...
Click to collapse
Daily! If not hourly. WinMo is not known for being stable.
A soft reset for heavy users is almost required dally in some cases to release the memory from being attached to programs and the OS which is consider to be called "Memory Leaks." A typical problem for all 6.1 Roms.
Click to expand...
Click to collapse
I'm well versed in what memory leaks are. 'Round here we call them bugs. Being in the business for some 30 years now I can tell you that having to reboot an OS periodically is a sign of an extremely buggy OS. Unfortunately that's what WinMo is.
This slow and sometimes unresponsive behaviour was what also experience as well. There are programs that help memory find it's home but sometimes a good old fashion soft reset is what's needed.
Click to expand...
Click to collapse
There's a big difference between being slow and being suddenly SLOOOOOOOOOWWWWW.
Last thing: Make sure that when you have flashed a new ROM to ALWAYS do a HARD RESET immediately. Not sure if you followed that procedure in your last flash. IF not, I'm afraid a soft reset might not be sufficient to remedy this issue for you.
Click to expand...
Click to collapse
I've yet to flash this phone. I was hoping to avoid it. There are so many ROMs to choose from, some better than others. And I'm not looking forward to having to reapply all my customizations...

i get a problem like this occasionally after a restart. I need to hit the green dial key to get it to ask my PIN. after i enter my pin everything is back to normal.
just an idea

sprite backup
What you should do is when you hard-reset the phone and you have installed all your must-have apps (and the phone still runs smoothly) use Sprite Backup to make an image. This way when things go bad again, just restore the Sprite image to that wonderful time when everything still worked smoothly and you won't have to install all the apps again. Only the apps you installed after the image ofcourse... depends how often you backup
Works like a charm.
Be careful though, when you flash another rom, you CAN'T use the Sprite image anymore!! You have to make a new image then.
Hope this helps.

[REF] "LOCKUP" issue on HD

** Please check post #2 first. It looks like we have found a solution. **​
We don't reprimand anyone for asking questions, so feel free to ask (preferably after reading or searching the thread) if you have doubts.​
I'm starting this thread in the hope that we can determine and find a cure for the lockup issue some of us have been dealing with in the later Manila 2.5 version ROMs.
This is something I've been trying to deal with for some time now and it seems more widespread than people realize from the number of posts by users who have had this issue.
Let me explain my definition of "lockup":
1- It always happens when the device is in sleep mode, never while it's used.
2- Never happens with stock ROM or Manila 2.1, only on Manila 2.5.
3- It's random, could happen any time of the day, in any frequency.
4- It's more likely to happen with some ROMs than others, leading me to believe it is related to the ingredients used in the kitchen (that is: operating system/software ) The "lockups" will start within the first 24 hours and possibly become more frequent over time.
5- It's highly unlikely that any sw installation is responsible for this (NeoS2007_Driverpack_3 excluded, I haven't done sufficient testing with it)
6- When the "lockup" occurs, the screen lights up (you can see it does in the dark) but the device is unresponsive. If you wait for a while, the home screen appears but the device is unresponsive. The only way out is taking the battery out or doing a soft reset.
7- Using MTTY or flashing a stock ROM may help fix other problems but does not help for this specific case, the "lockup" will still occur.
8- It's entirely possible (but hard to determine) that hardware may be an issue here. The fact that some people always have this problem and others don't, may be due to different hardware revisions, if there are any.
9- This problem is very specific and never leads to a hard reset.
10- When the lockup has occurred, people calling may hear the phone ringing but the HD remains unresponsive and there is no call logged, so at least the radio section is working.
Please post you experience with this issue, including the ROM involved, and any action you have taken that leads to a solution.
Please also mention whether you flash using SD card or from the PC. Since none of my SD cards work, I always have to flash using my PC, so that is something I need more info on.

Please read this post to be uptodate on the latest situation with this issue
Quite a number of new sys versions seem to be causing lockups on most HDs. This is a sys problem and is not related to the lockup with the video drivers but is related to the OS version. If you are using a ROM with a new sys version and are having lockups, just switch to another ROM with a different sys version.​
As the number of pages in the thread started to increase, I want to post a summary of our findings here.
As stated numerous times, not everyone suffers from this problem but the number of people who do suffer seems to be much more than I originally thought.
Please remember that we are talking about a very specific kind of lockup here as explained in post #1.
So far, our findings indicate that it is a combination of conditions that cause this issue. If Manila 2.5 and the Neo's Driver pack are used together, this lockup will occur on those HDs that are prone to this issue.
mnet has prepared a cab that effectively deletes the driver pack and restores stock drivers. If you are having this problem on a Manila 2.5 ROM, you should try this. Needless to say, before trying this, you should have already tried the recommended cures, like flashing a stock ROM or using MTTY.
You can't actually delete the files cooked in the ROM, only replace them...Some dlls from Neos drivers remain in the windows folder, however they are no longer used due to registry modifications.
Several users who have been suffering from this lockup have confirmed that after applying mnet's cab to uninstall the Neo's Driver Pack, the lockups have stopped. So, it's a definite cure.
Cab to remove Neo's Driver Pack.
Also, please check this post. It may be worth giving it a try if you have unexplained lockups.
The Topaz D3DM drivers also seem to be causing lockups, confirmed by other users.
Mikenificent BlackStone TestDrivers seem to be safe. I tested for a few days and no lockups occurred.

sounds like an app conflict, I have run WM6.5.x for many weeks now without any lockups.

homer285 said:
sounds like an app conflict, I have run WM6.5.x for many weeks now without any lockups.
Click to expand...
Click to collapse
Can also agree with Homer above. Haven't experienced this lockup mate and I've tried nearly all wm6.5 manila 2.5 roms out there.
If others could post their experiences it would maybe help narrow this issue down. Does this happen on a bare rom or after certain apps are installed?

Fallen Spartan said:
Can also agree with Homer above. Haven't experienced this lockup mate and I've tried nearly all wm6.5 manila 2.5 roms out there.
If others could post their experiences it would maybe help narrow this issue down. Does this happen on a bare rom or after certain apps are installed?
Click to expand...
Click to collapse
I was experiencing this only on 23xxx, 28xxx etc builds and I flashed a ship ROM and I have yet to have it happen again. Of course I'm on new builds since then too.
It is a very puzzling issue though and I hope we can bring it to light.

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.

bobsbbq said:
I was experiencing this only on 23xxx, 28xxx etc builds and I flashed a ship ROM and I have yet to have it happen again. Of course I'm on new builds since then too.
It is a very puzzling issue though and I hope we can bring it to light.
Click to expand...
Click to collapse
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

homer285 said:
sounds like an app conflict, I have run WM6.5.x for many weeks now without any lockups.
Click to expand...
Click to collapse
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.

Fallen Spartan said:
Does this happen on a bare rom or after certain apps are installed?
Click to expand...
Click to collapse
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).

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)

termignoni said:
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..
Click to expand...
Click to collapse
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.

makbil said:
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.
Click to expand...
Click to collapse
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..

termignoni said:
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)..
Click to expand...
Click to collapse
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.

makbil said:
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.
Click to expand...
Click to collapse
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..

termignoni said:
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..
Click to expand...
Click to collapse
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.

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://forum.xda-developers.com/showthread.php?t=540290

bodgeman said:
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.
Click to expand...
Click to collapse
any reference to this "MTTY thing" u did? i might give a try 1st..

bodgeman said:
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.
Click to expand...
Click to collapse
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?

termignoni said:
any reference to this "MTTY thing" u did? i might give a try 1st..
Click to expand...
Click to collapse
Here . My results are on page 50.

makbil said:
Here . My results are on page 50.
Click to expand...
Click to collapse
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)