qmk/qmk_firmware

[Bug] Azoteq mouse button processing bug - resets the status of mouse buttons

Open

#26168 opened on Apr 21, 2026

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C (20,368 stars) (43,867 forks)batch import
bughelp wanted

Description

Describe the Bug

Hi I think there's a bug in the way mouse buttons are processed in azoteq_iqs5xx.c. It's preventing click&drag if mouse click is coming from outside of Azoteq device. It comes down to the fact that there's an empty mouse report created called temp_report and it's then being returned without consideration of previous mouse_report state. This is causing mouse button release even though user is still holding the key. I have shown this on my stream.

Thank you.

Keyboard Used

No response

Link to product page (if applicable)

No response

Operating System

All

qmk doctor Output

Is AutoHotKey / Karabiner installed

  • AutoHotKey (Windows)
  • Karabiner (macOS)

Other keyboard-related software installed

No response

Additional Context

No response

Contributor guide

Tech stack
c
Domain
backend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
C programmingHID report structure
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80
Research direction
Investigate the azoteq iqs5xx.c file, specifically the function around line 356 where temp report is created. Understand how mouse report global state is used and why returning temp report without merging previous button states causes clicks to be released. Review the video link for a demonstration of the bug. The fix likely involves preserving the button state from mouse report into temp report before processing.