Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consumer keycodes for launchpad and mission control are unknown #3310

Open
MageJohn opened this issue Nov 24, 2022 · 10 comments
Open

Consumer keycodes for launchpad and mission control are unknown #3310

MageJohn opened this issue Nov 24, 2022 · 10 comments

Comments

@MageJohn
Copy link

I have a Keychron K8 Pro keyboard, and noticed that, when Karabiner-Elements was modifying events for it, the Launchpad and Mission Control keys didn't work. This keyboard sends consumer keycodes (usage page 12) for these buttons, and the other consumer keycodes that this keyboard sends, in particular brightness, play/pause, next and previous song, and volume control keys, are all recognised by Karabiner; they're correctly identified in the Karabiner-EventViewer, and when event modification is enabled they work as expected.

Here's the JSON output of the Unknown Events tab in Karabiner-EventViewer, showing the keycodes being used. The first key pressed is the Mission Control key, and the second is the Launchpad key.

[
  {
    "value": "1",
    "usagePage": "12 (0x000c)",
    "usage": "671 (0x029f)"
  },
  {
    "value": "0",
    "usagePage": "12 (0x000c)",
    "usage": "671 (0x029f)"
  },
  {
    "value": "1",
    "usagePage": "12 (0x000c)",
    "usage": "672 (0x02a0)"
  },
  {
    "value": "0",
    "usagePage": "12 (0x000c)",
    "usage": "672 (0x02a0)"
  }
]

These keycodes are correctly recognised by MacOS and do what I expect. Can they be added to the known events in Karabiner so it passes them through correctly to the virtual keyboard?

@psyspeedi
Copy link

I join

@ucomesdag
Copy link

Same issue on the Keychron K6 Pro, they are registered as unknown events and not passed on.

@puttin
Copy link

puttin commented Jun 6, 2023

Keychron Q1 Pro, exactly same

[
  {
    "value": "1",
    "usagePage": "12 (0x000c)",
    "usage": "671 (0x029f)"
  },
  {
    "value": "0",
    "usagePage": "12 (0x000c)",
    "usage": "671 (0x029f)"
  },
  {
    "value": "1",
    "usagePage": "12 (0x000c)",
    "usage": "672 (0x02a0)"
  },
  {
    "value": "0",
    "usagePage": "12 (0x000c)",
    "usage": "672 (0x02a0)"
  }
]

@puttin
Copy link

puttin commented Jun 6, 2023

@puttin
Copy link

puttin commented Jun 6, 2023

@ucomesdag
Copy link

Would adding this be enough to make it work? 🤷🏼‍♂️

constexpr value_t mission_control(0x029f);
constexpr value_t spotlight(0x0221);

@tborychowski
Copy link

any progress on this? or a workaround? I have a Keychron Q3 and the same issue.

@sevenshamrocks
Copy link

sevenshamrocks commented Sep 4, 2024

I'm having the same issue. Those two commands don't work with Karabiner running. Keychron K8 Pro.

@jjaychen1e
Copy link

Same issue here.

@bellflower2015
Copy link

bellflower2015 commented Oct 7, 2024

Same issue with Keychron B1 Pro.
671: MissionControl(F3), 672: LaunchPad(F4), and 545: SpotlightSearch(F5).

[
  {
    "value": "1",
    "usagePage": "12 (0x000c)",
    "usage": "671 (0x029f)"
  },
  {
    "value": "0",
    "usagePage": "12 (0x000c)",
    "usage": "671 (0x029f)"
  },
  {
    "value": "1",
    "usagePage": "12 (0x000c)",
    "usage": "672 (0x02a0)"
  },
  {
    "value": "0",
    "usagePage": "12 (0x000c)",
    "usage": "672 (0x02a0)"
  },
  {
    "value": "1",
    "usagePage": "12 (0x000c)",
    "usage": "545 (0x0221)"
  },
  {
    "value": "0",
    "usagePage": "12 (0x000c)",
    "usage": "545 (0x0221)"
  }
]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants