Currently, there are some issues with this specific model of the Win4:
There is a SteamOS Handheld Controller created by what is most likely InputPlumber, boot logs confirm that I think (it does detect it's a GPD Win 4 as well). However, it doesn't do anything and only the Xbox 360 Controller actually reads inputs from the device.
logs-this-boot.txt
I attach also these logs:
udevadm_info_a_sys_class_dmi_id.txt
cat_proc_bus_input_devices.txt
During "sudo libinput debug-events", back buttons of the GPD Win 4 2023 are reported as KEY_F20 and KEY_F21
"cat /sys/bus/iio/devices/*/name" result is "bmi260".
Currently, there are some issues with this specific model of the Win4:
There is a SteamOS Handheld Controller created by what is most likely InputPlumber, boot logs confirm that I think (it does detect it's a GPD Win 4 as well). However, it doesn't do anything and only the Xbox 360 Controller actually reads inputs from the device.
logs-this-boot.txt
I attach also these logs:
udevadm_info_a_sys_class_dmi_id.txt
cat_proc_bus_input_devices.txt
During "sudo libinput debug-events", back buttons of the GPD Win 4 2023 are reported as KEY_F20 and KEY_F21
"cat /sys/bus/iio/devices/*/name" result is "bmi260".