qmk/qmk_firmware

[Bug] Mouse movement freaks out on resume from suspend - on chibiOS

Open

#16,683 opened on Mar 18, 2022

View on GitHub
 (4 comments) (0 reactions) (0 assignees)C (43,867 forks)batch import
bughelp wanted

Repository metrics

Stars
 (20,368 stars)
PR merge metrics
 (Avg merge 20d 9h) (27 merged PRs in 30d)

Description

Describe the Bug

when resuming from sleep/suspend, the mouse movement (x and y reports) don't work. with my large mouse reports, it does... kind of, but much slowed down. To the point of unusable.

Similarly odd behavior happens with mousekeys.

System Information

**Keyboard: Tractyl Manuform 5x6 blackpill (f411) Operating system: macOS qmk doctor output:

Ψ QMK Doctor is checking your environment.
Ψ CLI version: 1.0.0
Ψ QMK home: /Users/drashna/repos/qmk_firmware
Ψ Detected macOS 11.6.4.
Ψ Git branch: develop
Ψ Repo version: 0.16.5
Ψ CLI installed in virtualenv.
Ψ All dependencies are installed.
Ψ Found arm-none-eabi-gcc version 10.2.1
Ψ Found avr-gcc version 11.1.0
⚠ We do not recommend avr-gcc newer than 8. Downgrading to 8.x is recommended.
Ψ Found avrdude version 6.4
Ψ Found dfu-util version 0.11
Ψ Found dfu-programmer version 0.7.2
Ψ Submodules are up to date.

Any keyboard related software installed?

  • AutoHotKey (Windows)
  • Karabiner (macOS)
  • Other:

Additional Context

Contributor guide

Research direction
Investigate the ChibiOS suspend/resume code path for USB HID mouse reports. Check if mouse state is properly reinitialized after resume. Trace the mouse report generation after resume and compare with normal operation.
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.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
CGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40