Quest Pro with Ethernet | How-to

[nikoel]

What is this?

A guide on how to connect your quest pro to your router via ethernet instead of WiFi for use with Virtual Desktop

Why do I want this?

Depending on your router, location, speed etc... a cable connection can result in fewer artifacts, an ability to push higher bandwidth, a more stable connection with fewer micro stutters and tears and much faster eye tracking. The user may have more money to spend on DCS modules as they no longer need to purchase a WiFi 6/e router

(I have a WiFi 6e Router - for me no improvements in bandwidth and overall image quality - but I have fewer artifacts, rock solid frame stability and much faster eye tracking)

What do I need?

• A Quest Pro
• Data USB Cable to connect the Quest Pro to your Computer
• A fast Ethernet cable from your computer to the router, an equally fast Ethernet cable from your router to your Quest Pro
• A Router with DHCP
• A Ethernet to USB-C adapter - I used https://www.unitek-products.com/products/usb-c-to-gigabit-ethernet-5gbps-aluminium-adapter
• Virtual Desktop
• Recommended: A high quality USB-C Female/Male *data* extension cable so you can leave the ethernet adapter on the desk and just run one cable to the headset

Guide

In short, Meta have disabled ethernet by default. To enable it you need to input a command into your headset via something that is called ADB (Android Debug Bridge). To do this you are required to have Developer Mode turned on and the headset connected to your computer to input this command

Disconnect QuestPro from computer

Put your headset into developer mode (inside the phone app and headset settings). It's actually very simple. Screenshot flow on how to do this is here: https://help.arborxr.com/en/articles/6333136-developer-mode-on-meta-quest-devices

Plug the headset into your computer via any *DATA* USB cable.

Next, put the headset over your head and inside the headset allow the incoming connection (a Virtual Reality popup will appear as soon as the USB connection is being made)

Install Android Studio

Navigate to the folder ADB is installed. For me it was in Users/~Username~/AppData/Local/Android/Sdk/platform-tools. AppData folder may be hidden - make sure to view hidden folders in explorer

Right click anywhere inside the folder (but not on any of the files) - Open in Terminal

 

Then run the following command to double check that everything is good to go

.\adb devices

Your quest pro should come up as some bunch of numbers and characters. It should tell you if it's authorised (aka if you performed the above steps correctly)

Then run the following command

.\adb shell setprop debug.usb.ethernet.enabled 1

Disconnect your quest pro USB cable. Plug in ethernet adapter. Into the ethernet adapter connect PD power source and ethernet cable. Connect the other end of the ethernet cable to the router. (If you, like me forgot to order your USB extension cable, your quest pro should now look like this):

Inside your headset settings turn off wifi. If you still have interwebs then she is working gud. The ethernet lights should also be flashing

Documentation on ADB within Meta ecosystem: https://developers.meta.com/horizon/documentation/native/android/ts-adb/

Closing Concerns

This is not officially supported by Virtual Desktop. I believe this is because Meta could theoretically remove this feature at any time, leaving us at their mercy if they decide to alter the code or delete the feature. (I’ve disabled updates until other guinea pigs update their headsets first and confirm it’s safe.) Nonetheless, it’s not really a risk, since Meta seems hell-bent on bricking everyone’s devices with updates regardless of which features are installed.

Frequent User Errors

• Not using a data delivery USB cable (i.e. the default cable used for charging only)
• Only enabling the developer mode inside the headset or inside the iPhone/Android App. Both are required
• Not putting on the headset and accepting the connection inside VR when connecting QuestPro to PC
• Not providing power to the ethernet adapter
• Plugging the ethernet cable directly from computer to the headset. Need a router with DHCP

Edited December 29, 2024 by nikoel

[Panzerlang]

Jesus, and I thought doing it with the Pico4 was a PITA.

[Qcumber]

I tried this a few weeks ago and could not get it to work. I might try again. 

[nikoel]

It's easier than what it reads. Much like a certain yesteryear guide from long ago, I tried making the steps user error proof. Which meant writing additional instructions that most users would not need (i.e. Not using a power only USB cable etc...)

This entire thing can be summarised as: Connect the headset with developer mode enabled via USB to computer, go to ADB folder and run terminal, input the command, disconnect from computer and finally connect the peripherals to the router and power - done

Edited December 29, 2024 by nikoel

[Qcumber]

Got it working and eye tracking is definitely better. I am also getting 400mbps with a very smooth experience. 

One step I did not see on your list though is that I had to confirm connection on the headset before I could run the code. 

[nikoel]

1 hour ago, Qcumber said:

Got it working and eye tracking is definitely better. I am also getting 400mbps with a very smooth experience. 

One step I did not see on your list though is that I had to confirm connection on the headset before I could run the code. 

I did put this step into the guide. I'll think of a way to make it more clear. Here is the step copied and pasted:

