OK, all the hardcore folks here will certainly call this a repost and this registry tweak is on the KaiserTweak thread, but I thought it was good enough and hidden/buried enough that is warranted a repost.
To the point: If you are unhappy with the responsiveness and sensitivity of your Tilt/Kaiser touch screen give the following registry change a go. I found it made just the right difference. The touch screen is more sensitive and responsive and I have many less double taps required because the first one was missed. Of course it helps both stylus and finger tapping. This has nothing to do with TouchFLO, this is just the touch screen itself.
HKEY_LOCAL_MACHINE>Drivers>TouchPanel>PressureThreshold
modify to 200 or more (modify the DWORD Data field).
I used 200 and it feels just perfect. I think the default was 157 on my AT&T branded device. I imagine this tweak will help if your screen protector decreases the sensitivity of your screen as well.
Wouldn't it have been better to simply bump one of the many existing threads that mention this tweak already? Would cut down on clutter IMO.
I was surprised to see that on my AT&T Tilt the sensitivity was already set, from the factory, with a default value of 233!
Why so much variation between defaults?
jomo25 said:
Wouldn't it have been better to simply bump one of the many existing threads that mention this tweak already? Would cut down on clutter IMO.
Click to expand...
Click to collapse
Perhaps but I only saw it myself really burried on the KaiserTweak thread.
@drb123 - Interesting. Must be a slightly different ROM if the default registry settings are different, right? Since I like the performance at 200 I guess I may give a shot at closer to your default value or even higher. It is the phone number keys that really seem to be the worst (with a finger, of course) and are not yet perfect at 200.
Hi
The sensitivity is set to various values based on the screen calibration test so everyone's will be different. When you touch the crosses during the first switch on or when you align the screen from the Settings menu, this value is set automatically based on the pressure you use during that calibration.
Simply recalibrate, that is probably the better method to get the correct value, all devices will vary anyway and no one value will be good for every phone.
Regards
Phil
PhilipL said:
Hi
The sensitivity is set to various values based on the screen calibration test so everyone's will be different. When you touch the crosses during the first switch on or when you align the screen from the Settings menu, this value is set automatically based on the pressure you use during that calibration.
Simply recalibrate, that is probably the better method to get the correct value, all devices will vary anyway and no one value will be good for every phone.
Regards
Phil
Click to expand...
Click to collapse
So if I want my screen to be responsive, i.e: light touch is enough rather than poking hard, what do I do when calibrating? Hit hard or soft?
Originally Posted by PhilipL
Hi
The sensitivity is set to various values based on the screen calibration test so everyone's will be different. When you touch the crosses during the first switch on or when you align the screen from the Settings menu, this value is set automatically based on the pressure you use during that calibration.
Simply recalibrate, that is probably the better method to get the correct value, all devices will vary anyway and no one value will be good for every phone.
Regards
Phil
Talk about opening Pandora's box...I went to settings > screen and tried to recalibrate, but my HTC Kaiser/Tilt freezes and I am forced to do a soft reset.
I can't even get the crosshairs to move from Point A to Point B, let alone all 5 Points.
I had changed my value in Registry from 233 to 300, just as a trial, but put it back to 233. Did I screw something up and need to do a hard reset to regain that setting function?
Thanks
PhilipL said:
Hi
The sensitivity is set to various values based on the screen calibration test so everyone's will be different. When you touch the crosses during the first switch on or when you align the screen from the Settings menu, this value is set automatically based on the pressure you use during that calibration.
Simply recalibrate, that is probably the better method to get the correct value, all devices will vary anyway and no one value will be good for every phone.
Regards
Phil
Click to expand...
Click to collapse
Thanks - good information. I did verify that.
Things still work much better on my device if I calibrate using the crosses to get the 2D spatial calibration correct, then increase the sensitivty manually. The calibration tool with the crosses simply seems unresponsive and usually takes multiple taps on the crosses to accept the tap.
*****************
Caution
*****************
This has screwed my Kaiser up this afternoon. The registry only took effect after a reboot and I lost touch altogether. Had to do a hard reboot, I'm leaving well alone.
j1ngles said:
*****************
Caution
*****************
This has screwed my Kaiser up this afternoon. The registry only took effect after a reboot and I lost touch altogether. Had to do a hard reboot, I'm leaving well alone.
Click to expand...
Click to collapse
Wow, sorry to hear that, what a hassle. However, at the same time I have used this hack repeatedly and it always works just perfecty. I strongly suspect you did not change the registry value properly.
For those that changed their settings, just remember to check the decimal circle. If you change the default 2a (which is equal to 168 decimal), and input 200 while you are in Hex value, YOU WILL screw up your settings 2a is a Hex value.... Just be careful.
Doesn't KaiserTweak do this already?
Surely safer to use that then risk things in the reg?
Anyone who can tell me what value it should be in case of HTC Touch (Elf)? I have found the reg key but with totaly different value. I am using Bram's dual touched rom and the default settings here is as followed:
Decimal: 7736
Hexadecimal: 1E38
Just had to bump this because its really useful. thanks
Ditto. I missed this when it was first posted.
BTW. if this screws up the touch screen, just use keys to go reset the value. No hard reset required...
Later, Lew
I just seen what my default value was.....it's 400. Is this too high?
afrikandesi said:
I just seen what my default value was.....it's 400. Is this too high?
Click to expand...
Click to collapse
That's what my att tilt was when I first purchased it.
High Sensitivity on Kaiser Tweak sets this value to 190.
Bill
Just use AdvancedConfig and put pressure threshold (under the touchFLO tab) at about 40, This works fine for me .
Where do I get AdvancedConfig?
Thanks
Related
Silly me, screwing around with registry tweaking... well looks like HTC already modified some cache settings, however... they left the CacheSize at 0.
I increased the value [HKEY_LOCAL_MACHINE\System\StorageManager\FATFS]
"CacheSize" to 4096, then 8192... and suddenly... I was poppin around in the UI.
Obviously this uses RAM.
Here's a good test. Before you edit the value, close all programs, then go to home screen and hit start. Then increase the value, and hit start.
Awesome.
Good tweak. However, "dangerous" to use with a device that eats ram as wings.
I have to say I do not see much (if any) difference in phone behaviour. It still "freezes" randomly same way as it did before, sometimes buttons must be pressed 4 times (or held down long enough) so that finally it does something.
I am now half way convinced to return product in warranty as it simply does not work as intended, no matter what setting or registry I change. Beeing BFU, I would probably smash this crap aginst the wall already.
I can't see any effect either (nor does it consume more ram for that matter).
So it does not work. I guess it would be great to send it back to manufacturer all toghether.
It works. You all are crazy.
Must be the placebo effect.
Blue or red pill?
lol
hahahahaha, any green pills ?
Hi Guys!
I have a Touch Pro, but i thought I post here, because it's acually the same phone, and here it's more crowded..
I installed S2U2 2 days ago, and just now after waking up the device I saw S2U2 flickering in the background. Like it was a flickering transparant overlay.
So I turn off the device, and turn it back on..
Then when I got the Touch Pro logo (Pre-windows!!) I saw S2U2 stiill overlaying the screen!!!
So my conclusion is: S2U2 Burned in my screen, so if you have it installed i'd suggest removing it before it trashes your display!..
I'm going to return my phone.. hoping they'll repair it..
Cant take photos now.. but will do when i get home...
Edit.. Sorry guys.. changed my conclusion! S2U2 is not guilty.. TouchPro's/Diamond's display is
Sounds scary. Could you post a photo?
Found some information about this.. Thought it would be nice to share, since I will not be the only and the last one with this problem:
TFT monitors don't suffer from burned-in images.. But they do suffer from "retained pixel charge".. this will cause "Ghost images" (like mine)
More info HERE
Is Image-Sticking Reversible?
Unlike permanent burn-in in phosphor-based displays, which is the result of a premature aging of the phosphors of individual pixels, and thus, is irreversible, image sticking in LCD panels can often be reversed to a point of total invisibility.
However, the extent to which image sticking can be reversed depends on the severity of the causes that eventually led to image retention; top in the list is the environmental temperature at which image sticking took place.
A way to remove a retained image on an LCD panel is to run an all-white screen saver for several hours. It would generally help if this image sticking reversal operation were run at an elevated temperature of around 100 deg. Fahrenheit or 40 deg. Celsius. This should help speed up the reversal process.
Some manufactures would recommend instead using an all-back or dark gray pattern screen saver. Whichever method you choose, make sure the LCD TV or monitor energy savings settings will not turn the backlight off after some time of inactivity.
Other manufacturers would recommend turning off the LCD display for a longer period than the time it took for the static image to cause image retention.
While all three methods can help to remove image sticking, yet our best advice is to follow the manufacturer's instructions whenever these are available.
Click to expand...
Click to collapse
Seems like it will go away when I turn off the screen for a while..
So let's do that, and I'll keep you posted!
damn, try this on your diamond browser:
http://www.jscreenfix.com/basic.php
click the link on the bottom of that page after reading
Thanks! but the applet doesn't work on the mobile browser..
But i've created an avi of it (it works on the pc so Print Screen )
I will play that a couple of times!
Will keep you posted!
oh my god...
i can't understand how it happens.
do you turn off the screen while locked?
[i don't think it's a problem of s2u2...]
I don't think it's S2U2's fault either.. Usualy I turn the screen off. but today while charging through usb, maybe it stayed on, I didn't pay any attention it acually..
I made an wmv file with some flickering screens to stress the tft/lcd screen.. looks like it worked.. stressed it for nearly an hour and it looks gone..
I'll look for somewhere to upload it.. maybe someone else can use it too!
edit: here it is.. :
Click here to open the wmv, right-click save as to save it
g8 work man.
i wait a definitive release of sensorlock, so i'm using s2u2
but i pay attention to switch off the screen ALWAYS
Hakko said:
Found some information about this.. Thought it would be nice to share, since I will not be the only and the last one with this problem:
TFT monitors don't suffer from burned-in images.. But they do suffer from "retained pixel charge".. this will cause "Ghost images" (like mine)
Click to expand...
Click to collapse
Was just about to say that! Atleast the part with TFT cant be burned-in.
Hakko said:
I made an wmv file with some flickering screens to stress the tft/lcd screen.. looks like it worked.. stressed it for nearly an hour and it looks gone.. [/URL]
Click to expand...
Click to collapse
You needn't have done - see my related article and the video file inside.
if the touchscreen is pressure sensitive on the xperia of course. does anyone think it would be possible to code a program to measure that pressure in mass?
i think it would be so sick to use the xperia as a scale
It can not measure mass. Any more pressure will break the screen. Use your common sense!
its not a matter of common sense.
what do you mean anymore pressure would break the screen?
im sure by slightly touching my screen im putting less than a gram of pressure per sq. inch on the screen so im not sure what your talking about because im not going to measure a boulder on the thing, use your common sense..
Yes, it's definitely possible and would not be too hard to code. One way would be to define a measurement area ("scale") on the screen then gradually increase sensitivity settings (via a program, of course) in the registry until a touch was registered in that area. Initially, the registry values would need to be calibrated against a set of small weights (up to a reasonable weight, of course). Anyone got their high school physics weights?
But yo, what would be the good of a tiny xperia scale?
Y'all are crazy.
i have installed your soft touch on my xperia and i love it, where would the registry settings be found to change the sensitivity?
I think it's a really interesting idea to test.
I think it can be done since X1's touchscreen is resistive so it will be able to sense graduations in changing pressure.
Had you had an IPhone, it's capacitative screen would made this impossible.
The thing is, working with registry settings won't do the trick in my opinion. I think you need something more low level (like a driver maybe) to talk directly to the touchscreen.
If I were you I'd go and check the WM 6.1 SDK and see what it makes visible thru its API for the touchscreen part.
It would be worth investigating how the driver accesses the touchscreen hardware.
I'd be happy to try and help with the programming btw
It's the fingerpressure registry setting that changes it.
But storm' is right. I forgot that those registry settings don't take effect until a reset, so you'd need another method to either dynamically change the sensitivity or capture the value of the pressure as it is being applied.
ok, thanks storm seeing as this would be my first ever program to code I would really appreciate the help..
I was looking at the SDK site last night but didnt quite know what i was looking for, but now ill research the touchscreen driver(s) and how they are accessed by the phone and how we can use them to our benefit.
there is a touch.dll file in the windows folder im wondering if this registers the pressure applied..
Sweet,
I'm also gonna investigate more
Keep you posted
hmmm, i guess the first step would be to create a program that accesses the touch.dll to see if it records pressure applied?
3 guesses as to what you guys want to use this for
SamAsQ said:
3 guesses as to what you guys want to use this for
Click to expand...
Click to collapse
LOL They'd be better off with a Touch Pro. Don't want evidence getting under that recessed screen
e: Bloody great idea though. i'm not sure how it'll really work or how accurate it'll be... An object placed on the screen might have multiple contact points, and as the screen cannot detect multiple points pressure from the weight might be exerted elsewhere on the screen and not detected.
squidgyb said:
lol :d they'd be better off with a touch pro. Don't want evidence getting under that recessed screen
Click to expand...
Click to collapse
hahahahaahahahahahahahahahah :d:d:d:d:d:d:d:d
SquidgyB said:
LOL They'd be better off with a Touch Pro. Don't want evidence getting under that recessed screen
e: Bloody great idea though. i'm not sure how it'll really work or how accurate it'll be... An object placed on the screen might have multiple contact points, and as the screen cannot detect multiple points pressure from the weight might be exerted elsewhere on the screen and not detected.
Click to expand...
Click to collapse
true squidgy, but,
ok but you know on the fish panel?
i can place four fingers on the screen and they will find the exact center lift one finger up they will find the exact center of the three remaining fingers etc etc maybe this can help us in our mission..
so say you have a nice beautiful green flower that is making contact at three seperate points on the screen maybe we can incorporate what is going on in the fish panel to find the center and compare the pressure applied that the touch.dll hopefully will give us, and that we hope to figure by placing weights on the screen
I don't think the SDK will help us in our pursuit... I think it only gives back X,Y pairs...
We'd have to get pretty low level on this one.
The thing is, in theory its actually do-able.
http://www.scribd.com/doc/12804586/fourwire-resistivetype-touch-screen-with-usb-interface
This guy built its own drawing "board" by using a resistive touchscreen. The interesting thing is that he provides two methods of actually calculating the touch resistance which means that
1) it's possible to use it as a balance because the resistance would be dependent on the pressure, and the pressure depends on the mass in our case
2) it doesn't matter how many points you have... There's only one Rtouch so this means it calculates the overall pressure that is exerted onto the touchscreen. Even though you can only determine one X,Y pair...that's of no interest to us...
All this to say that in theory this is actually possible...Only problem is how to access the hardware...
At least this is my take on this, but I might be wrong
dbl post..
stormlv said:
1) it's possible to use it as a balance because the resistance would be dependent on the pressure, and the pressure depends on the mass in our case
2) it doesn't matter how many points you have... There's only one Rtouch so this means it calculates the overall pressure that is exerted onto the touchscreen. Even though you can only determine one X,Y pair...that's of no interest to us...
All this to say that in theory this is actually possible...Only problem is how to access the hardware...
At least this is my take on this, but I might be wrong
Click to expand...
Click to collapse
nice research
cool thats what i was thinking about the screen, but squidgy's thinking seemed logical, but if the resistive screen already calculates the overall pressure thats perfect..
ok so now we know that it is "theoratically" possible we just gotta get to action
im gonna be in vegas this whole weekend so ill try to update my progress when i can
Tool for resistance measurement
If the touchscreen panel that you want to measure is resistive you can measure it's force/displacement and resistance using one of the switch testers offered by a company called TRICOR Systems.
The touchscreen would have to use resistive technology in order to measure the resistance. Most of the newer touchscreens use either capacitive or surface acoustic wave technology.
Is this a common thing known about? The response is not too bad using my fingers, but when using the stylus to move right hand side scroll bars up and down, or to close a window with the 'x' or 'ok' it's nowhere near as responsive as my artemis, and the interfaces on both phones are practically identical. Even doing taps for screen alignment requires much harder pressing than on the artemis. Is there a way to improve the response or does the screen 'wear in' after time and make things faster? The only thing that helped so far was removing the screen protector which seemed to dull the responses even more.
I haven't owned an artemis,but the diamond has the worst screen sensitivity out of the many device's I've had before it,advanced configuration adjustment does nothing that I could feel.....I did read somewhere that they use a harder or thicker screen cover because of it being flush and more prone to damage,which would make sense,but,combined with it's sluggish speed,equal's a device I find barely usable,which is a shame because it has such a nice looking screen.
BTW I'm talking about stylus use,which is mainly what I use 99% of the time.
Yeah, I'd heard about it's bad touch response from someone that owned a diamond and has now put it on ebay. And frankly, as nice looking as it is and with all it's cool new features, I think the artemis is a better phone, slightly bigger screen, more user friendly and far less confusing and fiddly. I can get around my older phone faster with the simpler menus and scroll wheel, and also, the volume in tomtom 6 at 100% on the diamond is much quieter than on the artemis. However, there's a screen sensitivity hotfix that someone posted in the Development and Hacking forum. I was trying to find out which one of the cab files he posted is best for my phone. Has anyone in here tried it for the T-Mobile Compact 4?
This is the thread:
http://forum.xda-developers.com/showthread.php?t=469865&page=28
.
try tf3d config tool.
there is an option to make the fingertouch better
vbakker said:
try tf3d config tool.
there is an option to make the fingertouch better
Click to expand...
Click to collapse
Thanks. Might try it, although, I now installed the iTouch_azharsunny.cab from the development and hacking forum and it seems to have increased the sens quite well. The scroll bar is still not quite as sensitive as my old phone, but quite acceptable mostly.
Not sure if this is a defective hardware problem or just the "normal" result of rooting this device.
Examples:
#1) Touching items on the screen seem to be "off". For example, when I have a list of 4 emails and I "touch" the top one the one below it often gets selected. I have no problem being on "target" on my iPhone so I am good at aiming on small devices.
#2) When I need to select a checkbox at the very left edge of the screen (again in an email app) I rarely am able to select it. Once again, seems like the "touch area" is missing.
It's like I am not "aiming" properly to select what I want but I am extra careful and have no problems on other touch devices.
Is this "just the way it works" or do I possibly have bad hardware? Is there a touch screen calibration utility app out there? That seems to be the problem, it needs to be calibrated.
Thanks.
Anytime I've had issues like this, I just put it into sleep mode and power it back up and the problem seems to be solved.
http://nookdevs.com/Recalibrate_the_NookColor_touch_screen
You may want to give that a try as well.
i used this and it worked great:
http://forum.xda-developers.com/showthread.php?t=934500
smitty0255 said:
i used this and it worked great:
http://forum.xda-developers.com/showthread.php?t=934500
Click to expand...
Click to collapse
Same here; this especially helped with touches near the edges of the screen that would not register 50% of the time.