If you've managed to run the ts_calibrate program, you should also build the other test programs, most notably ts_test and with the calibration done, you should run ts_test and see if the touch is responding.
If it is, then you can focus on your Android changes as opposed to not knowing what part of the touchscreen path is failing.. Regards -- Ashwin 2010/1/31 தங்கமணி அருண் <thangam.ar...@gmail.com>: > Hi, > > my touch screen is still not yet working. To make it work, i did the > following. > > 1. I have applied patch from: > http://www.mail-archive.com/android-porting@googlegroups.com/msg05571.html > on android source > > 2. I have integrated "tslib" package from > :http://android-m912.googlecode.com/files/tslib-android.tar.gz > and also able to run "ts_calibrate" utility on android. able to get > calibration done. > But still there is no response from android application > > 3. I am getting response from my kernel. > > 4. I have all the Android Drivers in kernel. see blow. > > 5. Kindly guide me to make it work, thanks for your help > > # Power management options > # > CONFIG_PM=y > CONFIG_PM_DEBUG=y > CONFIG_PM_VERBOSE=y > CONFIG_CAN_PM_TRACE=y > CONFIG_PM_SLEEP=y > CONFIG_SUSPEND=y > CONFIG_PM_TEST_SUSPEND=y > CONFIG_SUSPEND_FREEZER=y > CONFIG_HAS_WAKELOCK=y > CONFIG_HAS_EARLYSUSPEND=y > CONFIG_WAKELOCK=y > CONFIG_WAKELOCK_STAT=y > CONFIG_USER_WAKELOCK=y > CONFIG_EARLYSUSPEND=y > > CONFIG_ANDROID_PMEM=y > CONFIG_ANDROID_TIMED_GPIO=y > CONFIG_BINDER_IPC=y > > CONFIG_LOW_MEMORY_KILLER=y > CONFIG_LOGGER=y > CONFIG_ANDROID_RAM_CONSOLE=y > CONFIG_ANDROID_RAM_CONSOLE_ENABLE_VERBOSE=y > > > > -- > unsubscribe: android-porting+unsubscr...@googlegroups.com > website: http://groups.google.com/group/android-porting -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
