Arch Linux

mip001

Member

Registered: 2024-10-16

Posts: 1

Constant KEY_BRIGHTNESSUP Signals from Unknown Input Device

Hello,

Apologies for my lack of familiarity with Linux and my poor English. I've recently installed Arch Linux on my Honor Magicbook 2023, and I've encountered an issue where an unknown device keeps sending KEY_BRIGHTNESSUP events. Specifically, when I run

evtest /dev/input/event14

I get the following output:

Input driver version is 1.0.1
Input device ID: bus 0x18 vendor 0x27c6 product 0x1e0 version 0x100
Input device name: "GXTP7863:00 27C6:01E0 UNKNOWN"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 224 (KEY_BRIGHTNESSDOWN)
    Event code 225 (KEY_BRIGHTNESSUP)
    Event code 248 (KEY_MICMUTE)
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Key repeat handling:
  Repeat type 20 (EV_REP)
    Repeat code 0 (REP_DELAY)
      Value    250
    Repeat code 1 (REP_PERIOD)
      Value     33
Properties:
Testing ... (interrupt to exit)
Event: time 1729078900.492670, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 2
Event: time 1729078900.492670, -------------- SYN_REPORT ------------
Event: time 1729078900.529416, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 2
Event: time 1729078900.529416, -------------- SYN_REPORT ------------
Event: time 1729078900.569407, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 2
Event: time 1729078900.569407, -------------- SYN_REPORT ------------
Event: time 1729078900.606089, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 2
Event: time 1729078900.606089, -------------- SYN_REPORT ------------
Event: time 1729078900.642762, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 2
Event: time 1729078900.642762, -------------- SYN_REPORT ------------
Event: time 1729078900.679402, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 2
Event: time 1729078900.679402, -------------- SYN_REPORT ------------
Event: time 1729078900.715964, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 2
Event: time 1729078900.715964, -------------- SYN_REPORT ------------
Event: time 1729078900.752665, type 1 (EV_KEY), code 225 (KEY_BRIGHTNESSUP), value 2

In practice, this keeps randomly lowering my screen brightness to 0.

This device seems to be related to the touchpad:

-event12  DEVICE_ADDED            GXTP7863:00 27C6:01E0 Mouse       seat0 default group7  cap:p left scroll-nat scroll-button
-event13  DEVICE_ADDED            GXTP7863:00 27C6:01E0 Touchpad    seat0 default group7  cap:pg  size 119x70mm tap(dl off) left scroll-nat scroll-2fg-edge click-buttonareas-clickfinger dwt-on dwtp-on
-event14  DEVICE_ADDED            GXTP7863:00 27C6:01E0 UNKNOWN     seat0 default group7  cap:k

While event13 is the properly functioning touchpad, event14 is the device that continuously sends the key event.

I have tried disabling this device via the kernel, but that also disables the touchpad, which I need. I also attempted to set the device's inhibited value to 1 using udev on startup, but this approach disables the touchpad as well. Is there any way to stop this key event from being sent without disabling the touchpad?

In addition, I've found a similar post that has the same problem. But it seems that they solved the problem using "xinput --disable" which is not available on Wayland.

Here is my system information:

Operating System: Arch Linux 
KDE Plasma Version: 6.2.1
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.11.3-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 16 × 13th Gen Intel® Core™ i5-13500H
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: HONOR
Product Name: GLO-GXXX
System Version: M1020

Thank you in advance for any help you can provide!