This story was originally published and last updated .
Google's Pixel lineup might offer some of the best phones out there when it comes to software, but they've always struggled with one hardware issue or another over the years. From the Pixel 2 XL display to the Pixel 3's long list of problems, the reliability of Pixel devices isn't among their best selling points. Now it looks like the back panels of some Pixel 4 XL units are peeling off, but Google has promised to exchange devices still under warranty, refuting claims bloated batteries might be at fault.
Starting last evening, Google's Nest cameras started suffering widespread issues with both live feeds and recorded video history. Although the issue resolved for many overnight, some are experiencing problems accessing video recordings and, in some cases, live feeds as well. Google currently claims a "small portion of cameras" are still having trouble, and it's working on a fix.
Google rolled out its augmented reality "Live View" navigation for Google Maps last year, but it looks like not everyone has been able to enjoy it. For some Pixel 4 owners, the feature doesn't appear, leaving many with Google's own flagship unable to use one of Google Maps' coolest features.
Over the last three days, there have been widespread reports of Google Home smart speakers becoming entirely unresponsive. Most of those affected appear to be in the Google Home preview program, which allows the adventurous to test early firmware releases. While a factory reset has fixed the issue for some, for others, it reportedly makes things worse, rendering the device no longer discoverable.
For some, the snazzy new face unlock system on Google's latest Pixel 4 is a whole lot less convenient than it should be. Reports over the last couple of months indicate that the face unlock process is simply failing for a handful of Pixel 4 and 4 XLs, even after re-enrolling their faces or resetting the phone. Thankfully, the issue doesn't sound too widespread.
Following a recent update to the Zenfone 6, some owners have been reporting system stability problems including frequent crashes/restarts, network connectivity problems, and bootloops. According to a recent statement issued by an ASUS representative on the company's ZenTalk forums (spotted by PiunikaWeb), the issue is a hardware fault in affected devices which is triggered by the update.
Being able to run Linux applications on Chromebooks isn't just useful for developers, it can help plug what little remaining app or feature gap prevents you from using the platform. Unfortunately for those that do use it, some folks have been experiencing a problem where their devices spontaneously reboot during sleep if Linux containers are running, and it isn't clear if it will be fixed in time for the next Chrome OS release.
We were recently tipped off that some OnePlus 7 Pro owners are running into a significant but thankfully not widespread issue: Their phones appear to randomly turn off or shut down, potentially while they're even being used. The only means of resuscitation in such cases is manually rebooting into fastboot by holding down a combination of hardware buttons. Thankfully, OnePlus is both aware of the issue and planning a fix.
This seems to be the week of Bluetooth bugs. In what could be a related issue, we've received reports that notifications and notification sounds are being doubled (or even tripled) on Android devices which are paired with other Bluetooth devices. Some are also reporting that media and ringer volume are being inexplicably paired together, resulting in do not disturb, silent, and vibrate mode settings being effectively ignored when media channel volume is above silent.
If you are on Google Fi and you're unable to place a call right now, you aren't alone. Widespread reports indicate that Fi subscribers are unable to place or receive calls via their cellular connection, though SMS, data, and Wi-Fi calling services appear to be unaffected. We can independently confirm that calls placed over Fi are failing.