qmk/qmk_firmware

[Bug] Cannot control RGB Matrix manually, colors repeatedly overwritten with solid color under RGB_MATRIX_NONE mode

Open

#14,686 opened on Oct 4, 2021

View on GitHub
 (13 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

The RGB matrix mode RGB_MATRIX_NONE interferes with manual RGB control. Unable to set RGB states manually.

Setting rgb_matrix_mode(RGB_MATRIX_NONE); results in a constant red colour under every key. When I set an LED color using rgb_matrix_set_color, the new color setting applies for an instant before being overwritten again by the red colour. This makes it impossible to control the LEDs manually.

  • Keyboard: ZSA Moonlander
  • QMK Firmware version: 0.14.16

Contributor guide

Research direction
Inspect the RGB MATRIX NONE mode implementation in QMK. Trace the code path where manual calls to rgb matrix set color are overwritten by the solid color in the matrix update loop. Look for the iteration over all LEDs in matrix scan or rgb matrix task and identify where the default color is applied.
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.
1-3 hours
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.
Clear
Prerequisites
GitCQMK Build Environment
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70