09-22-2020, 01:13 PM
I got a Samsung S8 to test this today. The problem last time this happened was a piece of the Oculus SDK was left in the build that caused that behavior just on Samsungs. Our fix to that is still in place but we'll figure out how it got back in.