Related
I just came across this tweak on this website:
http://www.pocketpctweaks.com/pocketpc_tweaks/Minimize_tapping_Pressure
I tried it and it works great. I now use less pressure on the screen.
What ever you do, don’t set the value below the default of 7526. If you do, you may set it too low, the sensitivity will be too low and you will have to perform a Hard reset.
Here is the tweak from the website listed above:
Minimize Pressure when Tapping the screen
Ever got used to tapping without screen protectors and suddenly you put some screen protector and have a pecuilar feeling (some-what like tapping harder than u normally do) due to the increase thickness of the protector?
Well i have gone to that and finally ive done some simple tweaks to my xda mini.
I also figure out this could lessen normal wear and tear(scratching of protectors/PDA screens) since lesser pressure is applied to Tap the screen
here's what i did..
HKEY_LOCAL_MACHINE\SOFTWARE\Drivers\Touch
If not there try here:
HKLM\Drivers\Touchpanel\ Pressure Threshold
or find 'Threshold'
Change the value of Pressure Threshold.(INCREASE value ONLY!!!)
what i did is set the value at 11880.
i tried doubling the default value. until i have reached my desired setting.
now,its like tapping soflty without having a feeling that i have screen protector. Also less stress on the stylus and screen and faster tapping.
WARNING: Only INCREASE THE VALUE BUT NEVER THE DECREASE THE DEFAULT VALUE.
Lowering the value of Pressure Threshold means you need to apply more pressure in tapping than you normally do.
ive tried this and when i soft reset, the screen won't react even if i apply deep pressure in tapping so i needed to do a HARD Reset!!!
So don't ever think of lowering the value, JUST INCREASE but NEVER LOWER!!
Tweak open for comments.
thanks...
Thanks, this tweak worked wonderfully!
I dont use a screen protector (for now at least) and I noticed an improvement in sensitivity as well when I set it to 11880.
disabling the touch pad configuration at startup
is it possible to disable the touch pad configuration at
the initial start up.my touchpad isnt functioning and i
wish anyone would help me with a rom that doesnt allow
you to configure the touch panel so you can go straght to
the system.
my Pda is
tmobile MDA USA
IPL 2.26.
SPL 2.26.
GSM 02.25.11
OS 2.26.10.2
thanks in advance
rusar said:
is it possible to disable the touch pad configuration at
the initial start up.my touchpad isnt functioning and i
wish anyone would help me with a rom that doesnt allow
you to configure the touch panel so you can go straght to
the system.
my Pda is
tmobile MDA USA
IPL 2.26.
SPL 2.26.
GSM 02.25.11
OS 2.26.10.2
thanks in advance
Click to expand...
Click to collapse
I posted a thread about this before. Nobody answered but I finally found the answer on my own. What you have to do is to make sure you have a storage card and put a file called welcome.not in the root of it. There doesn't have to be anything in it, you can just open notepad and save the blank file with that name. That tells the device to skip the whole welcome bit with the touch screen calibration and all that.
I may not have the name exactly right, it's been several months. But if you do a search on threads started by me you can probably find it.
i saw this in another link and they said to put it at 240, i listened and i had to hard reset. thank you for clearing things up buddy
hey, the link for the program is bad i was wondering if any one could post the a link for it i have looked everywhere. I have a prob. alighning screen and would like to see if changing the sensitivity will somehow help.
Use Schap's Advanced Configuration Tool. Saves you a ton of brainwork, since it's just doing the registry edits for you. Can also be used to tune your Bluetooth Stereo setup, and a host of "basic" UI modifications.
Hi all at this forum
The Link±
Increase the sensitivity of Touch Screen
I just came across this tweak on this website:
http://www.pocketpctweaks.com/pocket...pping_Pressure
dont work anymore...
Has anybody got an actial link???
And... Does this work for a samsung i900?
With regards
VArmand
Works great for me - thanks colouro
For the max senstivity set both fingerpressure and threshold to -1 or FFFFFFFF in Hex..
When I upgraded my Galaxy S to Froyo (XWJPA), I noticed quite a loss in touch screen sensitivity. I was used to making small "jabs" to switch pages in the launcher, and with the new and improved "sluggish" touchscreen, that was no longer possible: I had to really drag the thing instead of just throwing it.
So I had a look at the Samsung kernel source and found that:
drivers/input/touchscreen/qt602240.c.
To control the touchscreen parameters, just do a "echo XYYY > /sys/class/touch/switch/set_touchscreen" where X controls which parameter is affected and YYY is the value:
* sensitivity: X=7 (default 7040)
* minimum duration to register touch: X=8 (default 8002)
* minimum motion: X=11 (default 11003)
* motion filter: X=13 (default 13046)
* maximum multi-touch points: X=14 (default 14005)
So in my case, I used:
cd /sys/class/touch/switch
echo 8000 > set_touchscreen
echo 13008 > set_touchscreen
... and my TouchWiz is flying again!
For a laugh, try "echo 7005 > set_touchscreen". Your touchscreen is now so sensitive that it registers "touch" events from as much as 3 millimeters away. It *may* go a little crazy, though
I don't know if this'll be of any help, but the AT42QT602240 is the capacitive touchscreen sensors from Quantum, bought by Atmel in 2008, and used in their maxTouch (formerly Qtouch) multi-touch gizmos:
Atmel mXT224 (AT42QT602240)
alcom.be/binarydata.aspx?type=doc/Atmel_maXTouch.
maybe this GPL code from Patchwork will help:
patchwork.kernel.org/patch/108363/
Sorry for the truncated addresses but it's my first post and I can't post links yet, forum rules
Bump .
Thanks for bump, actually. Its nice to take control of those features
Lol: it actually it can work as 'non-contact' touch screen... This might be interesting for users having their hands dirty often and gloves wearers
Finally! Amazing. I have always felt that JM9 was way smoother than any of the 2.2 roms and seems that it was because of the touchscreen parameters.
exxos77 said:
When I upgraded my Galaxy S to Froyo (XWJPA), I noticed quite a loss in touch screen sensitivity. I was used to making small "jabs" to switch pages in the launcher, and with the new and improved "sluggish" touchscreen, that was no longer possible: I had to really drag the thing instead of just throwing it.
So I had a look at the Samsung kernel source and found that:
drivers/input/touchscreen/qt602240.c.
To control the touchscreen parameters, just do a "echo XYYY > /sys/class/touch/switch/set_touchscreen" where X controls which parameter is affected and YYY is the value:
* sensitivity: X=7 (default 7040)
* minimum duration to register touch: X=8 (default 8002)
* minimum motion: X=11 (default 11003)
* motion filter: X=13 (default 13046)
* maximum multi-touch points: X=14 (default 14005)
So in my case, I used:
cd /sys/class/touch/switch
echo 8000 > set_touchscreen
echo 13008 > set_touchscreen
... and my TouchWiz is flying again!
For a laugh, try "echo 7005 > set_touchscreen". Your touchscreen is now so sensitive that it registers "touch" events from as much as 3 millimeters away. It *may* go a little crazy, though
Click to expand...
Click to collapse
For all us non devs could you possibly explain a little more how this is done? Thanks
Sent from another GALAXY
Hardcore, can you please look into this for your next kernel version?
Sent from my GT-I9000 using Tapatalk
Hi.
Any one could make an update file for this solution to setup from recovery?
Sent from my GT-I9000 using Tapatalk
This is interesting, I too thought that touch response was much better on eclair
Sent from my GT-I9000 using XDA App
It is actually working and you can feel the changes in real time
Ok for the noobs around here ...
do you run the commands on pc via adb ? or on the phone via an android terminal emulator ? root needed ? etc ...
What command I could use to get current values for the parameters?
Ok answered my own question it seems a terminal emulator on the phone does the job...
Do NOT try the supersensitivity thing though ( 7003 ) it will mess up your phone and you won't be able to use terminal to type anything ... soft reset fixes it though...
I think this isn't 100% correct:
Code:
To control the touchscreen parameters, just do a "echo XYYY > /sys/class/touch/switch/set_touchscreen" where X controls which parameter is affected and YYY is the value
if I understand correctly, we must use "echo XXYYY > /sys/class/touch/switch/set_touchscreen"
So the line to type via adb shell are:
Code:
cd /sys/class/touch/switch
echo 08000 > set_touchscreen
echo 13008 > set_touchscreen
And for a laungh try: "echo 07006 > set_touchscreen"
This sets the sensitivity to the maximum practical you can use the touchscreen without "touch"
Interresting finding , thanks !
Will test that one
Thanks again for sharing
Will these settings keep after a reboot?
And also, there are 2 methods described in this thread, are both correct or is just one of them? I used the method described in the first post and it seems to work just fine.
Thanks for the find.
AlexandreT said:
Will these settings keep after a reboot?
And also, there are 2 methods described in this thread, are both correct or is just one of them? I used the method described in the first post and it seems to work just fine.
Thanks for the find.
Click to expand...
Click to collapse
Yes they stay after a reboot
rigor.m said:
Ok answered my own question it seems a terminal emulator on the phone does the job...
Do NOT try the supersensitivity thing though ( 7003 ) it will mess up your phone and you won't be able to use terminal to type anything ... soft reset fixes it though...
Click to expand...
Click to collapse
OMG guys! little help here.
i type thihs"echo XYYY > /sys/class/touch/switch/set_touchscreen" on my SGS using a terminal emulator" and the touch screen totally not responding.
Any advice?
========================
update: after a while the screen sensitivity came back. phew!
manosv said:
Yes they stay after a reboot
Click to expand...
Click to collapse
Are you sure? I think it doesn't.
matsuru said:
OMG guys! little help here.
i type thihs"echo XYYY > /sys/class/touch/switch/set_touchscreen" on my SGS using a terminal emulator" and the touch screen totally not responding.
Any advice?
========================
update: after a while the screen sensitivity came back. phew!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=11258219&postcount=14
Dear all,
has anyone tried
==> SGS Touchscreen Booster
that is available for free on the market ?
Seems to do similar tweaks with a comfortable UI
I think I'll give it a try
Also, when I apply
cd /sys/class/touch/switch
echo 8000 > set_touchscreen
echo 13008 > set_touchscreen
Click to expand...
Click to collapse
I notice that the screen kind of wobble (especially when holding my finger on a page I'm reading in the browser)
am I the only one ?
Thanks !
I have better keyboard pro but I am running hyperdroid which has the density set at 167, making the keyboard smaller.
Is there any way that I can make the better keyboard bigger?
Im not sure, as i havent tried that rom, but if you have spare parts installed, try turning off compatibility mode, reboot and see if it works. or you can always edit your build.prop lcd density.
snyper2k2 said:
I have better keyboard pro but I am running hyperdroid which has the density set at 167, making the keyboard smaller.
Is there any way that I can make the better keyboard bigger?
Click to expand...
Click to collapse
There's an app in the market called LCD density changer, you could try that..
I would personally like to know this too. I would like to have low density with a normal size keyboard. I have tried turning off compatibility mode.
ive done a little testing myself now, running hyperdroid and same key board. i couldnt get it to work right til i un-installed it after turning compat mode off and restarting. so maybe it will work for you this way,,, un-install it, turn compat mode off and resart, best to turn off phone then back on really. after re-start, re-install and see if it is full screen. good luck!
Same issue here. Interesting problem -- the HyperDroid rom with CM7 on my HD2 *came* with a 167 density setting (tiny fonts) but a large keyboard (sized as if density were 240). I wanted to change the size a bit and set the density to 200, and then the keyboard got *smaller*. Now they are correlated and I can't get back to the way it was originally. Love to hear if anyone has this figured out. There must be a separate setting somewhere for the keyboard size.
hey all
as i found, we edit /system/build.prop as follow
change
qemu.hw,mainkeys=0 can enable softkey
change
ro.sf.lcd.density=240 we can change the resolution ratio
but when i change the value of ro.sf.lcd.density from 240 to 260 and reboot
the screen size of HD2 become ugly, font size are too big and cover one by one.
and the icon became more big too
which parameter can i change to fix this issue
all i want to do is resize the bottom navigation bar without changing anything else.
my current ROM is HD2 android [4.0.4][720p] NexusHD2-ICS-CM9-HWA V2.9a [NativeSD]
hope you guys can help me
I usually find mine in the settings & set it to around 24 so that it can be as small as possible
mengfei said:
I usually find mine in the settings & set it to around 24 so that it can be as small as possible
Click to expand...
Click to collapse
yes, but i try to find a usual method to config it out, many of ROMs doesn't give a UI support of this issue
OP, try to follow these instructions
http://forum.xda-developers.com/showthread.php?t=2227668
The density setting in build.prop changes every size onscreen not just the bottom like you need.
Sent from my SGH-T889 using xda app-developers app
How to adjust your DPI without root, I believe the current DPI is around 300 I could be wrong.
To adjust the DPI follow the steps below, THIS DOES NOT REQUIRE ROOT.
Open settings and scroll all the way down to About
Open Software Information
Tap the build number quickly a couple times till it says "You're now a developer"
Head back into the main settings page and open the new Developer Options
Enable USB debugging
Install ADB on your computer (there are plenty of tutorials out there if you don't know how)
Start ADB and check if you see your device by typing
Code:
adb devices
If you see your phone go ahead and type
Code:
adb shell wm density 250
Reboot your phone to apply the effects system wide.
250 is the DPI set which I think looks the best for me. Adjust how you like it
NOTE: IT WILL LOOK WEIRD AT FIRST, REBOOT YOUR PHONE!
This is a great method. Use it often. Couple more commands:
Code:
adb shell wm density reset (set to default)
adb shell wm size 1080x1920 (emulate whatever resolution)
adb shell wm size reset (set to default)
What Screen Resolution have you chosen?
Chinaphonearena said:
This is a great method. Use it often. Couple more commands:
Code:
adm shell wm density reset (set to default)
adm shell wm size 1080x1920 (emulate whatever resolution)
adm shell wm size reset (set to default)
Click to expand...
Click to collapse
I noticed in the pics from your review consisted of smaller icons. I am assuming you changed the DPI to 250. I would like to know if you have tinkered with your screen resolution as well. If yes can you show us some screenshots? Does that have any other benefits like battery performance and processing speed?
sanjeevopeth said:
I noticed in the pics from your review consisted of smaller icons. I am assuming you changed the DPI to 250. I would like to know if you have tinkered with your screen resolution as well. If yes can you show us some screenshots? Does that have any other benefits like battery performance and processing speed?
Click to expand...
Click to collapse
Yes, you're correct the dpi was changed. There's no performance gain I see. I do this so I can fit more on the screen at once within apps, while browsing etc... For me this is half the value of an HD device - you can shrink stuff down to fit 2x as much, but tiny text still remains comfortably legible.
This can also be done within terminal emulator. For me, not successful unless entering su.
nice way to adjust animations on your phone..its now fast without the animation by the way i need help i accidentally touch the Logger Buffer Sizes....its under settings..developer options...scroll down you will see. logger buffer sizes...now there are number to choose from..64k..256k...1m...4m...16m.... now would like to ask if what is your default value in your phone"? want to do default...whats the diffence it do when you change those settings 64...256...etc....tnx
pato2015 said:
nice way to adjust animations on your phone..its now fast without the animation by the way i need help i accidentally touch the Logger Buffer Sizes....its under settings..developer options...scroll down you will see. logger buffer sizes...now there are number to choose from..64k..256k...1m...4m...16m.... now would like to ask if what is your default value in your phone"? want to do default...whats the diffence it do when you change those settings 64...256...etc....tnx
Click to expand...
Click to collapse
Mine is 256k. That should be how much data is held in the logs.
thanks...got it...it just goes to default by itself when closing developer option......
This is pretty cool, is there an adb command to readout the density what ever it's currently set at?
I ended up at 390, it gives a nice 5x5 grid.
Thanx, work fine! A little notice: Asus Powermanagment end in force closed when you change the DPI. Went back to orig. 480 and it works, when you need it
And next big issue Swift key doenst work with changed DPI. When changed i saw only a few very!! big letters. Keyboard not useable.
Thanks OP!
The issue with swiftkey is well known and documented, just search Google for it (XDA says I don't have enough posts to post links yet). It looks like there's a fix, but it requires root. I switch to the Google keyboard and it works fine with modified DPI.
FYI, density setting of 460 is the lowest (stock is 480) that will keep the widget width taking up the whole screen for wide widgets. Makes everything a little sharper than stock, which was needed.
The hardware keys below the screen also stop working when the screen resolution is changed.
tasar said:
Thanx, work fine! A little notice: Asus Powermanagment end in force closed when you change the DPI. Went back to orig. 480 and it works, when you need it
And next big issue Swift key doenst work with changed DPI. When changed i saw only a few very!! big letters. Keyboard not useable.
Click to expand...
Click to collapse
ZenMotion touch gestures config also crashes.
As for swiftkey, you could probably use xposed appsettings to adjust its dpi/dp settings.
ziddey said:
As for swiftkey, you could probably use xposed appsettings to adjust its dpi/dp settings.
Click to expand...
Click to collapse
I have test it with AppSettings at first but no luck or i do something wrong. I have set DPI to 480 all other at default but same as before.
tasar said:
I have test it with AppSettings at first but no luck or i do something wrong. I have set DPI to 480 all other at default but same as before.
Click to expand...
Click to collapse
Try a different DPI. 480 is extreme and some apps simply won't work properly at such a high setting.
After doing this, how to revert to the original one???
dineshdotcom2000 said:
After doing this, how to revert to the original one???
Click to expand...
Click to collapse
adb shell wm density reset
Chinaphonearena said:
Try a different DPI. 480 is extreme and some apps simply won't work properly at such a high setting.
Click to expand...
Click to collapse
480 is original dpi
tasar said:
480 is original dpi
Click to expand...
Click to collapse
Tasar, I stand corrected. 480 it is.
Application settigs
Anyone having problems with some applications after using this mod? I am having issues with viber(photos sent wont open properly- always zoomed in and i cannot see the entire photo and no option to be zoomed out) and instagram as well. Hope anyone can help me with this. Thanks
Photo Studio pro the same problem, see only a quarter of the pic, cant zoom it to full. App settings doenst help