[How To] Two finger touch for right click

[EchoEum]

I cant make the file. I'm getting the following when I run make.

Code: Select all

gcc -c -Wall -O2 twofingemu.c
In file included from twofingemu.c:17:0:
/usr/include/linux/input.h:12:22: fatal error: sys/time.h: No such file or directory
 #include <sys/time.h>
                      ^
compilation terminated.
Makefile:12: recipe for target 'twofingemu.o' failed
make: *** [twofingemu.o] Error 1

[mikeh8020]

I get to the "twofing --debug" part and I get the following message.

twofing, the two-fingered daemon
Version 0.1.2.20120708

Input device name: "FT5406 memory based driver"
XInput device ID is 7.
XInput device ID for calibrations is 7.
Start Calibration
No calibration data found, use default values.
No valid axis inversion data found.

The hardware:
Pi3B
Official 7" touchscreen

The software:
Raspbian Jessie
RetroPie installed (manual installation on top of Jessie)

[ibex]

I have got exactly the same problem as reported by mikeh8020.

Thank you for any help in advance!

I get to the "twofing --debug" part and I get the following message.

twofing, the two-fingered daemon
Version 0.1.2.20120708

Input device name: "FT5406 memory based driver"
XInput device ID is 7.
XInput device ID for calibrations is 7.
Start Calibration
No calibration data found, use default values.
No valid axis inversion data found.

The hardware:
Pi3B
Official 7" touchscreen

The software:
Raspbian Jessie
RetroPie installed (manual installation on top of Jessie)

[aerowolf]

Make that three of us...

I've attempted following this short tutorial and checking out the information given at http://plippo.de/p/twofing to no avail. If anyone has sorted out a way to resolve this issue I'd love to hear it. Until then I'm going to keep banging my head against the wall. It has to crack eventually right?

[Metallode]

i think that i found @EchoEum
use

Code: Select all

sudo apt-get install libxtst-dev

or spécificly rewritte this

Code: Select all

 sudo apt-get install build-essential libx11-dev libxtst-dev libxi-dev x11proto-randr-dev libxrandr-dev

EDIT: sorry, aerowolf it was for @EchoEum

[aerowolf]

i think that i found
use

Code: Select all

sudo apt-get install libxtst-dev

or spécificly rewritte this

Code: Select all

 sudo apt-get install build-essential libx11-dev libxtst-dev libxi-dev x11proto-randr-dev libxrandr-dev

So what you've done is replace the step where you install the libs

Code: Select all

 sudo apt-get install build-essential libx11-dev libxtst-dev libxi-dev x11proto-randr-dev libxrandr-dev

with this instead?

Code: Select all

sudo apt-get install libxtst-dev

In that case, I'm guessing I should remove all of the other items and just leave libxtst-dev installed. Here's what I'll try when I get a chance:

Code: Select all

sudo apt-get autoremove build-essential libx11-dev libxi-dev x11proto-randr-dev libxrandr-dev
cd twofing-0.1.2
make
sudo cp twofing /usr/bin/
twofing --debug

I've already got the rules file in place, and I'm assuming everything still compiles correctly without the other libs. If I misinterpreted your comment let me know...it'll be a while before I can test it anyway.

[wolfmanjm]

I get the infamous "No valid axis inversion data found."

This stops it running. I solved it by making a simple change to the code...

https://github.com/Plippo/twofing/blob/ ... mu.c#L1036

change this line to..

Code: Select all

readCalibrationData(0);

Then recompile.

Then it seems to work.

[FlipPI76]

Everyone who is having problems with Jessie and the debug message "No valid axis inversion data found".
I think I found a workaround... Additional to the installation procedure in the beginning of this thread, I performed the following steps:

Install evdev driver

Code: Select all

sudo apt-get install xserver-xorg-input-evdev

