ehm01
Lurker
I saw this problem in many other phones and Android versions here on this forum, where people complain about the keyboard being unresponsive, stop working at all.
for those who have the prediction ON, the phone still showing prediction words, but nothing goes to the application.
I tough that could be my MultLink keyboard at the first, so I disable it and went back to LG Keyboard.
Same issue.
I could not find a 'step-by-step' to crash. and like most of us here, the only solution was a reset.
Them today I decided to just wait.
The keyboard stopped working, I click on the 'Switch Keyboard' option and then just wait.
I wait for about 4 minutes and the Switch option opens. I select the MultiLink Kayboard (as I was using LG) and then it immediately went back to the application and start working.
So, my humble deduction here is that there are some LAG on my phone that prevent the keyboard to work and there is nothing to do with the phone it self.
It happens here in the forum in version 2 to 4, so it's not a version issue neither.
Many people reporting, with different keyboards installed, so it's not keyboard related neither.
Could be an Operation System bug?
Any other experiences on waiting until it goes back to work by it-self?
for those who have the prediction ON, the phone still showing prediction words, but nothing goes to the application.
I tough that could be my MultLink keyboard at the first, so I disable it and went back to LG Keyboard.
Same issue.
I could not find a 'step-by-step' to crash. and like most of us here, the only solution was a reset.
Them today I decided to just wait.
The keyboard stopped working, I click on the 'Switch Keyboard' option and then just wait.
I wait for about 4 minutes and the Switch option opens. I select the MultiLink Kayboard (as I was using LG) and then it immediately went back to the application and start working.
So, my humble deduction here is that there are some LAG on my phone that prevent the keyboard to work and there is nothing to do with the phone it self.
It happens here in the forum in version 2 to 4, so it's not a version issue neither.
Many people reporting, with different keyboards installed, so it's not keyboard related neither.
Could be an Operation System bug?
Any other experiences on waiting until it goes back to work by it-self?