BlackBerry Key2 + LineageOS 22.2 : Pastiera key mapping issue (M key / period)

[tiomsy]

Hi everyone,

I recently installed LineageOS 22.2 (Android 15) on my BlackBerry Key2 (BBF100-4, Chinese variant) and installed Pastiera to handle the physical keyboard.

I'm facing an issue with the key mapping: the M key is not working properly : it always produces a comma regardless of the configuration (both in AZERTY and QWERTY layouts). As a result, the period (.) is also inaccessible since it's mapped to ALT+M on the physical keyboard.

Also, a less critical issue: the digits 1 and 7 are swapped compared to the physical Key2 keyboard layout.

I found the online layout editor at https://pastierakeyedit.vercel.app/ but I'm not sure how to use it correctly for the Key2 keyboard. Specifically, I don't understand what each column corresponds to : for example, which column maps to the Shift layer and which one maps to the Alt layer?

Could anyone help with either:

• A ready-to-use JSON layout file for the BlackBerry Key2 (QWERTY or AZERTY)
• Or a step-by-step explanation of how to properly configure the Key2 layout using the online editor

Thanks a lot for your help!

[pzauner]

Thanks for the detailed report, and sorry for the trouble.

You’re right that this does not look like a normal layout-choice issue.
It may be the case that physical keys may be reported with unexpected Android keycodes, which could cause symptoms like M -> , and Alt+M not producing .

To make this easier to diagnose, we added an in-app key event view (no ADB needed) that shows:

• Action
• KeyCode
• ScanCode
• Unicode

Could you please open the app home screen on the newest nightly build (should be online 31.03.2026) and press these keys one by one, then share what values you see?

M
N
Alt+M
Alt+N
1
7

This will let us build a proper Key2-specific fix for your device variant.

Also added a central keyboard layout mode switch:

• Automatic layout mapping (locale/subtype-based default)
• Manual override (force one layout globally)

So if auto-detection is wrong on your ROM, you can explicitly choose the layout you want.

[pzauner]

With the new nightly build there is an updated screen for debugging, please share the according screenshots for all special keys like SYM, ALT etc as well as the misbehaving ones from your post.

[tiomsy]

Thank you for your quick response and for adding the diagnostic tool, that's really helpful!

Here are the results from the key event view on the latest nightly build. Device: BlackBerry Key2 BBF100-4 (Chinese variant), LineageOS 22.2 / Android 15.

Individual key results (in-app diagnostic):

M :
KEYCODE_55
Action : KEY_UP
KeyCode : 55
ScanCode : 50
Unicode : 44 (,)

N :
KEYCODE_N
Action : KEY_UP
KeyCode : 42
ScanCode : 49
Unicode : 110 (n)

ALT :
KEYCODE_57
Action : KEY_UP
KeyCode : 57
Scancode : 56
Unicode : 0 (N/D)

SHIFT :
KEYCODE_59
Action : KEY_UP
KeyCode : 59
Scancode : 42
Unicode : 0 (N/D)

SYM :
KEYCODE_SYM
Action : KEY_UP
KeyCode : 63
Scancode : 100
Unicode : 0 (N/D)

Speed Key (9-dot key) :
KEYCODE_119
Action : KEY_UP
KeyCode : 119
Scancode : 110
Unicode : 0 (N/D)

1 (Alt+W) :
KEYCODE_Z
Action : KEY_UP
KeyCode : 54
ScanCode : 17
Unicode : 122 (z)

7 (Alt+Z) :
KEYCODE_W
Action : KEY_UP
KeyCode : 51
ScanCode : 44
Unicode : 119 (w)

Note: when testing key combinations such as Alt+Z or Alt+M, the diagnostic screen registers each key separately : first the ALT keycode, then the M keycode. No combined result is shown.

For your information, the sequential key events via ADB (adb shell getevent -l /dev/input/event2):

Alt+M:

