touchscreen support.

by sathish kumar » Fri, 22 May 2009 11:30:47 GMT


Sponsored Links
 I have added touchscreen support but the calibration is not proper.
my LCD resolution is 640x480.
Has anyone tried touchscreen on different resolution LCDs?

sathish

--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



touchscreen support.

by neo . drizzle » Fri, 22 May 2009 12:06:20 GMT


 Android accepts abs events from input subsystem. You can check  
omapzoom kernel ts driver for reference.

-Girish

On May 21, 2009, at 10:30 PM, sathish kumar <sathish...@gmail.com>  




--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---


Sponsored Links


touchscreen support.

by deepak singal » Fri, 22 May 2009 12:55:22 GMT


 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 what i got:

(kernel printk msg + getevent msg)

# getevent &
# add device 1: /dev/input/event0
  name:     "tsc2004"
could not get driver version for /dev/input/mice, Not a typewriter
x:873 y:211 down:1
Pressure On Screen x=873 y=211
/dev/input/event0: 0003 0000 000001f7
/dev/input/event0: 0003 0001 0000025f
/dev/input/event0:x:3440 y:3786 down:1
 0003 0018 000000ea
/dev/input/Pressure On Screen x=3440 y=3786
event0: 0000 0000 00000000
/dev/input/event0: 0003 0000 00000066
/dev/input/event0: 0003 0001 00000030
/dev/input/event0:x:3436 y:3780 down:1
 0000 0000 00000000
Pressure On Screen x=3436 y=3780
/dev/input/event0: 0003 0000 00000067
/dev/input/event0: 0003 0001 00000031
/dev/input/event0:x:3433 y:3777 down:1
 0000 0000 00000000
Pressure On Screen x=3433 y=3777
x:3389 y:3761 down:0
/dev/input/event0: 0003 0018 000x:3389 y:3761 down:0
00000
/dev/input/event0: 0000 0x:3389 y:3761 down:0
000 00000000
x:3389 y:3761 down:1
Pressure On Screen x=3389 y=3761
/dev/input/event0: 0003 0000 0000006e
/dev/input/event0: 0003 0001 00000034
/dev/input/event0:x:587 y:3819 down:1
 0003 0018 000000ea
/dev/input/Pressure On Screen x=587 y=3819
event0: 0000 0000 00000000
/dev/input/event0: 0003 0000 00000224
/dev/input/event0: 0003 0001 0000002b
/dev/input/event0:x:582 y:3818 down:1
 0000 0000 00000000
Pressure On Screen x=582 y=3818
/dev/input/event0: 0003 0000 00000225
/dev/input/event0: 0000 0000 00000000
x:579 y:3815 down:1
Pressure On Screen x=579 y=3815
x:581 y:3798 down:0
/dev/input/event0: 0003 0018 000x:581 y:3798 down:0
00000
/dev/input/event

# cat /proc/bus/input/devices
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="tsc2004"
P: Phys=
S: Sysfs=/class/input/input0
U: Uniq=
H: Handlers=event0
B: EV=b
B: KEY=0
B: ABS=1000003

looks like kernel is able to read the event but android does not able to
understand it.
I tried with all the patchs available for touch screen (for android) . But
still my touchscreen did not work.
Please help me out.

Thanks in advanced
Deepak

--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



touchscreen support.

by Yi Sun » Fri, 22 May 2009 23:39:45 GMT


 HOw big is your screen? 3440x3786 does not seem to be a right value




--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



touchscreen support.

by deepak singal » Sun, 24 May 2009 18:03:18 GMT


 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 anyone tried tsc2004 touchscreen on android.

Deepak

--~--~---------~--~----~------------~-------~--~----~

-~----------~----~----~----~------~----~------~--~---



Other Threads

1. Linking Google Checkout to Adwords save fees??

I dont think that applies.





--~--~---------~--~----~------------~-------~--~----~

2. Synchronous OpenMAX IL component

Hi,

I am integratring n my OpenMAX IL  for audio decoder to PV Framework.
However since my component only supports synchronous calls and doesnt
implement asynchronous operation, will that be an issue .

As of now the AudioDecodeNode calls Prepare and the Buffers are
allocated. But it looks like the State transition to execute mode is
not happening , since my component doesnt receive and  SendCommand
with EXECUTE.

Does Android mandate async calls for OpenMAX plugins ?

Thanks
Ajay
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: 

3. a/v sync in mediarecorder

4. the market for profit is open!!

5. IM doesn't stay signed in

6. help to start simulator that built by myself

7. Good App. Ideas for Developers!!