simple-keyboard icon indicating copy to clipboard operation
simple-keyboard copied to clipboard

Keyboard not starting automatically at system boot, only after unlocking the screen

Open Danilo2103 opened this issue 9 months ago • 2 comments

I am experiencing an issue with Simple Keyboard where it does not start automatically during system boot. Instead, it only starts after the screen is unlocked. This prevents me from typing the password on the lock screen, as the virtual keyboard does not appear during boot. Once the device is unlocked, the keyboard works normally, even if the screen is locked again.

It's important to note that Simple Keyboard is set as the default keyboard, and there are no other keyboards installed on the device, not even the pre-installed ones.

This issue only occurs during the initial boot; after the device is unlocked, the keyboard functions properly.

Device information Android Version: 13 Device Model: Galaxy A03 Core (SM-A032M) Simple Keyboard Version: 5.25

Erros that may be useful: logcat_boot.txt logcat_errors.txt

If you need any further information or additional logs, please let me know. Any help will be welcome.

Danilo2103 avatar Mar 06 '25 15:03 Danilo2103

Does your phone ask for password before boot or after it boots only to unlock the screen?

rkkr avatar Mar 06 '25 15:03 rkkr

Also did you trim the logs? The first entry in logcat_boot is InputMethodBindingController: mSelectedMethodId is null! and that is final result saying that no keyboard could be loaded by OS. The logs before that are the important ones and might hint at what happened.

rkkr avatar Mar 06 '25 15:03 rkkr

Does your phone ask for password before boot or after it boots only to unlock the screen?

after it boots, only to unlock the screen

ghost avatar Mar 08 '25 20:03 ghost

Also did you trim the logs? The first entry in logcat_boot is InputMethodBindingController: mSelectedMethodId is null! and that is final result saying that no keyboard could be loaded by OS. The logs before that are the important ones and might hint at what happened.

oh sorry, wait a min, I'm gonna send the full logs

ghost avatar Mar 08 '25 20:03 ghost

@rkkr I had uninstalled the keyboard before because of this issue and reinstalled it again now to capture the logs. Now it's working 100% perfectly, 0 errors, it's starting normally during boot and everything else. I’m not sure what happened, but since it’s working I’ll continue using it instead of the other one. Anyways, tysm for your attention. Wishing you all the best 🙏

ghost avatar Mar 08 '25 20:03 ghost