Database Develop

Tilt Touch Screen failing after loading Dutts latest ROM

Hey there,
A bit new, just finished loading Duttys WM6.1.5.2.1972_Hybrid_V2_1_65.14.06[CubeV2] Rom. Seems great at first. Had to download Goodlink for the corporate stuff. It works fine for a bit, but as soon as an Outlook reminder pops up, suddenly the touch screen is completely dead. Tried all buttons etc on the front. The keyboard works and the buttons can be used as the menu choices, but it took a hard reset to fix it. Which then I had to reload Goodlink and it happened again.
Any patches or settings anyone can think of? Goodllink is the only add in I put in. Any other ROM's recommended perhaps? Thanks all!

Borg7of9 said:
Hey there,
A bit new, just finished loading Duttys WM6.1.5.2.1972_Hybrid_V2_1_65.14.06[CubeV2] Rom. Seems great at first. Had to download Goodlink for the corporate stuff. It works fine for a bit, but as soon as an Outlook reminder pops up, suddenly the touch screen is completely dead. Tried all buttons etc on the front. The keyboard works and the buttons can be used as the menu choices, but it took a hard reset to fix it. Which then I had to reload Goodlink and it happened again.
Any patches or settings anyone can think of? Goodllink is the only add in I put in. Any other ROM's recommended perhaps? Thanks all!
Click to expand...
Click to collapse
I notice this is your fisrt post so welcome. There is a great deal of helpful experience here to help but it does certainly pay to pose questions in the correct place. If you ever have a question about a ROM then post your question in that area and you will be far more likely to get the helpful anser that you want. People are also sometimes too quick to 'Flame' people making such errors - but not me so hopefully this will help:
I am on that same ROM and have noticed that after initial ROM installation that the touch screen is initially 'prone' to what appear to be freezes. In fact I noticed on my device that I had to press quite hard to get any interaction with the screen and sometimes it did not respond.
Cannot say why but this has now completely gone and did so with each ROM install. It took a few soft resets to see the screen working correctly but it is great now! So it may not be your additional software. Just try sticking with it for longer and some soft resets. You might also try tweaking the sensitivity of the screen.
Suggest you search within the correct area and you'll see few comments about this kind of thing (but not many).
Regards

Thanks Tony. My first time posting so wasnt sure where to put it. Have done all you suggested. Worse case, back to the ATT rom, oh well. Will search also and try posting in the right location. Thanks!

Borg7of9 said:
Thanks Tony. My first time posting so wasnt sure where to put it. Have done all you suggested. Worse case, back to the ATT rom, oh well. Will search also and try posting in the right location. Thanks!
Click to expand...
Click to collapse
i just reviewed the software online and i can make several predictions why this is conflicting with the rom. 1) htc home
go to settings>personal>today>items>and uncheck htc home.
let me know if goodlink works thereafter if not I have a few more predictions to why it doesn't operate correctly.
Oh, and i just noticed you had a cube version, which could also be conflicting.

Thanks for the input Red. Tried that to no avail. Even tried soft reset afterwards. It is dead before goodlink even starts. BTW, this will be worth a Pint or two if you get me working.
I thought it might be the Cube version so after several hard resets(storage clearing), I went ahead and flashed it with Dutty's Non Cube version just to see if that was it and it wasn't. I tried tuning the touch screen too, bumping sensitivity up to 200, didnt help either. Tried loading the tweaks program, but nothing there either helped(actually cant even use it when frozen). The keypad, buttons all work, but the touch screen is dead. Hard reset fixes it, loading Goodlink, which I have to have for its a corp phone, kills the touch screen. I believe it worked for a few minutes, then locked up. I need to reverify that just to make sure it didnt happen immediately with Goodlink install. Very strange.

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

AT&T Tilt 6.1 Lags

