Related
This is one of several problems with my AT&T Tilt. My 30 day return policy ends November 8, so I'm trying to figure out which problems are specific to my phone and which are just Kaiser in general.
Once or twice a day, my phone screen gets corrupt with overlapping text and only the screen locks up. Also, ActiveSync no longer connects. Otherwise, the phone is still fully functional. The screen still responds to touch (although I can't tell what I'm touching), sounds still works, I can make/receive calls, and Voice Command works and even announces incoming calls. The only way I've found to unfreeze the screen is to soft reset.
This happens on both the AT&T and Helmi ROMs with minimal apps and tweaks commonly used by fellow XDA members. So I'm thinking either the problem is my phone's video chip or it's the video driver common to Kaiser ROMs. But if it's the latter and it's happening to other people twice a day, too, I can't imagine that no one would have posted about this irritating problem.
Note that this is different from the thread "random freezing on tilt", where their phone locks up for a few seconds then unfreezes. In my case, ONLY the SCREEN locks up and NEVER unlocks.
Anyone's Kaiser having this only-screen-frozen problem?
Is it only me?
I take by the complete lack of responses and very low view count that no one has this problem except me?
I'm thinking I just got a f'd up Tilt based on these constant lockups on two different ROMs, my Bluetooth problems (which no one else seems to have), plus the 2 dead pixels on the screen (one locked blue above the Start icon and the second locked red just above the hour digits on the HTC Home clock). Guess it's back to the crappy AT&T ROM for me, then wait for a lock up as partial proof of my problems and go the AT&T store to request a new Tilt (which, according to another recent thread, AT&T no longer has in stock).
Just for future reference, it seems that I actually get two types of lockups.
The most common lockup is as described, where the screen gets corrupted with overlapping text and locks up, but phone and touchscreen are still fully operational.
Less common is a complete phone lockup, which causes me to miss calls. The screen doesn't get corrupt, but the phone is completely frozen except for the power button turning the screen off/on.
The following (long!) post was originally posted at the PointUI forum, but I thought it best to cross post it here. I've tried to organize it as best as I can and appreciate those with the patience to read it and the good will to offer help.
------------------------
My AT&T Tilt (HTC TyTN II) is basically out of commision right now, and I can only track the source of the problems back to the latest update of PointUI (v1.02b, Feb. 4th 2008), as I've done nothing else with the phone since. However, seeing as how I've uninstalled PointUI and the problems persist (and are getting worse), I suspect a virus is afoot, or some other lovely problem.
Since the update, I've experienced the same problems as everyone else on this PointUI thread (system hangs on "running apps" screen and randomly), but in addition to that, several other things. I am running the stock AT&T ROM without the bloatware. These have been my symptoms for the most part since then:
Periodically, animations between menus would slow down considerably and sometimes freeze for a moment, even when I had nothing else running in the background. This would happen for any menu: the cog, the bottom bar, favorites, etc.
The touchscreen would stop working (usually, only within PointUI). This usually happened when animations would slow down, but it would also occur alone, randomly. The hardware buttons would still work during touchscreen failure, usually, but sometimes they wouldn't, and I would have to soft reset.
Sometimes, the power button wouldn't work, and I would press it several times thinking I didn't do it hard enough the first few times. After ~20 seconds, the screen would turn itself off and on. When the screen was on, it would not responding to touches.
The PointUI top bar that appears when using any application would, at random, not work. By this I mean when I would tap it, it's like it wasn't even there -- the Start menu would come down, or the volume control, date/time, etc. depending on where I tapped it. Also, the top right button (red X, or the check mark) would not display correctly in programs or the today screen (a check mark when it should be an X, etc.), randomly, and would not be responsive.
Yesterday (Feb. 23rd), things took a turn for the worse. Here's what happened:
When I started up Tom Tom, the screen went completely non-responsive. Only buttons would work.
After exiting Tom Tom (in an attempt to restart it), the touchscreen would continue not to work, both in PointUI and regular old Windows.
Shortly following this, buttons would stop working, and the entire phone would freeze up. Couldn't turn the touchscreen on and off. I did a soft reset.
During startup, when it showed the AT&T logo, the screen dimmed itself to the lowest brightness setting (it never does this). It would remain this way all the way through the bootup process and into Windows as well, never getting any brighter. Even after going to the backlight settings and increasing the brightness, the screen would get brighter, but would never turn off.
Once in Windows, the touchscreen was completely non-responsive. Buttons would still work, but everything would move really slow.
The screen would never turn itself off. Also, when pressing buttons, the screen would never get any brighter.
After mashing the buttons a bit (in anger, yes, but lightly), the touchscreen alignment application came up, asking me to touch the screen in a few places. This worked.
Then, a call came in. The screen froze during the animation for the notification of an incoming call. Also, the phone started to ring, but within 1 second stopped. However, it would vibrate nonstop (my phone is setup to ring and vibrate at the same time) till the end of the earth!
At this point, none of the buttons would work, not even the power button. Did a soft reset.
This was followed by the same exact symptoms ~4 times (touch screen not working, never turning off and staying at the same brightness level, etc). Outgoing calls would work ok, but each time, a call would come in and freeze up my phone.
Eventually, after several resets, the touchscreen would work without having to mash the buttons to get the touchscreen alignment app running. However, it would still freeze on incoming calls (only).
Somewhere between all the resets, I realized that sliding out the keyboard would never switch the screen to landscape. I can still type and my text would show up on-screen, and screen taps still work properly (even touchflo), but all of this would occur while still in portrait mode.
Lastly, the power button would only work once. It can turn the screen off, but not back on, ever.
Somewhere, between the resets, I uninstalled PointUI, which did nothing. I also tried running Sprite Backup, which would never open (and still doesn't at time of writing)!
Before the PointUI update, none of these symptoms were present (earlier release was v1.01b, used since early January). After the update, they began creeping up, getting worse over time. I have installed nothing else since the update, and have only ever sync'd the phone with my computer to charge it.
Today (Feb. 24th), it started getting a little worse...
When I make calls, sometimes the microphone doesn't work at all. I can hear the person I'm calling, but they can't hear me.
Sometimes, the green phone button won't start the phone application.
Power button isn't turning off the screen anymore at all.
This is the current status of the phone. Weathered, battered and beaten, it marches on, still capable of opening the HTC Audio Manager and playing my MP3's in consolation.
Any help regarding the source of these issues is greatly appreciated.
Some additional notes/summary:
I am running the stock AT&T ROM without the bloatware.
I haven't dropped the phone or let it get wet.
I may hard reset sometime this coming week, probably Monday. The first thing I'll do is reinstall PointUI v1.02b, and maybe TomTom. We'll see how that goes.
You know, the more I read this post, the more it seems like a virus.
Man... just hard reset/flash a new rom and be done with it.
SH4YD33 said:
Man... just hard reset/flash a new rom and be done with it.
Click to expand...
Click to collapse
I thought the above was the reason we DIDN'T have WM viruses?
Virus + Hard Reset = Problem solved?
SH4YD33 said:
Man... just hard reset/flash a new rom and be done with it.
Click to expand...
Click to collapse
I agree, at least that way you know if its hardware or software related and you stop fighting a losing battle
MM
tsadek said:
I thought the above was the reason we DIDN'T have WM viruses?
Virus + Hard Reset = Problem solved?
Click to expand...
Click to collapse
That's why I haven't bothered with any of the anti-virus programs out there. Why bother having a constant drain on the system resources when you can do a hard reset, and restore all the cabs & hacks in under 30 minutes?
-Jay
Just an update here, my phone started acting up again ~5 days ago: freezing on incoming calls, not switching to landscape when sliding out the keyboard, never turning the screen off, etc. 3 days ago it got better, and I was able to run Sprite Backup and tried to restore the phone back to my pre-PointUI days. It had to reset, and on that same reset, Sprite didn't run -- the phone just booted into Windows, and all my problems came back.
Last night, I got a call that froze up my phone again. So I reset it, and by surprise, Sprite Backup ran and started restoring my phone. Now it's back to the way it was in January, and everything works perfectly! This backup was made before I ever installed PointUI.
Bottomline, no PointUI, no problem.
However, I should say that with v1.01b, I never experienced any of these issues. Because of my experience, I'm not giving any test versions a try, but I may install 1.03b, when it comes out. Definitely doing another backup before that too.
Thank you everyone.
Sounds to me more like a hardware issue, perhaps with your SD card.
I had the same issues you were havingh, but without ever having installed PointUi on my Kaiser.
I was using Dutty's Rom version 7 with radio 1.27.xx
only installed aps : TomTom and SPB brain training
So it would seem this is a WM or TomTom triggered issue....
My Kaiser just started doing this very same thing today. I'm running the standard AT&T WM6.1 ROM and have been successfully since December 07. I have a 6GB SD card with TomTom on it, also have had no issues until now. Today, the screen didn't switch into landscape upon sliding the keyboard out; the camera freezes and/or is unresponsive; power button doesn't work (on OR off; with or without SD card inserted); couldn't pick up a call earlier today; TomTom freezes when loading; WM player freezes while loading media.... I have not installed any apps on this thing since January. Seems to me like some memory corruption going on, possibly page file related.
I *did* notice that I had about 45MB worth of temp internet files cached and cleaned those up earlier today after these symptoms started. Didn't fix the problem though, but being low on main storage may have contributed to the corruption problem.
I had hoped I wouldn't need to hard reset my phone but here we go....
I purchased a new TyTN II with Windows Mobile 6.1 preinstalled to replace my AT&T Tilt.
Everything seems to function fine except the backlight (on battery power) keeps reverting back to 10 seconds no matter how many times I change it to 1 minute. I've tried disabling the feature and re-enabling. I've tried power cycling the device after making the change. No matter what I do it goes right back to 10 seconds.
The only other problem that I have encountered is with ClearType in landscape, but that's another topic for another thread.
Any help is appreciated. Thank you.
mine too!
ITs really weird...almost like an over the air update...havent changed anything (that I remember of) and my phone is doing the same thing....Anyone else?
ME Too
try setting it for whatever amount of time you want then doing a soft reset.. that worked for me.
Does anyone experience "Grey Screen of Death"??
Every couple of days my Diamond crashes, the screen is stuck displaying a noisy grey screen.
Most likely I will have to reinstall the ROM (I'm using SwiftBL 5.5) ... but if there is a simpler solution out there I'd love to know it,
Thanks,
Mike
I've seen that kind of screen but only when I'm playing a particular game and if I switch the Diamond off before closing the game down; when I next switch it on I get the noisy (mostly) grey screen. When this happens to me though I just need to toggle the power on and off a couple of times and it sorts itself out. Or just not switch the thing off when playing that game of course.
None of which helps you of course as yours sounds like a much more serious and randomly occurring issue.
never heard of it before. try changing to a different Hard SPL, these can have funny effects sometimes.
Thanks for reply. Well, at least I'm not alone.
Mine is more worrying alright. I left the Diamond in standby last night, it wasn't running any apps before that, and the phone didn't wake me up with my normal alarm as it had crashed sometime during the night, not doing anything in particular.
do you notice it get unusually hot at any time?
with some diamonds, when it is processing a lot and on charge it can get very hot, and this may have caused ur problem.
Maybe the Hard SPL will help.
One possibly odd thing I notice is that my ROM is listed as 1.93.00.00 on the bootup screen, I expected this to be 1.93.405.1. Is that usual?
It's not the hot or charging possibilities.
I can't find a pattern really, it definitely crashes just sitting there doing nothing.
Does this also happen with a stock rom?
I didn't see it on the stock rom, but that didn't last too long in my diamond and I've been running the Swift one for a couple of months now.
To rule out SPL and radio, you could try different versions there. If that doesn't help, try flashing another rom (maybe also the stock rom).
If this still doesn't get rid of the GSOD, I would send the phone back for repairs.
Sorry, I couldn't be of more help...
Good suggestions, thanks. At least there's something to try without flashing whole rom.
mine is the same, seems to only do it when phone is charging but idle overnight, and certainly not hot when it does it. I am running the stock 1.93 ROM. Maybe it just gets bored lol!
Then mine was very bored.
Always restarted itself during the night - and lost half the battery charge while doing so.
Had it repaired twice and now it works great. They told me it was a software problem, but I wonder what they fixed, because I have flashed the same SPL, radio and rom on my phone as before.
Glad you fixed it. Mine was ordered on the cheap from HK (to Ireland) so I'm reluctant to send it back except in dire need.
I often see it get very hot around the crash time, as if some app is running crazy, would explain the low battery.
BTW, what rom, spl, radio do you use?
I had the same exact problem up till a week ago.
Now I'm happily a satisfied Diamond user. To solve this issue, do either of the following:
1. Find a rom with a newer Manila version, e.g. Dutty > v2.6.
2. Install the latest Manila cab.
Changing hard spl doesnt work, as I had tried them all. Stock rom was more acceptable but the problem still occurs once in a while.
I had changed to Dutty's rom more than a week ago I haven't had the problem ever since. Try it and share with us if it works.
Reason I say its due to Manila is becos Dutty is using a newer version of Manila as compared to the rest.
Oooh, tasty. A confirmed software method of fixing the problem! I'll give that a go and observe the phone for a week. I'll post then if all is well.
Many thanks,
Mike
I'm running Olinex HardSPL 1.93, Radio BS14 and O2 Germany stock rom 1.93.207.2.
I hope knave's solution will do the trick for you.
Hi...
This just append to my phone sometime tonight..!
A left it charging over night ... like I always do..
and when I wake up... there's just a gray screen of death!
I've just flashed my first cooked rom... had stock HTC ROM before...
and my TF3D version is 1.2.35091.2_1813.6..
maybe this was just a freak accident... one time happening??
lets wait and see...
i'm backing up my phone at the moment to hard reset it later. i've got the problem, that in opera when the page (spiegel.de especially) is fully loaded and it idles for 5 secs, the screen turns grey with stripes and blocks slowly. after hitting power on/off 2 times it's normal again, but as soon as it's idling for 5 secs it fades to grey again.
must have messed up something while updating opera
Hey guys/girls...
I flashed my kaiser about a week ago with the newest official HTC wm6.1 rom (the WWE version). Everything was great, plus i finally managed to send and recieve my emails with my googlemail account...
however, since friday its been acting very slow... even opening the HTC action screen, and selecting "new sms" either took 5 minutes or just didnt do anything... I was having to soft reset every 10 minutes in order to get any life out of it! I've since got rid of my hotmail account, which i think was causing the slowness (as my kaiser auto downloaded the first 50 emails to my phone, which i believe tends to hog resources and slows everything down). Its been responding much better since then... but this morning it started being slow again, and even came up with a "noisey screen" - meaning a mixmash of pixels and colours... which didnt want to go away.
I also have the same old invisible txt when i type an SMS, but only after I've typed about 30/40 characters... and yes, ive disabled cleartype in the system and in kaisertweak.
I've installed hardly anything onto it, and i dont get why im having these issues... it was running super fast and smooth just after I'd flashed it, but its just been getting real slow again... slower than before it got flashed!
any ideas/pointers would help greatly
Also, does anyone know what BTcoreif.dll is/does?
Do a hard reset and then don't change anything until you have made sure all is running fine, then add the next change (one at a time) and wait again. That will help you isolate the cause.