The OnePlus 3 and OnePlus 3T are amongst the most powerful smartphones available out there. The OnePlus 3 was released back in June with the Snapdragon 820 SoC, 6GB of RAM and a 16-megapixel rear-facing camera. The OnePlus 3T landed earlier this month, and it’s essentially identical to the OnePlus 3 on the outside, but it comes with a more powerful SoC, larger battery and a more capable front-facing camera. The OnePlus 3T is essentially an upgrade over the OnePlus 3, and it is replacing the OnePlus 3 in OnePlus’ lineup for this year.
The OnePlus 3 has been available for sale for months now, and the OnePlus 3T rolled out quite recently in the US, Europe and Hong Kong. Initial impressions when it comes to the OnePlus 3T have been really good actually, but it seems like both devices have issues with touch latency, at least according to the latest report. Now, some of you might now consider these to be issues, it all depends on your usage of the OnePlus 3 / OnePlus 3T... in any case, read on. What is touch latency? Well, it's a delay between the response on the touchscreen to your input. Most modern smartphones these days, especially flagship smartphones, have latency at around 50ms, well, the OnePlus 3 and OnePlus 3T seem to have a touch delay of 93ms. Quite a few users brought up this issue in the OnePlus Forums, XDA Forums and Reddit.
Now, a user named Arter97 decided to comment on this issue at OnePlus’ forums, he basically wants users to differentiate touch latency delay and smoothness, as the two are not the same. Chances are you won’t notice any screen latency issues while using the device, well, until you start typing really fast, that is when you might notice some difference / delay. Do keep in mind that the OnePlus 3 and OnePlus 3T are not bad devices because of it, not at all, but you may notice these screen latency issues if you’ve been using another flagship device recently and do tend to type really fast. It is also worth mentioning that OnePlus can fix these issues through a software update, as this is not a hardware issue, luckily.