Virtual Desktop wired mode for lower latency.


How to Set Up Wired Virtual Desktop (USB Tether Method)​

TL;DR: You can run Virtual Desktop over USB using gnirehtet. Expect 150-200 Mbps max with H.264+ before latency becomes an issue. May need to restart PC between sessions.

Background​

Tested this recently after seeing it mentioned here. It's not a magic bullet but might be useful for people with WiFi issues. The setup uses USB tethering via gnirehtet to create a wired connection to your Quest.

Performance Reality Check:

  • Max bitrate: ~150-200 Mbps with H.264+ before latency gets bad
  • Network latency won't read zero (this is normal)
  • Some users report needing PC restart between sessions
  • Your mileage may vary

What You Need​

  • Quest headset + USB cable
  • Windows PC with admin access
  • About 10 minutes for setup

Setup Steps​

This uses the gnirehtet project by Genymobile. Full technical details available on their GitHub: https://github.com/Genymobile/gnirehtet

  1. Install Java Download from Oracle: https://www.oracle.com/java/technologies/downloads/#jdk22-windows
  2. Download Tools
  1. Connect & Run
  2. Plug Quest into PC via USB
  3. Make sure developer mode is on
  4. Double-click gnirehtet-run.cmd in your gnirehtet folder
  5. Allow the connection request in your headset (first time only)
  6. Keep that command window open
  7. Use Virtual Desktop
  8. Turn off Quest WiFi
  9. Open Virtual Desktop normally
  10. PC will say "not on same network" - ignore this, it still works
  11. Connect as usual

Settings That Worked For Me​

  • Started with H.264+ codec
  • 150 Mbps bitrate was the sweet spot
  • Going above 200 Mbps = latency problems

Gotchas​

  • That command prompt needs to stay open the whole time
  • Don't expect zero latency readings
  • If latency gets bad, try restarting your PC before next session
  • Haven't tested other codecs yet
  • Make sure USB debugging is allowed and Java installed correctly if gnirehtet won't run

Is It Worth It?​

Very much worth it! Even with the bitrate ceiling, the stability and consistency you get from a wired connection can be a game changer. If you're having WiFi issues or want to experiment, it's fairly easy to set up.

Anyone else tried this? Curious about experiences with other codecs or higher bitrates.
 

How to Set Up Wired Virtual Desktop (USB Tether Method)​

TL;DR: You can run Virtual Desktop over USB using gnirehtet. Expect 150-200 Mbps max with H.264+ before latency becomes an issue. May need to restart PC between sessions.

Background​

Tested this recently after seeing it mentioned here. It's not a magic bullet but might be useful for people with WiFi issues. The setup uses USB tethering via gnirehtet to create a wired connection to your Quest.

Performance Reality Check:

  • Max bitrate: ~150-200 Mbps with H.264+ before latency gets bad
  • Network latency won't read zero (this is normal)
  • Some users report needing PC restart between sessions
  • Your mileage may vary

What You Need​

  • Quest headset + USB cable
  • Windows PC with admin access
  • About 10 minutes for setup

Setup Steps​

This uses the gnirehtet project by Genymobile. Full technical details available on their GitHub: https://github.com/Genymobile/gnirehtet

  1. Install Java Download from Oracle: https://www.oracle.com/java/technologies/downloads/#jdk22-windows
  2. Download Tools
  1. Connect & Run
  2. Plug Quest into PC via USB
  3. Make sure developer mode is on
  4. Double-click gnirehtet-run.cmd in your gnirehtet folder
  5. Allow the connection request in your headset (first time only)
  6. Keep that command window open
  7. Use Virtual Desktop
  8. Turn off Quest WiFi
  9. Open Virtual Desktop normally
  10. PC will say "not on same network" - ignore this, it still works
  11. Connect as usual

Settings That Worked For Me​

  • Started with H.264+ codec
  • 150 Mbps bitrate was the sweet spot
  • Going above 200 Mbps = latency problems

Gotchas​

  • That command prompt needs to stay open the whole time
  • Don't expect zero latency readings
  • If latency gets bad, try restarting your PC before next session
  • Haven't tested other codecs yet
  • Make sure USB debugging is allowed and Java installed correctly if gnirehtet won't run

Is It Worth It?​

Very much worth it! Even with the bitrate ceiling, the stability and consistency you get from a wired connection can be a game changer. If you're having WiFi issues or want to experiment, it's fairly easy to set up.

Anyone else tried this? Curious about experiences with other codecs or higher bitrates.

Great write up and should be easy to follow along for anyone attempting this.

I haven't tried it myself, but what kind of latency are you talking about when you go above 150Mbps?
 
Great write up and should be easy to follow along for anyone attempting this.

I haven't tried it myself, but what kind of latency are you talking about when you go above 150Mbps?

Yes the OP on reddit did a good job. I asked them about latency, and they came back with the following -

At 150 Mbps I will with h.264+ be getting around a 25-30ms stable with peaks of 50-60ms, at the max It allows me which is 236Mbps I will be getting a 38-47ms average with peaks of 70-80ms.
 
Yes the OP on reddit did a good job. I asked them about latency, and they came back with the following -

At 150 Mbps I will with h.264+ be getting around a 25-30ms stable with peaks of 50-60ms, at the max It allows me which is 236Mbps I will be getting a 38-47ms average with peaks of 70-80ms.

Thanks. It's still not great though. For example, his 236Mbps results, I am getting the roughly the same latency on a cheap AC router but at 400Mbps.

For those sort of results, I still think you would be better off getting a dedicated router. You can get second hand AX routers for less than £50 and AC routers for even less than that.

I guess it's useful for those people who have no other option. But I am not sure why else anyone would want to do this? If I am going to lose my wireless freedom, I would want my wired connection to be better not worse.
 
Back
Top Bottom