Weird touch sensitivity behaviour on screens with a resolution higher than 1080p.

This affects both the Galaxy S6, the Nexus 6, and assumedly any other phone that has a screen with a resolution higher than 1080p. Both the Galaxy S6 and the Nexus 6 have screens with resolutions of 1440p (2560*1440). When moving your finger on the screen in order to change look direction, the scrolling seems very choppy. Upon closer examination, it appears that the camera only moves when you've moved your finger across a certain number of pixels. Thus, it appears that there is a sort of "touch grid" of some sort. Optimally this touch grid would contain cells that are 1 pixel wide, which means that when the user touches the screen, the camera would follow their every movement very accurately. I'd guess that these grid cells are about 10 pixels wide or something, as when moving your finger across it there seems to be a bit of room you have to move your finger before the camera shifts. This creates a very annoying effect which upon first glance without examining what is actually happening could be mistaken for frame rate lag (which is not the case).

This affects both the Galaxy S6, the Nexus 6, and assumedly any other phone that has a screen with a resolution higher than 1080p. Both the Galaxy S6 and the Nexus 6 have screens with resolutions of 1440p (2560*1440). When moving your finger on the screen in order to change look direction, the scrolling seems very choppy. Upon closer examination, it appears that the camera only moves when you've moved your finger across a certain number of pixels. Thus, it appears that there is a sort of "touch grid" of some sort. Optimally this touch grid would contain cells that are 1 pixel wide, which means that when the user touches the screen, the camera would follow their every movement very accurately. I'd guess that these grid cells are about 5 pixels wide or something, as when moving your finger across it there seems to be a bit of room you have to move your finger before the camera shifts. This creates a very annoying effect which upon first glance without examining what is actually happening could be mistaken for frame rate lag (which is not the case).