Modify X11-conf (in Jessie it's here: /usr/share/X11/xorg.conf.d)

Code: Select all

sudo nano /usr/share/X11/xorg.conf.d/40-libinput.conf

At the end of the file add:

Code: Select all

Section "InputClass"
   Identifier "calibration"
   Driver "evdev"
   MatchProduct "FT5406 memory based driver"

   Option "EmulateThirdButton" "1"
   Option "EmulateThirdButtonTimeout" "750"
   Option "EmulateThirdButtonMoveThreshold" "30"
EndSection

Create a new rule-file

Code: Select all

sudo nano /etc/udev/rules.d/70-touchscreen-raspberrypi.rules

Add the lines below

Code: Select all

KERNEL=="event*",ATTRS{name}=="FT5406 memory based driver",SYMLINK+="twofingtouch",MODE="0440"

Reboot your device

Code: Select all

sudo reboot

After reboot check the X11-logfile

Code: Select all

cat /var/log/Xorg.0.log

There you should find something like:

• 
  [ 13.726] (II) config/udev: Adding input device FT5406 memory based driver (/dev/input/event0)
  [ 13.727] (**) FT5406 memory based driver: Applying InputClass "evdev touchscreen catchall"
  [ 13.727] (**) FT5406 memory based driver: Applying InputClass "libinput touchscreen catchall"
  [ 13.727] (**) FT5406 memory based driver: Applying InputClass "calibration"
  [ 13.727] (II) LoadModule: "evdev"
  [ 13.728] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
  [ 14.621] (II) Module evdev: vendor="X.Org Foundation"
  [ 14.622] compiled for 1.18.4, module version = 2.10.3
  [ 14.622] Module class: X.Org XInput Driver
  [ 14.622] ABI class: X.Org XInput driver, version 22.1
  [ 14.622] (II) Using input driver 'evdev' for 'FT5406 memory based driver'
  [ 14.622] (**) FT5406 memory based driver: always reports core events
  [ 14.622] (**) evdev: FT5406 memory based driver: Device: "/dev/input/event0"
  [ 14.623] (--) evdev: FT5406 memory based driver: Vendor 0 Product 0
  [ 14.623] (--) evdev: FT5406 memory based driver: Found absolute axes
  [ 14.623] (--) evdev: FT5406 memory based driver: Found absolute multitouch axes
  [ 14.623] (II) evdev: FT5406 memory based driver: No buttons found, faking one.
  [ 14.623] (--) evdev: FT5406 memory based driver: Found x and y absolute axes
  [ 14.623] (--) evdev: FT5406 memory based driver: Found absolute touchscreen
  [ 14.623] (II) evdev: FT5406 memory based driver: Configuring as touchscreen
  [ 14.623] (**) Option "EmulateThirdButton" "1"
  [ 14.623] (**) Option "EmulateThirdButtonTimeout" "750"
  [ 14.624] (**) Option "EmulateThirdButtonMoveThreshold" "30"
  [ 14.624] (**) evdev: FT5406 memory based driver: YAxisMapping: buttons 4 and 5
  [ 14.624] (**) evdev: FT5406 memory based driver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
  [ 14.624] (**) Option "config_info" "udev:/sys/devices/virtual/input/input0/event0"
  [ 14.624] (II) XINPUT: Adding extended input device "FT5406 memory based driver" (type: TOUCHSCREEN, id 6)
  [ 14.624] (II) evdev: FT5406 memory based driver: initialized for absolute axes.
  [ 14.625] (**) FT5406 memory based driver: (accel) keeping acceleration scheme 1
  [ 14.625] (**) FT5406 memory based driver: (accel) acceleration profile 0
  [ 14.626] (**) FT5406 memory based driver: (accel) acceleration factor: 2.000
  [ 14.626] (**) FT5406 memory based driver: (accel) acceleration threshold: 4
  

Now start twofing with debug option

Code: Select all

twofing --debug

and you should see

• 
  twofing, the two-fingered daemon
  Version 0.1.2.20120708
  
  Input device name: "FT5406 memory based driver"
  XInput device id is 6.
  XInput device id for calibration is 6.
  Start calibration
  No calibration data found, use default values.
  Calibration: MinX: 0; MaxX: 800; MinY: 0; MaxY: 480
  Invert X Axis: No
  Invert Y Axis: No
  Swap Axes: No
  Calibration Matrix: 1.000000 0.000000 0.000000
  0.000000 1.000000 0.000000
  Grab Result: 0
  Reading input from device ... (interrupt to exit)
  Current window: 'lxtermin'
  Use default profile.
  

Now twofing should work...

Cheers,
Flip

[FlipPI76]

For the sake of completeness, here the complete installation from scratch...

Code: Select all

# Install packages
sudo apt-get update && sudo apt-get install build-essential libx11-dev libxi-dev x11proto-randr-dev libxrandr-dev libxtst-dev xserver-xorg-input-evdev

Code: Select all

# Install twofing
cd ~
wget http://plippo.de/dwl/twofing/twofing-0.1.2.tar.gz
tar -xvzf twofing-0.1.2.tar.gz
cd twofing-0.1.2
make && sudo make install

Code: Select all

# create a new rule-file
sudo nano /etc/udev/rules.d/70-touchscreen-raspberrypi.rules

# add the following line
KERNEL=="event*",ATTRS{name}=="FT5406 memory based driver",SYMLINK+="twofingtouch",MODE="0440"

Code: Select all

# modify X11 config
sudo nano /usr/share/X11/xorg.conf.d/40-libinput.conf

# add the following lines at the end of the file
Section "InputClass"
   Identifier "calibration"
   Driver "evdev"
   MatchProduct "FT5406 memory based driver"

   Option "EmulateThirdButton" "1"
   Option "EmulateThirdButtonTimeout" "750"
   Option "EmulateThirdButtonMoveThreshold" "30"
EndSection

Code: Select all

# Reboot your device
sudo reboot

Code: Select all

# Check if twofing is working 
twofing --debug

Code: Select all

# Add twofing to autostart
nano ~/.config/lxsession/LXDE-pi/autostart

# add the line at the end
@/usr/bin/twofing

Code: Select all

# Cleanup
cd ~
rm -rf ~/twofing-0.1.2

[Tozzi1]

Works like a charm. Thanks a lot, I've been pulling my hair out over this.

[Webmets]

Everyone who is having problems with Jessie and the debug message "No valid axis inversion data found".
I think I found a workaround... Additional to the installation procedure in the beginning of this thread, I performed the following steps:

Install evdev driver

Code: Select all

sudo apt-get install xserver-xorg-input-evdev

Modify X11-conf (in Jessie it's here: /usr/share/X11/xorg.conf.d)

Code: Select all

sudo nano /usr/share/X11/xorg.conf.d/40-libinput.conf

At the end of the file add:

Code: Select all

Section "InputClass"
   Identifier "calibration"
   Driver "evdev"
   MatchProduct "FT5406 memory based driver"

   Option "EmulateThirdButton" "1"
   Option "EmulateThirdButtonTimeout" "750"
   Option "EmulateThirdButtonMoveThreshold" "30"
EndSection

Create a new rule-file

Code: Select all

sudo nano /etc/udev/rules.d/70-touchscreen-raspberrypi.rules

Add the lines below

Code: Select all

KERNEL=="event*",ATTRS{name}=="FT5406 memory based driver",SYMLINK+="twofingtouch",MODE="0440"

Reboot your device

Code: Select all

sudo reboot

After reboot check the X11-logfile

Code: Select all

cat /var/log/Xorg.0.log

There you should find something like:

• 
  [ 13.726] (II) config/udev: Adding input device FT5406 memory based driver (/dev/input/event0)
  [ 13.727] (**) FT5406 memory based driver: Applying InputClass "evdev touchscreen catchall"
  [ 13.727] (**) FT5406 memory based driver: Applying InputClass "libinput touchscreen catchall"
  [ 13.727] (**) FT5406 memory based driver: Applying InputClass "calibration"
  [ 13.727] (II) LoadModule: "evdev"
  [ 13.728] (II) Loading /usr/lib/xorg/modules/input/evdev_drv.so
  [ 14.621] (II) Module evdev: vendor="X.Org Foundation"
  [ 14.622] compiled for 1.18.4, module version = 2.10.3
  [ 14.622] Module class: X.Org XInput Driver
  [ 14.622] ABI class: X.Org XInput driver, version 22.1
  [ 14.622] (II) Using input driver 'evdev' for 'FT5406 memory based driver'
  [ 14.622] (**) FT5406 memory based driver: always reports core events
  [ 14.622] (**) evdev: FT5406 memory based driver: Device: "/dev/input/event0"
  [ 14.623] (--) evdev: FT5406 memory based driver: Vendor 0 Product 0
  [ 14.623] (--) evdev: FT5406 memory based driver: Found absolute axes
  [ 14.623] (--) evdev: FT5406 memory based driver: Found absolute multitouch axes
  [ 14.623] (II) evdev: FT5406 memory based driver: No buttons found, faking one.
  [ 14.623] (--) evdev: FT5406 memory based driver: Found x and y absolute axes
  [ 14.623] (--) evdev: FT5406 memory based driver: Found absolute touchscreen
  [ 14.623] (II) evdev: FT5406 memory based driver: Configuring as touchscreen
  [ 14.623] (**) Option "EmulateThirdButton" "1"
  [ 14.623] (**) Option "EmulateThirdButtonTimeout" "750"
  [ 14.624] (**) Option "EmulateThirdButtonMoveThreshold" "30"
  [ 14.624] (**) evdev: FT5406 memory based driver: YAxisMapping: buttons 4 and 5
  [ 14.624] (**) evdev: FT5406 memory based driver: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
  [ 14.624] (**) Option "config_info" "udev:/sys/devices/virtual/input/input0/event0"
  [ 14.624] (II) XINPUT: Adding extended input device "FT5406 memory based driver" (type: TOUCHSCREEN, id 6)
  [ 14.624] (II) evdev: FT5406 memory based driver: initialized for absolute axes.
  [ 14.625] (**) FT5406 memory based driver: (accel) keeping acceleration scheme 1
  [ 14.625] (**) FT5406 memory based driver: (accel) acceleration profile 0
  [ 14.626] (**) FT5406 memory based driver: (accel) acceleration factor: 2.000
  [ 14.626] (**) FT5406 memory based driver: (accel) acceleration threshold: 4
  

Now start twofing with debug option

Code: Select all

twofing --debug

and you should see

• 
  twofing, the two-fingered daemon
  Version 0.1.2.20120708
  
  Input device name: "FT5406 memory based driver"
  XInput device id is 6.
  XInput device id for calibration is 6.
  Start calibration
  No calibration data found, use default values.
  Calibration: MinX: 0; MaxX: 800; MinY: 0; MaxY: 480
  Invert X Axis: No
  Invert Y Axis: No
  Swap Axes: No
  Calibration Matrix: 1.000000 0.000000 0.000000
  0.000000 1.000000 0.000000
  Grab Result: 0
  Reading input from device ... (interrupt to exit)
  Current window: 'lxtermin'
  Use default profile.
  

Now twofing should work...

Cheers,
Flip

After following these steps, twofing works, but now whenever I start twofing from commandline, my desktop disapears, and the file manager crashes. Any idea how that happend?

[daniel_e]

I keep getting this annoying error, as I have gone through everything at least 4 times... I can't find my mistake. Can anyone help?

Code: Select all

twofing, the two-fingered daemon
Version 0.1.2.20120708

/dev/twofingtouch: No such file or directory

[skinkone]

For the sake of completeness, here the complete installation from scratch...
...
...

Just wanted to thank you: this worked for me except I had to change "FT5406 memory based driver" to "USBest Technology SiS HID Touch Controller" for my Hannspree 27" touchscreen monitor. Perhaps that's an obvious mod to the majority of people reading this, but to someone like me who is just slightly more capable than a trained monkey in all things Linux ( ), it could end the frustration!

[paulkonp]

Two finger support is working with the instructions by @FlipPI76, however I'm unable to get single finger long-press right-click to work.

Is there a simple way to enable long-press for single finger that will show the right-click context menu? I'm using Quanta OpticalTouchScreen device.

Thanks.

[robiv8]

So i have :
Linux Testrechner 4.14.34-v7+ #1110 SMP Mon Apr 16 15:18:51 BST 2018 armv7l GNU/Linux

I do all step by step but no luck!

pi@Testrechner:~ $ twofing --debug
twofing, the two-fingered daemon
Version 0.1.2.20120708

/dev/twofingtouch: No such file or directory

My /etc/udev/rules.d/70-touchscreen-egalax.rules:

KERNEL=="event*",ATTRS{name}=="eGalaxTouch Virtual Device for Multi",SYMLINK+="twofingtouch",RUN+="/bin/chmod a+r /dev/twofingtouch"
KERNEL=="event*",ATTRS{name}=="FT5406 memory based driver",SYMLINK+="twofingtouch",MODE="0440"

Any help please?

[il_diavolo]

Anyone got this to work with Buster?

My set up is an early Pi2B and the official 7" screen. I had twofing working correctly with Stretch but it doesn't work after a fresh install of Buster, following the installation instructions in this thread.
The error I get when I type "twofing --debug" in a terminal window is

Code: Select all

/dev/twofingtouch: No such file or directory

EDIT Just noticed this is the same error that robiv8 in the post above had with Stretch. I'm non the wiser though!

[il_diavolo]

So, I've solved it myself, sorry to have bothered you all.

The solution is to add the missing bit to:

Code: Select all

sudo nano /etc/udev/rules.d/70-touchscreen-raspberrypi.rules
KERNEL=="event*",ATTRS{name}=="FT5406 memory based driver",SYMLINK+="twofingtouch",MODE="0440"

which is:

Code: Select all

KERNEL=="event*",ATTRS{name}=="FT5406 memory based driver",SYMLINK+="twofingtouch",RUN+="/bin/chmod a+r /dev/twofingtouch",MODE="0440"

Cheers

[Redhatter]

I figured I'd share this here… since some of the posts have been a big help to getting multi-touch working. I've bundled the above fixes into a Debian package.

Basically, there's a fork of twofing that added Debian packaging, and I forked that some time ago to add a udev rule file for the Raspberry Pi touch-screens.

My fork of a fork is here: https://github.com/sjlongland/twofing

I've submitted this as a pull request upstream. Update: this has been accepted upstream.

To build: install the dependencies mentioned earlier in this thread, then run

Code: Select all

dpkg-buildpackage -us -uc -b

. You'll be left with a .deb file which may then be deployed on any Raspberry Pi with a 7" screen attached.

[huunguyen]

Code: Select all

twofing, the two-fingered daemon
Version 0.1.2.20120708

/dev/twofingtouch: No such file or directory

fixed on buster for ras pi 3

sudo apt install input-utils
sudo ln -s /dev/input/event0 /dev/twofingtouch

[Pydat]

Hello !

I've a Asus VT168H touchscreen plugged and I've follow all the topic.

Have going true the installation (the updated one).
Get some adjustment from some user to fit some bug.

Then I am stuck with the --debug,
I've got the "No valid axis inversion data found".

But maybe I have a clue: (???)
When I call the --debug, the terminal told me that he's calling the xinput ID 6, but when I do a xinput-list, my touchscreen is on ID 9 "ELAN touchscreen"

How could I force/call the programme to get the correct ID ??

Also I might say that I'm a newborn linux user with all that it should mean...

Amicalement,

[bokismoki777]

I've a Asus VT168H touchscreen plugged and I've follow all the topic.
...
...
I've got the "No valid axis inversion data found".

As one Linux noob to another, I proudly report I have just succesfully implemented two-finger touch for Asus VT168H on RasPi 3B and Raspbian Stretch. So first of all, thank you all for your invaluable contributions!

I can confirm the instructions from FlipPI76 work. The only thing that needs to be altered is the device name of the touchscreen. Asus VT168H registers in Raspbian as device "ELAN Touchscreen", which can be verified with command "xinput list" or with inspecting the /var/log/Xorg.0.log.

So, alternate step #1: Edit /usr/share/X11/xorg.conf.d/40-libinput.conf file

Code: Select all

sudo nano /usr/share/X11/xorg.conf.d/40-libinput.conf

At the end of the file add:

Code: Select all

Section "InputClass"
   Identifier "calibration"
   Driver "evdev"
   MatchProduct "ELAN Touchscreen"

   Option "EmulateThirdButton" "1"
   Option "EmulateThirdButtonTimeout" "750"
   Option "EmulateThirdButtonMoveThreshold" "30"
EndSection

Alternate step #2: Create a new udev rule-file. You can name it anything you like (except for the '70-' prefix which is there to ensure the proper order of processing multiple rule files). I chose to name mine after Asus and ELAN, because it contains configuration based on this specific touchscreen:

Code: Select all

sudo nano /etc/udev/rules.d/70-touchscreen-asusELAN.rules

Add the following line:

Code: Select all

KERNEL=="event*",ATTRS{name}=="ELAN Touchscreen",SYMLINK+="twofingtouch",MODE="0440"

That's it. After reboot two-finger tap worked like a charm!

[Lowkeycoat]

i am also getting error

twofing, the two-fingered daemon
Version 0.1.2.20120708

/dev/twofingtouch: No such file or directory

when i type in "ls -l /dev/twofingtouch " i get

ls: cannot access '/dev/twofing': No such file or directory


typed in "ls -l /etc/udev/rules.d/70-touchscreen-egalax.rules" got

-rw-r--r-- 1 root root 123 Jun 2 21:45 /etc/udev/rules.d/70-touchscreen-egalax.rules

and this is my sudo nano /etc/udev/rules.d/70-touchscreen-egalax.rules

KERNEL=="event*",ATTRS{name}=="FT5406 memory based driver",SYMLINK+="twofingtouch",RUN+="/bin/chmod a+r /dev/twofingtouch"

i cannot for the life of me find what i did wrong. ths is the most current raspbian os
i did a fresh install 2 days ago all upgraded&&updated

plz help thanks in advanced

[RobertMcLean]

I have Official 7" touch screen and Raspbian downloaded and updated today 18 Jul 2020.

When I follow the instructions given by FlPi76, which have worked for some people here, I have the following problems

1) after sudo apt-get update && etc
I get error messages Could not open lock file /var/lib/dpkg/lock-fronteend etc
and
Unable to acquire the dpkg frontend lock etc are you root ?

I am new to Linux, but I thought sudo made me super user, or root ? Am I misunderstanding that ? do I need to do something to fix this ?

But I thought I would continue with the instructions anyway, maybe I was lucky and did not need updates since I did a fresh install today.

But after make && sudo make install gcc -c-Wall -02 twofingemu.c
I got fatal error :X11/extensions/XTest.h no such file of directory

Am I missing a file ? Should I just add that file and retry ?

Thanks for any suggestions

[bokismoki777]

I am new to Linux, but I thought sudo made me super user, or root ? Am I misunderstanding that ? do I need to do something to fix this ?
...
But after make && sudo make install gcc -c-Wall -02 twofingemu.c
I got fatal error :X11/extensions/XTest.h no such file of directory
...
Am I missing a file ? Should I just add that file and retry ?

"sudo" does make you root (super user). There is nothing else you need to do. I've never encountered your specific problem before, but I found this article which might give you a clue how to proceed: https://itsfoss.com/could-not-get-lock-error/. But like you said, updating may not be absolutely necessary if you installed a fresh OS. But the fact that the lock file exists is not a good sign in itself.

As for your second error, the internet suggests installing a missing package "libxtst-dev":

Code: Select all

sudo apt-get install libxtst-dev

So you might try that. But the question is why is the package missing? And what else might be missing as well? Which Raspbian did you install? I would definitely recommend "Raspberry Pi OS (32-bit) with desktop and recommended software" from https://www.raspberrypi.org/downloads/raspberry-pi-os/.

[RobertMcLean]

Thank you, I have it all working now.
The lock problem just went away, the information at itsfoss.com makes me think there was just something else running at the time, but I have no idea what.

I installed the libxtst-dev. The suggested Raspberry Pi OS (32-bit with desktop and applications is what I had installed, so I dont know why I got that error.

To add TwoFing to autostart I put it in /etc/xdg/lxsession/LXDE-pi/autostart
When I added lxsession/LXDE-pi directories to .config and put an autostart in there
the result was the normal start up was short circuited and I did not get the "normal" graphical screen, I got a black screen
and right clicking on it gave me a menu for OpenBox or some name like that. Fortunately I could open a terminal from there and undo what I did, and change the autostart file at /etc/xdg/lxsession/LXDE-pi/

I realize now I could have left it in .config/lxsession/LXDE-pi and called up the /etc ... autostart first, but its working now, so I think will leave it alone.