Since upgrading to the AT&T 6.1 ROM I have 2 recurring issues. First, the device seems to have "busy" times when it will not respond to screen taps. If I turn off the phone radio the problem goes away. Second, the on/off/sleep button on the side will occasionaly turn on the phone from sleep for less than the second. The screen flashes and then back off. The next press of the button will turn the phone on.
I have seen these problems posted on other forums but not here and have not seen any solutions posted. Has anyone else seen these problems and are there any fixes?

Did you have HardSPL V1 installed prior to installing the update? If so you would need to manually update the SPL to 3.xx.

The power button issue seems to be related to WM 6.1 (it's been present in every 6.1 ROM I've used). I've read several comments about it in several different threads. NotATreoFan (NATF) posted a 'workaround' in his ROM thread which has worked perfectly for me. Simply hold the power button for a very short time instead of just pushing it - .5 second works fine.

The power button issue has been revealed as a "feature" AT&T added to their 6.1 ROM. It is intended to prevent accidental powering on when the phone is in your pocket.

NotATreoFan said:
The power button issue has been revealed as a "feature" AT&T added to their 6.1 ROM. It is intended to prevent accidental powering on when the phone is in your pocket.
Click to expand...
Click to collapse
Some "Feature"

Kuschelweich said:
Did you have HardSPL V1 installed prior to installing the update? If so you would need to manually update the SPL to 3.xx.
Click to expand...
Click to collapse
I had the previous stock ROM installed and whatever SPL version that was. The power switch is an interesting feature, I guess now that I know it, it makes sense. The Tilt power switch is so hard to press that it seems unnecessary.
Has anyone else experienced the lag. It is very noticable when I am playing a game like solitaire. The phone will work fine for 2 or 3 minutes then be unresponsive for 10 or 15 seconds and then be good again. I haven't installed any 3rd party apps yet, just run them from my SD card.

I gave up on the official ROM, and had to be selective on which ones to load up. My favorites were the basic naked ROMs (NATF-it will be missed, yes yes, go Phillies-That old dude sounded like a rock star, and AthineOS). Added applications (not all at once) to be able to see what programs would mess up the speed or even the sound (found out that a certain version of SRSWOW would render the volume control and anything having to do with sound as useless). Ended up with what I think is a completely functioning, lag free WinMo phone. Yes, it took a little while, but worth the effort. So far have over 35 different programs/customizations along with Igo8 and Manilla 2D (w/o Youtube or GoogleMaps) working together beautifully. To save me the trouble of having to load cabs one by one I installed SASHIMI to my storage card and, voila! Almost automated reloading of all cabs...

I've experienced the lag across some new cooked roms I've been trying. I'll have to go back and figure out the SPL situation to see if that fixes it. The lag is super annoying though.

Kuschelweich said:
Did you have HardSPL V1 installed prior to installing the update? If so you would need to manually update the SPL to 3.xx.
Click to expand...
Click to collapse
Yup that was exactly my problem. I still had V1, what a huge difference, no more lag. Thank you!
TracyD follow this tutorial:
http://forum.xda-developers.com/showthread.php?t=433835

Lev00 said:
Yup that was exactly my problem. I still had V1, what a huge difference, no more lag. Thank you!
TracyD follow this tutorial:
http://forum.xda-developers.com/showthread.php?t=433835
Click to expand...
Click to collapse
I ran through the tutorial and updated the SPL but that did not fix the lag. I ran the unlocker and that seemed to do the trick. No more lag. I had already determined that I could stop the lag by putting the phone in flight mode. There must be a problem with the stock ATT Radio.

tilt keeps freezing

hey guys, not sure whats going on, but my tilt lately keeps freezing, but it only freezes when i go into landscape mode. i've ran the same programs for a long time (palringo, google maps, live search, kaiser tweak and srs wow) i'm not even running skyfire anymore, and i've uninstalled my opera browser but it keeps freeze. i've done some reflashes and hardware resets, and only ran the above programs, and it still ends up freezing when i put it into landscape. Anyone know what could be causing this? it doesn't matter if im typing landscape in notes, palringo, PIE or anything else, always freezes. The ironic thing is that if i bust out my stylus and type w/ that using the soft keyboard it seems to run just fine (but slows me down A LOT). any help would be much appreciated.

