Phone Keyboard Test for Autocorrect, Lag and Wrong Letters

It is usually autocorrect or predictive text silently replacing what you typed, a learned-word problem in the keyboard dictionary, or — on some iOS versions — a known typing bug. This test shows whether the wrong letters come from autocorrect (it logs every substitution) or from the keys themselves, then gives you the matching fix steps.

Restart the iPhone, update to the latest iOS, turn off Auto-Correction and Predictive in Settings → General → Keyboard, and if it persists reset the keyboard dictionary in Settings → General → Transfer or Reset iPhone → Reset → Reset Keyboard Dictionary. The typing-rhythm meter here helps you confirm whether the lag is gone.

Clear the Gboard cache (Settings → Apps → Gboard → Storage → Clear cache), turn off Text correction options in the Gboard settings, update Gboard from the Play Store, and as a last step clear its storage to reset learned words. Then re-run this test to check the result.

Yes. The output-verification test asks the field not to autocorrect so you measure your own typing, while the autocorrect detector deliberately lets the keyboard correct you so it can show what it changed. Comparing the two tells you whether the keyboard or autocorrect is the problem.

Yes. Connect a keyboard to your phone, tablet or computer and switch to the physical-keyboard test — each real key lights up when pressed, with a live key/code readout. For deep ghosting, rollover (NKRO) and chatter diagnostics, use our dedicated keyboard test.

On a phone, the on-screen keyboard does not send a normal key event for each letter — Android reports a placeholder code 229 and iOS often sends no key event at all. So instead of lighting up keys, this test verifies the text your keyboard actually produces, which is the honest, reliable signal a browser can read.