Description:
When I type random gibberish (e.g., "asdfghjkl" or "qwertyu"), the keyboard automatically tries to interpret these as real words and inserts spaces between them, creating meaningless sentence-like structures. This happens even when "Auto-correction" is disabled in the settings.
Root Cause Analysis (User-side observation):
This seems to be caused by the Android system's built-in dictionary and the AOSP "phantom space" mechanism. When the prediction engine receives unrecognizable input, it forces a match with the closest system dictionary word and automatically appends a space after it.
Suggested Fix / Feature Requests:
To resolve this fundamentally, I would like to request the following improvements:
- Isolate from System Dictionaries: Add an option to completely disconnect the keyboard from Android's system-level dictionaries. The app should rely solely on its own local/user dictionary (or none at all) to prevent external interference.
- Control "Phantom Space": Add a dedicated toggle to disable "Auto-insert space after selecting a suggestion." This would override the AOSP default behavior and prevent the engine from forcibly adding spaces to meaningless inputs.
Thank you for your hard work on this keyboard. I hope these suggestions help in debugging the issue.
Description:
When I type random gibberish (e.g., "asdfghjkl" or "qwertyu"), the keyboard automatically tries to interpret these as real words and inserts spaces between them, creating meaningless sentence-like structures. This happens even when "Auto-correction" is disabled in the settings.
Root Cause Analysis (User-side observation):
This seems to be caused by the Android system's built-in dictionary and the AOSP "phantom space" mechanism. When the prediction engine receives unrecognizable input, it forces a match with the closest system dictionary word and automatically appends a space after it.
Suggested Fix / Feature Requests:
To resolve this fundamentally, I would like to request the following improvements:
Thank you for your hard work on this keyboard. I hope these suggestions help in debugging the issue.