touch screen configuration

98 views
Skip to first unread message

Claw

unread,
Feb 25, 2009, 8:55:08 AM2/25/09
to android-porting
Hi,

I am able to receive the events from the touch screen into the home
page of the android but the mapping is not correct. Each touch
converts into a touch at the top bar, irrespective of where it is
being tapped. The tslib is configured but I don't have an idea as to
how it could be linked to Android.

Any suggestion would help.

Thanks

virstud

unread,
Feb 25, 2009, 11:24:17 AM2/25/09
to android-porting
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

---------------------------------------------------------------------
verify init.rc:

chown radio system /sys/android_power/state
chown radio system /sys/android_power/request_state
chown radio system /sys/android_power/acquire_full_wake_lock
chown radio system /sys/android_power/acquire_partial_wake_lock
chown radio system /sys/android_power/release_wake_lock
chown radio system /sys/power/state
chown radio system /sys/power/wake_lock
chown radio system /sys/power/wake_unlock
chmod 0660 /sys/power/state
chmod 0660 /sys/power/wake_lock
chmod 0660 /sys/power/wake_unlock


service zygote /system/bin/app_process -Xzygote /system/bin --zygote --
start-system-server
socket zygote stream 666
onrestart write /sys/android_power/request_state wake
onrestart write /sys/power/state on
--------------------------------------------------------------------------------------------
or use last ver init.rc


if not resolv problem:

1.ts scale problems
2.use spi ts driver

Claw

unread,
Mar 23, 2009, 6:18:10 AM3/23/09
to android-porting
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 done scaling using the tslib? If so, how?

Thanks in advance.
> > I am able to receive the events from thetouchscreen into the home
> > page of the android but the mapping is not correct. Eachtouch
> > converts into atouchat the top bar, irrespective of where it is

Jim

unread,
Mar 23, 2009, 7:24:57 AM3/23/09
to android-porting

Claw

unread,
Mar 23, 2009, 11:06:52 AM3/23/09
to android-porting
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.

Is this link a precursor to touchscreen work?
http://www.kandroid.org/android_pdk/keymaps_keyboard_input.html . I
have implemented a generic keyboard driver for my device which is
working perfectly well for linux but only the Enter key works in
android home page where as the other arrow keys do not.

Thanks in advance.

Manav Gautama

unread,
Mar 23, 2009, 11:15:23 AM3/23/09
to android...@googlegroups.com
On Mon, Mar 23, 2009 at 8:36 PM, Claw <praveeng...@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
with inputdevice which picks up pointercal

Jim

unread,
Mar 23, 2009, 6:06:13 PM3/23/09
to android-porting
> 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, look at altering system/usr/keylayout/
querty.kl on the device
Reply all
Reply to author
Forward
0 new messages