Nov 26th, 2016
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 2.10 KB | None | 0 0
  1. OnePlus 3/3T needs touch firmware(in /system/etc/firmware/tp, closed source) tuning for better latency.
  3. The latest 3.5.3 update on the 3T is still not good enough(tried it myself).
  5. Currently, the "move sensitivity" on the OnePlus 3 is set too big, which results in latency.
  6. If you touch the screen and move the finger around very little(like 3~5mm), it won't be registered as a scroll. This is because the "move sensitivity" is set too big. We are on a 5.5" screen. I think it'll be totally fine to reduce the threshold a bit.
  7. (If the threshold is set too small, a tap will be registered as a scroll. If it's set too big, a scroll will be registered as a tap and increase latency.)
  9. Smoothness is not equal to latency.
  10. OnePlus 3’s hardware is “smooth”. And by smooth, it means the GPU can consistently handle 60fps output.
  11. Latency is another thing, since latency is big, contents beneath the finger always follow your finger slowly(more noticeable when you scroll slowly).
  13. iPhone always had the lowest latency and iPhone switchers are already noticing the latency on the OnePlus 3.
  14. For me personally, I can tell the differences too on a Galaxy device, and even with the previous OnePlus 1.
  16. For more explanation, watch Microsoft’s video on YouTube :
  20. There are multiple sources that can add up to touch latency.
  21. 1. Hardware
  22. 2. Linux kernel
  23. 3. Linux kernel device drivers from OnePlus
  24. 4. Touch firmware (/system/etc/firmware/tp)
  25. 5. Android OS
  27. 1. OnePlus 3/3T uses touch panels from Synaptics, which has very good reputations around touch hardware, including laptop's trackpad and smartphone/tablet's touch panel. I highly doubt Synaptics would produce such a high latency product in 2016.
  28. 2. Linux kernel is already quite efficient and every Android devices are using it.
  29. Nothing wrong here.
  30. 3. The measured latency is 2~4ms, which is way below vsync event(16.67ms), so it’s fine for the drivers to have 2~4ms delay.
  31. 4. This is responsible for the “touch tuning”, which includes the threshold I’ve mentioned earlier.
  32. 5. Same reason as No 2.
  35. Thanks.
Add Comment
Please, Sign In to add comment