Regarding game development on Android 17, Google Play Games' Level Up guidelines have set out a requirement of confirming updated GPU drivers while positioning Vulkan as the primary API. The 2026 list of baseline devices includes the Tensor G5-powered Pixel 10 Pro XL and Pixel 10 Pro Fold. However, Android Authority, which retested an actual Pixel 10 Pro XL unit, reports that while issues in typical games have decreased, there are still cases on emulators where it falls short of the Pixel 9 Pro XL.
The Pixel 10's issue isn't something that can be settled by comparing gaming performance with a single benchmark. How Android uses Vulkan and ANGLE, and how far GPU vendors' drivers have implemented that pathway, causes results to diverge app by app even on the same device. Putting Google's official guidelines alongside the actual measurements after Pixel 10's updates together, when looking at a device's gaming performance, the completeness of the initial drivers becomes something to check in addition to peak performance.
Android 17's guidelines explicitly state GPU driver requirements
Google Play Games' Level Up guidelines presuppose updated GPU drivers with FEATURE_VULKAN_DEQP_LEVEL of 20240301 or higher for games supporting Android 17 and later. On top of that, for games using Unity 2021 or later, or Unreal Engine 4.25 or later, it specifies that Vulkan should be the primary graphics API. Cases where the portion using OpenGL ES—such as ads and WebView—stays under 10% are listed as an exception. This is a requirement of that guideline, and does not guarantee performance for all games on Android.
Among the conditions Google is looking at is GPU driver support, in addition to the Android version number. Android Developers explains that Vulkan's API version isn't determined by the OS alone, but is also affected by GPU driver support. Even when upgrading to Android 17, each GPU's implementation doesn't necessarily mature to the same level. The reason Google encourages profiling games per GPU is that performance and bottlenecks vary greatly by GPU vendor and generation.
Starting with Android 17, games can also specify in manifest metadata that ANGLE be prioritized as the GLES driver. ANGLE is a mechanism that implements OpenGL ES on top of Vulkan. However, use of this pathway isn't guaranteed, and if it's unavailable, it falls back to the GPU vendor's GLES driver. The fact that API options have increased doesn't mean that older OpenGL ES-based games or emulators will automatically stabilize.
The reason the Pixel 10 Pro XL and Pixel 10 Pro Fold were included among the baseline devices is that Google treats these as subjects for evaluating gaming experience. This isn't a certification that they are high-performance gaming devices. Rather, it would be more accurate to view it as the devices having become ones on which developers can check behavior under the conditions of Vulkan, ANGLE, and updated drivers.
Pixel 10 has improved to "playable," but emulators remain a weak point
During the early days after the Pixel 10 Pro XL's launch, which Android Authority documented, there was driver instability that the outlet assessed as accompanying the PowerVR transition. Running COD Mobile's Battle Royale at high graphics settings reportedly showed flickering attributed to anti-aliasing. In a comparison running F-Zero GX on Dolphin, while the Pixel 9 Pro XL held nearly a fixed 60fps, the Pixel 10 Pro XL fluctuated between 40-60fps, sometimes dropping below 30fps.
The gaps between APIs were also large. The outlet reported that on the early Pixel 10 Pro XL, F-Zero GX with OpenGL anti-aliasing enabled crashed on launch, and on Vulkan, textures were missing. It says the Pixel 9 Pro XL didn't have these same issues. This is based on actual device testing with specific devices, games, and settings, and isn't a conclusion applicable to all Pixel 10 models or all games. Even so, it's an example where differences in driver implementation persist even after OS updates.
Updates have been addressed. According to Android Authority, driver updates included in the late-2025 QPR beta improved performance and resolved some issues, and a March 2026 update was also confirmed to fix graphics problems. Google also noted in its March Pixel update an optimization to reduce OpenCL driver overhead and raise benchmark scores. However, Google hasn't gone so far as to state that this optimization resolves all issues with OpenGL, Vulkan, Dolphin, and NetherSX2.
In a retest with Android 17 and the July 2026 security patch applied, Android Authority says graphics glitches in major titles largely disappeared, and typical games ran smoothly if settings were lowered. On the other hand, the six-year-old Genshin Impact couldn't maintain 60fps at maximum settings, with results closer to the mid-40fps range. Since measured values depend on in-game settings and measurement conditions, they can't be substituted for an overall device performance figure.
What hasn't disappeared is the gap on emulators. The outlet stated that while Dolphin's Vulkan performance on Android 17 improved significantly from launch, it still falls short of the Pixel 9 Pro XL's Mali GPU and can't consistently deliver a stable 60fps. Issues also remain with Dolphin's OpenGL pathway, and it reported that NetherSX2's Need for Speed: Most Wanted didn't reach a playable frame rate on either OpenGL or Vulkan. At least in this retest, gaps between APIs remained even after updating the OS and patches.
For Pixel 11, what matters is the initial drivers rather than the GPU name
Google's emphasis in explaining Tensor G5 was on TSMC's 3nm process, up to 60% faster TPU compared to before, an average 34% faster CPU, and on-device AI and camera. Concrete figures about GPU gaming performance were absent from this explanation. The Pixel 10 was announced on August 20, 2025, and Android 17's release and rollout to supported Pixels came on June 16, 2026 — roughly 10 months of updates after the announcement have improved the gaming environment.
This history can't simply be projected onto the next device. Android Authority introduced a rumor that the unannounced Pixel 11's Tensor G6 will use a different PowerVR-based GPU, and wrote that its biggest concern isn't peak performance but the rebuilding of the driver stack that comes with a new GPU architecture. Google has not announced the Pixel 11's Tensor G6 or its GPU, and this is neither a confirmed specification nor a performance forecast.
What should be checked is how Google explains the unannounced Pixel 11's GPU and its launch-day drivers, and how the Vulkan and ANGLE-priority pathway can be verified across individual games and emulators. The Pixel 10's retest showed that updates can widen the range of what's playable. At the same time, gaps in initial drivers can still affect the assessment of a device generation, particularly for older OpenGL ES-based games and emulators.