The new Google Pixel 4a 5G is a force of miniature technology: a long time ago on the JerryRigEverything channel we saw how super resistant it is. However, even though it is an engineering masterpiece, it is not without software problems. In the last period many users are complaining touch problems and in particular find themselves unable to use the navigation keys on their device. This all happened after an update that arrived last month. Let's see the details.
Still problems with the touch on Google Pixel 4a 5G: no navigation keys, the bottom of the smartphone is unusable after a month
The bug in question is that hits the sensor for touch does not allow users to use the lower part of the device in any way. Clearly this problem is much more evident when using i digital navigation keys (the ones we activate when we don't want to use gestures). Through a video posted by an XDA member let's see concretely how the Pixel 4a 5G behaves. Specifically, the Horizontal swipes work but taps don't.
However, the reports also speak of the reverse problem: the touches are the only ones that work while for the swipes there is nothing to do. According to the XDA member the problem would be due to some form of palm rejection or prevention of accidental touch, an active mechanism precisely to prevent accidental touches from pressing any key or activating some function. But in this case, if confirmed, the December update definitely amplified the positive effect of this feature by taking it to the extreme.
We tried to eliminate tempered glass to protect the screen but unfortunately this has had no effect. One user even got to replace (under warranty) your Google Pixel 4a 5G but the new unit also presented the same kind of problem.
It was Christmas when the problem first surfaced and the moderators of the official Google forum said it would be fixed soon. Now, neither with the December update, nor with the January update, the bug has been eliminated. Hopefully, the company has done something with the February OTA.
On offer on Amazon
Sources | Google official forum, Google Issue Tracker
Through | Android Police
