Key Mapper Accessibility service crashing

[bjones-eng]

Have you checked if an issue already exists for this bug?

• Nobody else has reported this bug before

Have you tried restarting your device?

• I have tried restarting my device and that did not help

What happened that you did not expect?

I am having an issue with the Key Mapper Accessibility service crashing as soon as I click into any input box.

I have installed Key Mapper 3.2.1 on a CHAINWAY C61 Android 13 scanner device with a 47 alpha numeric key pad.
Followed the installation/setup steps: Set App Battery Usage to Unrestricted. Turned Memory Storage Manager OFF. Turned Accessibility for KeyMapper ON. Set the keyboard language to English. Enabled KeyMapper Basic Input Method.

Attached is the KeyMapper log file.
key_mapper_log_20260225-182649.txt

Any help would be greatly appreciated.

What did you expect to happen?

No response

What would the developer need to do to reproduce the bug?

No response

App version

3.2.1 123

Android version

Android 13

Device model and manufacturer

CHAINWAY C61 Android 13 scanner with a physical full alph numeric keypad

Extra info

• My device is rooted

[jambl3r]

Cool device! And great log, thank you. We will investigate

[sds100]

This seems to be a crash in your phones fork of Android. I've never seen this before and there isn't much we can do. Does it crash if you do not use the key mapper keyboard?

[bjones-eng]

The device works fine when I disable the Key Mapper Basic Input Method. Both the Gboard on-screen keyboard and the alpha numeric keypad work as expected. I was thinking I must have some setting that is set or not set that is causing the problem. About a year ago, I was able to get the Key Mapper (v 3.2.1 132) working on a different device but same model (CHAINWAY C61 Android 13) barcode scanner.

[sds100]

Can you try upgrading to version 4.0.4 of Key Mapper. The crash is not related to key mapper code and it is definitely caused by something unique to the ROM your barcode scanner is using. I can't find anything in the AOSP source code to do with the issue.

So this crash is a side effect of some functionality that is supposed to work. We just need to narrow down what is causing it and work around it. Can you try using the Key Mapper GUI Keyboard and see if that works?

Your device is trying to modify the "cw_disable_soft_keyboard_auto" setting. Is there some functionality in your device to show and hide the soft keyboard automatically? "cw" looks suspiciously like CHAINWAY, hence why I'm pretty certain its not Key Mapper code at fault, usually I wouldn't be so dismissive 😄