Google Pixel 5a has reportedly been canceled as global chip shortages persist

Google has reportedly canceled the Pixel 5a (codenamed Barbet), with sources placing the blame on the global chip shortage. The device was rumored to make its debut at Google’s I/O developer conference, which is scheduled to kick off in May.

The news was broken by Jon Prosser and later confirmed by Android Central.

“‘Barbet’ (Pixel 5A) has been canceled,” Prosser Tweeted on Friday. “I’m told it’s due to the chip shortage, and as of this morning, it’s not moving forward.”

The Pixel 5a was expected to be similar to last year’s Pixel 5, but with lower specs and a more affordable price tag. Google has followed a similar release pattern for the last couple of generations, introducing the Pixel 4a and Pixel 4a 5G toward the end of last year. With the Pixel 5a allegedly canceled, Google is reportedly turning its attention to the Pixel 4a and 4a 5G.

If true, it’s a surprising development considering how much we know about the Pixel 5a. We’ve seen leaked renders of the device and have also learned some of its specs, which may have included a 6.2-inch OLED display, hole-punch design, and a size that closely matches the Pixel 4a.

The global chip shortage has been a major concern for smartphone manufacturers over the last several months. Recently, Xiaomi warned that the shortage could result in increased phone prices, while Samsung’s Galaxy Note is reportedly facing delays. It’s also said to be partly to blame for the painfully slow production of Sony’s next-generation PlayStation 5.

While the Pixel 5a has reportedly been canceled, Google is still expected to launch new products this year. The search giant is expected to unveil more affordable wireless earbuds called Pixel Buds A. Meanwhile, it was recently reported Google is developing its own chip that will debut with the Pixel 6 this fall.

The post Google Pixel 5a has reportedly been canceled as global chip shortages persist appeared first on xda-developers.

from xda-developers https://ift.tt/39TXxSw
via IFTTT