Related
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
Recently upgraded to 6.1 on my ATT Tilt. Now after i lock the device it will go to a grey lit up screen and suck the battery. The screen will go from grey to black and back and forth a few times then remain grey.
If i hit the power button on and then hit the power button again the screen will go away.
The problem is when i do not notice this, my battery dies FAST!
Anyone else have this? Any idea why?
Bump. Please this is draining my battery like crazy.
Not sure if this is the exact same issue or not, but I've noticed that occasionally, after I hit the power button or it goes into stanby on its own, that my screen will "turn grey" as you put it..... I think it is the backlight comming on without the rest of the screen. I've noticed it a couple times where it flashes on, then goes off again a couple times... once or twice staying on longer. Also, if I hit the power button to turn it on, the regular screen comes on and then it seems to stop. I've got the lock set to activate after 1 hour of stanby and rarely lock the phone otherwise.
I only noticed this after upgrading to AT&T's official WM6.1 ROM.
Anyone have any ideas?
That is the exact situation. And when you hit the power button on again then off again it seems to go away.
Glad I am not alone. Someone out there that is smart should know what is going on with the 6.1 and backlight.
I just noticed this happen on my Tilt last night when I plugged in the charger. The screen was already locked and in standby when I plugged it in. I placed in down on the desk and started to walk away when I saw the screen light up... just blank gray. I pressed the button to take it out of standby and then again to put it back in standby and then it was fine. Didn't think too much about it until I saw this thread.
I'm running totally stock WM6.1.
great im posting this months after the last poster but yes i just updated my phone to the 6.1 rom and i have the same issue happening.....and what is sad is that no one has answered with any help!
to EVERYONE in this thread...this forum would love to help others facing problems but we are not mind readers! please post more information...
for example, quite a few of you have noticed that the problem started happening after the ROM update to 6.1...don't you then think that it is important for you to look into what changes occur in your device when you upgrade a ROM?
if you read around, you will notice that SPL version and Radio ROM versions are just as important as your ROM version and that certain combinations of these three key ingredients will cause unexpected problems.
for those in this thread that already know the importance of SPL and Radio ROM versions, don't you think it is important to let the rest of us know these details in your posts about issues if you want help?
my suggestion to you is to post information about your device in your signatures (see mine for an example) so that you can post short messages about your issues and not have to worry whether or not you've provided the basic amount of information...you don't go to your doctor and tell him it hurts and then expect the doctor to guess where it hurts and to guess your medical history? you bring this information along in the form of medical history documents when you FIRST visit the doctor.
i'll try to help (and so will countless others) once you provide the basic information.
read the wiki for more details.
good luck!
thank you for help and advice. I have added information into my signature about my phone. And the grey screen has gotten worse. and yes it started when i dl the ROM from the HTC site for the ATT Tilt phone. Ive searched around and no one really has an answer from what i have found...please help!! Its is really annoying!
you still need to mention your SPL version so we can proceed from there. read the wiki for more information on how to find out what SPL version is present on your device.
update your signature with that information and then i feel your signature will be complete. remember, if the filename of the ROM contains some strings defining the versions of the various parts of the ROM, it does NOT mean that those parts of the ROM will be updated exactly as expected. for example, your signature says your ROM is "3.57.502.2 WWE"...did you get that information from the filename containing the ROM update? or did you actually go into Settings->System->Device Information to see the versions?
bottom line, don't rely on the version strings in the file that you download. instead, after the ROM has been updated, check on your device to make sure that the ROM, Radio, and SPL versions are as expected.
after you find and report your SPL here (read the wiki to find out how to check your SPL version), then we will probably advise you play around with the SPL version or maybe even try some other 6.1 ROM for the Kaiser. you should know that there are SEVERAL "official" ROMs available to upgrade to an "official" WinMo 6.1 and there are even more unofficial "cooked" ROMs to get you to WinMo 6.1.
hey thanks...i totally understand what your saying but i really dont even know how to check for my SPL or what SPL im using. I dont even know what SPL stands. I looked at the wiki but its talking about restoring your ROM and SPL back to what it was and stuff. I also found my ROM name in the phone info tab.
in the wiki (http://wiki.xda-developers.com/index.php?pagename=HTC_Kaiser) the second question in the "ROM Upgrading" section should have an answer (http://wiki.xda-developers.com/index.php?pagename=SPL Questions?) that will explain what SPL stands for, what it does, and other terms that can refer to the SPL.
once you have read all of that, you will understand that the term "bootloader" is also used to refer to the SPL...then you can look at this page (http://wiki.xda-developers.com/index.php?pagename=Kaiser_Resets) detailing the various methods of accessing low level device functionalities such as hard resets, soft reset, and entering the bootloader screen (at the bottom of this page). once you enter the bootloader screen (its called the tri-color screen), all the information displayed indicates what SPL version you have installed.
i agree that the information on how to check your SPL version is a bit difficult to find in the wiki but ALL of the above information is there...just have to read quite a lot of it and carefully too! but believe me, once you've done some solid reading and searching, you won't regret it!
please find out your SPL version and let us know! good luck
Thanks again...and i didnt see that SPL question before...i might have missed it...but it was helpful. Thank you...i hope i finally got what is needed and i added it to my signature! So i hope that is all the info needed to help me out because that grey screen is annoying...never happened before until i went to the WM 6.1 rom!
let take a step back......why dont you flash the at&t 6.0 rom back onto your device, if it still does that grey screen thing, we could then rule out the rom upgrade as being the cause.
well i really dont know how to go back to the other ROM since it is one o the ATT Tilt ROMs from HTC. And i like how the WM 6.1 is...they got really some nice new upgrades but thats about the only annoying glitch that comes with it other then the backlight resetting to dim at 10 sec's all the time. I know it is the ROM cause a lot of other people on here had the same issue after the upgrade...and some people tried to go back to the original ROM before the upgrade and it messed their phone up for a few people so i dont want that to happen with me!
Download the 6.0 ROM and and flash it just like how you upgraded it to 6.1, exactly the same process. You dont need to install HardSPL but it advisable that you do so.
Ton of ppl flash their device many many times, and they dont mess up their device. If you are too afraid that flashing ur device will mess it up, and you are very sure that the grey screen is cause by the 6.1 rom, good luck figuring out, cause i dont have any suggestions that doesnt involve flashing. ok maybe a hard reset.....but after that i'm out of suggestions.
Aight thanks for your help but flashing back isnt really what i want to do....like i said i like the new ROM but the grey screen is the only issue i have...and i know its only cause of the new ROM but im hoping someone else has an answer to the issue!!!
same here
Not looking for a solution, but just adding mine to the list,, I had a 6.0 version that did this. got a replacement after complaining of the backlight problem, and it did it (6.1 version), took it to the ATT device store and they swapped it for a third, 6.1 version also and it does it,, called the help line and they pretended not to know anything about it. just did a hard reset and said "its not doing it now,, I cant help you" I'll live with it if its the worst thing it has.
Scott
I just upgraded to the ATT 6.1 Rom last night and I'm facing the same issue. I have been trying to research as much as possible today and can only find people describing the issue. I did do some experiments today and here is what I noticed...
I have the Device Lock on my today screen. Before the ROM upgrade, when I would lock the device the screen used to dim immediately, and then of course I would press the power button to shut off the screen. Now, with 6.1 ROM, I noticed that when I lock the phone, the dim does not take place until 10 seconds. What seemed to be happening with my "experiments" today, is that if I press lock and wait for the 10 seconds for the screen to dim, and then press the power button to turn off the screen, no grey screen. If I press lock and hit the power button before the screen dims I get the grey.
Looking further into this, I hit lock and waited 2 seconds before turning off the screen. Sure enough after 8 more seconds I get grey. I repeated the experiment again. This time I hit the lock icon and waited 8 seconds before turning off the screen. Sure enough after only two seconds, the grey screen returned.
I feel pretty confident that if that dim took place immediately after lock, like the original ATT ROM, this might not be an issue (at least for someone like me that is used to the 2-step, lock and power button process).
As another experiment...
I also noticed that if I get the grey screen, I could slide out the keyboard and slide it back (which of course turns the screen back on), hit the power button to turn the screen back off, and the grey screen would go away.
Grey Screen on Tilt Problem
Same issue on mine. Anyone find a solution (for any version ROM, etc.) on the ATT Tilt? Thanks.
Hi, I'm just turning on my 8925 for the first time and before setting it up I want to remove all the trial stuff. I set up, soft reset when the "3 seconds customization" comes up, but when the device turns back on, it takes me back to set up again (screen align, password, etc.) I've done this before with another Kaiser and I know it works, but this one keeps recycling the whole process. I've gone through the clear storage, set up, soft reset several times already and it's the same each and every time. What am I doing wrong?
I would keep resetting and if it still continues trying to install the bloatware, dump the rom and go with some of the other great ones. L26 Kaiser Diamond Rom V12 has been good for me lately, Schaps has some good ones ot there too. Those roms will better utalize the hardware on your kaiser. Hope this helps...
I'm so fed up with this. I going to stop now since I think too many resets will screw with the device. I'm starting to wonder if this is the same as the last Kaiser I had. For once there's a new green "window mobile 6.1" screen right after the AT&T logo at start up, which my other tilt didnt have. The screen says to wait while it's clearing storage everytime I do a hard reset, then take me to set up again, then back to the 3 seconds of bloated wares. Rinse and repeate. Another difference is that this one came with HTC Home today home screen the one with the big digital clock and tabs.
Could it be this is a used phone and the previous user loaded it with a different ROM?
You need to soft reset BEFORE the 3 second notice comes up...if the box pops up, you're too late and need to wait to get to the today screen once again. Remember...BEFORE...either way, there are many really nice ROMs out there...
Ah hah! Voila, you are THE man! Thank you thank you! <3
Still strange that this one came preloaded with HTC Home plug-in, though. But Im happy either way
My sister got a Tilt today and had the same issue (I tried to guide her over the phone to ditch the bloatware - she won't be flashing ROMs anytime soon...)
Hers contains the HTC Home plugin as well.
They've apparently updated the shipping ROM...
Glad to hear that it works fine before the 3 second box.
You'll be able to remap the PTT button right out of the box also. Good stuff.
Im just hoping this one doesnt have battery problem like the one I got before. I kept it as long as I could, even got an extra power battery for it (since the stock one drained after maybe 6 hours), until the damn thing heat up so bad while being charged that it almost burn my hand...
Been charging this one for a few hours and no heat problem yet!
/fingers crossed
You should really try a Manilla ROM--they are easy on the eyes, very nice interface...look up NATF or the AthineOS Manilla ROM. Both guys did a fantastic job on those...
NATF http://forum.xda-developers.com/showthread.php?t=424725
Athine OS http://forum.xda-developers.com/showthread.php?t=435345
But, make sure to read the WIKI
http://forum.xda-developers.com/showthread.php?t=369282
Search around, more than likely, that question on your mind may have already been answered.
There's no such thing as a stupid question, but they are the easiest to answer...
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
This is one big PITA with the crappy ATT ROM image. I have to press the power button twice to get the phone out of sleep mode. Once just isn't enough for the wonderfully tested ATT image. This never happened with the 6.0 image, or with any of the cooked images.
So what is the fix? I've seen several threads complaining about this, but none offer a fix. I do not want to flash another non-std "cooked" image, but registry or DLL replacements are OK by me.
here - http://tinyurl.com/d8wfg9
bwnotredame06 said:
here - http://tinyurl.com/d8wfg9
Click to expand...
Click to collapse
If you don't know then there's no need to post.
Potential fix
ButtonBoy said:
This never happened with the 6.0 image, or with any of the cooked images.
So what is the fix? I've seen several threads complaining about this, but none offer a fix. I do not want to flash another non-std "cooked" image
Click to expand...
Click to collapse
So a cooked ROM is out and I suspect a reg entry won't cover something like this (just a hunch, no proof) but you haven't ruled out going back to WM 6.0 (which never had the problem) - you have a potential fix. The screen flashes coming out of powersaving mode were just one of many reasons why I reverted my TyTN II back to WM 6.0. Although that OS also has a few bugs, they're far less of a PITA than WM 6.1s so I haven't looked back
This is a common problem with the majority of the later 6.1 builds, and depending on who you talk to, it is either a great feature ,built in to 6.1 to keep the phone from accidently turning on in your pocket and draining your battery and scrambling your settings and calling people by accident. ......Or it is a really annoying feature that makes you press twice or one long press to get your phone out of sleep. Shall I put 1 vote in the annoying column for you ?
There is no fix. Two quick presses or one long press ? How annoying is it really ? Two quick presses is about as long as it takes to slide to unlock.
I had no such issues with any HyperDragon release. They all had the correct behavior, and none of the "fit-full sleep" issues either. Oh well. Soon enough I will migrate to a better device, and this time I won't tolerate any of ATT's brilliant engineering.