Related
I've searched long and at any places, but nowhere was an answer. Everybody goes crazy if we talk about sensitivity, but what are the benefits of a higher sensitivity really?
I mean, here on mother earth, you can't get something better, without decreasing other features...
So if i turn the sensitivity higher (or lower), i mean if its more precise... Where are the disadvantages?
Higher battery drain?
Please help me to understand
I you slide you finger over the screen it takes a small distance before the phone reactes and moves the part of the display. Try it and you will notice this small distance on the homescreen. It is like a dead zone where you move your finger but nothing happens.
With the toch sensitivity fixes or apps or scripts you can decrease this distance to 0 or any other value. I think a value around 5 is quite common. I am not sure but I thought 15 is default, so you usually want to decrease it.
A disadvatage is, that if you set it too low, the phone might recognize klicks a swipes.
Schindler33 said:
A disadvatage is, that if you set it too low, the phone might recognize klicks a swipes.
Click to expand...
Click to collapse
That was the answer i wanted! Thank you!
On some older kernels, when your phone is on ac power, the screen becomes very unresponsive. That's why people came up with the need to change the touch sensitivity.
Sent from my GT-I9100 using Tapatalk
Are there other ways to increase the touchscreen sensitivity? or Increase the X10 multi-touch Accuracy?
I want to ask this question too, but just specific on accuracy.
When I use apps to test the muiltitouch function, it will show a completely wrong result when I using two fingers.
It just show the result just like a "X"
(Assume that the end points of \ are my fingers and the end points of another / are the result)
eh_hk said:
I want to ask this question too, but just specific on accuracy.
When I use apps to test the muiltitouch function, it will show a completely wrong result when I using two fingers.
It just show the result just like a "X"
(Assume that the end points of \ are my fingers and the end points of another / are the result)
Click to expand...
Click to collapse
jrchan01 said:
Are there other ways to increase the touchscreen sensitivity? or Increase the X10 multi-touch Accuracy?
Click to expand...
Click to collapse
Short answer = (almost) "Impossible"
Almost cuz - you can maybe get the Multi-touch if you write the drivers from scratch (I guess you aren't good to driver coding )
Guys, accuracy and sensitivity are the opposite of capacitive touchscreens...
Its the bad on their technology and it is currently impossible to adjust their performance.Hw doesnt support it.
All is caused by massive "cool" fingerfriendy display hungry population.
Btw I am still crying for good phone with stylus performace screen capable for drawing...
So...
maybe I just pretend I am using a phone without muiltitouch
Just wanted to let everyone know TouchScreenTune in the app store is compatible with Da_Gs 0.2 debug kernel.
It takes a while to open the first time, you will need to click wait when the non response pop up comes. This hasn't happened since i first opened it.
You can use it and see how you like it without paying, it loses the settings after the screen shuts off.
If you like it pay $5 to register and keep your settings.
It's a pain to pay $5 for something the Note should come with, but it's better than having an unusable pen for detailed field mapping.
Hats off to Da_G for providing the debug version of his kernel.
so have you got yours to actually work correctly with this app. I played with it for a min but didnt seem to help much. If you have what settings did you use?
bkeaver said:
so have you got yours to actually work correctly with this app. I played with it for a min but didnt seem to help much. If you have what settings did you use?
Click to expand...
Click to collapse
Were you using Da_Gs 0.2 kernel with kallsyms, the debug version ( it's the only one i know that works) and you have to wait awhile for it to first load.
If you did all of that then set and apply the offsets to their max values to confirm that it works, this will put the point way off from the s pen.
I've been able to get my pen to mark spot on
thanks I will give that a try...
your right.. worked like a charm...
I get my pen spot-on by just drawing along (and crossing over) the screen edges. Occasionally i can do it just by holding the pen at about a 45 degree angle and pressing down, then slowly holding it perpendicular (90 degrees) and down to the other side at 45 degrees and back again while continuing to press down. One of the two methods have yet to fail calibrating the pen for me.
Seems to drift often though, but I then I just repeat the process whenever necessary.
EDIT: Using the app, does it drift over time? Do you have to re-calibrate occasionally?
Is anyone able to play with the Archos 80 9g?
I got the Turbo 1,5ghz version but im not able to play frontline commando or shadowgun because the touchscreen is.. how should i say.. maybe unresponsive?
it feels like the touchscreens resolutions itself is very low and you cant aim precisely. Using latest Archos ICS (4.06 atm)
cheers
*snip*
I have the same issue..maybe a anti reflex display protection might work? I know that they make a smooth and "soft" feeling!
Ncyde47 said:
Is anyone able to play with the Archos 80 9g?
I got the Turbo 1,5ghz version but im not able to play frontline commando or shadowgun because the touchscreen is.. how should i say.. maybe unresponsive?
it feels like the touchscreens resolutions itself is very low and you cant aim precisely. Using latest Archos ICS (4.06 atm)
cheers
Click to expand...
Click to collapse
I noticed the exact same thing.
I installed the following app from the Play store:
Input Benchmark (not allowed to post external links yet)
It's really simple and it has only three tests: Touch, Accelerometer, Multitouch.
Touch test shows the frequency of the touch events. My G9 shows only 50 to 52 touch events per second if you move your finger really fast. My phone (Samsung Galaxy Spica) shows 60 events per second.
Accelerometer shows around 130 events per second, and my phone shows around 100 events per second.
The multi-touch test shows the pixel positions of all touch points. My phone can detect sub-pixel changes. After you calculate the touch resolution it recognizes around 1024*1024 touch points on a 3.2 inch screen (480x320).
My Archos G9 80 Turbo shows only around 227*227 touch points. Usually the touch quantization works out to 3.37335 pixels vertical and 4.4978 pixels horizontal. This means that the touchscreen cannot resolve finer movements, and this is the reason why homescreen scrolling from left to right looks very choppy if you keep your finger on the screen, and much smoother if you fling (start the transition with rapid finger movement and take the finger off of the screen). Sometimes I got other pixel values that were about in between other the values I usually got. I think that this means that the touchscreen is at least capable of double the current precision (probably around 512*512 touch points), but it still lags behind my phone from 2009/2010.
In the teardown tread the touchscreen controller is identified as Cypress TMA 340. I found some Cypress presentations that classify this as a 3rd Generation touchscreen controller that is intended for screens with less than 5.1" diagonal, with a notice that 4 point multi-touch should be used on screens smaller than 4.6 inches.
I found that HTC Sensation (that had a lot of touchscreen issues) also uses a Cypress TMA 340 series 4-point multi-touch digitizer as a replacement digitizer (there are at least 4 different digitizers used on the Sensation production). On a international HTC Sensation I get around 1024*1024 touch points resolution @ 60 touch events per second, so the controller should be capable of at least that. It isn't ideal for our screen size but it would be a significant improvement over the current situation.
This means the issue could be either hardware (the capacitive matrix is low-res), or software (the driver is broken or poorly written). If the issue is hardware, we can't do anything about it (except to perhaps replace the digitizer with a better one, and add support for it in the kernel). If the issue is software, we maybe get some improvement later via improved or tweaked drivers (Cypress has released their drivers as open source)
Perhaps there is a trade off between 4-point multi-touch and 2-point multi-touch, and we could get better touch resolution if we allow only 2-point multi-touch.
neur0mans3r said:
...
My Archos G9 80 Turbo shows only around 227*227 touch points. Usually the touch quantization works out to 3.37335 pixels vertical and 4.4978 pixels horizontal. This means that the touchscreen cannot resolve finer movements...
Click to expand...
Click to collapse
This explains why when using a stylus and drawing a diagonal line I see an image that looks like a fine staircase rather than a smooth line.
So what can we do?
Does any1 know if Archos is aware of this fact?
Anyone willing to downgrade to honeycomb and test? Then we can know if its a kernel problem or a hardware problem
I made a basic test that displays the touch data provided by Android. For my G9 80 it shows a touchscreen resolution of 2048x2048, but in most cases the actual resolution is much lower.
When you move your finger horizontally or vertically, the difference between touch points on the main axis (the direction your finger is moving) is around 9 points (around 4.5 pixels horizontally and 3.37 pixels vertically). However, on the other axis you get much better results (all the way down to 1 touch point). The apparent touchscreen resolution depends on the angle between the motion of the finger and the horizontal and vertical axises of the digitizer.
To recap, in the most basic use case when moving your finger horizontally to navigate homescreen and app drawer, you get stuttering because the touch events are reported like that, not because the hardware is slow to render.
Since in games you usually move your fingers in the direction you need them to go this does not work as expected because the aiming jumps around too much.
I really hope this is a driver issue (some sort of poorly written averaging filter).
Shano56 said:
Anyone willing to downgrade to honeycomb and test? Then we can know if its a kernel problem or a hardware problem
Click to expand...
Click to collapse
I am on Honeycomb most of the time (my Gen9 doesn't like ICS)
Gen9 101 1GHz 512MB, using Input Benchmark:
Touch- 62-75 Hz
Accelerometer- 125-130 Hz
Multitouch- max x-y is correct (1280x800) but touch point move is registered
a)for "normal" speed- every 4-5 pixels for X and every 3-4 pixels for Y
b)for slow speed (press a finger to the touchscreen and tilt it slowly left/right)- readings are inaccurate- it registers 1 pix for X and 1 pix for Y but there is plenty of places where registered point "goes back" (eg- 630->tilt right->blinks between 627 and 631) and/or touch is not detected (this also flickers)
neur0mans3r said:
My phone (Samsung Galaxy Spica) shows 60 events per second.
Click to expand...
Click to collapse
I guess you use tom3q's CM7?
Were you by any chance using FrankenKenrel or FrozenLake previosuly?
gen_scheisskopf said:
I guess you use tom3q's CM7?
Were you by any chance using FrankenKenrel or FrozenLake previosuly?
Click to expand...
Click to collapse
Yes, tom3q's CM7 with the underclocked-overclocked-synced kernel (sound silly but is an accurate description) . I was mainly using Yonip kernels with FroYo.
I made a simple test app (attached in the above post) that shows the difference in the coordinates of touch events in pixels and touch points themselves. I tried it on a HTC Sensation and it's working OK with sub-pixel precision.
It looks like this behavior is not ICS specific, but Archos specific (maybe even G9 80 specific).
neur0mans3r said:
Yes, tom3q's CM7 with the underclocked-overclocked-synced kernel (sound silly but is an accurate description) .
Click to expand...
Click to collapse
I know what you mean, I did some pre-alpha tests for tom3q
neur0mans3r said:
I was mainly using Yonip kernels with FroYo.
Click to expand...
Click to collapse
Competition.....
FrankenKernel was for Ecalir btw
neur0mans3r said:
I made a simple test app (attached in the above post) that shows the difference in the coordinates of touch events in pixels and touch points themselves. I tried it on a HTC Sensation and it's working OK with sub-pixel precision.
It looks like this behavior is not ICS specific, but Archos specific (maybe even G9 80 specific).
Click to expand...
Click to collapse
Tested and
-"normal" speed 4-5 pixel precision for both X and Y
-slow speed- 4-5 pixel precision for the main movement axis and at the same time 1 pixel precision for the second axis
gen_scheisskopf said:
Tested and
-"normal" speed 4-5 pixel precision for both X and Y
-slow speed- 4-5 pixel precision for the main movement axis and at the same time 1 pixel precision for the second axis
Click to expand...
Click to collapse
I think the difference in touch points is more representative because we get an integer (4-5 pixels is 9-10 touch points).
Main question is can this be fixed (or atleast improved somewhat) with a driver update/fix, or is this a limitiation of the digitizer.
P.S. I skipped Eclair and went straight to criminal's CM 6.1.
neur0mans3r said:
I think the difference in touch points is more representative because we get an integer (4-5 pixels is 9-10 touch points).
Main question is can this be fixed (or atleast improved somewhat) with a driver update/fix, or is this a limitiation of the digitizer.
Click to expand...
Click to collapse
Main question- how outdated are drivers and touchscreen firmware (if present), and who wrote them (read: can we source newer/not broken/just better ones?)
neur0mans3r said:
P.S. I skipped Eclair and went straight to criminal's CM 6.1.
Click to expand...
Click to collapse
SM-Froyo by any chance?
gen_scheisskopf said:
Main question- how outdated are drivers and touchscreen firmware (if present), and who wrote them (read: can we source newer/not broken/just better ones?)
Click to expand...
Click to collapse
Look in the hardware hacking thread, it looks like we only need to set a smaller active distance value in the controller configuration. I think the default value (8) is used (maybe the active distance value is not even configured explicitly so it defaults to 8).
gen_scheisskopf said:
SM-Froyo by any chance?
Click to expand...
Click to collapse
I used Voku's CM Mod+X for quite some time also, but then the phone would freeze and/or crash when using 3G to surf while commuting. After I lost data due to a damaged /data ext2 partition, I switched to CM7.4. It's really stable for me (over 400h uptime today, battery lasts 3 days since I don't use the phone much).
neur0mans3r said:
Look in the hardware hacking thread, it looks like we only need to set a smaller active distance value in the controller configuration. I think the default value (8) is used (maybe the active distance value is not even configured explicitly so it defaults to 8).
Click to expand...
Click to collapse
I've seen your post. Unfortunately I don't have enough time to dig in sources now
neur0mans3r said:
I used Voku's CM Mod+X for quite some time also
Click to expand...
Click to collapse
...which is based on SpicagenMod
gen_scheisskopf, by any chance, have you tried new 4.0.7? What problems did your G9 have on ICS? I suggest you RMA that s***
Shano56 said:
gen_scheisskopf, by any chance, have you tried new 4.0.7?
Click to expand...
Click to collapse
Nope, last ICS I used was 4.0.6-test4
Shano56 said:
What problems did your G9 have on ICS?
Click to expand...
Click to collapse
-device gets hot quite fast and it's quite hot even when I use not very demanding apps (pdf readers mostly)
-connected with above- shorter battery life
-there are system freezes (reset required) even when using not very demanding apps
-there seems to be a problem with memory management- sometimes using "ram heavy" app (like Firefox or Aurora) shell restarts
Shano56 said:
I suggest you RMA that s***
Click to expand...
Click to collapse
I have to contact service anyway- charger died
Anyway before that I have to return to stock partition layout (and I need tablet right now, still 5 test to pass, all materials are in pdf and reading them on a PC is killing me)
Tell them your GPS doesn't work or something, they'll say its a hardware error and replace it
Shano56 said:
Tell them your GPS doesn't work or something, they'll say its a hardware error and replace it
Click to expand...
Click to collapse
I don't know what is required to replace the device (maybe I'll run an infinite benchamark loop on ICS with tablet wrapped in a blanket or something? )
gen_scheisskopf said:
I don't know what is required to replace the device (maybe I'll run an infinite benchamark loop on ICS with tablet wrapped in a blanket or something? )
Click to expand...
Click to collapse
my otg usb port/charger port stopped working like many others, i simply said the device no longer received a charge (wasn't sure if it was the chargers fault or the tablets fault) and they said to ship the tablet and shipped a replacement to me after they received.
I've had S10, two S20's and now S21. They all have one thing in common... The fingerprint sensor does not work. I would guess my fingerprint success rate at about 20% accuracy. My S21 fingerprint sensor fails the first time every time. No matter how many times I re-enter my fingerprints. I thought the new fingerprint sensor in the S21 would be better, it isn't.
By accident, reading Flipboard, somebody posted a story on how to speed up android phones. I did what the article recommended. My phone did indeed seem faster, but there was an additional benefit, my fingerprint sensor went from 20% accuracy to well over 90%. Works almost every single time now.
Make sure developer mode is enabled (go to settings > about phone > tap build number a few times).
Go back to settings, at the bottom will be developer options > drawing section.
Three entries;
Window Animation Scale
Transition Animation Scale
Animator Duration Scale
All settings are default 1x.
Change all three settings to either .5x or zero.
Enjoy!
Sorry, but this solution doesn't make any sense.
Fingerprint on my S21 works great. Since dy one
goTouch said:
Sorry, but this solution doesn't make any sense.
Fingerprint on my S21 works great. Since dy one
Click to expand...
Click to collapse
Oh, I guess that means mine works great too. And, nobody else has ever had a problem with the Samsung fingerprint sensor. Got it.
I mean, the animation scale has nothing to do with the fingerprint sensor. So it's not that his works great and yours doesn't, but it's like saying you can fix your car's engine if you just eat 3 extra apples per day. Nothing to do with one another.
What exactly is the reasoning behind how this helps the fingerprint sensor? and what exactly is it doing? Are there any downsides to this?
Like I was saying, I changed the settings just out of curiosity because the originator of the article mentioned that the changes make your phone appear to run faster. Nothing was mentioned about the fingerprint sensor. But, after making the changes, I immediately noticed that my fingerprint sensor started working. It was very dramatic as my sensor would fail the first time every time, and maybe 50% of the time on the second attempt. It was not unusual for me to have 5 failures in a row, locking the sensor for 30 seconds, multiple times a week.
My sister has a N20 Ultra and her sensor was so bad she quit using it. I contacted her about changing those settings, which she did, and her sensor started working too. This isn't my first rodeo, I've had a history with Samsung and their under display sensors. Mine has never worked going back to the S10.
I can't explain why changing these settings affect the sensor, but they do. I just changed back to 1x and my fingerprint sensor started failing just like it always has. Changed back to .5x and it starts working again. Sometimes I get the sense my sensor is not actually attempting to read fingerprint, just fails repeatedly. My guess is because the screen draws animations faster, the fingerprint sensor animation is faster too. Maybe that has something to do with it? So, analogy of car engine and apples isn't applicable. There might actually be some connection here.
Bottom line, it takes 30 seconds to change settings so you can easily do it and revert back just as quick. There seems to be nothing to lose, so...
I've noticed a substantial decrease in battery life with the changes from 1x to .5x. I reverted back to 1x and redid my fingerprints, once focusing on the center of the sensor and then a 2nd entry for the same finger focusing on the edges of the sensor. I'm going to have to live with this until the next non-Samsung phone comes along that I want to try...
Animation sucks up cpu, which slows down fingerprint.
No animation is best, what do I need fancy effects to tell me what I'm already doing lol
This entire thread reads like an April Fools joke.
This is the first time I am using on screen fingerprint reader. Absolutely hated it. However, over the days I have developed muscle memory and my finger goes to the correct spot. My accuracy went from 40 to 90% in the last month or so.
There are few things that can be done to improve finger print reader
- Use both the thumbs in one fingerprint
- Scanning along the edges of the scanner location.
THere are you tube videos that explain this in detail.
Additinal tip. I have enabled lift to wake and faceunlock as well. This has helped me faster unlock pretty much every time i pick up the phone.
PS: To me on the screen reader is more of a gimmick, it will take a few more generations to get this working very well for everyone.
There is space near the camera on the back where samsung could have place the reader.
This will give you additonal finger gesture features. Like in note 9 you can pull down and push up the norification bar and so on. ANyways this is a lost cause.
Gopa
Techvir said:
There are few things that can be done to improve finger print reader
- Use both the thumbs in one fingerprint
Click to expand...
Click to collapse
Don't do this. Scan each thumb twice, and it will work better. I usually do my right thumb 3x, my left thumb once, and my pointer finger once. Works perfectly for me, I'd say 99.9% of the time.
entropism said:
Don't do this. Scan each thumb twice, and it will work better. I usually do my right thumb 3x, my left thumb once, and my pointer finger once. Works perfectly for me, I'd say 99.9% of the time.
Click to expand...
Click to collapse
Oh wow, how did you manage to register 5 fingerprints? I can only register a maximum of 4.
yeah_mike said:
Oh wow, how did you manage to register 5 fingerprints? I can only register a maximum of 4.
Click to expand...
Click to collapse
Sorry, I have a **** ton of phones laying around. Some let you scan 5 times, others 4.
robnitro said:
Animation sucks up cpu, which slows down fingerprint.
No animation is best, what do I need fancy effects to tell me what I'm already doing lol
Click to expand...
Click to collapse
I HATE animations. They were cute maybe the first two times but after that I was done with them. And having to enable dev options is stupid. I use several apps that either complain about dev options being enabled or just plain won't run at all. No animations should be a normal selectable item like wallpaper.
overclockxp said:
I HATE animations. They were cute maybe the first two times but after that I was done with them. And having to enable dev options is stupid. I use several apps that either complain about dev options being enabled or just plain won't run at all. No animations should be a normal selectable item like wallpaper.
Click to expand...
Click to collapse
To be honest, I thought I was the only one who truly hated animations. These seem extremely unnecessary and a little bit tacky.
yeah_mike said:
Oh wow, how did you manage to register 5 fingerprints? I can only register a maximum of 4.
Click to expand...
Click to collapse
Same here, I actually thought it was impossible to register 5 fingerprints, considering that I’ve been only able to do 3 or 4 max.