"Plug the headset into your computer via any *DATA* USB cable. Put on the headset and allow the incoming connection (popup will appear as soon as the USB connection is being made)"

Glad you're enjoying it. May I ask which one of the two code snippets worked for you and what is different to when you tried it first time?

Edited December 29, 2024 by nikoel

[Qcumber]

39 minutes ago, nikoel said:

I did put this step into the guide. I'll think of a way to make it more clear. Here is the step copied and pasted:

"Plug the headset into your computer via any *DATA* USB cable. Put on the headset and allow the incoming connection (popup will appear as soon as the USB connection is being made)"

Glad you're enjoying it. May I ask which one of the two code snippets worked for you and what is different to when you tried it first time?

The "./" one worked for me.

When I tried before I couldn't get it to connect to the headset. Your instructions are very good so a lot easier. It took me less than 5 minutes to get up and running. 

[Simo]

On 12/29/2024 at 12:21 PM, nikoel said:

I did put this step into the guide. I'll think of a way to make it more clear. Here is the step copied and pasted:

"Plug the headset into your computer via any *DATA* USB cable. Put on the headset and allow the incoming connection (popup will appear as soon as the USB connection is being made)"

Glad you're enjoying it. May I ask which one of the two code snippets worked for you and what is different to when you tried it first time?

Many thanks for the guide, and highlighting the above step - I'd tried this before based on guides on hoggit without success, but finally got it working as you described. Cheers!

[halufpv]

Sorry if this is a stupid question, but what's the point of this vs using Quest Link via cable?

[HiWay]

Sorry if this is a stupid question, but what's the point of this vs using Quest Link via cable?

Only if you are 100m from your PC


Sent from my SM-S906E using Tapatalk

[sleighzy]

1 hour ago, halufpv said:

Sorry if this is a stupid question, but what's the point of this vs using Quest Link via cable?

VirtualDesktop can be more performant than Quest Link (it has a lot smaller overhead for VRAM) for a lot of folk, and is less prone to the issues you can get with Quest Link app at times. Easier to setup and configure items, more encode options, and has additional features like pass through for bringing things into your VR environment.

[ischicopter]

3 hours ago, halufpv said:

Sorry if this is a stupid question, but what's the point of this vs using Quest Link via cable?

way better picture quality

better performance

better reprojection technique

easier to set up and better customization options

passthrough features

less bugs, 24/7 support on the Discord and ongoing development and updates

 

You are seriously missing out if you don´t buy it. Unless you are playing on a potato anyway...

 

[nikoel]

10 hours ago, Simo said:

Many thanks for the guide, and highlighting the above step - I'd tried this before based on guides on hoggit without success, but finally got it working as you described. Cheers!

There was a Hoggit guide...?!

Damn - I had to research and build this out from scratch and now I feel stupid for not looking there first as it took me hours of trial and error. Either way you're welcome. Glad it helped and thank you for replying as I was thinking it was too niche for me to bother writing it out and it would get lost in the depths of the forum

6 hours ago, halufpv said:

Sorry if this is a stupid question, but what's the point of this vs using Quest Link via cable?

 

You already have a few answers. But it comes down to somehow Virtual Desktop is able to do more with less. QuestLink is semi AbandonWare for Meta. They treat it like a bastard child and they have a habit of breaking it, hell they couldn't be bothered renaming it. In theory I agree, USB 3.2 connection it should be better, but it ain't and it's Meta's fault

Some people prefer QuestLink, and it might work better for them. The main thing here is that we have options and you're now free to chose between QuestLink WiFi or USB, Virtual Desktop Wifi or Ethernet. More options and more ways to get the experience that you want from an extremely expensive, niche hobby that we all love

In regards to one of the above comments, I already had a WiFi 6e Router 30 cm away from my headset that is solely dedicated to running VR. Ethernet was still an upgrade for me personally, and from a handful of people looks like I was not alone. You can read in my first post where the experience became better [for me] and where it didn't

 

Edited January 2 by nikoel

[diamond26]

15 hours ago, halufpv said:

Sorry if this is a stupid question, but what's the point of this vs using Quest Link via cable?

VD is definitely better in how it manages VRAM and offers mostly a more stable environment compared to Quest Link. Also you can now block Meta’s updates (by switching off WiFi)  and save yourself from the possibility of having a headset that doesn’t work as it should. The biggest flaw compared to Link is its reprojection method (SSW) which is still way behind ASW.
And with this proposal you eliminate the need of a dedicated Wi-Fi router and have less latency. I will soon try to find out .
Thanks @nikoel for highlighting this one!

Edited January 2 by diamond26

[Qcumber]

On 1/1/2025 at 6:17 PM, halufpv said:

Sorry if this is a stupid question, but what's the point of this vs using Quest Link via cable?

I use both. Overall there is very little difference between the two.

