we are developing an app using Open3D Engine on the Quest 3, and somewhere around the new year the Vulkan query pool timestamps started reporting back durations of only a few microseconds for our render passes. Going back to older versions of the engine and our app also did not fix this, even though we had stable timestamps on those before. We also tested on other hardware such as Snapdragon 740-based phones and PC. These all report back the timestamps correctly, so the Quest 3 seems to be the only remaining variable.
Could it be that a driver update in the past couple of months has changed something that either exposed an underlying issue, or has broken the timestamps?
If I could be provided with a way to roll back to an older version of the driver, I'll be able to narrow it down further.
