Google’s latest flagship handset, the Pixel 5 has been due a potentially showstopping problem, and it looks like we may have found it in the form of a possible design flaw. Some users of the XDA Forums are amongst those who have complained that the glass display panel on their device doesn’t sit flush with the casing. The number of reports is growing steadily as more and more units reach their new owners, suggesting that the problem isn’t isolated—though we might add that it certainly doesn’t apply to every single handset sold.
Various photographs of phones sporting the unsightly gap suggest that it isn’t isolated to one specific point, but rather than there’s just not enough room to snap the two halves together, suggesting a millimetres wide mismatch between parts. It doesn’t seem to be limited to one color variant, nor does it seem to be a flaw that develops over time—most people have spotted it straight out of the box.
Image credits: XDA Senior Member superleeds27
The biggest concern here isn’t the functionality of the phone—they all seem to work perfectly—but it does bring into question the potential for ingress of dust and, more importantly, water. The Pixel 5 has been certified as IP68, which should mean that almost nothing gets in or out. Clearly, that’s not going to be true if there’s a whacking great hole in the casing.
We all know that most flagship phones have at least one boo-boo to overcome—but so do the manufacturers and the fact that this issue has been allowed as far as the end consumer leaves Google sporting a potentially very red face. Given the lukewarm reception and sales for the Pixel 4, the company needed for this launch to go flawlessly.
We’ve asked Google for comment on the matter and will update this article once we have a statement.
Thanks for the tip, XDA Recognized Contributor TokedUp! Featured image credits: XDA Junior Member Sylabo
The post Some Pixel 5 owners are reporting a gap between the display and the body appeared first on xda-developers.
from xda-developers https://ift.tt/3dKMMCB
via IFTTT
Aucun commentaire:
Enregistrer un commentaire