I just bought the Fuze. The screen looks awesome. However I am having a problem where the touch screen is very unresponsive. I find myself having to tap the screen two or three times to get it to react. For example, I have to tap the Windows icon a few times before the menu opens. I also find that pressing harder on the screen with my finger or stylus makes it react a bit better as well. I shouldn't have to press that hard however. I never had an issue like that on my Kaiser.
Was wondering if anyone else has this problem. Could it be an unoptimized OS or video driver? Any way to adjust the sensitivity of the touch screen? Basically, I want to know if this might be an OS issue vs. a hardware issue.
I hate to return such a nice phone because of how unrepsonsive it is.
BTW, I am using ROMeOS v1.4.
Thanks for any inputs.
Its probably not defective in anyway. The fuze screen is a resistive screen, not a capacitive screen (the iPhone), so you do need to press a little harder. You can install the advanced config app and/or the TF3D customizer app to change the screen sensitivity. I have it on my fuze and it does make quite a difference.
FYI you need .NET compact framework 3.5 in order for advanced config to work
djcaston said:
Its probably not defective in anyway. The fuze screen is a resistive screen, not a capacitive screen (the iPhone), so you do need to press a little harder. You can install the advanced config app and/or the TF3D customizer app to change the screen sensitivity. I have it on my fuze and it does make quite a difference.
FYI you need .NET compact framework 3.5 in order for advanced config to work
Click to expand...
Click to collapse
Thanks for the reply. What setting did you use?
I just use the TF3D config with performance setting #4, which is the screen sensitivity one, I believe. I find that to be the best setting. The other thing you might wanna try, even though it may seem obvious, is realign the screen. that could cause some problems.
Screen Not Responsive
my screen has become unresponsive over 75% of the time. same w/stylus or finger. already adjusted sensitvity through Advanced config tool, and Diamond tweak. try to re-align screen, and most of the time, screen does not even recognize the taps. This happened on previous one I exchanged. HELP ! !
Do you have a screen protector on your device?
I noticed that my Touch Pro was very unresponsive until I got rid of the stock screen protector and used it bare-screen
Try the second cab in this post
http://forum.xda-developers.com/showthread.php?t=469865
It drastically increases sensitivity for our pleasure--i felt that it does a better job than TF3D and Advanced Config. There may be an issue with your ROM--my old Tilt would lag on me dependent on the ROM even when the programs installed were identical. Currently using NATF's.
Screen Not Responsive - fixed
Wow ! !, I never would have thought it was the screen protector. I took it off, and it works great. thank you to TehPenguin. maybe it needs to be changed more often, or use a different brand.
That, was my second guess...but seriously, try the cab...
If you're using a snap=on case that can also cause the screen to stop responding. I was using a very cool looking red snap-on case I got from ebay. I got home from work today pulled out my phone to do something and it was completely unresponsive. I finally took off the case and it worked fine.
Related
I would like to know how much larger the cruise against the touch. does anyone have both that can post a side by side shot
I'm in the same boat. It's 10mm longer and 1.5 mm thicker according to specs. Really wish I could experience one before buying!
I was concerned about this as well, but its not bad. Its not too thick for me.
I am very glad I bought it. Its a great device... everything worked perfectly out of the box.
From the specs it's almost identical in size and weight to the Artemis so if you could find a store with an Artemis (or re-brand like O2 XDA Orbit) then that would give you a really good idea of how the TC will feel in the hand and/or pocket. In fact the TC is about a mm thinner than the Artemis so if anything the TC will be slightly more pocketable.
I'm in the UK and when I bought my first device (an Artemis) I went into an O2 shop and played for a long time with the Touch and the Artemis (O2 XDA Orbit). I ended up buying the Artemis, even though it is bigger and I really do care a lot about size and weight, and I didn't regret it. I find it completely unobtrusive in my pockets.
- Julian
Here you go (halfway down the page)
http://www.howardforums.com/showthread.php?t=1303843
JNGold said:
Here you go (halfway down the page)
http://www.howardforums.com/showthread.php?t=1303843
Click to expand...
Click to collapse
Geez, the Polaris IS thick.
I almost pulled the trigger on a Polaris this week but now I'm really torn. I dusted off my old Eten and Trinity and looked at some friends devices this weekend. One thing the Touch has going for is the very few small hard to press buttons. Add to that the screen that some claim is not sensitive enough and you have a device that is ideal to store in your pocket. With my Trinity in my pocket, if I got a text or a call, buttons were always pressed and several apps opened. Even with the flush screen, the Touch never accidentally calls people, etc.
Hard to tell from the pics - does the Polaris have a large button pad like the trinity? I mean, are all the buttons one large piece?
My problem isn't the lack of features with the Touch. I can't get more than 1 bar in my office with AT&T GSM and miss calls but with 3G, I get 3. I've tried this with my trinity and 8525. I've Asked my AT&T rep and he can't explain it. Thought the size of the Touch would offset the reception issue. After 6 mo, I am looking for a small device with 3G. Considering a Polaris or LG MS25. Odd thing is that Sprint and Verizon don't get a signal either but T-mobile does. I'm gonna pop a T-Mobile SIM in my Touch and see. I'd hate to switch carriers but HTC has let us down by not putting 3G in the "enhanced" Touch.
Baxter said:
(..) With my Trinity in my pocket, if I got a text or a call, buttons were always pressed and several apps opened. Even with the flush screen, the Touch never accidentally calls people, etc.(..)
Click to expand...
Click to collapse
If you're seriously in doubt between these two devices you really need to take a look at S2U2 to lock your device (automatically on screen off).
Incidentally: I used to have S2U2 installed on my Artemis, but on the Polaris the ON/OFF button is situated on top of the device, which means that it is very unlikely going to be pushed inside my pocket. By default all buttons except ON/OFF are switched off on screen off. So far I haven't felt the need to install S2U2 on my Polaris, however happy I was with its performance on my previous device.
Seriously, the Touch is no competition for the Polaris, performancewise.
I've been looking for a long time for an app that would prevent all buttons & screen from waking on incoming sms/call but still allow audible alert or vibrate. Pressing on/off would wake much like opening a flip phone. I'd prefer that it run in the background and not require a slide or button combination to "unlock". Just simply have to press power to wake. Does it do that? I'll give it a try if you say it does.
Baxter said:
I've been looking for a long time for an app that would prevent all buttons & screen from waking on incoming sms/call but still allow audible alert or vibrate. Pressing on/off would wake much like opening a flip phone. I'd prefer that it run in the background and not require a slide or button combination to "unlock". Just simply have to press power to wake. Does it do that? I'll give it a try if you say it does.
Click to expand...
Click to collapse
What you're describing is the default functionality of the Polaris. After 3 minutes inactivity it falls asleep on screen off (you can use power button to force sleep) and locks screen and buttons except power button.
Calls, notifications etc. still work, (bluetooth) audio will also keep running.
To awake, press power button.
So you are saying that the polaris doesn't wake when you have an incoming call or sms? Maybe there is a misunderstanding. I want to have to press power before being able to answer.
Does anyone here know of a method that I can align a touch screen on a pocketpc/phone (XV-6700; did not post this on the Apache forum because I am just wondering about how to do this on WM6 regardless of the phone function) using the registry? I have to use the registry, if anything, or anything else because the traditional pointing and touching with the stylus does not work due to a 20% working screen. Only the middle portion of the screen registers clicks truely. The other 80% of the screen you click here and the touch registers as a touch over there, centimeters away, making it useless.
Thanks in advance... I really would love to get this spare xv-6700/ppc-6700 phone working how it used to but I am sure it's a hardware + OS issue and the phone function has nothing to do with it.
-Rob
Why not use the screen calibration under settings? If it still doesn't work, you may need a replacement.
I'm looking for a solution for a hermes, but assume it would be the same for wizard, kaiser, etc.
I'm often browsing the internet on my phone, and want to type just a few words without losing any screen estate to an onscreen keyboard, and without causing the screen to reprocess to landscape. I especially want to do this as I often have ms reader in the background, and it locks up the whole device while it repaginates the book.
Searching the obvious terms is just leading to people who want to rotate the screen without opening the keyboard - not want I want to do.
Any tips would be appreciated. I either want a way to lock the screen to portrait, or a way to make the device ignore the light sensor which tells it the keyboard is out (but if the keys could still light up, that would be a bonus.)
I`m using Opera, in portrait mode and I get keyboard to write -> the screen of my Kaiser flips in the opposite direction of my keyboard ._.
So yeah, this would be great.
if it works from a light sensor just cover it up with something maybe?
edit: it doesn't work lol, i also have this problem. my phone is too slow to handle this. i bet there's a registry setting for it. if i find anything out ill let you know
Okay, after further searching I found that someone had answered this question.
http://forum.xda-developers.com/showthread.php?t=349760
I now have rotate mapped to a button, (using spb pocket plus, rather than the program in the thread), so I rotate the screen manually when I want.
Lokioki - this solution will probably suit you for your opera problem.
Sorry if this has been covered already; I searched but didn't find anything, but then I may not know the right terms.
My question is: is there a hack or app to adjust when the hard buttons illuminate? I always forget they're there, and when I do remember I still have to look at the buttons. What I'd really like is to make them light up whenever the dial pad comes up or maybe even when the screen is fully illuminated (not staying on when the screen goes a little dim when you don't touch it for a while). I'd also like to be able to change the hardware Windows button to go back to the Sense home screen, rather than the Start menu.
i use KeypadLedControl, it enables the hardware buttons to light up whenever the screen is on
Excellent, thank you!
if i try to slide right after pushing the lock button, it doesn't response rapidly. I have to wait one second to slide the slider. Is there any way to get rid of this delay? I want to slide right after pushing the lock button
I have tried tommy's fix and heartwolf fix however they didn't make a big difference.
Any suggestions?
This has been there since the introduction of the new lock-screen that came with wm 6.5. As far as i am aware there is no fix. The tommy fix mentioned does not work for me. i just live with it, but if it bothers you try s2u2 that has no delay.
i wonder how is it fixed in s2u2. can't we the delay fix only?
slayerns said:
i wonder how is it fixed in s2u2. can't we the delay fix only?
Click to expand...
Click to collapse
I did notice when i used s2u2 slightly higher battery usage. So maybe it has something to do with the device coming out of a power saving mode. I have also tried the htc mini hd lock-screen. But that suffers from the same delay. Hopefully it will be fixed by ms.
It is a bug on the touch screen driver, it takes more or less a second to actually start detecting touch. Will happen with any (touch)lock screen. However in Pocketshield you can opt to use automatic unlocking (with proximity or light sensor), this way you don't have to wait for the touch screen.