Aligning the touch screen w/ WM6 + registry -- !!? - General Topics

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.

Related

Tornado locked keyboard still lights display, drains battery

I recently got a Qtek 8300 (similar to an i-Mate SP5m). It's working pretty well and I'm pleased with it. However, one thing I wish I could correct is that when I have my phone in a case, slightly touching the front of the case causes the locked keyboard to unblank the screen. I have an eBook reader so I have the screen stay on for a longer-than-usual time. The problem is that unblanking the screen for no reason wastes battery power. Half the time when I glance down at the phone case, the screen is on.
Is there any way to get only the left soft key, or any other key, to unblank the screen to unlock the keyboard, and have all the other keys ignored? Thanks.
-Gary-
I'd be very curious to get a solution to this problem too. Even the Automatic Keylock utility seems to end up calling the canned WM5 keylock routine, which turns on the light whenever you touch a locked key...
I really liked the way WM2003SE locked the keys on a PocketPC phone. With that, the light stayed off until I pressed the power button. The beauty of the power button is that it's recessed and won't be pressed by a carrying case. Plus, I always knew where the power button was - even in the dark.
Dave H
This is a BAD flaw in the software build.
Has anyone found a fix to this?
I do know that the PPC version of WM5 has a checkbox somewhere in settings that actually allows you to disable all keys except the power button, when the keylock is applied. So there's got to be some extra registry entries on the PPC. Anyone got a Wizard or similar rhey can take a look at the registry and see?
I am SURE standby time would be GREATLY improved if we could invoke this on the Smartphone platform.......
cinimod1000 said:
This is a BAD flaw in the software build.
Has anyone found a fix to this?
I do know that the PPC version of WM5 has a checkbox somewhere in settings that actually allows you to disable all keys except the power button, when the keylock is applied. So there's got to be some extra registry entries on the PPC. Anyone got a Wizard or similar rhey can take a look at the registry and see?
I am SURE standby time would be GREATLY improved if we could invoke this on the Smartphone platform.......
Click to expand...
Click to collapse
From my Wizard (XDA Mini-S), turning the "lock all keys" option on and off, changes this value:
[HKEY_CURRENT_USER\ControlPanel\Keybd]
"DefaultKeyLock"=dword:00000000 (unlocked)
"DefaultKeyLock"=dword:00000001 (locked)
unfortunately, there is no "Keybd" key on my Tornado (Xda IQ, specifically) so I suspect this won't work. Shame...
Daern

Open hardware keyboard WITHOUT rotating screen

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.

Touch Screen Problem

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.

Hack/app to illuminate hardware buttons too?

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!

[Q] Hardware buttons went crazy!

Hello!
I'm experiencing some problems with my o2 Touch Pro.
Hardware buttons on the bottom of the phone (d-pad, home, back, call, end call) are not working properly (they work fine only 20% of the time, it's random i guess).
When i press "call" button, device responds as if i pressed the "left" button. It's very annoying. The circle used to zoom in, and out around the "enter" button is problematic as well. It zooms - but but in a very chatoic way - a bit of of zoom in, then zoom out, another zoom in. Functions are just messed up.
Another time, it's all working...
How can i fix it? Is it a hardware problem?
I'm using the Energy Rom - titanium version.
Thanks for your help in advance...
Honestly, if you can't deal with it, get another device. Either that or stick with the stock ROM, less problematic (you can also keep the full function of the d-pad) but then again it may introduce other issues. Someone mentioned this being more a hardware than a software issue. Since I cannot reproduce this on my at&t Fuze, that is all I can suggest on my end.
I get some of that with my fuze; mostly, the d-pad doesn't read gestures properly. If I run compact heaps (from sk tools) periodically, it helps. Soft resetting obviously helps as well. I think it's more of a hardware issue. My problems have definitely gotten worse over time. You can also check out this tool (from an HTC test rom dump; can't remember where I got it). It's a debugger for the d-pad. At least you can see how accurately the button presses and gestures work.
Thanks.

Categories

Resources