Hi, Just got my MDA Vario III, and it appears the screen alignment that WM runs on first boot will not work. By that I mean its asks me to align the screen, but it will not register the taps with the stylus or fingers.
However, it does know when I touch the screen as it brings it out of powersave. I downloaded this Remote Screen Alignment program, which is able to skip the screen align process, but then when I have done that the taps from the screen are all over the place - because the screen hasn't been aligned. The keyboad works fine for navigation around the menu's.
Does this sound like a DOA device? Or am I missing something stupid?
foaf said:
Hi, Just got my MDA Vario III, and it appears the screen alignment that WM runs on first boot will not work. By that I mean its asks me to align the screen, but it will not register the taps with the stylus or fingers.
However, it does know when I touch the screen as it brings it out of powersave. I downloaded this Remote Screen Alignment program, which is able to skip the screen align process, but then when I have done that the taps from the screen are all over the place - because the screen hasn't been aligned. The keyboad works fine for navigation around the menu's.
Does this sound like a DOA device? Or am I missing something stupid?
Click to expand...
Click to collapse
It might be a simple loose connection or something trapped between screen and bezel. But I would not be even thinking about that, it would be going straight back under warranty. Thankfully, this is not a common problem with the Kaiser and I think you have just been unlucky.
I assume you have not put on any screen protector that might be causing this behaviour> Otherwise it is a DOA and nothing you can/should do other than return.
Mike
Thanks. I hope its not common! No screen protector, but I did try one first before first boot. I immediately removed it when the taps weren't working. I'll send it back tomorrow, thanks.
Dont tap. Just lightly drag the end of the stylus around each target until it proceeds to the next one.
It's common and should be fine.
Thanks unwired. Whilst that does get a response from the TyTn II, and moves the align crosshair, unfortunately it just loops the alignment process indefinitely. Arranged an exchange with T-Mobile without a problem
foaf said:
Thanks unwired. Whilst that does get a response from the TyTn II, and moves the align crosshair, unfortunately it just loops the alignment process indefinitely. Arranged an exchange with T-Mobile without a problem
Click to expand...
Click to collapse
If the future device does it, just try what I suggested but be as accurate as you can.
Unwired's method works for me as well. My Kaiser always seems to lose the ability to detect stylus presses (but finger pressure works) every time I use it on a plane which I assume is due to the cabin pressure. When the screen is reset, everything goes back to normal. Has anyone else noticed this, or do I have some defect that is only going to get worse?
I got the second Kaiser, and it happened again. But I immediatley used unwireds method, this time being extremely precise and only moving the stylus slightly. It works fine now, and stylus accurancy seems to be ok.
I still think it's strange, as I have had an HTC XDA before and a tap was sufficient on the screen align process. Furthermore it clearly states "tap screen" not "tap and drag".
My last three Wm devices (Prophet, Hermes and Tytn 2) have all been reticent to respond to alignment taps... but carefully moving the stylus around the target has always fixed it.
unwired4 said:
My last three Wm devices (Prophet, Hermes and Tytn 2) have all been reticent to respond to alignment taps... but carefully moving the stylus around the target has always fixed it.
Click to expand...
Click to collapse
For me it is more like 'tap-and-hold'. I make a firm tap on the '+' symbol, then keep the stylus pressed on the screen for one second, then release. The '+' then moves to the next alignment point.
Just for the record, I think the problem is common!
I've seen many people who have unresponsive touchscreens, and now I'm one of those unlucky people. And nothing works. And I don't have warranty because I'm in a different country than the purchase country and the reseller here only services phone bought in the Middle East. #[email protected]$#@$#@
I have an AT&T Tilt...until Friday it worked great...It has WM6.1, HTC Home and spb Mobile Shell.... Friday I changed the screen protector from the same pack that I have used for months and then the problems started.... Randomly when I try to touch the screen it appears to lock up, but then the start menu will drop down. The soft buttons work, but then every once in a while the start menu will drop down again. I have soft reset to no avail, but then in an hour or so it will start working fine again. Anyone have any ideas, does it sound like a hardware or software problem? should I hard reset the phone and start over? Help
Thanks
Andy
pull off your screen protector.
chances are you have it touching on a side which causes pressure somewhere else and it (touchscreen) thinks its being touched in a different place.
which in turn makes you believe its locked up, since it does not have multi-touch touchscreen it will not respond because it is perceiving a touch somewhere else.
Thank You...Thank You... I believe that was the problem.....
So I apologize if this problem has been adressed before but my forum searching abilities suck.
Ive had a few roms installed on my tilt now but I keep running into a problem with the touch screen. Randomly Ill touch the screen but its registers the stylus touching halfway between the bottom and the where im actually touching. So if I touch the top of the screen I end up hitting the exact middle. Doing a stylus reset seams to fix the problem but thats ridiculous to so it that often. Its not very fun only being able to use half my screen. Any suggestions?
Tentacle Master said:
So I apologize if this problem has been adressed before but my forum searching abilities suck.
Ive had a few roms installed on my tilt now but I keep running into a problem with the touch screen. Randomly Ill touch the screen but its registers the stylus touching halfway between the bottom and the where im actually touching. So if I touch the top of the screen I end up hitting the exact middle. Doing a stylus reset seams to fix the problem but thats ridiculous to so it that often. Its not very fun only being able to use half my screen. Any suggestions?
Click to expand...
Click to collapse
flashing is like pooping, 99% of all problems come from not wiping.
I searched and didn't find this topic.
My HTC Pure occasionally will not respond to touch. This usually happens after taking a call while it's been hooked up to the sync & mymobiler via USB.
Normally doing a soft reset or two, and playing with it in mymobiler would get the screen responding correctly but today it has stayed untouchable.
The bottom buttons, for picking up and hanging up calls, work fine, but unless I go into mymobiler, the screen is unresponsive to any touch.
I haven't dropped it nor gotten water all over it and all the programs seem to work as they should.
Any suggestions or has the display crapped out?
On a side note I did get an gwes.exe error this evening too.
It's possbile that your digitizer is going out but I would perform a hard reset first and see if that clears up the issue.
Hi guys,
So I had to replace my broken screen.
I replaced and everything was working fine until one day, after 1 month, I start getting some ghost touchs in my screen.
There are some spots that triggers the touch at random times and keep pressed.
I've attached a screenshot showing one touch, that of course it is not mine, but keeps pressed for some reason.
If I press that region very hard sometimes the ghost touch disappear which leads to conclude that something is wrong with the screen that I bought, BUT if I reboot the phone it also fixes it, and that is what bothers me the most, I think it is not a physical problem but a software thing.
Can anyone help me break down this problem?
solution?
Do you had any solution for that?
Was it a hardware or software problem?
Best regards,
Spasshawwe