Not a recommendation, but a question. I have a bunch of mechs
and not one will process the (Intel) startup sequence keys.
No starttup Cmd/Option/Control key combos are recognized.
This is either wired or wireless. As an aside the (wireless)
Apple Magic keyboard works as expected.
SO does the Matias, Keychron, etc., work?
How about QMK firmware?
Perhaps your keyboards require some driver to use, which won’t be loaded at startup? My ancient (and mechanical) keyboard doesn’t have a Windows/Command key (I map the caps lock key) but will do all the Intel startup sequences that don’t require holding down the Command key. When I need to do that, I attach an Apple keyboard temporarily.
I sometimes have this issue too. It seems that some(all?) keyboards reset upon boot. My guess is that if, say, option is held while rebooting, the keyboard resets, and the key(s) that are down don’t have their scancodes relayed to the computer.
So I repeatedly press the key combination, and always have an Apple keyboard around if things don’t work out.
Not sure if that is the case since I no longer have an Intel Mac to try.
In my QMK findings, I found that some Apple feature only work with their own keyboards, namely the fn key that’s now a core part of iPad’s multitasking keyboard shortcuts.
The solution is to make QMK identify the Keyboard as one from Apple by setting its vendor # to Apple’s code.
As a web developer, I find it hilarious how often the solution to a technology problem involves instructing your software to lie about what exactly it is.
Hey @jsamlarose, I’ve got a pair of nice!nanos 2 (and batteries, sockets and many shenanigans) and now am looking forward to build my first wireless sweep.
However, I’m still missing on a power switch and a reset button. As I was looking for a way to transport my keyboard around without using the power switch, I found two ways: a transport layer to be exited by a combo toggle and a patch that would enable the &suspend behavior.
Since I saw a few comments of yours on GitHub regarding this patch, I wanted to ask how well are you dealing with this feature on your Corne.
Just wanted to check out before deciding to solder the batteries directly to the nanos.
Hi! YMMV may vary with that “soft power off” patch— I’ve had a fair few cases where my board has switched itself back on in transit. Haven’t figured out how that’s happening yet.
For peace of mind I’m back to the first of the two options you found: a transport layer (all &none keys) toggled via a combo keypress (the four corners of my keyboard, as you can see from the keymap I posted, so very unlikely to be unintentionally invoked when packed away).
This has proven to be the most reliable way to pack the keyboard away without having to worry about random keypresses. There’ll still be some drain if the keys are pressed, but shouldn’t be anything more than regular usage. This will also be easier for you if you really want to get something up and running without having to install dedicated reset switches.
I’ve found the &suspend keys useful for disconnecting my keyboard without having to turn off bluetooth, but that might be another story…
A bit late to this, sorry, but it’s also possible to map Apple’s Fn key to a suitable key on a mechanical keyboard which doesn’t have a physical Fn key at all and which doesn’t use QMK — like the first version Kinesis Advantage.
It’s a two stage process:
On the Kinesis, remap a key from the number pad layer and remap it to a modifier key on the standard layer. I remap ‘Insert’ from number pad layer to Ctrl on the top right of the right thumb cluster.[*] So, you know have a top level ‘insert’ key, which is completely useless, of course.
So now you need to use Karabiner Elements to tell the Mac to treat the Insert key as a Fn key. This is a simple remapping in KE’s “Simple Modifications” tab.
I’ve not come across any problems at all with this method.
[*] I customise the thumb clusters heavily as they’re poorly designed in the standard configuration – I have 3 other control keys, so this one isn’t missed. Why they waste such import thumb space on unnecessary keys like Page Up/Down and Home/End is a mystery…
I tried holding Option on my Keychron Q10, and it was not recognized at boot of my iMac Pro.
I haven’t tried spoofing the Apple keyboard ID or anything.
I always have an Apple keyboard lying around, so not a problem for me.
I don’t use that Keyboad with the iPad, so that’s not been a problem for me, fortunately.
But I definitely wouldn’t remap CapsLock to Fn, because it’s needed for Control, which is used hundreds of times a day. Even better if you dual-map it – I have CapsLock as a dual Control/Escape key, (and Return as dual Control/Return).
On the iPad (Magic Keyboard), you can only have CapsLock as Control, but that’s still much better than the default.
FWIW, with my keyboard and iPad, I’ve mapped the Caps Lock key to Globe/Fn (via iPadOS settings), and my right shift key is a Caps Word key when double-tapped (via my keyboard firmware)…
Now I feel the urge to recommend a split keyboard to anyone who cares about ergonomics and comfort. It’s really great to keep an open chest on the desk and that alone far surpasses the learning curve hasle.
If you don’t want to go as minimal nor ortholinear as I have, there are some keyboards that keep the traditional staggered layout but in a split format, such as the Dygma Raise.
Progress report. I finally bought a white Keychron Q1 pro. The standard english ANSI version, not the barebones ISO version. It was cheaper that way, and less of a hassle.