Hi,
I am a computer science student working on a FTIR Do-It-Yourself
Multitouch-Table at university.
>From reading many papers about multitouch I know about a capacitive
system called DiamondTouch
where this effect also happens and is called “shadowing”.
At the “Internation Tabletops and Surfaces 2
The problem is, though, is no one was really aware of these
"limitations" (developers or users), at least for the Nexus One. I'll
admit I didn't research before buying the N1 that it was "basically
the same sensor as the G1"
Up until now, with the addition of multitouch into the SDK, it's been
'Gr
It's ok, it's not you, it's all of the chicken little world-is-falling
sort of articles that name me. I didn't write anything or make that
comparison video. Anyways..
Multitouch is not useless, there are just limitations. Pinching works
just fine because the axis flipping doesn't matter (all yo
Hi Robert,
I'm sorry I exposed your exposition mission, didn't mean to involve
you or anything.
Although it is a good thing that the information spreads, without
this, we won't have fixes anytime soon.
So you could actually confirm that this is HTC related ? I mean
hardware related ?
That is ver
Ugh, these articles are making me out to look like I was on some kind
of expose mission.
The conversation I had with the guy was like this:
He said, "Why didn't you use dual analog joysticks?"
I said, "Because it won't work right on HTC phones. Run my test app
to see why."
And now there are 200+
Ah maybe we're going to be allowed to file a bug report now that the
all word knows with clue :
http://www.mobilecrunch.com/2010/03/03/nexus-one-multi-touch-bugs
Please tell us you are working on a solution or that there is no
solution and we should not rely on multitouch for our apps.
Either way
Dianne, I'm unclear about just one thing here -- which "special code"
-- you mean the code in the sample apps?
Relative to the conversation since -- I don't disagree; this isn't an
Android "bug" and it theoretically should be in the device driver. It
does raise a question, though, about the API de
I love my nexus but I gotta agree with you. Between the not-yet-fixed
radio issues (yes, not fixed yet!) and this cheap touch screen I feel
like I got a bunch of money stolen from me.
I can't believe I'm saying this, but 3 years later, the 1st gen iPhone
has a better touch screen than the 2010 supe
To be honest this is really bad news. Marketed as a "superphone" and
not being able to even do valuable multi touch in gaming is pretty
weird/weak! Even a simple pong game (1 human vs 1 human on 1 device)
is not possible with that cheap screen.
On Feb 16, 12:18 pm, Sean Hodges wrote:
> > So Sean,
> So Sean, your answer to that is simply : Don't use multitouch at
> all !!
No.
My point was that you shouldn't rely on the touch screen for complex
gestures (particularly multi-touch). Otherwise your game will be
useless to anyone with a handset that doesn't support dual/multi
touch, or has char
So Sean, your answer to that is simply : Don't use multitouch at
all !!
When you think that most games need more than one input, that gesture
like pinch zooming are so very intuitive, it is very sad.
And it's not only developpers who are finding that this completely
sucks, it's actually snowballi
It doesn't seem as good because it isn't as good.
Have you looked at the supported gestures page I linked you to?
http://www.synaptics.com/solutions/technology/gestures/touchpad
All of the gestures that the screen used by the Nexus One claims to
support would not be affected by the issues you des
Droid handles better than the rest so far but my tests still showed
errors. Occasionally it still flips axis and has some small
interactions between the two fingers on near-axis touches. It's
better but doesn't seem as good as iPhone/iPod touch's screen.
On Feb 15, 5:51 pm, Dianne Hackborn wrot
On Mon, Feb 15, 2010 at 3:16 PM, Mario Zechner wrote:
> It's not so much an issue of gestures that may be impossible to
> recognize on certain screens but more that the API exposes
> functionality that is broken on all screens at the moment.
The Droid screen handles two fully independent fingers
It's not so much an issue of gestures that may be impossible to
recognize on certain screens but more that the API exposes
functionality that is broken on all screens at the moment. Especially
the coordinate flipping/confusion is something that can't be solved
according to Dianne. And it is exactly
The Nexus One uses the Synaptics ClearPad 2000 series:
http://www.synaptics.com/about/press/press-releases/synaptics-clearpad-on-nexus-one-smartphone
According to this reference:
http://www.synaptics.com/solutions/products/clearpad#benefits-2000
this model has support for a maximum of 2 simultaneo
G1, myTouch, and Passion use a Synaptics screen. Droid uses one from
another company (I can't recall).
Even for a particular company, there are a wide variety of screens you will
encounter. For example here is what I found for Synaptics:
http://www.synaptics.com/solutions/products/clearpad
On
So are they all using the same company for the screen?
On Sat, Feb 13, 2010 at 5:10 PM, Lance Nanek wrote:
> A more capable multitouch screen probably costs more. If that is the
> case, it isn't really surprising that multiple manufacturers would go
> with a cheaper, less capable one.
>
> On Feb
A more capable multitouch screen probably costs more. If that is the
case, it isn't really surprising that multiple manufacturers would go
with a cheaper, less capable one.
On Feb 13, 6:51 pm, Kevin Duffey wrote:
> So Robert.. is this a platform issue in your mind.. being that it happens on
> all
So Robert.. is this a platform issue in your mind.. being that it happens on
all android devices currently regardless of manufacturer? Or is it a driver
issue for each hand set and just oddly happens to be coincidental that
various manufacturers have the exact same issue with multi-touch? I am sure
Ok if you guys want to see what I'm talking about, check out the app I
just published called "Multitouch Visible Test." Play around with
that and you'll see the problems. If you're interested in developing a
multitouch app, check that out first so that you know the limitations
of the data you'll b
Luke's code cleans up some basic stuff like gestures involving
pinching but it can not fix the two independent point problem.
Currently, even with his code which filters out some noise, it is
impossible to have a reliable control system involving two independent
virtual joysticks placed along the s
Nevermind, I found it - it got segmented somehow.
On Feb 12, 11:33 am, Robert Green wrote:
> Where did my original post go? Was it deleted?
>
> This is a valid problem. How is it that the hardware coming from both
> HTC and motorola has the same problem? Also - how was this a solved
> problem
Where did my original post go? Was it deleted?
This is a valid problem. How is it that the hardware coming from both
HTC and motorola has the same problem? Also - how was this a solved
problem with iPhone several years ago? I'm trying to compete with
that platform but problems like this make i
You've got a point here. Unless the screen capabilities and/or
technologies is dictated by google to the vendors.
Does someone knows how to use the ndk ?
I believe using the ndk you can have direct access to the sensors and
thus find out if it's the hardware or one of the layers on top of it
that
If this same issue occurs on Nexus, Moto Droid, G1.. (any other devices??)
it seems it would more likely be Android and not the different devices all
with the same problem. But.. I don't know for sure.. just seems like that
two or three different vendors wouldn't end up with the same bug based on
Hi,
I should report the same thing.
My game Armaboing (www.armaboing.com) is multitouch since Android 1.5.
And I have the same problem with multitouch, and came to think that
it's not Android the problem but the drivers or the hardware.
I think that's why Diane doen't want a bug report on this b
27 matches
Mail list logo
