Gboard users across a range of Android devices, including Google Pixel owners, are reporting a bizarre and persistent issue. After disconnecting from Android Auto, the keyboard keys mysteriously shrink to an inconveniently tiny size. This frustrating bug has been around for months, defying even the latest Android Auto and Gboard updates.

Despite the widespread user complaints (1,2,3,4,5,6,7,8,9,10), Google has yet to officially acknowledge the issue. However, affected individuals have devised a few workarounds to mitigate the problem.

Gboard-tiny-keys-after-disconnecting-Android-Auto

One common solution involves typical troubleshooting measures such as clearing the Gboard app’s data and cache or force closing and reopening the application. Additionally, some users have discovered that rotating the phone and keyboard to landscape mode, then returning to portrait mode, effectively resolves the sizing anomaly. In another workaround, users have found success by enabling the voice keyboard feature and then reverting to the standard keyboard settings. This method reportedly restores the keyboard keys to their normal size within Gboard.

As noted earlier, the issue extends beyond Google Pixel devices, affecting users on various Android devices from manufacturers like Samsung and others. Despite differences in hardware, the common denominator appears to be the occurrence of the issue immediately after disconnecting from Android Auto.

Hopefully, Google will address this widespread problem soon, providing a proper fix for this strange keyboard-shrinking issue. In the meantime, those frustrated by tiny Gboard keys after disconnecting from Android Auto can resort to the above user-discovered workarounds.

Unfortunately, this isn’t the only long-standing issue affecting Gboard users. For months now, Wear OS 4 users are reporting that Gboard is still broken in some apps on Galaxy Watch devices. Hopefully, Google will address both issues once and for all in the near future.

Hillary Keverenge
2446 Posts

Tech has been my playground for over a decade. While the Android journey began early, it truly took flight with the revolutionary Lollipop update. Since then, it's been a parade of Android devices (with a sprinkle of iOS), culminating in a mostly happy marriage with Google's smart home ecosystem. Expect insightful articles and explorations of the ever-evolving world of Android and Google products coupled with occasional rants on the Nest smart home ecosystem.

Next article View Article

[U: It's finally here] Fitbit app still missing dark mode support, but you can enable it on Android using this workaround

Update 21/08/25 - 5:55 pm (IST): After making users wait a long time, Google has finally introduced native dark mode support on the Fitbit app. This new eye...
Aug 21, 2025 4 Min Read