A few months ago our app ran at closer to 30fps, and ATW would kick in and keep the headtracking smooth. After lots of optimizations, our app now runs at 50-60fps consistently. Not ideal, but ATW should be kicking in to smooth out the times when it's less than 60. Unfortunately, this is not the case -- we're getting a good deal of judder, especially on the Galaxy S6.
Tried creating an empty scene where you simply spawn cubes, and the same effect occurred. I even made it go below 30fps and ATW never kicked properly kicked in ATW is enabled according to adb, and I've definitely seen it work, for example during the loading screen.
What could cause timewarp to completely fail like this?