iFixit teardown points to possible causes of iPhone Duo screen and hinge damage

The Verge ·

iFixit’s teardown of Apple’s iPhone Duo offers possible explanations for reports of cracked screens and noisy hinges, while revealing how the foldable’s display is designed to disguise its crease. The phone scored 5 out of 10 for repairability, the highest mark iFixit has given a foldable so far.

The display’s matte nano-texture scatters reflections, and angled oval subpixels may further reduce the crease’s visibility. The outer texture layer can be replaced without changing the OLED, but repairing the screen itself is expected to be difficult and costly. iFixit found some dust in the hinge and ports, but less than in two rival foldables; it suspects a complex hinge part or a cable near the battery may concentrate pressure and contribute to the reported damage. Apple had not responded to a request for comment.

In short

  • iFixit gives the iPhone Duo a foldable-best repairability score of 5/10.
  • Display texture and angled subpixels may help hide the crease.
  • A hinge component or nearby cable may be linked to reported damage.

Explained simply

Foldable phones use a flexible inner screen that bends around a hinge, so the screen and hinge have to withstand repeated opening and closing. A crease can form where the display folds, and dust or pressure on delicate parts may affect how the phone works.

Apple makes the iPhone Duo, while iFixit takes devices apart to examine their design and how readily they can be repaired. Its repairability score compares how difficult repairs are; a higher score does not mean a device is less likely to break.

Screen and hinge repairs can affect the cost and practicality of owning a foldable phone. The design choices that make a crease less noticeable may also shape how the screen can be repaired.

Art Culture Gadgets Technology

Read the full article at the source →

Originally published by The Verge as “iFixit’s look inside the iPhone Duo may explain those broken screens and hinges”.

Log in to join the discussion