Do you mean your hardware keyboard lags?
If so in software is a speedup keyboard .cab.

stylez said:
Do you mean your hardware keyboard lags?
If so in software is a speedup keyboard .cab.
Click to expand...
Click to collapse
no its not a keyboard lag by any means, the phone literally freezes. i dont even have to type when its in lanscape mode for it to freeze, as soon as the screen changes orientation it freezes immediately

simbadogg said:
no its not a keyboard lag by any means, the phone literally freezes. i dont even have to type when its in lanscape mode for it to freeze, as soon as the screen changes orientation it freezes immediately
Click to expand...
Click to collapse
Thanks for clarification, just that you say soon as use onscreen keyboard no issue, are you using a stock ROM? Does it happen on a clean flash no programs installed?

stylez said:
Thanks for clarification, just that you say soon as use onscreen keyboard no issue, are you using a stock ROM? Does it happen on a clean flash no programs installed?
Click to expand...
Click to collapse
sorry, i should have given a lot more info, but i had to jet to class. Anyways, its not the stock rom, i'm running NATF's Lite rom (no TF3D). I actually downloaded originally around september/nov/dec of 08 (dont remember, but its been months that i've been running it). And never had a problem with it...now all of a sudden it seriously craps out everytime i run it. I tried running Hyperdragons IV Lite and i was experiencing some of the same problems. I'm really starting to think its one of the problems i'm running, so i'm going to to a hard reset (again) and see if it runs just palringo, and google maps w/out any problems. its just getting super frustrating to be honest. i'm running the exact same programs that i've ran for the last year, but now its deciding to act up. hopefully its something in the software and not hardware

ok...so i got home, and installed the OEM att tilt rom. really, no matter what program i install, pretty much anything. the freezing occurs. any out there familiar w/ cell phone hardware? i'm thinking that might be the cause, if so...do you think there's anything that can be done/replaced to fix it?

Hi, this started happening to my just today also! At first I thought it was the onscreen keyboard that made my phone freeze (as I have seen others with the same issue) and thought I could fix it by using another keyboard app. I used SPB's keyboard and it prevents my phone from freezing and I'm able to type things using it. BUT my phone STILL freezes when I put it in landscape mode and try to type something. It freezes after typing a couple of letters. This is stock ROM; I've never flashed it.
Is there a .dll I can use to repair or anything of the sort?
Btw, I'm using a Tilt. Thanks!

anyone have any method ..to prevent this problem???
I find that if restart the phone few times will freeze at gray screen .."the original HTC gray blank screen with loading box in the middle" but the antenna reception green light is normal blinking (all the button not functioning).... -solution have to press reset button below ...
so now everytime install new program very scare to restart .. if un lucky ..will stuck at that screen.... really wonder why ...is it the WM6.1 not stable???
I use motorola linux ..no such problem...

simbadogg said:
i'm running the exact same programs that i've ran for the last year, but now its deciding to act up. hopefully its something in the software and not hardware
Click to expand...
Click to collapse
Try the relevant ROM thread also look at your hardSPL version. Some users have fewer freezing probs just by updating hardSPL.

tsfatt said:
so now everytime install new program very scare to restart .. if un lucky ..will stuck at that screen.... really wonder why ...is it the WM6.1 not stable???
Click to expand...
Click to collapse
Not at all, there's definitely something wrong with your setup if it wont even boot fully. Maybe a hard reset and some testing between installing each individual program will weed out the culprit. That said I've found (at least the HTC official) WM 6.0 ROMs to be much more reliable and stable than WM 6.1 ROMs.

Flying Kiwi said:
Try the relevant ROM thread also look at your hardSPL version. Some users have fewer freezing probs just by updating hardSPL.
Click to expand...
Click to collapse
Sorry if it's a dumb question, but is there a HardSPL update for OEM OS?

DaDragonChild said:
Sorry if it's a dumb question, but is there a HardSPL update for OEM OS?
Click to expand...
Click to collapse
Not as such - hardSPL is made by dedicated folks who have customised the OEM version but installing it will mean you no longer have an 'official' setup. That said, you can always revert to the official HTC SPL if needed for eg a warranty return. You could also install a newer HTC SPL for your ROM (as long as it's compatible *be careful about this* - eg I'm using the 1.93 HTC SPL with my ROM instead of the 1.56 SPL). This is all explained in the Kaiser wiki (through the xda-wiki button above) so it's well worth having a good read there

aaaahh I looked around. and I can't find a driver to reinstall for the hardware keyboard... I'm assuming this would fix it~

Sorry to double post but I just wanted to say I fixed the problem by backing up and restoring with SKTools after doing a hard reset. It makes me think, what exactly caused the problem in the first place if doing this fixes it? Is there anything that SKTools leaves behind in an All System backup? Perhaps something messed with my registry causing the keyboard to freeze the phone when used.
I'd hate to think my phone can actually get spyware now. Maybe Skyfire's true desktop viewing of webpages allows for this to happen?
Let me know what you guys think

" used Spb's keyboard and it prevents my phone from freezing and I'm able to type things using it. BUT my phone STILL freezes when I put it in landscape mode and try to type something. It freezes after typing a couple of letters. This is stock ROM; I've never flashed it."
If I will you to avoid ...uninstall this soft keyboard ... use back the original keyboard at the time being and see... if u restore back what is the diff compare to now ... If I not wrong still the same ...
FYI, I got this freezing problem is after I have install PCM kb 0.14 ...then I try install & uninstall & install ..and need to restart the phone ..2 out of 4 time is freeze at loading screen .. now really worry is it b'cos I uninstall it at the same time have remove certain original files .....
WM is diff with windows ...lack of tool to chk which system files damage .... I really hate hard reset ..just like computer... imagine keep format the hard disk ....

Hard reset comparible to system recovery process
tsfatt said:
WM is diff with windows ...lack of tool to chk which system files damage .... I really hate hard reset ..just like computer... imagine keep format the hard disk ....
Click to expand...
Click to collapse
If only restoring a full size PC was as easy and quick as hard restting. Sure there's a little work involved in reinstalling apps after completing the hard reset but if the apps are well designed ones that install via activesync, that's as easy as going to Activesyncs add and remove programs function and ticking a box. If this is not available then maybe the old app is the cause of the problem?
A hard reset every now and again is very useful for maintaining peak performance and it certainly weeds out whether a problem is hardware or software related pretty quickly.

Pocket Word won't work

Pocket Word has stopped working. Before you suggest a hard reset please read on.
Whenever I try load Pword it loads up, briefly shows the folders and then goes white with an empty bar at the bottom. It's as if it's attempting to load something as there is a cancel button at the button. But it's just completely locked and i have to terminate it manually.
At the moment I'm running G's Dk.10 but this has happened before when I was running one of Dutty's roms. Different screen but still wouldn't work.
I've only just finished customising my phone after the latest rom flash. I'm loathed to hard reset, especially when it might just stop working again. I've tried reinstalling office 6.1 but to no avail.
Changing radios couldn't affect Pword could it? I've flashed a couple of radios since it was last working. I'm probably grasping at straws here.
any suggestions other than hard reset?
Cheers

Yeah... A hard reset won't fix that... Try cooking a new ROM or something. My guess is that pword.exe became corrupted when the Kitchen built it. That has happened to many many many many system files of mine when I build custom ROMs.

EDIT: Removed. Double post. Doh!