OnePlus States the OnePlus 5’s Jelly Scrolling Effect is Not a Defect

OnePlus States the OnePlus 5’s Jelly Scrolling Effect is Not a Defect

We may earn a commission for purchases made using our links.

Yesterday, we published an article about a peculiar issue some OnePlus 5 owners were reportedly having: a jelly-like scrolling effect. We informed you of the various theories that were circulating around the web as to what may have been causing this issue, and we notified OnePlus regarding the issue so they could take a look into it. Now, the company has issued a statement to us regarding the jelly scrolling effect that reads:

The OnePlus 5 uses the same level of high-quality components as all OnePlus devices, including the AMOLED display. We’ve received feedback from a small number of users saying that at times they notice a subtle visual effect when scrolling. This is natural and there’s no variance in screens between devices.

Thus, the company is claiming that this scrolling behavior is not at all a symptom of a defective product. OnePlus would like to stress that this scrolling effect people are seeing is “not a QA or manufacturing defect” , and thus people should not expect an OTA update to resolve what they may be seeing, nor contact customer service for a replacement device.

In a teardown of the OnePlus 5 by YouTuber JerryRigEverything, we can see that the components of the OnePlus 5 are positioned on the bottom of the device.

Given this placement, it makes sense that the scrolling effect people are seeing is “natural” if it’s indeed caused by the placement of these modules. This does not mean that the display is mounted “upside-down” as some have suggested (meaning, this isn’t a QA issue), but rather this is because of the way the company chose to allocate the components, presumably because of the component crunch at the top caused by their choice of a dual-camera setup (though this is speculation).

Update: XDA’s Response to OnePlus’s Statement

We have responded to OnePlus’s statement on the matter in a follow-up article published here.