Karabiner-elements: Microsoft Natural Keybaord 4000 F13-15

[djcmike]

After having all my other issues fixed, which is nice, I stumpled over that I no longer can en or decrease light on my iMac using F14 and F15. Any ideas?

[talha131]

@djcmike try adding following rules

"f14" : "vk_consumer_brightness_down",
"f15" : "vk_consumer_brightness_up"

[djcmike]

Hi again :)

No that didn't work either :/

eventType:KeyDown code:0x6b name:F14 flags:Fn misc:characters:
eventType:KeyUp code:0x6b name:F14 flags:Fn misc:characters:
eventType:KeyDown code:0x71 name:F15 flags:Fn misc:characters:
eventType:KeyUp code:0x71 name:F15 flags:Fn misc:characters:

[talha131]

Are you trying Fn+F14 to decrease brightness?

[djcmike]

No, I don't have an FN key on the keyboard.

[talha131]

Just to be sure, configuration needs "fn_function_keys" object to redefine function keys.

{
    "profiles": [
        {
            "name": "Default profile",
            "selected": true,
            "simple_modifications": {
                "non_us_backslash": "grave_accent_and_tilde",
                "grave_accent_and_tilde" : "non_us_backslash"
            },
            "fn_function_keys": {
                "f14" : "vk_consumer_brightness_down",
                "f15" : "vk_consumer_brightness_up"
            }
        }
    ]
}

[djcmike]

No that didn't work either :/

[talha131]

Last attempt

From https://github.com/tekezo/Karabiner-Elements/issues/68#issuecomment-248698906

you need to define all of the fn_function_keys and you also need to give it a moment or so after restarting karabiner-elements to actually take effect.

You can copy rules for other fn keys from here, add all of them to your configuration, and relaunch karabiner-elements.

[djcmike]

No no luck, I am afraid :(

[tluck]

This maps works for my ps2 keyboard:

"fn_function_keys": {
"f1": "vk_consumer_brightness_down",
"f2": "vk_consumer_brightness_up",
"f3": "vk_mission_control",
"f4": "vk_launchpad",
"f5": "vk_consumer_illumination_down",
"f6": "vk_consumer_illumination_up",
"f7": "vk_consumer_previous",
"f8": "vk_consumer_play",
"f9": "vk_consumer_next",
"f10": "mute",
"f11": "volume_down",
"f12": "volume_up"
}

[djcmike]

"f1": "vk_consumer_brightness_down",
"f2": "vk_consumer_brightness_up",
This works for me as well, but not when using "f14" and "f15" Would have been nice to move things over there, since I use my fn keys a lot in terminal... Now comes the question, can you set it to CTRL+F1 becomes F1? Oh... Waiting for #16 Oki. Thanks for your help :) But it would be nice to investigate why F13-15 does not work. But keep up the most excellent work 👍

[xpert13]

@djcmike I had the same problem with F13 ("Print Screen" key on my keyboard). Then I tried to use "print_screen": "vk_consumer_brightness_up" rule and it works like a charm.

Try to use next rules:

"simple_modifications": {
                "scroll_lock" : "vk_consumer_brightness_down",
                "pause" : "vk_consumer_brightness_up"
            }

[CorcoranEd]

I was having trouble with F13-15 but using xpert13's advice above can set those keys now using print_screen, scroll_lock and pause keys.

[incandescentman]

What fixed this problem for me is going to Devices > Modify events from this device, and disabling a extra keyboard that was listed there and checked but that is not the one I'm using.

[decadent]

Just adding a data point: I use the same keyboard, and scroll lock and pause adjust the brightness for me out of the box, regardless of whether function keys without Fn are enabled or disabled. So the issue seems to affect users differently. I'm on El Capitan 10.11.6.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.