• I find that image quality is slightly better with meta link cable.
• Eye tracking might be very slightly better with VD.
• VD has some slight lag when moving your head quickly; you can see black edges which I don't see with meta link.
• VD reprojection is inferior to ASW.
• Although VD has more video encoding options, I find that h264+ gives me the best performance/quality. With wifi I can only manage a stable performance at 200mbps. With the ethernet cable I can max out at 400mbps. With meta link I can max out at 960mbps. 
• I had hoped that QVFR would be incorporated into VD but it looks like this is not going to happen now. 

I prefer using meta link but I keep up to date with VD as there are sometimes issues with meta updates.

Edit: I have retested this and am now erring towards VD with ethernet over meta link. The performance is so much better at 400mbps and very stable. The VRAM usage is also significantly less than with meta link. 

 

Edited January 2 by Qcumber

[Simo]

11 hours ago, nikoel said:

There was a Hoggit guide...?!

Yup, here it is.

Following those steps didn't work for me, so I'm glad you didn't see it and took the time to put together a more idiot-proof guide!

[diamond26]

@nikoel I wondered if the statement I made regarding no updates from Meta, since the wifi can be turned off, is valid. The reason I'm raising this is because a friend of mine who uses the method on a Q3 said that the headset has still access to internet. As I haven't yet purchase the necessary stuff for testing can you check this one?

[nikoel]

13 minutes ago, diamond26 said:

The reason I'm raising this is because a friend of mine who uses the method on a Q3 said that the headset has still access to internet. As I haven't yet purchase th

It has internet access updates will apply

The way to turn off auto updates is via settings -> updates toggle all to off

[diamond26]

Thank you @nikoelfor this guide. I just installed it (HW and SW) for Qpro and it works wonders in terms of stability and performance. It’s equal in stability to Link. For true performance I will have to run some tests on equal basis (resolution wise).

I was really surprised with the results as I have a dedicated Wi-Fi 6 router connected at 2400.

[Ironmexx]

On 1/3/2025 at 6:15 PM, nikoel said:

It has internet access updates will apply

The way to turn off auto updates is via settings -> updates toggle all to off

I used ADB command from computer: adb shell pm disable-user --user 0 com.oculus.updater

But when you turn off your quest there still a slider that says "install updates before shutdown" Just off to avoid install updates.

[diamond26]

After using this solution for some days now I can confirm that is a very good solution for stability over wifi option and as a bonus you get the benefits of using VD for other stuff too. My only gripe so far is the limited SSW option when it comes to reprojection technic. ASW from Meta is still better implemented.

[nikoel]

On 1/14/2025 at 8:44 AM, diamond26 said:

Thank you @nikoelfor this guide. I just installed it (HW and SW) for Qpro and it works wonders in terms of stability and performance. It’s equal in stability to Link. For true performance I will have to run some tests on equal basis (resolution wise).

I was really surprised with the results as I have a dedicated Wi-Fi 6 router connected at 2400.

Thanks mate, glad its working for you

[EightyDuce]

Just did this one my Q3 with very positive results. Using VD on WiFi connected to my Unifi U7Pro, it was extremely bipolar. It would be baby smooth 72Hz Godlike 120Mbit AV1 with SSW disabled, but every ~15 sec like clockwork, it would have a 1-second hiccup where latency jumps from 31-40 to 60, FPS drops from 72 top low 60's and game latency goes from sub 10 to 30+. Then drop back down to normal, drove me nuts. AirLink wasn't much better, straight USBC to PC link was smooth.

Same settings, with an ethernet adapter and its rock solid at the same settings. May try push bitrate more beyond 120/200. FPS locked at 72, no SSW, latency is 31-42, game latency is 8-13, encode 3-5 network latency is 0-1, decode is 10-13. 

Anyone run one of these with a head-strap battery kit?

Edited January 19 by EightyDuce

[Simo]

Is anyone actually able to maintain a constant 72fps with VD? Even on the main menu (hangar) screen I get a slight fluctuation from 71-72 FPS in VD, while in Link I get a flat line 72 FPS.

I'd prefer to use VD over Link due to the slightly crisper visuals, but the increased stutter due to not beng able to hold a solid 72fps puts me off.

Originally thought this might be down to poor WiFi connection, but get the same result connected via ethernet per nikoel's method. Even on potato settings the fluctuation is there.

[EightyDuce]

9 minutes ago, Simo said:

Is anyone actually able to maintain a constant 72fps with VD? Even on the main menu (hangar) screen I get a slight fluctuation from 71-72 FPS in VD, while in Link I get a flat line 72 FPS.

I'd prefer to use VD over Link due to the slightly crisper visuals, but the increased stutter due to not beng able to hold a solid 72fps puts me off.

Originally thought this might be down to poor WiFi connection, but get the same result connected via ethernet per nikoel's method. Even on potato settings the fluctuation is there.

I'll have to turn the overlay back on next time, but by just visual feels, its buttery smooth.