> I have multitouch working on the G1 in a way that is backwards-
> compatible with single-touch applications.  I capture the multitouch
> events and then hijack an unused field in MotionEvent to pass the
> multitouch events in a way that only affects programs that have been
> designed to work in multitouch mode -- i.e. this did not require re-
> plumbing the event system.  The approach also does not require any
> kernel modifications, it just needs modifications to one Java system
> class.

> Video and full source here:
> http://lukehutch.wordpress.com/android-stuff/

> S

> On 11 Jan 2009, at 13:30, luke wrote:

> > I have multitouch working on the G1 in a way that is backwards-
> > compatible with single-touch applications.  I capture the multitouch
> > events and then hijack an unused field in MotionEvent to pass the
> > multitouch events in a way that only affects programs that have been
> > designed to work in multitouch mode -- i.e. this did not require re-
> > plumbing the event system.  The approach also does not require any
> > kernel modifications, it just needs modifications to one Java system
> > class.

> > Video and full source here:
> >http://lukehutch.wordpress.com/android-stuff/

> My personal take is that there is a whole lot of prior art (the iPhone
> was not the first by a long shot), so it's probably not super-
> defensible in court... but Apple has deep pockets and an elite image
> to maintain.  They apparently have about 200 patents on the iPhone,
> two of which especially deal with their touchscreen technology -- but
> I haven't looked into the details.

> On Jan 11, 11:32 am, Sena Gbeckor-Kove <s...@imkon.com> wrote:
>> Great! Does anybody know if this is ok IP wise, or is a lawsuit likely?

>> S

>> On 11 Jan 2009, at 13:30, luke wrote:

>> > I have multitouch working on the G1 in a way that is backwards-
>> > compatible with single-touch applications.  I capture the multitouch
>> > events and then hijack an unused field in MotionEvent to pass the
>> > multitouch events in a way that only affects programs that have been
>> > designed to work in multitouch mode -- i.e. this did not require re-
>> > plumbing the event system.  The approach also does not require any
>> > kernel modifications, it just needs modifications to one Java system
>> > class.

>> > Video and full source here:
>> >http://lukehutch.wordpress.com/android-stuff/

> Unless an SDK is released with multi-touch support, this discussion is
> probably better off in android-discuss or android-platform.

> (Just trying to cut down on cross-posting)

> On Sun, Jan 11, 2009 at 2:34 PM, luke <luke.hu...@gmail.com> wrote:

> > My personal take is that there is a whole lot of prior art (the iPhone
> > was not the first by a long shot), so it's probably not super-
> > defensible in court... but Apple has deep pockets and an elite image
> > to maintain.  They apparently have about 200 patents on the iPhone,
> > two of which especially deal with their touchscreen technology -- but
> > I haven't looked into the details.

> > On Jan 11, 11:32 am, Sena Gbeckor-Kove <s...@imkon.com> wrote:
> >> Great! Does anybody know if this is ok IP wise, or is a lawsuit likely?

> >> S

> >> On 11 Jan 2009, at 13:30, luke wrote:

> >> > I have multitouch working on the G1 in a way that is backwards-
> >> > compatible with single-touch applications.  I capture the multitouch
> >> > events and then hijack an unused field in MotionEvent to pass the
> >> > multitouch events in a way that only affects programs that have been
> >> > designed to work in multitouch mode -- i.e. this did not require re-
> >> > plumbing the event system.  The approach also does not require any
> >> > kernel modifications, it just needs modifications to one Java system
> >> > class.

> >> > Video and full source here:
> >> >http://lukehutch.wordpress.com/android-stuff/