The new Pixel Buds have plenty going for them: they're modern and sleek, they sound nice, and their Android integration is top-notch. But a quick glance at the Pixel Buds support forums shows tons of reports of connectivity problems. The good news is that Google is aware of these issues and a fix is on the way — eventually.
LineageOS is the most popular custom ROM out there, with dozens of supported devices and a few nice features over stock Android. The new Android 10-based LineageOS 17.1 was just released earlier this month, and now the project is bringing back support for two classic Google phones.
According to a recent set of benchmarks conducted by the folks at Android Authority, Google’s latest Pixels suffer a bit of a problem with file transfer speed over USB Type-C. Although Google bills the port as supporting USB 3.0 transfer speeds, something about the phone’s configuration results in nearly half the speed compared to other recent phones, like the OnePlus 7T Pro and Galaxy S10e.
Last year, after the Android 10 update first started rolling out for Pixel owners, there were a handful of reports that device sensors — things like the ambient light sensor for screen brightness, orientation sensor for auto-rotation, and Active Edge sensor — stopped working. A workaround was found for those with unlocked bootloaders, and many of those affected were part of the root and ROM crowd, but almost six months later, many phones are still affected, and those with Verizon-branded, locked devices are still simply out of luck.
We're officially on the road to Android 11, which means a whole round of developer preview builds are on the way to Pixel phones — as well as other non-Google phones likely to be announced at I/O in May that will go through their own beta stack. Unfortunately, for O.G. Pixel and Pixel XL owners, they won't be joining for the ride.
Dozens of Pixel owners are reporting that they can't authenticate into their devices because every time they put their PIN in, the phone loops them back to the lock screen. The issue, which was first reported on the Pixel Phone Help forum nearly a month ago, seems to be affecting Pixel XLs the most, though there have been mentions of other Pixel, Pixel 2, and Pixel 3 series devices. So far, product experts have been encouraging affected users to escalate the issue with Google directly or reset their device from recovery.
December's monthly security patches are here for Google's Pixel phones — or, at least, most of them. While the 2016 Pixels are getting what Google previously claimed would be their very last update after the two phones missed November's patches, the Pixel 4 and 4 XL are curiously late to the party, with no images posted just yet. Most confusingly, though, Google is apparently breaking out its Pixel-specific functional patch notes this month, which often describe useful or noteworthy feature changes and tweaks.
Google announced a slew of updates as part of the first Pixel feature drop yesterday, among them the ability to automatically screen calls from unknown numbers on the Pixel 4. It looks like this option won't stay limited to the latest phone in the lineup for a long time, as Business Insider cites Google saying that it'll "roll out to all Pixel devices with Android 10 over the coming weeks."