Looking at the screen under bright light at an angle, I was able to see the matrix of sensors under the glass: 30 rows and 40 columns for a total of 1200 sensors.
Thus, the number and spacing of sensors is similar to other good quality tablets (Asus, Motorola, Samsung) and much better than cheaper brands (i.e. Le Pan).
I'm not sure how relevant this information is but I didn't find it on any forums or on the Web.
Anybody has this info?
Thank you.
Interesting. I wonder how this can affect how many touches it can sense.
Sent from my MB860 using XDA
ten. it can sense ten fingers on the screen at the same time.
download the multitouch tester from the play store and try it out your self.
honestly the only way it can be usefull, is for piano apps
I am more interested in the accuracy of the touch screen which I believe is related to how dense the sensors are. This density will have a greater impact when smaller areas are to be touched (like hyperlinks in browser, small keys on keyboard etc) - or am I wrong?
mikey_xda said:
I am more interested in the accuracy of the touch screen which I believe is related to how dense the sensors are. This density will have a greater impact when smaller areas are to be touched (like hyperlinks in browser, small keys on keyboard etc) - or am I wrong?
Click to expand...
Click to collapse
Right. More sensors = better accuracy.
Related
Ok, some people were confused as to what my problem was with my other post, They thought it was a performance lag issue; possibly due to low memory. So I am reposting, I am also making it a poll, as some mentioned that a downgrade fixed this behavior on there units.
I have noticed my touch screen does not have smooth response in apps. To confirm I downloaded a app that tests mulitouch; I used "multitouch vis test".
When moving my finger quickly, or swiping, the finger tracking of the touchscreen seems fine. The problem arises when moving slowly or making small movements of less than 10 pixels; that is when you can see that the touchscreen does not track smoothly. You can see the output on the screen stay in one position as you slowly move your finger, then suddenly jump several pixels. It repeats this process as you continue to move slowly, often times the output on the screen is still lagging behind your finger. (it is not centered under your finger even after the jump) This happens even on a fresh boot, and I have tried the touchscreen calibration several times.
Overall it seems like the touch detection is low resolution, and can not detect fine/small movements. If the ones claiming it is dependent on firmware version are correct, then this could be fixed by Archos. If I get enough responses to the poll, I will contact Archos if the results point in that direction. If this is a fairly rare issue, then I know my A70 is defective.
Edit: From the responses here, it seems that the display can detect point touch to a very fine degree. The problem is that the movement detection algorithm is low resolution; the device has to detect movement of several pixels before outputting that movement. That means it can be fixed within software. (unless it is built into the touch screen controller chip)
I run calbrate touch screen and it`s now Ok.
Did you try this?
ncuxxx said:
I run calbrate touch screen and it`s now Ok.
Did you try this?
Click to expand...
Click to collapse
Yes, several times.
Those claiming not to have this issue are ahead, but the sample size is too low.
Can you edit the polls for A101's and A70's separate?
marclh1992 said:
Can you edit the polls for A101's and A70's separate?
Click to expand...
Click to collapse
Polls can not be edited, but this is for A70 only. You having issues with the 101?
Hi all,
I don't know if this is of any relevance to the problems you guys are experiencing, but I thought the screen of my 101 was broken.
The problem was, me coming from a different china tablet with resistive screen, that I was applying far too much pressure to the screen and capacitive screens don't respond well to that.
These screens need almost feather light touch and are very, very responsive and the tracking (at least on my 101) is excellent.
I hope this helps...
I'm not sure you can accurately conclude that the touch response is low resolution for slow finger motion with the test scenario you are using. I say this not based on some intimate knowledge of Android touchscreen drivers, but on years of experience programming human interfaces at a low level for embedded systems. From using my Archos 101 and a Zenithink ZT-180 (Android 2.1 tablet), the touch response feels similar to how some mice (mouses?) interfaces might be programmed, but tweaked to compensate for the vagaries of using a fat index finger that lays over many pixels at once pretending to be a pressure sensitive mouse cursor. I can imagine the touch interface having to pay attention to how many pixels are being touched by your finger and how many of those pixels at the edges are noisily changing from inactive to active touch-wise. It's actually very impressive how intuitive it feels to use a good touch interface when I know how much logic is required to say this is a touch and hold verses a hard quick tap verses a small swipe verses whatever. As in mouse programming, there are logic thresholds based on how fast the cursor is moving and how quickly it's accelerating. It could very well be that your A70 may not have all the speed and acceleration thresholds set optimally, or to your tastes. I am only suggesting you keep an open mind and dig deeper to learn how these things work.
Bye.
Marine6680 said:
Ok, some people were confused as to what my problem was with my other post, They thought it was a performance lag issue; possibly due to low memory. So I am reposting, I am also making it a poll, as some mentioned that a downgrade fixed this behavior on there units.
I have noticed my touch screen does not have smooth response in apps. To confirm I downloaded a app that tests mulitouch; I used "multitouch vis test".
When moving my finger quickly, or swiping, the finger tracking of the touchscreen seems fine. The problem arises when moving slowly or making small movements of less than 10 pixels; that is when you can see that the touchscreen does not track smoothly. You can see the output on the screen stay in one position as you slowly move your finger, then suddenly jump several pixels. It repeats this process as you continue to move slowly, often times the output on the screen is still lagging behind your finger. (it is not centered under your finger even after the jump) This happens even on a fresh boot, and I have tried the touchscreen calibration several times.
Overall it seems like the touch detection is low resolution, and can not detect fine/small movements. If the ones claiming it is dependent on firmware version are correct, then this could be fixed by Archos. If I get enough responses to the poll, I will contact Archos if the results point in that direction. If this is a fairly rare issue, then I know my A70 is defective.
Click to expand...
Click to collapse
I'm not saying the hardware is low quality, and it could be software setup. I know a good deal about how these things work, or at least have the ability to understand the technical side. I am an avionics Tech by trade.
When testing the slow pixel to pixel fine movement adjustment, I do not slide my finger, I roll my finger on the screen. This allows smoother and more precise small movements. It is a technique I have used on other devices that works very well.
The issue, is that my phone and 10in tablet (non Archos) does not behave this way. It is a usability issue. When playing a game like Angry Birds, how precise you can aim is the difference between beating the level and failure.
CrunchyDoodle said:
I'm not sure you can accurately conclude that the touch response is low resolution for slow finger motion with the test scenario you are using. I say this not based on some intimate knowledge of Android touchscreen drivers, but on years of experience programming human interfaces at a low level for embedded systems. From using my Archos 101 and a Zenithink ZT-180 (Android 2.1 tablet), the touch response feels similar to how some mice (mouses?) interfaces might be programmed, but tweaked to compensate for the vagaries of using a fat index finger that lays over many pixels at once pretending to be a pressure sensitive mouse cursor. I can imagine the touch interface having to pay attention to how many pixels are being touched by your finger and how many of those pixels at the edges are noisily changing from inactive to active touch-wise. It's actually very impressive how intuitive it feels to use a good touch interface when I know how much logic is required to say this is a touch and hold verses a hard quick tap verses a small swipe verses whatever. As in mouse programming, there are logic thresholds based on how fast the cursor is moving and how quickly it's accelerating. It could very well be that your A70 may not have all the speed and acceleration thresholds set optimally, or to your tastes. I am only suggesting you keep an open mind and dig deeper to learn how these things work.
Bye.
Click to expand...
Click to collapse
I have noticed this issue too, with "multitouch vis test" When i move my fingers over the screen slowly it jumps at least 4 Pixels.
But the screen has not a low resolution, when i lift my finger up and place it down again, i can "select" for example 412 then 411.
I have the archos 70 it
Schroedinger
Edit:
When i use this program on my Desire HD, ich can slide from Pixel to Pixel by rolling my finger.
schroedinger said:
I have noticed this issue too, with "multitouch vis test" When i move my fingers over the screen slowly it jumps at least 4 Pixels.
But the screen has not a low resolution, when i lift my finger up and place it down again, i can "select" for example 412 then 411.
I have the archos 70 it
Schroedinger
Edit:
When i use this program on my Desire HD, ich can slide from Pixel to Pixel by rolling my finger.
Click to expand...
Click to collapse
Definitely the software movement detection algorithms then.
If we get some more votes on here, I am going to point Archos in this direction.
hardware or software problem...???
I have already contacted Archos support about this. They just told me they've never heard of this problem... I responded back with more detailed info and they have just ignored me.
I have also posted info on this on archosfans.com forum. There doesn't appear to be many people who care, or have this problem. I am trying to find out if there is defective hardware which means I need to get it replaced BEFORE I void the warranty with the developer firmware, or if it is expected because of software optimization that will be fixed.
http: forum.archosfans.com/viewtopic.php?f=73&t=48651
video:
http: www youtube.com/watch?v=zdH_Kg4-xTQ
Can a few people please try using Multitouch Visual Test and post results? I am wondering if any A70IT, or any other Gen 8 touch screen actually works properly. I am wondering if anyone has a an A70IT that actually picks up every pixel like it should...
If you don't have access to get it from the market (it is not in AppsLib), I am posting a link to the apk to download. It is just a development tool, so I am sure it is ok.
http: www megaupload.com/?d=PN7DVJZ2
that poll is completely unscientific
don't care about the poll
I don't really care about the poll. I have this issue and trying to figure out if anyone else has it or if I have a defective device that should be replaced. This was the only thread I could that related to my problem, and the original post explained it perfectly.
Should I start a new thread about this problem rather than a reply to this poll?
Coordinates seems to increment/decrement approx +- 5 only. Slow movements are delayed somehow. Not really a big problem, but if it is a software issue I would really like to see some improvements in the future.
It isn't scientific, but if a lot of people had participated, it would have been a good guide.
It is rather annoying, but no point in replacing it if it is a common issue with every tablet.
Marine6680,
Exactly my point. I don't want to waste my time in trying to replace something that might not be broken (in a matter of speaking).
I purchased the Photon on release day and have had no problems with it (shutoffs, reboots, screen of death, etc.). I came from an Iphone 4 on AT&T because I wanted unlimited data. My only gripe is what appears to be touchscreen sensitivity/preciseness.
When I look at my Photon with the screen turned off in the sunlight at an angle, I can see a grid of boxes that appears to be the touchsensing grid. When I look at an Iphone the same way, I can see a similar type of grid.
The difference in the grids is substantial, the Photon grid boxes are significantly larger than those on the Iphone.
I've noticed that in general, the Photon has worse touch sensitivity than the Iphone 4 did. Making exact screen presses on website links, for example, is simply not as fluid or precise. Not even the unlock keypad works as well.
I haven't had an opportunity to look at the Epic Touch (GS2), I'm wondering what the grid is like on this phone?
Anybody else here notice a lack of preciseness with the Photon touchscreen? Is it an Android issue or a hardware issue?
The grids are becuase the screen has an arrangement of pixels and subpixels called PenTile Matrix, which makes it appear as if it had more resolution than it actually does.
That does not affect, however, the touchscreen quality. The SGS2 does not have the square thingy.
You have too much time on your hands.
JCSands1109 said:
You have too much time on your hands.
Click to expand...
Click to collapse
Ha ha
Sent from my MB855 using xda premium
robinrisk said:
The grids are becuase the screen has an arrangement of pixels and subpixels called PenTile Matrix, which makes it appear as if it had more resolution than it actually does.
That does not affect, however, the touchscreen quality. The SGS2 does not have the square thingy.
Click to expand...
Click to collapse
No, I am familiar with the pentile nature of the screen.
l am referring directly to the capacitive matrix grid above the lcd used to sense finger presses. The grid squares are very large in comparison to the iPhone. That makes me wonder if the touchscreen is less accurate. Look at both phones with the screen at an angle in direct sunlight. Each has a grid.
I would definitely agree its not at fluid as other phones I've used but damn can it be touchy. Scrolling down a webpage always seems to end up in a unintended click for me.
Yeah mine can be touchy as well. Mostly with the xda app
Sent from my MB855 using XDA App
I am having issues with my touch screen not taking my input when in landscape. It works when I change to portrait and usually works when switching back to landscape but then stops again. I've noticed this playing angry birds and browsing in IE. Anything I can do to correct this?
edit: I think I found my issue. If i'm touching the bottom area where the capacitive buttons are the screen won't respond. Is this normal?
I find the sensitivity of the screen is less than the Focus. The Focus suffered from bad touch sensitivity if you didn't hold it (like laying it on the bed). If they can get full registry access to the phone, I'll bet the sensitivity is adjustable.
Sent from my PI39100 using Board Express
others have mentioned that touching the soft keys even slightly makes the rest of the screen unresponsive.
I don't know why capacitive buttons are so popular... they might be 'cool' but... hardbuttons aren't accidentally activated, they don't mess up the screen and they provide REAL tactile feedback.
Plus you can search for and use hardbuttons when they are out of sight. With my TV and BD player I have to put my face to the buttons with a magnifying class to see the icons because feeling them activates them and they have no backlights :/
link68759 said:
I don't know why capacitive buttons are so popular... they might be 'cool' but... hardbuttons aren't accidentally activated, they don't mess up the screen and they provide REAL tactile feedback.
Plus you can search for and use hardbuttons when they are out of sight. With my TV and BD player I have to put my face to the buttons with a magnifying class to see the icons because feeling them activates them and they have no backlights :/
Click to expand...
Click to collapse
They're popular because presumably they cost less than actual buttons, easier to manufacture, and are less likely to break or need maintainence.
The screen's glass is already set up to be capacitive, so extending that down to the "button" area requires virtually no additional cost - they only need 3 tiny LED's underneath, rather than housing full mechanical buttons, with a separate plastic overlays ontop on the buttons.
Did anyone else notice that the nexus 6p has force touch in the Google apps?
If I press harder on the screen in the Google photos app(and other galleries) in the Google pdf app and some other Google apps the screen will zoom in/out according to the pressure applied.
It is not hardware pressure detection but software one(using touch size)
How comes no one ever mentioned it?
This "feature" is not there on the nexus 5.
No it doesn't.
yossi2010 said:
Did anyone else notice that the nexus 6p has force touch in the Google apps?
Click to expand...
Click to collapse
It really doesn't...
yossi2010 said:
Did anyone else notice that the nexus 6p has force touch in the Google apps?
If I press harder on the screen in the Google photos app(and other galleries) in the Google pdf app and some other Google apps the screen will zoom in/out according to the pressure applied.
It is not hardware pressure detection but software one(using touch size)
How comes no one ever mentioned it?
This "feature" is not there on the nexus 5.
Click to expand...
Click to collapse
you sure? i try press very hard and now my screen cracked...and it doesnt zoom in at all! :crying:
Is this a joke?
Sent from my Nexus 6P using Tapatalk
You sure you didn't reach for your 6p and end up picking up a 6s? The 6p really doesn't have force touch....
I think he ended up doing the double tap slide zoom.
Sent from my Nexus 6P using Tapatalk
Your phone is detecting two inputs and zooming in.
Your laying your finger across the screen and pushing down. This increases the surface area and the phone thinks your pinching/spreading two fingers to zoom.
Sent from my Nexus 6P using Tapatalk
i tried it, it does zoom as you can see in my video it only shows one touch point what i did was use the joint of my thumb and then press the rest of my thumb down making the surface bigger here is video showing it https://www.youtube.com/watch?v=7jfXWidKp0Y
Still a matter of surface area and not force touch. Because the surface area is so great the phone assumes that it's not one touch input but two so close together that it can't differentiate them. Then it decides to treat that massive touch input as two, and as the surface area changes it gives you the pinch to zoom.
Sent from my Nexus 6P using Tapatalk
It's not pinch to zoom
Two facts.
Firstly It doesn't work in all of the apps that has pinch to zoom...
Secondly it zooms in while having 1 touch active.
here's What it is, it's probably some apps that use a new api for touch pressure and the nexus 6p using the touch size as pressure value(the 6p shows the pressure as always 1 since the value is larger than 1)
FYI guys, Android has had a "pressure sensitive" feature since its first or second public API level, BUT, it does not have a pressure sensor. It reads the amount of area your finger is occupying on the screen when you lay down your finger, if while your finger is down you cause a greater disruption in the screen electrical field it will register as you using more force. This is because the assumption is made that more finger area contact with the screen = more pressure being applied. This has been available in Android for a very long time, but devs and even Google don't make regular (or any that I can tell) use of it. If you want to write it into your own app you can, but it's not all the useful when you have long press (and less dangerous to screens).
I can't replicate what OP is doing and I suspect he may have accidentally tripped tap and drag and is subtly rolling his finger on the screen.
You can find info on it here under public methods. I suspect that poor calibration across all the various Android devices is why this isn't used much.
http://developer.android.com/reference/android/view/MotionEvent.html#getPressure(int)
@work said:
FYI guys, Android has had a "pressure sensitive" feature since its first or second public API level, BUT, it does not have a pressure sensor. It reads the amount of area your finger is occupying on the screen when you lay down your finger, if while your finger is down you cause a greater disruption in the screen electrical field it will register as you using more force. This is because the assumption is made that more finger area contact with the screen = more pressure being applied. This has been available in Android for a very long time, but devs and even Google don't make regular (or any that I can tell) use of it. If you want to write it into your own app you can, but it's not all the useful when you have long press (and less dangerous to screens).
I can't replicate what OP is doing and I suspect he may have accidentally tripped tap and drag and is subtly rolling his finger on the screen.
You can find info on it here under public methods. I suspect that poor calibration across all the various Android devices is why this isn't used much.
http://developer.android.com/reference/android/view/MotionEvent.html#getPressure(int)
Click to expand...
Click to collapse
I understand how it works but i do not understand why...
The Nexus 6p has no pressure support(sadly) while the nexus 5 has pressure support.
When using music apps i can play sounds as i want them to sound by tapping gently or forcefully on my friend's nexus 5.
(the nexus 5 shows different pressure values and touch size)
Yet on the nexus 6p the touch pressure always shows 1 yet the touch size changes.
The nexus 6p zoomes in (in sync with the touch size change) yet the nexus 5 doesn't behave like this.
I know about double tap and slide and i've used it for a long time and I can notice when it is applied and when it is not.
Double tap and slide is smooth and doesn't have anything to do with touch pressure yet this behavior is working in steps and in sync with touch size.
I would like to know why does it happen only on the nexus 6p(and only on certain apps and esp in google photos/whatsapp photos).
This thread is still a thing? Look if any Android device had a pressure sensitive screen it would be advertised. Since it's not it doesn't. End of story. Close this thread
Sent from my Nexus 6P using Tapatalk
It's not force touch.
Go to dev options and enable pointer location you will see that PRS (pressure applied) is constant at 1 (for me anyways) on LCD devices the value could change due to how light you touched it.
The display cant detect the pressure applied but the digitizer can estimate the size of the touch point.
delete
silentbrains said:
I'm able to replicate this behavior, and I'm in agreement about it measuring surface area of the touch (or multitouch) rather than pressure sensitivity. The Markers app works the same way (although it works barely if at all on the 6p, much better results on the Nexus 7 2013).
Click to expand...
Click to collapse
The weird zoom stopped occuring after the android N update but i can still replicate it on other 6p running android 6.
I wish the 6p had this value of pressure since the 5x and 5 has it, alot of apps use it for brush thickness and MIDI velocity on music apps(touch lightly for a soft and quiet sound touch fast with force for a rough and loud sound) it works perfectly fine on the nexus 5 and 5x yet doesn't work on the musical beast that is the nexus 6p.
www . youtube . com/watch?v=0Jt1WKymqkM
(not allowed to post links yet)
Hello
I'm using the m5 pro for drawing, but run into an issue with
the pressure sensitivity. The pen doesn't seem to register pressure
below a certain threshold. Then as pressure is increased, suddenly it does. When
drawing, this results in a dotted line, as opposed to a line with continuously
varying opaqueness. See movie above for an example.
Hoping someone can try and replicate this, so I can find out if this is
a design flaw, or a fault in my tablet or pen. Brush settings are quoted in
the movie's description..
Dzjoss
in case anyone is interested: meantime I was able to test the same app on an ipad, and it basically shows the same behaviour, though the ipad is a bit more sensitive. There I also see a broken line. So I think its not an issue with the device itself, just a limitation of the software and technology. You cant seem to beat the sensitivity of a siple pencil (lead)...
I find it heavy but sensitive. Any contact with the screen will draw. Android registers even the distance of the pen from the screen and its angles in the MotionEvent traces so I'd say you just need to tweak your app to make it oversensitive.
emiliewgnr said:
I find it heavy but sensitive. Any contact with the screen will draw. Android registers even the distance of the pen from the screen and its angles in the MotionEvent traces so I'd say you just need to tweak your app to make it oversensitive.
Click to expand...
Click to collapse
Yes I also think its due to the app. Unfortunately in infinit painter I cant find a way to change the pressure curves or something. I'm gonna try some other ones..