Ok.. thanks for the pointer Sean. So question for you and Dianne.. being on the platform team.. if his code works so well.. supposedly better than the OTA updates for Nexus.. why not just replace what is in Android.. or add it some how so that all of us developers can have this corrected data? Maybe I read incorrectly, but from what you and Dianne are saying, the issues the rest of the guys talk about.. where by touching one place, then a 2nd.. then lifting one finger, then touch again and the wrong data being sent.. this has to do with the massive events being sent and the confusion lies in that the MotionEvent is reporting incorrect data..but somewhere in there is the correct data.. and from what it looks like, Lukehutch's code resolves that issue?
If that is correct, great.. maybe Robert Green and others can take that class of his and retrofit it and report back on this thread if it works. But if so, why not put that into the core of the framework for all to benefit? Clearly this has been a problem for the likes of Robert and others who have done great work with game development and are complaining that it's ruining the ability to develop comparable (at least in multi-touch) games as iPhone.. so why not provide the corrected data within Android itself? Or.. why not require that all touch manufacturers.. devices.. report the right data in some specific way such that the framework provides accurate multi-touch completely? This really seems to be more complex than it should be for us developers wanting to utilize multi-touch. On Fri, Feb 12, 2010 at 11:42 AM, Dianne Hackborn <[email protected]>wrote: > Sorry I meant exactly what I said: this is how the touch screen hardware on > the Nexus One works (which is essentially the same screen as on the G1 and > myTouch). The Droid has a sensor from a different manufacturer, with > different behavior. Other phones will likewise have different sensors. > > This has nothing to do with the Android platform. Please do not file bugs > about it. Android is just reporting what the hardware is capable of > reporting. There is no "normalization" for games or such, there is just the > data the screen provides. (Though there is some special code in the current > framework for cleaning up the data from the Droid screen; arguably this > should be in the driver or firmware for it, since this is really screen and > hardware specific kind of stuff. At any rate, it is not applicable to basic > screen capabilities like here.) > > There is a good analysis of the G1 class touch screen here: > > > http://lukehutch.wordpress.com/2009/01/10/full-working-multitouch-on-the-t-mobile-g1-android-phone/ > > On Fri, Feb 12, 2010 at 4:39 AM, Sean Hodges > <[email protected]>wrote: > >> I think what Dianne is saying is that the values you are seeing are >> what is raw data returned from the sensor, it's not normalised for >> multi-touch games, or for any particular purpose. >> >> My understanding is that the values returned have different coordinate >> spaces, and have a tendency to "jump" about when used directly (I >> suspect this second issue is more an artefact of the device-specific >> screen sensitivity, dents, scratches and the impact of screen >> protectors). >> >> Take a look at Luke Hutchison's multi-touch controller, it might >> provide a suitable wrapper for your requirements: >> >> >> http://lukehutch.wordpress.com/2010/01/06/my-multi-touch-code-ported-to-eclair/ >> >> >> >> On Fri, Feb 12, 2010 at 8:39 AM, Kevin Duffey <[email protected]> >> wrote: >> > Ugh..sorry.. I hate using my moto droid to reply.. fat fingers and a >> > horrible physical keyboard don't go together. >> > Dianne, I don't understand your response.. it's quite clear from several >> > developers that the multi-touch has problems severe enough that >> > it's deterring game developers and others that would use it. You're >> saying >> > that it's normal behavior for the multi-touch to change the location of >> 2 >> > touches such that one of them is completely not in the location of where >> you >> > touched it? Is this an Android platform issue with how it handles sensor >> > data.. or are you saying that the G1, myTouch, Nexus One and Moto Droid >> (not >> > sure about others) ALL have built their touch sensors to purposely >> report >> > this sort of behavior when you touch, then release, then touch again as >> > Robert and several other posters have state is happening? >> > >> > >> > On Thu, Feb 11, 2010 at 7:46 PM, Dianne Hackborn <[email protected]> >> > wrote: >> >> >> >> On Thu, Feb 11, 2010 at 6:10 PM, Kevin Duffey <[email protected]> >> wrote: >> >>> >> >>> So what I want to know is what is being done about this? Is there a >> bug >> >>> file and if so is it >> >> >> >> This is how the sensor hardware works. It is essentially the same >> sensor >> >> as the G1 and myTouch. Please don't file a bug about it. >> >> -- >> >> Dianne Hackborn >> >> Android framework engineer >> >> [email protected] >> >> >> >> Note: please don't send private questions to me, as I don't have time >> to >> >> provide private support, and so won't reply to such e-mails. All such >> >> questions should be posted on public forums, where I and others can see >> and >> >> answer them. >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> >> Groups "Android Developers" group. >> >> To post to this group, send email to >> [email protected] >> >> To unsubscribe from this group, send email to >> >> [email protected]<android-developers%[email protected]> >> >> For more options, visit this group at >> >> http://groups.google.com/group/android-developers?hl=en >> > >> > -- >> > You received this message because you are subscribed to the Google >> > Groups "Android Developers" group. >> > To post to this group, send email to >> [email protected] >> > To unsubscribe from this group, send email to >> > [email protected]<android-developers%[email protected]> >> > For more options, visit this group at >> > http://groups.google.com/group/android-developers?hl=en >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Android Developers" group. >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected]<android-developers%[email protected]> >> For more options, visit this group at >> http://groups.google.com/group/android-developers?hl=en >> > > > > -- > Dianne Hackborn > Android framework engineer > [email protected] > > Note: please don't send private questions to me, as I don't have time to > provide private support, and so won't reply to such e-mails. All such > questions should be posted on public forums, where I and others can see and > answer them. > > -- > You received this message because you are subscribed to the Google > Groups "Android Developers" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected]<android-developers%[email protected]> > For more options, visit this group at > http://groups.google.com/group/android-developers?hl=en > -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
