Display

While the OnePlus v uses essentially the same 5.5-inch AMOLED panel with a resolution of 1920 x 1080, the visitor has fabricated some tweaks to its display profile to improve its color performance. For some bizarre reason, OnePlus was calibrating the 3 to the outdated NTSC color infinite rather than sRGB, which led to horrible performance and weird colors. With the OnePlus 5, the company has returned to using the right sRGB gamut for Android, at least at times.

1080p on a 5.five-inch display is still a little disappointing considering 1440p displays at this size are the norm, while entry-level phones now offer 1080p. I get that 1080p screens are still dainty and precipitous, and do nowadays some functioning and battery life advantages, even so 1440p is just that little fleck better and something you'd expect from a flagship. 1440p delivers a far meliorate experience in mobile virtual reality too; peradventure the lower resolution brandish hither is stopping the OnePlus 5 from supporting Google Daydream.

The OnePlus five's AMOLED produces a maximum brightness of around 410 nits, which is good from an AMOLED and perfectly acceptable for outdoor usage. Of course, contrast ratio is space due to the screen beingness off when displaying blacks, and that leads to a display that simply pops when displaying vibrant imagery. Viewing angles are bully as well, though there is some color shift at acute angles.

1 of the things I immediately noticed near the OnePlus 5's display is the 'jelly consequence'; something that other users also overserved when the telephone launched. The basic issue here stems from how displays refresh: they practise so line by line, significant that within the refresh window, the lines at the top are updated before the lines at the bottom. This line-by-line updating cycles repeatedly.

Normally y'all don't notice this line-past-line updating, because either the brandish finishes its refresh (as in, it finishes refreshing the last line) well earlier the end of the refresh window – say, within 16.7ms for a threescore Hz console – or because the way you use the brandish hides the issue. A groovy way to hide the outcome on phones is to accept the part of the display that updates kickoff on the top, so that when you lot interact with the touchscreen, the screen updates kickoff in the part y'all're more than likely to be looking at: the top.

On the OnePlus 5 nosotros have a combination of the 2 problems, which produces the jelly effect. Firstly, the AMOLED screen here doesn't refresh lightning-fast, so there is a perceptible delay between when the showtime and concluding line updates. Secondly, OnePlus 5 oriented the screen 'upside-down', such that the line that updates final is at the tiptop, right in the most highly viewed department of the screen.

The stop result is that when scrolling, particularly changing the scrolling management, text and imagery appears to contract and expand in a jelly-like way. This is because during a change in scrolling direction, some parts of the display are updating ahead of others. As the superlative part of the OnePlus five's display is updating slightly later the bottom part, that's where the effect is most noticeable, as the filibuster from finger movement to update is the longest.

Looking at the display's color performance, OnePlus is going with the usual smartphone playbook here: the display is also common cold under its default calibration by approximately 1000K, and the color gamut is significantly wider than sRGB, leading to oversaturation. Colors aren't off here, which was an outcome with some by OnePlus phones, but they're definitely oversaturated.

For those that require color accurateness for whatsoever reason, the OnePlus 5 does have an sRGB display mode, which is reasonably accurate. The screen becomes a flake also warm, with an boilerplate color temperature of 6394K, however saturation and ColorChecker functioning is pulled in to under an average dE2000 value of 2.0, which is a potent result here.

The OnePlus v also comes with a DCI-P3 color mode, though as Android has no color management and therefore tin can't support the DCI-P3 colour space, the way is basically useless. Unless you accept DCI-P3 images incorrectly encoded in sRGB.