qmk/qmk_firmware

[Bug] Looks like 0.11.0 broke something for jj40

Open

#11,389 opened on Jan 1, 2021

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

Hi,

I've wanted to alter the keymap for my jj40 board. When I flashed the firmware, keys started to behave strange. Sometimes there was no output at all, sometimes they would 'stick' (e.g. I type 'g' and the output goes 'gggggg...' until I hit 'g' again) and sometimes there would be a delay after I hit the key. Backlight Underglow wouldn't work at all. I've tried to compile the firmware both locally and on the website and I've had the same effect.

With the help of guys in discord (spidey3, Dasky) it was figured out that the last firmware that was working was compiled with 0.10.54. Everything after that just didn't work.

Contributor guide

Research direction
Compare the QMK firmware source code between versions 0.10.54 and 0.11.0, focusing on changes in matrix scanning, debounce, and keyboard specific files for jj40 (e.g., keyboards/jj40/). Look for any modifications to the keymap or default keymap that could cause stuck keys or underglow issues.
Tech stack
c
Domain
embedded iot
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.
Half day
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.
Unclear
Prerequisites
CGitQMK basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30