Is it just me or are GetTouch positions actually incorrect in Unity 5.2!?
Apparently correct touch position now requires
Input.GetTouch(0).position - new Vector2(0,Screen.height) ??
Close all other apps on your computer and then try it. I’ve come to find that the weirdest things interfere with the Unity remote, from Photo Booth to just a podcast playing in my web browser.
@ina this actually fixed the problem for me too. I have no idea why though. It’s fairly frustrating.