The Pixel 3 and 3 XL come with arguably the best cameras on a smartphone and amazing software to match. However, it can’t be all perfect, and the Pixel 3 and 3 XL suffer from software issues that affect the user experience by a whole lot.
The camera doesn’t save pictures sometimes
According to multiple reports from Reddit and comments on the Google Product Forums, the Pixel 3 and 3 XL fail to save photos that have just been taken. Some users say that it occurs when they leave the camera app or lock the phone right after taking a picture.
Google has promised that it will roll out a software update “in the coming weeks.”
Killing background apps aggressively
The Pixel 3 and 3 XL struggle to keep apps open in the background. According to multiple reports from Twitter, Reddit, and even MKBHD’s review, taking a photo is sometimes enough to kill Spotify if it’s playing music in the background. Cycling through 3 to 4 apps can force apps out of memory.
Is it because of Google’s decision to go with 4GB of RAM? Or is it because of memory management issues? While we can’t say for sure, Google has responded and made the following statement:
“We’re rolling out a software update in the coming weeks to keep background apps from being prematurely closed in certain situations.”
Video recordings have poor audio
YouTuber SuperSaf TV made a video that demonstrated the difference between the audio quality of the Pixel 3/3XL and the iPhone XS. It sounds exceptionally tinny and distant. Last year, even the Pixel 2 and 2 XL had audio recording issues which Google fixed in an update.
However, Google has acknowledged the issue and made a statement that it’s perfectly normal:
“We made several advances in the audio recording capabilities of Pixel 3, including enabling stereo recording in landscape mode. When recording outdoors, our tuning is specifically designed to reduce background noise like wind and road noise and overly loud sounds and optimize for audible speech. To achieve this, we selectively de-emphasize some frequencies, which minimizes disruptive noises and optimizes the resulting audio. We do extensive user testing of our products to ensure they are tuned for real world usage, and we’re always looking at additional tuning opportunities based on user feedback.”
Later on, Google acknowledged earlier that it would consider tweaking the Pixel 3’s microphone audio profile based on feedback, but so far there hasn’t been any official change.
One of the front-facing speakers is louder than the other
The front-facing speakers on the Pixel 3 XL’s have completely different volumes. The issue is prevalent on the Pixel 3 too, but the Pixel 3 XL stands out. Since there would be a difference in space between the top and bottom bezel due to the notch, the difference in volume can be explained by differently sized drivers.
Google acknowledged this issue too, and like the poor audio quality, they say it’s by design:
“Hi all, This is by design. We specially designed speakers that allow for louder sound (40% louder than last year) and better low frequency response. We use new amplifier technology with advanced speaker protection algorithms to push these speakers harder and really get every last bit of performance out of them. We also worked closely with the expert tuning of a Grammy-award winning music producer to enhance the audio in a way that plays to the strengths of the hardware system.”
Buzzing/distorted speakers on the Pixel 3 XL
A bunch of Twitter and Reddit users have reported that their speakers produce a static, buzzing, or distorted sound, even at low volumes. The issues seem to be confined to just the larger Pixel 3 XL and not the Pixel 3.
You know I thought I heard something similar at very low volume yesterday, but then I couldn't reproduce it on other videos. Does it happen to you with any sound or only some?
— Artem Russakovskii (@ArtemR) October 19, 2018
Redditor u/qtpa2tnh tested it further and suggested that low to mid-range frequencies are especially problematic (between 20-500Hz). Some users have RMA’d their devices while others have said the issue goes away on its own. This issue seems to be the same as last year’s Pixel 2, and we’re still waiting on an official response from Google on this issue.
Via: Android Police (1, 2, 3, 4, 5), 9to5Google
Note: This article was written in part by Karan Shah.
