Hi, Not sure why you need it.
The kernel driver should indicate the touchscreen coordinates corresponding to the corners (eg my controller gives 1024x1024) The Android input manager then handles the transform between the display coordinates and touchscreen coordinates. dumpsys input shoud show what it's doing. One thing to look out for is Android's notion of external and internal input devices. For example, by default, if you connect a USB touchscreen controller Android will assume it is for an external screen (even if there isn't one) and calculate the transform based on the resolution of this (possibly non existant) screen. It doesn't do this for touchscreens connected over other interfaces (eg I2C) I had to modify the input service to add an extra parameter to the .idc file to force certain devices to internal for this case (where the primary touchscreen is on USB).. Regards, Martin On Tuesday, 13 October 2015 13:10:44 UTC+2, [email protected] wrote: > > Hi there, > > has anyone integrated / ported tslib for Android KitKat, Lollipop > or Marshmallow? Or is there better way for adjusting (cropping) touch area > (kernel drivers)? > > Thanks for any info > > Kind regards, > Petr > -- -- unsubscribe: [email protected] website: http://groups.google.com/group/android-porting --- You received this message because you are subscribed to the Google Groups "android-porting" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
