Pixel 5a deliveries have only started a few days ago, but overheating and touchscreen issues have become a common concern in many reviews and personal accounts of early users. Google has reportedly started investigating what causes these problems, and if they stem from software bugs, a fix should be available soon.
What’s wrong with Pixel 5a?
Google’s latest A-series Pixel phone shipped with the capability to capture videos in 4K at up to 60 frames per second. This video mode is one of the highest settings possible to capture on smartphones, so having it on a mid-range device like Pixel 5a is noteworthy.
However, the feature is currently being criticized as it appears to cause the phone to overheat. Several pre-launch reviews have reported that recording 4K/60FPS videos on Pixel 5a prompted a warning message or caused the Camera app to close.
Android Police tested the Pixel 5a by capturing a video at 4K/60FPS in 70 degrees Fahrenheit ambient temperature, but the recording stopped after five minutes following a heat warning message. In CNET’s experience, the device kept recording for more than six minutes before the camera stopped as well. Hot Hardware also said the device stopped recording after six minutes while using the highest setting in 68 degrees Fahrenheit ambient temperature.
This is not the first time that a newly launched Google phone is observed to be overheating in certain situations. Shortly after Pixel 5 units were shipped in October 2020, some users have reported that their phones are crashing or overheating when recording 4K/60FPS videos.
Google reportedly starts investigating Pixel 5a issues
Google has yet to publicly address the reported overheating issues on Pixel 5a. But 9To5Google reports that the company has started investigating it, and the problem is likely to be fixed by releasing an over-the-air patch with Camera app updates.
There are also reports that the Pixel 5a appears to exhibit a touchscreen bug as well. The same article notes that one workaround for this issue is to use the phone in safe mode, suggesting that it is also caused by a software bug. In this case, an OTA patch should be able to fix this as well. However, it is still unknown when Google is going to come up with these updates.