Skip to content

MINIKeyboard v1.2.0

Choose a tag to compare

@hobbyworker hobbyworker released this 28 Oct 12:17
· 14 commits to main since this release
288187a

MINIKeyboard v1.2.0

Install: flatpak install --user https://mini-kb.hobbyworker.me/updates/linux/me.hobbyworker.MINIKeyboard.flatpakref,
or open that link in your software center. The bundles below are for installing without that link or keeping this
version — pick the one for your PC, MINIKeyboard-1.2.0-x86_64.flatpak (Intel and AMD) or
MINIKeyboard-1.2.0-aarch64.flatpak (ARM), and run flatpak install --user <file>. Updating: either way, new
versions come through your software center or flatpak update. Your settings stay. The udev rule that
How to Allow… shows now covers 1189:8851 too — if you have that keyboard, install the rule again.

New

  • Several keyboards — with more than one supported keyboard plugged in, a button beside the connection status
    chooses the one to open. The one you choose opens first next time.
  • Saves are read back — a keyboard whose settings can be read is read again right after saving, to check it holds
    what was written. If anything differs, the app says so and keeps those changes unsaved.
  • A keyboard with firmware the app hasn't seen before gets a notice that it hasn't been tested yet, and Keyboard
    Information marks it too.

Improved

  • Keyboards with firmware type 11, such as the 514C:8850 (12 keys, 2 knobs, a colour for each key), are read and
    saved correctly. With 1.1.0, reading that keyboard failed, and saving left the key empty.
  • The app follows the newest version of the vendor's app (2025-06): firmware types from 10 up use the newer format,
    keyboards with older firmware are read as soon as they connect too, and 1189:8851 is looked for as well.
  • When a read stops partway, what came is shown, and the app says some keys or knobs couldn't be read.
  • Switching to another keyboard or the simulator with unsaved changes asks first.
  • Unplugging or switching keyboards while reading or saving no longer mixes one keyboard's values into another's, and
    a keyboard unplugged and plugged straight back in is noticed.
  • Mouse actions are saved the way the vendor's app saves them.
  • The LED page hides Clear and Clear Layer, which clear what keys and knobs do, not their lights.

Fixed

  • Shape… with no keyboard connected opened an empty dialog you couldn't do anything with.