Related
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.
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
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.
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.
I recently falshed the new WM6.1 ROM from the HTC website. The only problem I can't seem to get around is when the phone is locked and put in sleep mode, a few seconds later the screen will flash white for a second. And then periodically blink white. Mainly I don't want to waist precious battery life. Its now driving me insane. I've looked and searched for hours on hours and can't find anything like this.
I've hard reset, soft rest. Got rid of the bloatware. But still got this blink.
Any help would be greatly appreciated!
Thanks in advance!
I've came across this several times with many 6.1 roms. I am not sure if a fix exists. However, this has never bothered me. I simply click the power button twice and the blinking stops. Hope this does the same for you.
All The Best.
Same thing happens to me. I will be watching to see what the response is. Bugs me too. No idea how many times that's happening while it's in my pocket or something - not good for battery life and can't be good for the screen either...
Empire101 said:
I've looked and searched for hours on hours and can't find anything like this.
I've hard reset, soft rest. Got rid of the bloatware. But still got this blink
Click to expand...
Click to collapse
As already mentioned several WM 6.1 ROMs suffers from screen flashes relating to power management issues. Using the latest HTC WWE WM 6.1 ROM the TyTN II will occasionally require two button presses to come out of power saving mode.
If you were happy/happier with the WM 6.0 ROM complain to your ROM provider and if necessary request it be reverted (or read up here and once you know whats required, do it yourself). I don't see any 'new' official ROMs coming for this device now it's comparitively elderly, so I think it'll be up to you to come up with a solution.
HTC has provided an HotFix for that issue at :
AT&T Tilt WM 6.1 Backlight HotFix
But Truely speaking, I installed and it didn't worked for me.
It might work for you, so just give a try.
Regards,
Thanks guys. I'll try the double push of the power button and see if it works, if not I live with it a little longer, till I go mad.
If I can't take it anymore I'll just re-flash to a different ROM.
Once again, thanks for the replies.
By the way the BACKLIGHT HotFix didn't work for me either. I think thats mainly to fix issues with the backlight timer always reverting back to 10 seconds, no matter what the user setting is.