Thanks for the reply. The touch screen works, meaning it recogizes the
inputs but the mapping is incorrect. It looks as if only the top
portion of the screen is touched, irrespective of where the touch is
done. I have not been able to use the pointercal from tslib into the
android. Has some one
As a quick hack, I found this worked
http://home.androidin.com/space.php?uid=17708do=blogid=21
--~--~-~--~~~---~--~~
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
On Mon, Mar 23, 2009 at 8:36 PM, Claw praveengudisa...@googlemail.com wrote:
I have followed the steps in the link provided. I get the events from
the touchscreen. But only that they are not not pointing to the right
objects.
There is a patch lying about by sean mcneal which does some hacks
Is this link a precursor to touchscreen work?
http://www.kandroid.org/android_pdk/keymaps_keyboard_input.html
If you've built the code (http://source.android.com/download), in
mydroid for example, then you'll find that same documentation in
mydroid/development/pdk/docs.
To change the keycodes,
2.6.27
keypad work? else no:
default new power drivers block event messages -- android gui
make menuconfig
enable:
PM
Power Management support
Suspend to RAM and standby
Wake lock
Wake lock stats
Userspace wake locks
Early suspend
User-space screen access - Sysfs interface
