Fix: Chrome Mobile Double Typing or Dead Backspace Bug

It is incredibly frustrating when your browser decides to rewrite your search queries. If you are trying to type a simple search term and it ends up looking like "Moorttall Koombbatt", or if your backspace key suddenly refuses to delete a single character, you are not alone.

This text-input glitch is hitting mobile users hard, particularly those using native keyboards on Samsung devices, though it has popped up across various Android hardware.

Here is exactly what is causing the loop and how to fix it in a few simple steps.

The Problem: Ghost Characters and Broken Backspaces

When you tap into the Chrome address bar (omnibox) or a text field on a website, the keyboard begins to misbehave in two specific ways:

1. Double Typing: Every other letter or vowel gets mirrored instantly as you type.
2. Dead Backspace: Hitting the delete key either does absolutely nothing, or it randomly skips backward and deletes entire chunks of text you didn’t mean to touch.

Why It’s Happening

This isn’t a hardware failure or a broken touchscreen. It is a classic communication breakdown between Chrome’s predictive text rendering engine and your phone’s system keyboard framework.

During a recent update, a conflict emerged in how Chrome interprets “inline text composition”—the background data your keyboard sends to the app to predict your next word. Instead of cleanly registering a keystroke, Chrome gets stuck in an input loop, registering the character twice and losing track of where the cursor actually is, which effectively breaks the backspace key.

How to Fix It: Step-by-Step Troubleshooting

If you want to clear this glitch out of your browser, work your way through these three reliable fixes.

1. Clear and Reset Android System WebView: Takes 2 minutes.

Because Chrome on Android relies heavily on the system’s underlying rendering architecture, a glitch there ripples into the browser.

• Open the Google Play Store on your device.
• Search for Android System WebView.
• Tap Uninstall (this will roll it back to the factory version; it won’t delete the app).
• Once uninstalled, tap Update to reinstall the cleanest, most recent version.

2. Switch Keyboards or Disable Predictive Text: Instant workaround.

If you are using a native OEM keyboard (like the default Samsung Keyboard), the fastest way to break the loop is to change how it handles text predictions.

• Go to your phone’s Settings > General Management > Keyboard list and default.
• If you are on a Samsung keyboard, try temporarily switching to Gboard (Google’s keyboard), or vice versa.
• Alternatively, stay on your current keyboard, open its specific settings, and toggle Predictive Text or Auto-correction to Off.

3. Reset Experimental Chrome Flags: Advanced browser tweak.

If system fixes don’t do the trick, an underlying UI experiment in Chrome might be forcing the input loop.

• Open Chrome on your mobile device and type chrome://flags into the address bar.
• Tap the Reset all button at the top of the page to clear any conflicting experiments.
• If the issue persists, use the flag search bar to search for “text input” or “virtualization” to see if any active keyboard rendering flags can be toggled to Disabled.
• Tap Relaunch at the bottom of the screen to apply the changes.

A Quick Note on Future Patches: Because this is a verified input regression bug within the Chromium ecosystem, Google and major device manufacturers usually roll out secondary stability patches within days of discovery. Keeping your apps set to auto-update in the Play Store ensures the permanent fix lands on your device the moment it goes live.

Questions? Drop them in the comments field below and we will do our best to get you an update.