The wev does detect the keys from the laptop keyboard, but the evtest doesn't.

[aljustiet]

When I run the evtest and f4-f12 keys it doesn't detect it, but when I run the wev and test it receive keys.
Laptop: Thinkpad T14s gen 3 amd.

[aljustiet]

Here's the demostration.

[jtroo]

The video is challenging for me to interpret, please do a text writeup of the logs frov evtest/wev

[aljustiet]

Which key stands for micmute in tthe defsrc?

[jtroo]

There might not be one yet.

[jtroo]

Based on your mention of micmut seems like you have f-keys combined with media keys with the fn key? Have you tried what happens with fn-lock enabled, perhaps fn+esc?

The laptop keyboard might also be presenting as two different keyboards for some reason which might be why evtest doesn't see the inputs.

[aljustiet]

Do you know which keys should I include in the defsrc to be able to map them in the deflayer?

[aljustiet]

Is this an issue of the evtest?

[jtroo]

Can you test evtest on the other devices being listed. As mentioned before I think your keyboard is presenting as multiple devices to the kernel.

[aljustiet]

On the Keychron K2 V2 keyboard, it detects the f1-f3, f7-12.

[aljustiet]

Can you test evtest on the other devices being listed. As mentioned before I think your keyboard is presenting as multiple devices to the kernel.

[jtroo]

I see two different K2 devices. Does one have a subset of the F-keys and the other has the rest? I also see Thinkpad extra buttons, what does that device send?

…

On Sat, Jul 20, 2024 at 11:59 AM aljustiet ***@***.***> wrote: Can you test evtest on the other devices being listed. As mentioned before I think your keyboard is presenting as multiple devices to the kernel. image.png (view on web) <https://github.com/user-attachments/assets/3c58623e-dd59-481b-a337-b1f16c45357b> — Reply to this email directly, view it on GitHub <#1084 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABSTVGGLWXPO5LVS7SUUO4TZNKXRBAVCNFSM6AAAAABIMMXZTKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTAMJQGM3TKMY> . You are receiving this because you commented.Message ID: ***@***.***>

[aljustiet]

@jtroo

[aljustiet]

How can I fix this error in my fork?

❯ cargo build --release
   Compiling kanata-keyberon v0.171.1 (/home/aljustiet/Documents/git/kanata/keyberon)
error[E0081]: discriminant value `224` assigned more than once
   --> keyberon/src/key_code.rs:16:1
    |
16  | pub enum KeyCode {
    | ^^^^^^^^^^^^^^^^
17  |     /// The "no" key, a placeholder to express nothing.
18  |     No = 0x00,
    |     -- discriminant for `K0xDF` incremented from this startpoint (`No` + 224 variants later => `K0xDF` = 224)
...
287 |     K0xDF,
    |     ----- `224` assigned here
...
291 |     LCtrl = 0xE0,
    |             ---- `224` assigned here

For more information about this error, try `rustc --explain E0081`.
error: could not compile `kanata-keyberon` (lib) due to 1 previous error

[jtroo]

The error says that you can't have duplicate values of 224 in the KeyCode enum.

What are you trying to achieve? This discussion has had a few topic changes now, so it's not clear to me what you're trying to do currently.

As something to throw out there you might want arbitrary-code?

[aljustiet]

I was able to include the keys in defsrc but was not able to map them.

[jtroo]

Simply delete the line: K0xAA, and it should work.