how many touches does vega support and how is multitouch performance? are there issues like axis inversion like on nexus one and desire?
The answers are:
2, reasonable (annoyingly any input will stop when a 3rd touch is registered) and yes (not as bad as video I saw of the n1).
Related
Hey guys, i was just wondering that, does the HD have multitouch capabilities. a couple of months back we saw the diamond has a little bit of multitouch in it. is there anyone out there that can test the hd to see if it can do "multitouch"
I don't think we have the type of touch screen to support that. Even if, Apple just got a patten for it, I expect lawsuits will fly over that shortly.
What do you mean with, the diamond has a "little bit of multouch"?
Do we really need another thread to discuss this?
The Touch Pro and Diamond have a capacitive touch pad below the screen. The HD does not.
I'm not really knowledgeable enough to actually dive down into the hardware and see exactly how multitouch inputs are registered, but after using a couple of multitouch enabled programs on my N1, namely Pong Multi Touch and Ethereal Dialpad (installing the NightSky multitouch-enabled dialpad), it seems as though the N1 registers multitouch inputs the same as (at least) the G1 and myTouch (I don't have access to any other multitouch-enabled Android devices to test).
That is, the screen is aware of 2 x and 2 y values, with snapping and both the x and y, and it's up to the OS to try to determine which x goes with which y.
In Pong Multi Touch, sometimes the paddles will switch fingers -- that is, the finger over the right paddle starts controlling the left paddle and vice versa -- when the paddles cross each other's line of sight.
In NightSky dialpad, you're actually given two blobs corresponding to your multitouch inputs, and like in the first multitouch demos by Luke Hutchinson on the G1, sometimes the points get confused and inhabit the opposite "corners" of where your fingers actually are.
It's possible that this is a software limitation and actually put into place for older Android devices whose screens operated this way, but I just really hate to think that in a world of true multitouch screens, the Nexus One might still be using that same flaws multitouch technology.
Does anyone have any experience with how say the Droid handles multitouch inputs? Does anyone have a better understanding of the Nexus One's touchscreen? I've searched this forum and Google, but I haven't really been able to wade through and pick something useful out.
why are apps like multi touch pong not really multi touch? when u have 2 fingers on the screen at the same time the 2 points interfere with each other making it impossible to play games like pong or air hockey etc
from what I understand, true multitouch is still disabled for US devices. What's used in most of these apps is a hacky multitouch we've been seeing since the G1.
kozm0naut said:
from what I understand, true multitouch is still disabled for US devices. What's used in most of these apps is a hacky multitouch we've been seeing since the G1.
Click to expand...
Click to collapse
this isn't true there is true multi touch from android 2.0 and up! but google decided to disable it in their native apps.
oh so what we have multi touch but not the real one like the iphone has. gay
i understand that theres multi touch. we can pinch to zoom and what not but download the simply draw app which is "multi touch" and try to draw 2 different objects at once. just wont work. i mean true multi touch
it's been made clear that android handsets (including n1) support true multitouch on the hardware level. however, the apps I've used on 2.1 so far with "multitouch" suffer from the mixed-axes issues mentioned here and elsewhere on the forums.
http://androidandme.com/2010/03/news/is-multitouch-broken-on-the-nexus-one/
I hope this is a problem that can be fixed. Although it appears to be a hardware issue according to a Google engineer.
I have a Nexus One.
puuh..I read this..and I dont like to read it again, not even think of it
I downloaded the app, and it's not as bad on mine as his. The issue mine kept having was that it would snap to the grid line of the other touch point, and then it would start losing track of the original touch point. So if touch point 1 y intersected with touch point 2 x it would snap to X and then I could slide along X and the dot would not follow.
The touch panel in the N1 is a Synaptics ClearPad 2000 Series. No more than two points can register at once. It supports pinch zoom and pivot. The problem with axis flipping looks like a driver issue.
Does anyone know what the droid touchscreen uses?
Ouch. I don't like looking at it but ultimately I'd don't believe its enough to detour me from getting a nexus one. Mostly I'd us it for pinch zoom browsing and looking at images. Does suck if you try to play games though.
About the only real use for a "proper" multi-touch screen would be games.
However, this may also mean that the "palm-wrap" problem will never go away. :/
Does anybody know if the desire has the same panel?
I believe so, yes, as the Desire is also made by HTC.
One thing that worries me about the HD2 is the touchscreen sensors. If it's just the same ones as the Nexus One, Synaptics CP2000 with faulty multitouch, I might have to reconsider my options.
It does have true multitouch. Youtube it there are a bunch of videos out there.
After seeing YT videos, it looks like the same wonky multitouch in Nexus One. I'm disappointed
What is it you find "wonky" about it
No it's not. Some of the first run HD2s had some bad sensors, but we don't have any trouble crossing streams or whatever you N1 kids call it nowadays.
Like in this video
http://www.youtube.com/watch?v=tTqh6u2OUFU
Sometimes it jumps all over the place.
And in here
http://www.youtube.com/watch?v=Hgrsq2-Vy7Q&feature=channel
It sometimes sticks when you're near the same axis.
The sticking is an auto-align in the driver.
Is there a way to turn that off? Does it support more than 2 fingers?
The limitation is currently the way the HTC code sends the data to other applications. It may be possible to get more points with a lower level hook, though I haven't yet gone that far as I want to investigate what can be done so far
Click to expand...
Click to collapse
Back in Nov, guess they got lazy
Not sure about turning it off.
HD2 has multitouch, but can only recognize 2 touch points.
(WP7S min requirement is 4 touch points)
As you can see here:
http://www.youtube.com/watch?v=qzhUzq6bTPg&feature=player_embedded
The N1 multi-touch issue is very pronounced and extremely different.
I just grabbed both Scilor and |3v5y apps for multitouch.
In the Scilor app (with two circles) you can see a clear snap when you are on the same x or y axis, but again this is driver behavior. Nothing unusual besides that.
In the |3v5y app, the x axis doesn't show any snapping, but crossing on the y axis (possibly a coding error?) swaps the 'paint stream' under the fingers, but still keeps with original positions.
This is similar to the droid on the youtube video above, where the blue and red dot might flip, but it doesn't lose track of what is being touched. Thus, not the same problem as the N1. Not the same sensor. Hurray, hurrah.
ahimberg said:
HD2 has multitouch, but can only recognize 2 touch points.
(WP7S min requirement is 4 touch points)
Click to expand...
Click to collapse
Not true. HD2 2-point multitouch is a driver (soft) limitation, if you read what I just quoted.
On that note does anyone know what sensor HD2 uses?