Thanks for your help.
I've managed to fix the issue by patching some of the Java code. The
driver was reporting the wrong event scan codes: ABS_Z instead of
ABS_Y and ABS_RX instead of ABS_X (have no idea why). When that was
fixed it was just a matter of calibrating the screen. Here are the
Um, okay, but it seems like it would be best to fix the driver rather than
hack the platform to do the wrong thing. :}
On Thu, Oct 1, 2009 at 6:21 AM, Jesper Nordenberg megagu...@gmail.comwrote:
Thanks for your help.
I've managed to fix the issue by patching some of the Java code. The
On Sep 29, 8:30 pm, Dianne Hackborn hack...@android.com wrote:
That event stream doesn't look good (though it doesn't look like you
included the whole thing so it is hard to tell). You can interpret it with
these constants for the first and second number:
The file I pointed to is the definition for the data -- the first number is
the class of event (like key or abs), the second number is the code (like
'a' or key or x for abs), and the third is the value. You should be seeing
this data fairly directly reflected in pointer location, except with the
On Sep 28, 7:07 pm, Dianne Hackborn hack...@android.com wrote:
What do you see in the Pointer Location app in DevTools?
I don't know how to run Pointer Location. When I try to install
Development.apk it says Dev Tools could not be installed on this
phone..
Does your event
stream from
What do you see in the Pointer Location app in DevTools? Does your event
stream from getevent look reasonable? What events is the driver saying it
generates?
On Mon, Sep 28, 2009 at 1:20 AM, Jesper Nordenberg megagu...@gmail.comwrote:
I'm running Android on a Beagle Board and want to add
Hello Sun,
Thanks for reply
#define ADC_MAX ((1 12) - 1)
#define ADC_SCALE(x) ((x) * 640 / 4096) // scale down to 640 pixels.
I am using 640 X 640 screen.
But on another board ads7846 touchscreen gives the approximate same output
means---
dev/input/Pressure On Screen x=3440 y=3786
Has
HOw big is your screen? 3440x3786 does not seem to be a right value
On Fri, 2009-05-22 at 10:25 +0530, deepak singal wrote:
dev/input/Pressure On Screen x=3440 y=3786
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website:
Hi all,
I am porting Android to a OMAP3530 LV SOM development platform. I am using a
tsc2004 touchscreen. I have built the 2.6.28 kernel and I can get Android to
boot however the touchscreen is not working. The touch screen is assigned to
event0. I can getevent and touched the screen and here is
Is this the case for every devices that if there is a kernel driver
for each device and that driver is published properly, then we don't
need to do any modification in the userspace, correct? for e.g i have
drivers for telephony(RIL), touchscreen, display, keyboard etc, in
this case i don't need
Not necessarily, other things may need user space code. For example,
hardware accelerated OpenGL is provided as a user-space library that takes
care of talking with its driver in an appropriate way.
There has already been lots of discussion on this list about porting various
parts of the system;
If you publish a proper kernel drive you won't need to modify user space.
Note that currently we don't support calibrating as is needed for
non-capacitive screens, so you would need to find some other way to
calibrate such a screen's points.
On Tue, Dec 2, 2008 at 9:37 PM, Pivotian [EMAIL
12 matches
Mail list logo
