Comment by 🐡 Breebee

Re: "[#109] Keyboard often not working on Android"

In: s/Lagrange-Issues

I can confirm this bug persists on other operating systems as well. I'm using a google pixel with stock android and for me it seems to be a 50/50 on whether or not the text input field just does nothing. While switching keyboards does (temporarily) fix it, I've just been closing the input window and clicking the link over and over until it lets me type. I typically use the stock keyboard but have tried with others

🐡 Breebee [it/its]

2025-08-14 · 9 months ago

5 Later Comments ↓

🌆 skyjake [mod...] · 2025-08-14 at 12:18:

@Breebee Which model of Pixel do you use, and which version of Android? At least I could try the same combo in the emulator.

🐡 Breebee [...] · 2025-08-14 at 12:59:

pixel 6a with android 16

☯️ johano · 2025-09-22 at 04:49:

I have this issue sometimes as well, using the latest version of LineageOS and primarily using the stock AOSP keyboard... usually don't have the issue using AnySoftKeyboard oddly enough

🌆 skyjake [mod...] · Mar 15 at 06:43:

This may be fixed or at least improved in Beta 46/47. Let me know if it still keeps happening.

☕️ dce [OP] · Mar 15 at 18:06:

Can't say I've noticed it in a while. Not sure if anyone else has experienced the glitch recently.

Original Post

🌒 s/Lagrange-Issues

☕️ dce:

The issue is exactly what the title says. If I tap on the address bar or try to provide input to a page (e.g. the Kennedy search engine), often the keyboard will not actually enter any text, and I have to switch to the default keyboard and back again, or to Florisboard and back again (depending on which I'm using). This issue is present with all keyboards I have tried, including the built-in AOSP keyboard. However, copy and paste in the context menu has no issues. I am running Graphene OS...

💬 13 comments · 2025-05-29 · 11 months ago · #android #needs-testing