REPRODUCIBILITY (% or how often): Sometimes
BUILD ID = OS VERSION (Settings > About product):
HARDWARE (XA2, X10, X10 II, …): XA2
UI LANGUAGE: Irrelevant
REGRESSION: (compared to previous public release: Yes, No, ?): Yes
DESCRIPTION:
Sometimes when using an app and/or webpage that requests numeric input the keyboard will get stuck in this mode. It’s impossible to type text and even the numbers that are shown don’t work
PRECONDITIONS:
STEPS TO REPRODUCE:
Use an app/webpage requesting numeric input
Switch to text input
Notice you have a broken numeric-only keyboard
EXPECTED RESULT:
Text input should work
ACTUAL RESULT:
It doesn’t. Only numbers are shown and the numbers don’t even work.
ADDITIONAL INFORMATION:
(Please ALWAYS attach relevant data such as logs, screenshots, etc…)
Looks similar, but I think not the same. That bug seems to need to have the device used in landscape orientation and numeric input called for, but I have seen this bug with the phone in portrait the entire time. Also – assuming that this is the same bug I was about to report – the numeric keypad appears at the wrong time, rather than just not working when it appears at the right time. (Correct me if I misunderstood.)
I’m gonna return to this thread on my phone in just a little bit – I’ve got a couple screen captures to upload of what I’m seeing so @martijntje can confirm if I’m seeing the same bug.
That looks like what I see. I assume with “appearing at the wrong time” you mean that the numeric keyboard shows up when you expect a regular text keyboard? Or do you mean the keyboard is just popping up without input requested at all?
My workaround has been to install OKboard. It doesn’t work for my phone (screen size is not supported), but enabling it and then disabling it resets the keyboard.
This way I only have to wait ~5 seconds for the keyboard to become available again.
The same issue happened to me yesterday on my Xperia 10 II.
The only way to fix it was by restarting lipstick. If it happens again, I will try OKboard.
Although I was pretty sure that there was a way to restart the keyboard from the terminal, I didn’t know it off the top of my head, and my goto resource (googling it) was unavailable due to the problem
OTOH, this discussion is now bookmarked for when the problem recurs, so we’ll see – eventually.
I can definitely confirm this bug, it hit me about five times after updating to Verla. I run into it in portrait mode, simply with the stock note app and sms.
I can reproduce the error with the numpad now. It seems to happen consistently after PHillis app crashes. To narrow it down further for you guys I created a poll. Feel free to answer when the error appears for you:
appears after using PHillis app (regular close of the app)
appears after PHillis app crashed
appears after use of a different app (regular close of the app)
crashes. To narrow it down further for you guys I created a poll. Feel free to answer when the error appears for you: