A
Project your Pixel phone screen
Pixel phones can connect over USB-C to a DisplayPort display or through an HDMI-to-USB-C path.
Source checked
Open source ↗
Verified XR compatibility
VITURE Beast + Pixel 10 Pro
CompatibleDirect connection
VITURE Beast connects directly to Pixel 10 Pro.
Evidence A
Confidence medium
Verified
Protocol-derived result. This connection is inferred from official host output specifications and official glasses input requirements. The exact device pair has not yet been explicitly confirmed by the manufacturer.
Recommended route
How to connect
Recommended connection route.
HostPixel 10 Pro
↓
XR glassesVITURE Beast
Capability matrix
What works
Connection and feature support are evaluated separately, so a direct connection can still have feature limitations.
Video
✓supported
Direct USB-C
✓supported
No adapter is required for the primary route.
Audio
✓supported
Native 3dof
✓supported
Supported by the glasses hardware.
Evidence chain
Why we say this
Compatibility conclusions are linked to explicit manufacturer or technical evidence rather than generated from prose alone.
A
How The Beast Stands Apart
VITURE Beast connects directly to Steam Deck and USB-C handhelds; Switch 2 works via VITURE Pro Mobile Dock.
Source checked
Open source ↗
A
VITURE Beast Dock Pack
VITURE Beast supports direct handheld connections and 120Hz; Pro Mobile Dock supports Switch and Switch 2.
Source checked
Open source ↗
Related compatibility
Check nearby combinations
Only launch-indexed results are linked here.
DirectVITURE BeastwithROG Ally Xhigh confidenceDirectVITURE BeastwithSteam Deck OLEDhigh confidenceAdapter requiredVITURE BeastwithNintendo Switch 2high confidenceDirectVITURE BeastwithiPhone 17 Promedium confidenceDirectVITURE BeastwithGalaxy S26 Ultramedium confidenceDirectVITURE BeastwithROG Xbox Ally Xmedium confidenceDirectXREAL One ProwithPixel 10 Promedium confidenceDirectXREAL 1SwithPixel 10 Promedium confidence
Methodology
Read methodology
Rules first, overrides when necessary
We calculate compatibility from device capabilities, connection protocols and verified accessory paths. Model-specific exceptions override protocol inference.