# Touchscreen issues If the screen is connected over USB, issues with the cable may cause similar symptoms. For that, please see [this guide](Physical_Install.md#cable-issues). ## Touch not working on RaspberryOS and derivatives Some DSI screens have issues where touch doesn't work with the default configuration. The current workaround/temporary fix involves changing the kernel driver module used for these displays. Open `/boot/config.txt` for editing using `sudo nano /boot/config.txt` and change ```sh dtoverlay=vc4-kms-v3d ``` to ```sh dtoverlay=vc4-fkms-v3d ``` Close the nano editor using `ctrl`+`x` (exit), then `y` for yes (save). **Reboot** to apply changes. If that doesn't fix it, you can try commenting these lines out, resulting in: ```sh # dtoverlay=vc4-kms-v3d # max_framebuffers=2 ``` **Reboot** to apply changes. ## Touch rotation and matrix If the touch works but registers touch input in a different location from the input, then you may need to apply an input transformation matrix. First you will need your device name. On a terminal, run: ```sh DISPLAY=:0 xinput ``` Output: ```text ⎡ Virtual core pointer id=2 [master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)] ⎜ ↳ ADS7846 Touchscreen id=6 [slave pointer (2)] ⎣ Virtual core keyboard id=3 [master keyboard (2)] ↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)] ``` In this case the device is the ADS7846 Touchscreen, yours may be different You can test a change by running: ```sh DISPLAY=:0 xinput set-prop "" 'Coordinate Transformation Matrix' ``` Where the matrix can be one of the following options: | Rotation | Matrix | |-----------------------------------------|-----------------------| | 0° | `1 0 0 0 1 0 0 0 1` | | 90° Clockwise | `0 -1 1 1 0 0 0 0 1` | | 90° Counter-Clockwise | `0 1 0 -1 0 1 0 0 1` | | 180° (Inverts X and Y) | `-1 0 1 0 -1 1 0 0 1` | | invert Y | `-1 0 1 1 1 0 0 0 1` | | invert X | `-1 0 1 0 1 0 0 0 1` | | expand to twice the size horizontally | `0.5 0 0 0 1 0 0 0 1` | For more in-depth guidance on using Coordinate Transformation Matrices: * [Ubuntu wiki InputCoordinateTransformation](https://wiki.ubuntu.com/X/InputCoordinateTransformation) * [Libinput docs](https://wayland.freedesktop.org/libinput/doc/1.9.0/absolute_axes.html) To make this **permanent**, modify `/etc/udev/rules.d/51-touchscreen.rules`: ```bash sudo nano /etc/udev/rules.d/51-touchscreen.rules ``` ```sh title="51-touchscreen.rules" ACTION=="add", ATTRS{name}=="", ENV{LIBINPUT_CALIBRATION_MATRIX}="" ``` Close the nano editor using `ctrl`+`x` (exit), then `y` for yes (save). !!! example Test: ```sh DISPLAY=:0 xinput set-prop "ADS7846 Touchscreen" 'Coordinate Transformation Matrix' -1 0 1 0 -1 1 0 0 1 ``` Permanent modification: ```bash sudo nano /etc/udev/rules.d/51-touchscreen.rules ``` ```sh title="51-touchscreen.rules" ACTION=="add", ATTRS{name}=="ADS7846 Touchscreen", ENV{LIBINPUT_CALIBRATION_MATRIX}="-1 0 1 0 -1 1 0 0 1" ``` Close the nano editor using `ctrl`+`x` (exit), then `y` for yes (save). !!! example "Alternative" As an alternative **if the above doesn't work**: ```bash sudo nano /usr/share/X11/xorg.conf.d/40-libinput.conf ``` ```sh title="40-libinput.conf" Section "InputClass" Identifier "libinput touchscreen catchall" MatchIsTouchscreen "on" MatchDevicePath "/dev/input/event*" Driver "libinput" Option "TransformationMatrix" "0 -1 1 1 0 0 0 0 1" EndSection ``` Close the nano editor using `ctrl`+`x` (exit), then `y` for yes (save). ## Touch is expanded: This can be due to other framebuffers being active, for example the composite output of Raspberries may be enabled automatically as a fallback when no HDMI device is plugged in. If this is the case: Open `/boot/config.txt` for editing: ```sh sudo nano /boot/config.txt ``` add at the bottom (in the `[all]` section) ```sh title="config.txt" enable_tvout=0 max_framebuffers=1 ``` Close the nano editor using `ctrl`+`x` (exit), then `y` for yes (save). **Reboot** to apply changes.