Linux USB
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 221774] hid-multitouch: report ID mismatch check breaks touchpad palm detection on ASUS ROG Flow Z13 (2025) GZ302EA (0b05:1a30)
Date: Mon, 03 Aug 2026 18:49:54 +0000	[thread overview]
Message-ID: <bug-221774-208809-Gmk16PfM6r@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221774-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=221774

--- Comment #16 from Lovekesh Solanki (lovekeshsolanki00@gmail.com) ---
(In reply to mayhemandcoffee from comment #14)
> I've tested the palm rejection.
> 
> It is a lot better as the cursor no longer jumps around when I am typing,
> nor is it clicking on stuff. However, I noticed that occasionally, a
Seems like the fix is working.

> keystroke would not register while typing. 
The patch is highly unlikely cause this. I don't think this would even be
fixable in kernel. Keystrokes all follow a different input path nothing
hid-multitouch touches. 
This could be a hardware/firmware issue, you could test running evtest on
keyboard node, if evtest does not list the unregistered keys then the device
didn't even send them. But if it does, then it's likely libinput or the
compositor.


(In reply to mayhemandcoffee from comment #15)
> I should also mention that I have a recent version of libinput and the quirk
> from commit 772c1f5ebb4a4122d55fc392a690056d8c55809d is already present in
> /usr/share/libinput/50-system-asus.quirks.
> 
> [thienan@thienan-pc libinput]$ sed -n '45,55p'
> /usr/share/libinput/50-system-asus.quirks
> AttrKeyboardIntegration=internal
> 
> # enable "disable touchpad while typing" to work with z13 keyboard
> [Asus ROG FLow Z13 2025 keyboard]
> MatchUdevType=keyboard
> MatchBus=usb
> MatchVendor=0x0B05
> MatchProduct=0x1A30
> AttrKeyboardIntegration=internal
About disable-while-typing being greyed out, that seems to be a libinput issue
and should be reported there instead. Touchpad might be getting set as external
by libinput and disabling the feature.

I'm going to send the patch after slightly revising it upstream, please let me
know if I should add a Tested by tag now.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2026-08-03 18:49 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-21  2:37 [Bug 221774] New: hid-multitouch: report ID mismatch check breaks touchpad palm detection on ASUS ROG Flow Z13 (2025) GZ302EA (0b05:1a30) bugzilla-daemon
2026-07-22  6:42 ` [Bug 221774] " bugzilla-daemon
2026-07-22 10:41 ` bugzilla-daemon
2026-07-22 13:03 ` bugzilla-daemon
2026-07-22 15:07 ` bugzilla-daemon
2026-07-23 18:24 ` bugzilla-daemon
2026-07-24  9:28 ` bugzilla-daemon
2026-07-24 13:14 ` bugzilla-daemon
2026-07-24 17:59 ` bugzilla-daemon
2026-07-24 18:00 ` bugzilla-daemon
2026-08-02 19:10 ` bugzilla-daemon
2026-08-02 22:10 ` bugzilla-daemon
2026-08-03  1:31 ` bugzilla-daemon
2026-08-03  5:39 ` bugzilla-daemon
2026-08-03 13:21 ` bugzilla-daemon
2026-08-03 13:29 ` bugzilla-daemon
2026-08-03 18:49 ` bugzilla-daemon [this message]
2026-08-04 14:45 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-221774-208809-Gmk16PfM6r@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox