Evtouch on fully updated Karmic (or current lucid) does not see the
NextWindow touchscreen on my HP TouchSmart 600-1050
See also: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-
evdev/+bug/379313
** Attachment added: "evtouch_hal.out"
http://launchpadlibrarian.net/37860091/evtouc
This fdi file work ok for my LG L1730SF touch screen. I saved it as:
/etc/hal/fdi/policy/lgtouch.fdi
evtouch
raw
true
50
on
3815
3948
295
200
CCW
true
false
I have a Xenarc 700TSV. it responds to touch, however cannot be
calibrated correctly.
** Attachment added: "lshal for Xenarc 700TSV"
http://launchpadlibrarian.net/19145097/lshal.txt
--
make evtouch devices work with hal-input in intrepid
https://bugs.launchpad.net/bugs/261873
You received thi
Also. here's the lshal for that lilliput 629GL in case it helps.
** Attachment added: "lshal.txt"
http://launchpadlibrarian.net/18889951/lshal.txt
--
make evtouch devices work with hal-input in intrepid
https://bugs.launchpad.net/bugs/261873
You received this bug notification because you are
Wow I'm sorry, ignore the last post and use this file (I was using a few
double-negatives in that configuration, really stupid). Again, this is
for lilliput 629GL 7-inch eGalax touchscreen.
evtouch
80
310
1970
1680
CW
Raw
Here's a good .fdi file for my Lilliput 629GL. The CarPC people will be
happy! This is an eGalax at heart, but actually has eGalax in the
product, so the previous .fdi didn't work.
evtouch
1
1
80
310
1970
1680
Raw
Setting movelimit to 2 in 10-Panasonic.fdi above makes drawing smooth in
karbon14 etc. Should be the same for Fujitsu since they are really the
same device. Can match contain an OR or regex in .FDI files? If so these
could be merged (they just have a slightly different manufacturer
string)
** Atta
most (all?) evtouch devices require a lower value for Option MoveLimit
as in https://bugs.launchpad.net/ubuntu/+source/xf86-input-
evtouch/+bug/204633
Can a value for this option be included in .FDI files? Not clear from
linked issue whether one generic value works for all devices.
--
make evtou
lshal output in case the .fdi above needs to be made more selective. can
this make it into intrepid?
udi =
'/org/freedesktop/Hal/devices/usb_device_430_501_noserial_if0_logicaldev_input'
info.capabilities = {'input', 'input.mouse'} (string list)
info.category = 'input' (string)
info.parent
here is an excellent calibration for my Panasonic CF-T2.
** Attachment added: "config"
http://launchpadlibrarian.net/18809637/config
--
make evtouch devices work with hal-input in intrepid
https://bugs.launchpad.net/bugs/261873
You received this bug notification because you are a member of Ub
I may have a better calibration after testing, but here's a first draft
in case I drop the ball.
** Attachment added: "/etc/evtouch/config"
http://launchpadlibrarian.net/18455448/config
--
make evtouch devices work with hal-input in intrepid
https://bugs.launchpad.net/bugs/261873
You received
I have a Panasonic "Let's Note" (Toughbook) T2. This FDI works for me.
Great work with the new xinput integration guys, much better than the
old "calibration by algebra" method I'd been using. I'm so excited I
want to swear in text. No swearing on Launchpad right?
PS for those following along at h
Just post a comment here once you uploaded the FDI. I will upgrade,
calibrate and send you the config file. Thanks a lot :-)
--
make evtouch devices work with hal-input in intrepid
https://bugs.launchpad.net/bugs/261873
You received this bug notification because you are a member of Ubuntu
Bugs,
The Calibrate option is handled by hal on the fly now, with the last
upload the evtouch calibration tool (which now has a menu entry in
"System->Administration->Calibrate Touchscreen") will also notify users
if their device isnt known by hal and instruct them how to generate
useful lshal output and
Sorry for being late but I have only access to this touchscreen since
this week.
The touchscreen is a "Xernarc 7" 706 series."
In Hardy and in Intrepid, it's basically working well with evtouch
except that it's very painful to calibrate and we still didn't succeed
to have a good calibration. (The
what kind of touchscreen is that ? it will only work with devices that
have a valid .fdi file, i made several calls on mailing lists and via
planet.ubuntu.com to send me lshal output for devices known to have
worked before with evtouch. if you own such a touchscreen, please attach
your lshal output
The bug is not fixed for me as hal gives the error "Wrong UDI" :
libhal.c 2016 : invalid udi: --key doesn't startwith
'/org/freedesktop/Hal/devices/'.
error: libhal_device_remove_property: (null): (null)
And it doesn't work (or, at least, I still don't understand how to make it
works)
--
m
This bug was fixed in the package xf86-input-evtouch - 0.8.7-3ubuntu8
---
xf86-input-evtouch (0.8.7-3ubuntu8) intrepid; urgency=low
* add 09_calibrate-script-halification.patch, adds hal functionallity to
calibration tool, makes the script work under X and gives useful output
** Changed in: xf86-input-evtouch (Ubuntu)
Importance: Undecided => High
Status: New => Triaged
Target: None => intrepid-alpha-6
--
make evtouch devices work with hal-input in intrepid
https://bugs.launchpad.net/bugs/261873
You received this bug notification because you are a mem
a .fdi file for an eGalax touchscreen from a Samsung Q1 Ultra MID:
[EMAIL PROTECTED]:~$ cat /etc/hal/fdi/policy/10-eGalax.fdi
evtouch
130
197
3945
3894
30
750
click
3
2
40
1
an .fdi file for an IDEACO touchscreen used in a CLEVO (nexoc osiris 621)
notebook:
[EMAIL PROTECTED]:~$ cat /etc/hal/fdi/policy/10-ideaco.fdi
evtouch
116
268
7940
7828
raw
a script to apply calibration data based on teh xkb one we use:
cat ../hal-setup-touchscreen
#!/bin/sh
#
# borrowed from Fedora and modified to apply touchscreen calibration data
#
[ -x /usr/bin/hal-set-property ] || exit 0
. /etc/default/evtouch > /dev/null 2>&1 || exit 0
hal_set () {
if [
22 matches
Mail list logo
