Repository navigation
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem: Fn+arrow works in BLE HID mode but sends nothing over I2C, breaking navigation on hosts like Meshtastic that expect original CardKB bytes (0xB4-0xB7).
Fix: In I2C mode, emit the same CardKB navigation codes when Fn+D/X/Z/C are pressed.
Enter also required 0x0D instead of the keymap's 0x0A
Testing: Flash firmware, confirm i2cget -y 1 0x5f returns 0xb5 while holding Fn+D in I2C mode.