|
This works pretty well on my Libra 2. I noticed something a little odd about the keymap with an 8BitDo Micro.
I remapped the keys on the controller using 8BitDo Ultimate so it just works in Nickel without any additional setup there.
I primarily read in KOReader, but I do use the reboot into Nickel when I want to read a library book. In Nickel, I find I have to put the controller in pairing mode (fast blinking LED) no matter what, even though it hasn't been used between in KOReader or any other device, if I use NickelMenu to do it. I do this because that seems to be the only consistent way to pair the remote quickly without backing out to the home menu.
In KOReader, it seems like I also need to repair the device if I used it in Nickel. I'm okay with this, but my key bindings are “forgotten” every time. If I go into the keymapper (I have only been defining keys using the guided method), they are still there. I tried reloading the map file, but that doesn't seem to work. Refreshing it also didn't seem to work.
This happens consistently. I have no choice but to completely redefine the keymap, unless I am missing something. When I go to the diagnostics and click on the event mapper (the one thing that doesn't have a checkmark next to it), I get told there's no map file.
As long as I don't use it in Nickel, it works perfectly in KOReader otherwise. I am glad I don't have to even repair it like I do in Nickel. No issues with forgotten keybindings; they're remembered.
I'd prefer to not have to rebind the buttons on repair of the same device with the same buttons. I have not been changing button mappings on the controller itself.
Did I miss something?
|