EV_MSC       MSC_SCAN             0000001e
EV_KEY       KEY_LEFTALT          DOWN
EV_SYN       SYN_REPORT           00000000
EV_MSC       MSC_SCAN             00000038
EV_KEY       KEY_M                DOWN
EV_SYN       SYN_REPORT           00000000
EV_MSC       MSC_SCAN             00000038
EV_KEY       KEY_M                UP
EV_SYN       SYN_REPORT           00000000
EV_MSC       MSC_SCAN             0000001e
EV_KEY       KEY_LEFTALT          UP
EV_SYN       SYN_REPORT           00000000

Alt+N:

EV_MSC       MSC_SCAN             0000001e
EV_KEY       KEY_LEFTALT          DOWN
EV_SYN       SYN_REPORT           00000000
EV_MSC       MSC_SCAN             00000030
EV_KEY       KEY_N                DOWN
EV_SYN       SYN_REPORT           00000000
EV_MSC       MSC_SCAN             0000001e
EV_KEY       KEY_LEFTALT          UP
EV_SYN       SYN_REPORT           00000000
EV_MSC       MSC_SCAN             00000030
EV_KEY       KEY_N                UP
EV_SYN       SYN_REPORT           00000000

Alt+W (expected: 1):

EV_MSC       MSC_SCAN             0000001e
EV_KEY       KEY_LEFTALT          DOWN
EV_SYN       SYN_REPORT           00000000
EV_MSC       MSC_SCAN             0000001f
EV_KEY       KEY_W                DOWN
EV_SYN       SYN_REPORT           00000000
EV_MSC       MSC_SCAN             0000001f
EV_KEY       KEY_W                UP
EV_SYN       SYN_REPORT           00000000
EV_MSC       MSC_SCAN             0000001e
EV_KEY       KEY_LEFTALT          UP
EV_SYN       SYN_REPORT           00000000

Alt+Z (expected: 7):

EV_MSC       MSC_SCAN             0000001e
EV_KEY       KEY_LEFTALT          DOWN
EV_SYN       SYN_REPORT           00000000
EV_MSC       MSC_SCAN             00000020
EV_KEY       KEY_Z                DOWN
EV_SYN       SYN_REPORT           00000000
EV_MSC       MSC_SCAN             00000020
EV_KEY       KEY_Z                UP
EV_SYN       SYN_REPORT           00000000
EV_MSC       MSC_SCAN             0000001e
EV_KEY       KEY_LEFTALT          UP
EV_SYN       SYN_REPORT           00000000

At the kernel level, the hardware correctly reports KEY_LEFTALT and the expected key names (KEY_M, KEY_W, KEY_Z, etc.). The issue therefore appears to be in how Android maps these keycodes on this specific device variant (BBF100-4).

Hope this helps build the BBF100-4-specific fix. Happy to run any additional tests if needed!

[pzauner]

Implemented a fix that should address this on BBF100-4 by adding an explicit Physical Keyboard Profile selector (Auto / BlackBerry Key2 / BlackBerry Q25 / Unihertz Titan 2) in Keyboard Layout Settings.

So if auto-detection is ambiguous, selecting BlackBerry Key2 manually will force the Key2 behavior path.

This should be fixed now, but we still need manual on-device verification from you on the latest nightly before we can confidently close the issue. If you can, please confirm whether Key2 profile selection now gives the expected behavior end-to-end.

I already tested this with the Titan 2 and the Key 2 mapping in software.

[tiomsy]

Confirmed working perfectly on BBF100-4! All keys are now producing the correct characters, the ALT layer works as expected, and I no longer need Key Mapper as a workaround.

The manual BlackBerry Key2 profile selection in Keyboard Layout Settings did the trick. End-to-end behavior is exactly what it should be.

Thank you so much for the fast turnaround and for taking the time to properly support this device variant. This is a great fix and will definitely help other BBF100-4 users running custom ROMs.