Keymapping issue on Blackberry Devices

[benknam]

Emulator version: 1.7.0-open

Game version: Multi

Game resolution: Multi

Device: Blackberry Classic (Q20)

Android version: Android 4.3 (VM via BBOS 10)

Description of the issue: The key mapping action keep telling "KEYCODE_UNKNOWN", then failed mapping the blackberry key to the game.

[woesss]

Are the buttons really not assigned or just the button names are not displayed? Was it before or appeared in a new version?

[benknam]

Are the buttons really not assigned or just the button names are not displayed? Was it before or appeared in a new version?

Yeah the buttons were not assigned to the game. If I add a new profile, Once I assign the key to replace the default one, the next tap of this key will show "KEYCODE_UNKNOWN", I'm sure this was cause by the Blackberry keyboard.

the default keycode before assign the key.

the failed one.

[woesss]

We do not understand each other. The name of the buttons may not be determined, but they will be assigned and they will work in the game. Have you checked them in the game?
If the buttons do not work in the game, test the keyboard with this (or a similar) application: https://play.google.com/store/apps/details?id=aws.apps.keyeventdisplay and show us the output.

[benknam]

We do not understand each other. The name of the buttons may not be determined, but they will be assigned and they will work in the game. Have you checked them in the game?

Sorry for my bad explanation :( . Yeah, I checked in the game too, it's not working.

Otherwise as I test again, once the second key was assigned, the previous assigned-key will be cleared (being empty). I guess the keyboard just only send a same code to the loader, once we assign the next key, the loader will think about this is the same code from the keyboard, so the last one will be cleared.

Attached a log file if its helping. log.txt

[JoseskVolpe]

I suggest to test the assigned keys on a key tester j2me application too. As woesss said, the name could not be obtained but the keycode was asigned. So, sometimes it's the game's problem and not the emulator, because the game is receiving a input but it's not recognizing that emulated keycode, and to solve this, you can try setting the device from Nokia to Siemens, Motorola or any other device listed.

You can check if this MIDlet returns a keycode, and send here if so. If it's not returning anything after you press the assigned key, or it returns a different one from the listed device, so it's a problem with the emulator.

https://ufile.io/apues0r3

[benknam]

We do not understand each other. The name of the buttons may not be determined, but they will be assigned and they will work in the game. Have you checked them in the game? If the buttons do not work in the game, test the keyboard with this (or a similar) application: https://play.google.com/store/apps/details?id=aws.apps.keyeventdisplay and show us the output.

Great idea, here's the result：

(Taping: q w e r t y u I o p)

Capture from the device

keyevent_2021-07-19-170536+0800.txt The saved log file.

[woesss]

Strange, the keyboard sends normal events.
Perhaps the BB incorrectly transfers them to the dialogue - an additional test is needed.

Run this test app: keys-test.zip (APK in ZIP, github doesn't allow adding APKs), press the buttons, then open the dialog via the options menu and press the same buttons again. Compare and show the result.

[benknam]

Strange, the keyboard sends normal events.
Perhaps the BB incorrectly transfers them to the dialogue - an additional test is needed.

Run this test app: keys-test.zip (APK in ZIP, github doesn't allow adding APKs), press the buttons, then open the dialog via the options menu and press the same buttons again. Compare and show the result.

Thanks woesss, this could be useful.

I'm keeping testing during this couple hours, I found that actually the blackberry device keyboard is working at all, but once I selected NK/SE layout (or any others except Custom), the BB keyboard should be "alt-lock" so it could directly input "number" but not "letter", then it will work as well as the NOKIA or SonyErrison device. So I modified a couple values of "Keymapping" line in the Config.json, which was located in the app config folder, then seems some keys are working directly without alt-lock. Maybe I got the wrong keycode or something, not all the key was setting as what I want, but I will test again with the key-test app comparation results.

[benknam]

Strange, the keyboard sends normal events. Perhaps the BB incorrectly transfers them to the dialogue - an additional test is needed.

Run this test app: keys-test.zip (APK in ZIP, github doesn't allow adding APKs), press the buttons, then open the dialog via the options menu and press the same buttons again. Compare and show the result.

Good day woesss, here's result capture from keys-test:

Upper two lines showing normally while I press "q", down two showing "KEYCODE_UNKNOWN" while I press "q" in dialog window.

open the dialog from menu, and showing "KEYCODE_UNKNOWN"

What does it mean?

[woesss]

As I suspected, the problem is in the dialogue. Another test is dialogue only: test-keys2.zip If this test fails, we need to somehow get rid of the dialogue. In the meantime, you can edit the mapping in text mode, a list of all android keycodes can be viewed here: https://github.com/aosp-mirror/platform_frameworks_base/blob/master/core/java/android/view/KeyEvent.java#L94

[benknam]

As I suspected, the problem is in the dialogue. Another test is dialogue only: test-keys2.zip If this test fails, we need to somehow get rid of the dialogue. In the meantime, you can edit the mapping in text mode, a list of all android keycodes can be viewed here: https://github.com/aosp-mirror/platform_frameworks_base/blob/master/core/java/android/view/KeyEvent.java#L94

Thanks woesss, here's the result of test-key2, yes it was failed to detect the input ( pressed "q")

[woesss]

KeyTest3.zip Another try.

By the way, are the "scan" values different for different buttons?

[benknam]

KeyTest3.zip Another try.

By the way, are the "scan" values different for different buttons?

Thanks woesss, I'm back onboard,

key-test1 showing no "scan" value. and yes, in key-test2 & key-test3 app, it's showing in different value for different button, but this just happens while the dialogue box showing, after press "OK" of the dialogue box, the "scan" value keeps showing 0 at all. Here's the capture below:

This is the capture with taping "q w e r t y u I o p" within a dialogue box.

This is the capture with taping "q w e r t y u I o p" after pressing the "OK" of the dialogue box.

[woesss]

It is clear that nothing is clear!
I haven't found a way to match scan codes to keys.
Thus, the only way to solve this problem is to change the GUI of the mapping settings window to do without the dialog.

[woesss]

I came up with a fix, a test build of my mod can be downloaded here: https://install.appcenter.ms/users/j2me.forever/apps/jl-mod/distribution_groups/testers

[benknam]

I came up with a fix, a test build of my mod can be downloaded here: https://install.appcenter.ms/users/j2me.forever/apps/jl-mod/distribution_groups/testers

Wooooow that's reallllllllly cooooooooool, woesss!! You did a really great job! This one works so perfectly on my Blackberry Q20 !!! Very perfect !!! I will tell my BB group members as they have another type of keyboard device, so let's test if this one works, too!

[alemanto]

It actually detects key presses and kind of works, but continuess press not working (holding down the button). You have to tap key so character moves in games.