Database Develop

Kaiser going crazy (looks haunted...) AGAIN - Update2: Not Solved?

Ever since returning from repairs, my Kaiser is giving me more problems than before.
First, I apparently lost the ability to hard reset my phone using the 2 softkeys & soft reset button method.
For more: http://forum.xda-developers.com/showthread.php?t=384581
First thing I did when I got my phone back, was flashing the latest ROM from Dutty (Dutty's Official WM6.1 5.2.19209 Release). After performing numerous installations and soft resets, my device went crazy after yet another installation and soft reset.
Just before my Kaiser takes me to the Today screen after (re)booting, the phonepad pops up and seems to be 'pushing numbers out of itself'. Confused by the explanation? Just take a quick look at the short vid I made.
http://www.youtube.com/watch?v=YGkot2-mbbI
(Fast forward to 01:00 to see it going crazy. Long after the vid ends this continues)
Anyone got a clue as to why this is happening? Or has my incompetence reached new heights and is that to blame for my problems?
Thanks in advance
P.S.: In the meantime I have hard resetted my device, but I'm still curious...

call at&t and get a replacement. Easiest thing to do.

Try load the factory default ROM.

FAx
The kaiser has been known to act haunted, thats why it comes in black.
Fix: When applying this fix avoid looking at the screen to avoid the image inside the device that you want to exorcise. Unplug fully and remove battery to prevent an escape through the wires; also ensure that you disconnect any usb devices to avoid an escape to your computer.
Once you have isolated the device. Find the packaging and insert carefully, ensuring that it is packed safely to avoid any breakage resulting in an escape to your home. Then ship to the place you purchased it from and ask them to send you back one that is not possessed.
Good luck.

alexn2 said:
The kaiser has been known to act haunted, thats why it comes in black.
Fix: When applying this fix avoid looking at the screen to avoid the image inside the device that you want to exorcise. Unplug fully and remove battery to prevent an escape through the wires; also ensure that you disconnect any usb devices to avoid an escape to your computer.
Once you have isolated the device. Find the packaging and insert carefully, ensuring that it is packed safely to avoid any breakage resulting in an escape to your home. Then ship to the place you purchased it from and ask them to send you back one that is not possessed.
Good luck.
Click to expand...
Click to collapse
Very dramatic - you don't work in Hollywood do you?

gqstatus0685 said:
call at&t and get a replacement. Easiest thing to do.
Click to expand...
Click to collapse
He's in Belgium

ach2 said:
Very dramatic - you don't work in Hollywood do you?
Click to expand...
Click to collapse
Is that a hint for a career change...... the loss of one's tilt is quite a dramatic event.

@alexn2
I already called in help from the Vatican, but it will take some days before the first batch of exorcists arrives (haunted was a sarcastic expression). Any explanation in the meantime?
@gqstatus0685
This device is a replacement which I got back last week. But it seems to me that I will need to send it back again. Another week without my Kaiser...

alexn2 said:
Is that a hint for a career change...... the loss of one's tilt is quite a dramatic event.
Click to expand...
Click to collapse
care to sign up for ma 4th installement of the exorcist?

Damn this is scary. Call the Ghost Busters!!

WTF?
I just don't get it...
I now have my 3rd Kaiser, since I had issues with the first two. One of the problems my second phone had was the 'haunted' problem as described above.
My Kaiser has been working like a charm for several weeks. I first used the stock ROM, then switched to Dutty's ROMs. I used 3 ROMs: Apr16, Apr29 and Jun07 release.
I installed the Jun07 release today. After installing and configuring the same software I had before upgrading the ROM, guess what?
HAUNTED AGAIN... WTF?
I loaded the ROM, did multiple hard-resets, soft-resetted after customization, loaded CABs, configured them, rebooted several times and when I had finally configured every app => TOTAL Clusterf*ck... (again)
Sometimes it does boot normally BUT when I press the 'Send'-button and the dialer opens => Kaiser goes LOCO again...
Anyone got any idea as to why this happens?
NOTE: I have the latest SPL + Radio NEON 1.58.25.17 (included in the ROM)

I did some additional testing. I had SPB Pocket Plus installed an had the Safe Boot option enabled. So I did some testing in safe mode.
The phone boots 'normally' to safe mode. No apps or services are loaded, and I can open the dialer and even enter numbers to dial. But when I try to delete a number using the backspace in the dialer => again haunted

I just discovered the problem. I always try to install most of my apps to my Storage Card.
Some of those apps is the Microsoft RDP (remote desktop) client.
Installing it to the Storage Card caused the phone to go crazy. It has to be installed to the Main Memory.
NOTE: After discovering the problem, I did find other posts across the forum reporting problems if the app isn't installed to the main memory. Since I found the cab on someone's 4Shared account, I wasn't aware of the installation requirements.
Thanks anyway for the support given

As posted before, I very recently flashed Dutty's Diamond V1 Build 19588 ROM (Jun07).
Today I tried playing WMV files with Windows Media Player for some performance testing. I loaded my first file and whenever I tried something, like fast-forward, switch to fullscreen mode,... my phone crashed and soft-resetted itself.
Guess what I got when the phone booted => The crazy dialer (haunted edition)... It kept doing this after every soft-reset until I removed the MicroSD card. The video I was trying to play was located on the Storage Card, so there might be a relation.
While I have done additional testing under the same circumstances, I haven't been able to simulate the problem.
I'm still clueless, so as always are ideas welcome...

Problems with Kaiser

My Kaiser has been acting up since today morning.
The buttons/keyboard wont work and the voice recording program will start automatically and create files for every 4-8 seconds back to back.
I'm running Dutty's Dual touch ROM.
I reinstalled it and it worked perfectly fine for few hours until when i started txt messaging again....
any suggestions

hamudi said:
My Kaiser has been acting up since today morning.
The buttons/keyboard wont work and the voice recording program will start automatically and create files for every 4-8 seconds back to back.
I'm running Dutty's Dual touch ROM.
I reinstalled it and it worked perfectly fine for few hours until when i started txt messaging again....
any suggestions
Click to expand...
Click to collapse
Are you performing a hard reset after the rom installation?
Also what applications have you installed?
Next time post this in the thread where the rom is, try to stick to forum rules

Also what do you mean your keyboard is broken? Is it simply not functioning at all or are you typing a sentence and " it cmes out lke tis"

oops thanks, I'll post it in that thread. Basically I've been using it for good 5 months and no other applications have been installed.
Keyboard is not broken...the send/end/email/windows start buttons wont work...only the touch screen works.
and yes i hard reset it after the installation

seems like the problem is not with custom rom/firmware and its with the phone in general.
I'm now running stock firmware and the butons still dont work and it acts weird as soon as i turn on (example - goes to phone mode and dials EDFC, and then opens voice recording and starts recording small clips for every 4-6 seconds until i bring it complete stop)

hamudi said:
seems like the problem is not with custom rom/firmware and its with the phone in general.
I'm now running stock firmware and the butons still dont work and it acts weird as soon as i turn on (example - goes to phone mode and dials EDFC, and then opens voice recording and starts recording small clips for every 4-6 seconds until i bring it complete stop)
Click to expand...
Click to collapse
Sounds like one of your buttons is stuck. Maybe try dusting the button area with canister air duster? Hope you don't have to do defective exchange, but that might be in the cards.

cushcalc said:
Sounds like one of your buttons is stuck. Maybe try dusting the button area with canister air duster? Hope you don't have to do defective exchange, but that might be in the cards.
Click to expand...
Click to collapse
I will try that tonight,
Might have to take it into a cell repair store...the drawback is i bought it off a local user, i will give HTC a call.
i love this phone

hamudi said:
My Kaiser has been acting up since today morning.
The buttons/keyboard wont work and the voice recording program will start automatically and create files for every 4-8 seconds back to back.
I'm running Dutty's Dual touch ROM.
I reinstalled it and it worked perfectly fine for few hours until when i started txt messaging again....
any suggestions
Click to expand...
Click to collapse
If i read you correctly, reinstalling the OS fixed it temporarily right? Maybe you got a corrupted file download and should redownload it again? It seems odd to me that the buttons would work short term after a reinstall.
Also , you can try other roms aside from Dutty's ( while his certainly is nice ) there are many alternatives. Pick one that has the radio included just to make sure you dont have some sort of firmware corruption. Also update Hard-SPL to the newest here.
Just a few things you could try

pyraxiate said:
If i read you correctly, reinstalling the OS fixed it temporarily right? Maybe you got a corrupted file download and should redownload it again? It seems odd to me that the buttons would work short term after a reinstall.
Also , you can try other roms aside from Dutty's ( while his certainly is nice ) there are many alternatives. Pick one that has the radio included just to make sure you dont have some sort of firmware corruption. Also update Hard-SPL to the newest here.
Just a few things you could try
Click to expand...
Click to collapse
Yea I tried that too, but now it just wouldn't work...I formatted the memory car but i couldn't format the device, i called HTC and they asked me to send it in and they will take a look at it and said will fix it. I have to return everything back to stock and see how it goes.
Thanks guys

Problem losing the top line of my display

Okay, I've searched and can't find this problem but hopefully somebody may have some ideas.
Quite frequently, I lose the top line of my display (the one with the start button and the system status icons). Everything else works but that line just disappears.
If I then lock the device it comes back. When I unlock it, it sometimes stays but sometimes disappears again once it's unlocked and I then have to turn my phone off and back on again.
I have a standard Orange UK phone, standard ROM and I've used some of the performance tweaks listed here. I've also disabled Touchflo and am using spb diary as my home page.
Anybody any ideas because this is driving me mad?

I had the same, but only when TF3D was deactivated. Since I use it again, it doesn't happen anymore...

It happens on my Orange diamond as well - stock 1.37 rom with TF3D enabled.
It seems to happen once every 4-5 days, and doesn't really have a pattern. Sometimes it's switching between Today and Second Today, sometimes it's rotating, sometimes it's unlocking etc..

flash a new ROM
Hello there.
Well i just recommend you to flash a new cooked ROM. I havent seen this behavior with a cooked ROM.
Best regards.

Well, at least it isn't just me but does anybody have any idea what causes the problem and how it can be solved.
Could it be something to do with glyph memory?

I used to see this sometimes on the orange rom. Since flashing a cooked rom makes the device twice as fast - and removes that problem - I would just flash it.

unwired4 said:
I used to see this sometimes on the orange rom. Since flashing a cooked rom makes the device twice as fast - and removes that problem - I would just flash it.
Click to expand...
Click to collapse
I know it's the wrong forum to say this but I'm just a bit scared to flash it because I've never done it before.
I'm worried about either a) bricking it or b) losing some setting that Orange put in to connect to their network (voice, data, voice mail etc).

Hi
I've had a similar Problem!
It seems to happen when I take the phone out of sleep cos I've got a text and its locked (I've set it for 30min).
I press the power button but the screen only half lights and the top line doesn't display. It sometimes says 'password' in the top left but does nothing if I press it.
I can slide along the bottom line but it doesn't work properly.
Interestingly I also have a Orange Diamond 1.37 ROM (which I've unlocked).
I'm gonna flash with HTC's ROM from there site and I'll let everyone know if the problem persists.
Wish me luck

TheFlash007 said:
Hi
I've had a similar Problem!
It seems to happen when I take the phone out of sleep cos I've got a text and its locked (I've set it for 30min).
I press the power button but the screen only half lights and the top line doesn't display. It sometimes says 'password' in the top left but does nothing if I press it.
I can slide along the bottom line but it doesn't work properly.
Interestingly I also have a Orange Diamond 1.37 ROM (which I've unlocked).
I'm gonna flash with HTC's ROM from there site and I'll let everyone know if the problem persists.
Wish me luck
Click to expand...
Click to collapse
And what happened?

Hi
Sorry for the delay. I tried the HTC site ROM but it just gave me a message saying 'Sorry, this software download is not suitable for your device'.
So it looks like i'm stuck cos its still doing it about once a day just have to switch of and on again.

TheFlash007 said:
Hi
Sorry for the delay. I tried the HTC site ROM but it just gave me a message saying 'Sorry, this software download is not suitable for your device'.
So it looks like i'm stuck cos its still doing it about once a day just have to switch of and on again.
Click to expand...
Click to collapse
Okay. I still have the problem and am very, very tempted to try flashing a new ROM (and Radio). But I just can't quite work up the courage to do it since I've never done it before and it's the fear of the unknown.

dastewart said:
Well, at least it isn't just me but does anybody have any idea what causes the problem and how it can be solved.
Could it be something to do with glyph memory?
Click to expand...
Click to collapse
This happens to me too. I have a T-Mobile Compact IV.
I've found that using FreeUP RAM (part of SKTools) not only releases memory, but also fixes this problem (until the next time it happens, which admittedly is not often).

Just wanted to say that I've upgraded my Orange ROM to the new 1.93 and I haven't had this problem....yet.
2 days without problems so I thought it may be safe to post.

IVe also had this on 1.37.x.x on my mda cmpct IV. Like everyone on here Im considering flashing but Im waiting for t-mobile to release an update (they keep telling me the will, presummably the 1.93.x.x) so that if I then brick the puppy - I can blame it on there rom upgrade.
I want this phone to be better, I know it can be with a ROM change...but I dont want to brick it and for once in my life will have some patience to wait.

new sms notification not sounding

hello xda, ive posted a previous msg about this issue b4, along with others who have the same problem. ive done searches on here and have found that the issues have to do with some version of OPERA. my issue on the other hand is i dont use opera i use SKYFIRE. Does Skyfire use some sort of OPERA? ok now to my issue, (back when i first got my tilt, i had att oem rom 6.1) i now have duttys 6.1. after about a week after i first got the phone, ive been having problems with the phone notifying me of a new msg after about 5-6 sms. ive also noticed that when it fails to notify me, the alarm fails to sound as well. only after a soft reset does it fix its self, until another 5-6 msgs. ive also done the enable/disable threaded msg cab and it doesnt work, both cabs try to disable it. the programs that are installed are. A_C S2U2, bejeweled 2, boz quick menu, s2u2c, phm reg edit, skyfire browser, spb backup, and tilt keyboard fix for cooked roms. <-THESE ARE ONES IVE ADDED, if you need to know all thats one there that was cooked in, please pm me. PLEASE SOMEONE HELP ME. im gettin tired of this issue. att no longer carrys the phone for a insurance claim and im not sending it to HTC and being without a phone. im starting to think its more of a hardware issue than a software issue, if flashing it doesnt solve the problem. Thanx in advanced and sorry for such a long post. also b4 anyone says anything, everything is still checked to sound and vibrate under notifications and sounds.
John

One option you could try is to disable then re-enable the sounds.
Are you sure theat the phone is not temporarily muting the sounds. You could try manually switching the sound off on the volume icon next to the top right X and then re-enabling it.

Have you tried the hard reset?
That will determin if it's hardware or not.

to gilligan8
yes i have done the hard reset several times and it also does it with every rom i flash to the phone

to Elwyn M3100
thanks for the fast reply. no i havent switched the phone volumn to off and then back on. next time it messes up i will do that be i soft reset. if it is muting its self what could this mean the issue is?

But it doesn't do it till you flash it with a rom?

not a flashed rom issue
I have had this problem from about a week after getting my phone. I had this issue with the att oem 6.1 rom after I noticed the problem I contactecd att for a replacement, only to find that they have disscontinued it. id had to trade in the phone for something diff, cuz I love everything about this phone except my sms issuse. trust me I've searched and searched hard about how to fix this and have had quite a few good solutions, but nothin seems to work. I believe this is a hardware issue and not software. I just hope someone has the same issue that I do and nows how to fix it. thank you all for ur help

Being a computer guy this really doesn't sound like hardware... why would a hardware failure be so consistent? 5-6 times then soft start brings it back.

i do believe it is hardware related because i still have the problem even when i reflash to a new diff rom. after i receive anywhere from 5 to 6 msgs it then fails to sound on the following msg. the only way i can get it to resound is to perform a soft reset.

I had exactly the same problem and realised it was just the radio needed changing.

what radio are u running? i have 1.65.14.06 i also had this same issue with the stock att rom and radio

[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)